Skip to content

Steelseries Arctis Pro is not recognized #151

Description

@adlerzei

Hi,
I recently bought a new Arctis Pro but it is not recognized by HeadsetControl.

christian@christian-PC:~$ headsetcontrol
No supported headset found

I requested more information about my USB devices to add the idProduct to the code if it differs:

christian@christian-PC:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Webcam
Bus 001 Device 007: ID 8087:0a2a Intel Corp. 
Bus 001 Device 014: ID 248a:8367 Maxxter Wireless Receiver
Bus 001 Device 012: ID 1038:1297 SteelSeries ApS 
Bus 001 Device 011: ID 1038:1290 SteelSeries ApS Wireless Receiver
Bus 001 Device 009: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and changed line 10 - 14 in steelseries_arctis_7.c to:

#define ID_ARCTIS_7        0x1260
#define ID_ARCTIS_7_2019   0x12ad
#define ID_ARCTIS_PRO_2019 0x1252
#define ID_ARCTIS_PRO_NEW 0x1290

static const uint16_t PRODUCT_IDS[] = { ID_ARCTIS_7, ID_ARCTIS_7_2019, ID_ARCTIS_PRO_2019, ID_ARCTIS_PRO_NEW };

but without success. I also tried using 0x1297 as product id, but it resulted in the same output. After rebuilding HeadsetControl I got:

christian@christian-PC:~$ headsetcontrol
Found SteelSeries Arctis (7/Pro)!

Requested/supported HID device not found or system error.

Can anyone help?

Activity

  1. Sapd commented on May 12, 2021

    @Sapd
    Owner

    Requested/supported HID device not found or system error.

    That unfortunately means, that you need an additional ID. idUsagePage and idUsage, like here:

    device_g930.idUsagePage = 0xff00;

    That means, that its also likely that the protocol will be different to some extent. So you probably have to create a new device file and use wireshark: https://github.com/Sapd/HeadsetControl/wiki/Development#adding-a-new-headset

    Edit: Its actually not idUsagePage, but idInterface.

  2. added 3 commits that reference this issue on Jun 12, 2021
    50d17b6
    5c745df
    4f4e1df
  3. added a commit that references this issue on Jun 12, 2021
    199c6e0
  4. added a commit that references this issue on May 31, 2024
    0753d40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions