View Single Post
Old 10-11-07, 11:36 AM   #33
mlfarrell
Registered User
 
Join Date: Mar 2005
Posts: 65
Default Re: nvidia 100.14.19 + ipw3945: system freezes

That's a shame. As I definitely think ipw3945 was corrupting the nvidia driver's kernel memory since both you and me have had no problems when the ipw3945 driver is not running.

So you're saying that iwl3945 loads but it won't connect to the ap after that?

There's three steps to installing the driver,
first copying the microcode for the new driver to the appropriate directory for your system. On mine its the same place where the old driver's code was:

kain@slickbox:~> ls /lib/firmware/*3945*
/lib/firmware/ipw3945.ucode /lib/firmware/iwlwifi-3945-1.ucode
(note the iwl entry)

You no longer need to run ipw3945d, so there's on daemon installation. Next verify that mac80211 is running via lsmod:

kain@slickbox:~> lsmod|grep mac
mac80211 116484 1 iwl3945
cfg80211 9096 1 mac80211


And check your kernel output:
kain@slickbox:~> dmesg|grep -i iwl
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.1.17ds
iwl3945: Copyright(c) 2003-2007 Intel Corporation
iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
iwl3945: Tunable channels: 11 802.11bg, 13 802.11a channels
wmaster0: Selected rate control algorithm 'iwl-3945-rs'

dmesg|grep eth1
...
...
eth1: Initial auth_alg=0
eth1: authenticate with AP 00:18:39:b4:8a:bb
eth1: RX authentication from 00:18:39:b4:8a:bb (alg=0 transaction=2 status=0)
eth1: authenticated
eth1: associate with AP 00:18:39:b4:8a:bb
eth1: RX AssocResp from 00:18:39:b4:8a:bb (capab=0x411 status=0 aid=1)
eth1: associated
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
eth1: duplicate address detected!
eth1: duplicate address detected!
..
..

(none of those errors give me any problems)
mlfarrell is offline   Reply With Quote