Intel 4965AGN No Go WPA/WPA2

[ohyes]

I started a thread about this issue in beginners..but perhaps it should posted
here

Puppy 4 with latest kernel, recognises and loads driver for the 4965 wifi card.
But trying to use it ..it connects for a few seconds then seems to time out..then gets blacklisted...tried this using wpa supplicant and wext...output below
using WPA2..TIA for any help.

Authentication with 00:13:d3:xx:xx:xx timed out.
BSSID 00:13:d3:xx:xx:xx blacklist count incremented to 2
wpa_driver_wext_disassociate
No keys have been configured - skip key clearing
State: 4WAY_HANDSHAKE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=12
Scan timeout - try to get results
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
Scan results: -1
Failed to get scan results
Failed to get scan results - try scanning again

[tempestuous]

This looks like a problem with how your driver (iwl4965) is interacting with wpa_supplicant via the "wext" protocol ... I hope you're using "wext"? This is how your command should look, please advise if otherwise -

Code: Select all

wpa_supplicant -i wlan0 -D wext -c /etc/wpa_supplicant2.conf -dd

Ive downloaded puppy 4 with the 2.6.25 kernel

The kernel in Puppy-4.1alpha2 is now quite different, and the loading of associated modules and firmware has changed significantly. I think you should move up to Puppy-4.1alpha2 before going any further -
http://distro.ibiblio.org/pub/linux/dis ... 4.1alpha2/
If you still get the same problem with Puppy-4.1alpha2 I suspect that changing the value of "ap_scan=" in /etc/wpa_supplicant2.conf (and /etc/wpa_supplicant.conf) might fix things. Puppy's default value is "2". Try changing it to "1", then try "0".

Also check if your wifi router is broadcasting the SSID. In theory, a hidden SSID is OK if you use "ap_scan=2" or "ap_scan=0" but generally wpa_supplicant will work more reliably if the SSID is broadcast.

[ohyes]

Thx for posting Tempestuous

the command and recent guide I followed was yours for manually connecting

yeah I used wext in the command line you posted.
Weird thing is it works better with network assistant...but it only connects 1 out of 20+ attempts with network assistant...but once connected it stays connected.

Ive tried many combos mannually all with the same result...will download the alpha..see how it goes ...

Will post result

Cheers

[ohyes]

Puppy 4 Alpha no better

Same errors as first post...tried ap_scan=1 & 2

with ap_scan=1 the scan failed to see any AP's
with ap_scan=2 started to get the authentication timeout error
and the blacklisting of the AP and the whole cycle repeated over & over
as first post

Noted that it says it finds a new AP:

Wireless event: new AP: 00:00:00:00:00:00
BSSID 00:00:00:00:00:00 blacklist count incremented to 2

A Buggy Driver perhaps ??? iwl4965 ?

Anyone got the iwl4965 to work with Puppy ?
Could I try a newer iwl4965 driver

Ive just tried it with Ubuntu latest live CD and it works ok.

Cheers

[ohyes]

BUG 1522 !

This bug has been posted ..it shows the same errors..as Im getting

http://intellinuxwireless.org/bugzilla/ ... ction=edit

Its a fairly old bug..so perhaps it has been fixed by now.
And perhaps it has..as it does work in Ubuntu...


Dont know much about all this...question is what can I do to get this puppy going using an Intel 4965AGN wireless card ?

Any ideas most appreciated
Cheers

[tempestuous]

I will compile the latest iwl4965 driver when I'm back in Sydney on Tuesday.

[ohyes]

tempestuous


Many Thanks

[tempestuous]

ohyes, upgraded iwl4965 module and underlying wifi stack are now available here -
http://www.murga-linux.com/puppy/viewto ... 308#207308

[ohyes]

Thanks Tempestuous !! Will give this a go and report back this Saturday

[ohyes]

Hi Tempestuous

Tried the wifi pet..now puppy does not recognise the wifi card for some reason.

do you want me to try anything ?

Cheers

[tempestuous]

Try to manually load your driver before running the wpa_supplicant commands. So -

Code: Select all

modprobe iwl4965

If you see error messages, please report.
If no error messages, bring up the interface -

Code: Select all

ifconfig wlan0 up

now run the wpa_supplicant commands.

[ohyes]

Hi Tempestuous

Yeah sorry I should make it clear that the intel wifi card is not being seen now
modprobe iwl4965 gives error 'device not found
I confirmed it was after'installing the pet...did a reboot without the puppy save and the wifi card was seen again.

lspci also showed the card was missing.

So to recap, after the pet install (and reboot) puppy cannot see the wifi card.

Cheers

[ohyes]

Forgot to mention that after the pet install the wired ethernet card is still seen and works OK..so its something wifi specific...

[tempestuous]

modprobe iwl4965 gives error 'device not found
lspci also showed the card was missing.

Wow, that's weird. I can't imagine how the installation of new modules would affect device detection.
All I can suggest is to hide your current pupsave file (or delete it if you don't care about losing settings) then boot afresh to create a new pupsave file, then install the new wifi drivers again.

If no success, wait for Puppy 4.1 alpha3

[ohyes]

dmesg output

cfg80211: no version for "struct_module" found: kernel tainted.
iwl4965: Unknown symbol sta_info_put
iwl4965: disagrees about version of symbol ieee80211_free_hw
iwl4965: Unknown symbol ieee80211_free_hw
iwl4965: disagrees about version of symbol ieee80211_alloc_hw
iwl4965: Unknown symbol ieee80211_alloc_hw
iwl4965: disagrees about version of symbol ieee80211_register_hw
iwl4965: Unknown symbol ieee80211_register_hw
iwl4965: disagrees about version of symbol ieee80211_rate_control_unregister
iwl4965: Unknown symbol ieee80211_rate_control_unregister
iwl4965: disagrees about version of symbol ieee80211_wake_queue
iwl4965: Unknown symbol ieee80211_wake_queue
iwl4965: disagrees about version of symbol ieee80211_tx_status_irqsafe
iwl4965: Unknown symbol ieee80211_tx_status_irqsafe
iwl4965: disagrees about version of symbol ieee80211_rate_control_register
iwl4965: Unknown symbol ieee80211_rate_control_register
iwl4965: disagrees about version of symbol sta_info_get
iwl4965: Unknown symbol sta_info_get
iwl4965: Unknown symbol ieee80211_start_queues
iwl4965: disagrees about version of symbol ieee80211_tx_status
iwl4965: Unknown symbol ieee80211_tx_status
iwl4965: disagrees about version of symbol ieee80211_stop_queue
iwl4965: Unknown symbol ieee80211_stop_queue
iwl4965: disagrees about version of symbol ieee80211_stop_queues
iwl4965: Unknown symbol ieee80211_stop_queues
iwl4965: disagrees about version of symbol ieee80211_scan_completed
iwl4965: Unknown symbol ieee80211_scan_completed
iwl4965: disagrees about version of symbol ieee80211_unregister_hw
iwl4965: Unknown symbol ieee80211_unregister_hw
iwl4965: disagrees about version of symbol ieee80211_beacon_get
iwl4965: Unknown symbol ieee80211_beacon_get
iwl4965: Unknown symbol ieee80211_register_hwmode
iwl4965: disagrees about version of symbol ieee80211_rx_irqsafe
iwl4965: Unknown symbol ieee80211_rx_irqsafe

[ohyes]

No worries looks like I will wait for alpha3 ...repeated the test same result


the demsg output again was the same as above post.

Cheers

[ohyes]

Not sure if this post from a gentoo forum might help shed some light...something about turning of option ''802.11'' in the kernel..hope this might make sense more than it does to me.

http://forums.gentoo.org/viewtopic-p-41 ... 002ee85081


Also another post about the same problem but perhaps a different answer ......which if any are right..

"The iwl4965 module failed to load because it is looking for some mac80211 symbols. These symbols are missing probably because the driver and the mac80211 substack was not compiled in the same environment. You need to compile iwl4965 after mac80211 has been installed in your kernel sources."

[ohyes]

error after modprobe iwl4965

modprobe iwl4965
FATAL: Error inserting iwl4965 (/lib/modules/2.6.25.4/kernel/drivers/net/wireless/iwlwifi/iwl4965.ko): Unknown symbol in module, or unknown parameter (see dmesg)

[ohyes]

This post from Ubuntu has the same error
posted day before yesterday !

"Updated the PPA to linux-backports-modules-2.6.24-19.18ubuntu3 which
fixes the missing symbols issue. Also contains updates to wireless-
testing.git up through tag master-2008-06-11."



http://www.mail-archive.com/ubuntu-bugs ... 79846.html

[ohyes]

Ok another most recent post has this ..from another ubuntu post ..11/6/08

"OK unresolved symbols issue has been fixed. A new package just need to be created. You can also just test the tarball from wireless.kernel.org."

perhaps this is the answer...getting the latest from the wireless.kernel.org site