TRENDware 802.11g 54MBPS PCI card driver?

[tempestuous]

The acx100 driver is not recognising a valid device, so all I can suggest is that you go back a step and do some hardware troubleshooting.
1. Does the card work in other PC's, or the same PC under Window$?
2. Make sure your bios is set for "PnP OS = NO"
3. Does "dmesg" or "lspci" show the card?
4. Does "cat /proc/interrupts" show an irq conflict?

[edoc]

The acx100 driver is not recognising a valid device, so all I can suggest is that you go back a step and do some hardware troubleshooting.
1. Does the card work in other PC's, or the same PC under Window$?
2. Make sure your bios is set for "PnP OS = NO"
3. Does "dmesg" or "lspci" show the card?
4. Does "cat /proc/interrupts" show an irq conflict?

Here is the output from those three info requests. In the meanwhile I will reboot into BIOS and check that setting:

START OF dmesg TEXT

(Some of the early output was cut off -- is there
a way to increase the buffer size?)

ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
PCI: Using ACPI for IRQ routing
Applying VIA southbridge workaround.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
apm: overridden by ACPI.
Starting kswapd
Journalled Block Device driver loaded
Squashfs 2.1-r2 (released 2004/12/15) (C) 2002-2004 Phillip Lougher
pty: 2048 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10f
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 12288K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:04.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:04.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
PDC20265: IDE controller at PCI slot 00:11.0
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
ide2: BM-DMA at 0x8800-0x8807, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x8808-0x880f, BIOS settings: hdg:pio, hdh:pio
hda: QUANTUM FIREBALLP LM20.5, ATA DISK drive
blk: queue c034b540, I/O limit 4095Mb (mask 0xffffffff)
hdc: LTN526S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 40132503 sectors (20548 MB) w/1900KiB Cache, CHS=2498/255/63, UDMA(33)
Partition check:
hda: hda1 hda2
ide: late registration of driver.
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.

Freeing unused kernel memory: 132k freed
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
SCSI subsystem driver Revision: 1.00
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:0a.0: 3Com PCI 3cSOHO100-TX Hurricane at 0xa400. Vers LK1.1.18
Via 686a/8233/8235 audio driver 1.9.1-ac3
PCI: Setting latency timer of device 00:04.5 to 64
ac97_codec: AC97 Audio codec, id: ICE17 (ICE1232)
via82cxxx: board #1 at 0xB800, IRQ 5
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 10:58:54 Jun 17 2005
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xd000, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
hub.c: new USB device 00:04.2-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x3f0/0x3d11) is not claimed by any active driver.
hub.c: new USB device 00:04.2-2, assigned address 3
usb.c: USB device 3 (vend/prod 0xa16/0x9988) is not claimed by any active driver.
hdc: attached ide-cdrom driver.
hdc: ATAPI 52X CD-ROM drive, 120kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport_pc: Via 686A parallel port: io=0x378
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Memorex Model: ThumbDrive Rev: 7.77
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 256000 512-byte hdwr sectors (131 MB)
sda: Write Protect is off
sda: sda1
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
USB Mass Storage support registered.
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 2 if 1 alt 0 proto 2 vid 0x03F0 pid 0x3D11
printer.c: v0.13: USB Printer Device Class driver
lp0: using parport0 (polling).
lp0: console ready
END COPY OF dmesg TEXT

# lspci
0:0.0 1106:0305 (rev 03)
0:1.0 1106:8305
0:4.0 1106:0686 (rev 40)
0:4.1 1106:0571 (rev 06)
0:4.2 1106:3038 (rev 16)
0:4.3 1106:3038 (rev 16)
0:4.4 1106:3057 (rev 40)
0:4.5 1106:3058 (rev 50)
0:10.0 10b7:7646 (rev 30)
0:11.0 11ab:1faa (rev 03)
0:17.0 105a:0d30 (rev 02)
1:0.0 10de:0110 (rev b2)

# cat /proc/interrupts
CPU0
0: 5228568 XT-PIC timer
1: 1732 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 10116 XT-PIC via82cxxx, eth0
8: 1 XT-PIC rtc
9: 14011 XT-PIC acpi, usb-uhci, usb-uhci
12: 98231 XT-PIC PS/2 Mouse
14: 17344 XT-PIC ide0
15: 35 XT-PIC ide1
NMI: 0
ERR: 0

doc

[edoc]

The acx100 driver is not recognising a valid device, so all I can suggest is that you go back a step and do some hardware troubleshooting.

2. Make sure your bios is set for "PnP OS = NO"

PNP is OFF

doc

[tempestuous]

OK. 11ab:1faa is the critical information. It appears that there is a later version of the Trendnet TEW-423PI (rev 03) which has a Marvell chipset, not TexasInstruments.
So ndiswrapper is your only option. On their compatibility list, http://ndiswrapper.sourceforge.net/medi ... x.php/List at T. 17, it appears you should be able to use the Window$ driver on your CD, but I read elsewhere that you might need to download a new version from http://www.trendware.com/fr/asp/downloa ... YPE_ID=690#

[edoc]

OK. 11ab:1faa is the critical information. It appears that there is a later version of the Trendnet TEW-423PI (rev 03) which has a Marvell chipset, not TexasInstruments.
So ndiswrapper is your only option. On their compatibility list, http://ndiswrapper.sourceforge.net/medi ... x.php/List at T. 17, it appears you should be able to use the Window$ driver on your CD, but I read elsewhere that you might need to download a new version from http://www.trendware.com/fr/asp/downloa ... YPE_ID=690#

Well, that is terribly disappointing news! I deliberately bought those boards because they were not going to force the ndiswrapper kludge.

I guess I am stuck with ndiswrapper until someone smarter than me creates a better way to get Linux & most wireless nocs to talk to one another -- or the manufacturers cease cowering before the Gates tyranny -- or the manufacturers hire some competent programmers who can write Linux drivers.

Thanks for your help ... will get back to this as soon as I can.

;-( doc

[puppypilgrim]

Edoc,

There appears to be a solution to your situation. Goto Marvell.com and download the driver MRV8335A.inf

This is the Windows driver. Follow the discussion below and it should install and work. Good luck.


-----------------------------------------------------

The following discussion is taken from here: http://article.gmane.org/gmane.linux.dr ... neral/5137

From: Alysa Leve <aleve <at> nightmare.com>
Subject: Re: TRENDnet TEW-423PI not working with ndiswrapper
Newsgroups: gmane.linux.drivers.ndiswrapper.general
Date: 2005-12-07 00:24:46 GMT (4 weeks, 19 hours and 7 minutes ago)

Giridhar,

Thanks for the information. Downloaded the driver from marvell.com and
now it is loading:

[root <at> orahome1 DRV]# ndiswrapper -i MRV8335A.inf
Installing mrv8335a
Forcing parameter AdhocGMode|1 to AdhocGMode|0
Forcing parameter AdhocGMode|1 to AdhocGMode|0
[root <at> orahome1 DRV]# ndiswrapper -l
Installed ndis drivers:
mrv8335a driver present, hardware present

Once again thanks.

-Bennett

Giridhar Pemmasani wrote:

>I guess the driver for wg311v2 (if that uses marvell chipset) is meant
>for different pci id. You should create an alias for your pci id for
>wg311v2 driver with 'ndiswrapper -d' option.
>
>BTW, driver from marvell.com should be preferred as it is more recent
>and supports power management, whereas wg311v2 driver is a bit old. If
>you want to use driver from marvell.com, uninstall wg311v2, install
>marvell's driver, and if necessary (if 'ndiswrapper -l' doesn't report
>'hardware present'), create an alias as explained above.

[puppypilgrim]

Here is the driver for the marvell chipset. Download it, unzip and follow instructions in the thread from previous post and see if it works for you.

BIOS PnP = NO

1. Unzip file

2. ndiswrapper -i MRV8335.inf

3. ndiswrapper -l

4. ## now set up the wireless network
iwconfig wlan0 essid MY_ESSID key 1234567890 mode Managed

## for automatic IP
dhcpcd -t 20 -h puppypc -d wlan0

## or for static IP
## modify /etc/resolv.conf to include your nameservers

#ifconfig wlan0 192.168.0.xx broadcast 192.168.0.255 netmask 255.255.255.0

#route add default gw 192.168.0.1 wlan0 # or whatever your router's IP #is

DISCLAIMER: I have no idea if any of what I have written will work or not. I am not a Linux Expert. But I have tried to scour the internet for the best fixes since I intend to buy this card as well. Let me know if this works for you.

[edoc]

Thanks puppypilgrim for your efforts!

I have modified your instructions some so that others following them see all of the sub-steps and details.

1. In your computer BIOS locate and set PnP = NO

2. Download (or copy from CD) the correct driver for your wireless card (in this case puppypilgrim provided the mrv8335 driver as a zip file).

3. Copy the "xxxxx.inf" file to /mnt/home or Unzip the zipped file (as in this case) to /mnt/home

4. Download (or copy if you already have it on a USB stick or CD) the usr_devx.sfs file to /mnt/home

5. Reboot

6. Open rxtv or some other console (teminal app/command line app) and type "ndiswrapper -i mrv8335.inf" (Be careful of upper and lower case and of precise spacing, these commands are very fussy.)

7. Type "ndiswrapper -l"

STOP!!

This is where I had to stop for the moment as I received the
message "mrv8335 invalid driver!"

I am going to dig the driver out of the CD that came with the
wireless nic and retry this.

Note: Manufacturers have a really bad habit of changing chipsets in
the middle of production runs and of failing to change the device
number to reflect that. This should be a no-no and pressure needs
to be applied from consumers to force them to properly label changes.

There are two known chipset differences in this Trendware wireless nic,
perhaps the Marvell driver reflects a third and not the one I have with is the second?

Will update this thread as soon as I have some progress to report.

Thanks! doc

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[edoc]

CONTEXT: Running 1.0.7 for these tests on a desktop PC.

This is where I had to stop for the moment as I received the
message "mrv8335 invalid driver!"

I am going to dig the driver out of the CD that came with the
wireless nic and retry this.

OK, just tried the WinXP Mrv8000c.INF file from the CD and it also failed with a similar "mrv8000c.inf invalid driver" message.

Anyone have thoughts as to what may be going wrong, please?

Thanks! doc

[puppypilgrim]

I wish to confirm that you have tried both the ACX1xx from Tempestuous and the MRV8000c and MRV8335 inf drivers from Marvell.com.

Hmmm, I wonder if kernel support has changed with the versions going to 1.07. I haven't received my Trendware card yet (supposed to get it later tonight). Have you tried both drivers with Puppy 1.05 or lower to check for kernel issues?

What ndiswrapper version are you running? Some users report differences from one version to another.

[edoc]

I wish to confirm that you have tried both the ACX1xx from Tempestuous and the MRV8000c and MRV8335 inf drivers from Marvell.com.

Hmmm, I wonder if kernel support has changed with the versions going to 1.07. I haven't received my Trendware card yet (supposed to get it later tonight). Have you tried both drivers with Puppy 1.05 or lower to check for kernel issues?

What ndiswrapper version are you running? Some users report differences from one version to another.

I tried the acx100 on Puppy 1.0.6 so I should try it on 1.0.7 so that all three are tested on the same platform.

I do have some older Puppy cd's around so I suppose I could try 1.0.4, 1.05. and 1.06 but I really want this nic working under 1.0.7 and to keep working under new versions.

Unless someone knows of a specific flaw in 1.0.7 that could impact loading these drivers I'd rather not play version-roulette.

I had hoped that wireless nics and ndiswrapper would finally be addressed in 1.0.7 -- perhaps it will rise as a priority in one of the next versions?

Between wireless nics and printers Puppy is locked out of much of the potential user population due driver access. How many non-geek users would jump though so many hoops and wait months to use their wireless nics and printers?

doc

[puppypilgrim]

I sympathize with your frustration. Linux is not easy that way. However, I find it much more rewarding (for a myriad of reasons) to be in Linux than Windows.

When I get my Trendware card, I will try it out and see what happens.

[edoc]

I sympathize with your frustration. Linux is not easy that way. However, I find it much more rewarding (for a myriad of reasons) to be in Linux than Windows.

When I get my Trendware card, I will try it out and see what happens.

I am almost exclusively Puppy Linux here but am occasionally forced via church or business systems to slum with MS Windows

(Pet Peeve: I believe we should always specify MS Windows since there are many OS's which use the "windows" format and MS did not originate it.)

Sure hope you spot the glitch that I am missing. I am going to try this on a laptop as the same desktop PC fails to play nice when I try to load the HP drivers & CUPS. Everything looks good until the very end of that process as well and no-one in Puppydom can figure out why.

I have not tried the HP printer thing under 1.0.7 but have no reason to believe that the printer thing received significant attention in 1.0.7, am hoping for that in 1.0.8 since the Puppy folks made huge strides with CUPS between 1.0.6 and 1.0.7.

I have hopes that the ndiswrapper script will also be automated in 1.0.8 since it appears to have been close to complete since WAG in v. 1.0.4.

doc

[tempestuous]

puppypilgrim and edoc,
A few points which should help -

1. When ndiswrapper installs a Windows .inf file, it needs other driver files specified by the .inf file, especially .sys files. So you must have all related Windows driver files in the same location.

2. The particular version of Windows driver you use can make a critical difference. See the ndiswrapper compatibility page for exact details - http://ndiswrapper.sourceforge.net/medi ... x.php/List
In the case of the Trendnet TEW-423PI (rev 03) the driver from www.marvell.com might work (?), but the version from www.trendware.com is recommended.

3. puppypilgrim's setup instructions are missing a few steps. I don't use ndiswrapper myself, but according to information at their homepage this is how it should be -

ndiswrapper -i /mnt/home/mywindowsdriver.inf
## now you can check installed drivers with "ndiswrapper -l"
depmod -a
modprobe ndiswrapper
## now set up the wireless network
iwconfig wlan0 essid MY_ESSID key 1234567890 mode managed
dhcpcd -t 20 -h puppypc -d wlan0

... or, you could use wifi-1.0.4-beta-2.pup from
http://www.yourfilehost.com/media.php?c ... beta-2.pup
which automates ndiswrapper setup for you.

[tempestuous]

I just noticed 2 points I should correct -

Download (or copy if you already have it on a USB stick or CD) the usr_devx.sfs file to /mnt/home

Not necessary. This is for compiling. You have nothing to compile.

I tried the acx100 on Puppy 1.0.6 so I should try it on 1.0.7 so that all three are tested on the same platform.

No point. If your card has pciid 11ab:1faa then it's definitely Marvell and the acx100 driver will be useless.

[edoc]

I just noticed 2 points I should correct -

Download (or copy if you already have it on a USB stick or CD) the usr_devx.sfs file to /mnt/home

Not necessary. This is for compiling. You have nothing to compile.

I added this due to the instructions in WAG which imply that ndiswrapper needs usr_devx.sfs

One less step is cool.

PROBLEM:

When I add the .sys file from the Trendware CD in the WinXP folder and try to re-run the ndiswrapper install it complains that the driver has already been installed.

When I run "ndiswrapper -e mrv8000c.inf" I am told that the driver has been uninstalled but when I run ndiswrapper -l it says it is still there and if I re-run ndiswrapper it says the driver is already installed.

How do I get rid of the defective install so I may try a new install?

Always something!

Thanks! doc

[tempestuous]

ndiswrapper -l
will list currently installed drivers. Let's say you see "mydriver". Now -
ndiswrapper -e mydriver
will remove this installed driver.

I edited the earlier ndiswrapper instructions to remove "ndiswrapper -m" - this step is not important.

[edoc]

PROBLEM:

When I add the .sys file from the Trendware CD in the WinXP folder and try to re-run the ndiswrapper install it complains that the driver has already been installed.

When I run "ndiswrapper -e mrv8000c.inf" I am told that the driver has been uninstalled but when I run ndiswrapper -l it says it is still there and if I re-run ndiswrapper it says the driver is already installed.

How do I get rid of the defective install so I may try a new install?

OK, found this (see following).

Black is what is supposed to work, Red is how one forces the issue when "ndiswrapper -e mdr800c.inf" doesn't work.

Will give it a try and report back ... Always a new adventure!

http://ndiswrapper.sourceforge.net/medi ... /Uninstall

Uninstall
From NdisWrapper

Starting with version 1.0, you can uninstall programs and modules installed with 'make uninstall' in ndiswrapper directory. This won't remove Windows drivers installed in '/etc/ndiswrapper'; for that, you should 'ndiswrapper -e <driver>' command. Rest of this document shouldn't be necessary to uninstall. However, should you have problems, follow it and see if 'make uninstal' fails to remove anything and report that to mailing list or forums.

* Make sure you unload your current ndiswrapper module with 'modprobe -r ndiswrapper'

* You need to remove the user space tools 'ndiswrapper' (in /usr/sbin) and 'loadndisdriver' (in /sbin), and kernel module 'ndiswrapper' (in /lib/modules/`uname -r`/misc). If these files are not in these locations, then they may have been installed elsewhere (e.g., user spaces tools may be installed in /usr/bin). You can use 'which' or 'locate' command to now where the user space tools are located (e.g., 'which ndiswrapper' gives the location of 'ndiswrapper' tool). Once these are located, remove them; e.g., 'rm ndiswrapper'. Note that the kernel module file is called ndiswrapper.o in 2.4 kernels and ndiswrapper.ko in 2.6 kernels.

* Alternately, you can use 'locate' to find where ndiswrapper files are stored. First, update the database used by 'locate' with 'updatedb'. This takes sometime and when it is done, run 'locate ndiswrapper' and remove all the files listed and then run 'locate loadndisdriver' and remove all the files listed.

* If 'locate' doesn't find the module, you can use 'find' instead:

find /lib/modules/$(uname -r) -name "ndiswrapper*" -print

will print the location of the modules. You should then remove all the files printed.

* ndiswrapper installs Windows drivers under /etc/ndiswrapper directory. If you want to uninstall just a specific Windows driver, first list the drivers installed with "ndiswrapper -l". If you then want to remove, say, driver "bcmwl5", then remove it with ndiswrapper itself with "ndiswrapper -e bcmwl5". If that doesn't work, just remove the directory /etc/ndiswrapper/bcmcwl5 (e.g., with '/bin/rm -rf /etc/ndiswrapper/bcmwl5'). If you want to uninstall all Windows drivers, then remove /etc/ndiswrapper (e.g,. with '/bin/rm -rf /etc/ndiswrapper').

* 'ndiswrapper -m' (creates and) installs an alias in /etc/modprobe.d/ndiswrapper. If you want to remove this alias (since you might not want ndiswrapper module to be loaded when using wlan0 network interface), remove it: 'rm -f /etc/modprobe.d/ndiswrapper'

[edoc]

* ndiswrapper installs Windows drivers under /etc/ndiswrapper directory. If you want to uninstall just a specific Windows driver, first list the drivers installed with "ndiswrapper -l". If you then want to remove, say, driver "bcmwl5", then remove it with ndiswrapper itself with "ndiswrapper -e bcmwl5". If that doesn't work, just remove the directory /etc/ndiswrapper/bcmcwl5 (e.g., with '/bin/rm -rf /etc/ndiswrapper/bcmwl5'). If you want to uninstall all Windows drivers, then remove /etc/ndiswrapper (e.g,. with '/bin/rm -rf /etc/ndiswrapper').

OK, this worked and reinstalling mrv8000c.inf with all three files present from the Trendware CD worked per Tempestuous' fine instructions.

NEW PROBLEM (of course):

ndiswrapper -l tells me:

"mrv8000c driver present"

That is good but not good enough, it should also say ", "hardware present"

ALSO, when I try to run:
"iwconfig wlan0 essid MY_ESSID key 1234567890 mode Managed " it tells
me "wlan0 No such device"

SO I TRY WAG and when I run WAG it finds nothing to work with.

SO I TRY Hardware Probe and it sees 11ab:1faa though it reports that it cannot find any information about the device.

Now what, please? Thanks! doc

[edoc]

Found a good discussion here:
http://danleff.net/myarticles/linksyswmp54gpage3.html

And another here:
http://ndiswrapper.sourceforge.net/medi ... p/ListItoP

# Card: Mentor WLG-PCI/II (802.11b/g)

* Chipset: Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
* pciid: 11ab:1faa (rev 03)
* Driver: mrv8335 (http://www.marvell.com/drivers/driverDi ... =122&pId=3)
* Other: The drivers on the CD provided with the card contains the mrv8000c drivers, but these drivers doesn't work fine for me. You can download the "Libertas CB-35P/MB-35P driver" on Marvell's site (link above). They work well with ndiswrapper 1.4 on a 2.6.13-gentoo-r3 kernel. You can also check this document (in French): http://perso.wanadoo.fr/kdntl/articles/ ... id-10.html

But neither tells me how to fix the wlan0 problem.

doc