Ubuntu
plymouth package

Plymouth seems to kill all tty's on my native resolution

Bug #550104 reported by u-foka on 2010-03-28

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	plymouth (Ubuntu)	Invalid	Undecided	Unassigned
Nominated for Lucid by u-foka

Bug Description

Binary package hint: plymouth

Hy!

I tryed to get plymouth to work on my note's native resolution (1280x800), with the nvidia binary drivers.

I found that if I tune the grub.d/000_header file to set gfxpayload=keep (as suggested somewhere) and set GRUB_GFXMODE=1280x800 in /etc/default/grub then plymouth works as expected on startup... then X loads properly, but when I switch to any tty's I can see only the first line of them at the bottom of the screen (last line), and at shutdown, plymouth uses only that bottom part of the screen (a purple line appears at the bottom in approx 2 terminal lines height)

If I keep the grub settings, but boot without the splash option the tty's working properly on my native resolution..

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Sun Mar 28 10:27:11 2010
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
MachineType: Dell Inc. Vostro1310
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-17-generic root=UUID=3627ba63-f81a-43ac-8e49-846267165266 ro quiet splash vga=792
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcFB:
0 VESA VGA
1 VGA16 VGA
SourcePackage: plymouth
dmi.bios.date: 03/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0G930C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1310:pvrNull:rvnDellInc.:rn0G930C:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1310
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.

Tags:

Revision history for this message

u-foka (ufooka) wrote on 2010-03-28:

BootDmesg.txt Edit (44.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (13.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (15.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (587 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (112.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (240.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Laurie Bradshaw (lauriebradshaw) wrote on 2010-04-03:

I'm seeing exactly the same problem

Revision history for this message

Siegie (siegie) wrote on 2010-04-04:

me too,
And exactly as described here

Revision history for this message

alexeagar (alexeagar) wrote on 2010-05-02:

I'm marking this as a duplicate of Bug #551013 because it's the same underlying problem and the same workaround, which will hopefully be adopted by the Ubuntu developers, fixes the problem. Here's the workaround. http://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-terminal-for-atinvidia-cards-with-proprietaryrestricted-driver/

Revision history for this message

alexeagar (alexeagar) wrote on 2010-05-03:

I reverted the duplicate status change which I made to this bug. This bug may be related to Bug #553854.

Revision history for this message

u-foka (ufooka) wrote on 2010-05-03:

Hy!

This bug is about that I can't easily set up the fb resolution by hand (now I solved it by using uvesafb, as many others), but Bug #553854 is about that ubuntu can't detect and use the right resolution after installing the prop driver... (what I tryed to do by hand)

So solving that may solve this, but not surely, because if ubuntu detects and uses the correct resolution by default, the user may still want to change it for any reason with GRUB_GFXMODE, and gfxpayload=keep, what seems the new default way to do that since grub2. So it should work, besides the correct default!

Revision history for this message

Jon Stumpf (jon-stumpf) wrote on 2010-06-06:

All,

After reading numerous posts on the "ugly purple screen", my fix was the following.

    1) purge all existing nvidia packages (sudo apt-get purge 'nvidia*')
    2) blacklist the free and old proprietary drivers (http://forums.nvidia.com/index.php?showtopic=167422)
    3) install the proprietary driver from the nvidia website (ppa repository didn't have nvidia-glx-195)
    4) Edit /etc/default/grub
        a) Add/update GRUB_GFXMODE to the physical screen resolution, GRUB_GFXMODE=1440x900
        b) Add GRUB_GFXPAYLOAD_LINUX=1440x900
    5) sudo update-grub2
    6) echo "FRAMEBUFFER=y" | sudo tee
    6) sudo update-initramfs -u

4b was the crucial step. Once I added this to /etc/default/grub, default.plymouth worked.

Most of my answers were found in http://ubuntuforums.org/showthread.php?t=1469475.

Revision history for this message

Jon Stumpf (jon-stumpf) wrote on 2010-06-06:

Correction
6) sudo gedit /etc/initramfs-tools/conf.d/splash and add "FRAMEBUFFER=y"
7) sudo update-initramfs -u

Revision history for this message

dino99 (9d9) wrote on 2016-01-23:

That version has died long ago; no more supported

Changed in plymouth (Ubuntu):
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuplymouth package

Plymouth seems to kill all tty's on my native resolution

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
plymouth package