this post was submitted on 05 Aug 2023
66 points (91.2% liked)

No Stupid Questions

35800 readers
1311 users here now

No such thing. Ask away!

!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules (interactive)

Rule 1- All posts must be legitimate questions. All post titles must include a question.

All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.

Rule 2- Your question subject cannot be illegal or NSFW material.

Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.

Rule 3- Do not seek mental, medical and professional help here.

Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.

Rule 4- No self promotion or upvote-farming of any kind.

That's it.

Rule 5- No baiting or sealioning or promoting an agenda.

Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.

Rule 6- Regarding META posts and joke questions.

Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.

On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.

If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.

Rule 7- You can't intentionally annoy, mock, or harass other members.

If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.

Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.

Rule 8- All comments should try to stay relevant to their parent content.

Rule 9- Reposts from other platforms are not allowed.

Let everyone have their own content.

Rule 10- Majority of bots aren't allowed to participate here.

Credits

Our breathtaking icon was bestowed upon us by @Cevilia!

The greatest banner of all time: by @TheOneWithTheHair!

founded 1 year ago
MODERATORS
ja2@lemmy.world
_MoveSwiftly@lemmy.world
Rooki@lemmy.world
Thekingoflorda@lemmy.world
automodbeta@lemmy.world
L3s@lemmy.world
66
Why is it usually advised to power off your computer to have Bluetooth work again if it stopped working after a kernel update? (lemmy.world)
submitted 1 year ago by AlmightySnoo@lemmy.world to c/nostupidquestions@lemmy.world
15 comments fedilink hide all child comments
 

Often with a Linux kernel update, or even after a first install of Linux in place of Windows, Bluetooth stops working and the advice is usually to just power off your computer, wait a bit, and then turn it on again. Bluetooth then miraculously works again.

I mean the issue could also come from other things (not starting the right kernel module etc...), but very often it's just this simple trick that makes it work again.

So what is changing in the Bluetooth device when you do this power off/wait a bit/power on trick?

top 15 comments
sorted by: hot top controversial new old
[–] kittenbridgeasteroid@discuss.tchncs.de 38 points 1 year ago (2 children)

You're just trying to get the device into a known good state.

The truth is that it's rarely worth trying to find the root cause of an issue unless it's a frequent problem.

Something somewhere went wrong. We don't know if it's a hardware or software issue, so we'll try a solution that covers both.

Powering the device off stops the flow of electricity, and waiting a few seconds makes sure that any capacitors (think of very tiny, very fast batteries) bleed off the power they've stored. Then turning it back on makes it go through the full startup process which is likely to result in a working state.

[–] Ocelot@lemmy.world 22 points 1 year ago

As a non-technical person, someone on Reddit once explained in a way that makes sense to me as an analogy. Say you are on vacation for a week. Over the course of the week you get pretty good at going from point A to point B, and can even take small side trips along the way. But one day you get a little turned around, and you find you can’t get back to where you need to go. But if someone could pick you up and return you to your starting point, you could do just fine going about your business.

[–] jet@hackertalks.com 9 points 1 year ago

What the asteroid said is 100% true.

I just like to add that when you change system drivers you're adding a lot of unknown state into the equation, which you don't have on day-to-day operation. So it's even less worthwhile to debug what happened. You're not likely to update drivers everyday.

[–] Elephant0991@lemmy.bleh.au 12 points 1 year ago* (last edited 1 year ago)

Not saying this is the answer to your question, but generally, it's the hardware/software unaccounted-for states that can't easily be recovered from. So, rebooting would hopefully get it in a known "clean" state, and hopefully, not falling into that unaccounted-for state again.

Shitty, but works with some other things too. Angry, frustrated, hopeless? Sleep it off, maybe (not guaranteed) it will be better tomorrow.

[–] The_Hideous_Orgalorg@sh.itjust.works 8 points 1 year ago (1 children)

[–] dezmd@lemmy.world 8 points 1 year ago

To be fair, this is a recurring experience on Linux, Mac, and Windows of varying generations of equipment. As an educated guess it seems to be hardware states that cant be reset from software for whatever reason.

[–] addie 8 points 1 year ago (1 children)

Could also be that the Bluetooth kernel module is a loadable one, and if you've updated the kernel (which will usually take place pretty soon after a first install) then you won't have the matching folder of modules to load up until you restart. Arch is a bugger for this - I've an external mouse that works fine if you keep it plugged in during a kernel update, but it won't be recognised after an update until you restart again. Not a big deal - you can choose when to update.

[–] nothacking@discuss.tchncs.de 2 points 1 year ago

I believe Arch has an optional pacman hook to prevent this.

[–] FuglyDuck@lemmy.world 7 points 1 year ago (2 children)

So… this is Linux… You could try restarting the specific service. If that works. The advice was dumb and it was a software problem.

If it doesn’t, it was some type of weird hardware problem.

In my experience, though simply toggling the antenna (using the gui widget next to the clock, or gui settings-> Bluetooth off) works

[–] FartsWithAnAccent@lemmy.world 5 points 1 year ago (1 children)

You can restart services in Windows too but directing someone who is bad with tech would take too long, so it's common to tell them to just restart.

[–] FuglyDuck@lemmy.world 3 points 1 year ago (1 children)

Eh, as long as you know the service in question, you can restart it. Windows…. Doesn’t trust the user that much.

This includes the kernel…. No… thst doesn’t end well…

[–] FartsWithAnAccent@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

No, you'd tell them to restart a specific service (like print spooler) for whatever issue they're having and provide a little tutorial with pictures. No guarantee they won't still fuck up of course.

[–] notasandwich1948@sh.itjust.works 3 points 1 year ago

I once had rsync going and didn't want to stop it. my xorg somehow died, managed to restart that from ssh keeping the rsync running. had to use something to move the rsyncs to a screen first. kinda cool how you can almost always just restart parts of Linux instead of the whole thing

[–] spark947@lemm.ee 3 points 1 year ago

Can't confirm, but I would assume that there is a capacitor in a few bluetooth modules that keeps some of the components charged, and that they only try to comminicate with the kernel after a power cycle.