Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
|
04-13-2024, 02:44 AM
|
#1
|
Member
Registered: Sep 2018
Location: Taipei/Taichung, TW
Distribution: Slackware
Posts: 114
Rep:
|
Broadcom wl driver not available upon resume on Linux 6.6.26
Hi,
A few days ago I upgraded from kernel 6.6.25 to 6.6.26, recompiled the broadcom-sta SlackBuild and installed it as usual, but unlike the previous build, Wi-Fi won't work after resuming from hibernation. modprobe -r wl then modprobe wl doesn't help.
Has anyone on -current also faced this issue? I've checked the Arch and Gentoo repos, and it seems like no patch is available yet.
-- ltlnx
Last edited by litelinux; 04-13-2024 at 02:44 AM.
Reason: missed space
|
|
|
04-13-2024, 03:16 AM
|
#2
|
Member
Registered: Apr 2016
Location: Detroit, MI
Distribution: Slackware
Posts: 233
|
I don’t generally hibernate my machine so I haven’t noticed anything nor have I seen any new patches. I’m away from my machine right now but I’ll do some tests when I’m around it to see how it behaves for me and report back.
|
|
|
04-13-2024, 04:47 AM
|
#3
|
Member
Registered: Feb 2016
Location: on the border of milky way
Distribution: Slackware
Posts: 159
Rep:
|
Bug confirmed
From Zenwalk tweaks , this hook fixes the problem :
/lib64/elogind/system-sleep/hook.sh
Code:
case $1/$2 in
pre/*)
for i in $( bluetoothctl devices | cut -f2 -d " " ); do
bluetoothctl info "$i" | grep -q "Connected: yes" && bluetoothctl disconnect "$i" && echo "$i" > /tmp/.last-bt-device
done
;;
post/*)
if [ -e /tmp/.last-bt-device ]; then
bluetoothctl connect "$(cat /tmp/.last-bt-device)"
rm -f /tmp/.last-bt-device
fi
/etc/rc.d/rc.networkmanager restart
;;
esac
All the best
|
|
2 members found this post helpful.
|
04-13-2024, 05:55 AM
|
#4
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
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...)
|
|
1 members found this post helpful.
|
04-13-2024, 07:04 AM
|
#5
|
Member
Registered: Feb 2016
Location: on the border of milky way
Distribution: Slackware
Posts: 159
Rep:
|
Quote:
Originally Posted by kgha
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...)
|
No need to reboot : just go to sleep and at resume : networkmanager will be restarted by the hook.sh. It can't "not" work
|
|
|
04-13-2024, 07:52 AM
|
#6
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
It actually can "not" work, at least here...
Maybe this has something to do with the confusing terms sleep/standby/suspend? Or have I missed something or made some mistake?
I'm on a fully upgraded -current (multilib) and the mate desktop, but behaviour is the same in a xfce session.
After suspending (by closing the laptop lid or choosing "suspend" from the shutdown menu) and resuming, the network connection is broken and the networkmanager applet is unresponsive/greyed out. The hook.sh script, placed in /lib64/elogind/system-sleep/ and made executable (-rwxr-xr-x) makes no difference at all. If I run the script in a terminal after having resumed, nothing happens.
Reverting to previous elogind version gets me the expected behaviour but affects some functions in the mate desktop (e.g disappearance of the shutdown menu).
I can choose "blank screen" instead of "suspend" as desired action when closing the lid. Then the network connection is still active and everything works when I open the lid (no need for the hook.sh script). I'll choose this as a workaround for now and hope for some kind of fix in a future elogind upgrade.
|
|
1 members found this post helpful.
|
04-13-2024, 08:11 AM
|
#7
|
Member
Registered: Jul 2019
Location: Europe
Distribution: Slackware64-current
Posts: 149
Rep:
|
Same issue here with Intel WiFi and KDE and I can confirm that the hook script does NOT work.
Edited to add: reverting to an older version of elogind solves the problem with the mentioned drawbacks
Last edited by z80; 04-13-2024 at 08:28 AM.
|
|
|
04-13-2024, 08:32 AM
|
#8
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
Just read this which seems to be relevant... https://github.com/elogind/elogind/r.../tag/v255.4-r1
Right now rebuilding elogind from this latest source file, will see what happens...
UPDATE: no difference, sadly.
Last edited by kgha; 04-13-2024 at 08:39 AM.
|
|
1 members found this post helpful.
|
04-13-2024, 08:58 AM
|
#9
|
Member
Registered: Jul 2019
Location: Europe
Distribution: Slackware64-current
Posts: 149
Rep:
|
If you revert polkit to polkit-123 shutdown / reboot / display brightness works as it should.
|
|
1 members found this post helpful.
|
04-13-2024, 09:34 AM
|
#10
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
Quote:
Originally Posted by z80
If you revert polkit to polkit-123 shutdown / reboot / display brightness works as it should.
|
Yes, downgrading both polkit and elogind solves both the suspend/resume issue and the problems with shutdown, brightness, power manager.
Tried rebuilding polkit-124 after upgrading to latest elogind, but that didn't change anything. So there must be some other interference somewhere...
|
|
|
04-13-2024, 12:14 PM
|
#11
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
Could the upower upgrade be involved somehow? Found this mentioning:
"-Dsuspend_resume=upower: Use this switch if you have UPower-1.90.4 installed and want to use it (instead of elogind-252.23 ) for suspend and resume support."
at https://www.linuxfromscratch.org/blf...rkmanager.html
Haven't tried rebuilding NM with that switch, though.
|
|
1 members found this post helpful.
|
04-13-2024, 12:58 PM
|
#12
|
Senior Member
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,162
|
OK, tried rebuilding NetworkManager with a change in the buildscript, line 136, from
Code:
--with-suspend-resume=elogind \
to
Code:
--with-suspend-resume=upower \
Now network connection (and the NM applet) is active after suspend/resume. However, it seems as if connection stays on during suspend. Previously, connection has been down during suspend, reconnecting after a few seconds. So upower doesn't seem to do anything.
Last edited by kgha; 04-13-2024 at 01:02 PM.
|
|
5 members found this post helpful.
|
04-13-2024, 06:40 PM
|
#13
|
Member
Registered: Sep 2018
Location: Taipei/Taichung, TW
Distribution: Slackware
Posts: 114
Original Poster
Rep:
|
Thanks for all the replies/testing! Can confirm downgrading both elogind and polkit works.
-- ltlnx
|
|
|
04-14-2024, 10:52 AM
|
#14
|
Member
Registered: Nov 2012
Posts: 299
Rep:
|
Recompiling with --with-suspend-resume=upower fixes it for me. Like kgha says, it seems to do "nothing" as in NM doesn't know the system is going to sleep so it doesn't bring down the network first. But it does still notice when the ethernet link comes back up and networking continues to work normally. This is the only message I get from NM when sleeping using the upower method:
Code:
NetworkManager[1217]: <info> [1713109578.3148] device (eth0): carrier: link connected
This is better for me than restarting networkmanager, because that breaks Firefox and thunderbird. If I restart NM then I also need to restart firefox and thunderbird otherwise they can't find the internet. So that kind of defeats the purpose of going to sleep in the first place a bit
|
|
|
04-14-2024, 11:34 AM
|
#15
|
Member
Registered: Feb 2016
Location: on the border of milky way
Distribution: Slackware
Posts: 159
Rep:
|
Quote:
Originally Posted by af7567
This is better for me than restarting networkmanager, because that breaks Firefox and thunderbird. If I restart NM then I also need to restart firefox and thunderbird otherwise they can't find the internet. So that kind of defeats the purpose of going to sleep in the first place a bit
|
Indeed
|
|
|
All times are GMT -5. The time now is 04:23 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|