Support for Blackwidow V4 X #2130
Labels
Device Support
need pcap
USB traffic packet captures are useful - see wiki "Reverse Engineering USB Protocol"
Comments
z3ntu
added
the
need pcap
|
Have a look at https://github.com/openrazer/openrazer/blob/master/DEVELOPMENT.md , if you like to tinker I'm sure you can add support for the device yourself! |
|
Hello, I'm not sure if I've done something wrong in setting up my system but I've basically bootlegged this commit, as I assume the two keyboards being of the same family, same effects etc... (as I can tell only difference really is the lack of the knob the pro has). Here's the daemon logwhich seems to have more going wrong with the permission denied errors than dmesg where everything seems to be going about right (included at the bottom). I tried running as root (the solution to all permisison issues), but as was indicated when trying to run as root at all, that's not really supposed to be done, and just errored outright. It seems to me more likely than anything that I just have something (most likely the damon) setup wrong on my system, leading to the permission errors, but I could use a nudge in the right direction. Also if it helps I'm using virtualbox usb passthrough, which although I can't see why wouldn't work, you specified qumu in your development md, so it's a difference that could be notable I guess. Dmesg |
|
Permission denied might either be that the sysfs file doesn't get created by the driver (but the daemon wants to use it), or it's that our udev script didn't run properly. I'm assuming the first but you can run But probably best if you submit a PR if you have something working where you can e.g. control the RGB and then already the CI will tell you if some things are wrong. |
|
You were absolutely on the mark, I missed installing the udev rules. now I'm getting Dmesg "Device data transfer failed" messages when I try to make changes to the settings (both brightness and effect type). DmesgDaemon output (it's a long one)It's pretty resonable to assume that this is because I basically copied the device configuration from #2054. I need to go take some actual packet captures to figure their differences. At least it shows up in razergenie :) |
|
Sounds like you might need to add your device to a different switch branch inside https://github.com/openrazer/openrazer/blob/master/driver/razerkbd_driver.c#L261 , then at least the serial number call should work correctly. |
|
Hello, |
|
@dvdred Nobody added support for this device yet, so yes it's not supported yet. If you have some time to tinker around, please read #2130 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Device Info
Device Information
Presumably it's relatively similar to Blackwidow V4 75% (already has an issue open), and Blackwidow V4 Pro (already has a PR open), but I thought it should be opened nonetheless.
The text was updated successfully, but these errors were encountered: