after starting ubuntu 16.10 -- no keyboard, no mouse

Bug #1630245 reported by Thomas Schweikle
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Yakkety
Won't Fix
Medium
Unassigned

Bug Description

After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Tue Oct 4 15:27:52 2016
InstallationDate: Installed on 2012-12-12 (1391 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

Revision history for this message
Thomas Schweikle (tps) wrote :
Martin Pitt (pitti)
affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Thomas Schweikle (tps)
tags: added: kernel-bug-exists-upstream
Revision history for this message
Thomas Schweikle (tps) wrote :

I've added kernel-bug-exists-upstream since this bug is in the latest upstream kernel, linux-image-4.8.0-17-generic, present.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you see if this issue exists in the following two kernels?

v4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
v4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/

Revision history for this message
Darius Davis (darius-vmware) wrote :

This is most likely the same issue reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630774

To verify, see if the guest OS kernel command-line option "modprobe.blacklist=intel_powerclamp" resolves the problem.

Revision history for this message
Thomas Schweikle (tps) wrote :

The bug exists in v4.7 final as in v4.8-rc1 -- as long as I use the Ubuntu kernels. compiling plain vanilla kernels seem to not have this bug (taking configuration from Ubuntu).

I tried to add modeprobe.blacklist=intel_powerclamp" without any effect: same as before -- no keyboard, no mouse.

Revision history for this message
Thomas Schweikle (tps) wrote :

Should have written modprobe.blacklist=intel_powerclamp -- this works. The systems now boot with kernel v4.7 final, v4.8-rc1 and the default kernel installed.

But ssh does not get started as before. Upgrading will make you loose connection to an headless server (tried on VMware, confirmed on real hardware).

Revision history for this message
Thomas Schweikle (tps) wrote :

And what a mess: after about 10 minutes you'll be unable to type anything on consoles. All keyboard events are ignored, as are mouse events!

The systems boot thrugh, start networking as expected, but then cancel networking.

Revision history for this message
Thomas Schweikle (tps) wrote :

And it is not guarantied systems boot through -- about every fifth boot fails. Last printed line on screen: "Reached target multi user system". No keyboard, no mouse, no network. I have to reset VM as I have to reset real Hardware!

Revision history for this message
Thomas Schweikle (tps) wrote :

Have a look at CentOS Mainline-kernels found at "http://elrepo.org/linux/kernel/el7/" these work even with ubuntu!

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Can you test the following kernels and report back? We are looking for the first kernel version that exhibits this bug:

4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/

Thanks in advance!

Revision history for this message
Thomas Schweikle (tps) wrote :

I've tested these now (quite difficult to push them into an image not running self contained ...):

4.5 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ -- seems to work: booting is ok, but no keyboard, no mouse. Unsure if keyboard and mouse are available for short, but the cursor blinks behind login, then jumps to blink under the "l" or login. At least once I was able to type "root", before the cursor changed position. Afterwards I could not enter any additional key. The mouse was dead either.

4.6 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ -- seems to hang without "modprobe.balcklist=intel_powerclamp". With it boots to prompt, but looses keyboard and mouse short after the prompt is shown. The cursor jumps to the "l" of login at that point. It is a few seconds. I was able to login once. The system is then accessible. sshd ist started in such a case (it is not, if you cant manage to login).

I've tried the latest 4.4 kernel from 16.04.1 -- this one works.
I converted CentOS kernels from elrepo using alien. They all worked:
4.4.x (-lt)
4.7.x (-ml)
4.8.x (-ml)

Revision history for this message
Thomas Schweikle (tps) wrote :

Was to fast -- non of these kernels work! They'll boot to login, but leaving the system alone for some time -> no keyboard, no mouse. Looks like these are started by systemd, but then terminated again. Maybe it's two different errors one being solved by changing kernels, one within system startup ...?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you give 4.5-rc1 a test? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc1-wily/

Revision history for this message
Thomas Schweikle (tps) wrote :

This kernel does not work either. Are you sure it is the kernel? I'd say it is systemd not doing what is expected. ALL kernels you gave me to test WILL work together with Ubuntu 16.04.1 LTS!!

ALL WORK. None of them works with Ubuntu 16.10!!

Revision history for this message
Thomas Schweikle (tps) wrote :

I've tried now:
With Ubuntu 16.04.1 LTS:
- Plain vanilla kernels 4.1.x, 4.4.x, 4.7.10, 4.8.x
- Ubuntu-Kernels: 4.5-rc1, 4.5-final, 4.6-final
- fedora mainline kernels (only took kernel-config, compiled kernel myself)
  Result: keyboard, mouse working as expected with all kernels, except
          4.8.6 -- maybe there was a missing configuration option with
                   this kernel. I did not dig into it.

With Ubuntu 16.10:
- Plain vanilla kernels 4.1.x, 4.4.x, 4.7.10, 4.8.x
- Ubuntu-Kernels: 4.5-rc1, 4.5-final, 4.6-final
- Fedora mainline kernels (compiled using Ubuntu 16.04.1 LTS)
  Result: no keyboard, no mouse for all kernels. But to be exact:
  Boot. Wait for Login prompt. For a short time the cursor is
  blinking behind "login:". While the cursor is blinking there, you
  can type! If you are fast, you may even press return, and
  "Password:" pops up. If you have a short password you may now
  be able to type this password and log in. In most cases at some
  point the cursor just vanishes and no further keypress is accepted,
  including CTRL-ALT-DEL. You are locked out.

  This is for all kernels I tested. It does not depend on some special kernel.

With the help of SystemRescueCD I've booted up and analyzed the logs written by systemd: Systemd starts consoles. Then, after starting some further parts of the system, terminates consoles. I could not find any console starts afterwards. I'd expect systemd to restart any terminated console for as long as systemd runs. This does not happen. Systemd is configured to restart consoles, but it does not do it. I was not able to find out why.
Networking is started but it seems not to establish network connections until users log in. In tune sshd never starts, because network isn't started at all. If you manage to login typing really fast, while the cursor blinks behind "login:" networking will start! You may be locked out at consoles, because no keypresses are accepted any more, but in case you managed to login, NetworkManager starts networking for the logged in user and in tune sshd is started and you may then login remote.

Revision history for this message
Thomas Schweikle (tps) wrote :

Next I've tried to install 16.10 without upgrading from 16.04.1 LTS. Install went fine, but rebooting at the end gave the same result: short time cursor blinking behind 'login:'. Within this time keyboard works. As soon, as the cursor vanishes, keyboard is dead.

I've tried other kernel too, but nothing changed.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this bug still occur after applying the latest updates?

Changed in linux (Ubuntu Yakkety):
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Mentis (mentis-by) wrote :

I have similar problem with 16.04.
I've tried following kernels
4.4.0-63-generic
4.8.0-36-generic

The only kernel that works is:
4.9.0-040900-generic which I've installed long time ago

Revision history for this message
Mentis (mentis-by) wrote :

I can provide whatever is needed for investigation.

Revision history for this message
Philipp Ludwig (philipp.ludwig) wrote :

I can confirm this bug.

Using 16.04 everything worked fine; after upgrading to 16.10, mouse and keyboard stopped working.

Revision history for this message
Philipp Ludwig (philipp.ludwig) wrote :

I should probably mention that the keyboard works fine in recovery mode, so I suspect it has something to do with X.

Revision history for this message
Philipp Ludwig (philipp.ludwig) wrote :

I fixed the problem by installing xserver-xorg-input-all.

Since this pulls in xserver-xorg-input-evdev, I suspect that this was the problem, as this package was not installed. It must have been somehow uninstalled during the upgrade.

Revision history for this message
Antonio DC (eelie) wrote :

hello, have exact same problem. Upgraded to 16.10 from a working 16.04 and now when 16.10 boots up I'm I cant login because the mouse and keyboard do not work. It connects to WiFi without issues.

How could I install the xserver-xorg-input-all without a working keyboard/mouse?

The keyboard works when I go into the advanced menu options. I'm still a novice user of Ubuntu any instructions would help!!

thank you

Revision history for this message
Philipp Ludwig (philipp.ludwig) wrote :

From the top of my head:

1) In grub, select Advanced options, then recovery mode
2) Select "Drop to root shell"
3) Press Enter to confirm
4) The filesystem is mounted read-only at this point, so remount it: mount -o rw,remount /
5) Install the needed package: apt install xserver-xorg-input-all
6) Press Ctrl+D to leave the root shell.
7) Select resume boot from the menu.

Here are some more information regarding the recovery mode: https://wiki.ubuntu.com/RecoveryMode

Revision history for this message
Antonio DC (eelie) wrote :

hello thanks for your help! did your instructions above but issue still persists. There are messages about dependencies after I complete step 5 above.

I attach a pic of the screen.

Revision history for this message
Daniel Gauthier (gaud) wrote :

is this fixed in ubuntu 17.04 ?

Revision history for this message
Jaredh (thejayroh) wrote :

I had a very similar problem when I upgraded my virtual machine to Ubuntu 16.10. My mouse and keyboard worked fine until I upgraded to 16.10. The virtual machine would boot just fine, but I had no cursor and no ability to click or type anything. My mouse was being captured by the VM, but not working at all. Well I did realize I had the ability to hold shift at boot to bring up the GRUB menu, so the virtual box was working fine! I figured the issue must be with Xorg. I was able to bring up a root shell and uninstall Xorg. Apt was having issues updating packages since it could not resolve name servers. This somehow caused Xorg to not come up at boot, which is when I also confirmed that bash was also working fine.

TL;DR: Uninstalling and reinstalling Xorg has fixed my issue.

Revision history for this message
leevanj (leevanjackson) wrote :

Had the same issue after upgrade from 16.04 - 16.10,
no response from keyboard but trackpad still worked.

I went software updater - which had software to upgrade,
reported it could only do a partial upgrade,
but this included xorg and the packages mentioned above.
let it run. reboot.

keyboard and mouse now work.

Revision history for this message
paulfmorillo (paulfmorillo) wrote :

My problem is that from the recover mode the http site are not reachable, I can pig anything but I cannot ping any repository when I do the update I got this error
 my options on GNU grub ubuntu, with Linux 4.8.0.53-generic (recovery mode) I tried and also I tried
ubuntu, with Linux 4.8.0.52
then I have to enable network which makes the mount
then I go to the drop to root shell prompt
enter apt install xserver-xorg-input-all
it says 1 upgrade, 6 nwely installed, 3 to remove then try to conect
then:
Err:1 http://us.archive.ubuntu.com/ubuntu ...... could not resolved I cannot ping this from there but I can pig 8.8.8.8 (wireless wont work) Ethernet pings just fine.
I do not want to lose my data and I do not know if a fresh reinstaled from CD will fix it.
Any Ideas?

Revision history for this message
Andy Whitcroft (apw) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Yakkety):
status: Incomplete → Won't Fix
Revision history for this message
Dejan (dejan-rodiger) wrote :

Hi, my Ubuntu 16.04 can install xserver-xorg-input-all and laptop keyboard and mouse are not working. I hope this will be fixed in new kernel...

sudo apt-get install xserver-xorg-input-all
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-input-all : Depends: xserver-xorg-input-vmmouse but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
➜ ~

sudo apt-get install xserver-xorg-input-vmmouse
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xserver-xorg-input-vmmouse : Depends: xorg-input-abi-22
                              Depends: xserver-xorg-core (>= 2:1.17.99.902)
E: Unable to correct problems, you have held broken packages.

Revision history for this message
Dejan (dejan-rodiger) wrote :

Hi,

I have encrypted disks and at the start of boot, I need to enter passwords.
With Kernel 4.10.0-32-generic I can enter password using only my USB (logitech wireless) keyboard and mouse. My laptop keyboard and touchpad does not work. It works only in BIOS.
I tried to install kernel 4.11.0-14 and with this, even the USB keyboard doesn't work when I have to enter disk passwords during boot.
xserver-xorg-input-all requires xserver-xorg-core. If I install this it will remove lots of things:
sudo apt-get install xserver-xorg-core
[sudo] password for drodiger:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  libxfont2
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  ubuntu-desktop ubuntu-gnome-desktop xorg xserver-xorg-core-hwe-16.04 xserver-xorg-hwe-16.04 xserver-xorg-input-all-hwe-16.04
  xserver-xorg-input-evdev-hwe-16.04 xserver-xorg-input-synaptics-hwe-16.04 xserver-xorg-input-wacom-hwe-16.04 xserver-xorg-video-all-hwe-16.04
  xserver-xorg-video-amdgpu-hwe-16.04 xserver-xorg-video-ati-hwe-16.04 xserver-xorg-video-fbdev-hwe-16.04 xserver-xorg-video-intel-hwe-16.04
  xserver-xorg-video-nouveau-hwe-16.04 xserver-xorg-video-qxl-hwe-16.04 xserver-xorg-video-radeon-hwe-16.04 xserver-xorg-video-vesa-hwe-16.04
  xserver-xorg-video-vmware-hwe-16.04
The following NEW packages will be installed:
  xserver-xorg-core
0 upgraded, 1 newly installed, 19 to remove and 0 not upgraded.
Need to get 1347 kB of archives.
After this operation, 5662 kB disk space will be freed.
Do you want to continue? [Y/n]

So, I am not sure this is the right thing to do?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

@Dejan,

File a new bug report. Yours is missing keyboard driver in initramfs.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Felix Moreno (info-justdust) wrote :

It ahppened to me in ubuntu 16.04 after some upgades.... trying to update virutal box and a vm was running.... that's the only one thing i can say.... trying sudo apt install xserver-xorg-input-all

Revision history for this message
Luis Guillermo Quevedo (cruciatus) wrote :

I have this bug in 16.04 xenial.
Last week I acepted a sys update, current. At next day I return to work boot ... success, wrote my user password, session started, seems correct, open netbeans ide to start coding a proyect,...
surprice: no keyboard, until now.
I, test almost all forum's suggetions, no success.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.