Netgear wg311v3 and Fedora 8

[Dan Williams]

On Mon, 2007-11-19 at 14:42 -0500, Randy Yates wrote:
> Hi List Members,
> 
> I'm trying to get my wg311v3 card working on my wife's home
> desktop system:

8335 chipsets are quite different from the 8388 & 8385 & 8686 actually.
The 8335 is a "softmac" chipset and the ones the current libertas driver
supports are the fullmac variety.  The 8335 isn't supported right, but
there is actually code floating around so at some point in the near
future it may be supported by another driver (mrv8k or mrvng are the
two).

Dan

>   Linux localhost.localdomain 2.6.23.1-49.fc8 #1 SMP Thu Nov 8 22:14:09 EST 2007 x86_64 x86_64 x86_64 GNU/Linux
> 
> I have a few questions:
> 
>   1. Should the Marvel Libertas driver work with this card? lspci -vvv
>   returns
> 
> 00:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
>         Subsystem: Netgear Unknown device 6b00
>         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: 64, Cache Line Size: 32 bytes
>         Interrupt: pin A routed to IRQ 10
>         Region 0: Memory at fbc00000 (32-bit, non-prefetchable) [size=64K]
>         Region 1: Memory at fbb00000 (32-bit, non-prefetchable) [size=64K]
>         Capabilities: [40] Power Management version 2
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
>   2. If the answer to 1 is yes, then how do I install it? The
>   installation didn't recognize the card, only the integrated wired
>   ethernet interface, which it configured as eth0. That is, ifconfig
>   after installation shows
> 
> eth0      Link encap:Ethernet  HWaddr 00:15:F2:4C:38:25  
>           inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::215:f2ff:fe4c:3825/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:360487 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:364827 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:42994405 (41.0 MiB)  TX bytes:216713105 (206.6 MiB)
>           Interrupt:11 Base address:0x2000 
> 
> lo        Link encap:Local Loopback  
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:18273 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18273 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0 
>           RX bytes:9462892 (9.0 MiB)  TX bytes:9462892 (9.0 MiB)
> 
>   I presume that the way to add the card is by invoking
>   system-config-network and then pressing the "New" button, selecting
>   "Other Wireless Card" (there are no other entries in the edit box),
>   and then selecting one of the cards in the "Adapter" list. However,
>   the Netgear card isn't there and it isn't apparent which of the cards
>   that are listed use the Marvel chipset. Which card should I select?
> 
>   Also, will this driver work with the 64-bit version of the kernel?
> 
>   3. If the answer to 1 is no, then let me state that I've had about 98
>   percent success in getting the driver from Marvell for XP working
>   using ndiswrapper. I see the interface using iwconfig, and I can do a
>   scan via iwlist wlan0 scan and see several nearby networks. However,
>   after configuring essid, channel number, and mode, and then issuing a
>   "ifconfig wlan0 up" and "ifconfig eth0 down" command, I get
>   disconnected. Any help there?
> 
>   4. I read on the ndiswrapper site that in order to use ndiswrapper the
>   kernel is supposed to be built using no-4k stack sizes (i.e., the a
>   stack size greater than 4k should be allowed). It states that to do
>   this, you should configure the kernel (make menuconfig) selecting the
>   Kernel Hacking... option and then NO4KStack (or somesuch). However, in
>   the 2.6.23 kernel, that option seems to be missing. Could it be that
>   the driver isn't operating correctly because the kernel is running
>   with a 4k stack limitation?
> 
>   5. In either case of 2 or 3, should I be able to use the NetManager
>   software to maintain the wired/wireless interfaces once I've got the
>   the correct driver installed?
> 
> Well, that's all for now... Thanks for any help/pointers you can provide.
> -- 
> %  Randy Yates                  % "The dreamer, the unwoken fool - 
> %% Fuquay-Varina, NC            %  in dreams, no pain will kiss the brow..."
> %%% 919-577-9882                %  
> %%%% <yates at ieee.org>           % 'Eldorado Overture', *Eldorado*, ELO
> http://www.digitalsignallabs.com
> 
> _______________________________________________
> libertas-dev mailing list
> libertas-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libertas-dev