You are not logged in.
Pages: 1
Hi everyone,
I installed last version of bunsenlabs in my laptop, everything was as expected but the touchpad is not working, (mouse ok).
Here some command outputs
cat /proc/bus/input/devices | grep -I touchpad
return nothing.
# xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ BisonCam, NB Pro: BisonCam, NB id=6 [slave keyboard (3)]
↳ Logitech USB Keyboard id=8 [slave keyboard (3)]
↳ Logitech USB Keyboard Consumer Control id=9 [slave keyboard (3)]
↳ Logitech USB Keyboard System Control id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)]
I installed xserver-xorg-input-synaptics but no working so it was removed. xserver-xorg-input-libinput, xserver-xorg-input-evdev and xserver-xorg-input-mouse are installed.
Also I have set boot options:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off i8042.reset i8042.nomux=1 i8042.nopnp i8042.noloop"
still no detected.
The touchpad was working with the previous bunsenlab version.
Thanks in advance for any advice in this matter.
Kind regards
Naddan
Offline
What relevant config do you have in /etc/X11/xorg.conf.d ?
Have you tried 'dmesg|grep i8042'?
Where did you get those kernel command options from, and what do you think they achieve? Why 'acpi=off'? Surely that is overkill.
What kernel, what hardware?
Does the touchpad not work at all, or does it work, but with the fallback driver (jittery)?
Please use CODE tags for code.
Search youtube without a browser: repo | thread
BL quote proposals to this thread please.
my repos / my repos
Offline
Hi ohnonot,
The only config in /etc/X11/xorg.conf.d is a file 20-intel.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
EndSection
without this, the system just display a black screen when the screen is looked and is unable to unlock it.
# dmesg | grep i8042
[ 1.033510] i8042: PNP: No PS/2 controller found.
[ 1.033510] i8042: Probing ports directly.
[ 1.291697] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.295718] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
For the option i8042 from here
for the option acpi=off I do not think it is overkill since it just disable the ACPI temporary at boot time. And it is needed otherwise the system hang at boot time....
Kernel: 4.19.0-8-amd64, on a Skylake system.
The touchpad is not working at all....
Offline
My laptop is dual boot, so I installed debian9 (kernel 4.9...) as the second OS. The touchpad works as expected.
The output for xinput
# xinput list
Virtual core pointer
Virtual core XTEST pointer ...
SynPS/2 Synaptics Touchpad ...
Is this a matter or kernel or module/drivers?
So should I build a kernel using the kernel options from the debian9 installation?
Offline
Bringing a new distro into this thread will make things confusing.
I will continue to refer to your original question and Bunsenlabs (Helium, I presume?).
First of all you need your system to recognize the device at all.
Remove those esoteric linux command line options.
Then have a more generic look at /proc/bus/input/devices or 'lshw' or 'dmesg' or /var/log/Xorg.0.log.
If your OS does not see the device at all there isn't much we can do.
I just spent a long time doing web searches on your behalf, so please don't take this lightly.
Also "Skylake system" is a little vague, esp. since intel did not make the touchpad.
Eventually, this answer might come in handy.
Please use CODE tags for code.
Search youtube without a browser: repo | thread
BL quote proposals to this thread please.
my repos / my repos
Offline
Bringing a new distro into this thread will make things confusing.
I will continue to refer to your original question and Bunsenlabs (Helium, I presume?).
I commented about my installation of debian9 as reference and as example that the touchpad is detected by debian9. I do not see how it could generate a confusion.
First of all you need your system to recognize the device at all.
Remove those esoteric linux command line options.
Obviously by calling them esoteric you do not understand them either... Without those options, the machine just hang at boot.
I just spent a long time doing web searches on your behalf, so please don't take this lightly.
Well thank you but I DID that research before asking for help here.
Link provided totally useless... Thank you anyway.
Offline
Pages: 1