![]() ![]() 3 different HDMI attachments USB-HDMI adapter, Dell U2415, Samsung Odyssey G9.7 different keyboards (toss-away crashcart style, generic USB 104, Costar CST104, GH60, Keychron K8 as control, EVGA Z20 as control).8 different C10U3 SD cards from 4 different vendors (64GB PNY, 64GB SanDisk, 16GB SanDisk, 32GB SanDisk).2 different LePotatos (both v1 one early, one later color-coded header).aml-s905x-cc-2022-07 is the last working one. ![]() Any suggestions? This is very, very OK, at this point, I’ve confirmed that the problem is not me - it is, in fact, the latest u-boot in the CI. I’ve not seen this behavior before, and without the keyboard working, there’s nothing I can do from the prompt. When mmcblk0p1 is /boot/efi then it returns an unknown filesystem error. Some more tweaking has revealed that if mmcblk0p1 is /boot and mmcblk0p2 is / then grub-install works. Failed to get keyboard state from device 05ac:024f (expected - no uboot.env!)Įrror (-2): cannot determine file size (I presume related) Some fail to get state, some just don’t detect, some detect but just don’t work. ![]() The problem now is that it seems to be failing to detect the EFI partition still, and no keyboard is working with my test unit. Ah-ha, it also doesn’t help when your offset is ‘419’ not ‘4196.’ That will definitely wipe out the u-boot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |