[SOLVED] Broadcom wl driver not available upon resume on Linux 6.6.26
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I never hibernate but often suspend by simply closing the laptop lid. Noticed today that suspend/resume actions change - system no longer resumes after opening the lid, I have to hit the on/off button to resume. After resuming, no wifi connection and NetworkManager applet unresponsible.
Tried the suggested hook.sh file - put it in /lib64/elogind/system-sleep/ and made it executable. No change after rebooting.
Reverted to elogind-252.23-x86_64-2.txz and all is well (although now I get an issue with mate-power-manager, but not sure if that's really connected...)
This is better for me than restarting networkmanager, because that breaks Firefox and thunderbird.
I spoke too soon. By using the upower workaround the internet still works fine, and firefox and thunderbird work initially after a resume. But after a few minutes they do go wrong and need restarting anyway. So it looks like NM aware apps are just going to go wrong whichever workaround is used, so downgrade is the only reliable fix at the moment.
I've raised the issue at github.com/elogind. Hopefully some explanation/help/solution will come out of it.
logind.conf is ignored by 255.4 at the moment (at least on Slackware), I opened an issue on github about that yesterday. So anything you tested changing in the logind.conf files won't have done anything.
edit: Oh sorry, I just saw you referenced my issue there so do know about the logind.conf thing
On my system resuming from s2idle results in my mouse not working for some reason, so it seems to break more devices than real sleep does. I have always had SuspendMode set to deep because of that, and s2idle also keeps the PC running so not really sleeping at all.
I have just seen that the elogind developer also mentions s2idle.
You can check what sleep method your system is using in /var/log/messages, and see if it is different when using 252 instead of 255
Code:
fgrep "suspend entry" /var/log/messages
s2idle would explain why the LEDs stay on, but the network staying down problem happens whatever sleep mode is used.
(The last line is the important one, changed from default).
I also have the rebuilt NetworkManager, built with --with-suspend-resume=upower \ as mentioned in post #12 above.
Suspend/resume behaviour appears "normal" - the wifi LED goes off during suspend, wifi and bluetooth immediately active after resume. And suspend/resume by closing/opening laptop lid works. I have not encountered any problems with my browser (vivaldi) or mail client (thunderbird) that af7567 mentions in post #18
EDIT: Have to revoke the last lines - I do get issues with Thunderbird. So this is not a viable option. Sorry.
Just to know if is related: after rollbacking polkit and elogind, I'm experiencing the notify service of KDE failing and falling back to xfce4 one. Anyone else experience the same?
EDIT: tried upgrading to the current version of elogind and polkit with no result. I guess is not related. Rollbacked again and i'll open another thread about it
Just to know if is related: after rollbacking polkit and elogind, I'm experiencing the notify service of KDE failing and falling back to xfce4 one. Anyone else experience the same?
EDIT: tried upgrading to the current version of elogind and polkit with no result. I guess is not related. Rollbacked again and i'll open another thread about it
I just had a reboot after a couple of days and had the same thing happening.
I guess this is related, i'm investigating the changes:
Code:
Sun Apr 14 18:35:32 UTC 2024
...
xfce/xfce4-notifyd-0.9.4-x86_64-1.txz: Upgraded.
Almost everyone has jumped to this version, so we'll get with the program.
I just had a reboot after a couple of days and had the same thing happening.
I guess this is related, i'm investigating the changes:
Code:
Sun Apr 14 18:35:32 UTC 2024
...
xfce/xfce4-notifyd-0.9.4-x86_64-1.txz: Upgraded.
Almost everyone has jumped to this version, so we'll get with the program.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.