Permanent problems with intel wlan (iwl3945)

dcrabs · 2009-04-30 16:04:52

Hi
I've got an intel wireless card and have constant problems connecting like normal people. Just using netcfg2 or networkmanager is not possible. When I try connecting (after ifconfig wlan0 up) the iwl3945 driver goes up to 100% cpu load on one core.
So I thought I try in single steps on the console.
It is the following chip:

10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

I did these steps but most of the time it doesn't work:

#!/bin/sh
sudo rmmod iwl3945
sleep 2
sudo modprobe iwl3945
sleep 10
sudo ifconfig wlan0 up
sudo iwconfig wlan0 essid CampusWlan
sudo dhclient wlan0

Usually after ifconfig wlan0 up I get a strange error message on the console which doesn't show in the log files.

SIOCSIFFLAGS: Connection timed out

This is part of /var/log/errors.log from today:

Apr 30 17:21:22 farnsworth kernel: iwl3945: Microcode SW error detected.  Restarting 0x82000008.
Apr 30 17:21:22 farnsworth kernel: iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x0000 ser 0x0000004E
Apr 30 17:21:22 farnsworth kernel: iwl3945: Error setting new configuration (-5).
Apr 30 17:21:22 farnsworth kernel: iwl3945: Can't stop Rx DMA.
Apr 30 17:21:27 farnsworth dhclient: wmaster0: unknown hardware address type 801
Apr 30 17:21:29 farnsworth dhclient: wmaster0: unknown hardware address type 801
Apr 30 17:21:55 farnsworth kdm_greet[4755]: Cannot open default user face

/var/log/everything.log shows this sometimes:

pr 30 14:33:12 farnsworth kernel: iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
Apr 30 14:33:12 farnsworth kernel: iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
Apr 30 14:33:12 farnsworth kernel: iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode
Apr 30 14:33:12 farnsworth kernel: iwl3945 loaded firmware version 15.28.2.8
Apr 30 14:33:14 farnsworth kernel: iwl3945: Wait for START_ALIVE timeout after 2000ms.
Apr 30 14:33:14 farnsworth logger: ACPI group/action undefined: thermal_zone / TZ0
Apr 30 14:33:44 farnsworth kernel: usb 3-1: USB disconnect, address 2
Apr 30 14:33:45 farnsworth kernel: irq 10: nobody cared (try booting with the "irqpoll" option)
Apr 30 14:33:45 farnsworth kernel: Pid: 0, comm: swapper Not tainted 2.6.29-ARCH #1
Apr 30 14:33:45 farnsworth kernel: Call Trace:
Apr 30 14:33:45 farnsworth kernel: [<c016e604>] __report_bad_irq+0x24/0x90
Apr 30 14:33:45 farnsworth kernel: [<c016e7c7>] note_interrupt+0x157/0x1a0
Apr 30 14:33:45 farnsworth kernel: [<c016ef9b>] handle_level_irq+0xcb/0xf0
Apr 30 14:33:45 farnsworth kernel: [<c0106373>] do_IRQ+0x43/0x90
Apr 30 14:33:45 farnsworth kernel: [<c013531c>] irq_exit+0x3c/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0116dbb>] smp_apic_timer_interrupt+0x5b/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0104527>] common_interrupt+0x27/0x2c
Apr 30 14:33:45 farnsworth kernel: [<c035007b>] __mutex_lock_interruptible_slowpath+0x2b/0x320
Apr 30 14:33:45 farnsworth kernel: [<c016d8e0>] handle_IRQ_event+0x10/0x60
Apr 30 14:33:45 farnsworth kernel: [<c016ef48>] handle_level_irq+0x78/0xf0
Apr 30 14:33:45 farnsworth kernel: [<c0106373>] do_IRQ+0x43/0x90
Apr 30 14:33:45 farnsworth kernel: [<c013531c>] irq_exit+0x3c/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0116dbb>] smp_apic_timer_interrupt+0x5b/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0104527>] common_interrupt+0x27/0x2c
Apr 30 14:33:45 farnsworth kernel: [<c035007b>] __mutex_lock_interruptible_slowpath+0x2b/0x320
Apr 30 14:33:45 farnsworth kernel: [<c016d8e0>] handle_IRQ_event+0x10/0x60
Apr 30 14:33:45 farnsworth kernel: [<c016ef48>] handle_level_irq+0x78/0xf0
Apr 30 14:33:45 farnsworth kernel: [<c0106373>] do_IRQ+0x43/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0104527>] common_interrupt+0x27/0x2c
Apr 30 14:33:45 farnsworth kernel: [<c015007b>] clockevent_delta2ns+0x1b/0xf0
Apr 30 14:33:45 farnsworth kernel: [<c0351a2a>] _spin_unlock_irqrestore+0x1a/0x60
Apr 30 14:33:45 farnsworth kernel: [<c0150435>] tick_notify+0x1d5/0x3c0
Apr 30 14:33:45 farnsworth kernel: [<c0106378>] do_IRQ+0x48/0x90
Apr 30 14:33:45 farnsworth kernel: [<c0149056>] notifier_call_chain+0x36/0x70
Apr 30 14:33:45 farnsworth kernel: [<c0149147>] raw_notifier_call_chain+0x17/0x20
Apr 30 14:33:45 farnsworth kernel: [<c014fdbe>] clockevents_notify+0x1e/0x70
Apr 30 14:33:45 farnsworth kernel: [<f8ad3131>] acpi_idle_enter_bm+0x2f4/0x356 [processor]
Apr 30 14:33:45 farnsworth kernel: [<c02b1e8f>] cpuidle_idle_call+0x6f/0xc0
Apr 30 14:33:45 farnsworth kernel: [<c0102dc6>] cpu_idle+0x66/0xa0
Apr 30 14:33:45 farnsworth kernel: handlers:
Apr 30 14:33:45 farnsworth kernel: [<f8607880>] (usb_hcd_irq+0x0/0x80 [usbcore])
Apr 30 14:33:45 farnsworth kernel: [<f8607880>] (usb_hcd_irq+0x0/0x80 [usbcore])
Apr 30 14:33:45 farnsworth kernel: [<f8607880>] (usb_hcd_irq+0x0/0x80 [usbcore])
Apr 30 14:33:45 farnsworth kernel: [<f8607880>] (usb_hcd_irq+0x0/0x80 [usbcore])
Apr 30 14:33:45 farnsworth kernel: Disabling IRQ #10
Apr 30 14:34:58 farnsworth shutdown[4654]: shutting down for system reboot

I tried booting with "irqpoll" option but it doesn't change things.
The only way I can connect sometimes is when wlan is turned of by pressing the rfkill button, then removing iwl3945, removing tg3 and loading iwl3945 module again. Next is ifconfig wlan0 up, setting the essid with iwconfig and using dhclient to get an ip address. It is no fancy network, university network, my mac address is registered there so no wpa, wep or other keys whatsoever. And additionally I had to do this to /etc/rc.conf:

DAEMONS=(syslog-ng !hal !network !networkmanager @crond !avahi-daemon !kdm !gcaldaemon)
MOD_AUTOLOAD="yes"                                                                                                               
MODULES=(!yenta_socket tg3 !ipw3945 iwl3945 fuse acpi-cpufreq cpufreq_ondemand cpufreq_powersave coretemp)

Interfaces are all switched of with "!". And my boot options are:

i915.modeset=1 root=/dev/sda5 ro quiet nopat noapic enable_mttr_cleanup

Ucode is installed btw (core/iwlwifi-3945-ucode 15.28.2.8-1). There are some other threads but nothing that fits exactly.
One or two kernels ago I could switch it on and off and connect to whatever network I wanted. Any ideas on this?
Thanks, David

Last edited by dcrabs (2009-05-15 07:42:42)

zenlord · 2009-05-01 11:06:54

Looks like a driver or hardware problem. The only (simple) possible solution I van come up with is to reinstall the ucode?

Zl.

dcrabs · 2009-05-01 14:08:21

Hi,
I tried that once but it didn't help. I noticed, there is a ucode update on the intelliwireless website. I will try with an updated PKGBUILD.

dcrabs · 2009-05-07 12:10:38

With the new ucode things are a little bit better. No more 100% cpu load on one core.
This is from a log trying to connect to my university network.

iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
iwl3945 0000:10:00.0: irq 23 for MSI/MSI-X
iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 loaded firmware version 15.32.2.9
iwl3945: Radio disabled by HW RF Kill switch
iwl3945 0000:10:00.0: PCI INT A disabled
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
iwl3945 0000:10:00.0: irq 23 for MSI/MSI-X
iwl3945: Radio disabled by HW RF Kill switch
iwl3945 0000:10:00.0: PCI INT A disabled
tg3 0000:18:00.0: PCI INT A disabled
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2008 Intel Corporation
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: setting latency timer to 64
iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945: Detected Intel Wireless WiFi Link 3945ABG
wmaster0 (iwl3945): not using net_device_ops yet
phy1: Selected rate control algorithm 'iwl-3945-rs'
wlan0 (iwl3945): not using net_device_ops yet
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 loaded firmware version 15.32.2.9
iwl3945: Radio disabled by HW RF Kill switch
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
iwl3945: Radio disabled by HW RF Kill switch
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
iwl3945: Radio disabled by HW RF Kill switch
usb 3-1: new full speed USB device using uhci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
Bluetooth: Core ver 2.14
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.4
usbcore: registered new interface driver btusb
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
CE: hpet increasing min_delta_ns to 15000 nsec
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID b6:a9:0b:65:2e:40
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 92:4e:1c:bd:a7:f8
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
CE: hpet increasing min_delta_ns to 22500 nsec
wlan0: Selected IBSS BSSID b6:a9:0b:65:2e:40 based on configured SSID
wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 7e:c3:85:0d:00:4c
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 12:8f:8a:ea:1a:51
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 7e:94:e8:b7:a9:e0
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 3e:61:4d:83:96:44
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 56:0d:da:c7:de:3c
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Selected IBSS BSSID b6:a9:0b:65:2e:40 based on configured SSID
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID de:73:55:48:91:a0
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID a2:3d:fb:a2:8e:0f
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 1a:f4:32:37:5b:be
wlan0: disassociating by local choice (reason=3)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 7e:fc:15:e5:e2:b5
wlan0: disassociating by local choice (reason=3)
wlan0: deauthenticating by local choice (reason=3)
wlan0: Selected IBSS BSSID b6:a9:0b:65:2e:40 based on configured SSID
------------[ cut here ]------------
WARNING: at net/mac80211/main.c:161 ieee80211_if_config+0x140/0x170 [mac80211]()
Hardware name: HP Compaq 6710s (GB883EA#ABD)
Modules linked in: btusb bluetooth iwl3945 coretemp cpufreq_powersave cpufreq_ondemand snd_seq_oss snd_seq_midi_event acpi_cpufreq snd_seq freq_table snd_seq_device fuse snd_hda_codec_analog snd_pcm_oss snd_mixer_oss arc4 snd_hda_intel usbhid hid ecb fan snd_hda_codec snd_hwdep snd_pcm snd_timer snd uhci_hcd sg joydev soundcore video thermal rfkill ehci_hcd container output iTCO_wdt iTCO_vendor_support serio_raw mac80211 battery wmi button ac snd_page_alloc processor psmouse usbcore led_class evdev lib80211 cfg80211 ext4 jbd2 crc16 libphy rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod cdrom sd_mod ata_piix ahci libata scsi_mod i915 i2c_algo_bit drm i2c_core intel_agp agpgart [last unloaded: iwl3945]
Pid: 4725, comm: iwconfig Not tainted 2.6.29-ARCH #1
Call Trace:
 [<c012f807>] warn_slowpath+0x87/0xe0
 [<c0182b3d>] __alloc_pages_internal+0xbd/0x470
 [<c011ec65>] default_spin_lock_flags+0x5/0x10
 [<c01529d8>] debug_mutex_add_waiter+0x48/0x80
 [<c0350124>] __mutex_lock_slowpath+0x244/0x2d0
 [<c011ec65>] default_spin_lock_flags+0x5/0x10
 [<c035180e>] _spin_lock_irqsave+0x3e/0x60
 [<f8b2ca20>] ieee80211_if_config+0x140/0x170 [mac80211]
 [<f908549f>] iwl3945_mac_reset_tsf+0x9f/0x140 [iwl3945]
 [<f8b34592>] ieee80211_sta_join_ibss+0x72/0x440 [mac80211]
 [<c03519ea>] _spin_lock_bh+0x1a/0x20
 [<f8b3213f>] ieee80211_rx_bss_get+0x9f/0xb0 [mac80211]
 [<f8b34c11>] ieee80211_sta_find_ibss+0x2b1/0x4b0 [mac80211]
 [<f8b2e4d7>] ieee80211_ioctl_siwessid+0x87/0xe0 [mac80211]
 [<c033a548>] ioctl_standard_call+0x1a8/0x3a0
 [<c02c6bb5>] __dev_get_by_name+0x75/0x90
 [<c033a067>] wext_handle_ioctl+0x157/0x230
 [<f8b2e450>] ieee80211_ioctl_siwessid+0x0/0xe0 [mac80211]
 [<c02caed2>] dev_ioctl+0x492/0x560
 [<c0182285>] __pagevec_free+0x25/0x30
 [<c0185671>] release_pages+0x171/0x1c0
 [<c02b9620>] sock_ioctl+0x0/0x250
 [<c01b569b>] vfs_ioctl+0x2b/0x90
 [<c01b58ab>] do_vfs_ioctl+0x7b/0x5b0
 [<c019597e>] unmap_region+0x10e/0x130
 [<c01959de>] remove_vma+0x3e/0x60
 [<c0196978>] do_munmap+0x228/0x280
 [<c01b5e46>] sys_ioctl+0x66/0x70
 [<c0103ea3>] sysenter_do_call+0x12/0x2f
 [<c0350000>] __mutex_lock_slowpath+0x120/0x2d0
---[ end trace b84e9caf6afffbd1 ]---
------------[ cut here ]------------
WARNING: at net/mac80211/main.c:161 ieee80211_if_config+0x140/0x170 [mac80211]()
Hardware name: HP Compaq 6710s (GB883EA#ABD)
Modules linked in: btusb bluetooth iwl3945 coretemp cpufreq_powersave cpufreq_ondemand snd_seq_oss snd_seq_midi_event acpi_cpufreq snd_seq freq_table snd_seq_device fuse snd_hda_codec_analog snd_pcm_oss snd_mixer_oss arc4 snd_hda_intel usbhid hid ecb fan snd_hda_codec snd_hwdep snd_pcm snd_timer snd uhci_hcd sg joydev soundcore video thermal rfkill ehci_hcd container output iTCO_wdt iTCO_vendor_support serio_raw mac80211 battery wmi button ac snd_page_alloc processor psmouse usbcore led_class evdev lib80211 cfg80211 ext4 jbd2 crc16 libphy rtc_cmos rtc_core rtc_lib ext3 jbd mbcache sr_mod cdrom sd_mod ata_piix ahci libata scsi_mod i915 i2c_algo_bit drm i2c_core intel_agp agpgart [last unloaded: iwl3945]
Pid: 4725, comm: iwconfig Tainted: G        W  2.6.29-ARCH #1
Call Trace:
 [<c012f807>] warn_slowpath+0x87/0xe0
 [<c0182b3d>] __alloc_pages_internal+0xbd/0x470
 [<c011ec65>] default_spin_lock_flags+0x5/0x10
 [<c01529d8>] debug_mutex_add_waiter+0x48/0x80
 [<c0350124>] __mutex_lock_slowpath+0x244/0x2d0
 [<c011ec65>] default_spin_lock_flags+0x5/0x10
 [<c035180e>] _spin_lock_irqsave+0x3e/0x60
 [<f8b2ca20>] ieee80211_if_config+0x140/0x170 [mac80211]
 [<f8b34751>] ieee80211_sta_join_ibss+0x231/0x440 [mac80211]
 [<c03519ea>] _spin_lock_bh+0x1a/0x20
 [<f8b34c11>] ieee80211_sta_find_ibss+0x2b1/0x4b0 [mac80211]
 [<f8b2e4d7>] ieee80211_ioctl_siwessid+0x87/0xe0 [mac80211]
 [<c033a548>] ioctl_standard_call+0x1a8/0x3a0
 [<c02c6bb5>] __dev_get_by_name+0x75/0x90
 [<c033a067>] wext_handle_ioctl+0x157/0x230
 [<f8b2e450>] ieee80211_ioctl_siwessid+0x0/0xe0 [mac80211]
 [<c02caed2>] dev_ioctl+0x492/0x560
 [<c0182285>] __pagevec_free+0x25/0x30
 [<c0185671>] release_pages+0x171/0x1c0
 [<c02b9620>] sock_ioctl+0x0/0x250
 [<c01b569b>] vfs_ioctl+0x2b/0x90
 [<c01b58ab>] do_vfs_ioctl+0x7b/0x5b0
 [<c019597e>] unmap_region+0x10e/0x130
 [<c01959de>] remove_vma+0x3e/0x60
 [<c0196978>] do_munmap+0x228/0x280
 [<c01b5e46>] sys_ioctl+0x66/0x70
 [<c0103ea3>] sysenter_do_call+0x12/0x2f
 [<c0350000>] __mutex_lock_slowpath+0x120/0x2d0
---[ end trace b84e9caf6afffbd2 ]---
iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
Registered led device: iwl-phy1:radio
Registered led device: iwl-phy1:assoc
Registered led device: iwl-phy1:RX
Registered led device: iwl-phy1:TX
wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan0: Trigger new scan to find an IBSS to join
wlan0: Trigger new scan to find an IBSS to join
wlan0: Creating new IBSS network, BSSID 9e:2a:08:82:cc:08
wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan0: Selected IBSS BSSID b6:a9:0b:65:2e:40 based on configured SSID
wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan0: Selected IBSS BSSID 9e:2a:08:82:cc:08 based on configured SSID

So far I couldn't figure out the exact steps I have to do in order to connect. Sometimes it works but I often get timeouts.
But I don't understand why nobody has such a problem. Is it only me who has to remove the tg3 and reload iwl3945 module and do an ifconfig wlan0 up? I mean there is no point in using netcfg2 or networkmanager when I have to do it manually anyway.
As I said it is a bit better, scanning now works with networkmanager but connecting doesn't. It is not a fancy network, my MAC address is registereed and all I have to do is assigning the ESSID and use dhclient wlan0
In networkmanager I only have SSID and I guess that is the same as ESSID, than there is a BSSID (whatever that is), security is switched off as there is no key. To get an IP address I can chose betwen 4 things, manual, dhcp with manual dns, auto ip and dhcp. What is the difference between the last and second last?
I would really appreciate when someone can shed some light on all this.
Thanks, David

dcrabs · 2009-05-13 10:28:03

Just an other update. I still couldn't figure out why all this happens. The new firmware is slightly better. It was even possible to use netcfg but of course after reloading the module and manually enabling the device. Am I the only one who has problems with this?
And I noticed that booting with kill switch disabled (wireless on) directly results in 100%cpu load on one core.

dcrabs · 2009-05-15 07:45:32

Is there really nobody who has problems with this chip? Or are all problems different?
Maybe someone knows a wiki page or whatsoever with more information in one place. That would help me a lot.
Thanks

dcrabs · 2009-05-28 13:17:07

Seems like I am having a conversation with myself.
Anyway, after the latest firmware upgrade I usually get timeouts with dhcp. Could someone please post kernel command lines? Maybe that is the cause. Everything seems totally random.
Here are a couple of logs:

May 25 09:48:36 farnsworth dhclient: Internet Systems Consortium DHCP Client V3.0.6
May 25 09:48:36 farnsworth dhclient: Copyright 2004-2007 Internet Systems Consortium.
May 25 09:48:36 farnsworth dhclient: All rights reserved.
May 25 09:48:36 farnsworth dhclient: For info, please visit http://www.isc.org/sw/dhcp/
May 25 09:48:36 farnsworth dhclient:
May 25 09:48:36 farnsworth dhclient: wmaster0: unknown hardware address type 801
May 25 09:48:36 farnsworth kernel: iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
May 25 09:48:36 farnsworth kernel: iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
May 25 09:48:36 farnsworth kernel: iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode
May 25 09:48:36 farnsworth kernel: iwl3945 loaded firmware version 15.32.2.9
May 25 09:48:38 farnsworth kernel: iwl3945: Wait for START_ALIVE timeout after 2000ms.
May 25 09:48:38 farnsworth kernel: iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
May 25 09:48:38 farnsworth kernel: iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X

May 24 10:40:41 farnsworth kernel: phy1: Selected rate control algorithm 'iwl-3945-rs'
May 24 10:40:41 farnsworth kernel: wlan0 (iwl3945): not using net_device_ops yet      
May 24 10:40:41 farnsworth NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
May 24 10:40:41 farnsworth NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'iwl3945')  
May 24 10:40:41 farnsworth NetworkManager: <info>  (wlan0): exported as /org/freedesktop/Hal/devices/net_00_1b_77_26_9a_2b
May 24 10:40:44 farnsworth logger: ACPI action undefined: C238                                                            
May 24 10:40:45 farnsworth kernel: iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10         
May 24 10:40:45 farnsworth kernel: iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X                                             
May 24 10:40:45 farnsworth kernel: iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode                        
May 24 10:40:45 farnsworth NetworkManager: <info>  (wlan0): device state change: 1 -> 2                                   
May 24 10:40:45 farnsworth NetworkManager: <info>  (wlan0): bringing up device.                                           
May 24 10:40:45 farnsworth kernel: iwl3945 loaded firmware version 15.32.2.9                                              
May 24 10:40:45 farnsworth kernel: iwl3945: Microcode SW error detected.  Restarting 0x82000008.                          
May 24 10:40:45 farnsworth kernel: iwl3945: Error Reply type 0x00000005 cmd UNKNOWN (0x00) seq 0x0000 ser 0x00000074      
May 24 10:40:47 farnsworth kernel: iwl3945: Wait for START_ALIVE timeout after 2000ms.
May 24 10:40:47 farnsworth NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
May 24 10:40:47 farnsworth kernel: iwl3945 0000:10:00.0: PCI INT A -> Link[C12E] -> GSI 10 (level, low) -> IRQ 10
May 24 10:40:47 farnsworth kernel: iwl3945 0000:10:00.0: irq 22 for MSI/MSI-X
May 24 10:40:47 farnsworth NetworkManager: <info>  Wireless now enabled by radio killswitch
May 24 10:40:47 farnsworth NetworkManager: <info>  (wlan0): bringing up device.

May 24 11:13:26 farnsworth kernel: INFO: task iwl3945/1:4717 blocked for more than 480 seconds.                           
May 24 11:13:26 farnsworth kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.              
May 24 11:13:26 farnsworth kernel: iwl3945/1     D c2009900     0  4717      2                                            
May 24 11:13:26 farnsworth kernel: f6b13f30 00000046 2f7ec23f c2009900 f64c03d0 f64c03fc f6b13efc c01256de                
May 24 11:13:26 farnsworth kernel: 926a7a43 00000004 c0355f40 c2009900 00c84113 00000000 ffffeb3b 01b58000                
May 24 11:13:26 farnsworth kernel: 00000001 f64c0548 c04b1900 f64c0548 c04b1900 f6597340 f64c03d0 f64c03d0                
May 24 11:13:26 farnsworth kernel: Call Trace:                                                                            
May 24 11:13:26 farnsworth kernel: [<c01256de>] dequeue_task_fair+0x3e/0x190                                              
May 24 11:13:26 farnsworth kernel: [<c0102424>] __switch_to+0xb4/0x1a0                                                    
May 24 11:13:26 farnsworth kernel: [<c0151c57>] debug_mutex_add_waiter+0x27/0x80
May 24 11:13:26 farnsworth kernel: [<c01294af>] finish_task_switch+0x1f/0xb0
May 24 11:13:26 farnsworth kernel: [<c034bf98>] __mutex_lock_slowpath+0xf8/0x2d0
May 24 11:13:26 farnsworth kernel: [<c0102424>] __switch_to+0xb4/0x1a0
May 24 11:13:26 farnsworth kernel: [<c034db55>] _spin_unlock_irq+0x5/0x30
May 24 11:13:26 farnsworth kernel: [<f8c51fd1>] iwl3945_down+0x11/0x80 [iwl3945]
May 24 11:13:26 farnsworth kernel: [<f8c5218f>] iwl3945_bg_restart+0x2f/0x50 [iwl3945]
May 24 11:13:26 farnsworth kernel: [<c013f943>] run_workqueue+0x73/0x130
May 24 11:13:26 farnsworth kernel: [<c011e555>] default_spin_lock_flags+0x5/0x10
May 24 11:13:26 farnsworth kernel: [<f8c52160>] iwl3945_bg_restart+0x0/0x50 [iwl3945]
May 24 11:13:26 farnsworth kernel: [<c013fa80>] worker_thread+0x80/0xf0
May 24 11:13:26 farnsworth kernel: [<c0143680>] autoremove_wake_function+0x0/0x40
May 24 11:13:26 farnsworth kernel: [<c013fa00>] worker_thread+0x0/0xf0
May 24 11:13:26 farnsworth kernel: [<c01432e9>] kthread+0x39/0x70
May 24 11:13:26 farnsworth kernel: [<c01432b0>] kthread+0x0/0x70
May 24 11:13:26 farnsworth kernel: [<c0104693>] kernel_thread_helper+0x7/0x14

Damnshock · 2009-05-28 16:10:51

I just want to say that I *do* have problems with the iwl3945 driver. The only way that I can connect to any wireless is:

1-Start network script (and if fails to connect)
2-ifconfig wlan0 up
3-Try again the network script: now everything works.

If I don't follow this steps, I simply can't connect to any wireless at all

dcrabs · 2009-06-02 21:45:06

I think, I will give up sooner or later. This ucode error is only existing in this thread.
Newest thing is that I don't see an error at all but clearly the module doesn't load properly:

cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: EU
        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
        (2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
        (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
        (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
        (5490000 KHz - 5710000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: EU
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2008 Intel Corporation

That's all I see in dmesg output.
And I thought I bought a piece of hardware that is well supported and widely used...

Last edited by dcrabs (2009-06-02 21:46:15)

bds · 2009-06-03 07:24:42

Don't give up!

My HP NC6400 has the same wireless/ethernet controllers and works perfectly.

hwd -e:

Network controller: Intel Corporation module: iwl3945 
          PRO/Wireless 3945ABG [Golan] Network Connection
Ethernet controller: Broadcom Corporation module: tg3 
          NetXtreme BCM5753M Gigabit Ethernet PCI Express

dmesg:

iwl3945 0000:10:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:10:00.0: restoring config space at offset 0x1 (was 0x100002, writing 0x100006)
iwl3945 0000:10:00.0: irq 28 for MSI/MSI-X
iwl3945 0000:10:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 loaded firmware version 15.32.2.9
wlan0: authenticate with AP xx:xx:xx:xx:xx:xx
wlan0: authenticated
wlan0: associate with AP xx:xx:xx:xx:xx:xx
wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x461 status=0 aid=1)

netcfg2 profile:

CONNECTION="wireless"
DESCRIPTION="Wireless connection via Intel iwl3945 driver"
INTERFACE=wlan0
SCAN="yes"
SECURITY="none"
ESSID="Wireless"
IP="dhcp"
POST_UP="iwconfig wlan0 rate 54M"

I would like to suggest the following:

1. Confirm via a live CD that your wireless HW is ok.

2. Leave the wireless radio ON when booting.

3. Put SCAN="no" in your profile and add the mac address of your ap to the POST_UP line in your profile (The mac address of the ap is the BSSID that you asked about earlier). This will force your card to try associating with the correct ap only.

4. Add the line DHCLIENT="no" to use dhcpcd instead of dhclient.

HTH,

bds

broch · 2009-06-03 17:26:11

I never had a problem with iwl3945
my setup:
hardware:
Network controller: Intel Corporation module: iwl3945
PRO/Wireless 3945ABG [Golan] Network Connection

software
iwlwifi-3945-ucode 15.32.2.9-1
dhcpcd 3.2.1-1
wpa_supplicant 0.6.9-1
kernel 2.6.29.4 or 2.6.30-rc7-zen0
wireless assistant 0.57

software setup:
rc.conf
INTERFACES=(eth0)
eth0="dhcp"
MODULES=(acpi-cpufreq)
DAEMONS=(@kdm @syslog-ng @network @hal)

wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="whatever"
scan_ssid=1
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk=your_key_goes_here
}

after loging I start wireless assistant and connect to whatever wireless network or if wired network is available plugging in ethernet cable is good enough.
as you can see, my setup is way easier,
I keep older version of dhcpcd client as this one os more robust than any newer version.

I hope this will help

Last edited by broch (2009-06-03 17:27:03)

rebugger · 2009-06-03 17:30:33

I had similiar problems with my hp 6510b which has a iwl3945 wlan adapter too.
The fun thing was: i just could get the wlan up, if i unplugged eth0 - still not sure why it is like that.
maybe you want to give it a try too...

dcrabs · 2009-06-03 18:40:02

Hi
Thanks to your replies and the encouragement.
Could you also post your kernel command lines? I have the suspicion that it might also be connected. Mine is currently like that:

i915.modeset=1 root=/dev/sda5 ro quiet nopat apic=debug debug=255 enable_mttr_cleanup clocksource=jiffies resume=/dev/sda6

I also tried without modesetting, and noapic as well as irqpoll options. clocksource=jiffies seems to stabilize my xserver.
@rebugger: I got this feeling too but could never prove it.
Everything seems a bit random and the latest "error" is not very helpful. Did anyone load the module with the debug option?
Thanks again for your help. I will try your set-ups and report back.

EDIT: typos

Last edited by dcrabs (2009-06-03 18:51:45)

broch · 2009-06-03 19:28:52

kernel /vmlinuz-2.6.30-rc7-zen0-RIGAUDON root=/dev/sda2 fastboot loglevel=0 quiet vga=792 ro

bds · 2009-06-04 03:10:23

As plain vanilla as can be:

kernel /boot/archee/vmlinuz26 root=/dev/sda7 ro

Bart(t · 2009-10-17 11:22:57

You're not the only one with this problem.

I'm using the Intel wifi 5300 (iwl5000) and I am having the same issues. Browsing on the web and this forum (with a different computer) I kinda got the impression that this error often concerns an Intel wifi card.

Checking the dmesg output, two messages might give some information:
Intel AES-NI instructions are not detetected.

wlan0: deauthenticated by local choice (reason=3)

The second messages is somewhat odd, since dmesg first tells me that wlan0 was authenticated. But at the end, for some reason, it gets deauthenticated.

Last edited by Bart(t (2009-10-17 11:29:00)

dcrabs · 2009-10-17 11:38:31

I am unfortunately not a big help cause my "old" notebook is standing at home now all the time. And with the new notebook at work I didn't get a chance to test if it's working. But I try to post it here as soon as I find something helpful.

kgas · 2009-10-17 13:15:01

In lenovo 3000 N100, the same wireless card is there and works without problem. wicd is used as network manager

>lspci | grep -i net
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

>dmesg | grep iwl3945
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:03:00.0: setting latency timer to 64
iwl3945 0000:03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945BG
iwl3945 0000:03:00.0: irq 26 for MSI/MSI-X
iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9

I am not sure whether you have to set crda policy. The only problem faced is swapping of eth0 and wlan0 frequently and solved by setting udv rules.

Renan Birck · 2009-10-17 18:36:01

In Acer Aspire 7720, I have the same WLAN card and connect without problem. I use wicd.

(11) alliance:~ >> lspci | grep -i 3945
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

(12) alliance:~ >> dmesg | egrep -i '(wlan0|3945)'
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:06:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
iwl3945 0000:06:00.0: setting latency timer to 64
iwl3945 0000:06:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 0000:06:00.0: Detected Intel Wireless WiFi Link 3945ABG
iwl3945 0000:06:00.0: irq 29 for MSI/MSI-X
phy0: Selected rate control algorithm 'iwl-3945-rs'
iwl3945 0000:06:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
wlan0: authenticate with AP 00:1c:df:ce:5e:d6
wlan0: authenticated
wlan0: associate with AP 00:1c:df:ce:5e:d6
wlan0: RX AssocResp from 00:1c:df:ce:5e:d6 (capab=0x411 status=0 aid=1)
wlan0: associated

dcrabs, have you tried with another network-manager, like wicd?

dcrabs · 2009-10-17 18:50:36

kgas wrote:

In lenovo 3000 N100, the same wireless card is there and works without problem. wicd is used as network manager
>lspci | grep -i net
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
>dmesg | grep iwl3945
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:03:00.0: setting latency timer to 64
iwl3945 0000:03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels
iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945BG
iwl3945 0000:03:00.0: irq 26 for MSI/MSI-X
iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
I am not sure whether you have to set crda policy. The only problem faced is swapping of eth0 and wlan0 frequently and solved by setting udv rules.

I used to load the module with EU regdom:
options cfg80211 ieee80211_regdom="EU"

dcrabs · 2009-10-17 19:27:33

Renan Birck wrote:

In Acer Aspire 7720, I have the same WLAN card and connect without problem. I use wicd.
(11) alliance:~ >> lspci | grep -i 3945
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
(12) alliance:~ >> dmesg | egrep -i '(wlan0|3945)'
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks
iwl3945: Copyright(c) 2003-2009 Intel Corporation
iwl3945 0000:06:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
iwl3945 0000:06:00.0: setting latency timer to 64
iwl3945 0000:06:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels
iwl3945 0000:06:00.0: Detected Intel Wireless WiFi Link 3945ABG
iwl3945 0000:06:00.0: irq 29 for MSI/MSI-X
phy0: Selected rate control algorithm 'iwl-3945-rs'
iwl3945 0000:06:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:06:00.0: loaded firmware version 15.32.2.9
wlan0: authenticate with AP 00:1c:df:ce:5e:d6
wlan0: authenticated
wlan0: associate with AP 00:1c:df:ce:5e:d6
wlan0: RX AssocResp from 00:1c:df:ce:5e:d6 (capab=0x411 status=0 aid=1)
wlan0: associated
dcrabs, have you tried with another network-manager, like wicd?

To be honest, I don't remember trying wicd. I think I did. But as you see in the earlier posts most of the time I tried without any manager to rule out problems with the manager. Unfortunately, I can't try now cause I recently moved to Sweden and don't need my private computer at the university any more and at home it's ethernet. If there is time in the next week I can try after work again.

Bart(t · 2009-10-18 20:01:38

bart:~$ lspci | grep -i net
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
07:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection

bart:~$ dmesg | grep iwl
iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks
iwlagn: Copyright(c) 2003-2009 Intel Corporation
iwlagn 0000:07:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwlagn 0000:07:00.0: setting latency timer to 64
iwlagn 0000:07:00.0: Detected Intel Wireless WiFi Link 5300AGN REV=0x24
iwlagn 0000:07:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
iwlagn 0000:07:00.0: irq 31 for MSI/MSI-X
phy0: Selected rate control algorithm 'iwl-agn-rs'
iwlagn 0000:07:00.0: firmware: requesting iwlwifi-5000-2.ucode
iwlagn 0000:07:00.0: loaded firmware version 8.24.2.12
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX
Registered led device: iwl-phy0::radio
Registered led device: iwl-phy0::assoc
Registered led device: iwl-phy0::RX
Registered led device: iwl-phy0::TX

Using netcfg and wpa_supplicant. Another computer has the same netcfg+wpa_supplicant settings and is working corrrectly. Figures?

I don't think it's netcfg or wpa_supplicant. Of course every tool can have a bug, but netcfg and wpa_supplicant are proven tools.

Last edited by Bart(t (2009-10-18 20:11:24)

Maximalminimalist · 2009-10-19 17:49:49

Hello!

I'm using a Thinkpad T60 and I also have the iwl3945.

lspci | grep -i net
02:00.0 Ethernet controller: Intel Corporation 82573L Gigabit Ethernet Controller
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

Since the last kernel update I also have problems with wlan0. I must admit that I am not an experienced user so my question will maybe seem silly.

I more or less read the whole topic and I could remove the soft block with rfkill. I don't know how to remove the hard block. The FN+F5 doesn't do anything...

I hope somebody can help me.
Thanks in advance.

Last edited by Maximalminimalist (2009-10-19 17:53:34)

alexandrite · 2009-10-20 13:37:23

I've come up with a possible workaround for whatever problem these 3945ABGs seem to have:

I have an Intel 3945ABG as well, and I've found that just using Wireless Extensions, I can't keep connected to the large wifi network at my school.

If I use wpa_supplicant with no key management (There's an example network block for that in the wpa_supplicant.conf that ships with Arch), then I can get a more-or-less consistent connection. This may explain why Broch's configuration works, and yours does not. He has to use wpa_supplicant, and would not see a problem.

Hope this helps, and if you try this, tell me if it works

Maximalminimalist · 2009-10-21 17:32:47

Thanks for your help. I'll check out the wpa_supplicant but first I want to tell that I have the same problem as in http://bbs.archlinux.org/viewtopic.php?id=82357 .
I couldn't decide in which thread I had to post...

ifconfig wlan 0 up
SIOCSIFFLAGS: Unknown error 132

Doesn't the wpa_supplicant only help if there is any connection possible?

Arch Linux

#1 2009-04-30 16:04:52

Permanent problems with intel wlan (iwl3945)

#2 2009-05-01 11:06:54

Re: Permanent problems with intel wlan (iwl3945)

#3 2009-05-01 14:08:21

Re: Permanent problems with intel wlan (iwl3945)

#4 2009-05-07 12:10:38

Re: Permanent problems with intel wlan (iwl3945)

#5 2009-05-13 10:28:03

Re: Permanent problems with intel wlan (iwl3945)

#6 2009-05-15 07:45:32

Re: Permanent problems with intel wlan (iwl3945)

#7 2009-05-28 13:17:07

Re: Permanent problems with intel wlan (iwl3945)

#8 2009-05-28 16:10:51

Re: Permanent problems with intel wlan (iwl3945)

#9 2009-06-02 21:45:06

Re: Permanent problems with intel wlan (iwl3945)

#10 2009-06-03 07:24:42

Re: Permanent problems with intel wlan (iwl3945)

#11 2009-06-03 17:26:11

Re: Permanent problems with intel wlan (iwl3945)

#12 2009-06-03 17:30:33

Re: Permanent problems with intel wlan (iwl3945)

#13 2009-06-03 18:40:02

Re: Permanent problems with intel wlan (iwl3945)

#14 2009-06-03 19:28:52

Re: Permanent problems with intel wlan (iwl3945)

#15 2009-06-04 03:10:23

Re: Permanent problems with intel wlan (iwl3945)

#16 2009-10-17 11:22:57

Re: Permanent problems with intel wlan (iwl3945)

#17 2009-10-17 11:38:31

Re: Permanent problems with intel wlan (iwl3945)

#18 2009-10-17 13:15:01

Re: Permanent problems with intel wlan (iwl3945)

#19 2009-10-17 18:36:01

Re: Permanent problems with intel wlan (iwl3945)

#20 2009-10-17 18:50:36

Re: Permanent problems with intel wlan (iwl3945)

#21 2009-10-17 19:27:33

Re: Permanent problems with intel wlan (iwl3945)

#22 2009-10-18 20:01:38

Re: Permanent problems with intel wlan (iwl3945)

#23 2009-10-19 17:49:49

Re: Permanent problems with intel wlan (iwl3945)

#24 2009-10-20 13:37:23

Re: Permanent problems with intel wlan (iwl3945)

#25 2009-10-21 17:32:47

Re: Permanent problems with intel wlan (iwl3945)

Board footer