08-02-2020, 09:00 PM
(07-26-2020, 05:20 PM)belfastraven Wrote:Opposite experience for me here. I did a fresh install of manjaro on a USB flash drive, ran all the updates and then installed from the link above. Sata boot still works, but this breaks USB boot. Not even USB2 boots properly now. Both stick at "Booting using fdtblob at 0x1f0000000"(07-26-2020, 05:33 AM)sigmaris Wrote: I've made another build based on 2020.07 using this branch, with a couple of additional patches:This works fine for me with USB3-- I have attached the u-boot logs from booting a SANDISK extreme stick and then a Samsung portable ssd T150. I was booting from SPI . I also booted my NVME, which I removed in order to boot the other devices, since that is first in the boot order. When not booting from the USB3, the kernel recognizes the USB3 devices, just FYI. Is there anything in particular I could do to help you debug your issue?
Patch from Tian Yuanhao which allows compressed (gzip, etc) kernels to be loaded. No need to gunzip the default arm64 kernels to load them with u-boot anymore.
Patch from Jagan Teki which is supposed to enable USB-3 support on the USB-3.0 type A port. When testing this with the one USB-3 disk drive I have, it didn't seem to work, the disk drive wasn't detected in the USB-3.0 port. I'd be interested to hear if anyone else has success in using USB-3.0 devices in USB-3.0 mode with this. Note the USB Type C port is configured as OTG mode by default in the DTS, and so won't be used as a host port, so only the Type A port should be used for USB-3.0.
Build artifacts for MMC and SPI installation from this branch can be found here.
Was seeing this on the screen something we could have turned on before? I prefer it to the blindly waiting for the OS to load.