Can you run fw_printenv | paste-log and send me the output?
Cheers
Here is the output of fw_printenv: https://paste.osmc.tv/zoyusubaji
Here is the output of grab-logs -A: https://paste.osmc.tv/lesebiwide
I booted into the Vero with the ssd plugged into the usb3 port and a keyboard to the usb2 port (so I could dump the logs).
Not forgotten… Thinking.
1 Like
I was thinking about creating a bootable usb pen drive with either a fresh copy of osmc (ensure if that’s easy to do) or another OS, plugging that into the usb2 port, and connecting a keyboard to the usb3 port.
If the keyboard works in that situation, it would at least rule out it could be an hardware issue (since a keyboard plugged in into the usb3 port doesn’t seem to be working in any pre/post boot situation).
Do you think it would be worth the experiment?
Well the smallest bootable OS would be the OSMC installer which reinstalls OSMC.
You get a 60 second warning before the device is formatted, so you could just unplug the device (completely safe) before the timer counts down. If you see that screen, the USB is functioning fine.
Sam
I put the osmc installer in a usb flash drive. When plugged in into the usb2 port it boots into the “formatting in 60s” screen. When plugged in into the usb3 port I don’t get anything. It just keep waiting until it times out waiting for my SSD as configured.
Okay, so you aren’t testing the pen drive in isolation?
It could only take one problematic USB device to cause this issue, if you get my point.
No no, I did test it in isolation. I tested the boot with only the pendrive in usb3. It just hangs in the osmc logo screen because my setup in fstab waits for the ssd to connect before proceeding.
Got it now.