Re: Problem using CVS Tarball on 2.6.5 kernel

Hi Ewan,

On Sat, 14 Aug 2004, Ewan Grantham wrote:

> On Sat, 14 Aug 2004 23:48:15 +0200 (CEST), Joerg Albert
> <[email protected]> wrote:
> > Please set debugging to 0x184003 in at76c503:
> >         modprobe -v at76c503 debug=0x184003
> >         modprobe -v at76c505-rfmd2958
> > plug the device in and post the syslog (with debug msgs included).
>
> OMG...
>
> When I did both modprobes, as listed above, the device was recgnized as wlan0.
>
> Can I assume that I was just being dumb in not realizing I needed to
> do a modprobe of both the at76c503 AND the 505 explicitly?

IMHO you inserted at76c505-rfmd before, not at76c505-rfmd2958
(please blame Atmel for so many (firmware) variants).

The two modprobes above are only needed to pass the debug= to at76c503;
a single
	modprobe -v at76c505-rfmd2958
should do the job as well (if depmod -ae run before as part of "make
install").

> To avoid having to do this by hand in the future, I assume I would add
> both of these (except not the -v or the debug) to the modprobe.conf?
> And, newbie question, where would that file go since I haven't needed
> it up to now?
> Finally, is there an iwconfig configuration file so I can avoid having
> to enter my essid and channel manually on each reboot?

IMHO, all this depends on your distribution. Here with Debian Woody,
hotplug does the modprobe automatically on plugging-in the device.
See
http://at76c503a.berlios.de/support.html#distros
for where to put the iwconfig params for some distros.

/Jörg