plymouth: after installing proprietary nvidia driver, splash screen displays in low color/low resolution mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Plymouth |
New
|
Undecided
|
Unassigned | ||
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: plymouth
While using the 'nouveau' driver during live CD installation, or after installation, plymouth displays the very pretty rebranded ubuntu logo at my native resolution, and supports a clean transition into the gdm logon screen.
As soon as I install the proprietary NVIDIA driver (I only tested with "(version current) [Recommended]", this is 190 or 195, I believe, I'm sure the logs will indicate), plymouth displays the Ubuntu logo in what appears to be a 256-color mode, the resolution appears to be 640x480.
I'm not sure how to troubleshoot this further, so if this isn't immediately clear or a duplicate, you may need to provide detailed instructions if you need additional information from me.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.1-4
ProcVersionSign
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Apr 2 00:54:54 2010
DefaultPlymouth: /lib/plymouth/
EcryptfsInUse: Yes
InstallationMedia:
MachineType: MSI MS-7586
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcFB: 0 VGA16 VGA
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
dmi.bios.date: 07/28/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.0
dmi.board.
dmi.board.name: P55-CD53 (MS-7586)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7586
dmi.product.
dmi.sys.vendor: MSI
Changed in plymouth (Ubuntu): | |
status: | New → Confirmed |
I have the same experience and know at least 3 people who encountered the same thing, we all have different hardware.
The work around found is either editing the config file myself or use startup-manager to patch the boot resolution.
But I definitely think this should be patched.