Intel 3945ABG Verbindungsprobleme

Einrichten des lokalen Netzes, Verbindung zu anderen Computern und Diensten.
Antworten
JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 31.05.2011 18:06:54

Hallo beisammen,

habe heute von lenny nach squeeze upgegradet. Alles funktioniert wieder - bis auf das WLAN. WLAN-Netzwe werden alle korrekt angezeigt, inklusive details:

Code: Alles auswählen

lavender:/etc/modprobe.d# iwlist scan
lo        Interface doesn't support scanning.

eth1      Interface doesn't support scanning.

eth2      Scan completed :
          Cell 01 - Address: 00:06:25:E5:C6:B9
                    Channel:8
                    Frequency:2.447 GHz (Channel 8)
                    Quality=61/70  Signal level=-49 dBm  
                    Encryption key:on
                    ESSID:"blueboxnet"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Mode:Master
                    Extra:tsf=00000015ae8fc126
                    Extra: Last beacon: 2492ms ago
                    IE: Unknown: 000A626C7565626F786E6574
                    IE: Unknown: 010482840B16
                    IE: Unknown: 030108
                    IE: Unknown: 0406000200000000
          Cell 02 - Address: 00:03:7F:FE:00:02
                    Channel:4
                    Frequency:2.427 GHz (Channel 4)
                    Quality=26/70  Signal level=-84 dBm  
                    Encryption key:on
                    ESSID:"LunaPark"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000011d25378188
                    Extra: Last beacon: 2772ms ago
                    IE: Unknown: 00084C756E615061726B
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 030104
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0104
                    IE: Unknown: 2F0104
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD060010180201F4
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
          Cell 03 - Address: 00:03:C9:7A:CB:F3
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=51/70  Signal level=-59 dBm  
                    Encryption key:on
                    ESSID:"pro-ap"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
                              24 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=0000038a4ce4018a
                    Extra: Last beacon: 2292ms ago
                    IE: Unknown: 000670726F2D6170
                    IE: Unknown: 010882848B962430486C
                    IE: Unknown: 03010B
                    IE: Unknown: 050400010000
                    IE: Unknown: 2A0100
                    IE: Unknown: 2F0100
                    IE: Unknown: 32040C121860
                    IE: Unknown: DD06001018010100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
          Cell 04 - Address: 00:C0:A8:D0:C9:8E
                    Channel:9
                    Frequency:2.452 GHz (Channel 9)
                    Quality=22/70  Signal level=-88 dBm  
                    Encryption key:on
                    ESSID:"WhiteBox"
                    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
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=000005bee64fb181
                    Extra: Last beacon: 8732ms ago
                    IE: Unknown: 00085768697465426F78
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 030109
                    IE: Unknown: 050402040000
                    IE: Unknown: 2A0100
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: 32043048606C
                    IE: Unknown: DD270050F204104A000110104400010210470010000102030405060708090A0B0C0D0E0F103C000101


Aber wenn ich mich verbinden will, bekomme ich in dmesg nur das hier zu sehen:

Code: Alles auswählen

[  239.395242] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
[  239.592035] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
[  239.793801] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
[  239.992034] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
[  260.393679] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
[  260.592045] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
[  260.792035] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
[  260.992037] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
[  273.235997] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
[  273.308316] eth2: direct probe responded
[  273.308322] eth2: authenticate with AP 00:03:c9:7a:cb:f3 (try 1)
[  273.508039] eth2: authenticate with AP 00:03:c9:7a:cb:f3 (try 2)
[  273.708045] eth2: authenticate with AP 00:03:c9:7a:cb:f3 (try 3)
[  273.829460] eth2: authenticated
[  273.829596] eth2: associate with AP 00:03:c9:7a:cb:f3 (try 1)
[  274.033306] eth2: associate with AP 00:03:c9:7a:cb:f3 (try 2)
[  274.234186] eth2: associate with AP 00:03:c9:7a:cb:f3 (try 3)
[  274.432056] eth2: association with AP 00:03:c9:7a:cb:f3 timed out
Das hier sagt lsmod:

Code: Alles auswählen

lavender:/etc/modprobe.d# lsmod |grep wl
iwl3945                45764  0 
iwlcore                66986  1 iwl3945
mac80211              122866  2 iwl3945,iwlcore
cfg80211               86977  3 iwl3945,iwlcore,mac80211
led_class               1757  3 iwl3945,iwlcore,sdhci
Hier meine Karte bei lspci:

Code: Alles auswählen

0b:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
Meine aktuelle iwconfig nach einem Verbindungsversuch:

Code: Alles auswählen

lavender:/etc/modprobe.d# iwconfig
lo        no wireless extensions.

eth1      no wireless extensions.

eth2      IEEE 802.11abg  ESSID:"pro-ap"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
pan0      no wireless extensions.
Kann mir da jemand weiterhelfen? hat da jemand ein ähnliches Problem?

Felis
Beiträge: 398
Registriert: 14.04.2006 17:00:13

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von Felis » 31.05.2011 18:47:55

Ins Blaue getippt: Was steht in der /etc/network/interfaces. Im Zweifel mal nur mit diesem Eintrag probieren

Code: Alles auswählen

auto lo
iface lo inet loopback
:

JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 31.05.2011 20:29:57

Habe nur das hier drinnen:

Code: Alles auswählen

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
Aber ich habe in meinem Syslog gerade folgendes gefunden:

Code: Alles auswählen

May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) starting connection 'pro-ap' 
May 31 20:24:41 lavender NetworkManager[2402]: <info> (eth2): device state change: 3 -> 4 (reason 0) 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started... 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete. 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting... 
May 31 20:24:41 lavender NetworkManager[2402]: <info> (eth2): device state change: 4 -> 5 (reason 0) 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2/wireless): access point 'pro-ap' has security, but secrets are required. 
May 31 20:24:41 lavender NetworkManager[2402]: <info> (eth2): device state change: 5 -> 6 (reason 0) 
May 31 20:24:41 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete. 
May 31 20:24:42 lavender NetworkManager[2402]: <warn> Failed to update connection secrets: 1 802-1x 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started... 
May 31 20:24:42 lavender NetworkManager[2402]: <info> (eth2): device state change: 6 -> 4 (reason 0) 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete. 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting... 
May 31 20:24:42 lavender NetworkManager[2402]: <info> (eth2): device state change: 4 -> 5 (reason 0) 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2/wireless): connection 'pro-ap' has security, and secrets exist.  No new secrets needed. 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Config: added 'ssid' value 'pro-ap' 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Config: added 'scan_ssid' value '1' 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Config: added 'key_mgmt' value 'WPA-PSK' 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Config: added 'psk' value '<omitted>' 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete. 
May 31 20:24:42 lavender NetworkManager[2402]: <info> Config: set interface ap_scan to 1 
May 31 20:24:42 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  inactive -> scanning 
May 31 20:24:45 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:24:45 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:24:45 lavender kernel: [ 6831.104743] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:24:45 lavender kernel: [ 6831.304039] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:24:45 lavender kernel: [ 6831.504045] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:24:45 lavender kernel: [ 6831.704027] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:24:55 lavender wpa_supplicant[2451]: Authentication with 00:03:c9:7a:cb:f3 timed out.
May 31 20:24:55 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:24:55 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:24:57 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:24:57 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:24:57 lavender kernel: [ 6843.981390] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:24:58 lavender kernel: [ 6844.180030] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:24:58 lavender kernel: [ 6844.380039] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:24:58 lavender kernel: [ 6844.580869] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:25:07 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): association took too long. 
May 31 20:25:07 lavender NetworkManager[2402]: <info> (eth2): device state change: 5 -> 6 (reason 0) 
May 31 20:25:07 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): asking for new secrets 
May 31 20:25:07 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:25:07 lavender wpa_supplicant[2451]: Authentication with 00:00:00:00:00:00 timed out.
May 31 20:25:10 lavender NetworkManager[2402]: <warn> Failed to update connection secrets: 1 802-1x 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started... 
May 31 20:25:10 lavender NetworkManager[2402]: <info> (eth2): device state change: 6 -> 4 (reason 0) 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete. 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting... 
May 31 20:25:10 lavender NetworkManager[2402]: <info> (eth2): device state change: 4 -> 5 (reason 0) 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2/wireless): connection 'pro-ap' has security, and secrets exist.  No new secrets needed. 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Config: added 'ssid' value 'pro-ap' 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Config: added 'scan_ssid' value '1' 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Config: added 'key_mgmt' value 'WPA-PSK' 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Config: added 'psk' value '<omitted>' 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete. 
May 31 20:25:10 lavender NetworkManager[2402]: <info> Config: set interface ap_scan to 1 
May 31 20:25:10 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:25:13 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:25:13 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:25:13 lavender kernel: [ 6859.341481] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:25:13 lavender kernel: [ 6859.540116] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:25:13 lavender kernel: [ 6859.740058] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:25:13 lavender kernel: [ 6859.941290] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:25:23 lavender wpa_supplicant[2451]: Authentication with 00:03:c9:7a:cb:f3 timed out.
May 31 20:25:23 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:25:23 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:25:26 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:25:26 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:25:26 lavender kernel: [ 6872.213485] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:25:26 lavender kernel: [ 6872.412427] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:25:26 lavender kernel: [ 6872.612210] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:25:26 lavender kernel: [ 6872.812080] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:25:36 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): association took too long. 
May 31 20:25:36 lavender NetworkManager[2402]: <info> (eth2): device state change: 5 -> 6 (reason 0) 
May 31 20:25:36 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): asking for new secrets 
May 31 20:25:36 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:25:36 lavender wpa_supplicant[2451]: Authentication with 00:00:00:00:00:00 timed out.
May 31 20:25:49 lavender NetworkManager[2402]: <warn> Failed to update connection secrets: 1 802-1x 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started... 
May 31 20:25:49 lavender NetworkManager[2402]: <info> (eth2): device state change: 6 -> 4 (reason 0) 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete. 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting... 
May 31 20:25:49 lavender NetworkManager[2402]: <info> (eth2): device state change: 4 -> 5 (reason 0) 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2/wireless): connection 'pro-ap' has security, and secrets exist.  No new secrets needed. 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Config: added 'ssid' value 'pro-ap' 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Config: added 'scan_ssid' value '1' 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Config: added 'key_mgmt' value 'WPA-PSK' 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Config: added 'psk' value '<omitted>' 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete. 
May 31 20:25:49 lavender NetworkManager[2402]: <info> Config: set interface ap_scan to 1 
May 31 20:25:49 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:25:52 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:25:52 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:25:52 lavender kernel: [ 6898.572473] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:25:52 lavender kernel: [ 6898.773548] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:25:52 lavender kernel: [ 6898.973961] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:25:53 lavender kernel: [ 6899.172031] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:26:02 lavender wpa_supplicant[2451]: Authentication with 00:03:c9:7a:cb:f3 timed out.
May 31 20:26:02 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:26:02 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:26:05 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:26:05 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:26:05 lavender kernel: [ 6911.442946] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:26:05 lavender kernel: [ 6911.640265] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:26:05 lavender kernel: [ 6911.840656] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:26:06 lavender kernel: [ 6912.040033] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:26:14 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): association took too long. 
May 31 20:26:14 lavender NetworkManager[2402]: <info> (eth2): device state change: 5 -> 6 (reason 0) 
May 31 20:26:14 lavender NetworkManager[2402]: <warn> Activation (eth2/wireless): asking for new secrets 
May 31 20:26:15 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:26:15 lavender wpa_supplicant[2451]: Authentication with 00:00:00:00:00:00 timed out.
May 31 20:26:19 lavender NetworkManager[2402]: <warn> Failed to update connection secrets: 1 802-1x 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled... 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started... 
May 31 20:26:19 lavender NetworkManager[2402]: <info> (eth2): device state change: 6 -> 4 (reason 0) 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled... 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete. 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting... 
May 31 20:26:19 lavender NetworkManager[2402]: <info> (eth2): device state change: 4 -> 5 (reason 0) 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2/wireless): connection 'pro-ap' has security, and secrets exist.  No new secrets needed. 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Config: added 'ssid' value 'pro-ap' 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Config: added 'scan_ssid' value '1' 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Config: added 'key_mgmt' value 'WPA-PSK' 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Config: added 'psk' value '<omitted>' 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete. 
May 31 20:26:19 lavender NetworkManager[2402]: <info> Config: set interface ap_scan to 1 
May 31 20:26:19 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:26:22 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:26:22 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:26:22 lavender kernel: [ 6928.035228] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:26:22 lavender kernel: [ 6928.232043] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:26:22 lavender kernel: [ 6928.432032] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:26:22 lavender kernel: [ 6928.632035] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out
May 31 20:26:32 lavender wpa_supplicant[2451]: Authentication with 00:03:c9:7a:cb:f3 timed out.
May 31 20:26:32 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  associating -> disconnected 
May 31 20:26:32 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  disconnected -> scanning 
May 31 20:26:34 lavender wpa_supplicant[2451]: Trying to associate with 00:03:c9:7a:cb:f3 (SSID='pro-ap' freq=2462 MHz)
May 31 20:26:34 lavender NetworkManager[2402]: <info> (eth2): supplicant connection state:  scanning -> associating 
May 31 20:26:34 lavender kernel: [ 6940.918995] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 1)
May 31 20:26:35 lavender kernel: [ 6941.116155] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 2)
May 31 20:26:35 lavender kernel: [ 6941.316176] eth2: direct probe to AP 00:03:c9:7a:cb:f3 (try 3)
May 31 20:26:35 lavender kernel: [ 6941.516134] eth2: direct probe to AP 00:03:c9:7a:cb:f3 timed out

Felis
Beiträge: 398
Registriert: 14.04.2006 17:00:13

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von Felis » 31.05.2011 21:32:25

Ich bin ja kein Experte, allerdings haben wir auch einen Dell mit 3945er Wlan mit Lenny. Dort ist noch das Paket firmware-iwlwifi installiert. Irgendwo habe ich zwar gelesen, dass das bei Squeeze nicht mehr benötigt werden soll, allerdings sehe ich gerade, dass es sehr wohl noch installierbar ist. Vielleicht versuchst es mal.

JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 31.05.2011 22:26:41

Dieses Paket ist bereits installiert und aktuell...

Felis
Beiträge: 398
Registriert: 14.04.2006 17:00:13

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von Felis » 31.05.2011 22:33:25

Welches Tool benützt du für die Verbindung?

JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 31.05.2011 22:42:54

Den NetworkManager mit KDE-Frontend...

Felis
Beiträge: 398
Registriert: 14.04.2006 17:00:13

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von Felis » 31.05.2011 22:52:10

Vielleicht ginge es mit einem anderen besser? Ich würde mal wicd testen. Fürs nm-applet des network-manager-gnome dürftest vmtl. sehr viel installieren müssen. Für wicd darf allerdings wirklich nicht mehr in der "interfaces" stehen, als was ich oben gepostet habe.

JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 31.05.2011 23:16:35

Ich habe Wicd gerade ausprobiert, der zeigt mir nur meine LAN-Verbindung an, und mein Radio Killswitch funktioniert nicht mehr, mit welchem ich die WLAN-Karte einschalten könnte (Ist eine Tastenkombination, DELL Inspiron 6400n). Und der KDE Manager wäre mir schon am liebsten. Falls es doch eine Möglichkeit mit Wicd gibt bin ich natürlich nicht abgeneigt, hauptsache es funktioniert.
noch was interessantes aus dem syslog beim Verbinden:

Code: Alles auswählen

May 31 23:11:01 lavender NetworkManager[3432]: <warn> Activation (eth2/wireless): association took too long, failing activation. 

Felis
Beiträge: 398
Registriert: 14.04.2006 17:00:13

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von Felis » 31.05.2011 23:25:34

Scheint nur zu sagen, dass die Anmeldung zu lange gedauert hat. Sorry dass ich drauf rumreite, aber hast die beiden letzten Zeilen aus der "interfaces" geloescht oder auskommentiert, und hast im wicd unter "preferences" korrekt eingetragen? Sonst muss ich leider passen. :)
Warum Fn+F2 plötzlich nicht mehr funktionieren kann ich nicht erklären. Ich schreibe auch gerade vom Dell Inspiron 6400. ;)

JayL
Beiträge: 6
Registriert: 31.03.2007 23:13:10
Wohnort: Bavaria // DE
Kontaktdaten:

Re: Intel 3945ABG Verbindungsprobleme

Beitrag von JayL » 01.06.2011 07:16:18

Du reitest zurecht drauf rum, aber da ist wirklich alles auskommentiert. Habs auch testweise ganz rausgelöscht, das Auskommentierte. Hat auch keinen Erfolg gebracht. Irgendwo habe ich gelesen, dass der Treiber dazu tendiert, den falschen Antennenanschluss anzusteuern, an dem garkeine Antenne sitzt. Jetzt habe ich testweise mal in die /etc/modprobe.d/modprobe.conf einen Eintrag mit "option iwl3945 antenna=1" oder so ähnlich (bin gerade nicht daheim) angelegt, aber das bringt auch nichts. Jetzt habe ich das hier ausm Wiki raus:

http://wiki.debian.org/iwlwifi#Squeeze

Ich denke, ich werde, wenn ich wieder zu Hause bin, mal das Troubleshooting ausprobieren und das Ganze ohne den Network Manager probieren. Mal sehen obs was bringt.

Also bisher kann ich das Upgrade auf Squeeze nicht empfehlen. Auch mein UMTS-Stick funktioniert nicht mehr... aber das wär ein anderes Topic.

Antworten