• [deleted]

  • Edited

WetGeek sudo mkdir -p /etc/modprobe.d

You can see it's shown by lspci, 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)

    [deleted] Intel Corporation Wireless 7260 (rev 73)

    Were you looking for a wireless device? Wireless has never given me a problem. It's the Bluetooth keyboard that sometimes stops unexpectedly.

      • [deleted]

      WetGeek Intel 7260 has integrated bluetooth.

        [deleted] Intel 7260 has integrated bluetooth.

        Yes, it does. What I'm looking for is something that causes the Bluetooth keyboard to stop working, while the Bluetooth settings continue to report that Bluetooth is ON, and the keyboard is paired, and connected. All the while, the wi-fi network controller has never been a problem.

          • [deleted]

          WetGeek sudo mkdir -p /etc/modprobe.d
          echo "options iwlwifi bt_coex_active=N" | sudo tee /etc/modprobe.d/iwlwifi-coex.conf

            [deleted]

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

              • [deleted]

              WetGeek You didn't make the directory

                [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]

                  WetGeek I literally instructed you to do so in my previous post

                    [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]

                      • Edited

                      WetGeek Yea, it's supposed to output that. But now it didn't complain about a missing directory so success.

                      What it did it was turn off the bluetooth coexistence feature of iwlwifi driver. That feature is known to cause issues with eg. audio streaming over Bluetooth when Wi-fi is enabled (as I told before, your Intel 7260 handles both wifi and bluetooth). So I thought it may be the culprit but apparently not, which is unfortunate.

                      If you wish to undo the changes, you can run sudo rm /etc/modprobe.d/iwlwifi-coex.conf which removes the modprobe file we created.

                        [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]

                          • Edited

                          WetGeek Yeah I just wanted to point it out in case you run into issues with wifi due to the settings or something.

                          Have you tried to change the power saving setting in Control Center? I think there's a setting in the Power section that allows the system to turn off bluetooth to save power. Turn that setting off. I would give you clearer instructions but I use Plasma 😄

                            [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] Turn that setting off.

                            It turns out that the setting you mentioned is rather puzzling. I turned it OFF, and it immediately turned OFF Bluetooth. I couldn't get it working again until I turned the setting back on, shutdown, and restarted. Apparently if you don't give it the ability to turn off the Bluetooth based on some usage timeout or other signal, it takes that to mean that you want it to be turned off unconditionally.

                              • [deleted]

                              WetGeek Ah right. It just turns Bluetooth off. A bit misleading option.

                              Let's see if this works
                              sudo mkdir -p /etc/bluetooth
                              echo -e "[General]\nIdleTimeout=0\n" | sudo tee /etc/bluetooth/input.conf

                              Then reboot and see if it makes a difference

                                [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.