We've added some new devices and there's been some general changes and improvements so we should update the documentation for the supported hardware to reflect this.
Metadata Update from @pbrobinson: - Issue tagged with: f32
…Fedora 34 is out and this is still not solved?
There have been a number of updates to the device list for Fedora IoT on F-34. I want to make it look prettier which is why it's still open.
Is there a good place to add hardware-specific details? For instance, the ROCKPro64 can boot from USB, but this requires Fedora's U-Boot on SPI flash... I tried a couple of other U-Boot releases to no avail. Of course, this is probably not specific to Fedora IoT.
Not really, the problem is it takes a LOT of time to keep up to date.
Is there a good place to add hardware-specific details? For instance, the ROCKPro64 can boot from USB, but this requires Fedora's U-Boot on SPI flash... I tried a couple of other U-Boot releases to no avail. Of course, this is probably not specific to Fedora IoT. Not really, the problem is it takes a LOT of time to keep up to date.
That makes sense, I'll see if I can get some info in PINE64's wiki page for the ROCKPro64.
So when you say "tried a couple of other U-Boot releases" what do you mean? We should mostly just boot with any vanilla upstream release but there have been some bug fixes and we actively improve upstream and you'll want a recent release. There's also a patch we pull in that's needed if you have a USB keyboard attached. The fix for that is not yet upstream.
The problem with even documenting something like that upstream is that it will be out of date very quickly. Ultimately that's why we've shipped our own to date.
Closing this bug as the improvements I've now pushed. I'm going to add images of the devices but the list is now up to date.
Metadata Update from @pbrobinson: - Issue status updated to: Closed (was: Open)
Is there a good place to add hardware-specific details? For instance, the ROCKPro64 can boot from USB, but this requires Fedora's U-Boot on SPI flash... I tried a couple of other U-Boot releases to no avail. Of course, this is probably not specific to Fedora IoT. So when you say "tried a couple of other U-Boot releases" what do you mean? We should mostly just boot with any vanilla upstream release but there have been some bug fixes and we actively improve upstream and you'll want a recent release. There's also a patch we pull in that's needed if you have a USB keyboard attached. The fix for that is not yet upstream. The problem with even documenting something like that upstream is that it will be out of date very quickly. Ultimately that's why we've shipped our own to date.
Yeah, I totally understand why updating that kind of information ins't feasible, and I've seen plenty of outdated wiki's where the information is out-of-date and not helpful.
Anyways, about U-Boot, I tried both Armbian's U-Boot and the latest pre-release of Sigmari's U-Boot on SPI flash, but neither could boot Fedora IoT from the USB-3 port on the ROCKPro64. Typically, the system would hang when it started booting the EFI, before the usual boot messages started appearing. I even tried to boot Armbian from the USB using Armbian's own U-Boot on SPI, and that ended up failing in the boot process.
I ended up finding your blog post on manually updating the SPI flash and followed that to put Fedora's U-Boot on SPI. The weird thing is I had to also flash U-Boot to the USB storage when I used the arm-image-installer, otherwise it wouldn't boot. So for some reason I had to use target=rockpro64-rk3399 instead of target=none. With target=none, the bootloader hung at booting from EFI.
target=rockpro64-rk3399
target=none
Once I got that working, I used the installer ISO image on an SD card to boot Anaconda, which allowed me to install to the USB drive on Btrfs. Everything's been working great so far.
Login to comment on this ticket.