* B43 will not associate
@ 2008-03-04 19:43 Ahmed Ammar
2008-03-04 19:47 ` Michael Buesch
0 siblings, 1 reply; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-04 19:43 UTC (permalink / raw)
To: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
b43 driver will never associate to my AP. below is the full dmesg
output. Also attached is the wireless capture from another card.
[-- Attachment #2: dmesg --]
[-- Type: application/octet-stream, Size: 28154 bytes --]
Linux version 2.6.24-zen-rt3 (root@b33fb0x) (gcc version 4.4.0-alpha20080229 (experimental) (GCC) ) #25 PREEMPT RT Tue Mar 4 15:39:51 GMT 2008
Command line: root=/dev/ram0 init=/linuxrc real_root=/dev/mapper/nvidia_cacjgecg3 dodmraid vga=0xf00 noload nodetect
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 0000000000097800 (usable)
BIOS-e820: 000000000009a800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Entering add_active_range(0, 0, 151) 0 entries of 256 used
Entering add_active_range(0, 256, 262128) 1 entries of 256 used
end_pfn_map = 1048576
DMI 2.3 present.
ACPI: RSDP 000F6C50, 0014 (r0 Nvidia)
ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD 1010101)
ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD 1010101)
ACPI: DSDT 3FFF30C0, 49CE (r1 NVIDIA AWRDACPI 1000 MSFT 100000C)
ACPI: FACS 3FFF0000, 0040
ACPI: APIC 3FFF7AC0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD 1010101)
Entering add_active_range(0, 0, 151) 0 entries of 256 used
Entering add_active_range(0, 256, 262128) 1 entries of 256 used
[ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
[ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
[ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
[ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
[ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
[ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
[ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0 -> 151
0: 256 -> 262128
On node 0 totalpages: 262023
DMA zone: 56 pages used for memmap
DMA zone: 1441 pages reserved
DMA zone: 2494 pages, LIFO batch:0
DMA32 zone: 3527 pages used for memmap
DMA32 zone: 254505 pages, LIFO batch:31
Normal zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Nvidia board detected. Ignoring ACPI timer override.
If you got timer trouble try acpi_use_timer_override
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Real-Time Preemption Support (C) 2004-2007 Ingo Molnar
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256999
Kernel command line: root=/dev/ram0 init=/linuxrc real_root=/dev/mapper/nvidia_cacjgecg3 dodmraid vga=0xf00 noload nodetect
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
time.c: Detected 2009.167 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
------------------------
| Locking API testsuite:
----------------------------------------------------------------------------
| spin |wlock |rlock |mutex | wsem | rsem |
--------------------------------------------------------------------------
A-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-C-C-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-A-B-C deadlock:failed|failed| ok |failed|failed|failed|
A-B-B-C-C-D-D-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-D-B-D-D-A deadlock:failed|failed| ok |failed|failed|failed|
A-B-C-D-B-C-D-A deadlock:failed|failed| ok |failed|failed|failed|
double unlock:failed|failed|failed|failed|failed|failed|
initialize held:failed|failed|failed|failed|failed|failed|
bad unlock order: ok | ok | ok | ok | ok | ok |
--------------------------------------------------------------------------
recursive read-lock: | ok | |failed|
recursive read-lock #2: | ok | |failed|
mixed read-write-lock: |failed| |failed|
mixed write-read-lock: |failed| |failed|
--------------------------------------------------------------------------
--------------------------------------------------------
53 out of 68 testcases failed, as expected. |
----------------------------------------------------
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Checking aperture...
CPU 0: aperture @ e8000000 size 128 MB
Memory: 1024040k/1048512k available (3148k kernel code, 23380k reserved, 1637k data, 232k init)
Calibrating delay using timer specific routine.. 4021.07 BogoMIPS (lpj=8042151)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: AMD Athlon(tm) 64 Processor 3000+ stepping 08
ACPI: Core revision 20070126
Using local APIC timer interrupts.
APIC timer calibration result 12557311
Detected 12.557 MHz APIC timer.
net_namespace: 144 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Scanning bus 0000:00
PCI: Found 0000:00:00.0 [10de/00e1] 000600 00
PCI: Found 0000:00:01.0 [10de/00e0] 000601 00
PCI: Found 0000:00:01.1 [10de/00e4] 000c05 00
PCI: Found 0000:00:02.0 [10de/00e7] 000c03 00
PCI: Found 0000:00:02.1 [10de/00e7] 000c03 00
PCI: Found 0000:00:02.2 [10de/00e8] 000c03 00
PCI: Found 0000:00:08.0 [10de/00e5] 000101 00
PCI: Found 0000:00:0a.0 [10de/00e3] 000101 00
PCI: Found 0000:00:0b.0 [10de/00e2] 000604 01
PCI: Found 0000:00:0e.0 [10de/00ed] 000604 01
PCI: Found 0000:00:18.0 [1022/1100] 000600 00
PCI: Found 0000:00:18.1 [1022/1101] 000600 00
PCI: Found 0000:00:18.2 [1022/1102] 000600 00
PCI: Found 0000:00:18.3 [1022/1103] 000600 00
PCI: Fixups for bus 0000:00
PCI: Scanning behind PCI bridge 0000:00:0b.0, config 010100, pass 0
PCI: Scanning bus 0000:01
PCI: Found 0000:01:00.0 [10de/0042] 000300 00
PCI: Fixups for bus 0000:01
PCI: Bus scan for 0000:01 returning with max=01
PCI: Scanning behind PCI bridge 0000:00:0e.0, config 020200, pass 0
PCI: Scanning bus 0000:02
PCI: Found 0000:02:07.0 [14e4/4320] 000280 00
PCI: Found 0000:02:09.0 [1814/0401] 000280 00
PCI: Found 0000:02:0a.0 [1102/0004] 000401 00
PCI: Found 0000:02:0a.1 [1102/7003] 000980 00
PCI: Found 0000:02:0a.2 [1102/4001] 000c00 00
PCI: Fixups for bus 0000:02
PCI: Bus scan for 0000:02 returning with max=02
PCI: Scanning behind PCI bridge 0000:00:0b.0, config 010100, pass 1
PCI: Scanning behind PCI bridge 0000:00:0e.0, config 020200, pass 1
PCI: Bus scan for 0000:00 returning with max=02
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 6 7 9 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
ACPI: PCI Interrupt Link [APC5] (IRQs *16)
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22) *0
ACPI: Power Resource [ISAV] (on)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
libata version 3.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Cannot allocate resource region 0 of device 0000:00:00.0
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 128M @ 0xe8000000
system 00:00: ioport range 0x1000-0x107f has been reserved
system 00:00: ioport range 0x1080-0x10ff has been reserved
system 00:00: ioport range 0x1400-0x147f has been reserved
system 00:00: ioport range 0x1480-0x14ff has been reserved
system 00:00: ioport range 0x1800-0x187f has been reserved
system 00:00: ioport range 0x1880-0x18ff has been reserved
system 00:01: iomem range 0xf0000-0xf3fff could not be reserved
system 00:01: iomem range 0xf4000-0xf7fff could not be reserved
system 00:01: iomem range 0xf8000-0xfbfff could not be reserved
system 00:01: iomem range 0xfc000-0xfffff could not be reserved
system 00:01: iomem range 0x3fff0000-0x3fffffff could not be reserved
system 00:01: iomem range 0xffff0000-0xffffffff could not be reserved
system 00:01: iomem range 0x0-0x9ffff could not be reserved
system 00:01: iomem range 0x100000-0x3ffeffff could not be reserved
system 00:01: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:01: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:03: ioport range 0x4d0-0x4d1 has been reserved
system 00:03: ioport range 0x800-0x805 has been reserved
system 00:03: ioport range 0x290-0x297 has been reserved
got res [fa000000:fa01ffff] bus [fa000000:fa01ffff] flags 7200 for BAR 6 of 0000:01:00.0
PCI: Bridge: 0000:00:0b.0
IO window: disabled.
MEM window: f8000000-faffffff
PREFETCH window: f0000000-f7ffffff
PCI: Bridge: 0000:00:0e.0
IO window: 9000-9fff
MEM window: fb000000-fbffffff
PREFETCH window: disabled.
PCI: Setting latency timer of device 0000:00:0e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 9, 3670016 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 1344k freed
tracer: 256 pages allocated for 16384<6> entries of 64 bytes
actual entries 16384
Total HugeTLB memory allocated, 0
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler cfq registered (default)
PCI: Calling quirk ffffffff80375b04 for 0000:00:00.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:00.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:00.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:01.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:01.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:01.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:01.1
PCI: Calling quirk ffffffff8043e9fe for 0000:00:01.1
PCI: Calling quirk ffffffff80490c14 for 0000:00:01.1
PCI: Calling quirk ffffffff80375b04 for 0000:00:02.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:02.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:02.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:02.1
PCI: Calling quirk ffffffff8043e9fe for 0000:00:02.1
PCI: Calling quirk ffffffff80490c14 for 0000:00:02.1
PCI: Calling quirk ffffffff80375b04 for 0000:00:02.2
PCI: Calling quirk ffffffff8043e9fe for 0000:00:02.2
PCI: Calling quirk ffffffff80490c14 for 0000:00:02.2
PCI: Calling quirk ffffffff80375b04 for 0000:00:08.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:08.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:08.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:0a.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:0a.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:0a.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:0b.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:0b.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:0b.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:0e.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:0e.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:0e.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:18.0
PCI: Calling quirk ffffffff8043e9fe for 0000:00:18.0
PCI: Calling quirk ffffffff80490c14 for 0000:00:18.0
PCI: Calling quirk ffffffff80375b04 for 0000:00:18.1
PCI: Calling quirk ffffffff8043e9fe for 0000:00:18.1
PCI: Calling quirk ffffffff80490c14 for 0000:00:18.1
PCI: Calling quirk ffffffff80375b04 for 0000:00:18.2
PCI: Calling quirk ffffffff8043e9fe for 0000:00:18.2
PCI: Calling quirk ffffffff80490c14 for 0000:00:18.2
PCI: Calling quirk ffffffff80375b04 for 0000:00:18.3
PCI: Calling quirk ffffffff8043e9fe for 0000:00:18.3
PCI: Calling quirk ffffffff80490c14 for 0000:00:18.3
PCI: Calling quirk ffffffff80375b04 for 0000:01:00.0
PCI: Calling quirk ffffffff8043e9fe for 0000:01:00.0
PCI: Calling quirk ffffffff80490c14 for 0000:01:00.0
Boot video device is 0000:01:00.0
PCI: Calling quirk ffffffff80375b04 for 0000:02:07.0
PCI: Calling quirk ffffffff8043e9fe for 0000:02:07.0
PCI: Calling quirk ffffffff80490c14 for 0000:02:07.0
PCI: Calling quirk ffffffff80375b04 for 0000:02:09.0
PCI: Calling quirk ffffffff8043e9fe for 0000:02:09.0
PCI: Calling quirk ffffffff80490c14 for 0000:02:09.0
PCI: Calling quirk ffffffff80375b04 for 0000:02:0a.0
PCI: Calling quirk ffffffff8043e9fe for 0000:02:0a.0
PCI: Calling quirk ffffffff80490c14 for 0000:02:0a.0
PCI: Calling quirk ffffffff80375b04 for 0000:02:0a.1
PCI: Calling quirk ffffffff8043e9fe for 0000:02:0a.1
PCI: Calling quirk ffffffff80490c14 for 0000:02:0a.1
PCI: Calling quirk ffffffff80375b04 for 0000:02:0a.2
PCI: Calling quirk ffffffff8043e9fe for 0000:02:0a.2
PCI: Calling quirk ffffffff80490c14 for 0000:02:0a.2
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.102
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: module loaded
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE3-250: IDE controller (0x10de:0x00e5 rev 0xa2) at PCI slot 0000:00:08.0
NFORCE3-250: not 100% native mode: will probe irqs later
NFORCE3-250: 0000:00:08.0 (rev a2) UDMA133 controller
NFORCE3-250: IDE port disabled
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide1...
Probing IDE interface ide0...
Probing IDE interface ide1...
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
sata_nv 0000:00:0a.0: version 3.5
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APSJ] -> GSI 22 (level, high) -> IRQ 22
PCI: Setting latency timer of device 0000:00:0a.0 to 64
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xc400 irq 22
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xc408 irq 22
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7: WDC WD2500KS-00MJB0, 02.01C03, max UDMA/133
ata1.00: 488397168 sectors, multi 16: LBA48
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7: WDC WD2500KS-00MJB0, 02.01C03, max UDMA/133
ata2.00: 488397168 sectors, multi 16: LBA48
ata2.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access ATA WDC WD2500KS-00M 02.0 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 sda4 < >
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access ATA WDC WD2500KS-00M 02.0 PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdb:
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:02:0a.2[B] -> Link [APC4] -> GSI 19 (level, low) -> IRQ 19
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[fb00e000-fb00e7ff] Max Packet=[2048] IR/IT contexts=[4/8]
ieee1394: raw1394: /dev/raw1394 device initialized
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [APCL] -> GSI 21 (level, high) -> IRQ 21
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: EHCI Host Controller
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.2: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: irq 21, io mem 0xfc004000
ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 20 (level, high) -> IRQ 20
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 20, io mem 0xfc002000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
ACPI: PCI Interrupt Link [APCG] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCG] -> GSI 22 (level, high) -> IRQ 22
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: OHCI Host Controller
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:02.1: irq 22, io mem 0xfc003000
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v3.0
usb 2-4: new low speed USB device using ohci_hcd and address 2
usb 2-4: configuration #1 chosen from 1 choice
usb 3-4: new low speed USB device using ohci_hcd and address 2
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023c015103175e]
usb 3-4: configuration #1 chosen from 1 choice
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
input: Microsoft Microsoft IntelliMouse? Explorer as /class/input/input1
input: USB HID v1.11 Mouse [Microsoft Microsoft IntelliMouse? Explorer] on usb-0000:00:02.0-4
drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed
drivers/hid/usbhid/hid-core.c: timeout initializing reports
input: Logitech Logitech Extreme 3D as /class/input/input2
input: USB HID v1.10 Joystick [Logitech Logitech Extreme 3D] on usb-0000:00:02.1-4
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.16rc2 (Thu Jan 31 16:40:16 2008 UTC).
ALSA device list:
No soundcards found.
netem: version 1.2
TCP westwood registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Freeing unused kernel memory: 232k freed
EXT3-fs: dm-3: couldn't mount because of unsupported optional features (40).
EXT4-fs: INFO: recovery required on readonly filesystem.
EXT4-fs: write access will be enabled during recovery.
kjournald2 starting. Commit interval 5 seconds
EXT4-fs: dm-3: orphan cleanup on readonly fs
ext4_orphan_cleanup: deleting unreferenced inode 10783322
ext4_orphan_cleanup: deleting unreferenced inode 10784106
ext4_orphan_cleanup: deleting unreferenced inode 10783527
ext4_orphan_cleanup: deleting unreferenced inode 8011823
ext4_orphan_cleanup: deleting unreferenced inode 1638423
EXT4-fs: dm-3: 5 orphan inodes deleted
EXT4-fs: recovery complete.
EXT4-fs: mounted filesystem with writeback data mode.
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
parport_pc 00:0b: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
Installing spdif_bug patch: Audigy 2 ZS [SB0350]
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [APC5] -> GSI 16 (level, low) -> IRQ 16
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 169.12 Thu Feb 14 17:51:09 PST 2008
EXT4-fs warning: maximal mount count reached, running e2fsck is recommended
EXT4 FS on dm-3, internal journal
lp0: using parport0 (interrupt-driven).
lp0: console ready
Adding 1959888k swap on /dev/mapper/nvidia_cacjgecg5. Priority:-1 extents:1 across:1959888k
Adding 9999992k swap on /swap_file. Priority:-2 extents:1405 across:12037368k
Ethernet Channel Bonding Driver: v3.2.3 (December 6, 2007)
bonding: MII link monitoring set to 100 ms
bonding: bond0: setting mode to broadcast (3).
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
PCI: Enabling Mem-Wr-Inval for device 0000:02:09.0
phy0: Selected rate control algorithm 'pid'
Registered led device: rt61pci-phy0:radio
Registered led device: rt61pci-phy0:assoc
bonding: bond0: Adding slave wlan0.
bonding: bond0: enslaving wlan0 as an active interface with a down link.
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: RX authentication from 00:90:d0:f2:ad:7b (alg=1 transaction=2 status=0)
wlan0: replying to auth challenge
wlan0: RX authentication from 00:90:d0:f2:ad:7b (alg=1 transaction=4 status=0)
wlan0: authenticated
wlan0: associate with AP 00:90:d0:f2:ad:7b
wlan0: RX AssocResp from 00:90:d0:f2:ad:7b (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 txop=0
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47
bonding: bond0: link status definitely up for interface wlan0.
bonding: bond0: Interface wlan0 is already enslaved!
stap_5b0265e3fafc2818bf8cae7f5486f44f_339805: systemtap: 0.6.1/0.131, base: ffffffff8896b000, memory: 486368+36528+7336+14000 data+text+ctx+net, probes: 1566
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC4] -> GSI 19 (level, low) -> IRQ 19
PCI: Enabling bus mastering for device 0000:02:07.0
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
ssb: SPROM revision 1 detected.
ssb: Sonics Silicon Backplane found on PCI device 0000:02:07.0
b43-phy1: Broadcom 4306 WLAN found
phy1: Selected rate control algorithm 'pid'
Broadcom 43xx driver loaded [ Features: PLD, Firmware-ID: FW10 ]
Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
bonding: bond0: Adding slave wlan1.
b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy1::tx
Registered led device: b43-phy1::rx
bonding: bond0: enslaving wlan1 as an active interface with a down link.
wlan1: Initial auth_alg=1
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authentication with AP 00:90:d0:f2:ad:7b timed out
wlan1: Initial auth_alg=1
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: Initial auth_alg=1
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: Initial auth_alg=1
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authenticate with AP 00:90:d0:f2:ad:7b
wlan1: authentication with AP 00:90:d0:f2:ad:7b timed out
[-- Attachment #3: b43.cap --]
[-- Type: application/octet-stream, Size: 583075 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-04 19:43 B43 will not associate Ahmed Ammar
@ 2008-03-04 19:47 ` Michael Buesch
2008-03-04 22:13 ` Ahmed Ammar
0 siblings, 1 reply; 11+ messages in thread
From: Michael Buesch @ 2008-03-04 19:47 UTC (permalink / raw)
To: Ahmed Ammar; +Cc: linux-wireless
On Tuesday 04 March 2008 20:43:12 Ahmed Ammar wrote:
> b43 driver will never associate to my AP.
You are wrong:
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:90:d0:f2:ad:7b
wlan0: RX authentication from 00:90:d0:f2:ad:7b (alg=1 transaction=2 status=0)
wlan0: replying to auth challenge
wlan0: RX authentication from 00:90:d0:f2:ad:7b (alg=1 transaction=4 status=0)
wlan0: authenticated
wlan0: associate with AP 00:90:d0:f2:ad:7b
wlan0: RX AssocResp from 00:90:d0:f2:ad:7b (capab=0x411 status=0 aid=1)
wlan0: associated
> below is the full dmesg
> output. Also attached is the wireless capture from another card.
Can you try disabling bonding? It seems to have problems:
bonding: bond0: link status definitely up for interface wlan0.
bonding: bond0: Interface wlan0 is already enslaved!
--
Greetings Michael.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-04 19:47 ` Michael Buesch
@ 2008-03-04 22:13 ` Ahmed Ammar
2008-03-05 14:17 ` Michael Buesch
0 siblings, 1 reply; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-04 22:13 UTC (permalink / raw)
To: Michael Buesch; +Cc: linux-wireless
> You are wrong:
I am NOT wrong. wlan0 is a rt61pci device.
And with or without bonding wlan1 will not associate.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-04 22:13 ` Ahmed Ammar
@ 2008-03-05 14:17 ` Michael Buesch
2008-03-05 15:26 ` Ahmed Ammar
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Michael Buesch @ 2008-03-05 14:17 UTC (permalink / raw)
To: Ahmed Ammar; +Cc: linux-wireless
On Tuesday 04 March 2008 23:13:38 Ahmed Ammar wrote:
> > You are wrong:
>
> I am NOT wrong. wlan0 is a rt61pci device.
Ok, gonna add you to my blacklist.
It's impossible to debug something, if you don't fscking
tell me your testbed setup and what's going on/wrong.
Your threads are a complete waste of time.
So if somebody else, who is capable to write usable bugreports,
does seem a similiar issue, please open a new thread and CC me.
Of course I want to fix this bug, but that doesn't work without
the help of the reporter. And no, throwing mail-forwards and
bugreports at me that consist of
<quote>
> b43 driver will never associate to my AP. below is the full dmesg
> output. Also attached is the wireless capture from another card.
</quote>
,a dmesg log and a capture are simply not the way bugreporting works.
This is useless.
--
Greetings Michael.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 14:17 ` Michael Buesch
@ 2008-03-05 15:26 ` Ahmed Ammar
2008-03-05 15:34 ` Ahmed Ammar
2008-03-05 15:49 ` Ahmed Ammar
2 siblings, 0 replies; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-05 15:26 UTC (permalink / raw)
To: Michael Buesch; +Cc: linux-wireless
> ,a dmesg log and a capture are simply not the way bugreporting works.
> This is useless.
>
That was the *exact* information you asked for. If you want more just ask.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 14:17 ` Michael Buesch
2008-03-05 15:26 ` Ahmed Ammar
@ 2008-03-05 15:34 ` Ahmed Ammar
2008-03-05 18:16 ` Dan Williams
2008-03-05 15:49 ` Ahmed Ammar
2 siblings, 1 reply; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-05 15:34 UTC (permalink / raw)
To: Michael Buesch; +Cc: linux-wireless
> It's impossible to debug something, if you don't fscking
> tell me your testbed setup and what's going on/wrong.
Well you don't get what you don't ask for.
I assume testbed means my hardware.
x86_64 proc., runnig 2.6.24-rt3 (in 64bit) with gentoo userland
(64bit). The card in question is a pci card.
I have tried on 2.6.24 vanilla and the association problem is exactly
the same. The card can see the AP fine but simply won't associate, as
you can see in the previous dmesg (wlan1). The capture is was to see
what packets the b43 driver is sending. I was asked to do this by
Johannes Berg.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 14:17 ` Michael Buesch
2008-03-05 15:26 ` Ahmed Ammar
2008-03-05 15:34 ` Ahmed Ammar
@ 2008-03-05 15:49 ` Ahmed Ammar
2 siblings, 0 replies; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-05 15:49 UTC (permalink / raw)
To: Michael Buesch; +Cc: linux-wireless
Also the wpa_supplicant (v0.6.3) output:
wpa_supplicant -Dwext -iwlan1 -c /etc/wpa_supplicant/wpa_supplicant.conf -dd
Initializing interface 'wlan1' conf
'/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface
'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' ->
'/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
Line: 1 - start of a new network block
ssid - hexdump_ascii(len=16):
4f 32 77 69 72 65 6c 65 73 73 46 34 31 32 41 32 O2wirelessF412A2
key_mgmt: 0x4
wep_key0 - hexdump(len=5): [REMOVED]
wep_tx_keyidx=0 (0x0)
priority=5 (0x5)
auth_alg: 0x2
Priority group 5
id=0 ssid='O2wirelessF412A2'
Initializing interface (2) 'wlan1'
Interface wlan1 set UP - waiting a second for the driver to complete
initialization
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:40:05:a1:d9:09
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
RSN: flushing PMKID list in the driver
Setting scan request: 0 sec 100000 usec
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Added interface wlan1
Ignore event for foreign ifindex 9
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan
to speed up initial association
Received 268 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2'
Trying to associate with 00:90:d0:f2:ad:7b (SSID='O2wirelessF412A2'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b1a len=32
EAPOL: disable timer tick
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b19 len=16
Received 268 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2'
Already associated with the selected AP.
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b1a len=32
Authentication with 00:90:d0:f2:ad:7b timed out.
Added BSSID 00:90:d0:f2:ad:7b into blacklist
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
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Scan requested (ret=0) - scan timeout 30 seconds
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b19 len=16
Received 268 bytes of scan results (1 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2'
Trying to associate with 00:90:d0:f2:ad:7b (SSID='O2wirelessF412A2'
freq=2412 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
Overriding auth_alg selection: 0x2
WPA: clearing AP WPA IE
WPA: clearing AP RSN IE
WPA: clearing own WPA/RSN IE
No keys have been configured - skip key clearing
wpa_driver_wext_set_key: alg=1 key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b1a len=32
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b19 len=16
Received 568 bytes of scan results (2 BSSes)
CTRL-EVENT-SCAN-RESULTS
Selecting BSS from priority group 5
Try to find WPA-enabled AP
0: 00:14:6c:ab:90:5a ssid='SKY25726' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
1: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
skip - no WPA/RSN IE
Try to find non-WPA AP
0: 00:14:6c:ab:90:5a ssid='SKY25726' wpa_ie_len=22 rsn_ie_len=0 caps=0x11
skip - SSID mismatch
1: 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2' wpa_ie_len=0 rsn_ie_len=0 caps=0x11
selected non-WPA AP 00:90:d0:f2:ad:7b ssid='O2wirelessF412A2'
Already associated with the selected AP.
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b04 len=16
RTM_NEWLINK: operstate=0 ifi_flags=0x1803 ([UP])
Wireless event: cmd=0x8b1a len=32
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan1
State: ASSOCIATING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
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
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
ioctl[SIOCSIWENCODEEXT]: No such file or directory
Driver did not support SIOCSIWENCODEEXT
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - No keys have been configured - skip key clearing
Removed BSSID 00:90:d0:f2:ad:7b from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 15:34 ` Ahmed Ammar
@ 2008-03-05 18:16 ` Dan Williams
2008-03-05 20:53 ` Ahmed Ammar
0 siblings, 1 reply; 11+ messages in thread
From: Dan Williams @ 2008-03-05 18:16 UTC (permalink / raw)
To: Ahmed Ammar; +Cc: Michael Buesch, linux-wireless
On Wed, 2008-03-05 at 15:34 +0000, Ahmed Ammar wrote:
> > It's impossible to debug something, if you don't fscking
> > tell me your testbed setup and what's going on/wrong.
>
> Well you don't get what you don't ask for.
>
> I assume testbed means my hardware.
>
> x86_64 proc., runnig 2.6.24-rt3 (in 64bit) with gentoo userland
> (64bit). The card in question is a pci card.
>
> I have tried on 2.6.24 vanilla and the association problem is exactly
> the same. The card can see the AP fine but simply won't associate, as
> you can see in the previous dmesg (wlan1). The capture is was to see
> what packets the b43 driver is sending. I was asked to do this by
> Johannes Berg.
I think Michael was also looking for stuff like your wireless cards.
Kind of pointless to post about your hardware when you exclude the
wireless hardware you're using and the problem you're having is
wireless-related.
1) What's your wlan0? What driver is it using?
2) What's your wlan1? What driver is it using?
3) Which interface are you having problems on?
Personally, I was somewhat confused because you (I think) said you were
having problems with _wlan1_, but you referenced wlan0 in other mails.
Dan
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 18:16 ` Dan Williams
@ 2008-03-05 20:53 ` Ahmed Ammar
2008-03-05 21:23 ` Dan Williams
0 siblings, 1 reply; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-05 20:53 UTC (permalink / raw)
To: Dan Williams; +Cc: Michael Buesch, linux-wireless
> 1) What's your wlan0? What driver is it using?
rt61pci. connected to same AP as i'm trying to get wlan1 to connect to.
> 2) What's your wlan1? What driver is it using?
b43.
> 3) Which interface are you having problems on?
wlan1.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 20:53 ` Ahmed Ammar
@ 2008-03-05 21:23 ` Dan Williams
2008-03-06 0:12 ` Ahmed Ammar
0 siblings, 1 reply; 11+ messages in thread
From: Dan Williams @ 2008-03-05 21:23 UTC (permalink / raw)
To: Ahmed Ammar; +Cc: Michael Buesch, linux-wireless
On Wed, 2008-03-05 at 20:53 +0000, Ahmed Ammar wrote:
> > 1) What's your wlan0? What driver is it using?
> rt61pci. connected to same AP as i'm trying to get wlan1 to connect to.
> > 2) What's your wlan1? What driver is it using?
> b43.
> > 3) Which interface are you having problems on?
> wlan1.
Ok; and you are _never_ able to associate with the AP with with wlan1,
correct?
Dan
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: B43 will not associate
2008-03-05 21:23 ` Dan Williams
@ 2008-03-06 0:12 ` Ahmed Ammar
0 siblings, 0 replies; 11+ messages in thread
From: Ahmed Ammar @ 2008-03-06 0:12 UTC (permalink / raw)
To: Dan Williams; +Cc: Michael Buesch, linux-wireless
> Ok; and you are _never_ able to associate with the AP with with wlan1,
> correct?
Yes. WPA/WEP/Open. nothing works.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2008-03-06 0:12 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-03-04 19:43 B43 will not associate Ahmed Ammar
2008-03-04 19:47 ` Michael Buesch
2008-03-04 22:13 ` Ahmed Ammar
2008-03-05 14:17 ` Michael Buesch
2008-03-05 15:26 ` Ahmed Ammar
2008-03-05 15:34 ` Ahmed Ammar
2008-03-05 18:16 ` Dan Williams
2008-03-05 20:53 ` Ahmed Ammar
2008-03-05 21:23 ` Dan Williams
2008-03-06 0:12 ` Ahmed Ammar
2008-03-05 15:49 ` Ahmed Ammar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox