I got this error after opening my laptop, I am using Kubuntu
Thanks in advance
UPDATE:
I fixed it by looking in system logs and I realised something was wrong ith the cloned mac address and I fixed it and now it works.
I got this error after opening my laptop, I am using Kubuntu
Thanks in advance
UPDATE:
I fixed it by looking in system logs and I realised something was wrong ith the cloned mac address and I fixed it and now it works.
17 Comments
Havatra@lemmy.zip · 10 pts · 6d
Some more info would help:
And just to ask the painfully stereotypical tech support question: You've tried rebooting it?
Monkey@piefed.social · 3 pts · 6d
Havatra@lemmy.zip · 4 pts · 6d
So the issue started appearing after a hibernation/suspend? Personally I feel like there are so many issues (on all platforms) related to suspending a system instead of shutting it down, and this is an issue I've had myself.
Try following this guide: https://www.baeldung.com/linux/wifi-connection-fix-no-reboot
lspci -knnto list kernel modules, and find your wifi module.sudo rmmod [your_wifi_driver]to remove itsudo modprobe [your_wifi_driver]to load itThe site also shows how to make automation script and stuff too, and alternative solutions.
I hope it's not too complex, but I can try and help run you through some of it if you need.
Monkey@piefed.social · 1 pts · 5d
Havatra@lemmy.zip · 1 pts · 5d
Ah, remove the brackets
Monkey@piefed.social · 1 pts · 5d
I did it without the braxkets and it worked but I still get that notification/error
Havatra@lemmy.zip · 1 pts · 5d
Did any of the other methods in the article work?
Monkey@piefed.social · 1 pts · 5d
Nope, not yet
TootSweet@lemmy.world · 3 pts · 6d
Monkey@piefed.social · 3 pts · 6d
Thanks for the help.
TootSweet@lemmy.world · 3 pts · 6d
Ah! Not just when it comes back from suspend. Also... all other times as well. Heh.
First thing I'd try is to open up the network configuration interface. (My understanding is that there's a system tray icon for that.) Probably just try checking that everything looks right in the WIFI section of that interface first off. (That the SSID looks right, maybe type your password in again just to make sure it's right, that kind of thing. Basically as if you've never connected to that SSID/access point before and you're connecting for the first time.) It might be that your WIFI device changed its name recently during an update and the settings you had configured previously are associated with a WIFI device of a different name, so configuring the WIFI device under the new name may do the trick.
If that doesn't do it, a few more things to try:
journalctl -b | grep wifi. That might point to a problem.ip linkandip addr.nmcli dev wifijust to make sure the SSID(s) you're expecting appear as you expect and has decent signal strength. (Of course, if the SSID is hidden, I guess this will be less helpful.)(The sidebar here says it's against the rules to share logs and such, so maybe the output of the above commands should be shared via pastebin or some such.)
Monkey@piefed.social · 2 pts · 5d
Nevermind, I got it fixed a different way (see the upddate to the post), thanks for trying to help though.
TootSweet@lemmy.world · 2 pts · 5d
Great stuff! Glad to hear you've got things working.
Might be worthwhile to include whatever additional specifics about the issue you were having and what fix you applied that you can (without doxing yourself or anything like that, of course) if only for the benefit of any random person in the future with the same issue who might run across this thread. Just a thought. ;)