[fedora-arm] No devices with F39 on Raspberry Pi
Just checked the F39 rc1.2 on an raspi4 with Server Edition.
The fix for the display issue (https://bugzilla.redhat.com/show_bug.cgi?id=2241252) does
work for Server, too.
But there is a next issue:
If I try to adjust the LVM volume to the size of the SD card, I can enlarge the partition
mmcblk0p3 using cfdisk as usual without issues. But with pvresize I get
$ sudo pvresize /dev/mmcblk0p3
[sudo] password for pb:
Cannot use /dev/mmcblk0p3: device is not in devices file
0 physical volume(s) resized or updated / 0 physical volume(s) not resized
A lsblk
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 59.5G 0 disk
├─mmcblk0p1 179:1 0 600M 0 part /boot/efi
├─mmcblk0p2 179:2 0 1G 0 part /boot
└─mmcblk0p3 179:3 0 57.9G 0 part
└─fedora-root 253:0 0 5.4G 0 lvm /
zram0 252:0 0 3.7G 0 disk [SWAP]
looks fine and as expected.
And with cockpit -> storage the category „devices“ is empty (instead of listing a LVM
volume fedora as to expect). It seems, there is something badly wrong with the image.
Hence the error message with arm-installer after writing the image onto disk:
= Writing image complete!
mount: /tmp/root: unknown filesystem type 'LVM2_member'.
dmesg(1) may have more information after failed mount system call.
as mentioned in an earlier mail and as discussed at the go/no-go meeting
(https://meetbot.fedoraproject.org/fedora-meeting/2023-10-26/f39-final-go_...
)
The bottom line is that Server Edition is still unusable on Raspi4 and any other SBC,
unfortunately. What to do and how to proceed (the next go/no-go meeting is in 4 days
expecting rc 1.4 tomorrow or shortly after) ?
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast