input: CUST0000:00 04F3:30A0 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-CUST0000:00/0018:04F3:30A0.0002/input/input7
input: CUST0000:00 04F3:30A0 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-CUST0000:00/0018:04F3:30A0.0002/input/input9
00:15.0 Signal processing controller: Intel CorporationSunrise Point-LP Serial IO I2C Controller#0(rev 21)
Subsystem: Hewlett-Packard Company Sunrise Point-LP Serial IO I2C Controller
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
(II) config/udev: Adding input device CUST0000:00 04F3: 30A0 Touchpad (/dev/input/event15)
(**) CUST0000:00 04F3:30A0 Touchpad: Applying InputClass "libinput touchpad catchall"
(II) Using input driver 'libinput' for 'CUST0000:00 04F3:30A0 Touchpad
(**) CUST0000:00 04F3:30A0 Touchpad: always reports core events
(**) Option "Device" "/dev/input/event15"
(**) Option "_source" "server/udev"
(II) event15 - CUST0000:00 04F3:30A0 Touchpad:is tagged by udev as: Touchpad
(II) event15 - CUST0000:00 04F3:30A0 Touchpad:device is a touchpad
(II) event15 - CUST0000:00 04F3:30A0 Touchpad:device removed
(**) Option"config_info" "udev:/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-5/i2c-CUST0000:00/0018:04F3:30A0.0002/input/input21/event15"
(II)XINPUT: Addingextended input device "CUST0000:00 04F3:30A0 Touchpad" (type: TOUCHPAD, id 11)
(**) Option "AccelerationScheme" "none"
(**) CUST0000:00 04F3:30A0 Touchpad: (accel) selected shceme none/0
(**) CUST0000:00 04F3:30A0 Touchpad: (accel) acceleration factor: 2.000
(**) CUST0000:00 04F3:30A0 Touchpad: (accel) acceleration threshold: 4
(II) event15 - CUST0000:00 04F3:30A0 Touchpad: is tagged by udev as: Touchpad
(II) event15 - CUST0000:00 04F3:30A0 Touchpad: device is a touchpad
(II) config/udev: Adding input device CUST0000:00 04F3:30A0 Touchpad (/dev/input/mouse1)
(II) No input driver specified, ignoring this device
... But I see that it's loading it with "i2c_designware" in the path ...Try installing i2c-5.4.3-tinycore64.tcz.
Hi mrjake2Quote... But I see that it's loading it with "i2c_designware" in the path ...Try installing i2c-5.4.3-tinycore64.tcz.
In tc-10.x, Xorg-7.7 used xf86-input-evdev to detect input devices - this changed to xf86-input-libinput in tc-11.x.
You might want to check that you don't have both xf86-input-evdev and xf86-input-libinput loaded.
Hi mrjake2
This is basically what I went through finding drivers for an ASUS tablet for audio, BlueTooth, camera, I2C, wireless, GPIO, .......
I finally made a script to scan the tablet and create files that showed found hardware and drivers. I then wound up using the
various device IDs to grep the kernel sources to figure out which options I needed to enable in the kernel. Then compiled
a custom kernel. I went through this iteration 4 or 5 times.
hid:b0018g0004v000004F3p000030A0
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid-generic.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid-multitouch.ko
-e
input:b0018v04F3p30A0e0100-e0,1,3,4,k110,111,145,148,14A,14D,14E,14F,ra0,1,2F,35,36,37,39,m5,lsfw
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/macintosh/mac_hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/macintosh/joydev.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/macintosh/joydev.ko
-e
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid-generic.ko
So when you say "device IDs" above, is that what you mean?I mean a number that uniquely identifies a device. The VID:PID for example:
hid:b0018g0004v000004F3p000030A0
Ok, I think I've made a bit of progress here thanks to Rich's script. I couldn't find any useful information when running it on TC, but when I ran it on my working Linux Mint install I got the following from modaliasdrivers.txt:That's because you were focused on what that file was telling you and ignoring what it wasn't telling you. It tells you which drivers
linux driver 04F3:30A0
grep -ri "04f3" Path/To/Kernel/Source/* | grep -i "30a0"
grep -ri "04f3" /lib/modules/KERNEL/modules.alias | grep -i "30a0"
Here things get interesting. If you look at the current kernel config file:Code: [Select]hid:b0018g0004v000004F3p000030A0
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid-generic.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid.ko
insmod /lib/modules/5.0.0-32-generic/kernel/drivers/hid/hid-multitouch.ko
#
# HID support
#
CONFIG_HID=y
CONFIG_HID_BATTERY_STRENGTH=y
CONFIG_HIDRAW=y
# CONFIG_UHID is not set
CONFIG_HID_GENERIC=y
----- SNIP -----
CONFIG_HID_MULTITOUCH=m
... Then I tried Puppy Linux (bionic). The toutchpad works. Is it possible to use their kernel (http://distro.ibiblio.org/puppylinux/puppy-bionic/bionicpup64/)?If you are talking about using Tinycore extensions with a Puppy kernel, I'm going to say no. Any extension that depends on kernel
tc@E310:~/BuildTCZs/GPicView$ uname -r
4.19.10-tinycore
tc@E310:~/BuildTCZs/GPicView$
tc@E310:~/BuildTCZs/GPicView$ modinfo pcspkr
filename: /lib/modules/4.19.10-tinycore/kernel/drivers/input/misc/pcspkr.ko.gz
author: Vojtech Pavlik <vojtech@ucw.cz>
description: PC Speaker beeper driver
license: GPL
alias: platform:pcspkr
depends:
intree: Y
vermagic: 4.19.10-tinycore SMP mod_unload 486
tc@E310:~/BuildTCZs/GPicView$
You could try this:thanks ! juanito , ftrCode: [Select]$ sudo /usr/local/lib/libinput/libinput-list-devices
$ sudo /usr/local/lib/libinput/libinput list-devices
rmmod i2c_hid
modprobe i2c_hid
it seems that probing the HID I2C touchpad gets deferred until the GPIO chip gets probed
diff ./x86/provides.db ./x86_64/provides.db |grep gpio
the forum is having problems ??
internal server error for preview post , with lots of text =S
the forum is having problems ??Clicking the back button on your browser should get you back to the post you were working on.
internal server error for preview post , with lots of text =S