Recently, after upgrading a machine from 12.04 to 14.04 I noticed that neither keyboard nor network would work, making it rather hard to resolve the situation.
Upon further investigation, it turned out that this was because the linux-image-extra package was missing, and that 14.04 has some rather critical kernel modules, such as usbhid (keyboard and mouse) and r8169 (my network card).
Please make sure in the future that the basic necessities to interact with a system are in linux-image-generic, rather than extra.
root@hitchhiker:~# lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
root@hitchhiker:~# apt-cache policy linux-image-generic
linux-image-generic:
Installed: 3.13.0.71.77
Candidate: 3.13.0.71.77
Version table:
*** 3.13.0.71.77 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
3.13.0.24.28 0
500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
What I expected to happen:
- After an upgrade, I expect the computer to react when I enter keys, move the mouse, or attempt to connect to it over the network
What happened instead
- the system was completely unreactive, and needed a boot from a live CD to revive it again
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: alain 20052 F.... pulseaudio
/dev/snd/controlC0: alain 20052 F.... pulseaudio
/dev/snd/controlC1: alain 20052 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=c38c446b-65ae-46d8-8a18-be3d0ec158ba
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic root=UUID=e3f4a5e0-198c-44c3-82dd-529645435d71 ro quiet splash nomodeset console=tty0 libata.force=nosrst nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
RelatedPackageVersions:
linux-restricted-modules-3.13.0-71-generic N/A
linux-backports-modules-3.13.0-71-generic N/A
linux-firmware 1.127.19
RfKill: Error: [Errno 2] No such file or directory
StagingDrivers: keucr
Tags: trusty staging
Uname: Linux 3.13.0-71-generic x86_64
UpgradeStatus: Upgraded to trusty on 2015-08-26 (101 days ago)
UserGroups: adm admin audio cdrom cvs dialout dip disk floppy kqemu kvm libvirtd lpadmin netdev plugdev powerdev sbuild scanner video voice
WpaSupplicantLog:
_MarkForUpload: True
dmi.bios.date: 02/04/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 5001
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision5001:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1523125
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.