LAN Adapter will not work--tried ndiswrapper and Wine

**tatiana30241** · 03-31-2010

I am having a very hard time getting my EnGenius wireless LAN adapter to work on Linux Mint Helena. I have been scouring forums and fighting with this thing for 3 days now and I just am having very little luck. To make matters worse my Linux experience is very limited--about 4 days worth, to be specific--and I know I am bumbling around quite a bit. I would be extremely grateful if someone would help me solve this problem.

lsusb gives this output for my device:

Bus 001 Device 002: ID 0cf3:0002 Atheros Communications, Inc. AR5523 (no firmware)

I first tried using ndsiswrapper to load the Windows inf file, which is net5523.inf. It told me it was installed, but the device was still not recognized. An old post on a Ubuntu forum suggested that the device could be installed through Wine, which I finally managed to install without internet. I ran the driver installation through Wine and it seemed to go well, but the device was still listed as not present. I then used ndiswrapper to install the new inf file that the wine installation had put in the virtual system 32 directory, and finally ndiswrapper -l told me the device was installed and present. But iwconfig still lists no wireless extensions.

I tried to follow the directions in the mintWifi post here:

(Nevermind, this forum will not let me post URLs, but it is called mintWifi on the Linux Mint site.)

But I do not see any of the options for the Network Manager that the author describes. I have no option to "connect to another wireless network" or to "deactivate/activate wireless and networking." It doesn't say anything about wireless networks at all.

I looked at the /etc/network/interfaces file, and it says exactly what the author says it should:

auto lo
iface lo inet loopback

I really have no idea what to do here, as every option I found has been exhausted. I am sure I am doing something wrong, but what? Please help if you can.

**waterhead** · 03-31-2010

Hello, we could use more complete details of your system. There may be info that we could use, that is not obvious to you. First, read this sticky:

Wireless Setup - Start Here

Run the script in the second part of that thread, and post the info here.

I doubt that Wine will work. It is mainly for running windows software on Linux, and drivers are hardware related.

**tatiana30241** · 03-31-2010

Oh, thank you so much. I really appreciate this. Here is the information from the script:

============ lspci ============
00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3)
00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0050] (rev a3)
00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2)
Kernel driver in use: nForce2_smbus
Kernel modules: i2c-nforce2
00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2)
Kernel driver in use: ohci_hcd
00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3)
Kernel driver in use: ehci_hcd
00:04.0 Multimedia audio controller [0401]: nVidia Corporation CK804 AC'97 Audio Controller [10de:0059] (rev a2)
Kernel driver in use: Intel ICH
Kernel modules: snd-intel8x0
00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE [10de:0053] (rev f2)
Kernel driver in use: pata_amd
00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3)
Kernel driver in use: sata_nv
00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3)
Kernel driver in use: sata_nv
00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge [10de:005c] (rev a2)
00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller [10de:0057] (rev a3)
Kernel driver in use: forcedeth
Kernel modules: forcedeth
00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3)
Kernel driver in use: pcieport-driver
Kernel modules: shpchp
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103]
Kernel driver in use: k8temp
Kernel modules: k8temp
01:07.0 Communication controller [0780]: Conexant Systems, Inc. HSF 56k Data/Fax Modem [14f1:2f20]
01:0b.0 FireWire (IEEE 1394) [0c00]: Agere Systems FW322/323 [11c1:5811] (rev 61)
Kernel driver in use: ohci1394
Kernel modules: firewire-ohci, ohci1394
05:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV380 [Radeon X600 (PCIE)] [1002:5b62]
Kernel modules: radeon, radeonfb
05:00.1 Display controller [0380]: ATI Technologies Inc RV380 [Radeon X600] [1002:5b72]

============ lsusb ============
Bus 001 Device 003: ID 1058:1100 Western Digital Technologies, Inc.
Bus 001 Device 002: ID 0cf3:0002 Atheros Communications, Inc. AR5523 (no firmware)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

============ lsmod ============
Module Size Used by
isofs 31620 1
udf 80900 0
crc_itu_t 1852 1 udf
binfmt_misc 8356 1
dm_crypt 12928 0
snd_intel8x0 30168 2
snd_ac97_codec 101216 1 snd_intel8x0
ac97_bus 1532 1 snd_ac97_codec
snd_pcm_oss 37920 0
snd_mixer_oss 16028 1 snd_pcm_oss
snd_pcm 75296 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_dummy 2656 0
snd_seq_oss 28576 0
iptable_filter 3100 0
snd_seq_midi 6432 0
snd_rawmidi 22208 1 snd_seq_midi
snd_seq_midi_event 6940 2 snd_seq_oss,snd_seq_midi
snd_seq 50224 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_mid i_event
ip_tables 11692 1 iptable_filter
x_tables 16544 1 ip_tables
snd_timer 22276 2 snd_pcm,snd_seq
snd_seq_device 6920 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi ,snd_seq
ppdev 6688 0
snd 59204 14 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_ oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_ti mer,snd_seq_device
parport_pc 31940 1
lp 8964 0
parport 35340 3 ppdev,parport_pc,lp
i2c_nforce2 6784 0
soundcore 7264 1 snd
snd_page_alloc 9156 2 snd_intel8x0,snd_pcm
k8temp 4188 0
serio_raw 5280 0
joydev 10272 0
dm_raid45 84228 0
xor 15620 1 dm_raid45
hid_logitech 8412 0
ff_memless 5188 1 hid_logitech
usbhid 38208 1 hid_logitech
usb_storage 52544 1
radeon 636000 2
ttm 36212 1 radeon
drm 159584 4 radeon,ttm
agpgart 34988 2 ttm,drm
i2c_algo_bit 5760 1 radeon
ohci1394 29900 0
ieee1394 86596 1 ohci1394
floppy 54916 0
forcedeth 54152 0

============ dmesg-firmware ============

============ kernel version ============
2.6.31-14-generic

============ ifconfig ============
eth0 Link encap:Ethernet HWaddr 00:15:58:50:7f:ae
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:23 Base address:0xc000

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:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:720 (720.0 B) TX bytes:720 (720.0 B)

============ iwconfig ============

**retired1af** · 03-31-2010

You shouldn't have to use ndiswrapper with that wireless card. I have something similar and was able to use the linux driver for that particular card and compile it into the kernel. Works great.

In fact, the distro I use detected it all up front and did it for me.

**tatiana30241** · 03-31-2010

That is encouraging, however, I have looked everywhere and have not been able to find a Linux driver for this device. And Mint most definitely did not detect it up front. What distro did you use?

Also, I am unsure how to compile a driver into the kernel even if I had a driver. Perhaps you would be willing to offer more information, such as what driver to look for and how to compile it into the kernel once I get it.

Thanks,

Tatiana

**waterhead** · 03-31-2010

Unfortunately, there is no driver for your device presently in the kernel. But there is a driver under development. You will need to compile it from the source files, but I will guide you.

There also is a very good Debian How-To. And since Mint is based on Ubuntu, and Ubuntu is based on Debian, it should work:

ar5523 - Debian Wiki

First, you must have an internet connection. I do hope that you can find access to a wired LAN connection. Otherwise this will be very difficult.

Next you have to install a few needed files and programs. That is why you need the internet connection. Enter this to install the prerequisites:

Code:

sudo apt-get install build-essential linux-headers-$(uname -r) subversion wget wireless-tools

Now download the driver source:

Code:

svn co svn://svn.berlios.de/fullstory/ar5523/trunk/ ar5523

The Debian How-To says to next patch it for the 2.6.26 kernel. Since you have the 2.6.30.31 kernel, I don't know if this is necessary. We will follow the instructions, and see how it goes.

Code:

cd ar5523

Code:

patch < debian/patches/kcompat-2.6.2*

Now build the driver.

Code:

make

Now install the driver module. You first need to make a folder for it:

Code:

sudo mkdir -p /lib/modules/$(uname -r)/updates/drivers/net/wireless

Now copy the newly created driver module to the newly created folder.

Code:

sudo cp ar5523/ar5523.ko /lib/modules/$(uname -r)/updates/drivers/net/wireless

Now run the depmod command to make sure the new driver module is properly recognized.

Code:

depmod -a -F /boot/System.map-$(uname -r) $(uname -r)

=========================================

This device needs firmware before it will work. Your terminal should still be in the ar5523 folder, and that is OK. Download the firmware compressed file:

Code:

wget http://verein.lst.de/~hch/ar5523.tgz

Now unpack the archive:

Code:

tar xf ar5523.tgz ar5523/uath-ar5523.bin --strip 1

Then copy the firmware to the /lib/firmware folder:

Code:

sudo mv uath-ar5523.bin /lib/firmware

=========================================

You can now manually load the new driver module, or just reboot. To manually load the module, use this command.

Code:

sudo modprobe ar5523

Remember, this is untested. I haven't even performed all of the steps in this. If you get any errors at any of the steps, please post them.

Good luck!

**reed9** · 03-31-2010

There is a driver in the works for this card, which may still work in its current state of development.

Do you have a wired connection for now?

If so, I found instructions for building the module on the Debian Wiki, and Ubuntu/Mint are based on Debian, so this should work. The only thing I note is that Debian has a patch for their 2.6.26 kernel, which I'm leaving out here...

Open a terminal and enter

Code:

sudo apt-get install build-essential linux-headers-$(uname -r) subversion
svn co svn://svn.berlios.de/fullstory/ar5523/trunk/ ar5523
wget http://verein.lst.de/~hch/ar5523.tgz
tar xf ar5523.tgz ar5523/uath-ar5523.bin --strip 1
cd ar5523
make
cd ..
sudo mkdir -p /lib/modules/$(uname -r)/updates/drivers/net/wireless
sudo cp ar5523/ar5523.ko /lib/modules/$(uname -r)/updates/drivers/net/wireless
sudo depmod -a -F /boot/System.map-$(uname -r) $(uname -r)
sudo mv uath-ar5523.bin /lib/firmware
sudo modprobe ar5523

Look at the output of

Code:

iwconfig

Ideally it will now show a wireless interface.

**reed9** · 03-31-2010

Well, Waterhead beat me to the punch while I was typing.

**waterhead** · 03-31-2010

Well, I just tried it on my 2.6.28 kernel, and the patch command fails with this error:

bash: debian/patches/kcompat-2.6.2*: ambiguous redirect

And, of course the make command then fails too.

Code:

:~/ar5523$ make
make -C /lib/modules/2.6.28-18-generic/build SUBDIRS=/home/paul/ar5523 modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.28-18-generic'
  CC [M]  /home/paul/ar5523/ar5523.o
/home/paul/ar5523/ar5523.c:132: error: array type has incomplete element type

Looking at the patch folder, there are patches for these kernels:

kcompat-2.6.25.patch
kcompat-2.6.26.patch
kcompat-2.6.32.patch

It is possible that you need one of those three kernel versions. Since you have 2.6.31, that isn't listed either. But you can try

**waterhead** · 03-31-2010

Originally Posted by reed9

Well, Waterhead beat me to the punch while I was typing.

AH! The power of Google!

Maybe you can try to build the driver, and see how it goes.

Thread Tools

Display

LAN Adapter will not work--tried ndiswrapper and Wine

Posting Permissions