{"id":2768,"date":"2020-07-18T02:00:07","date_gmt":"2020-07-18T09:00:07","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=2768"},"modified":"2020-07-18T02:00:07","modified_gmt":"2020-07-18T09:00:07","slug":"arm64-8gb-pi4-fun-with-fedora","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=2768","title":{"rendered":"ARM64 – 8GB Pi4 – Fun with Fedora.."},"content":{"rendered":"

\"\"<\/a>My 8GB Raspbery Pi 4 finally arrived, and I was looking forward to trying Fedora 32 and KDE\/Plasma on it, and comparing it to the Odroid N2 from a few months back.. ( https:\/\/rglinuxtech.com\/?p=2689<\/a> )<\/p>\n

The Fedora 32 aarch64 install is supposed<\/span> to support the Pi 4 now, but the resulting sdcard image failed to boot, with many errors:<\/p>\n

……………
\n[ 6.961831] raspberrypi-firmware soc:firmware: Request 0x00000001 returned status 0x00000000<\/span><\/strong>
\n[ 6.974935] raspberrypi-firmware soc:firmware: Request 0x00030046 returned status 0x00000000<\/span><\/strong>
\n[ 6.988289] raspberrypi-firmware soc:firmware: Request 0x00030007 returned status 0x00000000<\/span><\/strong>
\n[ 7.001270] raspberrypi-clk raspberrypi-clk: Failed to get pllb min freq: -22<\/span><\/strong>
\n[ 7.012942] raspberrypi-clk raspberrypi-clk: Failed to initialize pllb, -22<\/span><\/strong>
\n[ 7.024387] raspberrypi-clk: probe of raspberrypi-clk failed with error -22<\/span><\/strong>
\n[ 7.037101] raspberrypi-firmware soc:firmware: Request 0x00030030 returned status 0x00000000<\/span><\/strong>
\n[ 7.053282] hctosys: unable to open rtc device (rtc0)<\/span><\/strong>
\n…………….
\n[ 16.052538] bcmgenet fd580000.ethernet: failed to get enet clock<\/span><\/strong>
\n[ 16.052894] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0x0000000000<\/span><\/strong>
\n[ 16.066097] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000<\/span><\/strong>
\n[ 16.120634] bcmgenet fd580000.ethernet: failed to get enet-wol clock<\/span><\/strong>
\n[ 16.152111] bcmgenet fd580000.ethernet: failed to get enet-eee clock<\/span><\/strong>
\n[ 16.239025] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000<\/span><\/strong>
\n[ 16.317157] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.318008] brcm-pcie fd500000.pcie: link up, 5 GT\/s x1 (SSC)<\/span><\/strong>
\n[ 16.332575] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 0 config (-22 80)<\/span><\/strong>
\n[ 16.389116] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00<\/span><\/strong>
\n[ 16.400193] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.417597] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)<\/span><\/strong>
\n[ 16.420234] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.440231] pci_bus 0000:00: root bus resource [bus 00-ff]<\/span><\/strong>
\n[ 16.447849] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 2 config (-22 82)<\/span><\/strong>
\n[ 16.497462] libphy: bcmgenet MII bus: probed<\/span><\/strong>
\n[ 16.519288] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])<\/span><\/strong>
\n[ 16.532956] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.552149] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 3 config (-22 83)<\/span><\/strong>
\n[ 16.568566] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400<\/span><\/strong>
\n[ 16.580239] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.597120] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)<\/span><\/strong>
\n[ 16.600228] pci 0000:00:00.0: PME# supported from D0 D3hot<\/span><\/strong>
\n[ 16.632585] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.648016] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 5 config (-22 85)<\/span><\/strong>
\n[ 16.654810] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring<\/span><\/strong>
\n[ 16.680377] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus<\/span><\/strong>
\n[ 16.693372] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.694400] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.708823] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)<\/span><\/strong>
\n[ 16.712831] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330<\/span><\/strong>
\n[ 16.712876] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]<\/span><\/strong>
\n[ 16.712988] pci 0000:01:00.0: PME# supported from D0 D3hot<\/span><\/strong>
\n[ 16.724176] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)<\/span><\/strong>
\n[ 16.742183] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01<\/span><\/strong>
\n[ 16.770228] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.778198] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.793342] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 1 config (-22 81)<\/span><\/strong>
\n[ 16.806981] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 7 config (-22 87)<\/span><\/strong>
\n[ 16.852871] pci 0000:00:00.0: BAR 14: assigned [mem 0x600000000-0x6000fffff]<\/span><\/strong>
\n[ 16.890220] pwrseq_simple: probe of wifi-pwrseq failed with error -22<\/span><\/strong>
\n[ 16.903405] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.918159] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)<\/span><\/strong>
\n[ 16.920206] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]<\/span><\/strong>
\n[ 16.940204] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 16.945691] pci 0000:00:00.0: PCI bridge to [bus 01]<\/span><\/strong>
\n[ 16.959801] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 6 config (-22 86)<\/span><\/strong>
\n[ 16.970188] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]<\/span><\/strong>
\n[ 16.990196] reg-fixed-voltage: probe of sd_vcc_reg failed with error -22<\/span><\/strong>
\n[ 17.000442] pcieport 0000:00:00.0: enabling device (0000 -> 0002)<\/span><\/strong>
\n[ 17.009258] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 17.030438] pcieport 0000:00:00.0: PME: Signaling with IRQ 41<\/span><\/strong>
\n[ 17.034646] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)<\/span><\/strong>
\n[ 17.050324] pcieport 0000:00:00.0: AER: enabled with IRQ 41<\/span><\/strong>
\n[ 17.080208] raspberrypi-firmware soc:firmware: Request 0x00030043 returned status 0x00000000<\/span><\/strong>
\n[ 17.094564] raspberrypi-firmware soc:firmware: Request 0x00030058 returned status 0x00000000<\/span><\/strong>
\n[ 17.094570] raspberrypi-exp-gpio soc:firmware:gpio: Failed to get GPIO 4 config (-22 84)<\/span><\/strong>
\n[ 17.094599] gpio-regulator: probe of sd_io_1v8_reg failed with error -22<\/span><\/strong>
\n[ 17.108820] pci 0000:01:00.0: Failed to load VL805’s firmware: -22. Will continue to attempt to work, but bad things might happen. You should fix this…<\/span><\/strong>
\n[ 17.108835] pci 0000:01:00.0: enabling device (0000 -> 0002)<\/span><\/strong>
\n[ 17.130226] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000<\/span><\/strong>
\n[ 20.544613] random: crng init done<\/span><\/strong>
\n[ 20.553873] random: 7 urandom warning(s) missed due to ratelimiting<\/span><\/strong>
\n[ 22.607938] pci 0000:01:00.0: xHCI HW not ready after 5 sec (HC bug?) status = 0x801<\/span><\/strong>
\n[ 22.621726] pci 0000:01:00.0: quirk_usb_early_handoff+0x0\/0x160 took 5411379 usecs<\/span><\/strong>
\n[ 22.635594] xhci_hcd 0000:01:00.0: xHCI Host Controller<\/span><\/strong>
\n[ 22.650515] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1<\/span><\/strong>
\n[ 32.670236] xhci_hcd 0000:01:00.0: can’t setup: -110<\/span><\/strong>
\n[ 32.681196] xhci_hcd 0000:01:00.0: USB bus 1 deregistered<\/span><\/strong>
\n[ 32.700993] xhci_hcd 0000:01:00.0: init 0000:01:00.0 fail, -110<\/span><\/strong>
\n[ 32.712832] xhci_hcd: probe of 0000:01:00.0 failed with error -110<\/span><\/strong>
\n[ 32.726793] raspberrypi-firmware soc:firmware: Request 0x00028001 returned status 0x00000000<\/span><\/strong><\/p>\n

After that the system failed back to the Dracut console..<\/p>\n

I could see that the u-boot version from the Fedora 32 install was quite old, so tried the Rawhide image, but got similar failures..<\/p>\n

I actually had more success with an _older_ version of Fedora aarch64, but there was no USB device shown, and the memory only showed as 4GB..<\/p>\n

I had had more success – years ago – with the OpenSuse<\/em> versions of aarch64, and so tried this for the Pi4, and it booted OK, but there was no USB device shown, although it did show the 8GB memory correctly. I did notice that the GRUB boot menu displayed correctly, and did recognise the USB-attached keyboard, so I compiled\/installed the latest (5.8-rc5) kernel, and all the USB devices were now detected..<\/p>\n

I then tried the OpenSuse version of u-boot on the Fedora sdcard, and u-boot failed.., and a new\/compiled version of u-boot also failed..<\/p>\n

I had noticed that the OpenSuse boot process used the two-stage GRUB process, similar to the one I had to use for the Odroid C2 and N2, and so I decided to ‘port’ this to the Fedora sdcard, and replaced the contents of the Fedora EFI partition with the contents of the OpenSuse partition, keeping the EFI\/fedora directory and contents (including the ‘real’ Fedora 32 grub.cfg)<\/p>\n

The 2-stage grub configuration is documented in my article for the Odroid C2 at https:\/\/rglinuxtech.com\/?p=2595<\/a><\/p>\n

With the two-stage grub\/EFI boot in place, I was able to successfully update u-boot.bin to the latest (compiled) version, and everything worked OK..<\/p>\n

[root@rgpi4 ~]# uname -a<\/span><\/strong>
\nLinux rgpi4 5.8.0-rc5 #1 SMP PREEMPT Thu Jul 16 00:58:39 PDT 2020 aarch64 aarch64 aarch64 GNU\/Linux<\/span><\/strong><\/p>\n

From first impressions, the system is very CPU-bound<\/em>, and the 8GB memory would seem to be largely redundant.. The KDE\/Plasma desktop runs, but is too sluggish..
\nThe Pi4 runs quite ‘hot’, and definitely needs cooling, and I have had bad experiences with tiny-fan coolers in the past, so opted for an all-metal case\/heatsink, which seems to work fine, even with kernel compiles running..
\nThere is a project to get a Pi Vulkan driver for proper 3D video support, but this is rather Debian-centric, and is only 32-bit at present..\u00a0\u00a0\u00a0 More to come, if\/when things improve..<\/p>\n

Robert Gadsdon.\u00a0\u00a0 July 18th 2020.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

My 8GB Raspbery Pi 4 finally arrived, and I was looking forward to trying Fedora 32 and KDE\/Plasma on it, and comparing it to the Odroid N2 from a few months back.. ( https:\/\/rglinuxtech.com\/?p=2689 ) The Fedora 32 aarch64 install is supposed to support the Pi 4 now, but the resulting sdcard image failed to boot, with …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1132,5,6,10,11,13,14,16,2022,2254],"tags":[2256,1135,2176,2257,2260,2261,2258,2259,2255,1175],"class_list":["post-2768","post","type-post","status-publish","format-standard","hentry","category-aarch64","category-compilation","category-crash-and-burn","category-fedora","category-hacks","category-kde-2","category-kernel","category-linux-arm","category-new-install","category-raspberry-pi-4","tag-8gb","tag-aarch64","tag-fedora-32","tag-fedora-install","tag-hybrid","tag-kde-plasma-too-slow","tag-opensuse-efi-substitute","tag-opensuse-u-boot","tag-raspberry-pi-4","tag-success"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2768","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2768"}],"version-history":[{"count":3,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2768\/revisions"}],"predecessor-version":[{"id":2772,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2768\/revisions\/2772"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2768"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2768"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2768"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}