You are not logged in.
my iwl3945 dosen't work if i not "sudo rmmod iwl3945 | sudo modprobe iwl3945" first when I start
the dmesg |grep iwl3945 results are following
sda: sda1 sda2 < sda5<6>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 -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:10:00.0: setting latency timer to 64
iwl3945: Detected Intel Wireless WiFi Link 3945ABG
iwl3945: Tunable channels: 13 802.11bg, 4 802.11a channels
iwl3945: Failed to register network device (error -2)
iwl3945 0000:10:00.0: PCI INT A disabled
iwl3945: probe of 0000:10:00.0 failed with error -2and lsmod | grep iwl3945
iwl3945 90100 0
rfkill 10008 1 iwl3945
mac80211 158876 1 iwl3945
led_class 5508 1 iwl3945
cfg80211 25224 2 iwl3945,mac80211my rc.conf
MOD_AUTOLOAD="yes"
MODULES=(e100 mii iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore )
HOSTNAME="wordog"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0,!wlan0)
DAEMONS=(syslog-ng !network hal !networkmanager wicd netfs crond @alsa sensors @fam slim @acpid mpd @httpd @mysqld net-profiles @laptop-mode)I use Wicd for my wireless admin
t
PS: Maybe I should post this issue in another place, but now I can't turn it further. The Admin of the bbs ,please remove this post to Networking . THX
Last edited by e6nian (2008-10-20 02:51:45)
Offline
i have the same problem and was told by dan williams (the networkmanager guy) that this was due to the 3945 driver not using rf_kill correctly in the past and broken hal. since 2.6.27's iwl3945 now is switched to rf_kill and hal's code in git fixed aswell, it should be fixed in the next hal release, which should arrive pretty soon now.
Offline
i have the same problem and was told by dan williams (the networkmanager guy) that this was due to the 3945 driver not using rf_kill correctly in the past and broken hal. since 2.6.27's iwl3945 now is switched to rf_kill and hal's code in git fixed aswell, it should be fixed in the next hal release, which should arrive pretty soon now.
what's your solution to this issue?
any patch for this or else?
Offline
You can add "sudo rmmod iwl3945 | sudo modprobe iwl3945" to autostart.sh (in openbox) or ~/.xinitrc, to make it executes automatically.
Offline
lol. it's a expedient.
waiting for more issure.
Offline
baze wrote:i have the same problem and was told by dan williams (the networkmanager guy) that this was due to the 3945 driver not using rf_kill correctly in the past and broken hal. since 2.6.27's iwl3945 now is switched to rf_kill and hal's code in git fixed aswell, it should be fixed in the next hal release, which should arrive pretty soon now.
what's your solution to this issue?
any patch for this or else?
booting with the killswitch off works for me. in this case, the device is activated by networkmanager (0.7 from trunk).
as long as i don't activated the killswitch, the device works. deactivating wifi in nm-applet and reactivating works aswell, in that case i don't have to reload the module either.
Offline
e6nian wrote:baze wrote:i have the same problem and was told by dan williams (the networkmanager guy) that this was due to the 3945 driver not using rf_kill correctly in the past and broken hal. since 2.6.27's iwl3945 now is switched to rf_kill and hal's code in git fixed aswell, it should be fixed in the next hal release, which should arrive pretty soon now.
what's your solution to this issue?
any patch for this or else?booting with the killswitch off works for me. in this case, the device is activated by networkmanager (0.7 from trunk).
as long as i don't activated the killswitch, the device works. deactivating wifi in nm-applet and reactivating works aswell, in that case i don't have to reload the module either.
THX a lot.
And how to set booting with the killswitch? in BIOS setting or archlinux configuration?
Offline