Touchpad not working on new Fedora install

Ask Fedora
, , , , ,
1

Hello,

I am hoping someone here can help me figure out why my touchpad is not working.

I just switched over to Fedora Workstation from Windows 10 two days ago. Immediately on install my touchpad stopped working (system updates did not fix the issue).

I did have this issue once before on windows, but the problem stopped on its own and I never had an issue again until now. Knowing this its possible it could be a hardware issue. However, if I restart and go into the bios the touchpad works fine, so I am pretty sure this time the issue is with linux somehow.

It does respond to a tap, and if I hold down the right button for a second it also responds to a right click, but does not move the cursor at all.

What I’ve Tried

The first search results I found seemed to suggest the problem was with the input settings for the touchpad. I checked libinput and the touchpad does exist there, but I could not get the settings to change either with a config file or using gsettings. Another forum suggested these solutions don’t work for Wayland, and I could not find a way that does work (I no longer think this is the issue, but if there is a way to do this I would like to know for future reference).

In my search I found a post on this forum that suggested checking journalctl -b -g hid and look for errors related to i2c hid. I checked this and I do see messages regarding the i2c, but there was no conclusion to that suggestion in the thread so I’m not sure what to do with this information.

Screenshot From 2025-03-03 18-44-37
Screenshot From 2025-03-03 18-44-371372×482 97.1 KB

From what I’ve been reading the i2c hid is how human input devices can send input data. Does this mean it actually is a hardware issue? Or is it an issue with the drivers? Similar questions I’ve found online don’t have the exact messages I do, and the solutions involve messing with the kernel in ways I don’t fully understand.

I am new to linux, and my experience with the terminal is limited to a few comp sci courses. Everything I’ve tried so far has been pieced together from different reddit/forum discussions and limited knowledge. I apologize if this actually makes no sense.

I am using an ASUS Zenbook Q528EH, and I have installed default Fedora Workstation.

Thank you to anyone reading for your time.

2

What happens if your mouse is not also connected?

What happens if you launch under another desktop - you could try Sway or i3 as they are light-weight and easy to remove later.

I’m thinking is might be a Gnome setting problem, as I’m sure you are right that it is not a hardware issue as it works in BIOS.

3

The same thing happens when the mouse isn’t connected except there is one additional line when using journalctl -b -g hid (the very last line).

Screenshot From 2025-03-04 18-15-00
Screenshot From 2025-03-04 18-15-001481×544 99.7 KB

If its an issue with gnome settings then would my initial strategy of trying to change the input settings fix it? Or do you mean something different?

I did have to look up what sway and i3 are, but it looks like they are alternatives to a typical graphical DE. So I could use one of them to replace gnome, and have basically a bare-bones window manager/compositor? Which means I have to do a lot more customization, but it will likely not have weird settings that stop my touchpad from working?

Sorry for the probably obvious questions. I appreciate your time and help.

4

Try this command in Gnome first

gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled

If that does not work, I sugested Sway as a way to find out if it is a Fedora problem, or a Gnome problem. If it is a Gnome problem, we can certainly try and fix it if that is the desktop you like.

Sway is bare bones. It is only a guess that your touchpad might work under a WM.

If you can not post screenshots but rather use ‘preformatted text’ - the </> button in the tools above the editing window it is easier for many people to read.

5

To check touchpad will be good to try gnome on xorg but jf you install fedora 41 workstation it is install wayland by default.To allow x11 you will need to install package gnome-session-xsession will pull all needed packages Once you install it reboot or logout to gdm select your user name will apper :gear: in right bottom corner click on it It will appear gnome and gnome on xorg options select xorg and login like that,Check your touchpad. If is not working we will try old synaptics packages

6

I tried the command you suggested, but it did not work unfortunately. I also tried similar commands I found online using gsettings but they did not work either. I did find some documentation about input device configuration in gnome. [Input device configuration - Fedora Project Wiki]

Apparently you need to set any config options in gdm, because xorg files are overwritten in gnome. I don’t fully understand all the steps to do that however, so I haven’t tried this yet.

I think this might be an issue with fedora though. I installed sway and my touchpad still did not work.

I am not super set on gnome so I don’t mind using a different desktop or distro if I need to. I was mainly motivated to fix this issue because I wanted to understand what was happening.

I really appreciate your time and help. If you have any other ideas on how to fix this I am happy to hear them, but I will begin looking into another distro to try since I would like to have my touchpad back. Thank you again!

7

I was reading about how xorg might fix the issue instead of using Wayland, but a lot of people online discouraged using xorg because it is being phased out.

I think my issue might be with fedora, so I do not know if using xorg would help in this case? If you have any insight that would be appreciated.

I am also going to be looking at different distros though and see if that works better with my laptop. Thank you for your time and help.

8

The only other thing I can think of is that the required driver is not installed.

Run

cat /proc/bus/input/devices | grep -i touchpad
cat /proc/bus/input/devices | grep -i multitouch
cat /proc/bus/input/devices

And look for your device.

If your touchpad shows up, which I think it will because you posted a screenshot with a ‘hid-multitouch’ showing up, then we will try and find if the required driver is already installed or if we can find it.

You can post the output of cat /proc/bus/input/devices in ‘preformatted text’. You can find the icon in the toolbar above when you reply.

9

Yes the touchpad does show up. I did make sure it was recognized and checked for drivers when I first started looking into the issue. The three things that I have tried so far for drivers is

xserver-xorg-input-libinput
xserver-xorg-input-evdev
xserver-xorg-input-mouse

All three were already installed. I also tried xserver-xorg-input-synaptics which wasn’t installed, but didn’t help so I removed it (I read it can cause issue with libinput)

I attempted to look for drivers more specific to my device, but I am not exactly sure what I am looking for.

If it is not the drivers I think it might be an issue with hardware compatibility and the kernel? I installed Pop_Os! to see if another distro would fix the issue, but the touchpad still does not work.

I was also looking at my input devices and I may be way off base, but I think it might read my touchpad gestures/buttons as a separate device from the mouse part of touchpad. Notice in the results below that there are two devices with very similar names except one has touchpad at the end and one has mouse.

I: Bus=0018 Vendor=04f3 Product=30f1 Version=0100
N: Name="ELAN1206:00 04F3:30F1 Mouse"
P: Phys=i2c-ELAN1206:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1206:00/0018:04F3:30F1.0002/input/input39
U: Uniq=
H: Handlers=mouse2 event25 
B: PROP=0
B: EV=17
B: KEY=30000 0 0 0 0
B: REL=1943
B: MSC=10

I: Bus=0018 Vendor=04f3 Product=30f1 Version=0100
N: Name="ELAN1206:00 04F3:30F1 Touchpad"
P: Phys=i2c-ELAN1206:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1206:00/0018:04F3:30F1.0002/input/input40
U: Uniq=
H: Handlers=mouse3 event26 
B: PROP=5
B: EV=1b
B: KEY=e520 10000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

I used evtest to see what outputs they were giving and the touchpad gives feedback, but the mouse does not. I thought maybe I was being dumb and it was just my usb mouse, but that was not the case. This would explain why it will recognize if I click my touchpad, but will not move the cursor.

Unless this is normal I am thinking that this is my issue somehow. Would installing a different driver make the two work together? Or am I way off base about the whole thing?

10

To me it looks like the driver is part of the Kernel. I think you not being dumb, you are getting good outputs and will eventually get there :slight_smile:

It looks like there have been many problems with Elan touchpads over the years. From drivers - Elantech touchpad does not work (i2c-hid) - Ask Ubuntu there might be some potential solutions regarding i2c_hid.

There is also this about old PS2 Multiplexing linux - What does the 'i8042.nomux=1' kernel option do during booting of Ubuntu? - Unix & Linux Stack Exchange

I was wondering about what xinput does under Wayland. So it has been replaced with libinput. So you can

sudo libinput list-devices

Sorry for the slightly ranty suggestions :slight_smile:
Also, have you looked for a ‘touchpad enable’ function button on the top row of your laptop keyboard? You never know.

Here is an interesting command to test inputs

sudo libinput debug-events

And someone found a Kernel bug and got their touchpad working aby rolling back to Kernel 6.1 217701 – Kernel 6.4.4 breaks Elan Touchpad 1206

11

I have a Lenovo thinkpad t490, i have been having the same problem but it was also a problem with windows. First when i got the laptop the touchpad was fine, one day all of a sudden gone and not working, sometimes after system update it would come back but after reboot it’s like the driver is gone again. Now i install fedora 41 and i have the same problem but yesterday i get a system update for bug fixes and bam, touchpad works, later the same day i had to reboot and it’s gone again. Same thing today, i get system update this morning and there the touchpad comes back again, after reboot it’s gone again. What is going on?

12

Likely a different problem. This topic deals with an Elan touchpad. It is often helpful to have the output (posted as pre-formatted text) from running inxi -Fzxx in a terminal. Unless inxi shows an Elan touchpad, you should start a new topic and include the inxi output there.

Laptop touchpads are enabled before linux is loaded, so you may need a UEFI/BIOS update from Lenovo.

13

Hello,

Sorry for the delay in response. Life was busy, but I also had to take a break because I was getting a bit frustrated. But I’m back at it now.

It looks like we are finding the same posts about the issue lol. I was looking into the PS/2 Multiplexing post, which seems like it could be related to my issue though I am not sure how to boot linux with extra options so I haven’t tried that yet.

I have also checked the function button, but that wasn’t the problem either.

There are a few posts I’ve seen that say rolling back the kernel fixed their issue, but I also don’t fully know how to do that yet. I plan to try when I read more about how to do that without breaking something.

I think my issue definitely has to do with how my specific hardware is being read. I just don’t understand enough about the kernel and drivers yet to figure out whats going on. If rolling back the kernel would work, or if i2c_hid is the issue, or if my hardware just isn’t supported at all.

When I use libinput debug-events these are the results:

-event16  DEVICE_ADDED                ELAN1206:00 04F3:30F1 Mouse       seat0 default group7  cap:p left scroll-nat scroll-button
-event17  DEVICE_ADDED                ELAN1206:00 04F3:30F1 Touchpad    seat0 default group7  cap:pg  size 125x63mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on dwtp-on

-event17  GESTURE_HOLD_BEGIN          +0.040s   1
 event17  GESTURE_HOLD_END            +0.104s   1
 event17  POINTER_BUTTON              +0.208s   BTN_LEFT (272) pressed, seat count: 1
 event17  POINTER_BUTTON              +0.416s   BTN_LEFT (272) released, seat count: 0
 event17  GESTURE_HOLD_BEGIN          +0.456s   1
 event17  GESTURE_HOLD_END            +0.520s   1
 event17  GESTURE_HOLD_BEGIN          +0.664s   1
 event17  GESTURE_HOLD_END            +0.728s   1
 event17  GESTURE_HOLD_BEGIN          +0.872s   1
 event17  GESTURE_HOLD_END            +0.936s   1
 event17  GESTURE_HOLD_BEGIN          +2.536s   1
 event17  GESTURE_HOLD_END            +2.600s   1
 event17  GESTURE_HOLD_BEGIN          +2.744s   1
 event17  GESTURE_HOLD_END            +2.808s   1
 event17  GESTURE_HOLD_BEGIN          +2.953s   1
 event17  GESTURE_HOLD_END            +3.016s   1
 event17  GESTURE_HOLD_BEGIN          +3.160s   1
 event17  GESTURE_HOLD_END            +3.224s   1
 event17  GESTURE_HOLD_BEGIN          +3.368s   1
 event17  GESTURE_HOLD_END            +3.432s   1
 event17  GESTURE_HOLD_BEGIN          +3.576s   1
 event17  GESTURE_HOLD_END            +3.640s   1

I am not sure what a normal touchpad should output, but to me it looks like mine is only being read for gestures and button presses. I think the mouse/pointer part of my touchpad is being read as the event 16 mouse instead event 17. Unless gesture also includes the pointer part of the touchpad?

I am wondering if there is a way to remap? how that works. As in remove mouse event 16 and have that be attached to the touchpad event 17 instead?

I also used dmesg to see if that could tell me anything, and I think it definitely does I’m just still trying to read about what they all mean. There are quite a few errors mostly involving ACPI and the IRQ.

I was reading that the ACPI is used to monitor hardware status. I am not sure if that includes touchpads or just batteries and fans, but I thought it could be related. I was also reading that the IRQ is involved with handling device drivers, so those errors may be more correlated to my issue. I’ll copy the parts I think are most relevant below:

ACPI BIOS - Errors 
[    0.168450] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.APLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168455] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168457] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168459] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.AUPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168461] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168462] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168465] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS01._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168467] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168468] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168470] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS01._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168472] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168473] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168475] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS02._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168477] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168479] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168480] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS02._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168482] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168483] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168485] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS03._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168487] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168489] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168490] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS03._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168492] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168495] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168497] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS04._UPC], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168498] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168500] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
[    0.168501] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.TXHC.RHUB.SS04._PLD], AE_ALREADY_EXISTS (20240827/dswload2-326)
[    0.168503] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    0.168504] ACPI: Skipping parse of AML opcode: OpcodeName unavailable (0x0014)
DMAR Inconsistent 
[    0.534484] DMAR: Intel-IOMMU force enabled due to platform opt in
[    0.534492] DMAR: No ATSR found
[    0.534493] DMAR: No SATC found
[    0.534494] DMAR: IOMMU feature fl1gp_support inconsistent
[    0.534495] DMAR: IOMMU feature pgsel_inv inconsistent
[    0.534496] DMAR: IOMMU feature nwfs inconsistent
[    0.534497] DMAR: IOMMU feature pds inconsistent
[    0.534497] DMAR: IOMMU feature dit inconsistent
[    0.534498] DMAR: IOMMU feature eafs inconsistent
[    0.534499] DMAR: IOMMU feature prs inconsistent
[    0.534499] DMAR: IOMMU feature nest inconsistent
[    0.534500] DMAR: IOMMU feature mts inconsistent
[    0.534500] DMAR: IOMMU feature sc_support inconsistent
[    0.534501] DMAR: IOMMU feature dev_iotlb_support inconsistent
[    0.534502] DMAR: dmar2: Using Queued invalidation
[    0.534505] DMAR: dmar1: Using Queued invalidation
[    0.534507] DMAR: dmar0: Using Queued invalidation
[    0.534509] DMAR: dmar3: Using Queued invalidation
PS/2 Controller 
[    1.019183] i8042: PNP: PS/2 Controller [PNP030b:PS2K] at 0x60,0x64 irq 1
[    1.019184] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    1.020626] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.020672] mousedev: PS/2 mouse device common for all mice
[    1.020737] rtc_cmos rtc_cmos: RTC can wake from S4
[    1.021540] rtc_cmos rtc_cmos: registered as rtc0
[    1.021690] rtc_cmos rtc_cmos: setting system clock to 2025-03-15T17:09:11 UTC (1742058551)
[    1.021720] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram
[    1.024212] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
ELAN Devices/ PCI Can't Assign Bridge Window 
[    1.674647] input: ELAN1206:00 04F3:30F1 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1206:00/0018:04F3:30F1.0003/input/input10
[    1.674737] input: ELAN1206:00 04F3:30F1 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1206:00/0018:04F3:30F1.0003/input/input11
[    1.674818] hid-generic 0018:04F3:30F1.0003: input,hidraw2: I2C HID v1.00 Mouse [ELAN1206:00 04F3:30F1] on i2c-ELAN1206:00
[    1.695878] i2c_hid_acpi i2c-ELAN9009:00: i2c_hid_get_input: IRQ triggered but there's no data
[    1.707440] input: ELAN9009:00 04F3:2C26 as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input12
[    1.719239] input: ELAN9009:00 04F3:2C26 UNKNOWN as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input13
[    1.719269] input: ELAN9009:00 04F3:2C26 UNKNOWN as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input14
[    1.719297] input: ELAN9009:00 04F3:2C26 Stylus as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input15
[    1.719338] input: ELAN9009:00 04F3:2C26 UNKNOWN as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input17
[    1.719363] input: ELAN9009:00 04F3:2C26 UNKNOWN as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input18
[    1.719385] input: ELAN9009:00 04F3:2C26 UNKNOWN as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN9009:00/0018:04F3:2C26.0004/input/input19
[    1.728785] input: ELAN1206:00 04F3:30F1 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1206:00/0018:04F3:30F1.0003/input/input21
[    1.729017] input: ELAN1206:00 04F3:30F1 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1206:00/0018:04F3:30F1.0003/input/input22
[    1.729235] hid-multitouch 0018:04F3:30F1.0003: input,hidraw3: I2C HID v1.00 Mouse [ELAN1206:00 04F3:30F1] on i2c-ELAN1206:00
[    1.764451] hid-multitouch 0018:04F3:2C26.0004: input,hidraw2: I2C HID v1.00 Device [ELAN9009:00 04F3:2C26] on i2c-ELAN9009:00
[    1.769315] pci 10000:e0:1d.0: bridge window [mem 0x6a000000-0x6a0fffff]: assigned
[    1.769323] pci 10000:e0:1d.2: bridge window [mem 0x6a100000-0x6a1fffff]: assigned
[    1.769326] pci 10000:e0:1d.0: bridge window [io  size 0x1000]: can't assign; no space
[    1.769328] pci 10000:e0:1d.0: bridge window [io  size 0x1000]: failed to assign
[    1.769330] pci 10000:e0:1d.2: bridge window [io  size 0x1000]: can't assign; no space
[    1.769332] pci 10000:e0:1d.2: bridge window [io  size 0x1000]: failed to assign
[    1.769336] pci 10000:e1:00.0: BAR 0 [mem 0x6a000000-0x6a003fff 64bit]: assigned
[    1.769354] pci 10000:e0:1d.0: PCI bridge to [bus e1]
[    1.769361] pci 10000:e0:1d.0:   bridge window [mem 0x6a000000-0x6a0fffff]
[    1.769373] pci 10000:e2:00.0: BAR 0 [mem 0x6a100000-0x6a103fff 64bit]: assigned
[    1.769387] pci 10000:e0:1d.2: PCI bridge to [bus e2]
[    1.769392] pci 10000:e0:1d.2:   bridge window [mem 0x6a100000-0x6a1fffff]
[    1.769421] pci 10000:e1:00.0: VMD: Default LTR value set by driver
[    1.769478] pci 10000:e2:00.0: VMD: Default LTR value set by driver
[    1.770420] pcieport 10000:e0:1d.0: can't derive routing for PCI INT A
[    1.770424] pcieport 10000:e0:1d.0: PCI INT A: no GSI
[    1.770553] pcieport 10000:e0:1d.0: PME: Signaling with IRQ 164
[    1.778159] pcieport 10000:e0:1d.2: can't derive routing for PCI INT C
[    1.778163] pcieport 10000:e0:1d.2: PCI INT C: no GSI
[    1.780443] pcieport 10000:e0:1d.2: PME: Signaling with IRQ 165
[    1.780630] vmd 0000:00:0e.0: Bound to PCI domain 10000
[    1.786122] usb 3-5: New USB device found, idVendor=13d3, idProduct=56eb, bcdDevice=19.64
[    1.786128] usb 3-5: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    1.786130] usb 3-5: Product: USB2.0 HD UVC WebCam
[    1.786132] usb 3-5: Manufacturer: Azurewave
[    1.786134] usb 3-5: SerialNumber: 0x0001
[    1.811344] nvme nvme0: pci function 10000:e1:00.0
[    1.811364] pcieport 10000:e0:1d.0: can't derive routing for PCI INT A
[    1.811367] nvme 10000:e1:00.0: PCI INT A: not connected
[    1.811475] nvme nvme1: pci function 10000:e2:00.0
[    1.811493] pcieport 10000:e0:1d.2: can't derive routing for PCI INT A
[    1.811496] nvme 10000:e2:00.0: PCI INT A: no GSI
Nobody Cares About the IRQ :( 
[    4.377215] systemd[1]: Detected architecture x86-64.
[    4.450411] irq 28: nobody cared (try booting with the "irqpoll" option)
[    4.450419] CPU: 3 UID: 0 PID: 0 Comm: swapper/3 Not tainted 6.13.6-200.fc41.x86_64 #1
[    4.450422] Hardware name: ASUSTeK COMPUTER INC. ZenBook UX564EH_Q528EH/UX564EH, BIOS UX564EH.313 04/21/2022
[    4.450423] Call Trace:
[    4.450425]  <IRQ>
[    4.450427]  dump_stack_lvl+0x5d/0x80
[    4.450430]  __report_bad_irq+0x35/0xa7
[    4.450432]  note_interrupt.cold+0xa/0x67
[    4.450433]  handle_irq_event+0x6f/0x90
[    4.450435]  handle_fasteoi_irq+0x78/0x200
[    4.450437]  __common_interrupt+0x49/0xd0
[    4.450439]  common_interrupt+0x80/0xa0
[    4.450442]  </IRQ>
[    4.450442]  <TASK>
[    4.450442]  asm_common_interrupt+0x26/0x40
[    4.450445] RIP: 0010:cpuidle_enter_state+0xd3/0x690
[    4.450447] Code: 00 00 e8 c0 53 00 ff e8 4b ee ff ff 49 89 c6 0f 1f 44 00 00 31 ff e8 7c a0 fe fe 45 84 ff 0f 85 13 02 00 00 fb 0f 1f 44 00 00 <45> 85 ed 0f 88 e3 01 00 00 4d 63 e5 49 83 fc 0a 0f 83 be 04 00 00
[    4.450449] RSP: 0018:ffffbc69c019be58 EFLAGS: 00000246
[    4.450450] RAX: ffff970d87580000 RBX: ffff970d875c3a50 RCX: 0000000000000000
[    4.450451] RDX: 000000010943ae9c RSI: 000000002da97f6a RDI: 0000000000000000
[    4.450452] RBP: ffffffff9db05260 R08: 00000000001da2a4 R09: 00000000000b94d8
[    4.450452] R10: 0000000000000004 R11: ffff970d875a17c0 R12: 0000000000000001
[    4.450453] R13: 0000000000000001 R14: 000000010943ae9c R15: 0000000000000000
[    4.450454]  ? cpuidle_enter_state+0xc4/0x690
[    4.450456]  cpuidle_enter+0x2d/0x40
[    4.450459]  cpuidle_idle_call+0xf3/0x160
[    4.450461]  do_idle+0x78/0xd0
[    4.450463]  cpu_startup_entry+0x29/0x30
[    4.450464]  start_secondary+0x12d/0x160
[    4.450467]  common_startup_64+0x13e/0x141
[    4.450469]  </TASK>
[    4.450469] handlers:
[    4.450472] [<0000000060a7f050>] i2c_dw_isr
[    4.450474] Disabling IRQ #28
ACPI BIOS - Errors Again 
[    5.032217] ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20240827/psargs-332)
[    5.032227] ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.032247] ACPI Warning: \_SB.IETM._TRT: Return Package has no elements (empty) (20240827/nsprepkg-94)
[    5.037739] input: Intel HID events as /devices/platform/INT33D5:00/input/input25
[    5.038967] Consider using thermal netlink events interface
[    5.056503] intel_pmc_core INT33A1:00:  initialized
[    5.059872] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20240827/psargs-332)
[    5.059881] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.059909] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20240827/psargs-332)
[    5.059913] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.059941] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20240827/psargs-332)
[    5.059947] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.060414] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20240827/psargs-332)
[    5.060423] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.071637] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20240827/psargs-332)
[    5.071645] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.071671] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20240827/psargs-332)
[    5.071676] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.071703] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20240827/psargs-332)
[    5.071708] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.071734] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20240827/psargs-332)
[    5.071738] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.086272] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT], AE_NOT_FOUND (20240827/psargs-332)
[    5.086281] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._CRT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.086307] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT], AE_NOT_FOUND (20240827/psargs-332)
[    5.086311] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._HOT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.086337] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT], AE_NOT_FOUND (20240827/psargs-332)
[    5.086341] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._PSV due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.095775] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT], AE_NOT_FOUND (20240827/psargs-332)
[    5.095783] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._CRT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.095809] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT], AE_NOT_FOUND (20240827/psargs-332)
[    5.095812] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._HOT due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.095835] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT], AE_NOT_FOUND (20240827/psargs-332)
[    5.095837] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._PSV due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
[    5.095858] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT], AE_NOT_FOUND (20240827/psargs-332)
[    5.095860] ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._AC0 due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Serial Bus Multi Instantiate - Errors 
[    5.116228] Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found
[    5.116235] Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at index 1

Sorry for the long post, or if I am wrong about these errors being relevant to my current issue.

I also wanted to mention that I went back to fedora after Pop_Os, but I installed Fedora KDE this time since I am more familiar with it (I use it on my PC). Apologies if the distro hopping makes this more difficult.

Thank you for your time, and insight. I really appreciate the help!

14

Hi Dani,

Welcome to Fedora :slight_smile:

Try this

Need to do as root or via sudo with vi or nano

  1. in /etc/default/grub
    look for a line that starts with the following
    GRUB_CMDLINE_LINUX=“{some_stuff}”
  2. add psmouse.elantech_smbus=0 as the very first parameter
    GRUB_CMDLINE_LINUX=“psmouse.elantech_smbus=0 …{rest of the existing stuff}”
  3. save the file
  4. then the following command
    grub2-mkconfig
  5. reboot
15

Please, when giving a command such as this provide the full command as best as possible.
In this case it would be sudo grub2-mkconfig -o /boot/grub2/grub.cfg

The same effect can be done with a single command
sudo grubby --update-kernel=ALL --args="psmouse.elantech_smbus=0"
and avoid both editing the file and running the grub2-mkconfig command

1 Like
16

Hello

I typed the following into the terminal:

sudoedit /etc/default/grub
*edited the line and saved*
sudo grub2-mkconfig -o /boot/grub2/grub.conf
reboot

But unfortunately this did not fix my issue. Thank you for the suggestion regardless!

17

Can you show ==> cat /etc/default/grub in terminal

It is wrong command sudo grub2-mkconfig -o /boot/grub2/grub.conf
Right ones are:
sudo grub2-mkconfig -o /etc/grub2.cfg for uefi system
sudo grub2-mkconfig -o /boot/grub2/grub.cfg for legacy boot system

18

sudo grubby --args=psmouse.elantech_smbus=0 --update-kernel=ALL easier way to add args to boot command line

19

The output for cat /etc/default/grub is below:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="psmouse.elantech_smbus=0 rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

Thank you! I did also try sudo grubby --update-kernel=ALL --args="psmouse.elantech_smbus=0" per Jeff V’s suggestion, but that also did not fix the issue.

20

You can see old kernel versions at Koji
If I remember people downgraded to 6.4 Kernel, which was only built up to F40. So it would be difficult to downgrade to that Kernel in F41.

It is probably better to move foward not backwards, so you could consider submitting a bug to https://bugzilla.redhat.com/ and get the issue fixed in future kernels.

Haha yes we have been reading the same forums trying to solve this issue. You’ve got all the diagnostic files and techniques to solve issues, shame this one is quite resistant.