#12: yes this is true, but does not explain why this leads to "blank
console" using the ubuntu supplied kernel and not using one self
compiled from plain vanilla sources. I've tested since: 3.12.8,
3.13.0-rc8 and 3.13. All show the same result: working console at
expected 800x600.
The ubuntu supplied kernel does not show a working console: only black
blank screen. It does not matter if within VMware, VirtualBox or on real
hardware -- it is all the same: console working if 640x480 but not if
set to 800x600 (or even higher -- I just do not set VMs to use higher
resolutions because my monitor isn't large enough for more).
Even the working kernel show this conflict -- IMHO it isn't the cause
Ubuntu supplied kernels do not work. I've tired to compile an Ubuntu
supplied kernel, but failed miserably (I gave up, because I *can*
compile plain vanilla ones -- why should I crop with applied patches?).
Within the fb-subsystem there are differences in kernel compile options.
Ubuntu kernels use a slightly different setup then I. I'd expect to find
the source of this problem there.
** Also affects: linux (Debian)
Importance: Undecided
Status: New
** Also affects: linux (Fedora)
Importance: Undecided
Status: New
--
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/1270656
Title:
Ubuntu 14.04 boots to blank console
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux” package in Debian:
New
Status in “linux” package in Fedora:
New
Bug description:
Ubuntu 14.04 as of 22:00 o'Clock Jan, 19th 2014 boots into blank console.
Ctrl-Alt-F{1..6} does nothing or all consoles are blank, but "ps axf" shows
/sbin/getty running on tty{1..6}:
# ps axf | grep tty
880 tty4 Ss+ 0:00 /sbin/getty -8 38400 tty4
885 tty5 Ss+ 0:00 /sbin/getty -8 38400 tty5
890 tty2 Ss+ 0:00 /sbin/getty -8 38400 tty2
891 tty3 Ss+ 0:00 /sbin/getty -8 38400 tty3
893 tty6 Ss+ 0:00 /sbin/getty -8 38400 tty6
4290 pts/1 S+ 0:00 \_ grep --color=auto tty
1093 tty1 Ss+ 0:00 /sbin/getty -8 38400 tty1
Removing deprecated "vga=768" from kernel commandline => doesn't boot into
800x600, keeps 640x480
Settings
GRUB_GFXMODE=800x600
GRUB_GFXPAYLOAD=800x600
are ignored.
Grub boots up with 800x600, switches back to 640x480 (setting
GRUB_GFXPAYLOAD to "keep" it is the same) kernel doesn't switch back
to 800x600.
Adding deprecated "vga=768" back in:
Grub boots up with 800x600, switches back to 640x480, kernel switches back to
800x600, but doesn't use this console. No output at all. Keys are accepted (you
can login, but you'll have to guess what is going on on the screen).
Exactly the same error is found with debian. Switching to a self
compiled kernel solves this error. Looks a lot like some necessary
stuff for console resolution switching is missing in the debian
-/ubuntu-kernels.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: util-linux 2.20.1-5.1ubuntu13
ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
Uname: Linux 3.13.0-4-generic x86_64
ApportVersion: 2.13.1-0ubuntu1
Architecture: amd64
Date: Mon Jan 20 00:20:36 2014
InstallationDate: Installed on 2012-12-12 (403 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release
amd64 (20120817.3)
ProcEnviron:
TERM=screen-bce
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2013-02-11 (342 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1270656/+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
