* orinoco_cs module and WPA not working
@ 2010-11-22 2:42 Giacomo Comes
2010-11-24 19:06 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-11-22 2:42 UTC (permalink / raw)
To: linux-wireless
Hi,
I'm having trouble with a wireless card using the orinoco driver.
The card is (pccardctl ident output):
Socket 2:
product info: "Dell", "TrueMobile 1150 Series PC Card", "Version 01.01", ""
manfid: 0x0156, 0x0002
function: 6 (network)
I'm running suse 11.3 with kernel 2.6.34.7
dmesg output shows that the card is supported by the orinoco_cs kernel module:
[ 14.239886] pcmcia_socket pcmcia_socket1: cs: memory probe 0x0c0000-0x0fffff: excluding 0xc0000-0xcffff 0xf0000-0xfffff
[ 14.241156] pcmcia_socket pcmcia_socket1: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 14.241409] pcmcia_socket pcmcia_socket1: cs: memory probe 0x60000000-0x60ffffff: clean.
[ 14.269111] pcmcia_socket pcmcia_socket2: pccard: PCMCIA card inserted into slot 2
[ 14.269128] pcmcia_socket pcmcia_socket2: cs: memory probe 0x0d0000-0x0effff:
[ 14.295349] ieee1394: Host added: ID:BUS[0-00:1023] GUID[5b4fc0003fffffff]
[ 14.320737] excluding 0xe0000-0xeffff
[ 14.320758] pcmcia_socket pcmcia_socket2: cs: memory probe 0x60000000-0x60ffffff: clean.
[ 14.332530] pcmcia_socket pcmcia_socket2: cs: memory probe 0xa0000000-0xa0ffffff: clean.
[ 14.344344] pcmcia_socket pcmcia_socket2: cs: memory probe 0xf9800000-0xfbffffff: excluding 0xf9f80000-0xfa1fffff 0xfae80000-0xfb0fffff
[ 14.355136] pcmcia 2.0: pcmcia: registering new device pcmcia2.0
[ 14.431345] cfg80211: Calling CRDA to update world regulatory domain
[ 14.476321] orinoco 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 14.494755] cfg80211: World regulatory domain updated:
[ 14.494766] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 14.494775] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.494783] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.494791] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 14.494798] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.494806] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 14.498825] orinoco_cs 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
[ 14.587767] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
[ 14.587897] orinoco_cs 2.0: Station identity 001f:0001:0008:000a
[ 14.587906] orinoco_cs 2.0: Firmware determined as Lucent/Agere 8.10
[ 14.587915] orinoco_cs 2.0: firmware: requesting agere_sta_fw.bin
[ 14.698324] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
[ 14.698457] orinoco_cs 2.0: Station identity 001f:0002:0009:0030
[ 14.698466] orinoco_cs 2.0: Firmware determined as Lucent/Agere 9.48
[ 14.698472] orinoco_cs 2.0: Ad-hoc demo mode supported
[ 14.698478] orinoco_cs 2.0: IEEE standard IBSS ad-hoc mode supported
[ 14.698483] orinoco_cs 2.0: WEP supported, 104-bit key
[ 14.698489] orinoco_cs 2.0: WPA-PSK supported
[...]
[ 32.967560] ADDRCONF(NETDEV_UP): eth1: link is not ready
NetworkManager is not able to connect to an AP and /var/log/messages contains:
Nov 12 18:55:22 rescue kernel: [ 388.982388] ------------[ cut here ]------------
Nov 12 18:55:22 rescue kernel: [ 388.982427] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.34.7/linux-2.6.34/net/wireless/core.c:633 wdev_cleanup_work+0xb7/0xe0 [cfg80211]()
Nov 12 18:55:22 rescue kernel: [ 388.982432] Hardware name: Latitude C840
Nov 12 18:55:22 rescue kernel: [ 388.982435] Modules linked in: fuse ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd cpufreq_conservative cpufreq_userspace cpufreq_powersave speedstep_ich speedstep_lib mperf ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables loop dm_mod michael_mic orinoco_cs orinoco cfg80211 rfkill firewire_ohci firewire_core snd_intel8x0m pcmcia crc_itu_t snd_intel8x0 snd_ac97_codec ppdev ac97_bus iTCO_wdt sr_mod snd_pcm parport_pc ohci1394 yenta_socket rsrc_nonstatic dcdbas pcmcia_core ieee1394 3c59x video parport floppy snd_timer sg cdrom iTCO_vendor_support snd battery ac pcspkr joydev soundcore snd_page_alloc shpchp pci_hotplug ext4 jbd2 crc16 nouveau ttm drm_kms_helper drm i2c_algo_bit button intel_agp fan processor ata_generic thermal thermal_sys
Nov 12 18:55:22 rescue kernel: [ 388.982543] Pid: 707, comm: cfg80211 Not tainted 2.6.34.7-0.5-desktop #1
Nov 12 18:55:22 rescue kernel: [ 388.982546] Call Trace:
Nov 12 18:55:22 rescue kernel: [ 388.982570] [<c02065c3>] try_stack_unwind+0x173/0x190
Nov 12 18:55:22 rescue kernel: [ 388.982580] [<c02051cf>] dump_trace+0x3f/0xe0
Nov 12 18:55:22 rescue kernel: [ 388.982589] [<c020662b>] show_trace_log_lvl+0x4b/0x60
Nov 12 18:55:22 rescue kernel: [ 388.982595] [<c0206658>] show_trace+0x18/0x20
Nov 12 18:55:22 rescue kernel: [ 388.982607] [<c064e0b3>] dump_stack+0x6d/0x72
Nov 12 18:55:22 rescue kernel: [ 388.982616] [<c02443ae>] warn_slowpath_common+0x6e/0xb0
Nov 12 18:55:22 rescue kernel: [ 388.982623] [<c0244403>] warn_slowpath_null+0x13/0x20
Nov 12 18:55:22 rescue kernel: [ 388.982635] [<e2db5497>] wdev_cleanup_work+0xb7/0xe0 [cfg80211]
Nov 12 18:55:22 rescue kernel: [ 388.982657] [<c025cfa9>] run_workqueue+0x79/0x170
Nov 12 18:55:22 rescue kernel: [ 388.982665] [<c025d123>] worker_thread+0x83/0xe0
Nov 12 18:55:22 rescue kernel: [ 388.982673] [<c025fef4>] kthread+0x74/0x80
Nov 12 18:55:22 rescue kernel: [ 388.982681] [<c0203826>] kernel_thread_helper+0x6/0x10
Nov 12 18:55:22 rescue kernel: [ 388.982688] ---[ end trace 3f0348b3b0c6f4ff ]---
Nov 12 18:55:25 rescue dhcpcd[6700]: eth1: dhcpcd not running
Instead of using NetworkManager, I tryed the wireless connection using
the traditional method with ifup. This time /var/log/messages contains:
Nov 14 21:30:22 rescue ifdown: eth1 device: Dell
Nov 14 21:30:22 rescue ifdown: TrueMobile 1150 Series PC Card
Nov 14 21:30:22 rescue ifdown: Version 01.01
Nov 14 21:30:22 rescue dhcpcd[10496]: eth1: sending signal 15 to pid 4944
Nov 14 21:30:22 rescue dhcpcd[4944]: eth1: received SIGTERM, stopping
Nov 14 21:30:22 rescue dhcpcd[4944]: eth1: removing IP address 192.168.16.100/24
Nov 14 21:30:22 rescue dhcpcd[10496]: eth1: exiting
Nov 14 21:30:23 rescue dhcpcd[4944]: eth1: exiting
Nov 14 21:30:24 rescue kernel: [ 841.364442] ------------[ cut here ]------------
Nov 14 21:30:24 rescue kernel: [ 841.364481] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.34.7/linux-2.6.34/net/wireless/core.c:633 wdev_cleanup_work+0xb7/0xe0 [cfg80211]()
Nov 14 21:30:24 rescue kernel: [ 841.364489] Hardware name: Latitude C840
Nov 14 21:30:24 rescue kernel: [ 841.364494] Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd af_packet cpufreq_conservative cpufreq_userspace cpufreq_powersave speedstep_ich speedstep_lib mperf loop dm_mod michael_mic orinoco_cs orinoco cfg80211 rfkill firewire_ohci snd_intel8x0 firewire_core snd_intel8x0m snd_ac97_codec crc_itu_t pcmcia ppdev iTCO_wdt ac97_bus snd_pcm parport_pc sr_mod ohci1394 yenta_socket 3c59x rsrc_nonstatic pcmcia_core ieee1394 dcdbas sg cdrom video parport floppy snd_timer snd shpchp iTCO_vendor_support battery ac pcspkr joydev soundcore snd_page_alloc pci_hotplug ext4 jbd2 crc16 nouveau ttm drm_kms_helper drm i2c_algo_bit button intel_agp fan processor ata_generic thermal thermal_sys [last unloaded: preloadtrace]
Nov 14 21:30:24 rescue kernel: [ 841.364635] Pid: 732, comm: cfg80211 Not tainted 2.6.34.7-0.5-desktop #1
Nov 14 21:30:24 rescue kernel: [ 841.364641] Call Trace:
Nov 14 21:30:24 rescue kernel: [ 841.364673] [<c02065c3>] try_stack_unwind+0x173/0x190
Nov 14 21:30:24 rescue kernel: [ 841.364689] [<c02051cf>] dump_trace+0x3f/0xe0
Nov 14 21:30:24 rescue kernel: [ 841.364703] [<c020662b>] show_trace_log_lvl+0x4b/0x60
Nov 14 21:30:24 rescue kernel: [ 841.364715] [<c0206658>] show_trace+0x18/0x20
Nov 14 21:30:24 rescue kernel: [ 841.364732] [<c064e0b3>] dump_stack+0x6d/0x72
Nov 14 21:30:24 rescue kernel: [ 841.364746] [<c02443ae>] warn_slowpath_common+0x6e/0xb0
Nov 14 21:30:24 rescue kernel: [ 841.364759] [<c0244403>] warn_slowpath_null+0x13/0x20
Nov 14 21:30:24 rescue kernel: [ 841.364778] [<e2d9b497>] wdev_cleanup_work+0xb7/0xe0 [cfg80211]
Nov 14 21:30:24 rescue kernel: [ 841.364807] [<c025cfa9>] run_workqueue+0x79/0x170
Nov 14 21:30:24 rescue kernel: [ 841.364822] [<c025d123>] worker_thread+0x83/0xe0
Nov 14 21:30:24 rescue kernel: [ 841.364835] [<c025fef4>] kthread+0x74/0x80
Nov 14 21:30:24 rescue kernel: [ 841.364848] [<c0203826>] kernel_thread_helper+0x6/0x10
Nov 14 21:30:24 rescue kernel: [ 841.364859] ---[ end trace 86f247bee785359d ]---
Nov 14 21:31:09 rescue kernel: [ 26.546538] powernow: This module only works with AMD K7 CPUs
Nov 14 21:31:21 rescue ifup: eth1 device: Dell
Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
Nov 14 21:31:21 rescue ifup: Version 01.01
Nov 14 21:31:21 rescue ifup: eth1 is controlled by ifplugd
Nov 14 21:31:21 rescue ifup: eth1 device: Dell
Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
Nov 14 21:31:21 rescue ifup: Version 01.01
Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: WPA configured, but is untested
Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: with this device
Nov 14 21:31:21 rescue ifup-wireless: eth1 starting wpa_supplicant
Nov 14 21:31:21 rescue kernel: [ 39.199513] ADDRCONF(NETDEV_UP): eth1: link is not ready
Nov 14 21:31:22 rescue ifup-dhcp: Starting DHCP4 client on eth1
Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: dhcpcd 3.2.3 starting
Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: hardware address = 00:02:2d:70:31:3b
Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: broadcasting for a lease
Nov 14 21:31:22 rescue ifup-dhcp: .
Nov 14 21:31:25 rescue ifup-dhcp: .
Nov 14 21:31:28 rescue ifup-dhcp: .
Nov 14 21:31:31 rescue ifup-dhcp: .
Nov 14 21:31:33 rescue ifup-dhcp: .
Nov 14 21:31:36 rescue ifup-dhcp: .
Nov 14 21:31:39 rescue ifup-dhcp: .
Nov 14 21:31:42 rescue ifup-dhcp: .
Nov 14 21:31:42 rescue dhcpcd[3584]: eth1: timed out
Nov 14 21:31:42 rescue dhcpcd[3584]: eth1: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth1.info'
Nov 14 21:31:42 rescue dhcpcd[3584]: eth1: adding IP address 192.168.16.100/24
Nov 14 21:31:42 rescue dhcpcd[3584]: eth1: adding default route via 192.168.16.1 metric 0
Nov 14 21:31:43 rescue ifup-dhcp:
Nov 14 21:31:43 rescue ifup-dhcp: eth1 DHCP4 continues in background
Nov 14 21:31:43 rescue ifdown: eth1 device: Dell
Nov 14 21:31:43 rescue ifdown: TrueMobile 1150 Series PC Card
Nov 14 21:31:43 rescue ifdown: Version 01.01
Nov 14 21:31:44 rescue ifup: eth1 device: Dell
Nov 14 21:31:44 rescue ifup: TrueMobile 1150 Series PC Card
Nov 14 21:31:44 rescue ifup: Version 01.01
Nov 14 21:31:44 rescue dhcpcd[3584]: eth1: exiting
It first tryes to connect to an AP using WPA, but it fails.
Thereafter it connects to a second AP using WEP.
If I use the traditional method with ifup, I can use the card with WEP
but not WPA. With NetworkManager I cannot even connect using WEP.
I have also used the latest compat-wireless tarball configured with
the options:
CONFIG_MAC80211_HT_DEBUG=y
CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
CONFIG_MAC80211_VERBOSE_DEBUG=y
but it didn't make any difference.
My question is:
Does orinoco_cs really support WPA or not?
Is the problem really with the orinoco_cs module or with something else
(may be wpa_supplicant)?
Another issue I have with the the orinoco_cs module is the following:
During suspend and resume there is a two minutes timeout period.
More precisely, after I start to suspend the laptop the screen
goes black, the message
s2disk: snapshotting the system
appears and then there is a two minutes period where the screen stays black
and nothing happens. After the two minutes, the messages snapshot ready
appears, the snapshot image is saved to the disk and the laptop turns off.
On resume, the kernel founds the snapshot image, loads it and then
stays two minutes doing nothing. After the two minutes, the text
s2disk: returned to userspace
appears on screen, there is some disk activity and then the sistem is back.
If I blacklist the orinoco_cs module, then suspend and resume work properly.
I have no idea if the two problems are related or not. If any of the issues
has been already discussed, please point me where I can find such discussion.
If you need more informations or you want me to test some code let me know.
Please CC the answer to me as I'm not subscribed.
Thanks.
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-11-22 2:42 orinoco_cs module and WPA not working Giacomo Comes
@ 2010-11-24 19:06 ` Dave Kilroy
2010-11-25 1:45 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-11-24 19:06 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Mon, Nov 22, 2010 at 2:42 AM, Giacomo Comes <comes@naic.edu> wrote:
> I'm having trouble with a wireless card using the orinoco driver.
>
> The card is (pccardctl ident output):
>
> Socket 2:
> product info: "Dell", "TrueMobile 1150 Series PC Card", "Version 01.01", ""
> manfid: 0x0156, 0x0002
> function: 6 (network)
This is the same card I used to develop the WPA functionality in orinoco.
> I'm running suse 11.3 with kernel 2.6.34.7
> [ 14.498825] orinoco_cs 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> [ 14.587767] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> [ 14.587897] orinoco_cs 2.0: Station identity 001f:0001:0008:000a
> [ 14.587906] orinoco_cs 2.0: Firmware determined as Lucent/Agere 8.10
> [ 14.587915] orinoco_cs 2.0: firmware: requesting agere_sta_fw.bin
> [ 14.698324] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> [ 14.698457] orinoco_cs 2.0: Station identity 001f:0002:0009:0030
> [ 14.698466] orinoco_cs 2.0: Firmware determined as Lucent/Agere 9.48
> [ 14.698472] orinoco_cs 2.0: Ad-hoc demo mode supported
> [ 14.698478] orinoco_cs 2.0: IEEE standard IBSS ad-hoc mode supported
> [ 14.698483] orinoco_cs 2.0: WEP supported, 104-bit key
> [ 14.698489] orinoco_cs 2.0: WPA-PSK supported
This means the driver should have been setup appropriately.
> [...]
> [ 32.967560] ADDRCONF(NETDEV_UP): eth1: link is not ready
>
>
> NetworkManager is not able to connect to an AP and /var/log/messages contains:
>
> Nov 12 18:55:22 rescue kernel: [ 388.982388] ------------[ cut here ]------------
> Nov 12 18:55:22 rescue kernel: [ 388.982427] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.34.7/linux-2.6.34/net/wireless/core.c:633 wdev_cleanup_work+0xb7/0xe0 [cfg80211]()
> Nov 12 18:55:22 rescue kernel: [ 388.982432] Hardware name: Latitude C840
> Nov 12 18:55:22 rescue kernel: [ 388.982435] Modules linked in: fuse ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd cpufreq_conservative cpufreq_userspace cpufreq_powersave speedstep_ich speedstep_lib mperf ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables loop dm_mod michael_mic orinoco_cs orinoco cfg80211 rfkill firewire_ohci firewire_core snd_intel8x0m pcmcia crc_itu_t snd_intel8x0 snd_ac97_codec ppdev ac97_bus iTCO_wdt sr_mod snd_pcm parport_pc ohci1394 yenta_socket rsrc_nonstatic dcdbas pcmcia_core ieee1394 3c59x video parport floppy snd_timer sg cdrom iTCO_vendor_support snd battery ac pcspkr joydev soundcore snd_page_alloc shpchp pci_hotplug ext4 jbd2 crc16 nouveau ttm drm_kms_helper drm i2c_algo_bit button intel_agp fan processor ata_generic thermal thermal_sys
> Nov 12 18:55:22 rescue kernel: [ 388.982543] Pid: 707, comm: cfg80211 Not tainted 2.6.34.7-0.5-desktop #1
> Nov 12 18:55:22 rescue kernel: [ 388.982546] Call Trace:
> Nov 12 18:55:22 rescue kernel: [ 388.982570] [<c02065c3>] try_stack_unwind+0x173/0x190
> Nov 12 18:55:22 rescue kernel: [ 388.982580] [<c02051cf>] dump_trace+0x3f/0xe0
> Nov 12 18:55:22 rescue kernel: [ 388.982589] [<c020662b>] show_trace_log_lvl+0x4b/0x60
> Nov 12 18:55:22 rescue kernel: [ 388.982595] [<c0206658>] show_trace+0x18/0x20
> Nov 12 18:55:22 rescue kernel: [ 388.982607] [<c064e0b3>] dump_stack+0x6d/0x72
> Nov 12 18:55:22 rescue kernel: [ 388.982616] [<c02443ae>] warn_slowpath_common+0x6e/0xb0
> Nov 12 18:55:22 rescue kernel: [ 388.982623] [<c0244403>] warn_slowpath_null+0x13/0x20
> Nov 12 18:55:22 rescue kernel: [ 388.982635] [<e2db5497>] wdev_cleanup_work+0xb7/0xe0 [cfg80211]
> Nov 12 18:55:22 rescue kernel: [ 388.982657] [<c025cfa9>] run_workqueue+0x79/0x170
> Nov 12 18:55:22 rescue kernel: [ 388.982665] [<c025d123>] worker_thread+0x83/0xe0
> Nov 12 18:55:22 rescue kernel: [ 388.982673] [<c025fef4>] kthread+0x74/0x80
> Nov 12 18:55:22 rescue kernel: [ 388.982681] [<c0203826>] kernel_thread_helper+0x6/0x10
> Nov 12 18:55:22 rescue kernel: [ 388.982688] ---[ end trace 3f0348b3b0c6f4ff ]---
> Nov 12 18:55:25 rescue dhcpcd[6700]: eth1: dhcpcd not running
I've never seen this before. It looks like a scan is in progress when
cfg80211 tries to do some cleanup - while bringing the interface down.
> Instead of using NetworkManager, I tryed the wireless connection using
> the traditional method with ifup. This time /var/log/messages contains:
<snip ifdown> This log shows the same.
> Nov 14 21:31:21 rescue ifup: eth1 device: Dell
> Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
> Nov 14 21:31:21 rescue ifup: Version 01.01
> Nov 14 21:31:21 rescue ifup: eth1 is controlled by ifplugd
> Nov 14 21:31:21 rescue ifup: eth1 device: Dell
> Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
> Nov 14 21:31:21 rescue ifup: Version 01.01
> Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: WPA configured, but is untested
> Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: with this device
> Nov 14 21:31:21 rescue ifup-wireless: eth1 starting wpa_supplicant
> Nov 14 21:31:21 rescue kernel: [ 39.199513] ADDRCONF(NETDEV_UP): eth1: link is not ready
> Nov 14 21:31:22 rescue ifup-dhcp: Starting DHCP4 client on eth1
> Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: dhcpcd 3.2.3 starting
> Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: hardware address = 00:02:2d:70:31:3b
> Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: broadcasting for a lease
> Nov 14 21:31:22 rescue ifup-dhcp: .
<snip dhcp log> This isn't interesting. If wpa_supplicant hasn't
connected you to an AP, dhcpcd isn't going to find anything.
> It first tryes to connect to an AP using WPA, but it fails.
> Thereafter it connects to a second AP using WEP.
Can you provide wpa_supplicant logs? With a reasonable amount of
debug. -dd should do.
> I have also used the latest compat-wireless tarball configured with
> the options:
> CONFIG_MAC80211_HT_DEBUG=y
> CONFIG_MAC80211_VERBOSE_PS_DEBUG=y
> CONFIG_MAC80211_VERBOSE_DEBUG=y
orinoco does not use mac80211.
> My question is:
> Does orinoco_cs really support WPA or not?
Yes.
> Is the problem really with the orinoco_cs module or with something else
> (may be wpa_supplicant)?
Probably a wpa_supplicant configuration issue.
> Another issue I have with the the orinoco_cs module is the following:
> During suspend and resume there is a two minutes timeout period.
> More precisely, after I start to suspend the laptop the screen
> goes black, the message
> s2disk: snapshotting the system
> appears and then there is a two minutes period where the screen stays black
> and nothing happens. After the two minutes, the messages snapshot ready
> appears, the snapshot image is saved to the disk and the laptop turns off.
> On resume, the kernel founds the snapshot image, loads it and then
> stays two minutes doing nothing. After the two minutes, the text
> s2disk: returned to userspace
> appears on screen, there is some disk activity and then the sistem is back.
>
> If I blacklist the orinoco_cs module, then suspend and resume work properly.
>
> I have no idea if the two problems are related or not. If any of the issues
> has been already discussed, please point me where I can find such discussion.
This is new. Depending on your kernel config, orinoco will either try
to keep a copy of firmware which it re-flashes on resume, or try read
the firmware on suspend, which is freed on resume. Both worked circa
2.6.32.
> If you need more informations or you want me to test some code let me know.
A wpa_supplicant log please. Note that the laptop I used to develop
for (and on) has moved on, so there's only a limited number of things
I can do to debug the issue.
Regards,
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-11-24 19:06 ` Dave Kilroy
@ 2010-11-25 1:45 ` Giacomo Comes
[not found] ` <AANLkTi=nkayyyzECi6MO87ZO-CUpZeNP007_hMp8LiPV@mail.gmail.com>
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-11-25 1:45 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 8040 bytes --]
On Wed, Nov 24, 2010 at 07:06:12PM +0000, Dave Kilroy wrote:
> On Mon, Nov 22, 2010 at 2:42 AM, Giacomo Comes <comes@naic.edu> wrote:
> > I'm having trouble with a wireless card using the orinoco driver.
> >
> > The card is (pccardctl ident output):
> >
> > Socket 2:
> > product info: "Dell", "TrueMobile 1150 Series PC Card", "Version 01.01", ""
> > manfid: 0x0156, 0x0002
> > function: 6 (network)
>
> This is the same card I used to develop the WPA functionality in orinoco.
>
> > I'm running suse 11.3 with kernel 2.6.34.7
>
> > [ 14.498825] orinoco_cs 0.15 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel Roskin <proski@gnu.org>, et al)
> > [ 14.587767] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> > [ 14.587897] orinoco_cs 2.0: Station identity 001f:0001:0008:000a
> > [ 14.587906] orinoco_cs 2.0: Firmware determined as Lucent/Agere 8.10
> > [ 14.587915] orinoco_cs 2.0: firmware: requesting agere_sta_fw.bin
> > [ 14.698324] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> > [ 14.698457] orinoco_cs 2.0: Station identity 001f:0002:0009:0030
> > [ 14.698466] orinoco_cs 2.0: Firmware determined as Lucent/Agere 9.48
> > [ 14.698472] orinoco_cs 2.0: Ad-hoc demo mode supported
> > [ 14.698478] orinoco_cs 2.0: IEEE standard IBSS ad-hoc mode supported
> > [ 14.698483] orinoco_cs 2.0: WEP supported, 104-bit key
> > [ 14.698489] orinoco_cs 2.0: WPA-PSK supported
>
> This means the driver should have been setup appropriately.
>
> > [...]
> > [ 32.967560] ADDRCONF(NETDEV_UP): eth1: link is not ready
> >
> >
> > NetworkManager is not able to connect to an AP and /var/log/messages contains:
> >
> > Nov 12 18:55:22 rescue kernel: [ 388.982388] ------------[ cut here ]------------
> > Nov 12 18:55:22 rescue kernel: [ 388.982427] WARNING: at /usr/src/packages/BUILD/kernel-desktop-2.6.34.7/linux-2.6.34/net/wireless/core.c:633 wdev_cleanup_work+0xb7/0xe0 [cfg80211]()
> > Nov 12 18:55:22 rescue kernel: [ 388.982432] Hardware name: Latitude C840
> > Nov 12 18:55:22 rescue kernel: [ 388.982435] Modules linked in: fuse ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd cpufreq_conservative cpufreq_userspace cpufreq_powersave speedstep_ich speedstep_lib mperf ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables loop dm_mod michael_mic orinoco_cs orinoco cfg80211 rfkill firewire_ohci firewire_core snd_intel8x0m pcmcia crc_itu_t snd_intel8x0 snd_ac97_codec ppdev ac97_bus iTCO_wdt sr_mod snd_pcm parport_pc ohci1394 yenta_socket rsrc_nonstatic dcdbas pcmcia_core ieee1394 3c59x video parport floppy snd_timer sg cdrom iTCO_vendor_support snd battery ac pcspkr joydev soundcore snd_page_alloc shpchp pci_hotplug ext4 jbd2 crc16 nouveau ttm drm_kms_helper drm i2c_algo_bit button intel_agp fan processor ata_generic thermal thermal_sys
> > Nov 12 18:55:22 rescue kernel: [ 388.982543] Pid: 707, comm: cfg80211 Not tainted 2.6.34.7-0.5-desktop #1
> > Nov 12 18:55:22 rescue kernel: [ 388.982546] Call Trace:
> > Nov 12 18:55:22 rescue kernel: [ 388.982570] [<c02065c3>] try_stack_unwind+0x173/0x190
> > Nov 12 18:55:22 rescue kernel: [ 388.982580] [<c02051cf>] dump_trace+0x3f/0xe0
> > Nov 12 18:55:22 rescue kernel: [ 388.982589] [<c020662b>] show_trace_log_lvl+0x4b/0x60
> > Nov 12 18:55:22 rescue kernel: [ 388.982595] [<c0206658>] show_trace+0x18/0x20
> > Nov 12 18:55:22 rescue kernel: [ 388.982607] [<c064e0b3>] dump_stack+0x6d/0x72
> > Nov 12 18:55:22 rescue kernel: [ 388.982616] [<c02443ae>] warn_slowpath_common+0x6e/0xb0
> > Nov 12 18:55:22 rescue kernel: [ 388.982623] [<c0244403>] warn_slowpath_null+0x13/0x20
> > Nov 12 18:55:22 rescue kernel: [ 388.982635] [<e2db5497>] wdev_cleanup_work+0xb7/0xe0 [cfg80211]
> > Nov 12 18:55:22 rescue kernel: [ 388.982657] [<c025cfa9>] run_workqueue+0x79/0x170
> > Nov 12 18:55:22 rescue kernel: [ 388.982665] [<c025d123>] worker_thread+0x83/0xe0
> > Nov 12 18:55:22 rescue kernel: [ 388.982673] [<c025fef4>] kthread+0x74/0x80
> > Nov 12 18:55:22 rescue kernel: [ 388.982681] [<c0203826>] kernel_thread_helper+0x6/0x10
> > Nov 12 18:55:22 rescue kernel: [ 388.982688] ---[ end trace 3f0348b3b0c6f4ff ]---
> > Nov 12 18:55:25 rescue dhcpcd[6700]: eth1: dhcpcd not running
>
> I've never seen this before. It looks like a scan is in progress when
> cfg80211 tries to do some cleanup - while bringing the interface down.
The patch you posted made this trace disappear.
>
> > Nov 14 21:31:21 rescue ifup: eth1 device: Dell
> > Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
> > Nov 14 21:31:21 rescue ifup: Version 01.01
> > Nov 14 21:31:21 rescue ifup: eth1 is controlled by ifplugd
> > Nov 14 21:31:21 rescue ifup: eth1 device: Dell
> > Nov 14 21:31:21 rescue ifup: TrueMobile 1150 Series PC Card
> > Nov 14 21:31:21 rescue ifup: Version 01.01
> > Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: WPA configured, but is untested
> > Nov 14 21:31:21 rescue ifup-wireless: eth1 warning: with this device
> > Nov 14 21:31:21 rescue ifup-wireless: eth1 starting wpa_supplicant
> > Nov 14 21:31:21 rescue kernel: [ 39.199513] ADDRCONF(NETDEV_UP): eth1: link is not ready
> > Nov 14 21:31:22 rescue ifup-dhcp: Starting DHCP4 client on eth1
> > Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: dhcpcd 3.2.3 starting
> > Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: hardware address = 00:02:2d:70:31:3b
> > Nov 14 21:31:22 rescue dhcpcd[3584]: eth1: broadcasting for a lease
> > Nov 14 21:31:22 rescue ifup-dhcp: .
>
> <snip dhcp log> This isn't interesting. If wpa_supplicant hasn't
> connected you to an AP, dhcpcd isn't going to find anything.
>
> > It first tryes to connect to an AP using WPA, but it fails.
> > Thereafter it connects to a second AP using WEP.
>
> Can you provide wpa_supplicant logs? With a reasonable amount of
> debug. -dd should do.
>
Attached you will find the wpa_supplicant.log created with the
following command line:
wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
>
> > Another issue I have with the the orinoco_cs module is the following:
> > During suspend and resume there is a two minutes timeout period.
>
> > More precisely, after I start to suspend the laptop the screen
> > goes black, the message
> > s2disk: snapshotting the system
> > appears and then there is a two minutes period where the screen stays black
> > and nothing happens. After the two minutes, the messages snapshot ready
> > appears, the snapshot image is saved to the disk and the laptop turns off.
> > On resume, the kernel founds the snapshot image, loads it and then
> > stays two minutes doing nothing. After the two minutes, the text
> > s2disk: returned to userspace
> > appears on screen, there is some disk activity and then the sistem is back.
> >
> > If I blacklist the orinoco_cs module, then suspend and resume work properly.
> >
> > I have no idea if the two problems are related or not. If any of the issues
> > has been already discussed, please point me where I can find such discussion.
>
> This is new. Depending on your kernel config, orinoco will either try
> to keep a copy of firmware which it re-flashes on resume, or try read
> the firmware on suspend, which is freed on resume. Both worked circa
> 2.6.32.
>
> > If you need more informations or you want me to test some code let me know.
>
> A wpa_supplicant log please. Note that the laptop I used to develop
> for (and on) has moved on, so there's only a limited number of things
> I can do to debug the issue.
If things don't go on, I will figure a way to give you access to the
truemobile card.
Regards.
Giacomo
[-- Attachment #2: wpa_supplicant.log --]
[-- Type: text/plain, Size: 4387 bytes --]
Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'wpa_supplicant.conf' -> '/root/wpa_supplicant.conf'
Reading configuration file '/root/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=5):
43 6f 6d 65 73 Comes
PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
key_mgmt: 0x2
priority=5 (0x5)
proto: 0x1
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
id=0 ssid='Comes'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0x5
capabilities: key_mgmt 0x5 enc 0x7 flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:02:2d:70:31:3b
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=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 65 86 3e 36 18 13 57 3a b2 46 2f 88 c6 00 3e 7d
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=10 (from group name 'wheel')
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
Scan timeout - try to get results
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
No keys have been configured - skip key clearing
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
[not found] ` <20101126040742.GA5238@monopoli.naic.edu>
@ 2010-11-28 16:10 ` Dave Kilroy
2010-11-30 2:19 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-11-28 16:10 UTC (permalink / raw)
To: Giacomo Comes, linux-wireless
On Fri, Nov 26, 2010 at 4:07 AM, Giacomo Comes <comes@naic.edu> wrote:
> On Thu, Nov 25, 2010 at 07:12:28PM +0000, Dave Kilroy wrote:
>>
>> > Attached you will find the wpa_supplicant.log created with the
>> > following command line:
>> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
>>
>> <paste>
>> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver
>> 'default' ctrl_interface 'N/A' bridge 'N/A'
>> ...
>> WEXT: cfg80211-based driver detected
>> ...
>> Driver did not support SIOCSIWENCODEEXT
>> </paste>
>>
>> eh? This looks like the problem. The driver should definitely support
>> this via the cfg80211 wrappers.
>>
>> You might try explicitly forcing wpa_supplicant to use the WEXT driver
>> with -Dwext, though I think the netlink interface ought to work as
>> well.
>
> Done. wpa_supplicant.log looks exactly the same except the line:
> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
> is replaced with:
> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> as it should be.
>
> One thing that I forgot to mention is that when I run wpa_supplicant,
> on the standard error are printed the following messages:
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
> ioctl[SIOCSIWSCAN]: Device or resource busy
> ioctl[SIOCSIWSCAN]: Device or resource busy
> ioctl[SIOCSIWSCAN]: Device or resource busy
> and so on until I interrupt wpa_supplicant.
>
>>
>> Check whether CONFIG_CFG80211_WEXT is configured in your kernel (it should be).
>
> It is.
>
>>
>> Also ensure that you're not trying to use CCMP. orinoco only supports
>> WPA with TKIP encryption.
>
> wpa_supplicant.conf contains:
> network={
> ssid="Comes"
> psk="<password>"
> key_mgmt=WPA-PSK
> priority=5
> proto=WPA
> }
Just had a closer look at your log. wpa_supplicant is clearing keys 4
and 5, which is why you're getting invalid arguments reported. This
shouldn't affect driver behaviour.
After that, something seems to go wrong with scanning. Try a plain
scan with wpa_supplicant turned off. Do you get any results?
iw dev eth1 scan
iwlist eth1 scan
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-11-28 16:10 ` Dave Kilroy
@ 2010-11-30 2:19 ` Giacomo Comes
2010-12-01 21:52 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-11-30 2:19 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
>
> Just had a closer look at your log. wpa_supplicant is clearing keys 4
> and 5, which is why you're getting invalid arguments reported. This
> shouldn't affect driver behaviour.
>
> After that, something seems to go wrong with scanning. Try a plain
> scan with wpa_supplicant turned off. Do you get any results?
>
> iw dev eth1 scan
> iwlist eth1 scan
>
> Dave.
After a reboot and without configuring the wireless interface,
iw dev eth1 scan
gives:
command failed: Network is down (-100)
and
iwlist eth1 scan
gives:
eth1 Interface doesn't support scanning : Network is down
I was trying to associate the wireless card using iwconfig:
iwconfig eth1 mode managed key <key>
iwconfig eth1 essid <essid>
but the card does not associate with the AP.
Isn't that supposed to work or am I missing something?
Buy the way, if I configure the wireless interface with yast
using WEP (the only way I can make the truemobile
card work) then iw dev eth1 scan gives:
BSS 00:18:f8:c6:04:05 (on eth1)
TSF: 21366823341 usec (0d, 05:56:06)
freq: 2412
beacon interval: 100
capability: ESS Privacy PBCC (0x0051)
signal: -60.00 dBm
last seen: 88 ms ago
SSID: ssid1
Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
DS Parameter set: channel 1
ERP: NonERP_Present Use_Protection Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
BSS 00:13:10:aa:89:4b (on eth1)
TSF: 12179691 usec (0d, 00:00:12)
freq: 2437
beacon interval: 100
capability: ESS Privacy PBCC ShortSlotTime (0x0451)
signal: -27.00 dBm
last seen: 48 ms ago
SSID: ssid2
Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
DS Parameter set: channel 6
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP
* Authentication suites: PSK
and iwlist eth1 scan gives:
eth1 Scan completed :
Cell 01 - Address: 00:18:F8:C6:04:05
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=58/70 Signal level=-52 dBm
Encryption key:on
ESSID:"ssid1"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000504cfa466
Extra: Last beacon: 248ms ago
IE: Unknown: 00076C696E6B737973
IE: Unknown: 010582848B962C
IE: Unknown: 030101
IE: Unknown: 2A0107
IE: Unknown: 32080C1218243048606C
Cell 02 - Address: 00:13:10:AA:89:4B
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-27 dBm
Encryption key:on
ESSID:"ssid2"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000000bf9a76e
Extra: Last beacon: 208ms ago
IE: Unknown: 0005436F6D6573
IE: Unknown: 010582848B962C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 32080C1218243048606C
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
I hope this help.
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-11-30 2:19 ` Giacomo Comes
@ 2010-12-01 21:52 ` Dave Kilroy
2010-12-02 0:22 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-01 21:52 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
> On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
>>
>> Just had a closer look at your log. wpa_supplicant is clearing keys 4
>> and 5, which is why you're getting invalid arguments reported. This
>> shouldn't affect driver behaviour.
>>
>> After that, something seems to go wrong with scanning. Try a plain
>> scan with wpa_supplicant turned off. Do you get any results?
>
> After a reboot and without configuring the wireless interface,
> iw dev eth1 scan
> gives:
> command failed: Network is down (-100)
The interface need to be up to scan:
ifconfig eth1 up
> I was trying to associate the wireless card using iwconfig:
> iwconfig eth1 mode managed key <key>
> iwconfig eth1 essid <essid>
> but the card does not associate with the AP.
> Isn't that supposed to work or am I missing something?
Was that AP using WEP or WPA? The former should work (with the
interface up, and all the parameters being set correctly). The latter
won't.
> Buy the way, if I configure the wireless interface with yast
> using WEP (the only way I can make the truemobile
> card work) then iw dev eth1 scan gives:
> BSS 00:13:10:aa:89:4b (on eth1)
> TSF: 12179691 usec (0d, 00:00:12)
> freq: 2437
> beacon interval: 100
> capability: ESS Privacy PBCC ShortSlotTime (0x0451)
> signal: -27.00 dBm
> last seen: 48 ms ago
> SSID: ssid2
> Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
> DS Parameter set: channel 6
> ERP: Barker_Preamble_Mode
> Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
> WPA: * Version: 1
> * Group cipher: TKIP
> * Pairwise ciphers: TKIP
> * Authentication suites: PSK
That's what I wanted to see. So the card is able to scan, but your
wpa_supplicant log indicates it is continuously timing out the scans.
I don't know what is going on there.
What you can try is to turn off wpa_supplicant roaming, and force
wpa_supplicant to connect to the AP with highest priority in your
config. Set ap_scan=2 in wpa_supplicant.conf, and set
group=TKIP
pairwise=TKIP
in the network block.
This also prevents wpa_supplicant trying to connect to an AP using
BSSID, which the agere cards don't support.
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-01 21:52 ` Dave Kilroy
@ 2010-12-02 0:22 ` Giacomo Comes
2010-12-02 17:46 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-02 0:22 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 3086 bytes --]
On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
> > On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
> >>
> >> Just had a closer look at your log. wpa_supplicant is clearing keys 4
> >> and 5, which is why you're getting invalid arguments reported. This
> >> shouldn't affect driver behaviour.
> >>
> >> After that, something seems to go wrong with scanning. Try a plain
> >> scan with wpa_supplicant turned off. Do you get any results?
> >
> > After a reboot and without configuring the wireless interface,
> > iw dev eth1 scan
> > gives:
> > command failed: Network is down (-100)
>
> The interface need to be up to scan:
>
> ifconfig eth1 up
Ok, my bad. After I put the interface up the scan works.
>
> > I was trying to associate the wireless card using iwconfig:
> > iwconfig eth1 mode managed key <key>
> > iwconfig eth1 essid <essid>
> > but the card does not associate with the AP.
> > Isn't that supposed to work or am I missing something?
>
> Was that AP using WEP or WPA? The former should work (with the
> interface up, and all the parameters being set correctly). The latter
> won't.
The AP was using WEP, but it didn't associate because I didn't put up
the interface. After doing it, it works.
>
> > Buy the way, if I configure the wireless interface with yast
> > using WEP (the only way I can make the truemobile
> > card work) then iw dev eth1 scan gives:
> > BSS 00:13:10:aa:89:4b (on eth1)
> > TSF: 12179691 usec (0d, 00:00:12)
> > freq: 2437
> > beacon interval: 100
> > capability: ESS Privacy PBCC ShortSlotTime (0x0451)
> > signal: -27.00 dBm
> > last seen: 48 ms ago
> > SSID: ssid2
> > Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
> > DS Parameter set: channel 6
> > ERP: Barker_Preamble_Mode
> > Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
> > WPA: * Version: 1
> > * Group cipher: TKIP
> > * Pairwise ciphers: TKIP
> > * Authentication suites: PSK
>
> That's what I wanted to see. So the card is able to scan, but your
> wpa_supplicant log indicates it is continuously timing out the scans.
> I don't know what is going on there.
>
> What you can try is to turn off wpa_supplicant roaming, and force
> wpa_supplicant to connect to the AP with highest priority in your
> config. Set ap_scan=2 in wpa_supplicant.conf, and set
>
> group=TKIP
> pairwise=TKIP
>
> in the network block.
>
> This also prevents wpa_supplicant trying to connect to an AP using
> BSSID, which the agere cards don't support.
>
Running:
wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
wpa_supplicant.conf content:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2
network={
ssid="Comes"
psk="<password>"
key_mgmt=WPA-PSK
priority=5
proto=WPA
group=TKIP
pairwise=TKIP
}
wpa_supplicant.log attached.
Giacomo
[-- Attachment #2: wpa_supplicant.log --]
[-- Type: text/plain, Size: 18593 bytes --]
Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'wpa_supplicant.conf' -> '/root/wpa_supplicant.conf'
Reading configuration file '/root/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0'
ap_scan=2
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=5):
43 6f 6d 65 73 Comes
PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
key_mgmt: 0x2
priority=5 (0x5)
proto: 0x1
group: 0x8
pairwise: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
id=0 ssid='Comes'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0x5
capabilities: key_mgmt 0x5 enc 0x7 flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:02:2d:7e:fc:cb
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=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 85 92 32 af f8 e1 55 09 8a 9c 35 74 b7 fa 7e 0b
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=0
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 4
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 5
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
Authentication with 00:00:00:00:00:00 timed out.
BSSID 00:00:00:00:00:00 blacklist count incremented to 6
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
wpa_driver_wext_associate: assoc failed because set_auth_param(IW_AUTH_MFP) failed
Association request to the driver failed
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
No keys have been configured - skip key clearing
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-02 0:22 ` Giacomo Comes
@ 2010-12-02 17:46 ` Dave Kilroy
2010-12-03 0:10 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-02 17:46 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Thu, Dec 2, 2010 at 12:22 AM, Giacomo Comes <comes@naic.edu> wrote:
> On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
>> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
>> wpa_supplicant log indicates it is continuously timing out the scans.
>> I don't know what is going on there.
>>
>> What you can try is to turn off wpa_supplicant roaming, and force
>> wpa_supplicant to connect to the AP with highest priority in your
>> config. Set ap_scan=2 in wpa_supplicant.conf, and set
>>
>> group=TKIP
>> pairwise=TKIP
>>
>> in the network block.
>>
>> This also prevents wpa_supplicant trying to connect to an AP using
>> BSSID, which the agere cards don't support.
>
> Running:
> wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
>
> wpa_supplicant.conf content:
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> ap_scan=2
>
> network={
> ssid="Comes"
> psk="<password>"
> key_mgmt=WPA-PSK
> priority=5
> proto=WPA
>
> group=TKIP
> pairwise=TKIP
> }
OK, looks like you're using a newer wpa_supplicant that tries to use
IW_AUTH_MFP which orinoco doesn't know about. I can modify the driver
to silently pass these calls through, but it would be nice if
wpa_supplicant didn't fail because a driver didn't support a
particular option.
I'll put together a patch to accept an IW_AUTH_MFP call set to NONE or
DISABLED, and fail on REQUIRED. In the meantime you could try use an
older wpa_supplicant. I think I was using 0.7.2 before, but I can't be
sure.
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-02 17:46 ` Dave Kilroy
@ 2010-12-03 0:10 ` Giacomo Comes
[not found] ` <AANLkTinLaa+dOiq67DAt+KYfnxUEkNgWEiE2x1NtT9RE@mail.gmail.com>
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-03 0:10 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 2318 bytes --]
On Thu, Dec 02, 2010 at 05:46:54PM +0000, Dave Kilroy wrote:
> On Thu, Dec 2, 2010 at 12:22 AM, Giacomo Comes <comes@naic.edu> wrote:
> > On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
> >> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
> >> wpa_supplicant log indicates it is continuously timing out the scans.
> >> I don't know what is going on there.
> >>
> >> What you can try is to turn off wpa_supplicant roaming, and force
> >> wpa_supplicant to connect to the AP with highest priority in your
> >> config. Set ap_scan=2 in wpa_supplicant.conf, and set
> >>
> >> group=TKIP
> >> pairwise=TKIP
> >>
> >> in the network block.
> >>
> >> This also prevents wpa_supplicant trying to connect to an AP using
> >> BSSID, which the agere cards don't support.
> >
> > Running:
> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
> >
> > wpa_supplicant.conf content:
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=0
> > ap_scan=2
> >
> > network={
> > ssid="Comes"
> > psk="<password>"
> > key_mgmt=WPA-PSK
> > priority=5
> > proto=WPA
> >
> > group=TKIP
> > pairwise=TKIP
> > }
>
> OK, looks like you're using a newer wpa_supplicant that tries to use
> IW_AUTH_MFP which orinoco doesn't know about. I can modify the driver
> to silently pass these calls through, but it would be nice if
> wpa_supplicant didn't fail because a driver didn't support a
> particular option.
>
> I'll put together a patch to accept an IW_AUTH_MFP call set to NONE or
> DISABLED, and fail on REQUIRED. In the meantime you could try use an
> older wpa_supplicant. I think I was using 0.7.2 before, but I can't be
> sure.
wpa_supplicant version is 0.7.3. It's the one included in suse 11.3.
About your patch, things are getting better.
I have applied the patch and run wpa_supplicant with the configuration
showed above. It works, the card associates with the AP.
The succesful log is attached.
After I removed from wpa_supplicant.conf the two lines:
group=TKIP
pairwise=TKIP
the association still works.
But after removing the line: ap_scan=2
the association fails.
The log is in the second attachment.
Also I have included in the 3rd attachement wpa_supplicant.log when
NetworkManager is used.
Giacomo
[-- Attachment #2: wpa_supplicant_ok.log --]
[-- Type: text/plain, Size: 15590 bytes --]
Initializing interface 'eth1' conf 'wpa_supplicant1.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'wpa_supplicant1.conf' -> '/root/wpa_supplicant1.conf'
Reading configuration file '/root/wpa_supplicant1.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
ap_scan=2
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=5):
43 6f 6d 65 73 Comes
PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
key_mgmt: 0x2
priority=5 (0x5)
proto: 0x1
group: 0x8
pairwise: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
id=0 ssid='Comes'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0x5
capabilities: key_mgmt 0x5 enc 0x7 flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:02:2d:70:31:3b
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=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 65 86 3e 36 18 13 57 3a b2 46 2f 88 c6 00 3e 7d
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=10 (from group name 'wheel')
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
State: DISCONNECTED -> SCANNING
Trying to associate with SSID 'Comes'
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: No WPA/RSN IE available from association info
WPA: Set cipher suites based on configuration
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_psk
Setting authentication timeout: 60 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8c07 len=32
AssocReq IE wireless event - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:13:10:aa:89:4b
Association info event
req_ies - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:13:10:aa:89:4b
No keys have been configured - skip key clearing
Select network based on association information
Network configuration found for the current AP
WPA: Using WPA IE from AssocReq to set cipher suites
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: not using MGMT group cipher
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
Associated with 00:13:10:aa:89:4b
WPA: Association event - clear replay counter
WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RX EAPOL from 00:13:10:aa:89:4b
RX EAPOL - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Setting authentication timeout: 10 sec 0 usec
IEEE 802.1X RX: version=1 type=3 length=95
EAPOL-Key type=254
key_info 0x89 (ver=1 keyidx=0 rsvd=0 Pairwise Ack)
key_length=32 key_data_length=0
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 01
key_nonce - hexdump(len=32): 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
WPA: RX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 00 89 00 20 00 00 00 00 00 00 00 01 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
State: ASSOCIATED -> 4WAY_HANDSHAKE
WPA: RX message 1 of 4-Way Handshake from 00:13:10:aa:89:4b (ver=1)
WPA: Renewed SNonce - hexdump(len=32): 0b 6f 62 ce db 30 8a 3b 14 f0 eb 3d bb af e9 b7 bb 87 f0 a1 57 c3 d6 04 82 46 fe 13 14 c4 cf 2e
WPA: PTK derivation - A1=00:02:2d:70:31:3b A2=00:13:10:aa:89:4b
WPA: PMK - hexdump(len=32): [REMOVED]
WPA: PTK - hexdump(len=64): [REMOVED]
WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: Sending EAPOL-Key 2/4
WPA: TX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 09 00 20 00 00 00 00 00 00 00 01 0b 6f 62 ce db 30 8a 3b 14 f0 eb 3d bb af e9 b7 bb 87 f0 a1 57 c3 d6 04 82 46 fe 13 14 c4 cf 2e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e2 e0 e8 f0 e9 2e 89 d9 75 d2 2a 01 ea 21 33 ec 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RX EAPOL from 00:13:10:aa:89:4b
RX EAPOL - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e9 b8 84 f7 58 12 13 3c 61 ae c3 e1 6a 7b 79 f2 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
IEEE 802.1X RX: version=1 type=3 length=119
EAPOL-Key type=254
key_info 0x1c9 (ver=1 keyidx=0 rsvd=0 Pairwise Install Ack MIC)
key_length=32 key_data_length=24
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 02
key_nonce - hexdump(len=32): 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6
key_iv - hexdump(len=16): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): e9 b8 84 f7 58 12 13 3c 61 ae c3 e1 6a 7b 79 f2
WPA: RX EAPOL-Key - hexdump(len=123): 01 03 00 77 fe 01 c9 00 20 00 00 00 00 00 00 00 02 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e9 b8 84 f7 58 12 13 3c 61 ae c3 e1 6a 7b 79 f2 00 18 dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
State: 4WAY_HANDSHAKE -> 4WAY_HANDSHAKE
WPA: RX message 3 of 4-Way Handshake from 00:13:10:aa:89:4b (ver=1)
WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: WPA IE in EAPOL-Key - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: No WPA/RSN IE for this AP known. Trying to get from scan results
Received 0 bytes of scan results (0 BSSes)
BSS: Start scan result update 1
WPA: Could not find AP from the scan results
WPA: Sending EAPOL-Key 4/4
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 01 09 00 20 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 85 78 6b 70 16 73 d0 71 8b ad 7c f0 97 64 64 5e 00 00
WPA: Installing PTK to the driver.
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=0 set_tx=1 seq_len=6 key_len=32
State: 4WAY_HANDSHAKE -> GROUP_HANDSHAKE
RX EAPOL from 00:13:10:aa:89:4b
RX EAPOL - hexdump(len=131): 01 03 00 7f fe 03 a1 00 20 00 00 00 00 00 00 00 03 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c5 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9a 58 3b 6c a8 47 27 18 ce 97 1e e2 fc 03 5b bb 00 20 e6 09 a7 99 a1 83 0b 6f ea 9b fa 08 2d 74 cb 99 94 e3 31 81 6e 18 44 65 0e b5 1d 4d 6e 08 65 7e
IEEE 802.1X RX: version=1 type=3 length=127
EAPOL-Key type=254
key_info 0x3a1 (ver=1 keyidx=2 rsvd=0 Group Ack MIC Secure)
key_length=32 key_data_length=32
replay_counter - hexdump(len=8): 00 00 00 00 00 00 00 03
key_nonce - hexdump(len=32): 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c5
key_iv - hexdump(len=16): c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c7
key_rsc - hexdump(len=8): 00 00 00 00 00 00 00 00
key_id (reserved) - hexdump(len=8): 00 00 00 00 00 00 00 00
key_mic - hexdump(len=16): 9a 58 3b 6c a8 47 27 18 ce 97 1e e2 fc 03 5b bb
WPA: RX EAPOL-Key - hexdump(len=131): 01 03 00 7f fe 03 a1 00 20 00 00 00 00 00 00 00 03 94 f9 ea a6 d3 de d8 23 88 f1 a0 64 8f 67 9a 08 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c5 c7 a4 68 35 94 8b 92 4f 6c aa 60 db a2 29 53 c7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9a 58 3b 6c a8 47 27 18 ce 97 1e e2 fc 03 5b bb 00 20 e6 09 a7 99 a1 83 0b 6f ea 9b fa 08 2d 74 cb 99 94 e3 31 81 6e 18 44 65 0e b5 1d 4d 6e 08 65 7e
WPA: RX message 1 of Group Key Handshake from 00:13:10:aa:89:4b (ver=1)
State: GROUP_HANDSHAKE -> GROUP_HANDSHAKE
WPA: Group Key - hexdump(len=32): [REMOVED]
WPA: Installing GTK to the driver (keyidx=2 tx=0 len=32).
WPA: RSC - hexdump(len=6): 00 00 00 00 00 00
wpa_driver_wext_set_key: alg=2 key_idx=2 set_tx=0 seq_len=6 key_len=32
WPA: Sending EAPOL-Key 2/2
WPA: TX EAPOL-Key - hexdump(len=99): 01 03 00 5f fe 03 21 00 20 00 00 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4b 78 b2 29 17 f0 e4 48 ef b1 e2 90 9b 62 0a 83 00 00
WPA: Key negotiation completed with 00:13:10:aa:89:4b [PTK=TKIP GTK=TKIP]
Cancelling authentication timeout
State: GROUP_HANDSHAKE -> COMPLETED
CTRL-EVENT-CONNECTED - Connection to 00:13:10:aa:89:4b completed (auth) [id=0 id_str=]
wpa_driver_wext_set_operstate: operstate 0->1 (UP)
netlink: Operstate: linkmode=-1, operstate=6
EAPOL: External notification - portValid=1
EAPOL: External notification - EAP success=1
EAPOL: SUPP_PAE entering state AUTHENTICATING
EAPOL: SUPP_BE entering state SUCCESS
EAP: EAP entering state DISABLED
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: Supplicant port status: Authorized
EAPOL: SUPP_BE entering state IDLE
EAPOL authentication completed successfully
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
EAPOL: startWhen --> 0
EAPOL: disable timer tick
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
wpa_driver_wext_deauthenticate
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=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: COMPLETED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 1->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6
[-- Attachment #3: wpa_supplicant_fail.log --]
[-- Type: text/plain, Size: 3968 bytes --]
Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file 'wpa_supplicant.conf' -> '/root/wpa_supplicant.conf'
Reading configuration file '/root/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=5):
43 6f 6d 65 73 Comes
PSK (ASCII passphrase) - hexdump_ascii(len=18): [REMOVED]
key_mgmt: 0x2
priority=5 (0x5)
proto: 0x1
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 5
id=0 ssid='Comes'
WEXT: cfg80211-based driver detected
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0x5
capabilities: key_mgmt 0x5 enc 0x7 flags 0x0
netlink: Operstate: linkmode=1, operstate=5
Own MAC address: 00:02:2d:70:31:3b
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=4 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
WPS: UUID based on MAC address - hexdump(len=16): 65 86 3e 36 18 13 57 3a b2 46 2f 88 c6 00 3e 7d
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: Supplicant port status: Unauthorized
EAPOL: Supplicant port status: Unauthorized
ctrl_interface_group=10 (from group name 'wheel')
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
Wireless event: cmd=0x8b1a len=8
State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
Scan timeout - try to get results
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.
Setting scan request: 1 sec 0 usec
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
No keys have been configured - skip key clearing
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portValid=0
EAPOL: Supplicant port status: Unauthorized
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Cancelling scan request
Cancelling authentication timeout
netlink: Operstate: linkmode=0, operstate=6
[-- Attachment #4: wpa_supplicant_nm_fail.log --]
[-- Type: text/plain, Size: 6606 bytes --]
1291334455.185942: dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
1291334455.204160: Providing DBus service 'fi.w1.wpa_supplicant1'.
1291334455.209388: Providing DBus service 'fi.epitest.hostap.WPASupplicant'.
1291334455.211357: Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
1291334455.211612: WEXT: cfg80211-based driver detected
1291334455.211825: SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0x5
1291334455.211849: capabilities: key_mgmt 0x5 enc 0x7 flags 0x0
1291334455.242013: netlink: Operstate: linkmode=1, operstate=5
1291334455.395240: Own MAC address: 00:02:2d:70:31:3b
1291334455.395325: wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
1291334455.418714: wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
1291334455.455154: wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
1291334455.499613: wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
1291334455.536584: wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
1291334455.536826: Driver did not support SIOCSIWENCODEEXT
1291334455.536847: wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
1291334455.536911: Driver did not support SIOCSIWENCODEEXT
1291334455.536929: wpa_driver_wext_set_countermeasures
1291334455.544624: RSN: flushing PMKID list in the driver
1291334455.544712: State: DISCONNECTED -> INACTIVE
1291334455.544829: WPS: UUID based on MAC address - hexdump(len=16): 65 86 3e 36 18 13 57 3a b2 46 2f 88 c6 00 3e 7d
1291334455.578382: EAPOL: SUPP_PAE entering state DISCONNECTED
1291334455.578453: EAPOL: Supplicant port status: Unauthorized
1291334455.578472: EAPOL: KEY_RX entering state NO_KEY_RECEIVE
1291334455.578489: EAPOL: SUPP_BE entering state INITIALIZE
1291334455.578506: EAP: EAP entering state DISABLED
1291334455.578520: EAPOL: Supplicant port status: Unauthorized
1291334455.578593: EAPOL: Supplicant port status: Unauthorized
1291334455.578651: dbus: Register interface object '/fi/w1/wpa_supplicant1/Interfaces/1'
1291334455.581620: Added interface eth1
1291334455.593117: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
1291334455.593209: RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
1291334455.593232: Wireless event: cmd=0x8b06 len=8
1291334455.593266: RTM_NEWLINK: operstate=0 ifi_flags=0x1043 ([UP][RUNNING])
1291334455.593281: RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
1291334455.593293: Wireless event: cmd=0x8b1a len=8
1291334455.593308: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
1291334455.593322: RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
1291334455.593520: Setting scan request: 0 sec 0 usec
1291334455.594140: Setting scan request: 0 sec 0 usec
1291334455.606652: State: INACTIVE -> SCANNING
1291334455.607495: Starting AP scan for wildcard SSID
1291334455.608412: Scan requested (ret=0) - scan timeout 5 seconds
1291334455.613314: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334456.579602: EAPOL: disable timer tick
1291334456.579683: EAPOL: Supplicant port status: Unauthorized
1291334460.611650: Scan timeout - try to get results
1291334460.612052: Failed to get scan results
1291334460.612094: Failed to get scan results - try scanning again
1291334460.612116: State: SCANNING -> INACTIVE
1291334460.617024: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334476.003602: Setting scan request: 0 sec 0 usec
1291334476.003785: State: INACTIVE -> SCANNING
1291334476.003932: Starting AP scan for wildcard SSID
1291334476.004185: Scan requested (ret=-1) - scan timeout 5 seconds
1291334476.004357: Failed to initiate AP scan.
1291334476.004382: State: SCANNING -> INACTIVE
1291334476.004521: Setting scan request: 1 sec 0 usec
1291334476.009841: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334477.005651: No enabled networks - do not scan
1291334477.005733: State: INACTIVE -> INACTIVE
1291334481.007606: Scan timeout - try to get results
1291334481.007847: Failed to get scan results
1291334481.007875: Failed to get scan results - try scanning again
1291334481.007898: State: INACTIVE -> INACTIVE
1291334506.004852: Setting scan request: 0 sec 0 usec
1291334506.005044: State: INACTIVE -> SCANNING
1291334506.005195: Starting AP scan for wildcard SSID
1291334506.005410: Scan requested (ret=-1) - scan timeout 5 seconds
1291334506.005625: Failed to initiate AP scan.
1291334506.005658: State: SCANNING -> INACTIVE
1291334506.005802: Setting scan request: 1 sec 0 usec
1291334506.010377: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334507.006958: No enabled networks - do not scan
1291334507.007044: State: INACTIVE -> INACTIVE
1291334511.009583: Scan timeout - try to get results
1291334511.009804: Failed to get scan results
1291334511.009833: Failed to get scan results - try scanning again
1291334511.009855: State: INACTIVE -> INACTIVE
1291334546.002272: Setting scan request: 0 sec 0 usec
1291334546.002470: State: INACTIVE -> SCANNING
1291334546.002670: Starting AP scan for wildcard SSID
1291334546.002881: Scan requested (ret=-1) - scan timeout 5 seconds
1291334546.003050: Failed to initiate AP scan.
1291334546.003078: State: SCANNING -> INACTIVE
1291334546.003219: Setting scan request: 1 sec 0 usec
1291334546.007851: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334547.004375: No enabled networks - do not scan
1291334547.004460: State: INACTIVE -> INACTIVE
1291334551.005668: Scan timeout - try to get results
1291334551.005889: Failed to get scan results
1291334551.005919: Failed to get scan results - try scanning again
1291334551.005945: State: INACTIVE -> INACTIVE
1291334596.005083: Setting scan request: 0 sec 0 usec
1291334596.005289: State: INACTIVE -> SCANNING
1291334596.005440: Starting AP scan for wildcard SSID
1291334596.005688: Scan requested (ret=-1) - scan timeout 5 seconds
1291334596.005866: Failed to initiate AP scan.
1291334596.005929: State: SCANNING -> INACTIVE
1291334596.006074: Setting scan request: 1 sec 0 usec
1291334596.010628: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1
1291334597.007229: No enabled networks - do not scan
1291334597.007312: State: INACTIVE -> INACTIVE
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
[not found] ` <AANLkTinLaa+dOiq67DAt+KYfnxUEkNgWEiE2x1NtT9RE@mail.gmail.com>
@ 2010-12-03 17:29 ` Dave Kilroy
2010-12-03 20:23 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-03 17:29 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Fri, Dec 3, 2010 at 5:23 PM, Dave Kilroy <kilroyd@googlemail.com> wrote:
> On Fri, Dec 3, 2010 at 12:10 AM, Giacomo Comes <comes@naic.edu> wrote:
>> On Thu, Dec 02, 2010 at 05:46:54PM +0000, Dave Kilroy wrote:
>>> On Thu, Dec 2, 2010 at 12:22 AM, Giacomo Comes <comes@naic.edu> wrote:
>>> > On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
>>> >> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
>>> >> wpa_supplicant log indicates it is continuously timing out the scans.
>>> >> I don't know what is going on there.
>>> >>
>>> >> What you can try is to turn off wpa_supplicant roaming, and force
>>> >> wpa_supplicant to connect to the AP with highest priority in your
>>> >> config. Set ap_scan=2 in wpa_supplicant.conf, and set
>>> >>
>>> >> group=TKIP
>>> >> pairwise=TKIP
>>> >>
>>> >> in the network block.
>>> >>
>>> >> This also prevents wpa_supplicant trying to connect to an AP using
>>> >> BSSID, which the agere cards don't support.
>>> >
>>> > Running:
>>> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
>>> >
>>> > wpa_supplicant.conf content:
>>> > ctrl_interface=/var/run/wpa_supplicant
>>> > ctrl_interface_group=0
>>> > ap_scan=2
>>> >
>>> > network={
>>> > ssid="Comes"
>>> > psk="<password>"
>>> > key_mgmt=WPA-PSK
>>> > priority=5
>>> > proto=WPA
>>> >
>>> > group=TKIP
>>> > pairwise=TKIP
>>> > }
>>>
>>> OK, looks like you're using a newer wpa_supplicant that tries to use
>>> IW_AUTH_MFP which orinoco doesn't know about. I can modify the driver
>>> to silently pass these calls through, but it would be nice if
>>> wpa_supplicant didn't fail because a driver didn't support a
>>> particular option.
>>>
>>> I'll put together a patch to accept an IW_AUTH_MFP call set to NONE or
>>> DISABLED, and fail on REQUIRED. In the meantime you could try use an
>>> older wpa_supplicant. I think I was using 0.7.2 before, but I can't be
>>> sure.
>>
>> wpa_supplicant version is 0.7.3. It's the one included in suse 11.3.
>>
>> About your patch, things are getting better.
>>
>> I have applied the patch and run wpa_supplicant with the configuration
>> showed above. It works, the card associates with the AP.
>> The succesful log is attached.
>> After I removed from wpa_supplicant.conf the two lines:
>> group=TKIP
>> pairwise=TKIP
>> the association still works.
>>
>> But after removing the line: ap_scan=2
>> the association fails.
>> The log is in the second attachment.
>>
>> Also I have included in the 3rd attachement wpa_supplicant.log when
>> NetworkManager is used.
> The failure and NM case are the same. There is still a problem with
> scanning. wpa_supplicant initiates a scan, and it appears to time out.
> Without scan results wpa_supplicant is not able to select an
> appropriate AP.
>
> Is the driver reporting any scanning issues in dmesg while
> wpa_supplicant is running?
Apologies, hit the wrong button again. Including linux-wireless
> Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-03 17:29 ` Dave Kilroy
@ 2010-12-03 20:23 ` Giacomo Comes
2010-12-03 22:49 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-03 20:23 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Fri, Dec 03, 2010 at 05:29:59PM +0000, Dave Kilroy wrote:
> On Fri, Dec 3, 2010 at 5:23 PM, Dave Kilroy <kilroyd@googlemail.com> wrote:
> > On Fri, Dec 3, 2010 at 12:10 AM, Giacomo Comes <comes@naic.edu> wrote:
> >> On Thu, Dec 02, 2010 at 05:46:54PM +0000, Dave Kilroy wrote:
> >>> On Thu, Dec 2, 2010 at 12:22 AM, Giacomo Comes <comes@naic.edu> wrote:
> >>> > On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
> >>> >> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <comes@naic.edu> wrote:
> >>> >> wpa_supplicant log indicates it is continuously timing out the scans.
> >>> >> I don't know what is going on there.
> >>> >>
> >>> >> What you can try is to turn off wpa_supplicant roaming, and force
> >>> >> wpa_supplicant to connect to the AP with highest priority in your
> >>> >> config. Set ap_scan=2 in wpa_supplicant.conf, and set
> >>> >>
> >>> >> group=TKIP
> >>> >> pairwise=TKIP
> >>> >>
> >>> >> in the network block.
> >>> >>
> >>> >> This also prevents wpa_supplicant trying to connect to an AP using
> >>> >> BSSID, which the agere cards don't support.
> >>> >
> >>> > Running:
> >>> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
> >>> >
> >>> > wpa_supplicant.conf content:
> >>> > ctrl_interface=/var/run/wpa_supplicant
> >>> > ctrl_interface_group=0
> >>> > ap_scan=2
> >>> >
> >>> > network={
> >>> > ssid="Comes"
> >>> > psk="<password>"
> >>> > key_mgmt=WPA-PSK
> >>> > priority=5
> >>> > proto=WPA
> >>> >
> >>> > group=TKIP
> >>> > pairwise=TKIP
> >>> > }
> >>>
> >>> OK, looks like you're using a newer wpa_supplicant that tries to use
> >>> IW_AUTH_MFP which orinoco doesn't know about. I can modify the driver
> >>> to silently pass these calls through, but it would be nice if
> >>> wpa_supplicant didn't fail because a driver didn't support a
> >>> particular option.
> >>>
> >>> I'll put together a patch to accept an IW_AUTH_MFP call set to NONE or
> >>> DISABLED, and fail on REQUIRED. In the meantime you could try use an
> >>> older wpa_supplicant. I think I was using 0.7.2 before, but I can't be
> >>> sure.
> >>
> >> wpa_supplicant version is 0.7.3. It's the one included in suse 11.3.
> >>
> >> About your patch, things are getting better.
> >>
> >> I have applied the patch and run wpa_supplicant with the configuration
> >> showed above. It works, the card associates with the AP.
> >> The succesful log is attached.
> >> After I removed from wpa_supplicant.conf the two lines:
> >> group=TKIP
> >> pairwise=TKIP
> >> the association still works.
> >>
> >> But after removing the line: ap_scan=2
> >> the association fails.
> >> The log is in the second attachment.
> >>
> >> Also I have included in the 3rd attachement wpa_supplicant.log when
> >> NetworkManager is used.
>
> > The failure and NM case are the same. There is still a problem with
> > scanning. wpa_supplicant initiates a scan, and it appears to time out.
> > Without scan results wpa_supplicant is not able to select an
> > appropriate AP.
> >
> > Is the driver reporting any scanning issues in dmesg while
> > wpa_supplicant is running?
In dmesg there is:
ADDRCONF(NETDEV_UP): eth1: link is not ready
and on standard error:
ioctl[SIOCSIWENCODEEXT]: Invalid argument
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-03 20:23 ` Giacomo Comes
@ 2010-12-03 22:49 ` Dave Kilroy
2010-12-04 3:36 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-03 22:49 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
>> >> But after removing the line: ap_scan=2
>> >> the association fails.
>> >> The log is in the second attachment.
>> >>
>> >> Also I have included in the 3rd attachement wpa_supplicant.log when
>> >> NetworkManager is used.
>>
>> > The failure and NM case are the same. There is still a problem with
>> > scanning. wpa_supplicant initiates a scan, and it appears to time out.
>> > Without scan results wpa_supplicant is not able to select an
>> > appropriate AP.
>> >
>> > Is the driver reporting any scanning issues in dmesg while
>> > wpa_supplicant is running?
>
> In dmesg there is:
> ADDRCONF(NETDEV_UP): eth1: link is not ready
>
> and on standard error:
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
Those are expected.
I'm at a loss. I've looked at the wpa_supplicant code, and had another
look at the driver. The scan should be a plain wildcard scan - which
you've identified works.
Does setting scan_ssid=1 in the wpa_supplicant network block change
the behaviour? That's usually only necessary for hidden SSIDs - but
I'd like to know if the scan succeeds in this case.
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-03 22:49 ` Dave Kilroy
@ 2010-12-04 3:36 ` Giacomo Comes
2010-12-04 12:01 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-04 3:36 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Fri, Dec 03, 2010 at 10:49:55PM +0000, Dave Kilroy wrote:
> >> >> But after removing the line: ap_scan=2
> >> >> the association fails.
> >> >> The log is in the second attachment.
> >> >>
> >> >> Also I have included in the 3rd attachement wpa_supplicant.log when
> >> >> NetworkManager is used.
> >>
> >> > The failure and NM case are the same. There is still a problem with
> >> > scanning. wpa_supplicant initiates a scan, and it appears to time out.
> >> > Without scan results wpa_supplicant is not able to select an
> >> > appropriate AP.
> >> >
> >> > Is the driver reporting any scanning issues in dmesg while
> >> > wpa_supplicant is running?
> >
> > In dmesg there is:
> > ADDRCONF(NETDEV_UP): eth1: link is not ready
> >
> > and on standard error:
> > ioctl[SIOCSIWENCODEEXT]: Invalid argument
>
> Those are expected.
>
> I'm at a loss. I've looked at the wpa_supplicant code, and had another
> look at the driver. The scan should be a plain wildcard scan - which
> you've identified works.
>
> Does setting scan_ssid=1 in the wpa_supplicant network block change
> the behaviour? That's usually only necessary for hidden SSIDs - but
> I'd like to know if the scan succeeds in this case.
No It doesn't work.
But I have more informations for you.
I have been testing different versions of wpa_supplicant
and I have found that if a use wpa_supplicant 0.7.0 or earlier,
it works. With 0.7.1 or newer it fails.
wpa_supplicant 0.7.0 works even without applying your patch.
I hope this helps.
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-04 3:36 ` Giacomo Comes
@ 2010-12-04 12:01 ` Dave Kilroy
2010-12-04 13:47 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-04 12:01 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
>> I'm at a loss. I've looked at the wpa_supplicant code, and had another
>> look at the driver. The scan should be a plain wildcard scan - which
>> you've identified works.
>>
>> Does setting scan_ssid=1 in the wpa_supplicant network block change
>> the behaviour? That's usually only necessary for hidden SSIDs - but
>> I'd like to know if the scan succeeds in this case.
>
> No It doesn't work.
> But I have more informations for you.
>
> I have been testing different versions of wpa_supplicant
> and I have found that if a use wpa_supplicant 0.7.0 or earlier,
> it works. With 0.7.1 or newer it fails.
> wpa_supplicant 0.7.0 works even without applying your patch.
I've set myself up so I can test with orinoco_usb. I can reproduce the
issue (or something that looks the same).
After much confusion, I suspect the initial scan is being triggered
before the hardware is ready. Internally, wpa_supplicant will do an
'ifconfig eth1 up' followed by an 'iwlist eth1 scan', and it seems the
driver/hardware wants more time between them.
Try the following (either in two command prompts, or with
wpa_supplicant in the background):
prompt1$ wpa_supplicant -dd -ieth1 ....
prompt2$ ifconfig eth1 down
prompt2$ ifconfig eth1 up
and see what wpa_supplicant is doing. If it has got scan results then
you're probably seeing what I am.
I need to have a think about how this needs to be fixed in the driver.
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-04 12:01 ` Dave Kilroy
@ 2010-12-04 13:47 ` Giacomo Comes
2010-12-04 14:40 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-04 13:47 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Sat, Dec 04, 2010 at 12:01:34PM +0000, Dave Kilroy wrote:
> >> I'm at a loss. I've looked at the wpa_supplicant code, and had another
> >> look at the driver. The scan should be a plain wildcard scan - which
> >> you've identified works.
> >>
> >> Does setting scan_ssid=1 in the wpa_supplicant network block change
> >> the behaviour? That's usually only necessary for hidden SSIDs - but
> >> I'd like to know if the scan succeeds in this case.
> >
> > No It doesn't work.
> > But I have more informations for you.
> >
> > I have been testing different versions of wpa_supplicant
> > and I have found that if a use wpa_supplicant 0.7.0 or earlier,
> > it works. With 0.7.1 or newer it fails.
> > wpa_supplicant 0.7.0 works even without applying your patch.
>
> I've set myself up so I can test with orinoco_usb. I can reproduce the
> issue (or something that looks the same).
>
> After much confusion, I suspect the initial scan is being triggered
> before the hardware is ready. Internally, wpa_supplicant will do an
> 'ifconfig eth1 up' followed by an 'iwlist eth1 scan', and it seems the
> driver/hardware wants more time between them.
>
> Try the following (either in two command prompts, or with
> wpa_supplicant in the background):
>
> prompt1$ wpa_supplicant -dd -ieth1 ....
>
> prompt2$ ifconfig eth1 down
> prompt2$ ifconfig eth1 up
>
> and see what wpa_supplicant is doing. If it has got scan results then
> you're probably seeing what I am.
You are right. After running ifconfig eth1 down,up on a second terminal,
while wpa_supplicant iis running on the first terminal,
it succesfully associates with the AP.
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-04 13:47 ` Giacomo Comes
@ 2010-12-04 14:40 ` Dave Kilroy
2010-12-06 4:28 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-04 14:40 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Sat, Dec 4, 2010 at 1:47 PM, Giacomo Comes <comes@naic.edu> wrote:
> On Sat, Dec 04, 2010 at 12:01:34PM +0000, Dave Kilroy wrote:
>> >> I'm at a loss. I've looked at the wpa_supplicant code, and had another
>> >> look at the driver. The scan should be a plain wildcard scan - which
>> >> you've identified works.
>> >>
>> >> Does setting scan_ssid=1 in the wpa_supplicant network block change
>> >> the behaviour? That's usually only necessary for hidden SSIDs - but
>> >> I'd like to know if the scan succeeds in this case.
>> >
>> > No It doesn't work.
>> > But I have more informations for you.
>> >
>> > I have been testing different versions of wpa_supplicant
>> > and I have found that if a use wpa_supplicant 0.7.0 or earlier,
>> > it works. With 0.7.1 or newer it fails.
>> > wpa_supplicant 0.7.0 works even without applying your patch.
>>
>> I've set myself up so I can test with orinoco_usb. I can reproduce the
>> issue (or something that looks the same).
>>
>> After much confusion, I suspect the initial scan is being triggered
>> before the hardware is ready. Internally, wpa_supplicant will do an
>> 'ifconfig eth1 up' followed by an 'iwlist eth1 scan', and it seems the
>> driver/hardware wants more time between them.
>>
>> Try the following (either in two command prompts, or with
>> wpa_supplicant in the background):
>>
>> prompt1$ wpa_supplicant -dd -ieth1 ....
>>
>> prompt2$ ifconfig eth1 down
>> prompt2$ ifconfig eth1 up
>>
>> and see what wpa_supplicant is doing. If it has got scan results then
>> you're probably seeing what I am.
>
> You are right. After running ifconfig eth1 down,up on a second terminal,
> while wpa_supplicant iis running on the first terminal,
> it succesfully associates with the AP.
DOH!
My speculation above was incorrect. There's a really stupid driver bug
that's been there ever since I added WPA capability. Patch incoming.
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-04 14:40 ` Dave Kilroy
@ 2010-12-06 4:28 ` Giacomo Comes
2010-12-06 18:43 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-06 4:28 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Sat, Dec 04, 2010 at 02:40:44PM +0000, Dave Kilroy wrote:
> On Sat, Dec 4, 2010 at 1:47 PM, Giacomo Comes <comes@naic.edu> wrote:
> > On Sat, Dec 04, 2010 at 12:01:34PM +0000, Dave Kilroy wrote:
> >> >> I'm at a loss. I've looked at the wpa_supplicant code, and had another
> >> >> look at the driver. The scan should be a plain wildcard scan - which
> >> >> you've identified works.
> >> >>
> >> >> Does setting scan_ssid=1 in the wpa_supplicant network block change
> >> >> the behaviour? That's usually only necessary for hidden SSIDs - but
> >> >> I'd like to know if the scan succeeds in this case.
> >> >
> >> > No It doesn't work.
> >> > But I have more informations for you.
> >> >
> >> > I have been testing different versions of wpa_supplicant
> >> > and I have found that if a use wpa_supplicant 0.7.0 or earlier,
> >> > it works. With 0.7.1 or newer it fails.
> >> > wpa_supplicant 0.7.0 works even without applying your patch.
> >>
> >> I've set myself up so I can test with orinoco_usb. I can reproduce the
> >> issue (or something that looks the same).
> >>
> >> After much confusion, I suspect the initial scan is being triggered
> >> before the hardware is ready. Internally, wpa_supplicant will do an
> >> 'ifconfig eth1 up' followed by an 'iwlist eth1 scan', and it seems the
> >> driver/hardware wants more time between them.
> >>
> >> Try the following (either in two command prompts, or with
> >> wpa_supplicant in the background):
> >>
> >> prompt1$ wpa_supplicant -dd -ieth1 ....
> >>
> >> prompt2$ ifconfig eth1 down
> >> prompt2$ ifconfig eth1 up
> >>
> >> and see what wpa_supplicant is doing. If it has got scan results then
> >> you're probably seeing what I am.
> >
> > You are right. After running ifconfig eth1 down,up on a second terminal,
> > while wpa_supplicant iis running on the first terminal,
> > it succesfully associates with the AP.
>
> DOH!
>
> My speculation above was incorrect. There's a really stupid driver bug
> that's been there ever since I added WPA capability. Patch incoming.
I have been testing your patches and I can confirm that now the orinoco
driver is working properly for me. Using directly wpa_supplicant and using
networkmanager.
Thank you very much for your work.
The only issue still not fixed is the suspend/resume timeout.
Can you help also with that?
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-06 4:28 ` Giacomo Comes
@ 2010-12-06 18:43 ` Dave Kilroy
2010-12-06 21:25 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-06 18:43 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
> I have been testing your patches and I can confirm that now the orinoco
> driver is working properly for me. Using directly wpa_supplicant and using
> networkmanager.
> Thank you very much for your work.
No problem.
> The only issue still not fixed is the suspend/resume timeout.
> Can you help also with that?
Absolutely. With the latest patches, please just do a suspend resume,
and post the dmesg output. Also let me know what the value of
CONFIG_HERMES_CACHE_FW_ON_INIT is.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-06 18:43 ` Dave Kilroy
@ 2010-12-06 21:25 ` Giacomo Comes
2010-12-08 19:24 ` Dave Kilroy
0 siblings, 1 reply; 21+ messages in thread
From: Giacomo Comes @ 2010-12-06 21:25 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
On Mon, Dec 06, 2010 at 06:43:04PM +0000, Dave Kilroy wrote:
> > I have been testing your patches and I can confirm that now the orinoco
> > driver is working properly for me. Using directly wpa_supplicant and using
> > networkmanager.
> > Thank you very much for your work.
>
> No problem.
>
> > The only issue still not fixed is the suspend/resume timeout.
> > Can you help also with that?
>
> Absolutely. With the latest patches, please just do a suspend resume,
> and post the dmesg output. Also let me know what the value of
> CONFIG_HERMES_CACHE_FW_ON_INIT is.
CONFIG_HERMES_CACHE_FW_ON_INIT=y
Attached is the outpur of dmesg after suspend/resume
As you can see, the driver is unable to load the firmware,
therefore WPA is not available after resume:
iwlist eth1 scan:
eth1 Scan completed :
Cell 01 - Address: 00:13:10:AA:89:4B
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-37 dBm
Encryption key:on
ESSID:"Comes"
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 168ms ago
IE: Unknown: 0005436F6D6573
iw dev eth1 scan:
BSS 00:13:10:aa:89:4b (on eth1)
freq: 2437
beacon interval: 100
capability: ESS Privacy PBCC (0x0051)
signal: -41.00 dBm
last seen: 0 ms ago
SSID: Comes
Giacomo
[-- Attachment #2: dmesgdiff --]
[-- Type: text/plain, Size: 9892 bytes --]
783a784,912
> [ 891.388960] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
> [ 891.389460] pcmcia_socket pcmcia_socket1: pccard: card ejected from slot 1
> [ 891.389569] pcmcia_socket pcmcia_socket2: pccard: card ejected from slot 2
> [ 895.286074] PM: Marking nosave pages: 0000000000002000 - 0000000000010000
> [ 895.286081] PM: Marking nosave pages: 000000000009f000 - 0000000000100000
> [ 895.286086] PM: Basic memory bitmaps created
> [ 895.642068] Syncing filesystems ... done.
> [ 895.650034] Freezing user space processes ... (elapsed 0.01 seconds) done.
> [ 895.663138] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
> [ 895.674258] PM: Preallocating image memory... done (allocated 72866 pages)
> [ 898.531573] PM: Allocated 291464 kbytes in 2.85 seconds (102.26 MB/s)
> [ 898.531579] Suspending console(s) (use no_console_suspend to debug)
> [ 898.536671] parport_pc 00:0e: disabled
> [ 898.540943] serial 00:0d: disabled
> [ 898.543249] ACPI handle has no context!
> [ 898.543350] [drm] nouveau 0000:01:00.0: Disabling fbcon acceleration...
> [ 898.543354] [drm] nouveau 0000:01:00.0: Unpinning framebuffer(s)...
> [ 898.543359] [drm] nouveau 0000:01:00.0: Evicting buffers...
> [ 898.547445] Intel ICH Modem 0000:00:1f.6: PCI INT B disabled
> [ 898.547667] Intel ICH 0000:00:1f.5: PCI INT B disabled
> [ 898.628878] [drm] nouveau 0000:01:00.0: Idling channels...
> [ 898.629588] [drm] nouveau 0000:01:00.0: Suspending GPU objects...
> [ 898.735443] [drm] nouveau 0000:01:00.0: And we're gone!
> [ 898.736048] sd 0:0:0:0: [sda] Synchronizing SCSI cache
> [ 898.990935] ata_piix 0000:00:1f.1: PCI INT A disabled
> [ 898.990956] PM: freeze of devices complete after 459.026 msecs
> [ 898.991448] PM: late freeze of devices complete after 0.483 msecs
> [ 898.996744] ACPI: Preparing to enter system sleep state S4
> [ 898.997725] PM: Saving platform NVS memory
> [ 898.997849] Disabling non-boot CPUs ...
> [ 898.997931] PM: Creating hibernation image:
> [ 898.998488] PM: Need to copy 58748 pages
> [ 898.998488] PM: Normal pages needed: 58748 + 1024, available pages: 72169
> [ 898.998488] PM: Restoring platform NVS memory
> [ 899.001534] ACPI: Waking up from system sleep state S4
> [ 899.014724] ata_piix 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2800003, writing 0x2800007)
> [ 899.014759] Intel ICH 0000:00:1f.5: restoring config space at offset 0x1 (was 0x2800005, writing 0x2800001)
> [ 899.014863] 3c59x 0000:02:00.0: restoring config space at offset 0x1 (was 0x2100117, writing 0x82100117)
> [ 899.014885] yenta_cardbus 0000:02:01.0: restoring config space at offset 0xf (was 0x74001ff, writing 0x5c001ff)
> [ 899.014908] yenta_cardbus 0000:02:01.0: restoring config space at offset 0x3 (was 0x822008, writing 0x82a810)
> [ 899.014948] yenta_cardbus 0000:02:01.1: restoring config space at offset 0xf (was 0x74001ff, writing 0x5c001ff)
> [ 899.014971] yenta_cardbus 0000:02:01.1: restoring config space at offset 0x3 (was 0x822008, writing 0x82a810)
> [ 899.014979] yenta_cardbus 0000:02:01.1: restoring config space at offset 0x1 (was 0x2100007, writing 0x82100007)
> [ 899.015062] ohci1394 0000:02:01.2: restoring config space at offset 0x1 (was 0x2100116, writing 0x82100116)
> [ 899.015085] yenta_cardbus 0000:02:03.0: restoring config space at offset 0xf (was 0x340010b, writing 0x5c0010b)
> [ 899.015107] yenta_cardbus 0000:02:03.0: restoring config space at offset 0x3 (was 0x22008, writing 0x2a810)
> [ 899.015116] yenta_cardbus 0000:02:03.0: restoring config space at offset 0x1 (was 0x2100007, writing 0x82100007)
> [ 899.015493] PM: early restore of devices complete after 0.970 msecs
> [ 899.040854] pm_op(): pci_pm_restore+0x0/0xa0 returns -16
> [ 899.040860] PM: Device 0000:00:00.0 failed to restore async: error -16
> [ 899.040966] uhci_hcd 0000:00:1d.0: setting latency timer to 64
> [ 899.041002] usb usb1: root hub lost power or was reset
> [ 899.041095] uhci_hcd 0000:00:1d.2: setting latency timer to 64
> [ 899.041127] usb usb2: root hub lost power or was reset
> [ 899.041193] pci 0000:00:1e.0: setting latency timer to 64
> [ 899.041299] ata_piix 0000:00:1f.1: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
> [ 899.041306] ata_piix 0000:00:1f.1: setting latency timer to 64
> [ 899.041612] Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
> [ 899.041620] Intel ICH 0000:00:1f.5: setting latency timer to 64
> [ 899.041691] Intel ICH Modem 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
> [ 899.041699] Intel ICH Modem 0000:00:1f.6: setting latency timer to 64
> [ 899.041769] [drm] nouveau 0000:01:00.0: We're back, enabling device...
> [ 899.041777] [drm] nouveau 0000:01:00.0: POSTing device...
> [ 899.041902] [drm] nouveau 0000:01:00.0: Loading NV17 power sequencing microcode
> [ 899.041911] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 0 at offset 0xC264
> [ 899.041954] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0xC531
> [ 899.041981] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0xC34E
> [ 899.042051] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0xCA34
> [ 899.042067] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0xC4CC
> [ 899.042080] agpgart-intel 0000:00:00.0: AGP 2.0 bridge
> [ 899.042105] agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
> [ 899.042131] nouveau 0000:01:00.0: putting AGP V2 device into 4x mode
> [ 899.042167] [drm] nouveau 0000:01:00.0: Reinitialising engines...
> [ 899.042199] [drm] nouveau 0000:01:00.0: Restoring GPU objects...
> [ 899.045684] sd 0:0:0:0: [sda] Starting disk
> [ 899.086577] [drm] nouveau 0000:01:00.0: Restoring mode...
> [ 899.086589] [drm] nouveau 0000:01:00.0: Calling LVDS script 1:
> [ 899.086595] [drm] nouveau 0000:01:00.0: Calling LVDS script 6:
> [ 899.086600] [drm] nouveau 0000:01:00.0: 0xD6D8: Parsing digital output script table
> [ 899.097133] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[f8fff000-f8fff7ff] Max Packet=[2048] IR/IT contexts=[4/4]
> [ 899.204451] ata1.00: configured for UDMA/100
> [ 899.210251] ata1.01: configured for MWDMA2
> [ 899.248064] serial 00:0d: activated
> [ 899.355134] parport_pc 00:0e: activated
> [ 899.608086] [drm] nouveau 0000:01:00.0: Calling LVDS script 2:
> [ 899.608095] [drm] nouveau 0000:01:00.0: 0xD780: Parsing digital output script table
> [ 899.642115] [drm] nouveau 0000:01:00.0: Calling LVDS script 5:
> [ 899.642120] [drm] nouveau 0000:01:00.0: 0xD662: Parsing digital output script table
> [ 899.849247] [drm] nouveau 0000:01:00.0: Restoring CRTC_OWNER to 0.
> [ 899.882143] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on lvds encoder (output 0)
> [ 899.882149] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on vga encoder (output 1)
> [ 899.882154] [drm] nouveau 0000:01:00.0: Setting dpms mode 3 on TV encoder (output 2)
> [ 899.904777] [drm] nouveau 0000:01:00.0: Output LVDS-1 is running on CRTC 1 using output A
> [ 899.904782] [drm] nouveau 0000:01:00.0: Calling LVDS script 6:
> [ 899.904787] [drm] nouveau 0000:01:00.0: 0xD6D8: Parsing digital output script table
> [ 900.426093] [drm] nouveau 0000:01:00.0: Calling LVDS script 2:
> [ 900.426098] [drm] nouveau 0000:01:00.0: 0xD780: Parsing digital output script table
> [ 900.460127] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on lvds encoder (output 0)
> [ 900.460131] [drm] nouveau 0000:01:00.0: Calling LVDS script 5:
> [ 900.460134] [drm] nouveau 0000:01:00.0: 0xD662: Parsing digital output script table
> [ 900.664099] [drm] nouveau 0000:01:00.0: Output LVDS-1 is running on CRTC 1 using output A
> [ 901.542098] pcmcia_socket pcmcia_socket2: pccard: PCMCIA card inserted into slot 2
> [ 901.542438] pcmcia 2.0: pcmcia: registering new device pcmcia2.0
> [ 901.624760] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> [ 901.624881] orinoco_cs 2.0: Station identity 001f:0001:0008:000a
> [ 901.624886] orinoco_cs 2.0: Firmware determined as Lucent/Agere 8.10
> [ 901.624891] orinoco_cs 2.0: firmware: requesting agere_sta_fw.bin
> [ 961.625193] orinoco_cs 2.0: firmware: requesting agere_sta_fw.bin
> [ 1021.625131] orinoco_cs 2.0: Cannot find firmware agere_sta_fw.bin
> [ 1021.625194] orinoco_cs 2.0: Hardware identity 0005:0004:0005:0000
> [ 1021.625302] orinoco_cs 2.0: Station identity 001f:0001:0008:000a
> [ 1021.625307] orinoco_cs 2.0: Firmware determined as Lucent/Agere 8.10
> [ 1021.625310] orinoco_cs 2.0: Ad-hoc demo mode supported
> [ 1021.625313] orinoco_cs 2.0: IEEE standard IBSS ad-hoc mode supported
> [ 1021.625316] orinoco_cs 2.0: WEP supported, 104-bit key
> [ 1021.627555] PM: restore of devices complete after 122586.854 msecs
> [ 1021.633004] snapshot_deprecated_ioctl: 6 callbacks suppressed
> [ 1021.633064] snapshot_ioctl: ioctl '4004330c' is deprecated and will be removed soon, update your suspend-to-disk utilities
> [ 1021.633072] Restarting tasks ... done.
> [ 1021.644392] PM: Basic memory bitmaps freed
> [ 1021.644406] video LNXVIDEO:00: Restoring backlight state
> [ 1053.626744] Disabling lock debugging due to kernel taint
> [ 1053.652635] ndiswrapper version 1.55 loaded (smp=yes, preempt=yes)
> [ 1053.716507] usbcore: registered new interface driver ndiswrapper
> [ 1053.801470] eth0: setting full-duplex.
> [ 1053.829438] ADDRCONF(NETDEV_UP): eth1: link is not ready
> [ 1054.154949] eth1: New link status: Disconnected (0002)
> [ 1059.608421] SFW2-INext-ACC-TCP IN=eth0 OUT= MAC=00:08:74:03:ab:0d:00:24:e8:a6:6e:a2:08:00 SRC=192.168.15.100 DST=192.168.15.101 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=4015 DF PROTO=TCP SPT=59089 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40402080A06E6DD9C0000000001030306)
> [ 1064.165048] eth0: no IPv6 routers present
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-06 21:25 ` Giacomo Comes
@ 2010-12-08 19:24 ` Dave Kilroy
2010-12-09 2:58 ` Giacomo Comes
0 siblings, 1 reply; 21+ messages in thread
From: Dave Kilroy @ 2010-12-08 19:24 UTC (permalink / raw)
To: Giacomo Comes; +Cc: linux-wireless
On Mon, Dec 6, 2010 at 9:25 PM, Giacomo Comes <comes@naic.edu> wrote:
> On Mon, Dec 06, 2010 at 06:43:04PM +0000, Dave Kilroy wrote:
>> > The only issue still not fixed is the suspend/resume timeout.
>> > Can you help also with that?
>>
>> Absolutely. With the latest patches, please just do a suspend resume,
>> and post the dmesg output. Also let me know what the value of
>> CONFIG_HERMES_CACHE_FW_ON_INIT is.
>
> CONFIG_HERMES_CACHE_FW_ON_INIT=y
>
> Attached is the outpur of dmesg after suspend/resume
>
> As you can see, the driver is unable to load the firmware,
> therefore WPA is not available after resume:
I've had a look at the log. Things aren't working as I'd expect.
orinoco_init is being called on resume, which I don't think used to
happen. That is what is causing the request for firmware, and the
delay on resume.
Instead I only expected orinoco_up to get called. I'll dig around to
see whether that's a change in the kernel. It might be distro specific
though. Do you know if suse works differently on suspend/resume? i.e
explicitly 'modprobe -r'ing drivers
Dave.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: orinoco_cs module and WPA not working
2010-12-08 19:24 ` Dave Kilroy
@ 2010-12-09 2:58 ` Giacomo Comes
0 siblings, 0 replies; 21+ messages in thread
From: Giacomo Comes @ 2010-12-09 2:58 UTC (permalink / raw)
To: Dave Kilroy; +Cc: Giacomo Comes, linux-wireless
On Wed, Dec 08, 2010 at 07:24:47PM +0000, Dave Kilroy wrote:
> On Mon, Dec 6, 2010 at 9:25 PM, Giacomo Comes <comes@naic.edu> wrote:
> > On Mon, Dec 06, 2010 at 06:43:04PM +0000, Dave Kilroy wrote:
> >> > The only issue still not fixed is the suspend/resume timeout.
> >> > Can you help also with that?
> >>
> >> Absolutely. With the latest patches, please just do a suspend resume,
> >> and post the dmesg output. Also let me know what the value of
> >> CONFIG_HERMES_CACHE_FW_ON_INIT is.
> >
> > CONFIG_HERMES_CACHE_FW_ON_INIT=y
> >
> > Attached is the outpur of dmesg after suspend/resume
> >
> > As you can see, the driver is unable to load the firmware,
> > therefore WPA is not available after resume:
>
> I've had a look at the log. Things aren't working as I'd expect.
> orinoco_init is being called on resume, which I don't think used to
> happen. That is what is causing the request for firmware, and the
> delay on resume.
>
> Instead I only expected orinoco_up to get called. I'll dig around to
> see whether that's a change in the kernel. It might be distro specific
> though. Do you know if suse works differently on suspend/resume? i.e
> explicitly 'modprobe -r'ing drivers
>
> Dave.
After more investigation, I have found that
suspend/resume works if I suspend the system from the console
with the command s2disk even if the orinoco module is loaded.
When I suspend the system from the desktop calling pm-hibernate
then there is the delay. Remember, the delay happens on suspend
AND on resume.
pm-hibernate will run a set of scripts in /usr/lib/pm-utils/sleep.d
One of these scripts (45pcmcia) executes:
"/sbin/pccardctl eject" on suspend and
"/sbin/pccardctl insert" on resume.
If I disable this script, then suspend/resume works properly.
I wonder if there are other pcmcia wireles cards that suffer
the same problem?
What is, in your opinion, the proper way to proceed?
To change something in the orinoco driver? Modify pm-utils?
Something else?
Giacomo
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2010-12-09 2:58 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-11-22 2:42 orinoco_cs module and WPA not working Giacomo Comes
2010-11-24 19:06 ` Dave Kilroy
2010-11-25 1:45 ` Giacomo Comes
[not found] ` <AANLkTi=nkayyyzECi6MO87ZO-CUpZeNP007_hMp8LiPV@mail.gmail.com>
[not found] ` <20101126040742.GA5238@monopoli.naic.edu>
2010-11-28 16:10 ` Dave Kilroy
2010-11-30 2:19 ` Giacomo Comes
2010-12-01 21:52 ` Dave Kilroy
2010-12-02 0:22 ` Giacomo Comes
2010-12-02 17:46 ` Dave Kilroy
2010-12-03 0:10 ` Giacomo Comes
[not found] ` <AANLkTinLaa+dOiq67DAt+KYfnxUEkNgWEiE2x1NtT9RE@mail.gmail.com>
2010-12-03 17:29 ` Dave Kilroy
2010-12-03 20:23 ` Giacomo Comes
2010-12-03 22:49 ` Dave Kilroy
2010-12-04 3:36 ` Giacomo Comes
2010-12-04 12:01 ` Dave Kilroy
2010-12-04 13:47 ` Giacomo Comes
2010-12-04 14:40 ` Dave Kilroy
2010-12-06 4:28 ` Giacomo Comes
2010-12-06 18:43 ` Dave Kilroy
2010-12-06 21:25 ` Giacomo Comes
2010-12-08 19:24 ` Dave Kilroy
2010-12-09 2:58 ` Giacomo Comes
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.