Larry Finger schrieb am Do, 12.04.2007 (13:08:31 -0500): > Philipp E. Letschert wrote: > >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.
I finally found out what my "corruption bug" was about: In kernel 2.6.20.4 the LED didn't work, when pressing the switch (btw. it is not directly on the keyboard, but a separate switch right above, with an integrated LED) and there were no "Radio hardware status changed" messages. So I assumed the switch doesnt work at all. But that was wrong, I silently disabled the device (with the LED still on) and it stayed disabled, even when turning power off. All I should have done, was to press the switch once more (even with LED already on), instead of resetting the BIOS. Finding this kept me busy for a few hours... In patched 2.6.21-rc6 LED works fine, and the "Radio hardware status changed" messages show up. Again I was wrong in thinking the switch doesnt turn off the device properly. It just doesnt switch off immediately. After pressing and the LED is off, you still have a result from "iwlist scan" for a some seconds, before the device is finally disabled - bad tester I am. I try to describe the LEDs behaviour: 1. Initial boot, hardware enabled, LED is off, no module loaded 2. modprobe bcm43xx, ifconfig ethx up 3. LED is on, Device is working 4. Reboot 5. Hardware enabled, LED is on, no module loaded 6. modprobe bcm43xx 7. LED goes off 8. ifconfig ethx up 9. LED goes on, device is working 10. pressing WLAN switch 11. LED goes off, device is not working 12. Power off, Boot 13. Hardware disabled, LED is off, no module loaded 14. modprobe bcm43xx, ifconfig ethx up 15. LED doesn't turn on, hardware still disabled, device not working 16. pressing WLAN switch 17. LED goes on, device is working This is all ok and I dont know if other devices are the same, but I could imagine a different behaviour: - loading the module initially disables the hardware, never mind if it was enabled or disabled before - doing ifconfig ethx up enables hardware (and LED) or pressing WLAN switch enables hardware and does ifconfig ethx up - doing ifconfig ethx down disables hardware or pressing WLAN switch disables hardware and does ifconfig ethx down - doing a reboot disables the hardware and turns the LED off. > >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? Ah, I had no AP associated, so no signal strength and no rate changing. Thanks for helping and all the explanation! Regards, Philipp _______________________________________________ Bcm43xx-dev mailing list [EMAIL PROTECTED] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
