Keyboard, Monitor, Touchscreen stopped working 20.04LTS

Asked by Bruce Toal

All of a sudden my monitor/touscreen that attaches via hdmi and usb (for touchscreen), my keyboard, and my mouse stopped working. I can still logon via ssh and vnc. When I use vcn, the monitor comes on and displys just fine (replicating vnc screen). Neither USB or Bluetooth keyboards or mice work. Also, when I click on the "Command Term" icon via vnc, nothing happens.

I tried sudo apt update and upgrade which did bring some packages, but no improvement on my monitor/Touchscreen/Mouse/keyboard.

I'd hate to go back to a backup a couple of months ago....

Any thoughts?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Does the system have a make and model?
Which version of Ubuntu?
Do you have the latest BIOS?
Is this a dual boot system?

Revision history for this message
Bruce Toal (btoal675) said :
#2

The hardware is an UDOO X86 Ultra II (https://shop.udoo.org/en/udoo-x86-ii-ultra.html)

The rusults from cat /etc/os-release:

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"

The bios is the latest.

It is indeed dual boot.

More info:

My touchscreen monitor (GeChic 1306H) that connects vis hdmi and usb (for touchscreen), my Mouse and Keyboard (usb and/or Bluetooth connected), stopped responding yesterday. Maybe there was an auto update overnight.

I can still logon via ssh and vnc. VNC usage causes the screen to come on and mirrors my vnc screen. Keyboard and monitor both work during grub bootup and if I choose the Windows10 dual boot, everything functions perfectly. Some info:

lsusb:

Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 8087:0aa7 Intel Corp.
Bus 001 Device 008: ID 8087:0ab6 Intel Corp. UDOO X86
Bus 001 Device 011: ID 0403:d9aa Future Technology Devices International, Ltd Actisense NGT-1 NMEA2000 PC Interface
Bus 001 Device 010: ID 258a:0001 ILITEK Multi-Touch-V3004
Bus 001 Device 009: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 002: ID 222a:0088 ILITEK Multi-Touch-V3004
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
For some reson the usb keyboard lists as one of the ILITEK Multi-Touch-V3004 entries.

Bluetooth recognizes a bluetooth keyboard and mouse:

$ bluetoothctl
Agent registered
[CHG] Controller 30:E3:7A:8D:54:45 Pairable: yes
[CHG] Device F0:65:DD:A8:FA:97 Connected: yes
[Logitech K810]# list
Controller 30:E3:7A:8D:54:45 udoo [default]
[Logitech K810]# quit
$ bluetoothctl
Agent registered
[CHG] Controller 30:E3:7A:8D:54:45 Pairable: yes
[HP Bluetooth Mouse Z5000]#
I can access the Settings app via VNC and have looked around but didn't see anything I could change.

One thing I cannot do via VNC is when I click on the Terminal icon, it displays "Terminal" in text at the very top next to activities with a spinning circle for about 5 seconds, then disappears with no terminal window opened. I have been able to do this in the past.

My last backup is from a month ago, and as luck would have it, I have installed new python packages (pip) and did not keep good track, so before I bite the bullet and do the older restore, I am hoping that some wisodm from the group might give me a silver bullet!

My hardware is an UDOO x86 Ultra II with an sd card, emmc, and m.2 dirve (which is where the dual boot partitions live). Network is wifi, not using ethernet.

Revision history for this message
Manfred Hampl (m-hampl) said :
#3

"It is indeed dual boot."

What is the other operating system?
How do you select the system to boot?
When you switch on the system, do you see anything on screen (before Ubuntu starts and everything is dead again)?

Revision history for this message
Bruce Toal (btoal675) said :
#4

Windows 10.

The grub dual boot comes up to allow OS selection and the keyboard works fine allowing me to navigate the grub choices. if Windows 10 is selected, everything works fine (keyboard, mouse, Bluetooth keyboard, Bluetooth mouse, and touchscreen).

This makes me believe that something in Ubuntu is broken/corrupted related to usb keyboard, usb touchscreen, Bluetooth keyboard, Bluetooth mouse. Monitor seems to function fine, but screen saver turns it off and no way to wake it up with keyboard/mouse (vnc session wakes it up).

Revision history for this message
Manfred Hampl (m-hampl) said (last edit ):
#5

For me this does not look like a problem just for mouse and keyboard, but a crash that goes deeper.

Can you try some options form the "advanced" menu in grub, like an older kernel, or root command prompt, or failsafe mode?
Does keyboard and display work then?

Revision history for this message
Bruce Toal (btoal675) said :
#6

I did try an older kernel(recovered), but same problem. I can get a root command prompt in grub advanced. I have not tried failsafe yet. Will try later today.

Thanks,

Bruce

Can you help with this problem?

Provide an answer of your own, or ask Bruce Toal for more information if necessary.

To post a message you must log in.