Hi!
> I tried to use `subj`, but hit few problems:
>
> There's no maintainers entry. Should
>
> James P. Ketrenos <[EMAIL PROTECTED]>
>
> be listed as a maintainer?
>
> Kconfig mentions...
>
> See <file:Documentation/networking/README.iwlwifi> for
> information on the capabilities currently enabled in this
> driver and for tips for debugging issues and problems.
>
> ...but that file does not exist.
More problems:
I managed to load the firmware and insert the module.... but I had
radio kill switch on. It complained that kill switch is on, but
turning it off did not help. Module unload/reload was neccessary to
get it to work.
I still do not see the wlan led. It seems to scan okay, but I can't
seem to connect, and I get this in logs:
Jun 9 23:53:21 amd kernel: wlan0: deauthenticated
Jun 9 23:53:21 amd kernel: wlan0: RX deauthentication from
00:11:2f:0e:95:a0 (reason=4)
Jun 9 23:53:21 amd last message repeated 2 times
Jun 9 23:53:22 amd kernel: wlan0: authenticate with AP
00:11:2f:0e:95:a0
Jun 9 23:53:22 amd kernel: wlan0: RX authentication from
00:11:2f:0e:95:a0 (alg=0 transaction=2 status=0)
Jun 9 23:53:22 amd kernel: wlan0: authenticated
Jun 9 23:53:22 amd kernel: wlan0: associate with AP 00:11:2f:0e:95:a0
Jun 9 23:53:22 amd kernel: wlan0: authentication frame received from
00:11:2f:0e:95:a0, but not in authenticate state - ignored
Jun 9 23:53:22 amd last message repeated 2 times
Jun 9 23:53:22 amd kernel: wlan0: RX ReassocResp from
00:11:2f:0e:95:a0 (capab=0x401 status=0 aid=2)
Jun 9 23:53:22 amd kernel: wlan0: associated
Jun 9 23:53:24 amd kernel: wlan0: No ProbeResp from current AP
00:11:2f:0e:95:a0 - assume out of range
Jun 9 23:53:43 amd kernel: e1000: eth0: e1000_watchdog: NIC Link is
Up 100 Mbps Full Duplex, Flow Control: RX/TX
Jun 9 23:53:43 amd kernel: e1000: eth0: e1000_watchdog: 10/100 speed:
disabling TSO
Jun 9 23:53:56 amd kernel: wlan0: No STA entry for own AP
00:11:2f:0e:95:a0
Jun 9 23:54:12 amd kernel: iwl3945: Microcode SW error detected.
Restarting 0x82000000.
Jun 9 23:54:12 amd kernel: iwl3945: Error Reply type 0x0000003A cmd
REPLY_RXON_ASSOC (0x11) seq 0x0447 ser 0x00000000
Jun 9 23:54:12 amd kernel: iwl3945: Error setting RXON_ASSOC
configuration (-5).
Jun 9 23:54:13 amd kernel: iwl3945: Error sending REPLY_RXON: time
out after 500ms.
Jun 9 23:54:13 amd kernel: iwl3945: Error setting new configuration
(-110).
Jun 9 23:54:15 amd kernel: iwl3945: Error sending REPLY_ADD_STA: time
out after 500ms.
Jun 9 23:54:15 amd kernel: iwl3945: ipw going down
Jun 9 23:54:15 amd kernel: iwl3945: Can't stop Rx DMA.
Jun 9 23:54:15 amd kernel: iwl3945: Grabbing access while already
held at line 825.
Jun 9 23:54:15 amd kernel: iwl3945: Microcode SW error detected.
Restarting 0x82000000.
Jun 9 23:54:15 amd kernel: iwl3945: Error Reply type 0x000004EB cmd
REPLY_TX_PWR_TABLE_CMD (0x97) seq 0x0402 ser 0x00000000
Jun 9 23:54:15 amd kernel: iwl3945: ipw going down
Jun 9 23:54:16 amd kernel: iwl3945: Can't stop Rx DMA.
Jun 9 23:54:16 amd kernel: iwl3945: Grabbing access while already
held at line 825.
Jun 9 23:54:16 amd kernel: iwl3945: Microcode SW error detected.
Restarting 0x82000000.
Jun 9 23:54:16 amd kernel: iwl3945: Error Reply type 0x000004EB cmd
REPLY_TX_PWR_TABLE_CMD (0x97) seq 0x0402 ser 0x00000000
Jun 9 23:54:16 amd kernel: iwl3945: ipw going down
Jun 9 23:54:17 amd kernel: iwl3945: Can't stop Rx DMA.
Jun 9 23:54:17 amd kernel: iwl3945: Grabbing access while already
held at line 825.
What are the next steps?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
