No devices with F39 on Raspberry Pi

[Peter Boy]

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

[Peter Robinson]

On Sun, Oct 29, 2023 at 4:24 PM Peter Boy <pboy(a)uni-bremen.de&gt; wrote:
>  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. 
Can you update the RHBZ and add karma so that can go stable.

>  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) ? 
Did you file a bug so it can be tracked and discussed in a central
location? Please reference it here too.

[Peter Robinson]

On Sun, Oct 29, 2023 at 6:22 PM Peter Robinson <pbrobinson(a)gmail.com&gt; wrote:
>  On Sun, Oct 29, 2023 at 4:24 PM Peter Boy <pboy(a)uni-bremen.de&gt; wrote:
>  >
>  > 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.
>
>  Can you update the RHBZ and add karma so that can go stable.
>
>  > 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) ?
>
>  Did you file a bug so it can be tracked and discussed in a central
>  location? Please reference it here too. 
BTW have you tested with the new arm-image-installer
(arm-image-installer-3.9-2.fc39) ? I've just added that to the update,
it fixes some bits with LVM.

Peter

[Peter Boy]

>  Am 29.10.2023 um 19:39 schrieb Peter Robinson
> <pbrobinson(a)gmail.com&gt;:
>  
> >> 
> >> 
> >> 
> >> 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) ?
> > 
> > Did you file a bug so it can be tracked and discussed in a central
> > location? Please reference it here too. 
I’m about to do, but I’m unsure which component to select. U-boot seems wrong, because it
is most likely the image generation, I guess.

Do you know which component I should select? 



>  
>  BTW have you tested with the new arm-image-installer
>  (arm-image-installer-3.9-2.fc39) ? I've just added that to the update,
>  it fixes some bits with LVM. 

I used version 3.8 which is part of the rc 1.2. How do I get version 3.9-2? I simple def
update does not do it.





--
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

[Peter Robinson]

On Sun, Oct 29, 2023 at 7:26 PM Peter Boy <pboy(a)uni-bremen.de&gt; wrote:
>  > Am 29.10.2023 um 19:39 schrieb Peter Robinson <pbrobinson(a)gmail.com&gt;:
>  >
>  >>>
>  >>>
>  >>>
>  >>> 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) ?
>  >>
>  >> Did you file a bug so it can be tracked and discussed in a central
>  >> location? Please reference it here too.
>
>  I’m about to do, but I’m unsure which component to select. U-boot seems wrong, because it
> is most likely the image generation, I guess.
>
>  Do you know which component I should select?
>
>
>
>  >
>  > BTW have you tested with the new arm-image-installer
>  > (arm-image-installer-3.9-2.fc39) ? I've just added that to the update,
>  > it fixes some bits with LVM.
>
>
>  I used version 3.8 which is part of the rc 1.2. How do I get version 3.9-2? I simple def
> update does not do it. 
Grab the rpm from koji?

[Sally A.haj]

As Peter Robinson, you can install the rpm package directly:
https://kojipkgs.fedoraproject.org//packages/arm-image-installer/3.9/2.fc...

Otherwise, you can use the original
file https://pagure.io/arm-image-installer/releases , just unzip then
use the 'arm-image-installer' file. I use it sometimes if I am not in
Fedora.
 

On Sun, 2023-10-29 at 19:28 +0000, Peter Robinson wrote:
>  On Sun, Oct 29, 2023 at 7:26 PM Peter Boy <pboy(a)uni-bremen.de&gt;
> wrote:
>  > 
>  > 
>  > 
>  > > Am 29.10.2023 um 19:39 schrieb Peter Robinson
>  > > <pbrobinson(a)gmail.com&gt;:
>  > > 
>  > > > > 
>  > > > > 
>  > > > > 
>  > > > > 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) ?
>  > > > 
>  > > > Did you file a bug so it can be tracked and discussed in a
>  > > > central
>  > > > location? Please reference it here too.
>  > 
>  > I’m about to do, but I’m unsure which component to select. U-boot
>  > seems wrong, because it is most likely the image generation, I
>  > guess.
>  > 
>  > Do you know which component I should select?
>  > 
>  > 
>  > 
>  > > 
>  > > BTW have you tested with the new arm-image-installer
>  > > (arm-image-installer-3.9-2.fc39) ? I've just added that to the
>  > > update,
>  > > it fixes some bits with LVM.
>  > 
>  > 
>  > I used version 3.8 which is part of the rc 1.2. How do I get
>  > version 3.9-2? I simple def update does not do it.
>  
>  Grab the rpm from koji?
>  _______________________________________________
>  arm mailing list -- arm(a)lists.fedoraproject.org
>  To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines:
>  https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam, report it:
>  https://pagure.io/fedora-infrastructure/new_issue