AR5523 Wifi Dongle -AGAIN! (SOLVED, thanks)

[BJF]

muungwana: This might be one for you...

The dongle is an Encore Electronics ENUWI-SG 802.11G and drivers are net5523.inf and athfmwdl.inf Chipset is Atheros AR5523.

This is the next installment of a love/hate relationship with this item giving connectivity to my venerable old Compaq NX9005 laptop. Joble, bless him, got it working on 2007 after a heroic effort but that thread is now sadly no longer accessible for reference. There have been a few hiccups along the way to early this year, when I found a bargain "300m range Realtech USB dongle" to replace it with. I was seduced. It was cheap, and it was almost worth every penny. It is flakey, won't survive Hibernation, and has pot-metal contacts that need cleaning and jiggling at intervals. I want my old faithful-ish Atheros dongle back!

I plug the Atheros dongle in. No lights. I do lsusb as Root, and it is found, but returns no firmware.
I have the .inf files for both net5523 and athfmwdl, and ar5523.bin together with the other files culled from a Win driver suite.
I attempt a ndiswrapper install in Configure Your Computer> and find no device supported by the wrapper files.
Reading suggests that I need to install the firmware first. As Root, do.... What?? (command)

Muungwana, are you willing or able to walk me through getting this dongle going reliably again? Updates to ndiswrapper over the years may have removed support of course but can we try please? I'll be your friend!

 

[coffeetime]

We need more info.

- kernel
- lsusb
- .inf files  --> for winxp, win 7...?

Ndiswrapper commands
win2k/xp drivers

[muungwana]

We need more info.

- kernel
- lsusb
- .inf files  --> for winxp, win 7...?

Ndiswrapper commands
win2k/xp drivers

I agree with this, the more info you give, the easier it will be to look for where the problem is.

Open the terminal,log in as root,plug in the dongle and then run these commands and give their output.

uname -a

lsusb

tail -n 20 /var/log/syslog

[BJF]

Gentlemen: Thank you for replying. The results of my homework:

[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# uname -a
Linux localhost.localdomain 2.6.33.7-pclos6.bfs #1 SMP PREEMPT Thu Oct 21 22:42:28 CDT 2010 i686 i686 i386 GNU/Linux
[root@localhost mdm]# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0d8e:7802 Global Sun Technology, Inc. AR5523 (no firmware)
[root@localhost mdm]# tail -n 20 /var/log/syslog
Jul 25 19:56:58 localhost klogd: hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
Jul 25 19:56:58 localhost klogd: usb 1-2: USB disconnect, address 2
Jul 25 19:56:58 localhost dhclient: receive_packet failed on wlan1: Network is down
Jul 25 19:56:58 localhost avahi-daemon[2543]: Interface wlan1.IPv4 no longer relevant for mDNS.
Jul 25 19:56:58 localhost avahi-daemon[2543]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.2.4.
Jul 25 19:56:58 localhost avahi-daemon[2543]: Withdrawing address record for fe80::2e0:4cff:fe05:8629 on wlan1.
Jul 25 19:56:58 localhost avahi-daemon[2543]: Withdrawing address record for 192.168.2.4 on wlan1.
Jul 25 19:56:58 localhost avahi-daemon[2543]: Withdrawing workstation service for wlan1.
Jul 25 19:56:59 localhost ifplugd(wlan1)[13671]: Failed to detect plug status of wlan1
Jul 25 19:56:59 localhost ifplugd(wlan1)[13671]: Exiting.
Jul 25 19:57:00 localhost klogd: ndiswrapper: device wlan1 removed
Jul 25 19:57:02 localhost ntpd[3302]: sendto(203.99.129.34) (fd=22): Invalid argument
Jul 25 19:57:05 localhost klogd: usb 1-2: new full speed USB device using ohci_hcd and address 3
Jul 25 19:57:06 localhost klogd: usb 1-2: New USB device found, idVendor=0d8e, idProduct=7802
Jul 25 19:57:06 localhost klogd: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 19:57:06 localhost klogd: usb 1-2: Product: AR5523
Jul 25 19:57:06 localhost klogd: usb 1-2: Manufacturer: Atheros Communications Inc
Jul 25 19:57:06 localhost klogd: usb 1-2: SerialNumber: 1.0
Jul 25 19:57:17 localhost ntpd[3302]: sendto(203.99.128.34) (fd=22): Invalid argument
Jul 25 19:58:22 localhost ntpd[3302]: sendto(202.21.137.10) (fd=22): Invalid argument
[root@localhost mdm]#

Obviously the Realtek thing was unplugged and swapped for the Atheros dongle. Hence the first few lines.

What do you see in the runes, oh wise ones?

[muungwana]

Jul 25 19:57:05 localhost klogd: usb 1-2: new full speed USB device using ohci_hcd and address 3
Jul 25 19:57:06 localhost klogd: usb 1-2: New USB device found, idVendor=0d8e, idProduct=7802
Jul 25 19:57:06 localhost klogd: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 19:57:06 localhost klogd: usb 1-2: Product: AR5523
Jul 25 19:57:06 localhost klogd: usb 1-2: Manufacturer: Atheros Communications Inc
Jul 25 19:57:06 localhost klogd: usb 1-2: SerialNumber: 1.0

Do you see anything there?
The kernel sees the dongle but there is no kernel module registered that claims it so nothing happen.

What you need is a kernel module that tells the kernel it can handle the dangle.

I noticed you are running "2.6.33.7-pclos6.bfs" kernel, any reason why you are running such an old kernel?

[BJF]

The kernel is still there from the original but updated install. And a fear born of ignorance around updating kernels! But I do respond to education, so a two-line primer on the topic will see me updating as and when required.

And the module problem will explain why when I do modprobe it returns a Fatal, no module present error. What, please, do I do next?

(Edit) OBTW, OS is LXDE up to date two days ago.

Thanks.

[muungwana]

In a sense kernels are not "updated" since installing a new one does not replace the old one.The new one will simple be dumped in its own folder in "/lib/modules" and additional files will be added in "/boot", nothing gets replaced.

Installing a new kernel will not affect the installed kernel at all since each kernel exists in its own folder. Since the old kernel will not be replaced with the new one, you can always go back to the old one simply by choosing it at the start up list and, if you prefer it, set to default kernel and it will be auto selected at boot time.

Go to synaptic and install kernel version "3.2.18-pclos2.bfs", restart your computer, boot up using the new kernel.

Then open the terminal, log in as root, plug in the dangle, wait for 3 seconds and then run below command and post its output

tail -n 20 /var/log/syslog

[BJF]

New kernel installed, booted, all good.

Return from terminal:

[mdm@localhost ~]$ su root
Password:
[root@localhost mdm]# tail -n 20 /var/log/syslog
Jul 26 09:55:55 localhost laptop-mode: enabled,
Jul 26 09:55:56 localhost laptop-mode: active [unchanged]
Jul 26 09:55:58 localhost klogd: EXT4-fs (sda1): re-mounted. Opts: commit=600
Jul 26 09:56:00 localhost dbus[7385]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Jul 26 09:56:02 localhost blueman-mechanism: Starting blueman-mechanism 
Jul 26 09:56:02 localhost dbus[7385]: [system] Successfully activated service 'org.blueman.Mechanism'
Jul 26 09:56:02 localhost blueman-mechanism: reload 0 0 
Jul 26 09:56:32 localhost blueman-mechanism: Exiting 
Jul 26 09:56:34 localhost ntpd_initres[8424]: host name not found: 0.nz.pool.ntp.org
Jul 26 09:56:34 localhost ntpd_initres[8424]: host name not found: 1.nz.pool.ntp.org
Jul 26 09:56:34 localhost ntpd_initres[8424]: host name not found: 2.nz.pool.ntp.org
Jul 26 09:56:56 localhost laptop-mode: Laptop mode
Jul 26 09:56:56 localhost laptop-mode: enabled,
Jul 26 09:56:56 localhost laptop-mode: active [unchanged]
Jul 26 09:56:57 localhost klogd: usb 1-2: new full-speed USB device number 2 using ohci_hcd
Jul 26 09:56:57 localhost klogd: usb 1-2: New USB device found, idVendor=0d8e, idProduct=7802
Jul 26 09:56:57 localhost klogd: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 09:56:57 localhost klogd: usb 1-2: Product: AR5523
Jul 26 09:56:57 localhost klogd: usb 1-2: Manufacturer: Atheros Communications Inc
Jul 26 09:56:57 localhost klogd: usb 1-2: SerialNumber: 1.0
[root@localhost mdm]#

 

[muungwana]

you can get the firmwawre at: http://wiki.debian.org/ar5523

from the terminal and as root, run

wget http://verein.lst.de/~hch/ar5523.tgz
tar xf ar5523.tgz ar5523/uath-ar5523.bin --strip 1
mv uath-ar5523.bin /lib/firmware

Try to redo the steps you already did that errored out for lack of firmware and see if they still error out.

The native driver from the card is on the page my first attempt at building it has failed

[BJF]

muungwana: I notice in the Debian link under supported devices that my dongle, identified by lsusb as 0d8e 7802, is a no-firmware device. lsusb agrees, seemingly. Do your observations verify this? I don't remember the firmware step in the Joble-v-2007 install to make it go.

[muungwana]

did you use ndiswrapper previously?

Lets try to use it from the terminal,  not through pcc.

open the terminal in the folder were "athfmwdl.inf" and "net5523.inf" files are located, log in as root and then run

ndiswrapper -i athfmwdl.inf
ndiswrapper -i net5523.inf

now run this command and post its output

ndiswrapper -l

then this one

modprobe ndiswrapper

if this are ok, then this one

iwconfig
plug in the dangle

[BJF]

Yes, using ndiswrapper.

[mdm@localhost win2kxp]$ su root

Password:

[root@localhost win2kxp]# ndiswrapper -i athfmwdl.inf

driver athfmwdl is already installed

[root@localhost win2kxp]# ndiswrapper -i net5523.inf

driver net5523 is already installed

[root@localhost win2kxp]# ndiswrapper -i

install/manage Windows drivers for ndiswrapper



usage: ndiswrapper OPTION

-i inffile       install driver described by 'inffile'

-a devid driver  use installed 'driver' for 'devid' (dangerous)

-r driver        remove 'driver'

-l               list installed drivers

-m               write configuration for modprobe

-ma              write module alias configuration for all devices

-mi              write module install configuration for all devices

-v               report version information



where 'devid' is either PCIID or USBID of the form XXXX:XXXX,

as reported by 'lspci -n' or 'lsusb' for the card

[root@localhost win2kxp]# ndiswrapper -l

airforceone : driver installed

airplus : driver installed

athfmwdl : driver installed

bcmwl5 : driver installed

bcmwl5a : driver installed

lstinds : driver installed

net5211 : driver installed

net5523 : driver installed

net8185 : driver installed

net8192cu : driver installed

netathw : invalid driver!

netr33x : driver installed

prismnic : driver installed

wlannic : driver installed

wlipnds : driver installed

[root@localhost win2kxp]# modprobe ndiswrapper

FATAL: Module ndiswrapper not found.

[root@localhost win2kxp]#

Didn't bother to plug the dongle in.

One thing that was noticeable though was that the laptop got into a tizzy and fanned hard and locked up when I plugged the ethernet in to send this. Had to hit the switch. The boot-up parade continuously shows a GPE Storm now, and the router is showing a red instead of green light for this connection even though it is working. It's unhappy!

[muungwana]

you have both of those windows drivers installed.

[root@mtz ink]# uname -a
Linux mtz 3.2.18-pclos2.bfs #1 SMP PREEMPT Thu May 24 04:44:50 CEST 2012 i686 i686 i386 GNU/Linux
[root@mtz ink]# locate ndiswrapper | grep /lib
/lib/modules/2.6.38.8-pclos3.bfs/kernel/3rdparty/ndiswrapper
/lib/modules/2.6.38.8-pclos3.bfs/kernel/3rdparty/ndiswrapper/ndiswrapper.ko.gz
/usr/lib/libDrakX/network/ndiswrapper.pm
[root@mtz ink]#

ndiswrapper kernel module seem to be missing in "3.2.18" kernel but is there in "2.6.38.8". This could be the cause of the problem.

Any kernel packager reading this thread? Any reason why "ndiswrapper" does not have a kernel module in "3.2.x" kernels.

[BJF]

I don't think 2.6.38.8 had it either.

And the module problem will explain why when I do modprobe it returns a Fatal, no module present error. What, please, do I do next?

...from my previous post.

Yep. Checked. Same result. Helps explain the erratic wifi going waaaaay  back?

[djohnston]

Any kernel packager reading this thread? Any reason why "ndiswrapper" does not have a kernel module in "3.2.x" kernels.

AS packaged the 3.2.x kernels. He's no longer here.