It turns out to be problem on my side, though I don't know whether or how I caused it as I'm not aware I was ever digging in booting stuff. This is log of my today's dpkg install|purge actions:
18:32:19 install linux-image-3.18.0-031800rc7-generic:i386 <none> 3.18.0-031800rc7.201411302035 Here I wrote comment #19, that the newest kernel does not boot, but learned I installed only one pkg out of three. Here I am making some space on a tight /boot partition: 19:34:34 purge linux-image-3.18.0-031800rc7-generic:i386 3.18.0-031800rc7.201411302035 <none> 19:35:34 purge linux-image-3.13.0-36-generic:i386 3.13.0-36.63 <none> 19:35:39 purge linux-image-3.13.0-37-generic:i386 3.13.0-37.64 <none> 19:36:40 purge linux-image-3.13.0-40-generic:i386 3.13.0-40.69 <none> Fully installing kernels for bisection as Joseph asked + the newest one again: 19:37:32 install linux-image-3.13.11-03131105-generic:i386 <none> 3.13.11-03131105.201407181735 19:37:41 install linux-image-3.13.11-03131106-generic:i386 <none> 3.13.11-03131106.201408131735 19:37:51 install linux-image-3.13.11-03131107-generic:i386 <none> 3.13.11-03131107.201409181736 19:44:14 install linux-image-3.18.0-031800rc7-generic:i386 <none> 3.18.0-031800rc7.201411302035 Discovering not only NONE of them boot (all fall into initramfs prompt), but my fallback kernel 3.13.0-34 (that I didn't touch today) start to run into PANIC, blinking Caps LED, power off-on needed. Took a panic screenshot. Able to boot in Recovery mode as always, I removed all tested kernels and installed the newest distro one again. 20:09:06 purge linux-image-3.13.11-03131105-generic:i386 3.13.11-03131105.201407181735 <none> 20:09:11 purge linux-image-3.13.11-03131106-generic:i386 3.13.11-03131106.201408131735 <none> 20:09:17 purge linux-image-3.13.11-03131107-generic:i386 3.13.11-03131107.201409181736 <none> 20:09:23 purge linux-image-3.18.0-031800rc7-generic:i386 3.18.0-031800rc7.201411302035 <none> 20:09:23 install linux-image-3.13.0-40-generic:i386 <none> 3.13.0-40.69 This leaves me with the panicking ver. -34 and (initramfs)-ing ver. -40. Then I started to experiment as I thought possible errors might be hidden from me. So I picked -40 in GRUB screen, chose to edit commands and removed 'quiet' and 'splash' words from line: linux /vmlinuz-3.13.0-40-generic root=/dev/mapper/xubuntu-root ro quiet splash $vt_handoff I was quickly asked for the LUKS passphrase in text mode, then the system went up and all appears to work. I have no idea what caused the problem. Luckily I have at least my system back. Attaching my /boot/grub/grub.cfg just for the record. Sorry for unintentionally leading the thoughts the wrong way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397321 Title: All images beyond 3.13.0-34-generic don't boot Status in linux package in Ubuntu: Incomplete Bug description: The linux-image-3.13.0-34-generic is the last kernel that (months ago) smoothly booted my Dell Latitude E6530 laptop with LUKS encrypted SSD. Usually it was asking for LUKS passphrase in blue graphical screen of Xubuntu. All kernels since then just show the usual BIOS "DELL" in circle splash, then 1 minute black screen and then BusyBox, ... (initramfs) _ I'm not aware of doing anything to cause the problem like changing booting, upgrading ubuntu release etc. Today I discovered that the current linux-image-3.13.0-40-generic boots in Recovery mode, asking for passphrase in text mode. Then I can resume normal boot in text dialog and almost all is up. But the xrandr does not work as well as monitor switching etc. Will return to the old -34 kernel. I asked in the local Linux group and other user reports the same, he didn't resolve the problem as well. Attaching the apport report. Thanks for hope. --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2012-11-27 (731 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) MachineType: Dell Inc. Latitude E6530 Package: linux (not installed) ProcEnviron: LANGUAGE=en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic root=/dev/mapper/xubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: trusty Uname: Linux 3.13.0-34-generic i686 UpgradeStatus: Upgraded to trusty on 2014-06-30 (151 days ago) UserGroups: audio dip plugdev pulse pulse-access video WifiSyslog: _MarkForUpload: True dmi.bios.date: 06/20/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.asset.tag: TUTTLE-LBC dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: TUTTLE-LBC dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd06/20/2014:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
