Fedora on Rock 5B
by Andreas Reschke
Hi there,
I've tried to install Fedora on my Rock 5 without success.
Booting with
https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock...
on SD-Card and source from
https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everyth....
Board boots up fine but later starting in loop with
350.456154] dracut-initqueue[1065]: Warning: ############# Anaconda
installer errors end ###############
[ 352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[ 352.161387] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh: "[ -e
"/dev/root" ]"
[ 352.164564] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[ "$main_loop"
-ge "10" ]"
[ 352.167716] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f
/tmp/settle.done ]"
[ 352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue:
starting timeout scripts
[ 352.172610] dracut-initqueue[1065]: Warning: ############# Anaconda
installer errors begin #############
[ 352.172852] dracut-initqueue[1065]: Warning: #
#
[ 352.173097] dracut-initqueue[1065]: Warning: It seems that the boot
has failed. Possible causes include
[ 352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2 or
inst.repo boot parameters on the
[ 352.173537] dracut-initqueue[1065]: Warning: kernel cmdline. Please
verify that you have specified
[ 352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or inst.repo.
[ 352.173918] dracut-initqueue[1065]: Warning: Please also note that
the 'inst.' prefix is now mandatory.
[ 352.174156] dracut-initqueue[1065]: Warning: #
#
[ 352.174354] dracut-initqueue[1065]: Warning: #### Installer
errors encountered during boot: ####
[ 352.174543] dracut-initqueue[1065]: Warning: #
#
[ 352.174775] dracut-initqueue[1065]: Warning: Reason unknown
[ 352.174970] dracut-initqueue[1065]: Warning: #
#
Full log file: see rock.txt
Has anybody more succcess ?
Greetings
Andreas
3 weeks, 5 days
U-Boot testing request - 2023.10 series
by Peter Robinson
Hi Folks,
The 2023.10 RC series are now landing in F-39 and rawhide. There's
been the beginnings of a few enhancements.
The first one that is noticeable is a bootmenu during the firmware
init process where it will allow you to select the device/partition
you wish to boot from, with the default selected and the usual time
out. It should make things a little easier for things like
reinstalling off a USB stick for devices that support that sort of
install.
I've done some testing across a bunch of devices, various RPi, the
Pinebook pro and numerous SBCs so I think it should work just fine, at
least be no different than the usual process but I'd like to hear any
feedback.
Regards,
Peter
1 month, 3 weeks
Re: wireless-tools
by Peter Robinson
Adding back arm list:
> It took a bit of fiddling to get the RPI 4 wireless up,
> so here are the requisite commands for use by anyone else who is doing a
> headless, wireless pi with Fedora 38 aarch64:
>
> # iw dev wlan0 info
>
> # nmcli device wifi list # Get SSID
> # nmcli device wifi connect "SSID" password "whatever"
Yes, these two commands are really all you need:
nmcli device wifi list
nmcli device wifi connect SSID --ask
> # nmcli -p -f general,wifi-properties device show wlan0
>
> # find /etc -name SSID.nmconnection -print # to locate config file automatically created by nmcli commands.
>
2 months, 2 weeks
wireless-tools
by David Legg
Just installed Fedora 38 (minimal) on an RPI 4 and found that the
wireless-tools package is not available. Anybody know where to get
iwconfig etc from, please?
:D
2 months, 2 weeks
PCIe slot on Raspberry Pi CM4
by James Clark
I am trying to connect an i210-T1 to the PCIe slot on a Raspberry Pi CM4
with the official IO board. The problem is it won't boot. I tried this in
Fedora 38 initially. Now I've installed a recent nightly
(Fedora-Server-39-20230828.n.0.aarch64.raw.xz) and I've connected a USB TTL
adapter. It appears to be a U-Boot problem. I get the following over and
over again
U-Boot 2023.10-rc3 (Aug 21 2023 - 00:00:00 +0000)
DRAM: 992 MiB (effective 7.9 GiB)
RPI Compute Module 4 (0xd03141)
Core: 212 devices, 16 uclasses, devicetree: board
MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In: serial,usbkbd
Out: serial,vidconsole
Err: serial,vidconsole
Net: eth0: ethernet@7d580000
PCIe BRCM: link up, 2.5 Gbps x1 (SSC)
"Error" handler, esr 0xbf000002
elr: 00000000000b52b0 lr : 00000000000b526c (reloc)
elr: 000000003df812b0 lr : 000000003df8126c
x0 : 000000000000dead x1 : 0000000000100000
x2 : 0000000000008000 x3 : 00000000fd508000
x4 : 000000003db399f0 x5 : 0000000000000001
x6 : 000000003df82bb8 x7 : 000000003db39fc0
x8 : 000000003df82c90 x9 : 000000003db3992c
x10: 0000000000000002 x11: 0000000000000140
x12: 000000003db39918 x13: 000000003db39fc0
x14: 00000000ffffffff x15: 000000003db39b78
x16: 000000003df82c90 x17: 0000000000c0c0c0
x18: 000000003db47d60 x19: 000000003db399f0
x20: 0000000000000001 x21: 000000003db53f00
x22: 0000000000000000 x23: 0000000000010000
x24: 000000003dfc58fc x25: 000000000001ff00
x26: 000000000000ffff x27: 0000000000000000
x28: 000000003db53b10 x29: 000000003db39950
Code: 350001f4 f94017e0 39400000 92401c00 (d5033fbf)
Resetting CPU ...
resetting ...
James
3 months, 1 week