Bluetooth Issue

[deleted]

tee: /etc/modprobe.d/iwlwifi-coex.conf: No such file or directory
options iwlwifi bt_coex_active=N

[deleted] You didn't make the directory

Of course I didn't. I had no idea a new directory was needed.

I've never needed to create a directory in order for any other Bluetooth device (like my earbuds) to work right.

[deleted] I literally instructed you to do so in my previous post

Sorry ... I must have thought that first line was a quote, or something. At any rate, the result of the query is the same:

options iwlwifi bt_coex_active=N

My keyboard is still working this morning, so something I've done during this adventure might have actually been the solution to this problem, but I won't know for sure until it's kept working longer than overnight. I'll know if it's really fixed when I only need to restart the laptop after each week's upgrades.

At any rate, thanks again for your help with this. I'm convinced it's a hardware issue, as I have another of these same keyboards connected to the media computer that streams content to my TV, and I've never experienced this issue with
that machine.

AW, RATS! Keyboard just quit. I'm typing this line on the laptop's keyboard. Did that modprobe result provide any useful clue as to whatever the root cause of the issue is?

[deleted] f you wish to undo the changes,

There seems to be little reason to undo something that hasn't actually changed anything. As my arm continues slowly to heal, before too long I'll be able to reach the laptop on its stand, and type on it the way I always have done. I can keep this keyboard as a spare for the media computer. Until then, I'll just put up with restarting the laptop when I need to, and have a lot of typing to do.

Thanks again for your help. If you happen to think of anything else I should try, please let me know, but otherwise I'm going to just deal with it as best I can for now.

[deleted] Turn that setting off.

Yes. I'd seen that before, but forgotten about it. I just turned it OFF, and will see what effect that has.

[deleted] Let's see if this works

If I continue to have trouble with it, I'll give that a try. For now, it's been working well for me all day so far. I hope it continues that way ... I'm pretty tired of restarting the laptop.

[deleted] Let's see if this works

That didn't take long. The keyboard quit soon after I answered you. I strongly suspect that it's not a timeout issue, though, because at least twice it's happened while I was in the middle of typing a reply to someone in Parler. The keyboard was definitely not idle.

WetGeek I'm not sure I actually invoked this.

Well, now I'm sure I got the job done. This morning the keyboard was dead again, so I repeated that command, and this time the prompt returned immediately. Now I can evaluate whether it's had any effect. The keyboard is once again working, and I can't wait to find out how long it lasts this time.

That didn't last long. Two hours later the keyboard quit again while I was typing something, so I think our thinking long the lines of a timeout may be faulty. I've removed all the stuff I added to /etc, and rebooted. I wanted to make sure I didn't forget, and leave something there.

I'm not sure what line of enquiry to take next, but I'll continue to work on it. Fortunately, Solus restarts so quickly that most of the time the need to do that isn't a huge annoyance ... just a frequent one for me.

SOLUSfiddler how is your BT keyboard powered

It has an internal lithium-ion battery that's fully charged. It has a multicolor LED that indicates when it's becoming discharged by flashing and turns red when the battery is depleted.

I've undone everything that I've done so far during this adventure, including un-pairing the keyboard and starting over from the beginning. The keyboard battery is supposedly good for 60+ hours on a charge, and it has a standby mode that engages after 10 minutes of non-use. One exits standby mode by pressing any key and waiting 3 seconds. I've never seen the LED flashing, so I'm not sure it's ever been run down.

Online research into troubleshooting this model keyboard has me wondering whether the original pairing occurred normally, which is why I've redone that from the beginning. All's working well at the moment, but it will take a couple days of correct operation before I'm ready to believe that it's really fixed.