Philipp E. Letschert wrote: > Hi all, > > > HP Compaq nx6325 laptop was already on the list for a few times, so I > would like to add my experiences: > > Im using kernel 2.6.21-rc6 with combined_2.6.21-rc6.patch applied. > > lspci -vn reports: > 30:00.0 0280: 14e4:4312 (rev 01) > > dmesg after modprobe bcm43xx and ifconfig eth1 up: > bcm43xx driver > ACPI: PCI Interrupt 0000:30:00.0[A] -> GSI 18 (level, low) -> IRQ 20 > PCI: Setting latency timer of device 0000:30:00.0 to 64 > bcm43xx: Chip ID 0x4311, rev 0x1 > bcm43xx: Number of cores: 4 > bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243 > bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243 > bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243 > bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243 > bcm43xx: PHY connected > bcm43xx: Detected PHY: Analog: 4, Type 2, Revision 8 > bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) > bcm43xx: Radio turned off > bcm43xx: Radio turned off > bcm43xx: PHY connected > bcm43xx: Microcode rev 0x118, pl 0x17 (2004-05-06 21:34:00) > bcm43xx: Radio turned on > bcm43xx: Radio enabled by hardware > bcm43xx: Chip initialized > bcm43xx: 32-bit DMA initialized > bcm43xx: Keys cleared > bcm43xx: Selected 802.11 core (phytype 2) > > First question: > Shouldnt the driver report Chip ID 0x4312 as lspci does?
No. The PCI id is different from the chip ID. Actually the programming of the device is mostly dependent on PHY and radio parameters. > Second: How important is the firmware version? Im using 3.70.22.0, as > recommended by Larry, but was also able to load 3.100.65.1, so I don't > know if this has an impact on the driver. It shouldn't matter. > btw, if it helps for development of 4.x support, the latest HP driver > for the nx6325 is located at > http://ftp.hp.com/pub/softpaq/sp34001-34500/sp34152.exe with firmware > version 4.100.15.5. > > > LED functionality: > > after `ifconfig eth1 up' the LED turns on, and using the WLAN keyboard > switch turns the LED on and off. But this has no impact on the driver, > WLAN seems to work, even with LED turned off. > > Using ndiswrapper, the LED turns on right after loading the module and > the keyboard switch turns LED on and off and additionally > enables/disables the device. In bcm43xx, the LED will never turn on until after the interface is brought up. That is deliberate. Are there any messages about "Radio hardware status changed" in the dmesg output? My laptop with a 4311 has a switch on the front lip, not on the keyboard, the LED changes with the switch and the radio is disabled by the hardware. If yours behaves differently, we should change it, but if the hardware status changes do not propagate, I'm not sure what we can do. > With both drivers, when rebooting the laptop with LED switched on, it > stays on, even when no driver is loaded and no device is available. So I > manually unload the driver during shutdown, so the LED goes off before > rebooting. That is a manifestation of the same problem. > Device corruption: > > this has been mentioned on the list before, and was also observed here: > When using 2.6.20 unpatched kernel and rebooting the laptop with bcm43xx > loaded and interface up, the device gets somehow corrupted. > After rebooting it was impossible to get the device working again. > Neither with bcm43xx nor ndiswrapper, power off didnt help either. The > only solution I found was to select 'Restore Defaults'->'Save' in the > laptops BIOS, and the device did work again. (The laptop BIOS version is > F.06) > > However this issue has been resolved using 2.6.21-rc6 with combined > patch applied. No PCIe device works on an unpatched 2.6.20 kernel. You need 2.6.20.4 or later. The reason is that PCIe interrupts are not passed on, which obviously confuses your BIOS, and jams up interrupts on the appropriate IRQ line. I'm surprised that turning off the power didn't get it reset. > Rate settings: > > setting a rate with iwconfig seems to have no effect, its always 1M > (with ndiswrapper its always 54M). But this could be a result of > unsupported wireless extensions? > > Warning: Driver for device eth1 has been compiled with version 22 > of Wireless Extension, while this program supports up to version 20. > Some things may be broken... No - The VERSION message is just a standard one. With 2.6.21-rc6, the rate is initialized at 24M. If it has been downgraded to 1M, it must be a consequence of the strength of your signal. What are the signal strengths, etc. shown by iwconfig? Larry _______________________________________________ Bcm43xx-dev mailing list [EMAIL PROTECTED] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
