No graphical boot screen since 10.10 (nvidia, plymouth)

Asked by Sven Jacobs

Since upgrading from Lucid to Maverick the graphical boot screen is gone. I now only get the textual boot screen (text theme of plymouth).

The graphics card is a GeForce 6800 Go. I am and have been using the binary/proprietary NVIDIA driver in both Ubuntu versions.

If this is related to Maverick now using KMS (kernel mode settings) then please explain how I get a beautiful boot screen when using the proprietary NVIDIA driver.

Many thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xserver-xorg-video-nv Edit question
Assignee:
No assignee Edit question
Solved by:
delance
Solved:
Last query:
Last reply:
Revision history for this message
delance (olivier-delance) said :
#1

Could you check if you have "quiet splash" at end of boot command line. You can find this information in /boot/grub/grub.cfg.

Revision history for this message
Sven Jacobs (svenjacobs) said :
#2

Yes, I have "quiet splash".

I was not talking about the boot process all in (ASCII) text. It's just that I only see the text "Ubuntu 10.10" with the dots below. I believe this is the text theme of plymouth. Sorry if that wasn't clear.

Revision history for this message
delance (olivier-delance) said :
#3

Me too, I only see text "Ubuntu 10.10" with the dots below.

Revision history for this message
Sven Jacobs (svenjacobs) said :
#4
Revision history for this message
delance (olivier-delance) said :
#5

You talk of Maverick but I see 10.04 on your scree shot.
But what I get in Maverick 10.10 is the same with "Ubuntu 10.10" text.
It's ugly, but doesn't look to be a bug!

Revision history for this message
Sven Jacobs (svenjacobs) said :
#6

This is not a screenshot of my computer! It's just a image I found on the web to demonstrate what I mean. It looks like this except the text of course, which is "Ubuntu 10.10".

I still think it's a bug because it should like the first screenshot.

Revision history for this message
Best delance (olivier-delance) said :
#7

In this case, convert your question into a bug.

Revision history for this message
Sven Jacobs (svenjacobs) said :
#8

Thanks delance, that solved my question.