As far as I remember we changed CONFIG_DRM_VMWGFX_FBCON to 'y ' now. Generally 
it is getting more complicated nowadays. Grub2 initializes some framebuffer 
graphics mode (unless console mode is enforced in /etc/default/grub), hands 
this fb over to plymouth and that hands things over to X. And somewhere between 
grub and plymouth starting, the kernel may start a gfx device specific modeset 
driver which may have its own fb driver. Many opportunities for things to go 
wrong. Btw, I think I mentioned it before but the vga= argument may be becoming 
more a problem than helping. Grub sets a gfx mode already and that is kept if 
no modeset driver is not changing it. And all newer modeset drivers use video= 
for specifying the preferred resolution. (like video=1280x800@32). But in 
theory that should not be necessary at all when the gfx mode is set ok by grub.
Anyway, I tend to declare this bug as "fixed" and have people with other gfx 
cards/drivers open individual bug reports. Mixing things in one single report 
will only cause confusion.

-- 
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

Reply via email to