R4.0 laptop trackpad not enabled in installer, OK after first boot

[trueriver]

Qubes OS version:

R4.0

Affected component(s):

Installer, trackpad

---

Steps to reproduce the behavior:

Download r4.0 ISO, dd to USB
Boot from USB on Asus laptop, c Nov 2015

Expected behavior:

Expected trackpad to work

Actual behavior:

Trackpad ignored, mouse pointer stuck in centre of screen - did not move between X starting and reboot

General notes:

Workaround:
use Tab to select fields and shift-tab to go back to previous field.
keyboard worked OK.
Reboot when prompted
Trackpad works from first boot onwards

---

Related issues:

NB this is different behaviour to #3784 which reported a Macbook Pro, where neither keyboard nor trackpad worked. At least mine was usable if clunky!

I have been using Qubes since the install and am not sure if the relevant logs will still be available. If someone tells me which log files and how to access them I will be glad to assist further.

Also I am not sure which VM will see my trackpad using lspci: be glad to post the relevant output if I know which one might help.

[lunarthegrey]

Specific model of the Asus laptop might help others troubleshoot as well.

[lunarthegrey]

Specific model of the Asus laptop might help others troubleshoot as well.

[trueriver]

Quite so - that info would help me too ;) Unfortunately I do not know the model name - it a laptop I got second hand. Nor am I sure how to find out. It had been wiped when I got it and a generic version of Win 10 (ie with no apparent Asus software/manuals/etc). Win has been totally replaced by Qubes now, of course. More relevant for this specific point would be to identify the trackpad. I Would be grateful for tips on how to do this, either from within Qubes or from a Mint live disk

…

On Fri, 13 Apr 2018, 18:19 Lunar, ***@***.***> wrote: Specific model of the Asus laptop might help others troubleshoot as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3816 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADFfwyaF5KxuxbRSugcgnCe6hxG3CuOcks5toN4vgaJpZM4TThL-> .

[trueriver]

Quite so - that info would help me too ;) Unfortunately I do not know the model name - it a laptop I got second hand. Nor am I sure how to find out. It had been wiped when I got it and a generic version of Win 10 (ie with no apparent Asus software/manuals/etc). Win has been totally replaced by Qubes now, of course. More relevant for this specific point would be to identify the trackpad. I Would be grateful for tips on how to do this, either from within Qubes or from a Mint live disk

…

On Fri, 13 Apr 2018, 18:19 Lunar, ***@***.***> wrote: Specific model of the Asus laptop might help others troubleshoot as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3816 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADFfwyaF5KxuxbRSugcgnCe6hxG3CuOcks5toN4vgaJpZM4TThL-> .

[marmarek]

Unfortunately I do not know the model name - it a laptop I got second hand.

sudo dmidecode in dom0 might be helpful.

More relevant for this specific point would be to identify the trackpad

See devices linked to psmouse driver: ls /sys/module/psmouse/driver/*/, in each device see uevent file for useful identification.

[marmarek]

Unfortunately I do not know the model name - it a laptop I got second hand.

sudo dmidecode in dom0 might be helpful.

More relevant for this specific point would be to identify the trackpad

See devices linked to psmouse driver: ls /sys/module/psmouse/driver/*/, in each device see uevent file for useful identification.

[pruflyos]

Maybe this is indeed related to: #3784
I found out, that many hid drivers are missing in the squashfs (Anaconda).

[pruflyos]

Maybe this is indeed related to: #3784
I found out, that many hid drivers are missing in the squashfs (Anaconda).

[trueriver]

marmrek suggested I look for uevent files under /sys/module/psmouse/driver/*/ from dom0 in my working Qubes system (where the trackpad is working)

I found a write-only uevent file (mode 200).

Even after a quick chmod 600 uevent bash gives me an Input/Output error on trying to cat or cp from that file. Reverted to chmod 200 uevent after these attempts in case the exact permissions matter.

Is there some special program to read uevent files?

I am deeper into the /sys/ tree than I have ever been before...

[trueriver]

marmrek suggested I look for uevent files under /sys/module/psmouse/driver/*/ from dom0 in my working Qubes system (where the trackpad is working)

I found a write-only uevent file (mode 200).

Even after a quick chmod 600 uevent bash gives me an Input/Output error on trying to cat or cp from that file. Reverted to chmod 200 uevent after these attempts in case the exact permissions matter.

Is there some special program to read uevent files?

I am deeper into the /sys/ tree than I have ever been before...

[trueriver]

From the dmidecode file the BIOS Information tells me the BIOS version is for UX360CA.202 released 17 Feb 2016 (so my laptop is either more recent than suspected, or its previous owner reflashed its BIOS).

The laptop product name is UX360CA version 1.0, manufacturer ASUSTek COMPUTER INC.

And I now have the serial number which I didn't know before... so thanks for the heads up on dmidecode :)

Do feel free to ask if any of the other dmidecode info would help with this bug.

[trueriver]

From the dmidecode file the BIOS Information tells me the BIOS version is for UX360CA.202 released 17 Feb 2016 (so my laptop is either more recent than suspected, or its previous owner reflashed its BIOS).

The laptop product name is UX360CA version 1.0, manufacturer ASUSTek COMPUTER INC.

And I now have the serial number which I didn't know before... so thanks for the heads up on dmidecode :)

Do feel free to ask if any of the other dmidecode info would help with this bug.