What does it take to get this wireless card working in Suse 11?
It is detected but shows not connected.
- Ski K2 wrote, On 07/30/2008 03:16 AM:
> What does it take to get this wireless card working in Suse 11?
>
> It is detected but shows not connected.
>
>
Does it display WLAN networks at all?
If not, try this:
As root, touch /etc/modprobe.d/iwl3945. Edit the file and add
alias wlan0 iwl3945
options iwl3945 disable_hw_scan=1
then reboot.
HTH
Uwe
Thanks Uwe but still no joy.
In Gnome the network manager Wireless is still greyed out.
In Yast the card shows not connected.
Acer TravelMate 4220
???
- Ski K2 wrote, On 07/30/2008 03:36 PM:
> Thank Uwe but still no joy.
>
> In Gnome the network manager Wireless is still greyed out.
>
> In Yast the card shows not connected.
>
> Acer TravelMate 4220
Erm, hardware switch to activate the card?
Uwe
Sorry but I’m not sure I understand.
I have toggled the physical switch on the laptop with no change. No led.
???
Perhaps this helps?
linux-2j1c:~ # hwinfo --wlan
05: PCI 200.0: 0282 WLAN controller
[Created at pci.310]
UDI: /org/freedesktop/Hal/devices/pci_8086_4222
Unique ID: y9sn.QcgIbfETkb6
Parent ID: z8Q3.ZbAWgKMCoE3
SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: “Intel PRO/Wireless 3945ABG Network Connection”
Vendor: pci 0x8086 “Intel Corporation”
Device: pci 0x4222 “PRO/Wireless 3945ABG Network Connection”
SubVendor: pci 0x8086 “Intel Corporation”
SubDevice: pci 0x1000
Revision: 0x02
Driver: “iwl3945”
Driver Modules: “iwl3945”
Device File: wlan0
Features: WLAN
Memory Range: 0x54000000-0x54000fff (rw,non-prefetchable)
IRQ: 16 (no events)
HW Address: 00:13:02:86:f1:65
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.745 5.765 5.785 5.805 5.825
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: “pci:v00008086d00004222sv00008086sd00001000bc02sc80i00”
Driver Info #0:
Driver Status: iwl3945 is active
Driver Activation Cmd: “modprobe iwl3945”
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (PCI bridge)
Perhaps the Gnome Keyring is blocking it.
In Yast I edited the config again and tried the Hotplug option.
Clicked finish and got a warning box about not being able to connect to skynet repo.
Clicked skip several times and got Keyring prompt.
Entered the Keyring password and BOOM got the wifi connection.
???
Rebooted.
This time when Gnome desktop loads I get the Keyring password prompt.
Enter Keyring password and desktop loads and wifi connects 
It seems Keyring blocked the wifi card until I did something that triggered the Keyring prompt.
Seems to be working OK now:-)
Ski K2 schrieb:
> Perhaps this helps?
>
> linux-2j1c:~ # hwinfo --wlan
…]
> Driver Status: iwl3945 is active
> Driver Activation Cmd: “modprobe iwl3945”
> Config Status: cfg=no, avail=yes, need=no, active=unknown
What do the commands “iwconfig” and “iwlist scan” say?
–
Tilman Schmidt t.schmidt@phoenixsoftware.de
Phoenix Software GmbH www.phoenixsoftware.de
Adolf-Hombitzer-Str. 12 Amtsgericht Bonn HRB 2934
53227 Bonn, Germany Geschäftsführer: W. Grießl
Now that it’s connected, bear in mind:
linux-2j1c:~ # iwlist
Usage: iwlist [interface] scanning [essid NNN] [last]
[interface] frequency
[interface] channel
[interface] bitrate
[interface] rate
[interface] encryption
[interface] keys
[interface] power
[interface] txpower
[interface] retry
[interface] ap
[interface] accesspoints
[interface] peers
[interface] event
[interface] auth
[interface] wpakeys
[interface] genie
[interface] modulation
linux-2j1c:~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:“tsgwifi”
Mode:Managed Frequency:2.412 GHz Access Point: 00:1E:58:F3:22:AB
Bit Rate=54 Mb/s Tx-Power=17 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:4E1D-4F3F-1BA2-B76F-4E7F-97F2-77B3-C155-AAFF-E8FA-E9D1-AC80-A841-BA92-B000-9F92 [3]
Link Quality=79/100 Signal level=-55 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
linux-2j1c:~ # iwlist scan
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wmaster0 Interface doesn’t support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:1E:58:F3:22:AB
ESSID:“tsgwifi”
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=78/100 Signal level=-56 dBm Noise level=-95 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000010ac3060df
Ski K2 schrieb:
> Now that it’s connected, bear in mind:
…]
Ah, so your problem is solved. Glad to hear that.
HAND
T.
For now it seems.
Thanks very much