You are not logged in.
I noticed that my bluetooth mouse, which works perfectly when I use my laptop with WiFi connection, becomes really laggy when I'm using a cabled connection. The laptop is a Dell XPS 15 9570 from 2018, and I use a Startech DKT30CSDHPD USB-C dongle that provides the ethernet port. I made several tests by removing and attaching the ethernet cable and the issue is 100% reproducible.
I don't have an idea about what can cause this malfunctioning, any hints? Thanks.
Offline
Is it possible to test the following configurations?
1. Bluetooth via the mentioned USB-C hub, Ethernet directly into the laptop without the USB-C hub
2. Bluetooth directly with the laptop without the USB-C hub, Ethernet via the USB-C hub
If either of these configurations work I'm thinking maybe it could be a question of bandwidth or even interference from the Ethernet current disrupting the Bluetooth signal even if it sounds quite odd.
Offline
Hi Maritim, 1. is not feasible since my laptop has no ethernet port and the USB-C hub has no Bluetooth interface. So practically all of my testing has been done in situation 2. I also don't have another USB ethernet dongle to test different hardware.
Offline
What is the output of lsusb with the Ethernet dongle attached to the USB-C port?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
@ewaller The lines that appear when plugging the USB-C dongle are:
Bus 001 Device 017: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 018: ID 05e3:0618 Genesys Logic, Inc. Hub
Bus 001 Device 019: ID 05e3:0752 Genesys Logic, Inc. micros Reader
Bus 001 Device 020: ID 2109:0100 VIA Labs, Inc. USB 2.0 BILLBOARD
Bus 003 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 004 Device 003: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 004 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Offline
Dang. I was hoping to find the Ethernet Adapter and the Bluetooth on the same bus. They aren't.
But, I also don't even see a Bluetooth module on any bus.
Is your Bluetooth integrated with your WiFi NIC? That could be a clue.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Yes the Bluetooth is integrated in the Killer 1535 WiFi card. Anyway this is the complete lsusb output (please notice that I have mouse and keyboard attached to the USB-C dongle at the moment, but I didn't have while testing the problem with the Bluetooth mouse) :
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0
Bus 001 Device 004: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader
Bus 001 Device 006: ID 0bda:5657 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 017: ID 2109:2813 VIA Labs, Inc. VL813 Hub
Bus 001 Device 018: ID 05e3:0618 Genesys Logic, Inc. Hub
Bus 001 Device 019: ID 05e3:0752 Genesys Logic, Inc. micros Reader
Bus 001 Device 020: ID 2109:0100 VIA Labs, Inc. USB 2.0 BILLBOARD
Bus 001 Device 021: ID 046a:b090 CHERRY Keyboard
Bus 001 Device 022: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 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 004 Device 003: ID 2109:0813 VIA Labs, Inc. VL813 Hub
Bus 004 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Offline
Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0That is new.
the Bluetooth is integrated in the Killer 1535 WiFi card
Have you two Bluetooth interfaces?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
The "Qualcomm Atheros Communications QCA61x4 Bluetooth 4.0" is present also when the USB-C dongle is not attached, that's why I didn't include it in the first lsusb output. As for the second question, I'm not sure: the Killer 1535 WiFi card has integrated Bluetooth 4.1, and I always assumed it's what my laptop is actually using. but now I'm doubting it, is there any way to check which WiFi module is actually in use?
Offline
"Killer" cards is marketing speech for what ultimately amounts to a qualcomm atheros chipset so you're likely seeing and talking about the same thing -- the BT integrated into the Wifi NIC.
When your network is on the cable, is normal "Wifi" explicitly disabled or potentially going crazy trying to scan for interfaces for no reason? e.g. if you're using networkmanager it should be very chatty about that in the journal, maybe try explicitly rfkilling the wifi while on cable or so.
Last edited by V1del (2024-05-28 16:12:40)
Offline
What are the output of:
bluetoothctl list
and
bluetoothctl show
?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
If it's not wifi interference, please specify "using"
1. plugging in the dongle
2. plugging a cable into the dongle
3. briging the NIC up
4. watching 8k online-porn videos
Offline
@ewaller here it is:
$ bluetoothctl list
Controller 9C:B6:D0:BE:BD:8E stryke [default]
$ bluetoothctl show
Controller 9C:B6:D0:BE:BD:8E (public)
Manufacturer: 0x001d (29)
Version: 0x08 (8)
Name: stryke
Alias: stryke
Class: 0x006c010c (7078156)
Powered: yes
PowerState: on
Discoverable: yes
DiscoverableTimeout: 0x00000000 (0)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d054C
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: appearance
SupportedIncludes: local-name@seth the problem appears when I bring up the NIC integrated in the dongle after plugging the cable, also with no Internet traffic (I wish I had a 8k screen for porn).
Last edited by snack (2024-05-29 06:22:03)
Offline
When your network is on the cable, is normal "Wifi" explicitly disabled or potentially going crazy trying to scan for interfaces for no reason? e.g. if you're using networkmanager it should be very chatty about that in the journal, maybe try explicitly rfkilling the wifi while on cable or so.
In doubt rfkill the wifi.
Offline
I have a systemd script that automatically turns off the WiFi interface when the cabled one is connected, so the WiFi is of although not rfkilled. Anyway ATM it seems that the mouse works well also with the ethernet cable plugged on the USB-C dongle; I don't know what happened but the issue seems fixed. I'll monitor it since I'm not sure: most of the times I saw the misbehavior at work, where it was consistently reproducible., but now I'm at home and everything seem to work. So I'll try again at work and let you know.
In the meantime let me thank all of you for the help!
Offline