On Mon, 1 Jun 2009, Andrew Morton wrote: > > My K__nig CMP-BARSCAN 10 (being reported as ID 1130:0001 Tenx Technology, Inc.) > > stopped working in kernels upwards from 2.6.28. I'm running a Gentoo 64-bits > > system. > > > > The device is still being detected, however, no input-node is being created. > > Dmesg reports (under a 2.6.28 kernel): > > > > usb 6-2: new low speed USB device using uhci_hcd and address 2 > > usb 6-2: configuration #1 chosen from 1 choice > > usb 6-2: New USB device found, idVendor=1130, idProduct=0001 > > usb 6-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 > > usb 62: Product: USB-TMU > > > > > > Under 2.6.27.24 it does work as expected. Dmesg reports: > > > > usb 6-2: new low speed USB device using uhci_hcd and address 2 > > usb 6-2: configuration #1 chosen from 1 choice > > input: USB-TMU as /class/input/input6 > > input: USB HID v1.10 Keyboard [USB-TMU] on usb-0000:00:1d.0-2 > > usb 6-2: New USB device found, idVendor=1130, idProduct=0001 > > usb 6-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 > > usb 6-2: Product: USB-TMU This is almost certainly because of this commit: commit d1d3a5f6eaee337d793ab9ac28e696f0262c3c8a Author: Remi Cattiau <remi@xxxxxxxxxxx> Date: Tue Sep 9 01:39:33 2008 +0200 HID: ignore iBuddy devices iBuddy devices claim to be HID devices, but they are not. Add them to the blacklist. Signed-off-by: Remi Cattiau <remi@xxxxxxxxxxx> Signed-off-by: Jiri Kosina <jkosina@xxxxxxx> The problem apparently [1] is, that the vendor has been super-creative and assigned the same combination of idVendor/idProduct to completely different devices. Oh well. Remi, could you please check your device against the lsusb data provided in bugzilla to check whether there is any possibility to distinguish these devices, so that we could put some ugly check in place probably? Thanks. [1] http://lkml.org/lkml/2009/2/10/434 -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
