vga=791 kernel line option breaks tty consoles

Architecture: amd64
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=468553ea-c737-4d2a-859c-9b0720c89d1a
MachineType: To Be Filled By O.E.M. S37S
NonfreeKernelModules: nvidia
Package: linux-meta (not installed)
ProcCmdLine: root=UUID=a8aa4adb-b3e6-4e1d-b4ad-e6cd704788b2 ro verbose
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
RelatedPackageVersions:

Uname: Linux 2.6.30-10-generic x86_64
UserGroups: adm admin cdrom davfs2 dialout dip fax floppy fuse kvm lpadmin nagios netdev plugdev polkituser sambashare scanner sudo sys syslog tape users video voice www-data
dmi.bios.date: 01/22/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: S37S
dmi.board.vendor: To Be Filled By O.E.M.
dmi.board.version: 1.00
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd01/22/2008:svnToBeFilledByO.E.M.:pnS37S:pvr1.0:rvnToBeFilledByO.E.M.:rnS37S:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvr1.0:
dmi.product.name: S37S
dmi.product.version: 1.0
dmi.sys.vendor: To Be Filled By O.E.M.

same thing with stanza:
kernel /boot/vmlinuz-2.6.30-10-generic root=UUID=a8aa4adb-b3e6-4e1d-b4ad-e6cd704788b2 ro vga=0x360

50% of the times it will fail to get to GDM

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

Architecture: amd64
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Vostro 1500
NonfreeKernelModules: nvidia
Package: nvidia-graphics-drivers-180 (not installed)
ProcCmdLine: root=UUID=d71b9610-9b11-446e-8aff-60b27f13ad94 ro quiet
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-2.16-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu4
 libgl1-mesa-glx 7.5~rc4-1ubuntu2
 libdrm2 2.4.11-0ubuntu1
 xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu5
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu1
Uname: Linux 2.6.31-2-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video www-data
dmi.bios.date: 04/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0WY040
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1500
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.31-2-generic

have a similar problem on
2.6.31-2-generic #17-Ubuntu SMP x86_64 GNU/Linux (Karmic)
I previously followed http://ubuntuforums.org/showthread.php?t=622018
and it worked fine (interpid & jaunty)
with vga=0x0365 in menu.lst.
in karmic I can't see anything but a blinking cursor at the corner in the tty's.
once I removed the vga setting from menu.lst i got my consoles back (not at the best resolution though).

Sam problem here.

As someone mentioned in a dupe of this bug not being able to access tty terminals is a major issue, please resolve this.

No one taking care of this?

My bugreport: https://bugs.launchpad.net/ubuntu/+bug/421117 was marked as a duplicat of this one.

I managed to fix the problem with:
sudo apt-get update
sudo apt-get install nvidia-185-kernel-source

Maybe this will help others here?

As described in my careless post to a duplicate bug report at

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391705/comments/10

this happens to me as well. Acer SK20, Intel 845 graphics so I don't think it's just an nVidia issue.

The following lines from dmesg (attached) are interesting:

[ 3.663897] [drm] Initialized drm 1.1.0 20060810
[ 3.681482] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 3.681491] i915 0000:00:02.0: setting latency timer to 64
[ 3.822499] [drm] fb0: inteldrmfb frame buffer device
[ 3.822515] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 3.834769] Console: switching to colour frame buffer device 80x43
[ 3.907975] render error detected, EIR: 0x00000010
[ 3.907981] [drm:i915_handle_error] *ERROR* EIR stuck: 0x00000010, masking
[ 3.908009] render error detected, EIR: 0x00000010
[ 3.922937] [drm] DAC-5: set mode 640x350 13
[ 4.053962] vesafb: framebuffer at 0xd8000000, mapped to 0xe0680000, using 3072k, total 8000k
[ 4.053968] vesafb: mode is 1024x768x16, linelength=2048, pages=4
[ 4.053971] vesafb: scrolling: redraw
[ 4.053978] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[ 4.054063] fb1: VESA VGA frame buffer device

It looks like the option is not being ignored, but is failing to do what it should.

John Yates,
     Have you tested and verified this against the latest Lucid Alpha? If so, I'd like to get you to run 'apport-collect -p linux 391215' so I can get detailed information on your specific hardware.

Thanks!

-JFo

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

John,
     I take it this option still breaks TTY consoles in Lucid?

Thanks!

-JFo

Oh yes.

What is the goal of using the vga=xxx options at boot? In Lucid, the nvidia driver has kernel mode setting, which should result in a better experience in the virtual terminal than under previous releases. The vga=xxx options should not need to be used in lucid. Please confirm whether the default boot options are sufficient.

If you still need better support under previous releases, please state which ones so we can properly target our solutions.

Thanks

Because this has not been confirmed as an upstream kernel bug, and likely can't be due to the proprietary nvidia module, I am marking this as invalid against the upstream project.

I don't use a graphical boot. I prefer more text on a line.
But whatever.

Hy!

I think this bug is something about the blocklisted fb drivers since I
don't know what version of ubuntu...
before that we used the vga param to get a high resolution terminal, I
personally used it to get usplash work on my native 1280x800 resolution
(nvidia 8400m, if I simply enter the resolution in /etc/usplash.conf
usplash still uses 1024x768).. Since ubuntu blacklisted these drivers, I
removed the blacklisting of vesafb, and added fbcon, vesafb to
/etc/modules (or something simlar I can't clearly remember) but since
karmic, I (and it seems others) can't get that working. On lucid I still
have a low res tty console, and plymouth only uses that text console
with a blue 1 line progress bar at bottom at boot (with or without the
nvidia drivers)... this will change till the release? I need the nouveau
packages installed to get it work? (I will test that soon)

On 02/17/2010 06:05 PM, Chase Douglas wrote:
> Because this has not been confirmed as an upstream kernel bug, and
> likely can't be due to the proprietary nvidia module, I am marking this
> as invalid against the upstream project.
>
> ** Changed in: linux
> Status: Confirmed => Invalid
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Low
>
>

I misspoke when I said nvidia will have kernel mode setting support in Lucid. The nouveau drivers will have KMS, but the proprietary nvidia drivers will not. Thus, the virtual terminal won't look the greatest when using the nvidia drivers.

Is it possible for those still wanting high resolution virtual terminals to use nouveau over nvidia? Nouveau will be the default in Lucid.

Well, maybe that is an acceptable solution if the stability of nouveau
will be good enough, but I had never any problems with the nvidia prop +
vesafb combo, so why I should not use it? no kms... ok... I don't care,
on my lcd screen, the resolution switch smooth and painless anyway...
And many people may prefer that over nouveau even if plymouth can't use that

On 02/17/2010 08:57 PM, Chase Douglas wrote:
> Is it possible for those still wanting high resolution virtual terminals
> to use nouveau over nvidia? Nouveau will be the default in Lucid.
>
>

Hy!

I did some testing around this:
Lucid Beta1 livecd, vga=792: proper 1024x768 console and graphical boot
Lucid up2date install, vga=792: proper 1024x768 console and graphical boot
Lucid Beta1 livecd, vga=865: proper 1280x800 console and graphical boot
Lucid up2date install, vga=865: like without the vga parameter (low res console, and text boot)

I'm listed the loaded modules when the livecd loaded and with the vga parameter it uses vesafb correctly instead of nouveau as expected...

So why can vesafb work on 1280x800 with the livecd, and can't on the installed system?
And why can vesafb work on 1024x768, and can't on 1280x800 on the installed system?

It affects linux 2.6.32-20-generic, too.
I use the nvidia-current driver (195.36.15).

The Kernel command line is:
BOOT_IMAGE=/vmlinuz-2.6.32-20-generic root=UUID=8d28f6d1-0f53-4e68-8694-7c1003cf30e7 ro vga=795 splash quiet quiet splash

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nk 1539 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'CMI8738'/'C-Media CMI8738 (model 55) at 0xd000, irq 18'
   Mixer name : 'CMedia PCI'
   Components : ''
   Controls : 41
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

DistroRelease: Ubuntu 10.04
HibernationDevice: RESUME=UUID=c8ff1644-26e1-49f8-9891-a386bed76850
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 ppp0 no wireless extensions.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-20-generic root=UUID=8d28f6d1-0f53-4e68-8694-7c1003cf30e7 ro splash quiet vga=786 quiet splash
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
Regression: Yes
RelatedPackageVersions: linux-firmware 1.33
Reproducible: Yes
RfKill:

Tags: lucid kconfig regression-potential needs-upstream-testing
Uname: Linux 2.6.32-20-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
WpaSupplicantLog:

dmi.bios.date: 12/21/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: nVidia-nForce
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd12/21/2005:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr:

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

this affects a friend from me on ubuntuusers.de too!

It seems that Lucid have chosen vga16fb per default. vga16fb doesn't support the vga= parameter and ends in broken tty consoles.

So I exchanged vga16fb with vesafb.
I added vga16fb to the blacklist (/etc/modprobe.d/blacklist-framebuffer.conf) and removed vesafb from it.

Furthermore I added fbcon and vesafb to /etc/modules. (I'm not sure if it runs without this modification.)

Alternatively (this works for me with Lucid, Nvidia with grub2) you can edit your grub (sudo gedit /etc/default/grub) file and add the following:

GRUB_GFXMODE=1280x800
GRUB_GFXPAYLOAD_LINUX=1280x800x32

then run:
sudo update-grub

The "keep" borks the terminals for gfxpayload but the GRUB_GFXPAYLOAD_LINUX works well if you specify the resolution. Note this will not work with non-GRUB2 bootloaders (i.e., GRUB) so you may have to update to GRUB2 if you are running the older grub.

That version is no more supported; please open a new bug report if the actual archive found version also has the same issue.