I’ve got an old Compaq Armada E500 laptop (850mhz PIII, 512mb RAM, 30GB HD) that I’ve been running OpenSUSE 11.1 w/Gnome desktop. My wireless adapter (Linksys Wireless-G, model WPC54G ver. 2 w/acx-111 chipset) worked well with this setup, but now that I’ve upgraded to OpenSUSE 11.2 w/KDE, I’ve got to start all over. I tried doing what I did before, which was to copy the firmware file into /lib/firmware/ but no dice. Any suggestions?
On 12/18/2009 06:06 PM, etpowell3 wrote:
>
> I’ve got an old Compaq Armada E500 laptop (850mhz PIII, 512mb RAM, 30GB
> HD) that I’ve been running OpenSUSE 11.1 w/Gnome desktop. My wireless
> adapter (Linksys Wireless-G, model WPC54G ver. 2 w/acx-111 chipset)
> worked well with this setup, but now that I’ve upgraded to OpenSUSE 11.2
> w/KDE, I’ve got to start all over. I tried doing what I did before,
> which was to copy the firmware file into /lib/firmware/ but no dice. Any
> suggestions?
Post the output of ‘/usr/sbin/iwconfig’. If it shows that you are
associated and authenticated (also shown in dmesg), then you have
either the routing or DNS bugs - these are well known and would be
found by searching the forum.
If you are associated, please look at the output of ‘/sbin/route -n’.
If you do not see a line with flags UG set, then the problem is
routing. To tell you what routing commands you should use, I need to
know the name of your wireless device and the address of your router.
usr/sbin/iwconfig output reads: lo no wireless extensions
eth0 no wireless extensions
Sounds like I need some wireless extensions,
On 12/18/2009 08:46 PM, etpowell3 wrote:
>
> usr/sbin/iwconfig output reads: lo no wireless extensions
> eth0 no wireless extensions
>
> Sounds like I need some wireless extensions,
Look at the output of the dmesg command to see why your wireless
driver is not loading.
I took a look at dmesg, but didn’t see anything obvious.Here’s some stuff that may or may not be relevant:
0.766949] pci 0000:00:09.0: Firmware left e100 interrupts enabled; disabling
11.772863] maestro_radio: probe of 0000:00:08.0 failed with error -5
3 12.324177] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
12.324258] pci 0000:02:00.0: reg 10 32bit mmio: [0x000000-0x001fff]
12.324275] pci 0000:02:00.0: reg 14 32bit mmio: [0x000000-0x01ffff]
12.324347] pci 0000:02:00.0: supports D1 D2
12.324356] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot
12.324369] pci 0000:02:00.0: PME# disabled
12.594972] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: excluding 0x100-0x107
12.595865] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: clean.
12.597503] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.
12.598131] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean.
12.599262] pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.
12.603515] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x100-0x107
12.604589] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
12.605043] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
12.605365] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
12.606274] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
12.676200] es1968: clocking to 48000
70.308074] eth0: no IPv6 routers present
On 12/19/2009 12:06 AM, etpowell3 wrote:
> I took a look at dmesg, but didn’t see anything obvious.Here’s some
> stuff that may or may not be relevant:
>
>
>
> 0.766949] pci 0000:00:09.0: Firmware left e100 interrupts enabled;
> disabling
>
>
>
> 11.772863] maestro_radio: probe of 0000:00:08.0 failed with error
> -5
This one looks bad. Please post the output of ‘/sbin/lspci -nn’. Is
the device on bus 0000:00:08.0 your wireless device?
Here’s the output. The device listed on the last line is my wireless adapter.
dwin@linux-dish:~> /sbin/lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 03)
00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 03)
00:04.0 CardBus bridge [0607]: Texas Instruments PCI1225 [104c:ac1c] (rev 01)
00:04.1 CardBus bridge [0607]: Texas Instruments PCI1225 [104c:ac1c] (rev 01)
00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02)
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
00:07.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01)
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03)
00:08.0 Multimedia audio controller [0401]: ESS Technology ES1978 Maestro 2E [125d:1978] (rev 10)
00:09.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 09)
00:09.1 Serial controller [0700]: Agere Systems LT WinModem [11c1:0445]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Rage Mobility P/M AGP 2x [1002:4c4d] (rev 64)
02:00.0 Network controller [0280]: Texas Instruments ACX 111 54Mbps Wireless Interface [104c:9066]
edwin@linux-dish:~>
On 12/19/2009 09:36 PM, etpowell3 wrote:
>
> Here’s the output. The device listed on the last line is my wireless
> adapter.
> 02:00.0 Network controller [0280]: Texas Instruments ACX 111 54Mbps
> Wireless Interface [104c:9066]
That device uses wl12xx as its driver. Does ‘lsmod | grep wl12’ show
any output? If so, the driver is loaded.
If the driver was already load, and it should have been, check for
firmware problems. What does ‘dmesg | grep firmware’ show?
Here’s the output of those two items:
edwin@linux-dish:~> lsmod | grep wl12
edwin@linux-dish:~> dmesg | grep firmware
58.017726] e100 0000:00:09.0: firmware: requesting e100/d101s_ucode.bin
edwin@linux-dish:~>
On 12/19/2009 10:16 PM, etpowell3 wrote:
>
> Here’s the output of those two items:
>
> edwin@linux-dish:~> lsmod | grep wl12
> edwin@linux-dish:~> dmesg | grep firmware
> 58.017726] e100 0000:00:09.0: firmware: requesting
> e100/d101s_ucode.bin
Your wireless driver is not loaded (nothing from the lsmod test). The
firmware request is from the driver for your modem, not the wifi.
I do not know why the driver is not loading. Please enter the commands
below:
sudo /sbin/modprobe -v wl12xx
/usr/sbin/iwconfig
and post any output.
Here’s the result of the modprobe:
insmod /lib/modules/2.6.31.5-0.1-default/kernel/lib/crc7.ko
insmod /lib/modules/2.6.31.5-0.1-default/kernel/net/rfkill/rfkill.ko
insmod /lib/modules/2.6.31.5-0.1-default/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/2.6.31.5-0.1-default/kernel/net/mac80211/mac80211.ko
insmod /lib/modules/2.6.31.5-0.1-default/kernel/drivers/net/wireless/wl12xx/wl12xx.ko
Here’s the result of the second part:
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
On 12/20/2009 12:46 PM, etpowell3 wrote:
>
> Here’s the result of the second part:
>
> /usr/sbin/iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
Were there any errors in dmesg after you modprobed the driver? For
whatever reason, the wireless interface was not created.
No errors. What I got was what I posted previously.
It looks like there’s firmware present but no driver.
On 12/20/2009 08:46 PM, etpowell3 wrote:
>
> No errors. What I got was what I posted previously.
>
> It looks like there’s firmware present but no driver.
Is this a Cardbus or PCMCIA device?
It’s a pcmcia card
Given the apparent lack of an installed driver, could this be a job for ndiswrapper? I’ve previously had some success using kndiswrapper, but it appears that hasn’t been updated for the latest version of OpenSUSE. I’ve never tried it from the command line.
WooHoo!!!
Ndiwapper did the trick! I’m now connecting wirelessly, just in time to travel for the holidays.
Thanks for all your help.
Okay, minor glitch in the system. When I started the computer up tonight, first time since I got the wireless working, it didn’t come up automatically as it had before the system upgrade. I had to go back into the terminal and modprobe ndiswrapper to activate wireless card, then restart the wireless, and futz around with the settings in the Network Manager before it finally came back up completely. Is there a way to configure things such that it will connect the network automatically at boot-up?