Re: CNET 611 support

Joerg Albert <[email protected]>
Newsgroups gmane.linux.drivers.at76c503a.user
Message-ID <Pine.LNX.4.56.0401072321160.504@invb>
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.