Fedora Core 3 not detecting my wifi card WG311v2

[Funky_DJ]

All,
I've installed Fedora Core3 (kernel 2.6.9.1.68???) and plugged in my Netgear WG311v2.

Logged in as root , opened a terminal and typed in lspci.

No sign of the card I've plugged in.....should there be or should I install ndiswrapper modules and reboot before expecting to see any info return form the "lspci /lspci -n" cmds??

[Detour]

Hey there I just finished installing this the other day. If I remember correctly lspci actually lists the chipset "Texas Instruments acx111" or some such. Anyway here's what I did to get it working:

1. Install the stack 16 kernel from Linuxant: http://www.linuxant.com/driverloader/wlan/full/downloads-fc3-kernel-i686.php

2. Install ndiswrapper. I couldn't find an rpm so I just followed the directions to compile from the ndiswrapper wiki (don't follow the directions for fedora they don't work)

Note that ndiswrapper is located in /usr/sbin so when executing the command use /usr/sbin/ndiswrapper

3. Install the windows xp driver included on the cd.


Oh yes and if you don't feel like messing around with ndiswrapper, Linuxant will provide you with a license (and support) for free. Quote from an email they sent when I asked about it:

"Since you will use a device based on the TI ACX111 chipset, you will not have to install a license at all."

[Funky_DJ]

Hey there I just finished installing this the other day. If I remember correctly lspci actually lists the chipset "Texas Instruments acx111" or some such. Anyway here's what I did to get it working:

1. Install the stack 16 kernel from Linuxant: http://www.linuxant.com/driverloader/wlan/full/downloads-fc3-kernel-i686.php

2. Install ndiswrapper. I couldn't find an rpm so I just followed the directions to compile from the ndiswrapper wiki (don't follow the directions for fedora they don't work)

Note that ndiswrapper is located in /usr/sbin so when executing the command use /usr/sbin/ndiswrapper

3. Install the windows xp driver included on the cd.


Oh yes and if you don't feel like messing around with ndiswrapper, Linuxant will provide you with a license (and support) for free. Quote from an email they sent when I asked about it:

"Since you will use a device based on the TI ACX111 chipset, you will not have to install a license at all."

Cool....could you post the link to the ndiswrapper wiki?
Also did you take the Linuxant offer any further - is this free licence available to download from there site??

[Detour]

http://ndiswrapper.sourceforge.net/phpwiki/index.php/Installation

I didn't follow up with Linuxant because I already had ndiswrapper installed so I tried that first and it worked first time. However, the way they work (as I understand it) is, they provide you with software that will load the drivers for your card but the license given to you is bound by your card's MAC address. Normally, you're free to try the software for 30 days and then you must purchase your license from them (reasonable, only $20). However, Texas Instruments has licensed Linuxant to support cards which feature their chipsets, so the fee for puchasing a license is waived. I woul d suggest that if you have any problems installing ndiswrapper to not waste your time and just head over to Linuxant for professional support.

[Funky_DJ]

Cool ...now you said "Hey there I just finished installing this the other day. If I remember correctly lspci actually lists the chipset "Texas Instruments acx111" or some such. Anyway here's what I did to get it working: "

If I don't see the lspci listing - is it worth my while going ahead and installing modules - I'm doing this on a rather old ABit BX6 II motherboard/Intel Celeron II CPU and I'm worried that the combination of those two non-linux friendly hardware items is stopping me before I get started - hence not being able to see

[Detour]

ah, I think I see your problem. This card uses a pci 2.2 slot which is supported by newer mobos.... I'm using an Asus K8N-E Deluxe (for my Athlon64 3000+ CPU). I'm guessing that if you can't see it with lspci that this is likely the reason.