Description of problem: On Fedora 7, during the boot process, the blue wifi LED on this laptop turned on when NetworkManager was started. On Fedora 8, the process is reversed : the light is turned on during the boot process and once NetworkManager is launched the LED is turned OFF. It should be the contrary : no light during the boot process and turned on when NM get started. Please help me to help you debugging this, as I really don't know which component is affected. Thanks.
Initial guess would be kernel (driver), followed by NM, and then HAL. If you do 'ip link set dev <whatever the device is> down', does the light change?
Unfortunately no it does not do anything concerning the light... It cuts off the connection, but nm-applet does not notice either.
Does using the F7 kernel in F8 yield any different behavior?
Yes, but not for the wifi led. I could decide to give life or not to the (un)mute led with the f7 kernel on f8 when I pushed the mute switch. But nothing for the wifi even before NM get loaded.
Assigning to hal-info - looks like there's a quirk wrong somewhere?
I doubt it. I think it's actually the kernel driver but I think dcbw knows better than me. So -> NM.
In fact as I noticed it in #4, the led of the (un)mute button is also no more functional, and it worked as well on f7. I don't know if managing both led is link to the same device or not however.
The wifi LED came back with the 2.6.23.14-107.fc8 kernel, but not the mute LED :)
yeah, kernel bug... might ACPI related or require some kernel module to be loaded to handle special keys and LED behavior like asus_acpi or tpbuttons.
ok everything is back to order now. I love these bugs that solve themselves by magic :)