Re: Linksys WMP55AG PCI

Then why in the world is it listed on a page linked to from something that says
"Hardware Compatibility - UPDATED February 1, 2004"? It is incredibly unclear
that it's not supported. I realize that there's a "Linux Support" column there
that's empty, but I doubt very strongly that I'm the only one who's ever taken
that page as a list of cards supported under Linux.

I'll go talk to the madwifi people to get this running. Meanwhile, if anyone on
this list has the power to do so, I'd strongly suggest making it more clear
which cards are supported and which aren't.

Alex Kirk

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This card is not supported by this driver.  If you look at the page you
> will notice that this card has an atheros chipset, which is not
> supported by the wlan-ng drivers (this only support 802.11b devices with
> a prism based chipset).
> 
> Fortunately you bought a card that is quite well supported under Linux,
> and what you are looking for is likely to be found here.
> http://sourceforge.net/projects/madwifi/
> 
> As a side note, it is better to use modprobe to insert the kernel
> module.  It won't help with your issue because you are loading the wrong
> driver for your hardware, but for future reference.
> 
> Cheers,
> Gustin
> 
> Alex Kirk wrote:
> > Hello All,
> > 
> > I recently purchased a PCI-based Linksys WMP55AG card, in large part
> because it
> > was listed as supported on
> http://www.linux-wlan.org/docs/wlan_adapters.html.gz.
> > Much to my chagrin, however, I've been having some real trouble getting it
> up
> > and running so far, and I'm hoping that someone here can help.
> > 
> > Using linux-wlan-ng-0.2.2, I was able to successfully build prism2_pci.o
> for my
> > kernel, along with all of the other supporting modules. However, when the
> system
> > tries to insmod prism2_pci, I get:
> > 
> > Using /lib/modules/2.4.22/net/prism2_pci.o
> > /lib/modules/2.4.22/net/prism2_pci.o: init_module: No such device
> > /lib/modules/2.4.22/net/prism2_pci.o: Hint: insmod errors can be caused by
> > incorrect module parameters, including invalid IO or IRQ parameters.
> >       You may find more information in syslog or the output from dmesg
> > 
> > dmesg isn't particularly helpful; in fact, I see only one line related to
> that
> > module:
> > 
> > prism2pci_init: prism2_pci.o: 0.2.2 Loaded
> > 
> > meanwhile, lsmod shows that the module isn't actually loaded:
> > 
> > Module                  Size  Used by    Tainted: P
> > p80211                 25424   0
> > ipt_MASQUERADE          1272   1 (autoclean)
> > iptable_nat            15928   1 (autoclean) [ipt_MASQUERADE]
> > ip_conntrack           18120   1 (autoclean) [ipt_MASQUERADE iptable_nat]
> > iptable_filter          1644   0 (autoclean) (unused)
> > ip_tables              12288   5 [ipt_MASQUERADE iptable_nat
> iptable_filter]
> > cisco_ipsec           379232   1
> > snd-pcm-oss            37252   0
> > snd-mixer-oss          11992   1 [snd-pcm-oss]
> > uhci                   24496   0 (unused)
> > usbcore                58400   1 [uhci]
> > snd-intel8x0           17156   1
> > snd-pcm                55904   0 [snd-pcm-oss snd-intel8x0]
> > snd-timer              13252   0 [snd-pcm]
> > snd-ac97-codec         37240   0 [snd-intel8x0]
> > snd-page-alloc          6004   0 [snd-intel8x0 snd-pcm]
> > snd-mpu401-uart         3136   0 [snd-intel8x0]
> > snd-rawmidi            12512   0 [snd-mpu401-uart]
> > snd-seq-device          3920   0 [snd-rawmidi]
> > snd                    27460   0 [snd-pcm-oss snd-mixer-oss snd-intel8x0
> snd-pcm
> > snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device]
> > soundcore               3332   3 [snd]
> > tulip                  40928   1
> > crc32                   2880   0 [tulip]
> > ide-scsi                9424   0
> > agpgart                39576   0 (unused)
> > 
> > I know that it's not an improperly built set of modules, given that the
> freshly
> > built p80211 module loads like a charm (in fact, I get unresolved symbol
> errors
> > if I try to unload it and then load the prism2_pci module, as expected).
> > However, some sort of hardware weirdness does seem likely, given the output
> of
> > lspci -vv for the card:
> > 
> > 01:0a.0 Ethernet controller: Unknown device 168c:0013 (rev 01)
> >         Subsystem: Linksys: Unknown device 0018
> >         Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr-
> > Stepping- SERR- FastB2B-
> >         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> > <TAbort- <MAbort- >SERR- <PERR-
> >         Latency: 32 (2500ns min, 7000ns max), cache line size 08
> >         Interrupt: pin A routed to IRQ 11
> >         Region 0: Memory at d5010000 (32-bit, non-prefetchable) [size=64K]
> >         Capabilities: [44] Power Management version 2
> >                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> > PME(D0-,D1-,D2-,D3hot-,D3cold-)
> >                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
> > 
> > After seeing all of this, I looked in the list archives, and to my great
> > surprise, I saw indications that this card isn't *actually* supported by
> > Linux-Wlan, but that I'd instead need to use drivers from
> > http://sourceforge.net/projects/madwifi/. Unfortunately, I've downloaded
> several
> > versions of those drivers, and I haven't even been able to get them to
> compile.
> > 
> > All that said, does anyone on this list know if my card is actually
> supported by
> > Linux-Wlan, and if so, what I'd need to do to get it up and running?
> > Alternately, does anyone have enough experience with these alternate
> drivers tha
> > they could help with them? Frankly I don't care what drivers I use, so long
> as
> > my card works. :-P
> > 
> > Thanks,
> > Alex Kirk
> > _______________________________________________
> > Linux-wlan-user mailing list
> > [email protected]
> > http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFDmGBQwRXgH3rKGfMRAgMZAJ9w9YC2hqGsgRMvQGRZlCOPnEgpYgCeI7rB
> G12YK1GIlD9O/0RUXEeltSU=
> =Sifl
> -----END PGP SIGNATURE-----
>