Ryan Hurley wrote: > Hi all, > > I'm running a newer Compaq laptop (v3000 series) which has one of these > wonderful broadcom PCI-E 4311 chips in them. I've been testing the > devicescape bcm43xx drivers from the wireless-dev tree for awhile, but > I still haven't gotten anything to work. This is the first time I've > submitted to a development list proper, so I apologize in advance if > I've forgotten anything or done something incorrectly. > --snip--
> > Even though lspci identifies this as a BCM4310 (UART), I've been told > that this is actually a 4311 core. > > I compiled a 2.6.19.1 <http://2.6.19.1> kernel to test out the new PCI-E > patches this afternoon, and while it compiled cleanly and was able to > scan, I was unable to associate with any access points, encrypted or > otherwise. The relevant parts of dmesg are: > > .... > [ 127.078000] bcm43xx driver > [ 127.080000] ACPI: PCI Interrupt Link [LK2E] enabled at IRQ 19 > [ 127.080000] ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LK2E] -> GSI > 19 (level, high) -> IRQ 20 > [ 127.080000] PCI: Setting latency timer of device 0000:01:00.0 to 64 > [ 127.087000] bcm43xx: Chip ID 0x4311, rev 0x1 It is a 4311. > [ 127.087000] bcm43xx: Number of cores: 4 > [ 127.087000] bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243, enabled > [ 127.087000] bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243, disabled > [ 127.087000] bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243, disabled > [ 127.087000] bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243, enabled > [ 127.088000] bcm43xx: PHY connected > [ 127.088000] bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8 > [ 127.088000] bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: > 2050 Rev: 2) > [ 127.088000] bcm43xx: Radio turned off > [ 127.088000] bcm43xx: Radio turned off > [ 127.153000] bcm43xx: PHY connected > [ 127.252000] bcm43xx: Microcode rev 0x127, pl 0xe (2005-04-18 02:36:27) > [ 127.260000] bcm43xx: Radio turned on > [ 127.260000 ] bcm43xx: Radio enabled by hardware > [ 127.449000] bcm43xx: Chip initialized > [ 127.449000] bcm43xx: 32-bit DMA initialized > [ 127.449000] bcm43xx: Keys cleared > [ 127.449000] bcm43xx: Selected 802.11 core (phytype 2) > [ 128.758000] SoftMAC: Authentication response received from > 00:11:50:a2:14:36 but no queue item exists. > [ 129.527000] bcm43xx: set security called, .level = 0, .enabled = 0, > .encrypt = 0 > [ 130.631000] bcm43xx: set security called, .level = 0, .enabled = 0, > .encrypt = 0 > [ 130.631000] bcm43xx: set security called, .level = 0, .enabled = 0, > .encrypt = 0 > [ 130.631000] bcm43xx: set security called, .level = 0, .enabled = 0, > .encrypt = 0 > [ 130.631000] bcm43xx: set security called, .level = 0, .enabled = 0, > .encrypt = 0 > [ 130.899000] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 130.899000] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 130.900000] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 136.380000] SoftMAC: Authentication response received from > 00:11:50:a2:14:36 but no queue item exists. > [ 137.977000] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 137.977000] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 137.978000 ] SoftMAC: Authentication response received from > 00:14:6c:03:c5:ff but no queue item exists. > [ 141.200000] bcm43xx: Radio turned off > > I turned the radio off myself when it failed to authenticate. I > repeated the process, (rmmod bcm43xx, modprobe 43xx, and then attempt to > connect) but got an identical result. If you do an 'iwlist s', what do you see? It seems that you have debugging turned on in SoftMAC, but I see no indication that anything attempted to scan. > Oh, and there's one other thing that I'd like to bring to the attention > of this list. The bcm43xx driver supplied with the default Ubuntu Edgy > kernel works. It runs very, very slowly (about 20 KB/s for download and > even slower for upload) but it identifies my chip and authenticates- the > whole 9 yards. Just a heads up. I'll have to pull that kernel to see what code is in there. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
