1. Please describe the problem:on ASUS R55 serie No Pad, No Keyboard, we have to return to old kernel 5.7 2. What is the Version-Release number of the kernel:5.8.4-200 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes, i return to 5.7 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Install kernel 5.8 and start 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: No 6. Are you running any modules that not shipped with directly Fedora's kernel?: no pad, no keyboard, i put an USB mouse and Usb Keyboard 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
The 5.8.x kernels accidentally have the XHCI driver built as a module rather then being built into the kernel. This may be related to your issue. Here is a test kernel-build which fixes this: https://koji.fedoraproject.org/koji/taskinfo?taskID=50680004 Can you please give this a try? See here for some generic instructions for testing kernels directly from koji: https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt If that does not help, please attach dmesg info as requested in the template for kernel bugs.
Created attachment 1713751 [details] bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ] [ 98.046896] nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ IBUS ]
Created attachment 1713853 [details] Dmesg to see default on 1190, 1184, 1171 etc... no pad, no keyboard on this device.
Still not working with 5.8.8-200.fc32.x86_64
Ugh, I'm afraid that this is likely my fault. I added support for SW_TABLET_MODE to the asus-wmi kernel driver and the patch for that has landed in the 5.8 kernel. Can you please run: sudo dnf install evemu acpica-tools evemu-record And in evemu-record select the "Asus WMI hotkeys" device? I expect that with the 5.8 kernel, you will see that that input device has a SW_TABLET_MODE switch and that that switch reports 1. This causes libinput to think that the device is a 2-in-1 with 360 degree (yoga style) hinges which has been folded into tablet-mode and then it suppresses kbds and touchpad events for the internal kbd and touchpad. If there indeed is a SW_TABLET_MODE switch being reported and it always reports 1, please run: sudo acpidump -o acpidump-asus-<your-model-number> And then attach the acpidump-asus-<your-model-number> file here?
Created attachment 1715032 [details] acpidump and evemu-record with asus R558U. there is not SW_TABLET_MODE. He seeing WMI HOTKEYS (but nothing change, the pad and keyboard still not working
excuse SW_TABLET_MODE state is 1, but nothing happen about keyboard and pad....
The acpidump command generates the file named by the "-o <filename>" option, please attach that file here for all Asus models you have access to. Note I'm working on a fix for this.
Also please provide the output of the following command run as a regular user: grep . /sys/class/dmi/id/* 2> /dev/null
I've started a kernel test-build with a patch added which fix this: https://koji.fedoraproject.org/koji/taskinfo?taskID=51598665 ATM this is still building (this takes a couple of hours). Once the build is finished please give this kernel a try. As soon as I've confirmation that the patch indeed fixes things I will submit it for inclusion into the Fedora kernels (as a downstream patch for now). See here for some generic instructions on how to test a kernel directly from koji (our buildsystem): https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt
This bug is currently being tracked in more then one bugzilla. Most of the initial debugging has been done in bug 1876997, so I'm marking this one as a duplicate of that bug. Please add any new comments / test findings there. *** This bug has been marked as a duplicate of bug 1876997 ***