TouchPad not detectable in Linux.

HansS

New Member
Credits
279
Everybody who uses Linux uses the Linux kernel (https://www.kernel.org/), so even though some companies have spent money on improvements to the kernel, they also use the work of others to realize their product, so the right thing to do is to give those improvements back to the community, that is the Linux way.
Putting in license stuff etc in the kernel that makes it usable only to those who use your distro is not the linux way.
I bought an AMD graphics card for a stationary computer and I could not get the accelerated graphics to work because the pro version of the driver was only available for distro's Ubuntu, Suse, Redhat and CentOS. So now I have ditched that AMD card and will never buy AMD again!
 
Last edited:


HansS

New Member
Credits
279
OK, thanks, I won't be any help here, then - I have used Calculate and Sabayon but not Gentoo itself.

Have you considered asking at Gentoo Forum? They are at

https://forums.gentoo.org/

Cheers

Wizard
I consider this a general Linux community forum (I hope it is), and as it is the Linux kernel I am having problems with, I don't regard it as a distro related issue, but a general Linux community issue.
I have of course read through relevant wiki pages on Gentoo related to touchpads.

I also have a post on libinput forum about this and it is stranded there also, as I get no reply from the guy who I am referred to for kernel issues.

Best,
HansS
 

wizardfromoz

Administrator
Staff member
Gold Supporter
Credits
18,245
Oh well, if you don't want to answer the question, that's your call.

Good luck.

Wizard

BTW just read your post above, maybe you are not understanding my question.

Reading wiki pages is fine, but you know as well as I do that accessing the kernel is influenced by distro family, vis-a-vis command syntax and so on.

Asking at Gentoo Forum might be a better option.

You were asked at #4 on page 1

You did remember to run the 'sudo update-grub' bit, correct? I've known a number of folks who overlooked that step, so I figure I'll double check.
Given you are on Gentoo that would be something similar to

Code:
sudo grub-mkconfig -o /boot/grub/grub.cfg
and your answer to that rather, was that you had made changes to /boot/grub/grub.cfg

I expect you do know that changes you make directly to that file are unlikely to survive an update on the grub kernel and likewise the changing of certain other software?

Just a thought or two.

Wizard
 

HansS

New Member
Credits
279
Oh well, if you don't want to answer the question, that's your call.

Good luck.

Wizard

BTW just read your post above, maybe you are not understanding my question.

Reading wiki pages is fine, but you know as well as I do that accessing the kernel is influenced by distro family, vis-a-vis command syntax and so on.

Asking at Gentoo Forum might be a better option.

You were asked at #4 on page 1



Given you are on Gentoo that would be something similar to

Code:
sudo grub-mkconfig -o /boot/grub/grub.cfg
and your answer to that rather, was that you had made changes to /boot/grub/grub.cfg

I expect you do know that changes you make directly to that file are unlikely to survive an update on the grub kernel and likewise the changing of certain other software?

Just a thought or two.

Wizard
Thanks for your suggested ideas.
It is so that I managed to get the touchpad detected by inserting boot parameters (and I ended doing so in /etc/default/grub to use grub-mkconfig), but the fact is that the Lubuntu distro where I tried the LiveCD, did not have boot parameters and the touchpad worked when inserting hid_i2c module.

(I think it is wrong that distros add/change scripts in the kernel build procedure, and I think that there is a very unhealthy tendency in the Linux distro community, which will lead to the erosion of Linux, and soon one day you will wake up to a Microsoft logo when you boot your new "Linux"!)

Best,
Hans,
 

HansS

New Member
Credits
279
Oh well, if you don't want to answer the question, that's your call.

Good luck.

Wizard
P.S. It should be obvious from what I have written, that I have not made a post on Gentoo forum as I don't regard it as a Gentoo issue. But I can try that also, as there might just be someone there who is skilled with kernel issues, who can help me. And I am now also looking at the mailing lists for kernel developers.

Best,
HansS
 

Lord Boltar

Well-Known Member
Credits
5,900
Thanks for your suggested ideas.
It is so that I managed to get the touchpad detected by inserting boot parameters (and I ended doing so in /etc/default/grub to use grub-mkconfig), but the fact is that the Lubuntu distro where I tried the LiveCD, did not have boot parameters and the touchpad worked when inserting hid_i2c module.

(I think it is wrong that distros add/change scripts in the kernel build procedure, and I think that there is a very unhealthy tendency in the Linux distro community, which will lead to the erosion of Linux, and soon one day you will wake up to a Microsoft logo when you boot your new "Linux"!)

Best,
Hans,
I only think it is a matter of time and you will see a Microsoft logo on Linux
 

HansS

New Member
Credits
279
So this issue has now been resolved, long last! :)

No boot parameters are needed. What is needed is a relatively newer kernel and from the 5.13.4 I am now using, one must enable:
CONFIG_INTEL_IDMA64 CONFIG_X86_INTEL_LPSS CONFIG_PCI_MSI, acpi and designware stuff and the HID modules and some configs naturally related to those listed.

Then
modprobe i2c_hid
modprobe i2c_hid_acpi
 
Last edited:

theislander

New Member
Credits
23
So you're using the procedure described by Lord Boltar (https://www.linux.org/threads/touchpad-not-detectable-in-linux.31846/post-123936) with CONFIG_INTEL_IDMA64 and such to build the kernel? What about modprobe commands, where do they go exactly?
I'm tempted to mess around with this myself as my trackpad requires manual `modprobe i2c_hid` and, the biggest problem, it doesn't wake up after I close the lid or suspend it. I have to keep it on and plugged for that reason while I'm working on something which can take days/weeks
 
Last edited:

endruschat100

Member
Credits
430
Such Things are very nerv-racking.at my device-that was lucky with the Touchpad i have now Mageia-Distribution installed.
Maybe you have to use a normal optimal USB Mouse!
But my Problem is,how can i Install new Software Like Openoffice?
 

brickwizard

Well-Known Member
Credits
6,381

endruschat100

Member
Credits
430
thanks to brickwizard-i downloaded packages like core-7.zip<webbrowser>i forget the name
and this package <SuperTux_2-v0.6.2.glibc2.27-x86_64.appimage>
because i am a rookie-that means i dont know how to install these packages
perhaps entering something in a console?
 

Lord Boltar

Well-Known Member
Credits
5,900
thanks to brickwizard-i downloaded packages like core-7.zip<webbrowser>i forget the name
and this package <SuperTux_2-v0.6.2.glibc2.27-x86_64.appimage>
because i am a rookie-that means i dont know how to install these packages
perhaps entering something in a console?
On an AppImage there is nothing to install it is a self contained program - simply right click it select properties then Permission tab and put a check mark in the block "Allow this file to run as a program"
then just double click it to run
 

HansS

New Member
Credits
279
So you're using the procedure described by Lord Boltar (https://www.linux.org/threads/touchpad-not-detectable-in-linux.31846/post-123936) with CONFIG_INTEL_IDMA64 and such to build the kernel? What about modprobe commands, where do they go exactly?
I'm tempted to mess around with this myself as my trackpad requires manual `modprobe i2c_hid` and, the biggest problem, it doesn't wake up after I close the lid or suspend it. I have to keep it on and plugged for that reason while I'm working on something which can take days/weeks
Since I am not using the main distro's I am not using the procedure Lord Boltar suggests. I use kernels from kernel.org and configure and build them myself (make menuconfig, make, make modules, make modules_install ...). It sounds like your device has a problem with ACPI, which is what should take care of ensuring that your device wakes up properly.
You can try and download a new kernel from kernel.org, use your config from the previous kernel and build a kernel based on newer code, maybe your problem has been solved.
 
Last edited:

HansS

New Member
Credits
279
...What about modprobe commands, where do they go exactly?
...
Until now I use a script that does the modprobes for me manually after boot. I have put it into my startup scripts under systemd, but it didn't work and I admit that I have not looked more into why it didn't work.
 

HansS

New Member
Credits
279
...
I'm tempted to mess around with this myself as my trackpad requires manual `modprobe i2c_hid` and, the biggest problem, it doesn't wake up after I close the lid or suspend it. I have to keep it on and plugged for that reason while I'm working on something which can take days/weeks
There has been a problem with elan_i2c module in earlier kernels as I am told on my libinput thread, which could also be a cause of your problem, where a blacklist of this module might help.
/etc/modprobe.d/blacklist.conf
It should then contain:
blacklist elan_i2c
 

endruschat100

Member
Credits
430
Thats right,i See this Yesterday.but sorry- it ist really Nerv-racking to get this Browser called-mudori to Run.
Package ist core-7.zip.

Maybe thats the Same Prozedure Like this Other App image.
I Hope you can Help me
 

HansS

New Member
Credits
279
Until now I use a script that does the modprobes for me manually after boot. I have put it into my startup scripts under systemd, but it didn't work and I admit that I have not looked more into why it didn't work.
A system update updated systemd and now my startup script inserting the modules works.
 

wizardfromoz

Administrator
Staff member
Gold Supporter
Credits
18,245
@endruschat100 , open your own Thread and ask your questions (#51 and #57)

Chris Turner
wizardfromoz
 
$100 Digital Ocean Credit
Get a free VM to test out Linux!

Staff online

Members online


Top