Fwd: sd-host-bcm2835-not registering properly in f31 arm .raw files
by Thomas Gilliard
requested to send to list:
-------- Forwarded Message --------
Subject: sd-host-bcm2835-not registering properly in f31 arm .raw files
Date: Fri, 19 Jul 2019 10:33:50 -0700
From: Thomas Gilliard <satellitgo(a)gmail.com>
To: pbrobinson(a)gmail.com
CC: satellitgo(a)gmail.com
Peter;
I have done a nodebug kernel [1] on soas;KDE;LXDE with 32 GB microSD
cards. All work smoothly and much faster afterwards.
"sd-host-bcm2835-not registering properly" so debug kernel keeps trying
to register it until it fills up the card.
Is there a missing file on the f31 spin . .raw files that precludes
registration?
I notice that the arm file:
ubuntu-mate-18.04.2-beta1-desktop-armhf+raspi-ext4.img Has a
"sd-host-bcm already registered - abort " on boot
This debug messaging appears to dominate all 3 spins to the point that
only a very few processor cycles are devoted to the spin itself.
This almost requires using a nodebug kernel to test spins on the Rpi3B+
Tom Gilliard
satellit on #fedora-arm
[1]
https://wiki.sugarlabs.org/go/Fedora_31#Enabling_the_rawhide_kernel_nodeb...
4 years, 9 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, 9 months
Rspamd Package for Fedora 30 armhfp
by arm_ml@rirasoft.de
Hello together,
I'm in the process to build up a new mailserver.
Old one: Odroid HC1 with CentOS 7; postfix with postscreen, amavis-new,
spamassassin, clamav, dovecot < runs smoothly nearly 2 years.
New One: Odroid HC1 with Fedora 30; postfix, dovecot, rspamd? < should
be state-of-the-art.
I can't find any package for rspamd for armhfp, neither Fedora or
https://rspamd.com/downloads.html. I only found x86_64.
Greetings
Andreas
4 years, 9 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, 9 months