"No GPUs found with udev" gnome-shell error on Raspberry Pi 3b+
by Brion Vibber
Hi all!
I've got a Raspberry Pi 3b+ with Fedora 30 on SD cards running armv7 and
aarch64. I recently installed updates with dnf on both after a few weeks,
and after reboot I can no longer get into a graphical login.
The shell fails to find a GPU which leads the session to fail:
---------
Apr 26 02:49:52 lilbit gnome-shell[916]: Failed to create backend: No GPUs
found with udev
Apr 26 02:49:52 lilbit gnome-session[889]: gnome-session-binary[889]:
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 26 02:49:52 lilbit gnome-session-binary[889]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1
Apr 26 02:49:52 lilbit gnome-session-binary[889]: Unrecoverable failure in
required component org.gnome.Shell.desktop
Apr 26 02:49:52 lilbit systemd-logind[725]: Failed to restore VT, ignoring:
Input/output error
---------
(Don't mind the wrong date, the system clock is wrong until networking
comes up.)
These SD cards were originally installed with Fedora 29 and upgraded via
dnf-system-upgrade, so that might lead to something funky in the boot
partitions perhaps; if that's an expected sort of failure I can just
reinstall. :)
Thanks for any advice!
-- brion
4 years, 3 months
F-30 Raspberry Pi 3B+ MMC/MicroSD sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt.
by Jan Kratochvil
Hi,
just copying from:
https://bugzilla.redhat.com/show_bug.cgi?id=1607872#c8
On Raspberry Pi 3B+ when I boot from MicroSD from USB adapter all works fine.
When I use the same MicroSD into the MicroSD slot of Raspberry it boots fine
and when it should be display text login prompt it prints:
[ 70.246299] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware interrupt.
And it is mostly dead (it pings but no sshd works anymore, NumLock works but no login prompt etc.).
Raspbian boots fine there even directly from MicroSD.
kernel-5.1.11-300.fc30.aarch64
kernel-5.2.0-0.rc3.git3.1.fc31.aarch64
I see nowhere on this list mentioned this problem, really nobody is using
MicroSD directly?
Jan
4 years, 3 months
Moving root fs to sata
by Steven A. Falco
I have a wandboard quad, and I'd like to move the root filesystem to a sata drive. I have the drive connected and formatted, and I copied all of "/" to a partition on the sata drive.
Now the question is "where do I need to change the UUID to match that of the new partition".
I know I need to change /etc/fstab, /boot/extlinux/extlinux.conf and perhaps /boot/grub/grub.conf, but do I also have to regenerate the initramfs images, and if so, what command would I use so they contain the correct UUID and drivers?
If I need to rebuild the initramfs, that would be a bit of a chicken and egg problem, because I would not be able to boot from the sata drive until I rebuilt it, but if I rebuilt it while running from the SD card, I'd guess the rebuilt initramfs would still reference the SD card.
Steve
4 years, 5 months
Raspberry Pi 3 B+ dmesg errors
by Felix Geschwindner
Hi guys,
I managed to get Fedora 30 AARCH64 installed on a RPI 3B+ and it mostly runs great but I'm hitting a couple issues that I'm just not sure where to start looking.
In order to make sure it's not the set of packages I'm installing, I brought up a second RPI 3B+ that runs the official minimal image. I installed all the same packages on the kicked system, that the minimal version has, so I don't have differences.
1. The NIC LED doesn't work after the installation. It works normally during kickstart. Connectivity is not affected. NIC LED works fine with the official image.
2. I get these messages in dmesg on a kicked system that are not poping up on the minimal image system:
...
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
...
[ 0.011655] arch_timer: WARNING: Invalid trigger for IRQ75, assuming level low
[ 0.011658] arch_timer: WARNING: Please fix your firmware
...
[ 1.887602] kvm [1]: Invalid trigger for vtimer IRQ76, assuming level low
...
3. Looks like the model that is being detected is different for both systems (where does that come from? Does that have effects somewhere?):
Minimal image:
[ 0.000000] Machine model: Raspberry Pi 3 Model B+
Kickstart:
[ 0.000000] Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
4. The kickstarted system has an additional CPU feature that the minimal image system doesn't have (They should have the same CPU?)
[ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
5. There is a couple more differences like hci initialization and other things. Isn't this part of the kernel support? And the kernel is the same on both systems.
Is there documentation around the generation of the RPI image? I replicated the kickstart file that can be found under /root on the minimal image but that alone didn't help above issues. Maybe there is something special about the environment this image is generated in?
Thanks
4 years, 5 months
Align the Fedora ARMv7 & AArch64 Spins offered in F31
by Paul Whalen
We currently offer a large group of Desktop Spins for ARMv7 in Fedora.
Initially we enabled all the desktops that ship for x86_64 to bring ARMv7
to parity, but for AArch64 we took a more conservative approach and only
enabled a select few.
In preparation for Fedora 31 we would like to reduce the Spins offered
to realistically reflect what people are actually using and ensure we
aren't shipping things that don't work.
The current list of Spins:
For ARMv7 - Workstation, KDE, LXDE, LXQt, Mate, Minimal, SoaS, Server,
Python Classroom
For AArch64 - Workstation, Minimal, Server
Proposed list for F31+:
For both ARMv7 and AArch64 - Workstation, Xfce, Minimal, Server
If there is a spin that you care about which is not included in the
proposed list and you would like to be a 'co-maintainer'- who will be
responsible for periodic testing during the development cycle and
filing bugs on issues you discover- let us know and we can add it back
in.
If you have any other concerns, please let us know as well.
Regards,
Paul
4 years, 5 months
Bluetooth on Udoo Neo ?
by Ken Harris
Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI
WL1831 module.
I tried :
hciattach -n ttymxc2 texas
... but got "Initialization timed out."
I also tried various combinations of bit rates and flow control.
Any tips are welcome.
-K
4 years, 5 months
Kernel 5.0 value add for Fedora arm?
by Robert Moskowitz
I am looking at summaries of features in the 5.0 kernel.
I will have to dig into what the Fscrypt algorithm is and what that
means, but..
I see support for RPi touchscreen.
Will this add RPi touchscreen support for Fedora-arm? I suspect a lot
more is needed than just a driver.
What about other touchscreen for other arm SOC?
Anything else I should look at and maybe take advantage of....
thanks. Good weekend to all.
4 years, 5 months