Before sending the patch to upstream, can you try [1] again? Thanks!
[1] http://people.canonical.com/~khfeng/lp1740438-3/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740438
Title:
Kernel has tro
I tested the above kernel over 15 reboots and the mouse activated
successfully every time. Great work! You're a legend. Let me know if you
need any additional information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Please try this kernel:
http://people.canonical.com/~khfeng/lp1740438-2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740438
Title:
Kernel has troule recognizing Corsair Harpoon RGB mouse
To mana
kaihengfeng, it seems to happen a little less often with the linked
kernel, but I'm still experiencing the error. I have copied my dmesg
output below.
[0.00] random: get_random_bytes called from start_kernel+0x42/0x4e1
with crng_init=0
[0.00] Linux version 4.13.0-22-generic (root@
I'm not sure whether it may be relevant in this context, but there is
unofficial driver support for your mouse: https://github.com/mattanger
/ckb-nex. I don't know if the source is part of the Linux kernel; if
that is the case, just ignore/delete my comment.
--
You received this bug notification
There is a typo in my previous comment, the correct URL is:
https://github.com/mattanger/ckb-next/. Sorry for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740438
Title:
Kernel has troule rec
Please try this Linux kernel:
http://people.canonical.com/~khfeng/lp1740438/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740438
Title:
Kernel has troule recognizing Corsair Harpoon RGB mouse
To
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.15 kernel[
