Re: Problem using CVS Tarball on 2.6.5 kernel
Alex Schultz <[email protected]>
| Newsgroups | gmane.linux.drivers.at76c503a.user |
|---|---|
| Message-ID | <[email protected]> |
Hi,
In cases like this when a modprobe -v shows no errors, the portion of
the output of the dmesg command that is new after the modprobe is
extreamly helpful for diagnostics. It would help if you post the portion
of the dmesg output that is new after the modprobe here (or the whole
dmesg output is ok if you can't isolate what the proper portion).
Alex S.
Ewan Grantham wrote:
>On Fri, 13 Aug 2004 01:03:35 +0200 (CEST), Joerg Albert
><[email protected]> wrote:
>
>
>>Call "modprobe -v at76c505-rfmd2958", _not_ "modprobe -v
>>at76c505-rfmd2958.ko" !
>>
>>
>
>Rebuilt to make sure the 2958 version was installed properly, and then
>did a modprobe as you show above rather than modprobe -v at76c503 as I
>had understood from the readme.
>
>Doing so shows a number of messages indicating the drivers are
>loading, and lsmod shows the drivers as loaded, but iwconfig wlan0
>still returns with no such device. Do I need to do something to make
>sure the drivers are loading as wlan0? Any other ideas? I've tried
>both with it plugged in when I boot, and not plugged in initially but
>after login.
>
>Thanks in advance,
>Ewan
>_______________________________________________
>at76c503a-user mailing list
>[email protected]
>http://lists.berlios.de/mailman/listinfo/at76c503a-user
>
>
>