You are not logged in.
I am trying to connect the SteelSeries Arctis 7 Bluetooth headset.
But the bluetooth dongle doesn't show up in bluetoothctl. I get the message:
No default controller available
When I plug the dongle into USB the following show up in the journal:
Dec 02 00:12:53 kasperarch kernel: usb 1-1.4: new full-speed USB device number 7 using ehci-pci
Dec 02 00:12:54 kasperarch kernel: usb 1-1.4: New USB device found, idVendor=1038, idProduct=12ad, bcdDevice= 1.19
Dec 02 00:12:54 kasperarch kernel: usb 1-1.4: New USB device strings: Mfr=4, Product=5, SerialNumber=0
Dec 02 00:12:54 kasperarch kernel: usb 1-1.4: Product: SteelSeries Arctis 7
Dec 02 00:12:54 kasperarch kernel: usb 1-1.4: Manufacturer: SteelSeries
Dec 02 00:12:54 kasperarch kernel: input: SteelSeries SteelSeries Arctis 7 Consumer Control as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.5/0003:1038:12AD.000B/input/input44
Dec 02 00:12:54 kasperarch kernel: input: SteelSeries SteelSeries Arctis 7 as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.5/0003:1038:12AD.000B/input/input46
Dec 02 00:12:54 kasperarch kernel: hid-generic 0003:1038:12AD.000B: input,hiddev0,hidraw3: USB HID v1.11 Device [SteelSeries SteelSeries Arctis 7] on usb-0000:00:1a.0-1.4/input5
Dec 02 00:12:54 kasperarch mtp-probe[3204]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4"
Dec 02 00:12:54 kasperarch mtp-probe[3204]: bus: 1, device: 7 was not an MTP device
***
Dec 02 00:12:54 kasperarch mtp-probe[3230]: checking bus 1, device 7: "/sys/devices/pci0000:00/0000>
Dec 02 00:12:54 kasperarch mtp-probe[3230]: bus: 1, device: 7 was not an MTP device
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 3 threads of 1 processes of 1 users.
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Successfully made thread 3233 of process 762 owned by>
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 4 threads of 1 processes of 1 users.
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 4 threads of 1 processes of 1 users.
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Successfully made thread 3234 of process 762 owned by>
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 5 threads of 1 processes of 1 users.
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 5 threads of 1 processes of 1 users.
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Successfully made thread 3235 of process 762 owned by>
Dec 02 00:12:54 kasperarch rtkit-daemon[763]: Supervising 6 threads of 1 processes of 1 users.
I omitted some KDE messages.
The bluetooth.service and btusb kernel module are loaded and running (though I have to load btusb manually), but there is no mention of Bluetooth in the journal.
the bluez packages and pulseaudio-bluetooth are installed.
Is there something else I need to do to be able to connect my headset to my computer using the USB adapter?
Edit: turns out it is not bluetooth, just wireless.
Last edited by kas0079 (2019-12-02 03:24:23)
Offline
Offline
Thank you for your reply.
I have read that page. I run my problem when I try to follow the procedure there to pair the devices.
I suspect my problem is that the dongle is detected as a HID rather than a HCI device. As the troubleshooting section suggests might be a problem.
I have tried unsuccessfully to change the mode using hid2hci.
[kasper@kasperarch ~]$ sudo hid2hci --devpath=devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.5 --method=logitech-hid
error: could not find hiddev device node
The 3 other --method= of hid2hci fail with
Control transfer failed: Broken pipe (32)
As neither the manpage or the wiki specifies how to find it, I am not sure the --devpath is correct. But 1-1.4 is the USB dongle and the 1-1.4:1.5 folder appears to be the HID since its uevent file has the line:
DRIVER=hid-generic
where the other folders in 1-1.4 (1-1.4:1.0 to 1-1.4:1.4) have snd-usb-audio.
Offline
After looking at the manufacturers page it seems that the arctis 7 is not bluetooth.
Does Arctis 7 have Bluetooth?
No, the Arctis 7 uses a lossless, low latency 2.4 GHz wireless technology that is made specifically for gaming. This provides superior audio quality and is not subject to the potentially long latencies that can occur with Bluetooth
https://steelseries.com/gaming-headsets/arctis-7
Edit: I thought it said there is analog connection available.
Edit1: You might try someting like this..
https://baldpenguin.blogspot.com/2017/0 … linux.html
Lots of info if you google 'steelseries arctis 7 linux'
Last edited by Zod (2019-12-02 02:27:57)
Offline
After looking at the manufacturers page it seems that the arctis 7 is not bluetooth.
Arctis 7s' webpage wrote:Does Arctis 7 have Bluetooth?
No, the Arctis 7 uses a lossless, low latency 2.4 GHz wireless technology that is made specifically for gaming. This provides superior audio quality and is not subject to the potentially long latencies that can occur with Bluetoothhttps://steelseries.com/gaming-headsets/arctis-7
Edit: I thought it said there is analog connection available.
Edit1: You might try someting like this..
https://baldpenguin.blogspot.com/2017/0 … linux.htmlLots of info if you google 'steelseries arctis 7 linux'
I completely missed that it was not a bluetooth dongle but just a wireless one.
It also turns out that the headset and adapter were already paired out of the box (a quickstart video for Windows mentioned it), and the audio and mic works, so I didn't need to do any of this. If only I had noticed that the adapter's light changes from blinking to constant, when I turn on the headset..
I had seen that blog post before, which is why I was confused as to why I couldn't connect it with bluetoothctl, since other people didn't seem to have problems with pairing them.
Thank you so much for your time, I am going to mark this as solved.
In conclusion: bluetoothctl doesn't work because it is not bluetooth. The adapter and headset are already linked, so bluetoothctl is uneeded anyway.
Additionally. The mono-channel-only problem that people talked about on reddit and on that blog doesn't seem to be a problem anymore, since I had stereo audio without having to do anything special.
I'm going to test tomorrow if I can unpair and pair using the buttons on the dongle and headset. (I have Windows available in case I can't)
Last edited by kas0079 (2019-12-02 03:24:53)
Offline