Re: CNET 611 support

I got a little further thanks to Joerg. I compiled the kernel without 
USBDEVFS support (CONFIG_USB_DEVICEFS). Try again with debug also in
place and I get this:

Jan  8 23:43:59 mc kernel: hub.c: new USB device 00:10.0-1, assigned
address 5
Jan  8 23:43:59 mc kernel: usb.c: USB device 5 (vend/prod 0x1371/0x1) is
not claimed by any active driver.
Jan  8 23:44:04 mc /etc/hotplug/usb.agent: Setup at76c503-rfmd for USB
product 1371/1/100
Jan  8 23:44:05 mc kernel: at76c503.c: Generic Atmel at76c503/at76c505
routines v0.11beta4
Jan  8 23:44:05 mc kernel: usbdfu.c: USB Device Firmware Upgrade (DFU)
handler v0.11beta4
Jan  8 23:44:05 mc kernel: usb.c: registered new driver usbdfu
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe entered
Jan  8 23:44:05 mc kernel: usbdfu.c: searching for driver
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe() exiting
Jan  8 23:44:05 mc kernel: at76c503-rfmd.c: Atmel at76c503 (RFMD)
Wireless LAN Driver v0.11beta4
Jan  8 23:44:05 mc kernel: usbdfu.c: registered new driver at76c503-rfmd
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe entered
Jan  8 23:44:05 mc kernel: usbdfu.c: searching for driver
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe() exiting
Jan  8 23:44:05 mc kernel: usb.c: registered new driver at76c503-rfmd
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe entered
Jan  8 23:44:05 mc kernel: usbdfu.c: searching for driver
Jan  8 23:44:05 mc kernel: usbdfu.c: usbdfu_probe() exiting

It looks like it is finding the driver, then doing a usbdfu_probe then
exiting.. Still no success but maybe these messages give away what Im
not doing right.

Stuart

On Thu, 2004-01-08 at 09:29, Joerg Albert wrote:
> Hi,
> 
> On Wed, 7 Jan 2004, sfg wrote:
> 
> > Hi Jörg
> >
> > Thanks for pointing me at the right module.
> >
> > After re-adding the prodid to at76c503-rfmd I recompiled and
> > reinstalled.
> >
> > Since I dont understand modules.conf, I inserted the module as follows:
> >
> > insmod at76c503-rfmd debug=-1
> 
> No, at76c503-rfmd does not accept a debug parameter, insmod should return
> an error here - I meant at76c503!
> You may consider to read the support part of http://at76c503a.berlios.de/,
> especially the troubleshooting section.
> 
> > For usbdfu, the device/resource was already there and refused to be
> > re-installed:
> >
> > rmmod usbdfu
> > usbdfu: Device or resource busy
> 
> First remove all modules which use usbdfu, then remove it itself.
> 
> > [root@mc at76c503a]# insmod usbdfu debug=-1
> > Using /lib/modules/2.4.22-10mdk/kernel/drivers/usb/usbdfu.o
> > insmod: a module named usbdfu already exists
> 
> I wrote debug=1 for usbdfu, but here it really doesn't matter.
> 
> > If you could explain the parameters to insert the debug parameter in
> > modules.conf I will do that. I have already RTFMed and do not understand
> > the man instructions.
> 
> The insmod way above will work, for modules.conf you need to add the
> lines
> options usbdfu debug=1
> options at76c503 debug=-1
> 
> How to do this depends entirely on your distribution, here with debian
> woody, this file is generated.
> 
> HTH,
> Jörg.
> _______________________________________________
> at76c503a-user mailing list
> [email protected]
> http://lists.berlios.de/mailman/listinfo/at76c503a-user
>