Re: Problem using CVS Tarball on 2.6.5 kernel

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?

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?

Thanks again,
Ewan