View previous topic :: View next topic |
Author |
Message |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Thu Mar 03, 2022 7:03 pm Post subject: [SOLVED] I2C touchpad recognized as a PS2 Logitech mouse |
|
|
Hi everybody, I'm currently struggling with my new laptop to get the gentoo kernel to recognize the touchpad.
At present it is seen as a simple ps2 mouse, but booting ubuntu or manjaro I see that it's correctly recognized, so it must be some kernel module that I'm missing.
Here is my xinput
Code: | ⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ ImPS/2 Logitech Wheel Mouse id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ BisonCam,NB Pro: BisonCam,NB Pr id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] |
and here is ubuntu's xinput:
Code: | ⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ FTCS1000:01 2808:0101 Mouse id=12 [slave pointer (2)]
⎜ ↳ FTCS1000:01 2808:0101 Touchpad id=13 [slave pointer (2)]
⎜ ↳ ImPS/2 Logitech Wheel Mouse id=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ Sleep Button id=9 [slave keyboard (3)]
↳ BisonCam,NB Pro: BisonCam,NB Pr id=11 [slave keyboard (3)]
↳ Intel HID events id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] |
here is also what udevadm info tells me under ubuntu:
Code: | looking at device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-29/i2c-FTCS1000:01/0018:2808:0101.0005/input/input25/event10':
KERNEL=="event10"
SUBSYSTEM=="input"
DRIVER==""
ATTR{power/control}=="auto"
ATTR{power/runtime_active_time}=="0"
ATTR{power/runtime_status}=="unsupported"
ATTR{power/runtime_suspended_time}=="0"
looking at parent device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-29/i2c-FTCS1000:01/0018:2808:0101.0005/input/input25':
KERNELS=="input25"
SUBSYSTEMS=="input"
DRIVERS==""
ATTRS{capabilities/abs}=="2e0800000000003"
ATTRS{capabilities/ev}=="1b"
ATTRS{capabilities/ff}=="0"
ATTRS{capabilities/key}=="e520 10000 0 0 0 0"
ATTRS{capabilities/led}=="0"
ATTRS{capabilities/msc}=="20"
ATTRS{capabilities/rel}=="0"
ATTRS{capabilities/snd}=="0"
ATTRS{capabilities/sw}=="0"
ATTRS{id/bustype}=="0018"
ATTRS{id/product}=="0101"
ATTRS{id/vendor}=="2808"
ATTRS{id/version}=="0100"
ATTRS{inhibited}=="0"
ATTRS{name}=="FTCS1000:01 2808:0101 Touchpad"
ATTRS{phys}=="i2c-FTCS1000:01"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{properties}=="5"
ATTRS{uniq}==""
looking at parent device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-29/i2c-FTCS1000:01/0018:2808:0101.0005':
KERNELS=="0018:2808:0101.0005"
SUBSYSTEMS=="hid"
DRIVERS=="hid-multitouch"
ATTRS{country}=="00"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{quirks}=="334864"
looking at parent device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-29/i2c-FTCS1000:01':
KERNELS=="i2c-FTCS1000:01"
SUBSYSTEMS=="i2c"
DRIVERS=="i2c_hid_acpi"
ATTRS{name}=="FTCS1000:01"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
looking at parent device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-29':
KERNELS=="i2c-29"
SUBSYSTEMS=="i2c"
DRIVERS==""
ATTRS{delete_device}=="(write-only)"
ATTRS{name}=="Synopsys DesignWare I2C adapter"
ATTRS{new_device}=="(write-only)"
ATTRS{waiting_for_supplier}=="0"
looking at parent device '/devices/pci0000:00/0000:00:15.0/i2c_designware.0':
KERNELS=="i2c_designware.0"
SUBSYSTEMS=="platform"
DRIVERS=="i2c_designware"
ATTRS{driver_override}=="(null)"
ATTRS{power/autosuspend_delay_ms}=="1000"
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="44907"
ATTRS{power/runtime_status}=="suspended"
ATTRS{power/runtime_suspended_time}=="451640"
looking at parent device '/devices/pci0000:00/0000:00:15.0':
KERNELS=="0000:00:15.0"
SUBSYSTEMS=="pci"
DRIVERS=="intel-lpss"
ATTRS{ari_enabled}=="0"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c8000"
ATTRS{consistent_dma_mask_bits}=="64"
ATTRS{d3cold_allowed}=="1"
ATTRS{device}=="0x43e8"
ATTRS{dma_mask_bits}=="32"
ATTRS{driver_override}=="(null)"
ATTRS{enable}=="1"
ATTRS{irq}=="27"
ATTRS{local_cpulist}=="0-15"
ATTRS{local_cpus}=="ffff"
ATTRS{msi_bus}=="1"
ATTRS{numa_node}=="-1"
ATTRS{power/control}=="auto"
ATTRS{power/pm_qos_latency_tolerance_us}=="auto"
ATTRS{power/runtime_active_time}=="54275"
ATTRS{power/runtime_status}=="suspended"
ATTRS{power/runtime_suspended_time}=="451465"
ATTRS{power_state}=="D3hot"
ATTRS{remove}=="(write-only)"
ATTRS{rescan}=="(write-only)"
ATTRS{revision}=="0x11"
ATTRS{subsystem_device}=="0x8511"
ATTRS{subsystem_vendor}=="0x1558"
ATTRS{vendor}=="0x8086"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
ATTRS{power/control}=="auto"
ATTRS{power/runtime_active_time}=="0"
ATTRS{power/runtime_status}=="unsupported"
ATTRS{power/runtime_suspended_time}=="0"
ATTRS{waiting_for_supplier}=="0" |
I searched a bit and seen many people with similar problems, with I2C touchpads (is it me or the hardware is becoming more and more needlessly complicated with the years?).
I tried to enable all modules (either as modules or compiled in) related to Intel LPSS, hid_multitouch, and all references I could find around about designware stuff.
Also I tired as a last desperate attempt to compile all the modules in the kernel sections related to
Input device support
Character devices (you never know...)
I2C support
Pin controllers (I've read somewhere some reference to this)
Multifunction device drivers (whaterver)
HID support
X86 Platform Specific Device Drivers
I can't think of any other pertinent kernel section. I could try next also to compile as built in the very same sections (instead of modules, just in case some pertinent model is not autoloaded at boot), but I'm starting to get desperate.
I'm starting to think that the solution may be in some udev or other obscure configuration lying in ubuntu or manjaro distributions, but it's complicated to search for it due to the very confusing way in which modern distributions (thanks systemd) scatter around configuration files that once were clearly stored in a single folder with a clear name found in /etc (yest, this is starting to be a rant, I'll stop here )
The only thing I didn't is trying to boot directly with ubuntu kernel, this is because I have a complicated boot setup with a fully encrypted system that boots from a uefi stub kernel (no bootloader). Yer there's no rational reason for it, I'm a nerd and I know it... Still trying to boot a pre-built kernel is a bit complicated as now...
Do anyone have some info to share in order to debug this problem?
Thanks a lot for any help provided  _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne
Last edited by Cazzantonio on Sat Mar 05, 2022 2:59 pm; edited 1 time in total |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
|
Back to top |
|
 |
grknight Retired Dev

Joined: 20 Feb 2015 Posts: 2262
|
Posted: Thu Mar 03, 2022 7:21 pm Post subject: |
|
|
I would suggest hunting down the last existing device in the path. Within the same machine, the /sys path will be the same for all. (/sys is omitted from the udev output, but just put it there before /devices every time.)
This would at least clue in to what is the functioning device and what needs more investigation |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Thu Mar 03, 2022 7:30 pm Post subject: |
|
|
Thanks a lot, I'll try with the infos found in the german post (seems clear enough, and my girfriend is half-german so I could manage to traslate potential obscure points).
I'll report it if I solve the issue _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Thu Mar 03, 2022 8:43 pm Post subject: |
|
|
No luck, sorry. I tried to compile in all the suggested options, which by the way were already been compiled as modules, but it still doesn't work and doesn't appear in xiput
Reading the first thread of the two, I see that it seems suggested (not clearly stated) that the touchpad only works with wayland... uh... I have plain old X, should I try to see if it works in wayland?
Apart from the fact that I barely know what wayland is (another X server basically), I use xfce which, as far as I know, still doesn't support wayland.
I'll see if I manage to get this wayland working, and I sincerely think it can't be the root of the problem... if it is, I get the impression that linux is becoming more and more macos style, dropping legacy stuff and all
Forgive my rant of an old-school linux user
Thanks for now, If anyone have some more suggestions I'll be happy to try them! _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Thu Mar 03, 2022 9:03 pm Post subject: |
|
|
Cazzantonio wrote: | [...] I have plain old X, should I try to see if it works in wayland? |
It should work with X11 also. You need libinput -> https://wiki.gentoo.org/wiki/Libinput
Best is to have an empty /etc/X11/xorg.conf.d for starting (so no old trash is doing stupid things)
Do you have all needed modules ? (you really need all)
Another way: Try to set needed modules static into your kernel (and disable all the rest).
P.S.: What is the exact name of the machine ? Maybe I can help with this information. |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Thu Mar 03, 2022 9:20 pm Post subject: |
|
|
Yes wayland have nothing to do with this. Xubuntu doesn't have wayland and recognizes the touchpad just fine.
I already have
INPUT_DEVICES="evdev synaptics libinput"
and
dev-libs/libinput
and
x11-drivers/xf86-input-libinput
So it should be already covered.
I also already tried all conceivable combinations of static and module drivers (related to these things, so HID, input devices, multifunction, etc...). All the modules mentioned in the above suggestion were already among the first that I included in my tests. Consider that it has been a week since I started testing and I tried several kernel build each day (depending on my free time).
The laptop is a "Pcspecialist Elimina", a configurable laptop based on a core 17-11800H _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Thu Mar 03, 2022 9:26 pm Post subject: |
|
|
Cazzantonio wrote: | INPUT_DEVICES="evdev synaptics libinput" |
Delete "evdev" and "synaptics". Read this chapter: https://wiki.gentoo.org/wiki/Libinput#Troubleshooting
Then do a world-update with -N ("emerge -uNDV @world") |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Thu Mar 03, 2022 9:29 pm Post subject: |
|
|
Be sure to have this:
Code: | Device Drivers --->
Input device support --->
<*> Event interface |
AND ALL you have seen in my post. |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Thu Mar 03, 2022 9:31 pm Post subject: |
|
|
And of course all from our AMD64 handbook:
Code: | Device drivers --->
HID support --->
-*- HID bus support
[*] Battery level reporting for HID devices
[*] /dev/hidraw raw HID device support
[*] Generic HID driver |
|
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Thu Mar 03, 2022 9:37 pm Post subject: |
|
|
Are you sure you have this ? ->
Code: | Device Drivers --->
[*] GPIO Support --->
[*] Character device (/dev/gpiochipN) support
Memory mapped GPIO drivers --->
[*] Intel ICH GPIO |
(I only ask, because I saw you said nothing about GPIO ... and ... you will SEE this option only when you have enabled ICH LPC before). |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Fri Mar 04, 2022 5:00 pm Post subject: |
|
|
Thanks pietinger,
I removed evdev and synaptics, uninstalled the corresponding x11 drivers, and also double checked that everything you suggested is already build-in in the kernel
Still no luck, touchpad is still not recognized as such  _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
grknight Retired Dev

Joined: 20 Feb 2015 Posts: 2262
|
Posted: Fri Mar 04, 2022 5:07 pm Post subject: |
|
|
Cazzantonio wrote: | Thanks pietinger,
I removed evdev and synaptics, uninstalled the corresponding x11 drivers, and also double checked that everything you suggested is already build-in in the kernel
Still no luck, touchpad is still not recognized as such  |
How far down the path of /sys/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-*/i2c-FTCS1000:01/0018:2808:0101.0005/input exists?
This will give a clue to what is and is not working. |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Fri Mar 04, 2022 6:44 pm Post subject: |
|
|
grknight wrote: |
How far down the path of /sys/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-*/i2c-FTCS1000:01/0018:2808:0101.0005/input exists?
This will give a clue to what is and is not working. |
Good point!
The path goes on up to here: Code: |
ls -l /sys/devices/pci0000\:00/0000\:00\:15.0/i2c_designware.0/i2c-0/
lrwxrwxrwx 1 root root 0 4 mar 19.41 device -> ../../i2c_designware.0
lrwxrwxrwx 1 root root 0 4 mar 19.41 firmware_node -> ../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:8b
drwxr-xr-x 3 root root 0 4 mar 18.57 i2c-dev
drwxr-xr-x 2 root root 0 4 mar 19.41 power
lrwxrwxrwx 1 root root 0 4 mar 19.41 software_node -> ../../../../../kernel/software_nodes/node0
lrwxrwxrwx 1 root root 0 4 mar 18.57 subsystem -> ../../../../../bus/i2c
--w------- 1 root root 4096 4 mar 19.41 delete_device
-r--r--r-- 1 root root 4096 4 mar 18.57 name
--w------- 1 root root 4096 4 mar 19.41 new_device
-rw-r--r-- 1 root root 4096 4 mar 18.57 uevent
-r--r--r-- 1 root root 4096 4 mar 19.41 waiting_for_supplier
|
i2c-0 is the only i2c-* in i2x_designware.0/
In ubuntu I see this instead:
ls -l /sys/devices/pci0000\:00/0000\:00\:15.0/i2c_designware.0/i2c-1/
Code: | --w------- 1 root root 4096 mar 4 19:47 delete_device
lrwxrwxrwx 1 root root 0 mar 4 19:47 device -> ../../i2c_designware.0
lrwxrwxrwx 1 root root 0 mar 4 19:47 firmware_node -> ../../../../LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:8b
drwxr-xr-x 3 root root 0 mar 4 19:46 i2c-dev
drwxr-xr-x 4 root root 0 mar 4 19:46 i2c-FTCS1000:01
-r--r--r-- 1 root root 4096 mar 4 19:46 name
--w------- 1 root root 4096 mar 4 19:47 new_device
drwxr-xr-x 2 root root 0 mar 4 19:46 power
lrwxrwxrwx 1 root root 0 mar 4 19:47 software_node -> ../../../../../kernel/software_nodes/node0
lrwxrwxrwx 1 root root 0 mar 4 19:46 subsystem -> ../../../../../bus/i2c
-rw-r--r-- 1 root root 4096 mar 4 19:46 uevent
-r--r--r-- 1 root root 4096 mar 4 19:47 waiting_for_supplier |
The i2C-FTCS1000:01 device is there
Ubuntu has a 5.13 kernel, I have gentoo-sources-5.16.12 _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
grknight Retired Dev

Joined: 20 Feb 2015 Posts: 2262
|
Posted: Fri Mar 04, 2022 7:53 pm Post subject: |
|
|
Please post your kernel config to a paste site. Perhaps some details could be found.
The next driver that should be necessary is CONFIG_I2C_HID_ACPI.
If built as a module, it may need to be loaded using: Code: | modprobe --first-time i2c-hid-acpi |
|
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Sat Mar 05, 2022 9:47 am Post subject: |
|
|
Yes I2C_HID_ACPI is already compiled in.
Here is my full kernel config:
https://justpaste.it/2agtk _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Sat Mar 05, 2022 2:58 pm Post subject: |
|
|
SOLVED!
I had to remove the following boot parameters, which were left from the previous installation on my old notebook:
acpi_osi=! acpi_osi=Windows 2009
I don't even remember what they did. I only remember they rewrote some indentification string in the ACPI parameters from the bios that allowed the sound card to be correctly recognized on my old laptop, along with other ACPI quirks.
Things seems to be working now. At least my touchpad is correctly recognized.
Little rant:
Hardware things (which should ideally be single devices independent on the rest of the hardware) are becoming more and more entangled with complex interactions with other seemingly unrelated pieces of hardware... If a notebook becomes a complex system, unpredictable behavior, chaos and other funny things are just around the corner
Thanks everybody for the help given! _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Sat Mar 05, 2022 3:59 pm Post subject: |
|
|
Cazzantonio,
I see you have tried to enable as much as possible in your kernel config (even AMD parts). And I have seen also this (I have made this while you found the solution by yourself):
Code: | acpi_osi=! \"acpi_osi=Windows 2009\"
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-8d-00 intel-ucode/06-8d-01"
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_BYD=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y
CONFIG_MOUSE_PS2_CYPRESS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_ELANTECH_SMBUS=y
CONFIG_MOUSE_PS2_SENTELIC=y
CONFIG_MOUSE_PS2_TOUCHKIT=y
CONFIG_MOUSE_PS2_FOCALTECH=y
CONFIG_MOUSE_PS2_SMBUS=y
CONFIG_MOUSE_SERIAL=y
CONFIG_MOUSE_APPLETOUCH=y
CONFIG_MOUSE_BCM5974=y
CONFIG_MOUSE_CYAPA=y
CONFIG_MOUSE_ELAN_I2C=y
CONFIG_MOUSE_ELAN_I2C_I2C=y
CONFIG_MOUSE_ELAN_I2C_SMBUS=y
CONFIG_MOUSE_VSXXXAA=y
CONFIG_MOUSE_GPIO=y
CONFIG_MOUSE_SYNAPTICS_I2C=y
CONFIG_MOUSE_SYNAPTICS_USB=y
# CONFIG_INPUT_MISC is not set
CONFIG_RMI4_CORE=y
CONFIG_RMI4_I2C=y
CONFIG_RMI4_SPI=y
CONFIG_RMI4_SMB=y
CONFIG_RMI4_F03=y
CONFIG_RMI4_F03_SERIO=y
CONFIG_RMI4_2D_SENSOR=y
CONFIG_RMI4_F11=y
CONFIG_RMI4_F12=y
CONFIG_RMI4_F30=y
# CONFIG_RMI4_F34 is not set
# CONFIG_RMI4_F3A is not set
# CONFIG_RMI4_F54 is not set
# CONFIG_RMI4_F55 is not set
# I2C support
#
CONFIG_I2C=y
CONFIG_ACPI_I2C_OPREGION=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y
#
# Multiplexer I2C Chip support
#
CONFIG_I2C_MUX_GPIO=y
CONFIG_I2C_MUX_LTC4306=y
CONFIG_I2C_MUX_PCA9541=y
CONFIG_I2C_MUX_PCA954x=y
CONFIG_I2C_MUX_REG=y
CONFIG_I2C_MUX_MLXCPLD=y
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=y
CONFIG_I2C_ALGOBIT=y
#
# I2C Hardware Bus support
#
# Intel pinctrl drivers
#
CONFIG_PINCTRL_BAYTRAIL=y
CONFIG_PINCTRL_CHERRYVIEW=y
CONFIG_PINCTRL_LYNXPOINT=y
CONFIG_PINCTRL_INTEL=y
CONFIG_PINCTRL_ALDERLAKE=y
CONFIG_PINCTRL_BROXTON=y
CONFIG_PINCTRL_CANNONLAKE=y
CONFIG_PINCTRL_CEDARFORK=y
CONFIG_PINCTRL_DENVERTON=y
CONFIG_PINCTRL_ELKHARTLAKE=y
CONFIG_PINCTRL_EMMITSBURG=y
CONFIG_PINCTRL_GEMINILAKE=y
CONFIG_PINCTRL_ICELAKE=y
CONFIG_PINCTRL_JASPERLAKE=y
CONFIG_PINCTRL_LAKEFIELD=y
CONFIG_PINCTRL_LEWISBURG=y
CONFIG_PINCTRL_SUNRISEPOINT=y
CONFIG_PINCTRL_TIGERLAKE=y
# end of Intel pinctrl drivers
# I2C Hardware Bus support
#
#
# PC SMBus host controller drivers
#
# CONFIG_I2C_ALI1535 is not set
# CONFIG_I2C_ALI1563 is not set
# CONFIG_I2C_ALI15X3 is not set
CONFIG_I2C_AMD756=y
# CONFIG_I2C_AMD756_S4882 is not set
CONFIG_I2C_AMD8111=y
CONFIG_I2C_AMD_MP2=y
CONFIG_I2C_I801=y
CONFIG_I2C_ISCH=y
CONFIG_I2C_ISMT=y
CONFIG_I2C_PIIX4=y
# CONFIG_I2C_NFORCE2 is not set
CONFIG_I2C_NVIDIA_GPU=y
# CONFIG_I2C_SIS5595 is not set
# CONFIG_I2C_SIS630 is not set
# CONFIG_I2C_SIS96X is not set
# CONFIG_I2C_VIA is not set
# CONFIG_I2C_VIAPRO is not set |
Maybe you are interested to tidy up your config. Maybe you are also interested in this chapter: https://www.kernel.org/doc/html/latest/i2c/busses/index.html
Do you really need Multiplexer I2C Chip support ?
As you have TigerLake these should fit:
Code: | CONFIG_PINCTRL_TIGERLAKE=y
CONFIG_I2C_I801=y |
What happens if you load only the latest ? ->
Code: | CONFIG_EXTRA_FIRMWARE="intel-ucode/06-8d-01" |
|
|
Back to top |
|
 |
Cazzantonio Bodhisattva


Joined: 20 Mar 2004 Posts: 4514 Location: Somewere around the world
|
Posted: Sat Mar 05, 2022 4:29 pm Post subject: |
|
|
pietinger wrote: | Cazzantonio,
I see you have tried to enable as much as possible in your kernel config (even AMD parts). |
Yes, I'm cleaning up now since the issue is solved. You know, when you don't know what's happening you end up enabling way more than you need...
pietinger wrote: | Cazzantonio,
Do you really need Multiplexer I2C Chip support ? |
Maybe not! I don't even know what a multiplexed I2C chip is, or what it is used for...
pietinger wrote: | Cazzantonio,
What happens if you load only the latest ? ->
Code: | CONFIG_EXTRA_FIRMWARE="intel-ucode/06-8d-01" |
|
I use to emerge intel-microcode with "hostonly" use flag, which should install only the microcode relevant for your architecture. So these two were the only left in /lib/firmware/intel-ucode/, and I thought that it couldn't harm to have them both. It's only two files.
I can try to experiment to see if some of them is unneded, but there's the possibility that both of them are unneded because the microcode of my CPU is already updated. _________________ Any mans death diminishes me, because I am involved in Mankinde; and therefore never send to know for whom the bell tolls; It tolls for thee.
-John Donne |
|
Back to top |
|
 |
pietinger Moderator

Joined: 17 Oct 2006 Posts: 5922 Location: Bavaria
|
Posted: Sat Mar 05, 2022 4:53 pm Post subject: |
|
|
For your microcode maybe take a look into your dmesg (at the very beginning). |
|
Back to top |
|
 |
|