Re: Question: kernelopts on raspberry pi
by Steven A. Falco
I tried adding:
GRUB_CMDLINE_LINUX="selinux=0"
to /etc/default/grub, then ran:
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
That successfully added the following to grub.cfg:
if [ -z "${kernelopts}" ]; then
set kernelopts="root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro selinux=0 "
fi
However, /boot/efi/EFI/fedora/grubenv didn't contain "selinux=0". So I manually added that via:
grub2-editenv - set "kernelopts=BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.8.0-1.fc33.aarch64 root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro selinux=0 "
But that doesn't seem to have any effect. After booting, I still see:
# cat /proc/cmdline
BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.8.0-1.fc33.aarch64 root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro
Where does the kernel get its command line on RPi?
Steve
On 9/8/20 3:56 PM, Steven A. Falco wrote:
> I'd like to add a kernel command line option (selinux=0) on a raspberry pi.
>
> Normally, I'd edit /etc/default/grub and append that setting to the GRUB_CMDLINE_LINUX variable, then run grub2-mkconfig to regenerate the /boot/efi/EFI/fedora/grub.cfg file.
>
> However, on the pi, /etc/default/grub doesn't have a GRUB_CMDLINE_LINUX variable defined. Yet, I do see this line in /boot/efi/EFI/fedora/grub.cfg:
>
> set kernelopts="root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro "
>
> To accomplish what I want, should I add a new GRUB_CMDLINE_LINUX variable to /etc/default/grub, for example:
>
> GRUB_CMDLINE_LINUX="root=UUID=36a097ba-7577-4cc9-977e-df76c6590c48 ro selinux=0"
>
> Or is there a more correct way to do this?
>
> Steve
3 years, 8 months
Re: Raspberry Ugrade to ARM Fedora 30
by ng0177＠gmail.com
Dear All,
I have now disabled any DNS resolver related services and was able to
reproduce your successful upgrades. However, I get
[pi@raspi ~]$ lsb_release -d;uname -r
Description: Fedora release 30 (Thirty)
5.0.10-200.fc29.aarch64
Should I wait until Fedora 30 is officially supported? Thanks, Thomas
On Wed, May 1, 2019 at 8:57 PM Paul Whalen <pwhalen(a)redhat.com> wrote:
>
>
> ----- Original Message -----
> > > Dear All, to upgrade a Raspberry 3 I executed this commands
> > >
> > > sudo dnf -y upgrade --refresh
> > > sudo dnf -y install dnf-plugin-system-upgrade
> > > sudo dnf -y system-upgrade download --releasever=30
> > > sudo dnf -y system-upgrade reboot
> > >
> > > after the reboot dnf fails. Is anyone else having the problem?
> >
> > I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30, and
> > do not see your problem. Dnf works as expected in F30 for "dnf
> > system-upgrade clean", "dnf list upgrades", and "dnf upgrade".
>
> I just did another upgrade on the rpi3 starting with the minimal f29
> aarch64
> image and using the same commands. No issues here either.
>
> What was the error you hit in dnf? Is there anything helpful in the logs?
>
> Paul
>
>
>
>
>
5 years, 1 month
Re: Unable to see 'Initial setup wizard' on Raspberry PI 3 using aarch64 images
by Peter Robinson
On Wed, Nov 22, 2017 at 12:58 PM, Ashwin Rao
<ashwin.shirvanthe(a)gmail.com> wrote:
> On Wed, Nov 22, 2017 at 11:46 AM, Peter Robinson <pbrobinson(a)gmail.com>
> wrote:
>>
>> On Wed, Nov 22, 2017 at 9:37 AM, Ashwin Rao <ashwin.shirvanthe(a)gmail.com>
>> wrote:
>> > Hi,
>> >
>> > When running the aarch64 Workstation, Server, and Minimal images I am
>> > not able to see the initial setup wizard. I can see the messages shown
>> > during boot but after some time the screen either starts to flicker or just
>> > blanks out. I tried this on 3 different raspberry Pis with different cards
>> > and the result is always the same.
>> > The steps I followed are
>> > 1. I downloaded the aarch64 images from [
>> > https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_P...
>> > ] and followed the instructions mentioned on the same web page to prepare
>> > the images using xzcat.
>> > 2. I connect the HDMI cable of my monitor, and connect the keyboard and
>> > mouse. I am not connecting an Ethernet cable.
>> > 3. I can see the boot screen, and the messages showing that the device
>> > is booting.
>> > 4. After some time the screen either blanks out or starts to flicker. I
>> > have tried it with different monitors and different power supplies as well
>> > but the result is the same. I noticed that the red LED of the Raspberry Pi
>> > also starts to blink abruptly.
>> >
>> > I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I
>> > doubt there is an issue with the card, the power supply, or with the Pis.
>> >
>> > It would be nice if someone suggests the things I need to do, or if
>> > someone was able to troubleshoot similar issues.
>>
>> The problem is with either the monitor or the HDMI cable, the VC4 open
>> driver (which neither of the other distros use yet) can be a bit
>> fragile with some EDID responses from some monitors or cables (yes
>> we've had people with issues that were fixed when they swapped the
>> HDMI cable). It's improved a lot since F-25 when we first started
>> supporting the RPi but it's not perfect yet.
>>
>> On the case of Server and Minimal if you never want to use a graphical
>> interface and are happy with just the text console you can add a
>> blacklist so the GPU driver isn't laoded on boot. This can be done by
>> adding blacklist=vc4 to the kernel command line or creating a file
>> /etc/modprobe.conf/vc4.conf with the line "blacklist vc4"
>>
> Thank you for the suggestion. I currently do not need the graphical
> interface, so I tried again with the Server image.
> Adding module_blacklist=vc4 instead of blacklist=vc4 to the kernel command
> line allowed me to get to the login prompt.
Yep, sorry, was replying on my mobile from memory and didn't have the
exact details to hand for the kernel cmd line :-/
6 years, 6 months
Re: Raspberry PI 3 locking up
by Sean Omalley
I have a 2.5amp power supply too. It stopped responding twice since I have updated (which took around 10 hours.)
I went to dinner and came back, and the monitor (tv in this case) was off, as it shuts itself off after not getting a signal for x amount of time. The keyboard didn't respond to any input. The ssh session I had open locked up, and I couldn't connect to it on the IP address the router said it was using. (it keeps incrementing, which is annoying and strange in it's own right.) This is the last part of that log.
It is connected to the network via a wireless dongle. But I didn't have issues with that adapter on x86 when I had other network issues with the built-in adapter.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net NetworkManager[742]: <info> [1485989019.9453] manager: NetworkManager state is now CONNECTED_SITE
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=742 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [21fdc, 21fe0) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [220c0, 220c4) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel: alloc_contig_range: [220c4, 220c8) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]: req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]: req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:43:50 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net NetworkManager[742]: <info> [1485989065.1881] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=742 comm="/usr/sbin/NetworkManager --no-daemon " label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount: Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]: req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]: req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:44:35 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 01 18:01:01 unknownc83a35b012e1.attlocal.net CROND[2082]: (root) CMD (run-parts /etc/cron.hourly)
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2085]: (/etc/cron.hourly) starting 0anacron
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2091]: (/etc/cron.hourly) finished 0anacron
________________________________
From: Rafael Leiva-Ochoa <spawn(a)rloteck.net>
To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <wdh(a)dds.nl>
Cc: arm(a)lists.fedoraproject.org
Sent: Wednesday, February 1, 2017 5:04 PM
Subject: [fedora-arm] Re: Raspberry PI 3 locking up
I will try my 2.5 amp power supply tonight. If I still see the same problems I will go ahead and respond back to the same email.
On Wed, Feb 1, 2017 at 11:41 AM Winfried de Heiden <wdh(a)dds.nl> wrote:
Hi all,
>
>Double checked: 2.5A power supply.Winfried
>
>
>Op 01-02-17 om 13:58 schreef Winfried de Heiden:
>
>Hi all,
>>
>>
>>I don't know by head but it should be enough; it worked for weeks and it is sold as "the official PI power supply".
>>
>>
>>I'll check tonight to be shure.
>>
>>
>>Winfried
>>
>>
>>-----Oorspronkelijke bericht-----
>>
>>
>>Datum: Wed, 1 Feb 2017 11:27:45 +0000
>>Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
>>Cc: arm(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn(a)rloteck.net>
>>Aan: Winfried de Heiden <wdh(a)dds.nl>
>>Van: Peter Robinson <pbrobinson(a)gmail.com>
>>On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
>>Hi all, Same for me, since a couple of days the Rapsbery Pi 3 suddenly stops. One or
two time I was quick enough to catch a kernel panic on the screen. Looks like a kernel thing to me. I moved the SD-card to my " old" Raspberry
Pi 2 (two), the same installation is running fine for a couple of days.
What is the AMP rating of your power supplies?
>>Screen shot of the kernel panic attached. I think I' ll create a bugzilla on
this. Winfried Op wo, 1 feb 2017 om 1:26 , schreef Rafael Leiva-Ochoa <spawn(a)rloteck.net>: Hi Everyone, I've been running a raspberry pi 3 with Fedora release 25 (Twenty Five)
using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the last 2
weeks that my Pi locks up. I tried hooking it up to an HDMI monitor, and USB
keyboard to see if the system generates any message, but I only get a blank
screen and no reaction from the keyboard. I have looked at the
/var/log/message, and dmesg, and I don't see anything that could be causing
the problem. I was thinking it could be overheating, but Fedara 25 does not
support any of the rasbian commands to run heat sensor checks. Any ideas? Thanks, Rafael _______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>>
>>
>>_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
7 years, 4 months
beginning of Fedora support for the Raspberry Pi 2
by Peter Robinson
Hi All,
As a follow up of the discussion that happened at the last ARM meeting
(and because 3 days post announcement of it I'm sick of repeating
myseld:-P ) I thought I'd outline the process for getting support for
the Raspberry Pi 2 into Fedora
The first phase I believe should be a remix, with the modified
packages required to support the install for that remix being is a
published repository, while we're awaiting all the bits to land
upstream.
The short term repository should only contain the following:
* kernel
* bootloader
* firmware
* mainline userspace packages that need non upstream pacakges
Everything else (eg xorg drivers) should be packaged up and go through
the standard package review process and be in mainline Fedora.
>From there we can spin a remix image for testing.
BUT before we get to that we need to review all the
projects/sources/packages that are needed and document what packages
are needed and where the upstream is located. In the case of firmware
we also need to ensure it's re-distributable. Does the GPU firmware
still boot or is it now possible to use the upstream u-boot support to
boot the device and then load the firmware via the kernel like other
standard drivers that need firmware, or do we even need binary
firmware any more?
I believe Seneca has volunteered to spear head this so it would be
great if they can start by documenting the above and post the details
of it in response to this mail so we can work out what needs to be
done and where in preparation for the remix, this will then give us a
good picture as well when we might be able to just support it by the
standard mainline process.
Regards,
Peter
9 years, 4 months
Re: [fedora-arm] beginning of Fedora support for the Raspberry Pi 2
by Robert Moskowitz
On 02/04/2015 10:43 AM, Peter Robinson wrote:
> Hi All,
>
> As a follow up of the discussion that happened at the last ARM meeting
> (and because 3 days post announcement of it I'm sick of repeating
> myseld:-P ) I thought I'd outline the process for getting support for
> the Raspberry Pi 2 into Fedora
Just a small question...
I have not found a schematic, but the pics do not seem to show a SATA
interface. Is this correct?
No SATA, I have no time for it; I am already crunched for time.
Though it would be nice.
9 years, 4 months
Re: Fedora 25 - Raspberry Pi - errors
by Peter Robinson
On Tue, Dec 20, 2016 at 9:20 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
> Hi all,
>
> Fedora 25 on Raspberry PI 3 gives lot's of errors: (journalctl -l -p err)
>
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
>
> Everything works fine, but what's failing and what to do to solve it?
They're mostly just spurious and can be ignored, upstream kernel
developers are aware and they'll be debugged/fixed at some point in
the future.
7 years, 5 months
Re: Raspberry pi 3: btrfs as root fs and uboot (or grub?)
by Peter Robinson
On Tue, Dec 13, 2016 at 12:55 PM, Tomasz Kłoczko
<kloczko.tomasz(a)gmail.com> wrote:
> Hi,
>
> Current rawhide fedora image is using xfs has a bit higher memory
> requirements than btrfs so I've started thinking about migration of my
> current image to new root fs on new card.
>
> Looking on partition table on rawhide image served by fedora I see:
>
> Device Boot Start End Sectors Size Id Type
> /dev/mmcblk0p1 2048 61439 59392 29M c W95 FAT32 (LBA)
> /dev/mmcblk0p2 * 61440 1060863 999424 488M 83 Linux
> /dev/mmcblk0p3 1060864 2060287 999424 488M 82 Linux swap / Solaris
> /dev/mmcblk0p4 2060288 15126527 13066240 6.2G 82 Linux swap / Solaris
>
> Q1: for what is this fat32 first partition?
The raspberry pi firmware
> Q2: is it possible to install uboot files from /boot on btrfs? (on x86 and
No. But there's no u-boot files in boot, they're on the VFAT
partition. I don't believe u-boot supports loading kernel/initrd from
btrfs though.
> grub it is no problem with this)
> Q3: seems someone done porting of the grub to arm so why there is n grub2
> package in fedora?
Because there's a lot of usecases that doesn't work with it. Some of
it histotical, but basically it comes down to someone to spend the
time to do all the work and QA to move over to it. Basically if i'ts
not broken why fix it...
7 years, 4 months
Re: Fedora 25 - Raspberry Pi - errors
by Peter Robinson
On Tue, Dec 20, 2016 at 10:29 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
> Now, that's nice to know, but what is causing these errors?
They should be fixed in the 4.9.2 kernel that will be headed to
updates-testing some time today. There was a number of fixes for i2c
on the RPi land in the upstream 4.10 kernel and I've back ported them
(and a few other fixed) to the 4.9 stable kernels.
> Is there a Bugzilla?
No there wasn't.
P
> Op 20-12-16 om 10:32 schreef Peter Robinson:
>
> On Tue, Dec 20, 2016 at 9:20 AM, Winfried de Heiden <wdh(a)dds.nl> wrote:
>
> Hi all,
>
> Fedora 25 on Raspberry PI 3 gives lot's of errors: (journalctl -l -p err)
>
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
> Dec 20 09:44:33 ipa.blabla.bla kernel: i2c-bcm2835 3f805000.i2c: i2c
> transfer failed: 100
>
> Everything works fine, but what's failing and what to do to solve it?
>
> They're mostly just spurious and can be ignored, upstream kernel
> developers are aware and they'll be debugged/fixed at some point in
> the future.
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
>
7 years, 4 months
Re: Raspberry Pi and its 7" display
by Torbjorn Jansson
On 2018-12-11 03:20, Peter Robinson wrote:
>> I'd like to turn this into a MythTV server (with a USB capture) and use
>> the display as a system console with the ability to watch videos on it.
>> (Yeah, I'm aware that its only a 800x400 screen.) Failing that, I'd
>> like to use it in a "tablet" mode and get used to the touch screen
>> interface.
>
> Well when it's supported upstream it will be enabled.
>
> [1] https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
A bit off-topic but i just checked the url above and noticed something:
Under section "Power Supplies" we have this text:
"The Raspberry Pi 3 Series needs a 2.5W PSU"
Surely this must be a typo, 2.5W would mean 5v at 500mA and that's unlikely to
be enough for a rpi3, even older official power supplies was 2amp and that is 10W
So it must be Amps and not Watts.
5 years, 5 months
