Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[Riccardo Mottola via Dng]

Hi,

g4sra via Dng wrote:

A web search suggests that the following will compensate for the hardware 
issues you are experiencing
I do not have your hardware and therefore cannot test.

edit /etc/default/grub and add parameters for i8042

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.notimeout i8042.nomux"

then run
$ sudo update-grub
and reboot

When done correctly they will show on the kernel command line
$cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-?.??. root=/dev/ ro quiet splash i8042.notimeout 
i8042.nomux


this worked smooth as butter! I get no more errors in dmesg and the 
touchpad works!


Now that you gave me the hint, this appears like a very old bug never 
solved and so the solution is still current. Scary.


curious if both options were needed. Only nomux is not enough, while 
notimeout is enough to have a working pointer!


This leave space for solving other important issues on this laptop, but 
that in separate threads.


Regards,
Riccardo
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[Arnt Karlsen]

On Sun, 12 Sep 2021 19:56:16 +, g4sra wrote in message 
:

> <--snip-->
> 
> A web search suggests that the following will compensate for the
> hardware issues you are experiencing I do not have your hardware and
> therefore cannot test.
> 
> edit /etc/default/grub and add parameters for i8042
> 
> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.notimeout i8042.nomux"

..drop the "quiet" part until you have fixed this issue,
you also might try "verbose" and "debug" for even more
error and warning messages.  

..can also be done on a per boot basis; on boot-up, simply
hit "e" to edit "quiet" out of the boot command line, 
then just boot to see them thar non-quiet messages.

> then run
> $ sudo update-grub
> and reboot
> 
> When done correctly they will show on the kernel command line
> $cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-?.??. root=/dev/ ro quiet splash
> i8042.notimeout i8042.nomux
> 


-- 
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[g4sra via Dng]

<--snip-->

A web search suggests that the following will compensate for the hardware 
issues you are experiencing
I do not have your hardware and therefore cannot test.

edit /etc/default/grub and add parameters for i8042

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.notimeout i8042.nomux"

then run
$ sudo update-grub
and reboot

When done correctly they will show on the kernel command line
$cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-?.??. root=/dev/ ro quiet splash i8042.notimeout 
i8042.nomux



publickey - g4sra@protonmail.com - 0x42E94623.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[aitor]

Hi,

On 12/9/21 21:33, Riccardo Mottola via Dng wrote:

And Steve's script does:
sh touchtoggle.sh
diagnostic devid =13
diagnostic scratchline=Device Enabled (175): 1
diagnostic proptext =Device Enabled#
diagnostic propid =175
Current state of 1 has been changed to 0.

and it always says 1->0 even if you rerun it.


The script is here:

https://privatebin.net/?d6389e057f8c9f02#7x9MGMcy3fFF7adKxQzuC46xpGvPvhC7LcAkccRAcxn2 



Are we talking about the same script, Riccardo?

Cheers,

Aitor.



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[Riccardo Mottola via Dng]

Hi,

On 2021-09-12 09:04:26 +0200 Riccardo Mottola via Dng  
wrote:

> I swear there was a touchpad, now it is totally gone ! I am puzzled.

I found out at least why this happens. The EFI BIOS has a setting for "USB 
Legacy mode" for the pointing device. If I enable it, the touchpad disappears, 
if I enable it shows.
However,  neither enabled nor disabled the touchpad works!
I would assume that in compatibilty mode maybe it shoudl somehow work as a 
simple mouse?

With compatibility mode, this is reported by xinput:

$ xinput
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB Optical Mouseid=10   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=13   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Fujitsu FUJ02E3   id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ FJ Camera: FJ Camera  id=11   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]
↳ BRLTTY 6.3 Linux Screen Driver Keyboard   id=14   [slave  keyboard (3)]


And Steve's script does:
sh touchtoggle.sh 
diagnostic devid =13
diagnostic scratchline=Device Enabled (175): 1
diagnostic proptext =Device Enabled#
diagnostic propid =175
Current state of 1 has been changed to 0.

and it always says 1->0 even if you rerun it.

More ideas?

Riccardo

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] fresh install of chimaera on an Ultrabook - no touchpad

[Riccardo Mottola via Dng]

Hi,

Can  I ask you back to my oiriginal issue? Installation media issues were 
worked around anyway.
Using chimarera I updated in the meanwhile, kernel, etc. but I still have no 
working touchpad, a hassle on a small Ultrabook the goal of which is to be 
portable.

I wonder if the issue is at kernel-level or at Xorg-level

I am worried that I continue to see in the kernel messages this:
[ 3259.860388] psmouse serio1: bad data from KBC - timeout
[ 3259.862378] psmouse serio1: bad data from KBC - timeout
[ 3259.864383] psmouse serio1: bad data from KBC - timeout
[ 3259.866390] psmouse serio1: bad data from KBC - timeout
[ 3259.868340] psmouse serio1: bad data from KBC - timeout

psmouse could well be my touchpad, no?

Somebody off-list sent me a script by Steve Litt, which I did run and does not 
help, giving this output:

diagnostic devid =
diagnostic scratchline=Device Enabled (175): 1
diagnostic proptext =Device Enabled#
diagnostic propid =175
Current state of 1 has been changed to 0.
Usage: xinput set-prop  [--type=atom|float|int] [--format=8|16|32] 
  [ ...]
Usage: xinput set-prop  [--type=atom|float|int] [--format=8|16|32] 
  [ ...]


no devid is found!

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB Optical Mouseid=10   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Fujitsu FUJ02E3   id=7[slave  keyboard (3)]
↳ Video Bus id=8[slave  keyboard (3)]
↳ Power Button  id=9[slave  keyboard (3)]
↳ FJ Camera: FJ Camera  id=11   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=12   [slave  keyboard (3)]
↳ BRLTTY 6.3 Linux Screen Driver Keyboard   id=14   [slave  keyboard (3)]

I swear there was a touchpad, now it is totally gone ! I am puzzled.


I am using libinput for xorg, since synaptics when installed has no cursor 
working at all, not even the external mouse :)

However I noticed checking the XFCE mouse panel

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] fresh install of chimaera on an Ultrabook - no touchpad

[Riccardo Mottola via Dng]

Hi all,

I "converted" a laptop from Windows 7 to Devuan and as a test, I
installed chimaera. The intel display should have no issues.
Install wasn't too easy due to the system having only WiFi and no
Optical drive - the WiFi needs firmware not included in the install media.
I used an USB stick with the full DVD, installed offline then found the
firmware on debian, copied over with an USB stick and things do work.

Partitioning was also very hard, but more about that in a separate thread.

What is really annoying is that X11 works but I have no touchpad. By
attaching an external mouse the cursor works.

In dmesg I get thousands of messages like this:
[255709.204049] psmouse serio1: bad data from KBC - timeout
[255709.206127] psmouse serio1: bad data from KBC - timeout
[255709.208137] psmouse serio1: bad data from KBC - timeout
[255709.210118] psmouse serio1: bad data from KBC - timeout
[255709.212111] psmouse serio1: bad data from KBC - timeout
[255709.213986] psmouse serio1: bad data from KBC - timeout
[255709.215980] psmouse serio1: bad data from KBC - timeout
[255709.217997] psmouse serio1: bad data from KBC - timeout
[255709.219983] psmouse serio1: bad data from KBC - timeout
[255709.222021] psmouse serio1: bad data from KBC - timeout
[255709.224043] psmouse serio1: bad data from KBC - timeout

I suppose it is related... psmouse! I have no other dmesg data since it
went overflow.

lsusb lists nothing:
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 10f1:1a44 Importek FJ Camera
Bus 001 Device 005: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 003: ID 0bda:0138 Realtek Semiconductor Corp. RTS5138
Card Reader Controller
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:07da Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The optical mouse is my Trust mouse I attached.

In Xorg I see:
[   121.142] (II) LoadModule: "libinput"
[   121.142] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[   121.214] (II) Module libinput: vendor="X.Org Foundation"
[   121.214]    compiled for 1.20.8, module version = 0.30.0
[   121.214]    Module class: X.Org XInput Driver
[   121.214]    ABI class: X.Org XInput driver, version 24.1
[   121.214] (II) Using input driver 'libinput' for 'Power Button'
[   121.214] (**) Power Button: always reports core events
[   121.214] (**) Option "Device" "/dev/input/event4"
[   121.215] (**) Option "_source" "server/udev"
[   121.239] (II) event4  - Power Button: is tagged by udev as: Keyboard
[   121.240] (II) event4  - Power Button: device is a keyboard
[   121.240] (II) event4  - Power Button: device removed
[   121.260] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4"
[   121.260] (II) XINPUT: Adding extended input device "Power Button"
(type: KEYBOARD, id 6)
[   121.260] (**) Option "xkb_model" "pc105"
[   121.260] (**) Option "xkb_layout" "it"
[   121.281] (II) event4  - Power Button: is tagged by udev as: Keyboard
[   121.281] (II) event4  - Power Button: device is a keyboard
[   121.282] (II) config/udev: Adding input device Fujitsu FUJ02E3
(/dev/input/event5)
[   121.282] (**) Fujitsu FUJ02E3: Applying InputClass "libinput
keyboard catchall"
[   121.282] (II) Using input driver 'libinput' for 'Fujitsu FUJ02E3'
[   121.282] (**) Fujitsu FUJ02E3: always reports core events
[   121.282] (**) Option "Device" "/dev/input/event5"
[   121.282] (**) Option "_source" "server/udev"
[   121.282] (II) event5  - Fujitsu FUJ02E3: is tagged by udev as: Keyboard
[   121.282] (II) event5  - Fujitsu FUJ02E3: device is a keyboard
[   121.282] (II) event5  - Fujitsu FUJ02E3: device removed
[   121.352] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input6/event5"
[   121.352] (II) XINPUT: Adding extended input device "Fujitsu FUJ02E3"
(type: KEYBOARD, id 7)
[   121.352] (**) Option "xkb_model" "pc105"
[   121.352] (**) Option "xkb_layout" "it"
[   121.355] (II) event5  - Fujitsu FUJ02E3: is tagged by udev as: Keyboard
[   121.355] (II) event5  - Fujitsu FUJ02E3: device is a keyboard
[   121.357] (II) config/udev: Adding input device Video Bus
(/dev/input/event7)
[   121.357] (**) Video Bus: Applying InputClass "libinput keyboard
catchall"
[   121.357] (II) Using input driver 'libinput' for 'Video Bus'
[   121.357] (**) Video Bus: always reports core events
[   121.357] (**) Option "Device" "/dev/input/event7"
[   121.357] (**) Option "_source" "server/udev"
[   121.359] (II) event7  - Video Bus: is tagged by udev as: Keyboard
[   121.359] (II) event7  - Video Bus: device is a keyboard
[   121.359] (II) event7  - Video Bus: device removed
[   121.408] (**) Option "config_info"