How to boot Fedora 39

Peter Robinson pbrobinson at gmail.com
Tue Dec 19 20:36:20 CET 2023


Hi Simon,

Sorry for the delayed response, I was out with COVID.

> I tried the instructions here with a rpi4:
>
> https://docs.fedoraproject.org/en-US/quick-docs/raspberry-pi/#_installing_fedora_on_a_raspberry_pi_for_linux_users
>
> xzcat Fedora-Workstation-39-1.5.aarch64.raw.xz | sudo dd
> status=progress bs=4M of=/dev/sdb
> 16843096064 bytes (17 GB, 16 GiB) copied, 151 s, 112 MB/s
> 0+2051288 records in
> 0+2051288 records out
> 17179869184 bytes (17 GB, 16 GiB) copied, 152.023 s, 113 MB/s

Hmm, I have not had any reports of Workstation failing to boot. Did
you check the sha256sum against the published ones to make sure it
came down properly?

I generally do all my U-Boot testing with the Minimal spin as it's a
little more straight forward for low level debugging like boots as it
doesn't have fun things like btrfs and graphical stacks. You can get
the F-39 one here:

https://dl.fedoraproject.org/pub/fedora-secondary/releases/39/Spins/aarch64/images/Fedora-Minimal-39-1.5.aarch64.raw.xz

Let me know how you get on.

Peter

>
> Then booted:
>
>
> U-Boot 2023.07 (Oct 25 2023 - 00:00:00 +0000)
>
> DRAM:  992 MiB (effective 3.9 GiB)
> RPI 4 Model B (0xc03111)
> Core:  211 devices, 17 uclasses, devicetree: board
> MMC:   mmcnr at 7e300000: 1, mmc at 7e340000: 0
> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
> In:    serial
> Out:   vidconsole
> Err:   vidconsole
> Net:   eth0: ethernet at 7d580000
> PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
> starting USB...
> Bus usb at 7e980000: USB DWC2
> Bus xhci_pci: Register 5000420 NbrPorts 5
> Starting the controller
> USB XHCI 1.00
> scanning bus usb at 7e980000 for devices... 1 USB Device(s) found
> scanning bus xhci_pci for devices... 3 USB Device(s) found
>        scanning usb for storage devices... 0 Storage Device(s) found
> Hit any key to stop autoboot:  0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> Found EFI removable media binary efi/boot/bootaa64.efi
> 966711 bytes read in 105 ms (8.8 MiB/s)
> Card did not respond to voltage select! : -110
> No EFI system partition
> No EFI system partition
> Failed to persist EFI variables
> Booting /efi\boot\bootaa64.efi
> No EFI system partition
> Failed to persist EFI variables
> No EFI system partition
> Failed to persist EFI variables
> No EFI system partition
> Failed to persist EFI variables
> error: ../../grub-core/commands/search.c:315:no such device:
> 77e306d4-532a-4d8c-b023-5bde5c8689ac.
>
>
>
>                                    GRUB version 2.06
>
>    Minimal BASH-like line editing is supported. For the first word,
> TAB lists
>    possible command completions. Anywhere else TAB lists possible
> device or file
>    completions.
>
>
> grub>
>
>
> I looked at the partition list and don't see that GUID, but perhaps
> U-Boot is missing some config?
>
> U-Boot> part list mmc 0
>
> Partition Map for MMC device 0  --   Partition Type: DOS
>
> Part    Start Sector    Num Sectors     UUID            Type
>   1     2048            1228800         7d51a49c-01     06 Boot
>   2     1230848         2097152         7d51a49c-02     83
>   3     3328000         30226432        7d51a49c-03     83
> U-Boot>
>
> Regards,
> Simon


More information about the U-Boot mailing list