[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wireless keyboard not detected if not usb-hub connected



On Thu, Sep 23, 2010 at 07:03:11PM +0200, Raphaël Droz wrote:
> Hi,
> I recently bought a (used) keyboard
> (http://www.microsoft.com/hardware/systembuilders/ProductDetails.aspx?pid=036)
> to connect it to my old eeepc 701
> I also have a USB hub
> (http://www.topproduct.nl/hardware/hubs/12935-typhoon/97140-typhoon-usb-hub-2.0/302335-typhoon-usb-hub-2.0-83045.html)
> 
> In Grub:
> - keyboard connected to the eeepc: working smoothly
> - keyboard connected to the hub: working, with some latency
> 
> After init/udev:
> - keyboard connected to the eeepc: not working
> - keyboard connected to the hub: working smoothly
> 
> At the beginning I believed I had some problem with the eeepc usb
> voltage, but ... _in_grub_it_works_
> I used udevd --debug, but it shows absolutely nothing when the keyboard
> is directly plugged.
> [ I attached a trace of the keyboard being hub-plugged and detected by
> udev; the modalias and its quirks *may* be the thing to look at ]
> 
> So, I guess, it has nothing to do with the bios, nor X/evdev/xinput, nor the
> hardware.
> 
> I wanted to trace kernel device events but I don't really know which of
> $(grep TRACE /boot/config-2.6.32-trunk-686)
> should be used (and activated in the stock Sid kernel as I wish to avoid
> a recompilation if possible as my HD space is dramatically low)
> 
> Finally I tried usbmon and, hope and surprise, I found something being
> logged while the keyboard is directly plugged.
> I used http://ns.spinics.net/lists/linux-usb/msg23537.html
> (parse_usbmon.sh) [no wireshark, HD space ...]
> but no much luck with it. When a direct connection happens usbmon just
> say "usb port is alive", and nothing happens on successive keypresses.
> 
> I also made some attempts of module manual loadings like I saw in udev log
> (like modprobe -b input:xxx...) but no success so far.
> 
> Attached are the usbmon sessions (raw and parsed) for {direct,hub}
> connections.
> A udevd --debug log of a hub connection + lspci and lsusb.
> 
> Any advice warmly welcomed
> 
> (sorry for the noise of the previous 'Unidentified subject!' message:
> attachment + email was a bit over 100k, thus the gzipped udevd.log here)
> 
> Raphaël


I still can not understand that a keyboard can work like a charm in the
bios/grub (the receiver flickers as I type) but not after init (the
receiver led stays desesperately off whatever module I load).

so just ping'ing as I'm still out of ideas and I would really like to
solve this problem but I do not want to disturb kernel-related
mailing-lists.
any hint ?

Raph


Reply to: