> Am 26.10.2023 um 15:30 schrieb Frantisek Zatloukal <fzatlouk@redhat.com>:
>
> With rpi4, I didn't hit any issues:
>
> $ sudo fedora-arm-image-installer --image=Fedora-Workstation-39-1.2.aarch64.raw.xz --norootpass --media=/dev/sda
> Place your finger on the fingerprint reader
> Failed to match fingerprint
> Place your finger on the fingerprint reader
>
> =====================================================
> = Selected Image:
> = Fedora-Workstation-39-1.2.aarch64.raw.xz
> = Selected Media : /dev/sda
> = Root Password will be removed.
> =====================================================
>
> *****************************************************
> *****************************************************
> ******** WARNING! ALL DATA WILL BE DESTROYED ********
> *****************************************************
> *****************************************************
>
> Type 'YES' to proceed, anything else to exit now
>
> = Proceed? yes
> GPT PMBR size mismatch (4156811 != 250085375) will be corrected by write.
> The backup GPT table is corrupt, but the primary appears OK, so that will be used.
> The backup GPT table is not on the end of the device.
> = Writing:
> = Fedora-Workstation-39-1.2.aarch64.raw.xz
> = To: /dev/sda ....
> dd: warning: partial read (65536 bytes); suggest iflag=fullblock
> 17014218752 bytes (17 GB, 16 GiB) copied, 213 s, 79.9 MB/s17179869184 bytes (17 GB, 16 GiB) copied, 213.812 s, 80.4 MB/s
>
> 0+619058 records in
> 0+619058 records out
> 17179869184 bytes (17 GB, 16 GiB) copied, 213.818 s, 80.3 MB/s
> = Writing image complete!
> = No U-boot will be written.
> = Removing the root password.
>
> = Installation Complete! Insert into the board and boot.
>
Well, if you look at the source, you'll see the issue is in line 543:
> = Writing image complete!
> mount: /tmp/root: unknown filesystem type 'LVM2_member'.
> dmesg(1) may have more information after failed mount system call.
> sed: /tmp/fw/EFI/fedora/grubenv kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
> DEBUT info:
> /tmp/root/usr/share/uboot/rock-pi-4-rk3399
> = No U-Boot files found for rock-pi-4-rk3399.
>
> = Installation Complete! Insert into the rock-pi-4-rk3399 and boot.
The PREFIX is "/tmp/root" but should be empty.
It is set in line 531 for IoT device and in line 533 adjusted for BTRFS (=Workstation). And for all others it is set in line with 535 to a value, which is wrong at least for Server and I guess all non-OStree and non-BTRFS editions.
And you didn't set an U-Boot target explicitly, I did. Maybe, there is yet another issue in the code.
I checked again the rpi4. The device does boot and the display works up to the EFI screen and turns black shortly thereafter. But I can log in via SSH.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy@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
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@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/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No comments:
Post a Comment