Thanks for your efforts. If you look in my original post you'll see that i am already on the latest eeprom:
Code:
:~# rpi-eeprom-updateBOOTLOADER: up to date CURRENT: Wed Jan 24 12:16:01 UTC 2024 (1706098561) LATEST: Wed Jan 24 12:16:01 UTC 2024 (1706098561) RELEASE: default (/lib/firmware/raspberrypi/bootloader-2712/default) Use raspi-config to change the release.Several change added to the eeprom, so an update may help fixing your issue. the detection line are even added automatically on the last release notes https://github.com/raspberrypi/rpi-eepr ... e-notes.mdthanks for that insight. It isn't relevant to my issue [yet]. I can't even start worrying about asking the pi to boot off of the X1003 if the pi isn't even seeing it yet. I don't want to enable boot yet, because i don't want the pi hanging while it waits for a device that isn't available. Especially since it's in the eeprom , and nut just the /boot/firmware/config.txtIf it matters:
I see your screenshot --> BOOT_ORDER=0xf41
Mine : BOOT_ORDER=0xf416
I need to know why the UBUNTU 23 image that the Raspberry Pi Imager creates cannot see this hardware, and or why it would matter whether it was PI OS, or UBUNTU 23...
I wonder if this can be fixed with an apt install of some driver or package
Statistics: Posted by etyrnal — Thu Feb 01, 2024 10:17 pm