Closed pedroadame closed 8 years ago
Read through #89 and provide me with the details I asked for in that issue.
Short answer, not yet. Long answer, if you help then probably soon.
Ok!
lsusb
outputs:
Bus 003 Device 006: ID 1532:011a Razer USA, Ltd
lsusb -d 1532:011a -vvv
outputs:
lsusb-verbose-output.txt
Razer Synapse allows:
Non pulsating/animated lightining. But I can't check Synapse currently on so i'll post an updated comment later.
My 2013 can do pulsating so I would assume the 2014 can but know knows. I think the chroma was the first animated one but the 2016 can do that now as well (though only in green).
Just looking at it. 0x011A is the same as my 2013, In theory you should be able to bind it to the current driver. Read the rest of #89 and move onto the binding and testing part as it might already be supported. On that page there is a link to the wiki explaining driver binding etc...
I'm trying to do the binding for a BW Ultimate 2014, and I don't see a mouse interface for it:
freso@din ~> ls -ld /sys/bus/hid/devices/*1532*
lrwxrwxrwx 1 root root 0 Jul 30 22:49 /sys/bus/hid/devices/0003:1532:011A.0003 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1532:011A.0003/
lrwxrwxrwx 1 root root 0 Jul 30 22:49 /sys/bus/hid/devices/0003:1532:011A.0004 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:1532:011A.0004/
freso@din ~> udevadm info -a /sys/bus/hid/devices/0003:1532:011A.0003|grep bInterfaceNumber
ATTRS{bInterfaceNumber}=="00"
freso@din ~> udevadm info -a /sys/bus/hid/devices/0003:1532:011A.0004|grep bInterfaceNumber
ATTRS{bInterfaceNumber}=="01"
It does show up in lsusb
though:
freso@din ~> sudo lsusb -v -d 1532:011a|grep bInterfaceProtocol
bInterfaceProtocol 1 Keyboard
bInterfaceProtocol 1 Keyboard
bInterfaceProtocol 2 Mouse
Any clues?
Dump of lsusb -vvv -d 1532:011a
(Arch Linux 64-bit, linux-lqx kernel with custom .config - I might well have disabled a needed option there.)
Unplug keyboard, then tail -f /var/log/dmesg
then plug in keyboard. You
should see some rubbish about usb plugged in etc... Put that in a pastebin
On 30 Jul 2016 22:13, "Frederik “Freso” S. Olesen" notifications@github.com wrote:
I'm trying to do the binding for a BW Ultimate 2014, and I don't see a mouse interface for it:
freso@din ~> ls -ld /sys/bus/hid/devices/1532 lrwxrwxrwx 1 root root 0 Jul 30 22:49 /sys/bus/hid/devices/0003:1532:011A.0003 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1532:011A.0003/ lrwxrwxrwx 1 root root 0 Jul 30 22:49 /sys/bus/hid/devices/0003:1532:011A.0004 -> ../../../devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.1/0003:1532:011A.0004/ freso@din ~> udevadm info -a /sys/bus/hid/devices/0003:1532:011A.0003|grep bInterfaceNumber ATTRS{bInterfaceNumber}=="00" freso@din ~> udevadm info -a /sys/bus/hid/devices/0003:1532:011A.0004|grep bInterfaceNumber ATTRS{bInterfaceNumber}=="01"
It does show up in lsusb though:
freso@din ~> sudo lsusb -v -d 1532:011a|grep bInterfaceProtocol bInterfaceProtocol 1 Keyboard bInterfaceProtocol 1 Keyboard bInterfaceProtocol 2 Mouse
Any clues?
Dump of lsusb -vvv -d 1532:011a https://github.com/pez2001/razer_chroma_drivers/files/392090/RazerBlackwidowUltimate2014-lsusb-dump.txt
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/pez2001/razer_chroma_drivers/issues/128#issuecomment-236390258, or mute the thread https://github.com/notifications/unsubscribe-auth/AB5PXY-CsdhBeXz3SOigvQunr3Z59c9Hks5qa75jgaJpZM4Ilm9u .
As it.