View Full Version : [ubuntu] hardy wireless network unclaimed

January 4th, 2009, 12:41 AM
Somebody please give me a hand with my wireless connection

mng@mng-laptop:~$ sudo lshw -C network
description: Ethernet interface
product: RTL8101E PCI Express Fast Ethernet controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:02:00.0
logical name: eth0
version: 02
serial: 00:1e:33:45:ba:c3
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip= latency=0 link=yes module=r8169 multicast=yes port=twisted pair speed=100MB/s
*-network UNCLAIMED
description: Network controller
product: Atheros Communications Inc.
vendor: Atheros Communications Inc.
physical id: 0
bus info: pci@0000:03:00.0
version: 01
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list
configuration: latency=0

mng@mng-laptop:~$ dmesg | grep -e ath -e rror
[ 17.841762] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
[ 22.488659] usb 2-2: device not accepting address 2, error -71

mng@mng-laptop:~$ sudo iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

mng@mng-laptop:~$ lspci -v | grep subordinate
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Bus: primary=00, secondary=08, subordinate=09, sec-latency=0
Bus: primary=00, secondary=06, subordinate=06, sec-latency=32

mng@mng-laptop:/etc/modprobe.d$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

mng@mng-laptop:~$ uname -r

January 4th, 2009, 01:25 AM
it looks like it doesn't have a driver
do you know whether you have madwifi or ndiswrapper installed (modprobe -l)?
if one is, you can start it with modprobe

January 4th, 2009, 01:32 AM
have a look here


January 4th, 2009, 04:36 AM
Thanks for the responses.

There is some madwifi around like this:

mng@mng-laptop:~$ modprobe madwifi
FATAL: Module madwifi not found.

I didn't realize madwifi was a driver. I thought only ath9k was. I will see if synaptic can find it.
Synaptic got the madwifi tools but no madwifi driver.
Is compat-wireless relevant?

January 4th, 2009, 11:13 AM
the madwifi driver is ath_pci

January 4th, 2009, 11:35 PM
I think it was compat-wireless that solved this. It seems to have left me with an ath9k.
Along the way I needed to add the linux-restricted repository

Now I have a whole lot of compat-wirelesses on my desktop like
.deb and

Can I get rid of them all, or should I keep the one I most likely used ? --

Thanks again.