[SOLVED] Hp chromebook c1030 Elan Touchpad not detected

[Latrina]

Hello folks,

I have had this HP Chromebook elite C1030 for about a week now and I am struggling to get the Elan touchpad to work under Gentoo. I am assuming the issue could be related to my kernel configuration as it doesn't even get detected. However, it works fine under both Fedora and Ubuntu.

I have compiled the relative kernel modules based on Fedora lsmod output, but still no go.

This is how the touchpad is seen from Fedora:

Code: Select all

scum@c1030 ~ $ grep  -i elan fedora/libinput  -A17
Device:           Elan Touchpad
Kernel:           /dev/input/event5
Group:            5
Seat:             seat0, default
Size:             119x71mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a
scum@c1030 ~ $ grep  -i elan fedora/dmesg 
[    8.747954] elants_i2c i2c-ELAN0001:00: supply vcc33 not found, using dummy regulator
[    8.748005] elants_i2c i2c-ELAN0001:00: supply vccio not found, using dummy regulator
[    8.769911] elants_i2c i2c-ELAN0001:00: nothing at this address
[    8.801997] elan_i2c i2c-ELAN0000:00: supply vcc not found, using dummy regulator
[    8.921685] elan_i2c i2c-ELAN0000:00: Elan Touchpad: Module ID: 0x00ac, Firmware: 0x0002, Sample: 0x0003, IAP: 0x0000
[    8.922911] input: Elan Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN0000:00/input/input6
scum@c1030 ~ $ 

This is the related kernel config:

Code: Select all

scum@c1030 ~ $  grep -iE 'elan|designware|cannonlake' /usr/src/linux/.config |grep -v '#'
CONFIG_MOUSE_PS2_ELANTECH=y
CONFIG_MOUSE_PS2_ELANTECH_SMBUS=y
CONFIG_MOUSE_ELAN_I2C=m
CONFIG_MOUSE_ELAN_I2C_I2C=y
CONFIG_MOUSE_ELAN_I2C_SMBUS=y
CONFIG_TOUCHSCREEN_ELAN=m
CONFIG_I2C_DESIGNWARE_CORE=m
CONFIG_I2C_DESIGNWARE_PLATFORM=m
CONFIG_I2C_DESIGNWARE_PCI=m
CONFIG_PINCTRL_CANNONLAKE=m
CONFIG_SND_SOC_SOF_CANNONLAKE=m
CONFIG_HID_ELAN=m
CONFIG_USB_FTDI_ELAN=m
scum@c1030 ~ $ 

USE and INPUT_DEVICES config in make.conf:

Code: Select all

scum@c1030 ~ $ grep -iE 'use|input' /etc/portage/make.conf 
USE="-doc -handbook -gtk-doc -systemd -plasma -qt5 -X -tracker wayland egl pulseaudio alsa gnome ffmpeg udisks dbus"
INPUT_DEVICES="synaptics libinput"
scum@c1030 ~ $ 

x11-drivers/xf86-input-synaptics is also installed.

Code: Select all

scum@c1030 ~ $ emerge -s x11-drivers/xf86-input-synaptics
  
[ Results for search key : x11-drivers/xf86-input-synaptics ]
Searching...

*  x11-drivers/xf86-input-synaptics
      Latest version available: 1.9.1
      Latest version installed: 1.9.1
      Size of files: 492 KiB
      Homepage:      https://www.x.org/wiki/ https://gitlab.freedesktop.org/xorg/driver/xf86-input-synaptics
      Description:   Driver for Synaptics touchpads
      License:       MIT

[ Applications found : 1 ]

scum@c1030 ~ $ 

I have ran out of ideas and don't know what else to do.

Here is Gentoo dmesg, lsmod, kernel config.

Also if of any help, here is Fedora dmesg, lsmod, libinput list-devices, kernel config.

Any help will be much appreciated.

Thanks

[pietinger]

Maybe you have problems because you miss some kernel settings. First of all you should try to enable this:

Code: Select all

Device Drivers  --->
  HID support  --->
    Special HID drivers  --->
      [*] HID Multitouch panels

If it doesnt help enable:

Code: Select all

Processor type and features  --->
  [*] Intel Low Power Subsystem Support

(of course both are enabled also in Fedora's Kernel Config)

I dont know if this is needed for your touchpad, but it should be enabled in every case:

Code: Select all

Device Drivers  --->
  Multifunction device drivers  --->
    [*] Intel ICH LPC

(this must have been enabled to see the following option)

Device Drivers  --->
  [*] GPIO Support  --->
    Memory mapped GPIO drivers  --->
      [*] Intel ICH GPIO

(of course both are enabled also in Fedora's Kernel Config)

[genBTC]

I got a custom kernel config made for you based on the old one you sent me https://dpaste.com/HFHQPG8ET
-thanks to TDR @ irc

I mentioned sound and touchscreen didnt work also , so hopefully all 3 should be good for now. find me on irc for questions
-gen

We located a big section of designware that wasnt enabled:
# DesignWare PCI Core Support
#
CONFIG_PCIE_DW=y
CONFIG_PCIE_DW_HOST=y
CONFIG_PCIE_DW_PLAT=y
CONFIG_PCIE_DW_PLAT_HOST=y
CONFIG_PCI_MESON=y
# end of DesignWare PCI Core Support


Among other things, i cant itemize them all in here

[pietinger]

I got a custom kernel config made for you based on the old one you sent me https://dpaste.com/HFHQPG8ET

I see all 4 mentioned options are enabled and I think this kernel config should work. But from a security point of view I cant recommend it. Only one example:

Code: Select all

CONFIG_MODIFY_LDT_SYSCALL=y

See more here: https://kernsec.org/wiki/index.php/Kern ... d_Settings

[genBTC]

Yes, and Since there were a lot of changes I dont personally agree with, like the KSPP options you brought up:
I will go the extra mile and itemize some more task on target options.
Here were some of the more relevant parts of the config that were toggled:

Pietingers suggestions:

+CONFIG_X86_INTEL_LPSS=y

+CONFIG_LPC_SCH=m
(LPC_ICH was already on)
(GPIO_ICH was already on)

+CONFIG_HID_MULTITOUCH=m

Others:

+CONFIG_MOUSE_SYNAPTICS_I2C=m
+CONFIG_MOUSE_SYNAPTICS_USB=m

+CONFIG_RMI4_CORE=m
+CONFIG_RMI4_I2C=m
+CONFIG_RMI4_SMB=m
+ all the others RMI4 (synaptics)

+CONFIG_I2C_MUX_GPIO=y
+CONFIG_I2C_MUX_REG=y
+all the other I2C MUX chip's

+CONFIG_I2C_SCMI=y

+CONFIG_I2C_DESIGNWARE_SLAVE=y
+CONFIG_I2C_GPIO=m
+CONFIG_I2C_SLAVE=y

+CONFIG_HP_WMI=m
+CONFIG_INTEL_WMI=y
(idk)

Take these ideas, look at the relevant sections, look at the diffs and run with them. GL!!

[Latrina]

I got a custom kernel config made for you based on the old one you sent me https://dpaste.com/HFHQPG8ET
-thanks to TDR @ irc

I mentioned sound and touchscreen didnt work also , so hopefully all 3 should be good for now. find me on irc for questions
-gen

We located a big section of designware that wasnt enabled:
# DesignWare PCI Core Support
#
CONFIG_PCIE_DW=y
CONFIG_PCIE_DW_HOST=y
CONFIG_PCIE_DW_PLAT=y
CONFIG_PCIE_DW_PLAT_HOST=y
CONFIG_PCI_MESON=y
# end of DesignWare PCI Core Support


Among other things, i cant itemize them all in here

Omg, selecting these kernel components does get the bloody touchpad to work. I am in tears I cannot believe it. However, I tried the kernel config you have shared and neither touchscreen nor audio are working. And I get a bunch of weird bug messages in dmesg that I do not get with mine. Take a look.. Reverting back to my config with the suggested DW modules.

[Latrina]

I got a custom kernel config made for you based on the old one you sent me https://dpaste.com/HFHQPG8ET

I see all 4 mentioned options are enabled and I think this kernel config should work. But from a security point of view I cant recommend it. Only one example:

Code: Select all

CONFIG_MODIFY_LDT_SYSCALL=y

See more here: https://kernsec.org/wiki/index.php/Kern ... d_Settings

Thanks for pointing that out. I am rebuilding the kernel without CONFIG_MODIFY_LDT_SYSCALL. Hopefully the touchpad will still be working. Otherwise I will have to enable it back :S

[Latrina]

Good news, touchpad does work without CONFIG_MODIFY_LDT_SYSCALL.

Now, any idea as to how to get either the touchscreen or the sound card to work? Unfortunately I have no idea on the touchscreen chipset and I forgot taking a dump of the ChromeOS logs. However, the soundcard on Fedora does show up as rt5682 i2c-10EC5682:00, though it does not work.

Code: Select all

scum@c1030 ~ $ grep -i sound  fedora/dmesg  -B3
[    9.606557] rt5682 i2c-10EC5682:00: supply VBAT not found, using dummy regulator
[    9.620827] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
[    9.633103] thermal thermal_zone5: failed to read out thermal zone (-61)
[    9.658550] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input8
[    9.658601] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input9
[    9.658642] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input10
[    9.658690] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[    9.658728] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
scum@c1030 ~ $ 

Thanks

[Latrina]

I got a custom kernel config made for you based on the old one you sent me https://dpaste.com/HFHQPG8ET

I see all 4 mentioned options are enabled and I think this kernel config should work. But from a security point of view I cant recommend it. Only one example:

Code: Select all

CONFIG_MODIFY_LDT_SYSCALL=y

See more here: https://kernsec.org/wiki/index.php/Kern ... d_Settings

I have done some light hardening and overall polishing. This is how my kernel config looks like now.

Thanks

[pietinger]

Yes, and Since there were a lot of changes I dont personally agree with, like the KSPP options you brought up

For the record: This is not only my thought - our Gentoo kernel developers think it is important and therefore they have added it to our Gentoo configuration in the kernel:

Code: Select all

Gentoo Linux  --->
  [*] Kernel Self Protection Project  --->
    [*]   Enable Kernel Self Protection Project Recommendations
    [*]     X86_64 KSPP Settings

If you dont see these two options, then some kernel options are enabled which must be disabled. First look into the help:

Code: Select all

CONFIG_GENTOO_KERNEL_SELF_PROTECTION:                                                                                                                                                                                              
Recommended Kernel settings based on the suggestions from the Kernel Self Protection Project                                                                                                                                      
See: https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings                                                                                                                                        
Note, there may be additional settings for which the CONFIG_ setting is invisible in menuconfig due                                                                                                                               
to unmet dependencies. Search for GENTOO_KERNEL_SELF_PROTECTION_COMMON and search for                                                                                                                                             
GENTOO_KERNEL_SELF_PROTECTION_{X86_64, ARM64, X86_32, ARM} for dependency information on your                                                                                                                                      
specific architecture.                                                                                                                                                                                                            
Note 2: Please see the URL above for numeric settings, e.g. CONFIG_DEFAULT_MMAP_MIN_ADDR=65536                                                                                                                                    
for X86_64

Second look into /usr/src/linux/distro/Kconfig (yes, this is our gentoo kernel config). There you will see:

Code: Select all

        depends on GENTOO_LINUX && !ACPI_CUSTOM_METHOD && !COMPAT_BRK && !DEVKMEM && !PROC_KCORE && !COMPAT_VDSO && !KEXEC && !HIBERNATION && !LEGACY_PTYS && !X86_X32 && !MODIFY_LDT_SYSCALL && GCC_PLUGINS

        select BUG
        select STRICT_KERNEL_RWX
        select DEBUG_WX
        select STACKPROTECTOR
        select STACKPROTECTOR_STRONG
        select STRICT_DEVMEM if DEVMEM=y
        select IO_STRICT_DEVMEM if DEVMEM=y
        select SYN_COOKIES
        select DEBUG_CREDENTIALS
        select DEBUG_NOTIFIERS
        select DEBUG_LIST
        select DEBUG_SG
        select BUG_ON_DATA_CORRUPTION
        select SCHED_STACK_END_CHECK
        select SECCOMP if HAVE_ARCH_SECCOMP
        select SECCOMP_FILTER if HAVE_ARCH_SECCOMP_FILTER
        select SECURITY_YAMA
        select SLAB_FREELIST_RANDOM
        select SLAB_FREELIST_HARDENED
        select SHUFFLE_PAGE_ALLOCATOR
        select SLUB_DEBUG
        select PAGE_POISONING
        select PAGE_POISONING_NO_SANITY
        select PAGE_POISONING_ZERO
        select INIT_ON_ALLOC_DEFAULT_ON
        select INIT_ON_FREE_DEFAULT_ON
        select REFCOUNT_FULL
        select FORTIFY_SOURCE
        select SECURITY_DMESG_RESTRICT
        select PANIC_ON_OOPS
        select GCC_PLUGIN_LATENT_ENTROPY
        select GCC_PLUGIN_STRUCTLEAK
        select GCC_PLUGIN_STRUCTLEAK_BYREF_ALL
        select GCC_PLUGIN_RANDSTRUCT
        select GCC_PLUGIN_RANDSTRUCT_PERFORMANCE

The first line is important: You will see this menu option only if all these kernel options are ! (=not) enabled ...


Let's put it this way: When I do a kernel config for my own, I can do what I want - even an insecure configuration. If I do a kernel for others, it should be as secure as possible ... Now, go on and find out what is the problem with sound ...

Kind regards,
pietinger

[Latrina]

Yes, and Since there were a lot of changes I dont personally agree with, like the KSPP options you brought up

For the record: This is not only my thought - our Gentoo kernel developers think it is important and therefore they have added it to our Gentoo configuration in the kernel:

Code: Select all

Gentoo Linux  --->
  [*] Kernel Self Protection Project  --->
    [*]   Enable Kernel Self Protection Project Recommendations
    [*]     X86_64 KSPP Settings

If you dont see these two options, then some kernel options are enabled which must be disabled. First look into the help:

Code: Select all

CONFIG_GENTOO_KERNEL_SELF_PROTECTION:                                                                                                                                                                                              
Recommended Kernel settings based on the suggestions from the Kernel Self Protection Project                                                                                                                                      
See: https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Recommended_Settings                                                                                                                                        
Note, there may be additional settings for which the CONFIG_ setting is invisible in menuconfig due                                                                                                                               
to unmet dependencies. Search for GENTOO_KERNEL_SELF_PROTECTION_COMMON and search for                                                                                                                                             
GENTOO_KERNEL_SELF_PROTECTION_{X86_64, ARM64, X86_32, ARM} for dependency information on your                                                                                                                                      
specific architecture.                                                                                                                                                                                                            
Note 2: Please see the URL above for numeric settings, e.g. CONFIG_DEFAULT_MMAP_MIN_ADDR=65536                                                                                                                                    
for X86_64

Second look into /usr/src/linux/distro/Kconfig (yes, this is our gentoo kernel config). There you will see:

Code: Select all

        depends on GENTOO_LINUX && !ACPI_CUSTOM_METHOD && !COMPAT_BRK && !DEVKMEM && !PROC_KCORE && !COMPAT_VDSO && !KEXEC && !HIBERNATION && !LEGACY_PTYS && !X86_X32 && !MODIFY_LDT_SYSCALL && GCC_PLUGINS

        select BUG
        select STRICT_KERNEL_RWX
        select DEBUG_WX
        select STACKPROTECTOR
        select STACKPROTECTOR_STRONG
        select STRICT_DEVMEM if DEVMEM=y
        select IO_STRICT_DEVMEM if DEVMEM=y
        select SYN_COOKIES
        select DEBUG_CREDENTIALS
        select DEBUG_NOTIFIERS
        select DEBUG_LIST
        select DEBUG_SG
        select BUG_ON_DATA_CORRUPTION
        select SCHED_STACK_END_CHECK
        select SECCOMP if HAVE_ARCH_SECCOMP
        select SECCOMP_FILTER if HAVE_ARCH_SECCOMP_FILTER
        select SECURITY_YAMA
        select SLAB_FREELIST_RANDOM
        select SLAB_FREELIST_HARDENED
        select SHUFFLE_PAGE_ALLOCATOR
        select SLUB_DEBUG
        select PAGE_POISONING
        select PAGE_POISONING_NO_SANITY
        select PAGE_POISONING_ZERO
        select INIT_ON_ALLOC_DEFAULT_ON
        select INIT_ON_FREE_DEFAULT_ON
        select REFCOUNT_FULL
        select FORTIFY_SOURCE
        select SECURITY_DMESG_RESTRICT
        select PANIC_ON_OOPS
        select GCC_PLUGIN_LATENT_ENTROPY
        select GCC_PLUGIN_STRUCTLEAK
        select GCC_PLUGIN_STRUCTLEAK_BYREF_ALL
        select GCC_PLUGIN_RANDSTRUCT
        select GCC_PLUGIN_RANDSTRUCT_PERFORMANCE

The first line is important: You will see this menu option only if all these kernel options are ! (=not) enabled ...


Let's put it this way: When I do a kernel config for my own, I can do what I want - even an insecure configuration. If I do a kernel for others, it should be as secure as possible ... Now, go on and find out what is the problem with sound ...

Kind regards,
pietinger

That's a lot of hardening! Won't that affect the overall system performance?

[pietinger]

Won't that affect the overall system performance?

Yes, its affects the overall system performance. May I suggest a test: Look to your system performance without these and with these configuration, then decide. As being paranoid for security I must recommend it always, but of course it is your decision.

(For example I have an Intel i7 and I noticed no difference with this hardened kernel, so my decision was simple ... )