Rahul Bedarkar <rpal143@xxxxxxxxx> writes: > I am using iBall 3.5G usb modem. When I connected it to my laptop > first time, it was detected by kernel but got segfault in > usb_modeswitch. I don't think the segfault is related to the drivers or kernel in any way. It is probably a usb_modeswitch bug. But the device is switched, so it doesn't really matter much. > [ 108.406430] usb 1-1: USB disconnect, device number 4 > [ 108.772070] usb 1-1: new high-speed USB device number 5 using ehci-pci > [ 108.906998] usb 1-1: New USB device found, idVendor=1c9e, idProduct=9605 [..] > Currently, I am using usbserial driver to get it working. I have > noticed in dmesg that it is generic driver and used for testing. > > [ 132.261962] usbcore: registered new interface driver usbserial > [ 132.262367] usbcore: registered new interface driver usbserial_generic > [ 132.262926] usbserial: USB Serial support registered for generic > [ 132.262951] usbserial_generic 1-1:1.0: The "generic" usb-serial > driver is only for testing and one-off prototypes. [..] > Could you tell me in which driver these ids are supposed to add ? The "option" driver is the most likely candidate. It already supports the 1c9e:9603 and 1c9e:9607 devices. You can test it temporarily by dropping the "vendor" and "product" parameters from usbserial and then doing modprobe option echo '1c9e 9605' >/sys/bus/usb-serial/drivers/option1/new_id If this works, then please submit a patch to get proper credit for this. Or let us know so that someone else can submit one in case you don't want to do so yourself. Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
