Brad Hards wrote: >On Wed, 6 Mar 2002 23:42, Geoff C. Ruscoe wrote: > >>Not sure what information I can provide but... >> ><snip> > >>T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 >>D: Ver= 2.00 Cls=02(comm.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 >>P: Vendor=04dd ProdID=8004 Rev= 0.00 >>S: Manufacturer=Sharp >>S: Product=SL Series >>C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr= 0mA >>I: If#= 0 Alt= 0 #EPs= 0 Cls=02(comm.) Sub=06 Prot=00 Driver=usbdnet >>I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=00 Driver=CDCEther >>I: If#= 1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=CDCEther >> >This doesn't look right, and CDCEther is supposed to avoid linking to devices >that have something already bound. Do the kernel logs show "kicking" by the >usbdnet driver? >What is this usbdnet driver anyway? Does it work if you only use one of the >drivers (ie compile just CDCEther, or just usbdnet)? > >If you have problems with the CDCEther driver causing panics, can you try >commenting out the multicast code routine? > >Brad > Currently I am only including the usbdnet modules and not the CDCEther module. I also thought it very odd that I saw them both listed. I think the usbdnet module might have been based on the CDCEther module. It was the first version -- but I have removed it from my kernel.
When you mention commenting out the multicast code, do you mean out of the .c file for the usbdnet module? Or to not include an option when building the kernel or something else entirely? Thanks so much for your help. Geoff _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
