-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does u-boot version v12.0.2 support boooting (loading the kernel) directly from NVME? #18
Comments
Hi Artem. Yes booting directly to NVMe became possible in 12.0.1. There was a report of |
Oh, cool! Thank you for your work! I am not using your Debian image, though, but I bootstrapped NixOS and use the bootloader to boot it. Does this build support booting in UEFI mode, too (just like 12.0 did)? Haven't there been any device preference/boot method changes made to the bootloader of which I am better to be aware? |
The build was updated to use u-boot 2023.07.02 and changed to use extlinux boot rather than boot scripts. I am interested in your feedback on this topic. While u-boot will prefer |
@inindev How about UEFI support? Is it still supported? |
@inindev It seems that with the latest bootloader LEDs associated with network interfaces (the ones on the front panel) do not work anymore on my R5S. |
@inindev I have moved /boot to NVME and the device still boots! Great! But I am wondering why the front LEDs do not work anymore (apart from the STAT one, which blinks as it should). Kind of bearable, but annoying. |
@inindev On your image the LEDs do work. Hm... I have something missing in my kernel configuration, it seems. |
@inindev Haven't there been any changes related to LED? |
The The leds are defined here:
|
Contents of Also, they seem to be properly defined in the DTB as well:
Out of a sudden, the LEDs stopped working. |
@inindev Don't you know, by any chance, what module is responsible for triggering the LEDs? I suspect that I might be missing something, though. I haven't updated the kernel - that is, I am running exactly the same kernel I was running before and the LEDs worked fine. Strange, but your images work fine, so, I suppose, that is related to my configuration. |
check the trigger values:
|
@inindev Thanks for your help! On my machine I have only this one:
The rest is not available. BTW, the power indicator (aka Regarding the contents of
Again, only the power led is configured. I am running Linux kernel 6.4.10 with the corresponding DTB downloaded from the release section. The system is booted in UEFI mode. I will be appreciated if you can tell me in which direction to dig. |
@inindev Are there any differences (which might cause that) in the DTB available from the download section compared to the one included into the mainline kernel version 6.4.10? |
They are not being set for some reason which leads me to believe a device tree without these entries is being loaded. I assume manually setting these causes them to function as expected? as root:
|
@inindev Yes, that helped! After re-plugging the cable LAN1 led indicates the link status. That is strange, what could have caused that? I am using the latest DTB that you provided. |
@inindev I have tried to boot the device using the device tree from the mainline kernel - the result is the same. I have switched back to the one you provided for now. |
@inindev I have dumped the loaded blob (the device was set to boot with yours DTB).
|
@inindev Aha, it turns out that eMMC is not writeable. |
I did not think about that. With the latest version using extlinux, the filesystem is initially mounded read-only (notice /boot/extlinux/extlinux.conf
Then when the filesystems are mounted by /etc/fstab
You can edit this out at the top of
Then run |
no no, I am not using your Debian images - they work fine. It seems that, indeed, the DTB file is not loaded from |
Yeah, confirmed. The latest release of u-boot does not try to load device tree from /dtb directory on the boot partition. |
Thanks for testing. The paths to the three files needed for booting are hard-coded in
|
@inindev I know what is going on. So, the newer versions of u-boot (newer than 12.0.0 release) do not look for DTB files within As I boot in UEFI mode, I fixed by adding the following kernel option: So, it works fine again. @inindev I kind of liked the old way better (as it allowed me to have a dedicated partition on eMMC containing only the directory with the DTB file), but oh well. Everything is back to normal again. Thank you for your hard work and help with troubleshooting this and for making it possible to boot directly from NVME. |
I am not booting with uefi. How should the boot dtb be repaired? |
I have noticed that you have released updates to the bootloader for r5s/r5c. Does this update make it is possible to have
/boot
on the NVME device? Provided that the u-boot itself is on the eMMC or SD, of course.The text was updated successfully, but these errors were encountered: