My L5 is not connecting to my Mouse and Keyboard anymore 😠

ASwyD2 · January 23, 2024, 8:51pm

A couple months ago I had my Dell wireless keyboard and mouse hooked up to my L5 via a small apple usb-c hub.
Recently, it will not connect to my mouse even when using a variety of hubs available.
I even tried using a usb-c to usb-a direct adapter and it still won’t work.
I have not tried using a wired mouse but I did try another wireless mouse that did not work.
It will connect to a TV I have access to via a usb-c to hdmi adapter.
lsusb returns the adapter showing but not the mouse

Christal · January 23, 2024, 9:16pm

It could be a bug, or you have to follow some kind of an order.

First add your usb-c to usb-a adapter, and then attach the Mice and keyboard a few seconds later. I think this may be some race condition. Because it worked last time.You say you proved the Hardware with another system, so it just can be a software issue.

Can it be some kind of a power issue and about Voltage related too? Have Checks and error Messages aside ASwyD2 - however it can be a kernel driver issue. But if you do not know how to boot a specific Kernel on a Linux system try to be careful. Keep in mind that it could be some random cable brake issue, by a random wire expose/attache in the first place. Have a Check List to exclude every unlikely possibility first. Yes it could be a bad official purism update too.

irvinewade · January 23, 2024, 11:12pm

So this means a wireless keyboard and mouse combo using a nano receiver? As distinct from a fully wireless keyboard and mouse (Bluetooth)?

If the former, I assume that you have fault isolated the nano receiver in another computer? Batteries not flat in the keyboard or mouse? Mouse not faulty? Proprietary pairing problem?

Are you implying that the keyboard works? Or the keyboard doesn’t work either?

You might try a USB flash drive, as something simpler than USB-C to HDMI and simpler than a nano receiver.

ASwyD2 · January 24, 2024, 12:02am

Yes

All checked on a PC

No the keyboard does not work either.

I will try that. Thanks

I don’t know how to check.

There isn’t any cables

irvinewade · January 24, 2024, 12:55am

Running Linux?

ASwyD2 · January 24, 2024, 1:42am

No. Windows 11

ASwyD2 · January 24, 2024, 1:50am

@Ick
Is this similar to the problem you had in this thread

irvinewade · January 24, 2024, 2:53am

FWIW, this can work with the Librem 5.

When I plug in the USB-C to USB-A adapter to the Librem 5, root hubs appear in lsusb output.

When I plug in the Logitech nano receiver to the adapter, the nano receiver appears in lsusb output. NB: Logitech, not Dell. So not a definitive test. At this point a cursor appears on the screen also.

When I switch on the keyboard (which has a built-in trackpad), there is no change to lsusb output at all - but of course the keyboard can now be used and the cursor on the screen can be moved using the trackpad.

That is to say, lsusb -v output for the receiver reports the existence of two HIDs, the keyboard and the mouse, even when there aren’t any because the keyboard is switched off. (So I guess maybe the nano receiver hides the state transitions of the keyboard/mouse appearing and disappearing. Perhaps this is OK since these are only input devices. They just don’t generate any input when switched off.)

However, if I understand your situation, the nano receiver doesn’t even ever appear. (I like to capture lsusb output so that if something “used to work” and now “doesn’t” then I have something to compare with.)

Edit: PS byzantium, kernel 6.6.0-1-librem5

Ick · January 24, 2024, 2:58am

After restarting phone everything works as usual. So if it doesn’t work for you, it’s something different. Also I used journalctl --system to look at logs. I had a lot of spam log when error happens.

It’s too early to be sure, but I guess it’s something different. Since Kernel 6.6 an error seems to be fixed (too early to say), but I’ve got another error that seem to be caused by flashing my keyboard plus connecting via Bluetooth as next step. It seems that Bluetooth itself makes no troubles anymore (as I said “too early to be sure”), but the combination of both steps. And I’m sure you didn’t flash your devices. Restarting phone and connecting via Bluetooth or USB shouldn’t make any troubles anymore (at least I hope so).

ASwyD2 · January 24, 2024, 4:57am

This is it without anything attached:

purism@pureos:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM
Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is with the adapter attached:

purism@pureos:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM
Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

This is it with the nano chip plugged in:

purism@pureos:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM
Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb -v with everything attached

 purism@pureos:~$ lsusb -v

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         3 
  bMaxPacketSize0         9
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0003 3.0 root hub
  bcdDevice            6.06
  iManufacturer           3 Linux 6.6.0-1-librem5 xhci-hcd
  iProduct                2 xHCI Host Controller
  iSerial                 1 xhci-hcd.4.auto
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001f
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12
        bMaxBurst               0

Bus 001 Device 004: ID 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2020 
  idProduct          0x2060 
  bcdDevice            0.00
  iManufacturer           3 Qualcomm, Incorporated
  iProduct                2 Qualcomm CDMA Technologies MSM
  iSerial                 4 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0091
    bNumInterfaces          5
    bConfigurationValue     1
    iConfiguration          1 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    254 
      bInterfaceProtocol    255 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x88  EP 8 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0424 Microchip Technology, Inc. (formerly SMSC)
  idProduct          0x4041 Hub and media card controller
  bcdDevice            2.09
  iManufacturer           1 Generic
  iProduct                2 Ultra Fast Media Reader
  iSerial                 3 000008264001
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower               96mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0

Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x0424 Microchip Technology, Inc. (formerly SMSC)
  idProduct          0x2640 USB 2.0 Hub
  bcdDevice            9.02
  iManufacturer           0 
  iProduct                0 
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0019
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0001  1x 1 bytes
        bInterval              12

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            6.06
  iManufacturer           3 Linux 6.6.0-1-librem5 xhci-hcd
  iProduct                2 xHCI Host Controller
  iSerial                 1 xhci-hcd.4.auto
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0019
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         3 
  bMaxPacketSize0         9
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0003 3.0 root hub
  bcdDevice            6.06
  iManufacturer           3 Linux 6.6.0-1-librem5 xhci-hcd
  iProduct                2 xHCI Host Controller
  iSerial                 1 xhci-hcd.5.auto
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x001f
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12
        bMaxBurst               0

Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            9 Hub
  bDeviceSubClass         0 
  bDeviceProtocol         1 Single TT
  bMaxPacketSize0        64
  idVendor           0x1d6b Linux Foundation
  idProduct          0x0002 2.0 root hub
  bcdDevice            6.06
  iManufacturer           3 Linux 6.6.0-1-librem5 xhci-hcd
  iProduct                2 xHCI Host Controller
  iSerial                 1 xhci-hcd.5.auto
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0019
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         9 Hub
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 Full speed (or root) hub
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              12

irvinewade · January 24, 2024, 5:08am

In other words nothing? no change? not recognised?

(So the lsusb -v output is not relevant. I actually just meant lsusb -v on the one specific device, the nano receiver.)

Maybe take a look at the system journal to see whether anything gets reported when you plug in the nano receiver.

Do you have another Linux system that you could use to try the nano receiver on?

ASwyD2 · January 24, 2024, 5:24am

No, sadly It has worked previously on my L5 though.
How would I get the journalctl narrowed down to the usb?

irvinewade · January 24, 2024, 5:34am

You mean journalctl ?

Probably something like journalctl -b 0 | grep zzz where zzz is suitable to pick out the approximate time when you plugged in the nano receiver. For more specificity you can use --since= and/or --until= with journalctl but you will probably need to read the man page for the details.

ASwyD2 · January 24, 2024, 5:42am

I’m not finding anything that points to the nano receiver
I’ll probably work on it more in the morning. Thanks

Christal · January 25, 2024, 11:26pm

Oh… its USB with Bluetooth Dongle. OK. This way you can have two Systems which need to cooperate and likely another third one to take care, if your Keyboard is still working (Keyboard Hardware Check) and if its Battery is full (if it has some kind of Accumulator).

For the USB-BT-Dongle, you have to Check if your Kernel support that Dongle, but i’am not sure if there is something like a special driver needed for (some Bluetooth Device, cause i have not much Hardware to test) - if its worked before is more unlikely.

Your lsusb did not list any USB-Device through, after attaching or it needs more time. And its different if you have it attached before boot or just hot plug it later.

This way its good to have another Linux System to check, like what driver Modules got load and what Log-messages it tell after attaching. - Yes Computers are kind of complex.

But maybe, your device care about connected Bluetooth addresses and will only pair with a few. In that case you should have to take care about the dongle (and its Hardware Address), or other Devices in range, you already paired it with. And how you can flush the Hardware Pairings list, to connect to another device. I am sad to tell, but this is Hardware dependable and on Linux/Windows and Mac as OS, maybe Operating-System-individual too. And it may be different if you have only one Device in Range or more.

That was why i talk about some List for a check. And the empty battery will made it more complex.

Think your issue is less complex, cause its often just one rival, like have to many BT Devices connected near and use this with 3 or more Devices.

j_s · January 26, 2024, 12:18am

As covered in a number of posts above, probably not bluetooth.

irvinewade · January 26, 2024, 5:13am

That’s an interesting question. Because of this topic I had a look at some Dell wireless keyboard / mouse combos. It seems that some of them offer both of the following:

Bluetooth direct to a host that has Bluetooth hardware, and
nano receiver plugged into a USB port
(but presumably not both at the same time)

(It seems that the main motivation of the latter is that many systems don’t support Bluetooth in the early boot environment. So if you routinely need a keyboard to boot the computer, that is a problem. Obviously the nano receiver is also essential for those computers that don’t even have Bluetooth hardware.)

Does this imply that the nano receiver is simply a Bluetooth dongle? No, very likely it’s not. Does this imply that the nano receiver uses Bluetooth in some form? No, not necessarily. Would it be efficient design for the nano receiver to use Bluetooth in some form? Yes. It is my suspicion that the nano receiver is basically using Bluetooth but it pairs automatically and then just pretends that the host is looking at a USB keyboard and mouse. Of course with blackbox hardware we may never know.

ASwyD2 · January 26, 2024, 2:37pm

Yeah my Dad has one of those. It is very handy, but it wouldn’t connect to the L5 via bluetooth(redpine card).

It says that it is 2.4 but can we trust what they say?

j_s · January 26, 2024, 5:06pm

I had not heard of dual 2.4 GHz / bluetooth devices.

Sounds like a two edged sword of convenience and complicated trouble shooting / OS support.

I have always been frustrated by the ambiguity of the term “2.4 GHz wireless” because bluetooth and some wifi are also 2.4 GHz and all three are wireless.

ASwyD2 · January 26, 2024, 11:59pm

Mine isn’t bluetooth, but yeah.