Keyboard position on Boot
3 posts, 3 voices
Keith Dunlop (214)
162 posts
|
If my keyboard is plugged in to the USB hub in my monitor boot hangs with “searching for boot device”. This is because there is a card reader also built into the monitor. This wasn’t a problem at all until the new RISC OS 5.19 builds just after the RISC OS SW show. I have just loaded the current 5.19 ROM (06/03/12) to see if this has been spotted / made a difference. Looking through CVS there seems to have been some changes regarding keyboard detection at boot. Quick diagram to explain the situation: BB – Keyboard All OK BB – Monitor – Keyboard (with hub and card reader) Waiting for Boot device. BB = BeagleBoard mounted USB ports. My machine is an ARMini. Has a little bug crept in here? From my testing it looks like that wherever RISC OS detects the keyboard during boot, in terms of where it is USBwise, if it then sees a USB storage device off the same hub it expects it to be the boot device. Of course this isn’t a showstopper but I would like to move the keyboard USB port if I can! The mouse is not affected. |
Jeffrey Lee (213)
6048 posts
|
The only keyboard scanning/detection changes I can remember making were to the IOMD HAL, so it should be possible for those to affect the OMAP ROM. Does 5.18 work OK? It shouldn’t be too hard to narrow down what’s causing the problem. |
Andrew Rawnsley (492)
1445 posts
|
It is worth remembering that we had a hold-up for a long time on 5.18 release because the devices were being enumerated in a different order. This ended up being due to the devices being enumerated on callbacks, which were occuring when debug info was printed out from 5.17/5.19, but since 5.18 wasn’t showing debug, the callbacks weren’t getting to the Kernel/HAL in the right order, so device enumeration ended up happening later and resulting in different device order. In the end, Sprow added some callback checking stuff into the kernel/hal in 5.18 to allow things to happen as before. I have no clue if this is relevant here, but I mention it so that everyone is up to speed with stuff that went on internally during 5.18 testing. |
