Touchpad works in Ubuntu but not Slackware Current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Touchpad works in Ubuntu but not Slackware Current
Hello,
Sorry for the duplicate thread, I originally started this in the laptop section before I had done a test with Ubuntu.
My touchpad on my laptop (PcSpecialist Fusion Series) isn't working after installing Slackware current, and nothing is showing up in /proc/bus/input/devices.
I tried booting from a Ubuntu live iso and it worked straight away. Ubuntu is on a slightly different kernel (5.4.0-26) comparent to Current (5.4.41).
/proc/bus/input/devices shows up as follows in Ubuntu: From this info is it possible to work out what I should do to get this working in slackware?
Did you use huge or generic kernel?
i assume it's huge since it's a new installation.
please try with generic kernel first
Quote:
Originally Posted by I.G.O.R
Did you install xf86-input-synaptics?
Thanks for the replies. I've temporarily parked this, I've always loved Slackware but for the first time in years I've decided to try out some new distros.
There shouldn't be a difference on HW support between the two kernels. I've always used the scaremongering huge kernel because the improperly named "generic" is difficult to use and I had no actual usage for it until now (encrypted drive, etc). https://www.kernel.org/doc/html/v4.1...de/initrd.html
Quote:
The key role of initrd here is to re-use the configuration data during normal system operation without requiring the use of a bloated “generic” kernel or re-compiling or re-linking the kernel.
@gusgorman
Sorry to see you go. It's not the distribution that caused your issue, but the kernel. It would have been beneficial for us to learn and fix the kernel support for your particular hardware. Maybe comparing the kernel config from Ubuntu with the one from Slackware would highlight the differences in HW support. Unfortunately I have no clue about Ubuntu and where I could find the kernel config file.
There shouldn't be a difference on HW support between the two kernels. I've always used the scaremongering huge kernel because the improperly named "generic" is difficult to use and I had no actual usage for it until now (encrypted drive, etc). https://www.kernel.org/doc/html/v4.1...de/initrd.html
@gusgorman
Sorry to see you go. It's not the distribution that caused your issue, but the kernel. It would have been beneficial for us to learn and fix the kernel support for your particular hardware. Maybe comparing the kernel config from Ubuntu with the one from Slackware would highlight the differences in HW support. Unfortunately I have no clue about Ubuntu and where I could find the kernel config file.
I've actually got Manjaro running on this machine at the moment. I can send you any config you want. Its my first time on any arch related distro so off the top of my head I don't know where the kernel config file is... but I'll have a look.
I've actually got Manjaro running on this machine at the moment. I can send you any config you want. Its my first time on any arch related distro so off the top of my head I don't know where the kernel config file is... but I'll have a look.
In the outputs from your first post it appears you're using the i2c_designware_pci driver, which is supported by both the Slackware & Manjaro kernels. And, it looks to be a problematic driver (some issues are reported starting with the 5.4 kernel): https://bbs.archlinux.org/viewtopic.php?id=252711
- from the outputs in your first post - your Touchpad, apparently connected throgh I2C and using i2c_designware (highlighted in bold):
Now, there are some slight differences between the Slackware(5.4.42) and Manjaro(5.7rc6-1) kernels (there could be options available only in the newer 5.7 kernel):
- in the I2C support sections, Manjaro has some additional options enabled:
Code:
#
# I2C support
#
CONFIG_ACPI_I2C_OPREGION=y
#
# Multiplexer I2C Chip support
#
CONFIG_I2C_ARB_GPIO_CHALLENGE=m
CONFIG_I2C_MUX_GPMUX=m
CONFIG_I2C_MUX_PINCTRL=m
CONFIG_I2C_DEMUX_PINCTRL=m
#
# PC SMBus host controller drivers
#
CONFIG_I2C_CHT_WC=m
#
# I2C system bus drivers (mostly embedded / system-on-chip)
- this is the section where the CONFIG_I2C_DESIGNWARE_CORE is also enabled (modular in Slackware and in-kernel in Manjaro)
#
CONFIG_I2C_CBUS_GPIO=m
CONFIG_I2C_KEMPLD=m
CONFIG_I2C_RK3X=m
It would be interesting to boot Slackware, if you still have it installed, or a Slackware Live system (USB stick) and provide the I2C related kernel boot messages (dmesg).
It would be interesting to boot Slackware, if you still have it installed, or a Slackware Live system (USB stick) and provide the I2C related kernel boot messages (dmesg).
I don't still have Slackware installed, but I'll give booting off a USB stick a go later today.
Fyi i'm using the following kernel:
Code:
$ uname -r
5.6.12-1-MANJARO
and have checked /proc/bus/input/devices on my Manjaro installation and its the same driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.