Bug 1811424 - Keyboard diNovo Edge Y-RAY81 with kernel 5.5.7
Summary: Keyboard diNovo Edge Y-RAY81 with kernel 5.5.7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 32
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1811421 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-08 14:58 UTC by mrblack
Modified: 2020-12-14 05:51 UTC (History)
20 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-12-14 05:51:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg with old kernel (75.15 KB, text/plain)
2020-10-22 20:21 UTC, mrblack
no flags Details
libinput (13.14 KB, text/plain)
2020-10-22 20:23 UTC, mrblack
no flags Details
dmesg with last kernel (82.27 KB, text/plain)
2020-11-01 18:39 UTC, mrblack
no flags Details
libinput with last kernel (8.00 KB, text/plain)
2020-11-01 18:40 UTC, mrblack
no flags Details

Description mrblack 2020-03-08 14:58:17 UTC
Description of problem:

With a 5.1.19-300.fc30.x86_64 kernel no problem but with a 5.5.7 kernel only the keyboard works more the mouse.

Version-Release number of selected component (if applicable):


How reproducible:
Use diNovo Edge with kernel 5.1.19-300 it's fully operational
use diNovo Edge with kernel 5.5.7 the mouse pad not working.

Comment 1 Kevin Fenzi 2020-03-08 17:16:13 UTC
*** Bug 1811421 has been marked as a duplicate of this bug. ***

Comment 2 mrblack 2020-10-06 15:30:07 UTC
can you deal with this problem quickly! thank you.
The ticket is open since the month of March and it is penalizing, I do not understand if it worked in an interior version that we cannot quickly correct this problem.
Because if the problem is not corrected I will have to change the release for an ubuntu or another release with which I have no keyboard mouse problem.

Comment 3 Hans de Goede 2020-10-06 17:09:22 UTC
(In reply to mrblack from comment #2)
> can you deal with this problem quickly! thank you.
> The ticket is open since the month of March and it is penalizing, I do not
> understand if it worked in an interior version that we cannot quickly
> correct this problem.
> Because if the problem is not corrected I will have to change the release
> for an ubuntu or another release with which I have no keyboard mouse problem.

Does this still happen with the 5.8.x kernels which are currently in the fedora-updates repository ?
(do "sudo dnf update 'kernel*'" and then reboot to install the latest kernel)

Comment 4 mrblack 2020-10-12 16:42:16 UTC
(In reply to Hans de Goede from comment #3)
> (In reply to mrblack from comment #2)
> > can you deal with this problem quickly! thank you.
> > The ticket is open since the month of March and it is penalizing, I do not
> > understand if it worked in an interior version that we cannot quickly
> > correct this problem.
> > Because if the problem is not corrected I will have to change the release
> > for an ubuntu or another release with which I have no keyboard mouse problem.
> 
> Does this still happen with the 5.8.x kernels which are currently in the
> fedora-updates repository ?
> (do "sudo dnf update 'kernel*'" and then reboot to install the latest kernel)

Yes, I have the 5.8.12 kernel and I still have the same problem.

Comment 5 Hans de Goede 2020-10-13 09:17:21 UTC
(In reply to mrblack from comment #4)
> Yes, I have the 5.8.12 kernel and I still have the same problem.

Ok, thank you for testing, I've asked a colleague who knows a lot more about this then I do to take a look.

Comment 6 Benjamin Tissoires 2020-10-13 13:22:36 UTC
Can we get some logs on the working and non-working kernel (if still possible)?

We need at least:
- the dmesg of the kernels, 
- the output of `sudo libinput debug-events` (package libinput-utils), 
- and the output of hid-recorder (from https://gitlab.freedesktop.org/libevdev/hid-tools) for all the Logitech nodes attached to the diNovo, and while using the touchpad.

Comment 7 mrblack 2020-10-17 23:04:32 UTC
Malereusement Je n'ai plus le noyeau fonctionnelFollowing the update I unfortunately no longer have the functional kernel 5.1.19-300.fc30.x86_64

Comment 8 Hans de Goede 2020-10-18 09:11:04 UTC
(In reply to mrblack from comment #7)
> Malereusement Je n'ai plus le noyeau fonctionnelFollowing the update I
> unfortunately no longer have the functional kernel 5.1.19-300.fc30.x86_64

You can find the old 5.1.19-300.fc30 build here:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1319048

See here for some generic instructions for installing a kernel directly from koji:
https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Comment 9 mrblack 2020-10-22 20:21:34 UTC
Created attachment 1723606 [details]
dmesg with old kernel

Comment 10 mrblack 2020-10-22 20:23:48 UTC
Created attachment 1723608 [details]
libinput

Comment 11 mrblack 2020-10-22 20:28:03 UTC
(In reply to Hans de Goede from comment #8)
> (In reply to mrblack from comment #7)
> > Malereusement Je n'ai plus le noyeau fonctionnelFollowing the update I
> > unfortunately no longer have the functional kernel 5.1.19-300.fc30.x86_64
> 
> You can find the old 5.1.19-300.fc30 build here:
> 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1319048
> 
> See here for some generic instructions for installing a kernel directly from
> koji:
> https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Ok i have intalled the kerned, I have attached the dmesg and libinput.
But I failed to make the hid-recorder

Comment 12 Benjamin Tissoires 2020-10-23 10:29:12 UTC
> Ok i have intalled the kerned, I have attached the dmesg and libinput.

Can we also get the dmesg from the new (non working kernel)?

> But I failed to make the hid-recorder

Well, I was about to give some instructions, but after further debugging, we will likely not get anything useful from hid-recorder.


In terms of debugging, so far:
- the keyboard and the mouse are on 2 distinct HID nodes (C70E and C70A)
- both are handled properly with hid-generic on the working kernel.
- I do have a Logitech DiNovo mini here with the receiver having slightly different PIDs (C71E and C71F)
- On my DiNovo mini, the mouse part is handled by hid-logitech, and works fine with 5.8.4
- C70E+C70A are currently used in the hid-logitech-dj.c module, with the reference of "Logitech MX5000 HID++ / bluetooth receiver mouse intf"
- this device was added by Hans in f2113c3020ef ("HID: logitech-dj: add support for Logitech Bluetooth Mini-Receiver")

Hans, if you still have the MX5000, it might be easier for you to debug this one.
Again, for Hans: in terms of logs, I wanted to write the same debugging BPF tool I wrote for I2C but for USB. I think it might be handy here, unless you have a quick way of retrieving the data you'll need.

Comment 13 Hans de Goede 2020-10-23 20:36:08 UTC
(In reply to Benjamin Tissoires from comment #12)
> Hans, if you still have the MX5000, it might be easier for you to debug this one.

Hmm, so this keyboard uses the same receiver as the MX5000. Interesting. Yes I still have the MX5000. I have done some asking around and it looks like I will also be able to get my hands on a Dinovo Edge Y-RAY81. It will take about a week before I will get access to that.

So I should be able to debug this further in about a week from now and then I will hopefully be able to solve this reasonable quick.

Comment 14 mrblack 2020-11-01 18:39:15 UTC
Created attachment 1725582 [details]
dmesg with last kernel

Comment 15 mrblack 2020-11-01 18:40:04 UTC
Created attachment 1725583 [details]
libinput with last kernel

Comment 16 mrblack 2020-11-01 18:42:25 UTC
(In reply to Benjamin Tissoires from comment #12)
> > Ok i have intalled the kerned, I have attached the dmesg and libinput.
> 
> Can we also get the dmesg from the new (non working kernel)?
> 
> > But I failed to make the hid-recorder
> 
> Well, I was about to give some instructions, but after further debugging, we
> will likely not get anything useful from hid-recorder.
> 
> 
> In terms of debugging, so far:
> - the keyboard and the mouse are on 2 distinct HID nodes (C70E and C70A)
> - both are handled properly with hid-generic on the working kernel.
> - I do have a Logitech DiNovo mini here with the receiver having slightly
> different PIDs (C71E and C71F)
> - On my DiNovo mini, the mouse part is handled by hid-logitech, and works
> fine with 5.8.4
> - C70E+C70A are currently used in the hid-logitech-dj.c module, with the
> reference of "Logitech MX5000 HID++ / bluetooth receiver mouse intf"
> - this device was added by Hans in f2113c3020ef ("HID: logitech-dj: add
> support for Logitech Bluetooth Mini-Receiver")
> 
> Hans, if you still have the MX5000, it might be easier for you to debug this
> one.
> Again, for Hans: in terms of logs, I wanted to write the same debugging BPF
> tool I wrote for I2C but for USB. I think it might be handy here, unless you
> have a quick way of retrieving the data you'll need.

I have attached the dmesg and libinput with the last kernel

Comment 17 Hans de Goede 2020-11-02 23:03:23 UTC
I have managed to reproduce and fix the problem.

I have posted a patch fixing this upstream. I've also done a test-build of the Fedora 33 kernel with the patch added:

https://koji.fedoraproject.org/koji/taskinfo?taskID=54797631

You can find generic instructions for directly installing a kernel from koji (the Fedora buildsystem) here:

https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Please give the test kernel-build a try and let us know if this fixes things for you.

Once the patches have been accepted upstream I will add them as downstream patches to the Fedora kernels for now.

Comment 18 Ben Cotton 2020-11-03 16:49:03 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 mrblack 2020-11-11 18:04:50 UTC
(In reply to Hans de Goede from comment #17)
> I have managed to reproduce and fix the problem.
> 
> I have posted a patch fixing this upstream. I've also done a test-build of
> the Fedora 33 kernel with the patch added:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=54797631
> 
> You can find generic instructions for directly installing a kernel from koji
> (the Fedora buildsystem) here:
> 
> https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt
> 
> Please give the test kernel-build a try and let us know if this fixes things
> for you.
> 
> Once the patches have been accepted upstream I will add them as downstream
> patches to the Fedora kernels for now.

Hello,
The 2nd link you sent is not functional.

https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Please give me a link for the test procedure

Comment 20 Hans de Goede 2020-11-12 10:04:59 UTC
The:

https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Link works for me, perhaps the host was down temporarily, can you try again?

Comment 21 mrblack 2020-12-14 05:51:20 UTC
ok i confirm that the problem is solved.
I updated to Fedora32 version and in kernel 5.9.13-100.fc32.x86_64 no more problem.
Thank you for your work and your help.
Best regards


Note You need to log in before you can comment on or make changes to this bug.