(12-03-2022, 03:25 PM)bosi564 Wrote: Sorry to disappoint you, but both ubuntu images:
1. Armbian_22.11.0-trunk_Quartz64a_jammy_edge_6.1.0.img (md5 sum 030c1f596402809f01b674cb3afa6eeb)
2. Armbian_22.11.0-trunk_Quartz64a_jammy_edge_6.1.0_xfce_desktop.img (md5 sum 5a589965573896585e41ab4c4d0244d0)
Do not work. They too print the three lines with "EFI stub", then the monitor enters into sleep and the keyboard loses power. For example Num Lock stops toggling the led, which it did during booting up and while being in the menu of GRUB.
The first time after flashing the usb stick the wait time for default choice in GRUB is 5 seconds and later after just a reboot it's 30 seconds, but I do not know if this is significant.
Well, I'll also add the md5 sum of QUARTZ64_EFI.img - eb4c625a3ab63c7c2cf61b41ac6c3cf6, just to have something to compare. I didn't overwrite the microSD between changing OSes on the usb stick.
My usb stick is 128 gigabytes for at least USB 3.0. My microSD is 64 gigabytes for UHD video. I probably won't find anything smaller to test with.
I've tried both USB 2.0 ports on my model A and the result is the same. I've attached only a usb keyboard on one of the faster USB ports (which works in the menu of GRUB and the Tianocore EDK II menu), an HDMI cable and the power cable from the official power brick (5 amperes for NAS variant). No disks and no eMMC are attached at the moment, although I do have them available.
Previously I had a mini PCI express card plugged, but after removing it the results were the same.
Still, I feel we're really close to have it all work.If there's a need to test anything, I'll check every few days.
Changing the time in the menu from 5 to 30 seconds is important. This means that the system started to start and it was "incorrectly" turned off (the correct shutdown of the system was not performed). If you use 128 GB of USB, the first startup time will be very long (the partition is automatically expanded to the entire media). It is likely that with such a large delay, the monitor turns off.
It is also possible that it is "not compatible" with your USB media. I observed how some USB 3.0 devices could not work correctly due to the design (inside, a "tricky option" of connecting chips is used, through an additional controller, which is not always correctly detected immediately at the kernel startup stage).
Try disabling the primary setup wizard (immediately after writing the image to USB, delete the /usr/lib/armbian/armbian-firstlogin file from USB) and try running without it. Now I am testing a new version that will work immediately from the SD card.
By the way, have other images been recorded on your SD card before? Perhaps the reason is the "remnants" of old systems that leave a backup copy of GPT or other data. Try to completely clean the SD card (using the DD utility) before writing the EDK2 image.