[SOLVED] wireless link light off after reboot

[paultgg]

I've managed to get my wireless working with the broadcom-wl driver (bcm43225). When the wl rpms install initially, the wireless comes up and works just fine. But after a reboot, the wireless link light doesn't come on, and no networks show.

It seems as if some sort of background command is run when the rpms install which fires up the hardware. I tried "modprobe wl", but the link light stayed off. Does anyone know how the rpms work, or what command I could set to run at boot time that would force the wireless hardware to come up? Thanks in advance.

MY SOLUTION: There were two interfaces listed for my wireless (wlan0 and eth1). In MCC, I used "Remove a Connection" to delete them both. Mageia added one back automatically, and everything's been good since.

[tom_]

have you tried with rfkill?

someting like

Code: Select all

rfkill unblock wlan0

could help you

[paultgg]

Thanks very much, I'll definitely try that. Unfortunately (?), it looks like it's auto-magically working now. Tried a cold boot last night (after using "modprobe wl" a number of times earlier) and it worked, and a cold boot this morning worked as well. Might be fixed, but I'll keep an eye on things and try the rfkill if anything goes amiss.

[doktor5000]

rfkill didn't seem to work. I noticed that if I reboot, the link light goes off, but if I cold boot, it will come back on...

[doktor5000]

Actually, now the link light is staying on fairly consistently. Sadly, at the moment, the light is on, but I can't connect to my network... Anyone have any thoughts?

[doktor5000]

I managed to get myself reconnected after having the link light on, but not being able to connect to the network. (Had to restart wpa_supplicant and ifplugd.) Seems pretty stable at the moment, although still don't know what the problem with the link light was in the first place...

[doktor5000]

Please next time do not use fullquotes, but only use the Reply function. Greatly improves clarity and reading flow