Arctis Nova Elite support

[Awshuckz]

I have tried adding the new Arctis Nova Elite to the installer, but the service just exists when started saying the service is not available. I added the device in the /udev/91-steelseries-arctis.rules file and added a new file in the /arctis_manager/devices/ folder, copying the pro file and changing to match the nova elite, but still no luck. Not sure what other steps I am missing. Below is the udevadm output:

looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:74:00.4/usb7/7-2/7-2:1.4/0003:1038:2270.000>
KERNELS=="input2"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{capabilities/abs}=="0"
ATTRS{capabilities/ev}=="13"
ATTRS{capabilities/ff}=="0"
ATTRS{capabilities/key}=="7800000000 c000000000000 0"
ATTRS{capabilities/led}=="0"
ATTRS{capabilities/msc}=="10"
ATTRS{capabilities/rel}=="0"
ATTRS{capabilities/snd}=="0"
ATTRS{capabilities/sw}=="0"
ATTRS{id/bustype}=="0003"
ATTRS{id/product}=="2270"
ATTRS{id/vendor}=="1038"
ATTRS{id/version}=="0100"
ATTRS{inhibited}=="0"
ATTRS{name}=="SteelSeries Arctis Nova Elite"
ATTRS{phys}=="usb-0000:74:00.4-2/input4"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{properties}=="0"
ATTRS{uniq}==""

looking at parent device '/devices/pci0000:00/0000:00:08.1/0000:74:00.4/usb7/7-2':
KERNELS=="7-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{authorized}=="1"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{bConfigurationValue}=="1"
ATTRS{bDeviceClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{bMaxPower}=="500mA"
ATTRS{bNumConfigurations}=="1"
ATTRS{bNumInterfaces}==" 5"
ATTRS{bcdDevice}=="0125"
ATTRS{bmAttributes}=="80"
ATTRS{busnum}=="7"
ATTRS{configuration}==""
ATTRS{devnum}=="3"
ATTRS{devpath}=="2"
ATTRS{idProduct}=="2270"
ATTRS{idVendor}=="1038"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="SteelSeries"
ATTRS{maxchild}=="0"
ATTRS{physical_location/dock}=="no"
ATTRS{physical_location/horizontal_position}=="left"
ATTRS{physical_location/lid}=="no"
ATTRS{physical_location/panel}=="back"
ATTRS{physical_location/vertical_position}=="center"
ATTRS{power/active_duration}=="2222172"
ATTRS{power/autosuspend}=="2"
ATTRS{power/autosuspend_delay_ms}=="2000"
ATTRS{power/connected_duration}=="2222172"
ATTRS{power/control}=="on"
ATTRS{power/level}=="on"
ATTRS{power/persist}=="1"
ATTRS{power/runtime_active_time}=="2221928"
ATTRS{power/runtime_status}=="active"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{product}=="Arctis Nova Elite"
ATTRS{quirks}=="0x0"
ATTRS{removable}=="removable"
ATTRS{remove}=="(not readable)"
ATTRS{rx_lanes}=="1"
ATTRS{speed}=="12"
ATTRS{tx_lanes}=="1"
ATTRS{urbnum}=="9535"
ATTRS{version}==" 2.00"

When trying to start the service this is what the journalctl output gives:
journalctl --user -b -f -u arctis-manager
Dec 19 11:40:23 user-x870iaorusproice systemd[60221]: arctis-manager.service: Scheduled restart job, restartcounter is at 4.
Dec 19 11:40:23 user-x870iaorusproice systemd[60221]: Started Arctis Manager.
Dec 19 11:40:23 user-x870iaorusproice (-manager)[295986]: arctis-manager.service: Unable to locate executable 'arctis-manager': No such file or directory
Dec 19 11:40:23 user-x870iaorusproice (-manager)[295986]: arctis-manager.service: Failed at step EXEC spawning arctis-manager: No such file or directory
Dec 19 11:40:23 user-x870iaorusproice systemd[60221]: arctis-manager.service: Main process exited, code=exited, status=203/EXEC
Dec 19 11:40:23 user-x870iaorusproice systemd[60221]: arctis-manager.service: Failed with result 'exit-code'.
Dec 19 11:40:25 user-x870iaorusproice systemd[60221]: arctis-manager.service: Scheduled restart job, restartcounter is at 5.
Dec 19 11:40:25 user-x870iaorusproice systemd[60221]: arctis-manager.service: Start request repeated too quickly.
Dec 19 11:40:25 user-x870iaorusproice systemd[60221]: arctis-manager.service: Failed with result 'exit-code'.
Dec 19 11:40:25 user-x870iaorusproice systemd[60221]: Failed to start Arctis Manager.

[elegos]

Hello @Awshuckz ,

I see a couple of problems here:

• Unfortunately adding the udev rule is not enough to allow the support for a specific device, as they don't share a common communication framework (they're essentially all different hardwares)
• If you installed the software via the package manager, it seems that somehow it didn't install the arctis-manager executable

May you please tell me which OS and version, and how you installed the software?

Besides that, you'll need to reverse engineer the device's USB messages. You can first try using the USB analyzer and, if it doesn't work, go manual with Wireshark.

• https://github.com/elegos/Linux-Arctis-Manager/blob/main/docs/USB_ANALYZER.md
• https://github.com/elegos/Linux-Arctis-Manager/blob/main/docs/WIRESHARK.md

[Awshuckz]

Tried both installing with the code from the github and from the aur for arch (https://aur.archlinux.org/packages/linux-arctis-manager). Garuda Arch linux using the 6.18.2-arch2-1-znver5 kernel.

Will try the usb analyzer later to see what shows up.

[elegos]

Hello @Awshuckz

have you tried using Wireshark to sniff USB traffic? I wanted to let you know that I released a new (beta untill someone will acknowledge it's working on some other computer but mine, too xD) arctis manager 2.0. This version of the manager allows you to support your own device by reverse engineering and trying it out in seconds by editing a configuration file, instead of messing around with Python code. This should help with the testings.