Shocky wrote: > Hi, > > I recently bought an HP Pavilion dv2412ca laptop, which came with Vista > pre-installed. I backed it up, then reformatted and installed Mandriva > 2007.1. > > The laptop has a builtin wireless card that lspci identifies as a "Broadcom > Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 02)". I couldn't get > it working with either bcm43xx or ndiswrapper using the Vista driver. > > I got an XP driver for it from the HP support web site (sp34152.exe), and was > able to extract it using wine. I still couldn't get it to work with bcm43xx, > but I got it sort of working with ndiswrapper. I say "sort of" because it was > very flakey. It would usually connect when I first booted if the AP was > within reach, but if it lost the signal there was no way to make it reconnect > other than rebooting, and it wouldn't reconnect after suspend. This was with > Mandriva's 2.6.17-13 kernel, and wireless_tools version 28. I upgraded the > kernel to 2.6.17-15 (the latest available for 2007.1), but that didn't help. > > Now I'm trying again with bcm43xx. I downloaded the source tarball for 2.6.22 > from kernel.org and built a custom kernel (and I turned on wireless and > bcm43xx debugging while I was at it). I also got an SRPM from Mandriva cooker > for wireless_tools version 29 and built and installed it. > > lspci -vn gives me: > > 01:00.0 0280: 14e4:4311 (rev 02) > Subsystem: 103c:1374 > Flags: bus master, fast devsel, latency 0, IRQ 20 > Memory at c3000000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [40] Power Management version 3 > Capabilities: [58] Vendor Specific Information > Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 > Enable- > Capabilities: [d0] Express Endpoint IRQ 0 > Capabilities: [100] Advanced Error Reporting > Capabilities: [13c] Virtual Channel > Capabilities: [160] Device Serial Number 1a-00-5c-ff-ff-73-3d-b9 > Capabilities: [16c] Power Budgeting
..snip.. > ... > Sep 20 15:46:33 rllt01 kernel: bcm43xx: Chip ID 0x4311, rev 0x2 > Sep 20 15:46:33 rllt01 kernel: bcm43xx: Number of cores: 4 > Sep 20 15:46:33 rllt01 kernel: bcm43xx: Core 0: ID 0x800, rev 0x13, vendor > 0x4243 > Sep 20 15:46:33 rllt01 kernel: bcm43xx: Core 1: ID 0x812, rev 0xd, vendor > 0x4243 > Sep 20 15:46:33 rllt01 kernel: bcm43xx: Unsupported 80211 core revision 13 The above message is pretty clear. We don't support that 80211 core revision (yet). It will not be properly supported until our reverse engineers have a chance to find out what special programming is needed for that device. It may, or may not work. I have no way to predict that. > ... > Sep 20 15:46:37 rllt01 kernel: bcm43xx: PHY connected > Sep 20 15:46:37 rllt01 kernel: bcm43xx: Microcode rev 0x173, pl 0x425 > (2006-10-04 21:02:04) > Sep 20 15:46:37 rllt01 kernel: bcm43xx: Firmware: no support for microcode > extracted from version 4.x binary drivers. You need to get a version 3.x driver to use bcm43xx. The place to get one is listed below. > These "core up ... failed" messages continue to appear in the log once per > second. I suspect the message about version 4.x drivers not being supported > is the problem. Only part of the problem, but a killer for sure. > If I try to bring up the interface manually, I get the error "SIOCSIFFLAGS: > Operation not supported". > > Should I try to find an older driver? Is it likely to work with my newer > hardware? Partially. > I can help try to add support for 4.x drivers if anyone is interested. I am > an > experienced developer, though not on Linux, and especially not on device > drivers. Not needed. In the near future, bcm43xx will be replaced by a driver named b43, which supports V4 firmware. To get a V3 driver, please go to "http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o";. Grab that driver, extract the firmware, and see what happens. Send the bcm43xx messages from the new trial. Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
