@kaihengfeng, I've sent the code to kernel.org and it's under review.
In the meantime, I am keeping the code in my Github updated, so the
users can download a pre-packaged DKMS deb file from it (or compile
their own).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I confirm the module works like a charm on Arch Linux, kernel 4.17.
Thanks!
(Here are the instructions to compile it:
https://help.ubuntu.com/community/DKMS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
@kaihengfeng, I believe upstreaming the driver is the right thing to do,
but I need to learn more about how in-tree drivers are written and
submitted.
Yes, I will try my best to upstreaming it. I will contact you when/if
the driver is accepted. Thank you very much for your help.
--
You received
Will you upstream your driver? I can backport it to Ubuntu's kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing extended key
To manage no
Release 0.5 makes this device fully functional. You can download it
from: https://github.com/dmlambea/linux-cougar-500k-drv/releases
** Attachment added: "DKMS module package for v0.5"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511511/+attachment/5156241/+files/cougar-500k-dkms_0.5
** Description changed:
- USB keyboard Cougar K500 gaming keyboard has some additional extended
+ USB keyboard Cougar 500k Gaming Keyboard has some additional extended
keys, all of them making the keyboard stop responding if pressed under
linux. The device is recovered only by unplugging the U
I've uploaded the code to Github, so it can be better read there.
https://github.com/dmlambea/linux-cougar-500k-drv
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops w
@Alexander, @Taimur: thanks to your comments and efforts, I've managed
to make a very basic HID driver for this keyboard. I have tested it
against kernel 4.15.0-23-generic with success. Please remove
"hid_generic" before loading this module and plugging the keyboard in,
so that hid_generic doesn't
Well, that's something from quite a long time ago, I can't find anything
remains for this bug in my Linux source tree, so...
I guess I added some workaround for it, but it's not the right solution.
The correct way is to write a new HID driver for the device.
--
You received this bug notificatio
@Kai-Heng Feng: Could you please upload a patch, or the sources, or the config
file, or whatever change you have made to the kernel, so those with other
distributions (like me) can also test it?
I am on Arch Linux with kernel 4.12.8.
--
You received this bug notification because you are a membe
Please try kernel here:
http://people.canonical.com/~khfeng/lp1511511/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing extended key
To manage
Never mind, @Alexander. I managed to find out myself. As it may be
useful to others, I will explain how it's done. I created a small bash
script, e.g. cougar_keyboard.sh, with the following contents:
#!/bin/bash
sudo su -c 'echo -n "1-13:1.2" > /sys/bus/usb/drivers/usbhid/unbind'
sudo su -c 'echo
@Alexander: This is by far the best solution that I found so far. I
followed your steps, and managed to attach the whole device (the 3
interfaces) to the aziokbd driver. However, by doing so, the main keys
also do not work. How did you attach only the third interface to the
aziokbd driver, and kept
I can confirm that the same happens on Cougar 700k. Also tried on Fedora
25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing extended key
To m
As a basis, I used the sources from
https://bitbucket.org/Swoogan/aziokbd/overview.
Just correct values for the 'VENDOR_ID' and "PRODUCT ID' and other parameters,
as well as cut out a piece of code that handles data from the keyboard (the
method 'static void usb_kbd_irq (struct urb * urb)', line
@Alexander: I would very much appreciate if you could share the driver
you have created...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing exte
Partially I solved the problem with Cougar 500K.
The problem lies in the fact that this keyboard has three interfaces (in terms
of USB), for the first two (keyboard and mouse) the kernel attaches the input
driver (from dmesg):
0003:060B:500A.0001: input,hidraw0: USB HID v1.11 Keyboard [Cougar500
the same happen in cougar 500k :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing extended key
To manage notifications about this bug go to:
h
I've managed to collect two PCAPNG files, one captured using virtualized
Windows 7 and the second directly under Ubuntu 16.04LTS fully upgraded
up to date.
In both sessions, after initialization I pressed "a" key, then special key
"G6". The "a" key makes four packets to be recorded. The "G6" spec
The keyboard has been tested in Ubuntu 16.04LTS kernel 4.4.0-34 x86_64
with the same behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511511
Title:
USB keyboard stops working after pressing
The keyboard was bought a few months ago and the bug have always been
there. I've tried the keyboard both in upgraded systems and in fresh
installations to no avail.
Following your instructions, I have just tested it right now using the
mainline kernel (at the URL you provided) and the bug is stil
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 kernel[0
Dmesg log info shows the folling: "hid-generic 0003:060B:500A.000A:
usage index exceeded".
I attach the device rdesc file, obtained from: cat
/sys/kernel/debug/hid/0003:060B:500A.000A/rdesc
** Attachment added: "rdesc info obtained from cat
/sys/kernel/debug/hid/:060B:500A./rdesc"
23 matches
Mail list logo