Keyboard and Mouse Pad not Working

92 views
Skip to first unread message

Ray Joseph

unread,
Oct 3, 2017, 2:42:58 PM10/3/17
to qubes-users
I just installed R3.2 on a Toshiba Satellite. I had been running Debian 9.
I installed to a USB drive with dd after checking signatures.
The installation went fine use the mouse pad and keyboard.

After installation and reboot, I selected defaults and the sign on screen came up. It did not respond to either laptop keyboard or mouse pad. So I plugged in a USB mouse, it worked fine but there was no response to the laptop keyboard. I plugged in a USB keyboard and was able to sign in and navigate around.

I have looked up a variety of issues on laptop keyboards, but those that seem close address files in the /etc folder which Qube doesn't seem to have.

1) How can I pursue the making the laptop keyboard and mouse work?
2) Where can I find a graphic of the Qube folder structure?

Thank you,
Ray

Ray Joseph

unread,
Oct 4, 2017, 7:31:49 AM10/4/17
to qubes-users
After rebooting tow more times, the keyboard and mousepad became functional.

Ray

Ray Joseph

unread,
Oct 21, 2017, 9:06:57 PM10/21/17
to qubes-users
On Wednesday, October 4, 2017 at 6:31:49 AM UTC-5, Ray Joseph wrote:
> After rebooting tow more times, the keyboard and mousepad became functional.
>
> Ray

I have continued experimenting and and ran into to losing the input devices again. A day or so later, the I/O would come back up, and they go away again.

As I am relatively new to Linux, I dumped the journal to file and pulled it into Excel. I tagged those sections where I had not I/O; filtered, color coded, sorted. I could not find a correlation between no I/O and journal entries. Is there another resource I should be looking at?

I have just found that the laptop time/date was off. So I went into the BIOS and set it to UTC. When it booted up, I/O was available. I have rebooted a couple times and I/O has been available each time.

I don't know if this is 'fixed'.

When the I/O was not available, I took pictures of messages during the boot process and transcribed them (partially):
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ 10.108174] systemctl[1]: Failed to start Load Kernel Modules.
OK
OK...
Starting Show Plymouth Boot Screen...
Starting dracut initqueue hook...
11.851549] [drm:intel_dp_link_training-channel_equalization [i915]] *ERROR 5.4 Gbp link rate without HBR2/TPS3 support

After reading the above error, I went back to the journal file and found that 'failed' showed up often in the file when there was no I/O. I will study this further to see if I can get a better idea of what is happening.

BTW, I web searched for the above error and found this error to have occurred in fedora and ubuntu; but those were consistent - they were not intermittent. I never found whether there was a related I/O failure.

If anything changes, I will report it back here.

Ray

Ray Joseph

unread,
Oct 23, 2017, 9:29:17 PM10/23/17
to qubes-users

I compared the output of the screen after a keyboard/touchpad failure and a successful boot. The FAILURE lines are still there:


[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[ 10.108174] systemctl[1]: Failed to start Load Kernel Modules.

The 'OK' lines were still there.

The last three lines were missing:


Starting Show Plymouth Boot Screen...
Starting dracut initqueue hook...
11.851549] [drm:intel_dp_link_training-channel_equalization [i915]] *ERROR
5.4 Gbp link rate without HBR2/TPS3 support

Ray

Reply all
Reply to author
Forward
0 new messages