I read the stickies and have been searching this forum, but haven’t seen this one yet. If I’ve missed it, it’s not for lack of trying.
PC Hardware: Older Compaq Armada E500 laptop, with PCMCIA 802.11b adapter from Cisco. I think it’s an Air-PCM350, but the lable is kinda worn off and hard to read.
Router is a Linksys WRT54GS.
I just installed OpenSUSE 11.1 today on this machine. Fresh install, so nothing left hanging around from a previous setup or anything. Using Gnome for the desktop. Wireless driver is airo().
Neither side of this supports WAP. So, I have SSID broadcast disabled, using WEP128 for security. (No, it’s not really all that secure, I know. I’ll deal with that later.)
If I have the SSID broadcast turned on at the router, NetworkManager works fine. If I turn off SSID broadcast, I can’t get NetworkManager to establish a connection. It just keeps prompting me for the WEP key.
I know the WEP key is right, as I’m looking at the router config via my desktop machine. And, it works ok if SSID broadcast is turned on.
It looks like NetworkManager is supposed to work, but here it doesn’t seem to. Other than the obvious solutions (enable SSID broadcast, or don’t use NetworkManager), any ideas on what to do here?
Open the wireless adapter config file (found in /etc/sysconfig/network) and add (or edit) this line:
WIRELESS_AP_SCANMODE=‘2’
The config file name will start with ifcfg- and the next part of the file name will identify the wireless adapter. (It should be fairly obvious)
except that there’s one problem with this advice. There is no such file there to edit. There is an ifcfg-eth0 for the wired connection, but no ifcfg-* for the Cisco wireless adapter.
00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
Subsystem: Compaq Computer Corporation Armada M700/E500
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at 3000 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: ES1968 (ESS Maestro)
Kernel modules: snd-es1968, radio-maestro
00:09.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 09)
Subsystem: Intel Corporation EtherExpress PRO/100+ MiniPCI
Flags: bus master, medium devsel, latency 66, IRQ 11
Memory at 41280000 (32-bit, non-prefetchable) [size=4]
I/O ports at 3440 [size=64]
Memory at 41200000 (32-bit, non-prefetchable) [size=128]
[virtual] Expansion ROM at 41500000 [disabled] [size=1]
Capabilities: [dc] Power Management version 2
Kernel driver in use: e100
Kernel modules: e100, eepro100
00:09.1 Serial controller: Agere Systems LT WinModem (prog-if 00 [8250])
Subsystem: Intel Corporation PRO/100+ MiniPCI on Armada E500
Flags: medium devsel, IRQ 11
I/O ports at 3430 [size=8]
Memory at 41300000 (32-bit, non-prefetchable) [size=4]
Capabilities: [dc] Power Management version 2
Kernel driver in use: serial
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA controller])
Subsystem: Compaq Computer Corporation Armada E500
Flags: bus master, stepping, medium devsel, latency 66, IRQ 11
Memory at 40000000 (32-bit, non-prefetchable) [size=16]
I/O ports at 2000 [size=256]
Memory at 41000000 (32-bit, non-prefetchable) [size=4]
[virtual] Expansion ROM at 41400000 [disabled] [size=128]
Capabilities: [50] AGP version 1.0
Capabilities: [5c] Power Management version 1
Kernel modules: atyfb[/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size][/size]
and just loops back to this when “Connect” is selected. This is true whether I allow it to try to auto-connect, or if I select “connect to hidden network” from Network Manager.
The file opens in Gedit and around the line 353 you’ll find the instruction “stop)” (or do a find for “stop)” (without quotes)). Below this instruction you should add these two instructions:
ifconfig wlan0 down
ifconfig eth0 down
So, the section of the file should look like this after editing (don’t delete/change anything after this section!):
stop)
ifconfig wlan0 down
ifconfig eth0 down
EXITSTATUS=0
Best fix:
Don’t release buggy software. Hopefully they push an update via update manager.
As it seems, the problem is with the Network Manager.
This is a possible solution for Ubuntu, but i can’t find the file /etc/init.d/alsa-utils…
If anyone that understands a little more than i do, please help.