Just a data point...one of the boxes I've tried (can't remember which of Foxconn nt535, nt-i1250, nt-i2847) had a similar/same problem. About 30%-50% of the time when I switched to it, no kernel messages on the screen, no keyboard. I found that plugging in a USB flash drive caused both the flash drive and the keyboard to be detected -- so that was my workaround.
I've not seen the problem on other HW using the same cheap KVM. On Sat, Feb 9, 2013 at 11:58 AM, Bastien Durel <[email protected]> wrote: > Quoting Francois Pussault <[email protected]>: >> >> Hi, many hardware cannot manage USB keyboards without it present at boot. >> because bios or equiv doesn't enable the port so the OS (whatever it is) >> cannot use it. >> > [...] > >> a solution could be to have an usb-test device connected to garantee usb >> is enable >> even if kvm is on another device. > > Hello, > > But KVM *is* connected at boot time, as you can see here : > >>> uhidev1 at uhub4 port 1 configuration 1 interface 1 "CHESEN USB Keyboard" >>> rev 1.10/1.10 addr 3 > > It's the diconnection-reconnection which is not managed. > > Regards, > > -- > Bastien > -- > Bastien
