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.
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.
And rpi4 boots just fine from the created mSD with 39 1.2 .
On Thu, Oct 26, 2023 at 2:51 PM Peter Boy <pboy@xxxxxxxxxxxxx> wrote:
> Am 26.10.2023 um 13:36 schrieb Peter Robinson <pbrobinson@xxxxxxxxx>:
>
> For arm testers too
I just tested RC 1.2 with the server image. It’s rather broken and I don’t think we should release it.
1. (minor)
With arm-installer you get an error message:
To: /dev/mmcblk0 ....
dd: warning: partial read (8192 bytes); suggest iflag=fullblock
If you add this (w and w/o leading —-) it doesn’t start and you get a usage message listing all available parameters and that iflag isn’t among them.
(I didn’t add it to the dd command line, most users wouldn’t do that, I suppose)
2. (major)
At the end of arm-installer you get a message:
= 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
= No U-Boot files found for rock-pi-4-rk3399.
= Installation Complete! Insert into the rock-pi-4-rk3399 and boot.
(a)
You can’t create a usable image without U-Boot files, of course and the final message is badly misleading.
(b)
We had this (or a similar looking) error briefly in F38 as well. The U-Boot files are perfectly where they belong. The reason was that several lines before copying the U-Boot files, the paths were changed specifically for IOT, but these changes were then used for all other editions, too, when copying the U-Boot files, instead of only for IoT.
So, it’s quite easy to fix, I suppose. But we need another RC, I think.
I got that for all of my SBCs besides RPi4:
= 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
= Raspberry Pi 4 Uboot is already in place, no changes needed.
= Installation Complete! Insert into the rpi4 and boot.
But it didn’t boot either.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy@xxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Best regards / S pozdravem,
František Zatloukal
Senior Quality Engineer
Red Hat
_______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
