Pulsar has a website that allows people to configure their gaming mice at https://bbb.pulsar.gg/cMouse/. But when I hit connect and connect my device nothing happens.
The website is similar to the Wootilty website by Wooting, but Wooting has instructions on how to create rules to allow the website to interact with Wooting keyboards for Linux users.
Pulsar does not have any such instructions.
Does anyone know a way to fix this without reaching out to Pulsar and waiting for instructions?
You probably have to set a website permission like “don’t block popups”.
No, that’s not it. I managed to get it working temporarily by watching
chrome://device-log and using sudo chmod a+rw /dev/hidraw to temporarily allow the events that (I’m assuming) the OS is blocking but I’m looking for a more permanent solution.
The wooting instructions tell people to put a config file in /etc/udev/rules.d/ that looks like this:
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“03eb”, ATTRS{idProduct}==“ff01”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
SUBSYSTEM==“usb”, ATTRS{idVendor}==“03eb”, ATTRS{idProduct}==“ff01”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“03eb”, ATTRS{idProduct}==“2402”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
I’m assuming the config file is restricting it to a certain device by a certain vendor but I’m a little out of my wheelhouse here and I’m net even sure how I would find the vendor id and product id of my new mouse to copy the rules.
Maybe check
udevadm info --attribute-walk --name=/dev/hidraw
Or maybe something like
udevadm monitor --udev --subsystem-match=hidraw --property
before connecting your device.
That might work but what I found out was that you can pull vendor and product IDs of plugged in devices from chrome://device-log (it lists them farther below). What I came up with was:
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“14096”, ATTRS{idProduct}==“21510”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
SUBSYSTEM==“usb”, ATTRS{idVendor}==“14096”, ATTRS{idProduct}==“21510”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
SUBSYSTEM==“hidraw”, ATTRS{idVendor}==“14096”, ATTRS{idProduct}==“29957”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
SUBSYSTEM==“usb”, ATTRS{idVendor}==“14096”, ATTRS{idProduct}==“29957”, MODE:=“0660”, GROUP=“input”, TAG+=“uaccess”
Which fixes a portion of the blocks I was getting in chrome://device-log. Now I only get Failed to open ‘/dev/hidraw1’: FILE_ERROR_ACCESS_DENIED.
Before I was getting failures hidraw6 and others. I’m not sure what else I need to add to the rules file as those are vendor and product IDs are the only ones I’m seeing listed for Pulsar products. There is a single unnamed USB device, which I guess could be part of the Plusar mouse but all of the other ones have the Pulsar name attacked to it.