It is still unsolved i was just thanking for efforts you people make for us 
1 Like
This is the device my errors I posted refer too.
i am seriously not able to understand a thing here could you please make it more noob friendly
You gave us information about your system, the last two responses I gave show that your system not recognizes this device (check the code blocks).
The link to the Arch forum shows a similar situation with a Lenovo laptop also not recognizing the trackpad. While black list a kernel module, the system is checking and finding a other driver. This way the trackpad got recognized.
Now we do look for specific error messages and try to find more information in the internet. The best way to check for errors is the boot process to see what is going wrong. The command to check errors and other messages is journalctl.
journalctl --no-tail --no-hostname -S "today" -p err Please run the command and give us the information from the output.
It can be very long so to begin we need just from the last boot. There are sections with the string
-- Boot f9b8effbfa9f4c419e392d6dfc4d9034 --
give us this information from the string to the end (your number looks different but starts with --Boot).
Did you understand now what I try to tell you? To check the startup log with jorunalctl?
yes i got this error
-- Boot 1495f9f44ae54f8db73f27b1b1265c4d --
Jan 14 18:36:56 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.I2C0._INI], AE_ALREADY_EXISTS (20240827/dswload2-326)
Jan 14 18:36:56 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Jan 14 18:36:56 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.I2C2._INI], AE_ALREADY_EXISTS (20240827/dswload2-326)
Jan 14 18:36:56 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
Jan 14 18:37:01 kernel: ov13858 i2c-OVTID858:01: probe with driver ov13858 failed with error -22
is this the thing you are asking for
1 Like
Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:15 id=9 [slave keyboard (3)]
∼ xwayland-pointer-gestures:15 id=8 [floating slave]
∼ xwayland-relative-pointer:15 id=7 [floating slave]
∼ xwayland-pointer:15 id=6 [floating slave]
i think this is my trackpad device
However, if you want serious help, I guess you need to contact the support of infinix now. To see if they will keep up with the new kernels.
You can test an old LTS kernel … to see if it works.
Copr LTS Kernels:
kwizart/kernel-longterm-6.6 Coprhttps://copr.fedorainfracloud.org/coprs/kwizart/kernel-longterm-6.1/
1 Like
i am going to try old kernal because once it worked in linux mint with kernal version 5…
big broooo not way it worked 
i am so happy thank you soo muchh big brother
used this kernal
thank you so much brother 
1 Like
Thank you all of you for your efforts, i will always remember all of you 
Now the audio is not working 
i am going to jump from 6th floor
Please make a new topic with the audio and deliver audio specific information.
I guess we learned a lot here how to debug the system 
Yes i am thanking my self that i picked fedora over trash windows 11, linux is fast more beautiful and it is helping me learn new things 
That appears to show that your system is using/trying-to-use the i801_smbus driver for that device, but it shows that a different driver – i2c_i801 – is identifying itself as being compatible with the device. As ilikelinux suggested earlier, if you blacklist the driver it is currently using, it should fallback to the other driver and that might have a chance of working.
Try the following command:
echo "blacklist i801_smbus" | sudo tee /etc/modprobe.d/touchpad.conf
Then reboot your system. If it doesn’t work, remove the /etc/modprobe.d/touchpad.conf file to undo the change.
1 Like
no it didn’t worked, but i am thinking that if trackpad can work in older kernal why can’t in the newer kernal
1 Like
Did you rerun lspci -k to confirm that it switched to using the other driver? It is possible that the config file I suggested didn’t “take” because it was loaded too late. I think that is unlikely, but it is always good to confirm things and double-check the logs to see if there might be another clue.
Other than that, I’m out of ideas. Sorry.
SMBus: Intel Corporation Jasper Lake SMBus (rev 01)
DeviceName: Onboard - Other
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
So it didn’t switch (the config file didn’t work for whatever reason). How about if you run sudo rmmod i801_smbus followed by sudo modprobe i2c_i801? If the other driver loads, but it still doesn’t work, you might experiment with unloading it and reloading it with some extra parameters:
$ modinfo -p i2c_i801
disable_features:Disable selected driver features:
0x01 disable SMBus PEC
0x02 disable the block buffer
0x08 disable the I2C block read functionality
0x10 don't use interrupts
0x20 disable SMBus Host Notify (uint)
You should be able to pass parameters when loading the module with modprobe. For example, sudo modprobe i2c_i801 disable_features=0x01.
sudo rmmod i801_smbus
[sudo] password for aadit:
rmmod: ERROR: Module i801_smbus is not currently loaded
you were right i801 is not loaded