[Rant]
Deja vu. When Ubuntu first introduced PulseAudio, it was one hell of a plight for the end-user. And now it is Plymouth turn to make life an uphill struggle for user with recent ATI or NVIDIA card and proprietary drivers (as well as people having examination like me >.<). Here is an interesting article by Scott James Remnant on why your expensive card doesn’t play nice with Plymouth in Lucid. I also grow tired and wary of all the copy-n-paste instructions lying on the Internet which are out-dated and untested yet considered as panacea. My most hated one is ‘set gfxpayload=keep’ originated from Arch forum and now spreading like fire. It makes your the Virtual Terminal (VT) useless, ‘keep’ is not the working option in Ubuntu, last and not least, in Lucid, there is a more graceful way to do it. And I hope my guide below will not suffer the same fate as them. It was quite comprehensive after days of manual grinding and testing during exam period.
[Problems/Symptoms/Why-Are-You-Here]
Plymouth splash screen…
- is in low res mode.
- has corrupted graphic
- is decent but can’t switch to virtual terminal or VT is horribly in low res mode
- is decent but the splash screen only appears for a brief 1-2 second ( you are missing the dots moving :P), before that you only see a black/blank screen
[Environment]
Use Synaptic or ‘apt-cache policy ‘ or common-sense to find out.
- GRUB >= 1.98-1ubuntu5
- Plymouth >= 0.8.2-2
- ATI cards with FGLRX >= 8.723.1-0ubuntu3
- NVIDIA cards with nvidia-glx-1*
- A clean without other tweaks to plymouth & grub, please revert them before proceeding. Really, it will not work if you insisted on apply other tweaks. !!! IMPORTANT !!!
- Common-sense and google searching skill
- A bit of risk taking spirit and confidence
[Caveats and Limitations]
I will use the uvesafb to fix all the problems mentioned above but I have to warn you about certain limitations first. They don’t affected me much though (widescreen works on mine). I think problem will come when you want to use solar theme or any complex theme as uvesafb doesn’t have acceleration -> slow. Extract from documentation for uvesafb
uvesafb is a _generic_ driver which supports a wide variety of video cards, but which is ultimately limited by the Video BIOS interface. The most important limitations are:
– Lack of any type of acceleration.
– A strict and limited set of supported video modes. Often the native or most optimal resolution/refresh rate for your setup will not work with uvesafb, simply because the Video BIOS doesn’t support the video mode you want to use. This can be especially painful with widescreen panels, where native video modes don’t have the 4:3 aspect ratio, which is what most BIOS-es are limited to.
– Adjusting the refresh rate is only possible with a VBE 3.0 compliant Video BIOS. Note that many nVidia Video BIOS-es claim to be VBE 3.0 compliant, while they simply ignore any refresh rate settings.
Also, uvesafb replaces vesafb in Ubuntu, in case you are wondering.
[Fix/Workaround]
* uvesafb required v86d package to be installed. Hwinfo package is required for the next step as well.
sudo apt-get install v86d hwinfo
* Find out the supported resolution by using hwinfo.
sudo hwinfo --framebuffer
Sample output :
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
...
Hardware Class: framebuffer
Model: "(C) 1988-2005, ATI Technologies Inc. M92"
Vendor: "(C) 1988-2005, ATI Technologies Inc. "
Device: "M92"
SubVendor: "ATI ATOMBIOS"
...
Mode 0x0321: 640x480 (+2560), 24 bits
Mode 0x0322: 800x600 (+3200), 24 bits
Mode 0x0323: 1024x768 (+4096), 24 bits
Mode 0x03ee: 1366x768 (+1408), 8 bits
Mode 0x03ef: 1366x768 (+2752), 16 bits
Mode 0x03f0: 1366x768 (+5504), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown
* Edit /etc/default/grub to make sure we boot with uvesafb framebuffer. For the mode_option parameter change to your native screen resolution you see from running the above comment (if not just set to 1024×768-24 which is safest. Oh, Netbook user – please exercise some common-sense here) Non relevant lines are omitted for clarity.
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset video=uvesafb:mode_option=1366x768-24,mtrr=3,scroll=ywrap"
...
GRUB_GFXMODE=1366x768
* Edit /etc/initramfs-tools/modules to include uvesafb by adding the following line.
uvesafb mode_option=1366x768-24 mtrr=3 scroll=ywrap
* Force the use of framebuffer:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
* Update and we are done 🙂
sudo update-grub2
sudo update-initramfs -u
* Now reboot and enjoy the high resolution sensation 🙂 (my first reboot hangs, but 2nd time onward it works flawlessly). If it works correctly, you should be able to have moving dots with the splash screen; lesser time of blank screen and much more time with splash screen.
* And contrary to popular belief, my laptop resume and suspend works with uvesafb! 🙂
* Thing you probably will see in dmesg if succeed:
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic-pae root=UUID=44c7c661-1f5e-49e6-a14e-7a35f1ec3f9f ro quiet splash nomodeset video=uvesafb:mode_option=1366x768-24,mtrr=3,scroll=ywrap
[ 6.684235] uvesafb: (C) 1988-2005, ATI Technologies Inc. , M92, 01.00, OEM: ATI ATOMBIOS, VBE v3.0
[ 6.783693] uvesafb: protected mode interface info at c000:a2d4
[ 6.783695] uvesafb: pmi: set display start = c00ca376, set palette = c00ca434
[ 6.783727] uvesafb: VBIOS/hardware supports DDC2 transfers
[ 6.845060] uvesafb: monitor limits: vf = 61 Hz, hf = 48 kHz, clk = 69 MHz
[ 6.845110] uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
[ 6.847159] uvesafb: framebuffer at 0xc0000000, mapped to 0xf8380000, using 8256k, total 16384k
[ 6.854259] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[Other Alternatives]
* Rog131’s ‘Making a low resolution low color plymouth theme’ is an ingenious workaround. Here
* No splash screen but high resolution virutal terminal using EFI framebuffer. Edit /etc/default/grub, remove ‘splash’ option and replace the two entries below with your native resolution. Seriously, this is way better than setting the payload to keep and in 00_header. GRUB_GFXPAYLOAD_LINUX is only available from grub 1.98 in lucid.
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
...
GRUB_GFXMODE=1366x768
GRUB_GFXPAYLOAD_LINUX=1366x768
...
[Last Words]
– Comments are welcome and appreciated.
– Testers are welcome.
– I will try to respond to you ASAP but spare me some thoughts cos the poor guy here is having his final exams at his university life 🙂
That’s work!! ;D Thank’s o a lot.
Really worked: great explanation!
Thanks! 😀
This is the first workaround that actually works for me. It works just fine with the current NVIDIA closed drivers, at 1280×1024-24.
Now I can see Plymouth at it’s full glory, and still get Compiz and 3-D on my desktop.
Hi, I can confirm this works wit my HD 3200 thanks a bunch!
Works Perfect with mobility radeon HD 3450, at 1024×768-24!!
No more low res mode at boot.
Thanks!!
Very good work.
XD
worked great !
nice one!
This works on my machine even though my monitor’s native resolution is not supported. The only downside is the addition of 6 or so seconds to my boot time.
As I mentioned in the caveat, uvesafb has no acceleration. Slowness is expected. Try to set to the resolution and colour bits reported by hwinfo, native one will be the fastest as tested by me. I didn’t experience +6 second, mine was very fast comparable to EFI fb workaround.
Perfect! thanks alot!
Thanks for posting this. Both VT and plymouth are looking lovely now. It added a few seconds to the boot time but I can live with that and another bonus is that it seems to have got rid of many of the flashes I had on start up before.
Thanks alot!!!! 😀
It works! Thanks
Works like a charm – except:
Quite often the computer won’t reboot or shutdown. While this happens, the splash screen is shown infinitely. Pressing Esc – which kills the plymouth splash – doesn’t lead to any additional informations. I have to force a reboot with Alt + Print + B.
System: Clean Kubuntu 10.04 installation with Nvidia GeForce FX 5200 and driver nvidia-173 (formerly called nvidia-glx-173).
Any idea?
Happened to me once only. Yeah, could be great if you can provide some logs 🙂 I am also not discarding the possibilities of recent updates (2-3 updates to plymouth and mountall lately).
Other good piece of news is there seems to be an update in propose repo for plymouth which we can revert back to original config.
[ Alessandro Ghersi ]
* Fix Plymouth logo on 16 bit graphics, LP: #551290
– Merge lib/plymouth/themes/kubuntu-logo/kubuntu-logo.script with Ubuntu
– Use alternate BackgroundTopColor and BackgroundBottomColor when we have only 4bpp
[ Giuseppe Pennisi ]
* Add 16-color images to use when we have only 4bpp
Many thanks mate.
Thanks for your reply.
I don’t have much knowledge of reporting bugs. Consequently I don’t know which logs might be helpful.
It happens virtually every time, trying to reboot or shutdown.
Hmph, I suggest you revert back the changes from this post since the problem occurred every time. And waiting for the update as I pointed out in my previous reply. Prettiness is secondary, but stability is a must.
You also can try other alternatives suggested here in the comment section (1 suggestion so far), if it works for you then good. Though I won’t endorse that method at all, but it is just me.
This happens in lucid regardless of the above fix. In fact I found this page by googling for a solution to the splash screen freeze.
I agree with your rant, don’t release cutting edge features if they’re not properly tested (if at all). Lucid is LTS and it’s completely f**ked.
Seems like we’re being used as guinea pigs here, oh well I guess you get what you pay for 😉
Didnt work for me…but this did:
http://www.webupd8.org/2010/03/how-to-get-plymouth-working-with-nvidia.html#comment-41037671
Not all resolutions work though. Check in grub console by typing “vbeinfo” (without the quotes), which resolutions are supported by your card.
Mate I suggest you start educating yourself with GRUB2. Deprecated things isn’t in my book. And for god sake, stop use set gfx_payload=keep already. I am tired of seeing that thing. And I am sure you didn’t read my rant did you?
i was just trying to help people find alternative solutions in case yours doesnt work for them. linking, you know!?
well, it was a couple of days ago i tried your solution, so sorry for forgetting about your “rant”.
btw, my vc is not “useless”. a bit messy, but still fully functional.
Apologize for losing my coolness. But yes, let me get to my point again. I acknowledge that your vga=XXX thing helps certain users especially grub1 user. But it is because of you are using vga parameter (deprecated anyway aka transitional stuff should be avoided at all cost, they are transitional for a reason. LTS is what we want to achieve here).
Still get your stuff right, because of vga=xxx parameter, you can have a usable VT not set gfxpayload=keep. Unless you can prove me otherwise, for fglrx and ati card (Mobility ATI 4330) as well as nvidia-glx (NVS Quadro 110m) here, all other tweaks just don’t work. And I don’t post crap before testing all the instructions/variances out myself. Like we always do things nowadays, google for solution first, if it fails dig out the manual and documentation and start create a solution ourselves.
Last, I am more than grateful for any extra tips and links here. Just look at my 9.04 pulseaudio post and see the from the comments how many user-fixes links they provided for 9.10 which i can’t figure out how to do at all. They helped porting the instruction to 9.10 so well.
edit: here’s the actual link: http://www.webupd8.org/2010/03/how-to-get-plymouth-working-with-nvidia.html
Thanks Erik
Your post helps me because I could figure it out that I have Grub 1 in my system.
I upgrade Grub and now idyllictux workaround works for me.
Thanks a lot!!!!!!
Hi!
looks like a great thing!
but what i’m asking myself: does this replace the fglrx driver? (i’ve an ati card)
or is this ‘slow’ driver only used at starting up? i don’t want to lose acceleration because of compiz effects. does it matter?
Hi Philipp,
It only affects the starting up sequence. You will not lose any acceleration for desktop effect at all (if you use fglrx). I put ‘nomodeset’ as a parameter in kernel boot parameter as a pre-caution for that already.
Cheers,
oh yeah thats great, thanks!
i made it, its working, im happy, your awesome!
Excellent its works, Thanks a lot, greetings from Mexico
Thank you so much for this post!
Confirmed working on Ubuntu 10.04. Asus N51Vn-A1. Ge Force 240M GT on nvidia 195.36.34 Beta Drivers!!!
Grub’s menu resoltution is still 640×480 though… dont know if that was meant to change
Hi, you can set GRUB resolution by changing this line ONLY in /etc/default/grub
…
GRUB_GFXMODE=
…
Then ‘sudo update-grub2’
Thanks a lot! It worked like a charm – I still don’t believe it!
Greetings from Italy 😉
Great! Thanks a million
It works perfect! Much thanks for this info.
On first boot, splash screen looked like it hanged. But Ctrl+Alt+Del rebooted the system and it’s perfect now.
One thing though. My screen has 1440×900 resolution but hwinfo does not display it.
GRUB_GFXMODE=1440×900 works fine.
But;
video=uvesafb:mode_option=1366×768-24
didn’t worked.
Best resolution hwinfo reported was 1152×864-24 bit and I used it.
Now everything is perfect.
I have Toshiba Satellite P200D-12O with ATI Mobility Radeon HD 2600.
Thanks again.
Hail you man…!!
Really great information…
worked for me as well… 🙂
But after logging in the notification doesn’t have the transparency but a thick border..
Any idea about this…?
Hi, my workaround doesn’t affect desktop effect. So I suggest you to search for information regarding desktop effect and notification. Your xsession-error or Xorg.0.log will be helpful.
That’s work!! 😀
Thank’s o a lot.
Keep Sharing…
it doesn’t wirk for me: nvidia 8200 g. Dmesg :
dmesg | grep vesa
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=a5645330-a1bc-48f7-9062-3d8c2d1b3816 ro quiet splash nomodeset video=uvesafb:mode_option=1280×800-24,mtrr=3,scroll=ywrap
you see: uvesafb is not loaded 😦
well: i regenerate again my initram and now works! very very very good, thank you!
Thanks for this solution! It worked perfectly for me. I tried to douse a bit of the ‘set gfxpayload=keep’ fire by commenting on two of the offending sites with a link to this page.
Thank you so much! I’ve spent hours and hours looking for a fix and yours was spot on.
Thank you for this detailed article!
The described steps work for me. My Hardware setup:
HP Compaq 6830
ATI Mobility Radeon HD 3430 @ 1440×900
But I used the highest available resolution which was reported by hwinfo –framebuffer: 1152×864-24.
Also a switching (back and forth) to the virtual terminals after boot (eg. Strg+Alt+F1) works like a charm with Compiz and displays sexy terminal resolution 🙂
This works on my laptop with a NVidia Geforce Go 7400
However, hwinfo does not list my screen’s native resolution (1280×800).
I’m using 1024×768 instead. Any ideas why?
More annoying is the fact that I get a black screen with only the mouse cursor for a second or two before the wallpaper loads. Is this also a plymouth issue?
(1) A strict and limited set of supported video modes can be used for uvesafb. Often the native or most optimal resolution/refresh rate for your setup will not work with uvesafb, simply because the Video BIOS doesn’t support the video mode you want to use.
(2) It is not a plymouth issue. Quite a common thing for old Nvidia card (my old card was a Nvidia Quadro NVS 110M – aka Geforce Go 7300 happened to have a same problem as yours – I think it is related to desktop effect or gdm transition)
Everyone please log in to Launchpad and let the developers know whether this bug affects you too.
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/551013/+login
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/551013/+affectsmetoo
Also, here is the same solution re-written for Linux beginners. http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-Logo-in-Ubuntu-10-04-140810.shtml
After much hoo-ha, the bug has changed to #553854.
Everyone please log in to Launchpad and let the developers know whether this bug affects you too.
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553854/+login
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/553854/+affectsmetoo
The bug is now #563878.
Thanks man!
tested on radeon x1200
Hi!
It worked for me thanks a lot!
Just one question:
If a real fix will be ever released by Canonical, how can we revert changes made by this workaround?
Do we need to follow the instructions in reverse order?
Sorry if this question is stupid but I’m a newbie.
Thanks
Just reverse the order of instruction basically. Erm you might need to delete this file /etc/initramfs-tools/conf.d/splash , the rest you just remove / reverse them.
[…] here are created for beginners in Linux. No terminal hassle! The first fix was developed by Hoa Nguyen from the Ubuntu community. All credits go to him! All I did was to find a second fix and compile […]
It works perfectly. I have got an ATI Radeon 2400. Thanks for the help. Good luck with your final exams.
bad ass
Thank you.
Also, I heard about efifb, an equivalent to (u)vesafb for EFI.
Is it better, and/or can it be used instead of uvesafb?
It appears that efifb driver is not include in the kernel. There is nothing we can do about it.
Also, once the Plymouth splash is gone, the tty2 console appears (in high-res) and asks me to log in. It hangs there for about 10 seconds (a bit longer than the splash itself!), then a bunch of boot messages are printed very quickly and then KDM appears instantly after. There are flickers between Plymouth -> tty2 and between tty2 -> KDM. Any help?
I only experience it at shutdown (bunch of messages that’s). On boot, i have like solid 1-2second of black screen before KDM. No idea why though.
OS – ubuntu lucid lynx 10.04
in the line u mentioned
* Force the use of framebuffer:
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
is this supposed to be added in any of the files u mentioned ???
i ran it in the terminal after the edits to the files
now my boot screen is small (roughly of font size – 28/30) and is placed near top-left corner.
PS- i use grub1 bcoz i keep installin n removin alpha n beta releases of other linux distros and i find grub1 to get back easier than grub2 in case of a crash 🙂
It create a file at /etc/initramfs-tools/conf.d/splash with the content of ‘FRAMEBUFFER=y’. I haven’t tested with GRUB1 so do it at your own risk.
I don’t know what’s going on, I have no “/etc/default/grub” which I could edit? Anyone?
Are you still using GRUB 1 (legacy) ? Check which package of grub was installed – grub-pc (GRUB 2 which is supported in this guide) or grub-legacy (GRUB1)
[…] up Plymouth (graphical boot) and Virtual Terminals for High-resolution: Tux’s Idyllic Life has a perfect guide that has worked for both my machines with proprietary Nvidia drivers […]
@idyllictux
Just to inform you that the following worked for me, with no further tweaks on a fresh and up to date installation. I have the NVIDIA proprietary drivers installed:
1 – Add the following line to /etc/default/grub:
GRUB_GFXPAYLOAD_LINUX=1280×1024 // or whatever is your native resolution
2 – On the terminal, execute: echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
3 – sudo update-grub
sudo update-initramfs -u
There seems to be no need to use uvesafb. Am I wrong?
What is the output of your ‘cat /proc/fb’ ? Seem like NVIDIA cards can handle that output buffer well (I suspect EFI). I mean good for NVIDIA users. But I aimed for universal solution across ATI/NVIDIA, so i went for uvesafb.
You’re right. The output is:
0 EFI VGA
Aren’t you nvidia user lucky? 😀 Really, if only ATI card and their video bios can be like NVIDIA. Sigh…
Yeah, actually my NVIDIA card was a blessing. 😀 I had an old ATI card, but I switched to NVIDIA when I adopted Linux as my main OS.
I have a Dell Vostro 3500 (Nvidia 310m) and your sugestion worked. I think it’s a lot easier.
But it’s very important to pay atention to the screen resolutions informed by framebuffer and X-server.
My X-server, with Nvidia driver, uses 1366x768x24, but the result of “sudo hwinfo –framebuffer” gives me 1360x768x(8, 16, 24,32). A so little diference that I spent a lot of time to realize that a was typing 1366×768 in GRUB settings and it would never work.
EDIT: My X-server, with Nvidia driver, uses 1366x768x24, but the result of “sudo hwinfo –framebuffer” gives me 1360x760x(8, 16, 24,32)
[…] https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-termin… […]
how can I remove the changes made by this turorial?
It somehow broke my /etc/default/grub
And resulted in this: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/575913
How can I undo this command?
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
thanks
In terminal, ‘sudo rm /etc/initramfs-tools/conf.d/splash’ .
Btw, why the heck this line is not in the GRUB_CMDLINE_LINUX_DEFAULT: “video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap”? In the bug report, it appears as a separate line.
Works fine!!!!!
Thank you that much!!!!
Worked for me without any issues. The first boot it self was fine.
Good job, Thanks.
Hello !
It doesn’t totally work for me. The only problem is that the Kubuntu logo and the animation are not centered on the screen ! I have a part of the logo in the right and the other part on the left.
Help me please ! Thank you !!!
Is there any error in the dmesg log? (dmesg | grep uvesafb)
Also since you are using kubuntu, there is an update recently on kubuntu-default-settings which provides a reasonable 640×480 resolution on default vga16. If nothing works, that’s the best bet.
Hi ! Thank you for helping me.
This is the result of your command (dmesg | grep uvesafb) :
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=316cd63e-6cb4-45bb-ad60-a220197733af ro quiet splash nomodeset video=uvesafb:mode_option=1440×900-24,mtrr=3,scroll=ywrap
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=316cd63e-6cb4-45bb-ad60-a220197733af ro quiet splash nomodeset video=uvesafb:mode_option=1440×900-24,mtrr=3,scroll=ywrap
[ 2.652652] uvesafb: NVIDIA Corporation, G84 Board – e416h10 , Chip Rev , OEM: NVIDIA, VBE v3.0
[ 2.754040] uvesafb: VBIOS/hardware doesn’t support DDC transfers
[ 2.754042] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 2.754351] uvesafb: scrolling: redraw
[ 2.754355] uvesafb: cannot reserve video memory at 0xcd000000
[ 2.754361] uvesafb: probe of uvesafb.0 failed with error -5
________________________________________
I did not understand your second advice : if I put 640×480 instead of my native resolution (1440×900), the logo would be big and crappy ?
From the dmesg log, you are not using uvesafb at all (from the error code -5). Did you use any other tweaks before this?
create /etc/modprobe.d/uvesafb with the following line
options uvesafb mode_option=1440×900-24 mtrr=3 scroll=ywrap
Then run
sudo update-initramfs -u
From the comment section, you can try this user’s method: https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-terminal-for-atinvidia-cards-with-proprietaryrestricted-driver/#comment-481
If not working for you again, request output of your ‘cat /proc/fb’.
Hi ! Thank you for helping me !
This is the result of the command “dmesg | grep uvesafb”.
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=316cd63e-6cb4-45bb-ad60-a220197733af ro quiet splash nomodeset video=uvesafb:mode_option=1440×900-24,mtrr=3,scroll=ywrap
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=316cd63e-6cb4-45bb-ad60-a220197733af ro quiet splash nomodeset video=uvesafb:mode_option=1440×900-24,mtrr=3,scroll=ywrap
[ 2.652652] uvesafb: NVIDIA Corporation, G84 Board – e416h10 , Chip Rev , OEM: NVIDIA, VBE v3.0
[ 2.754040] uvesafb: VBIOS/hardware doesn’t support DDC transfers
[ 2.754042] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 2.754351] uvesafb: scrolling: redraw
[ 2.754355] uvesafb: cannot reserve video memory at 0xcd000000
[ 2.754361] uvesafb: probe of uvesafb.0 failed with error -5
______________________________________________
If I put 640×480 instead of my native resolution, the result would be crappy, no ?
Thank you !
Thanks! It really works!
I have tried this, but no succses. after all instructions done when rebooting I get a black screen with monitors message “Input Not Supported”
hwinfo shows 1920x1200x24 as the highest resolution, but best what I can get is 1280×1024. I do this by adding vga=0x031b to GRUB_CMDLINE_LINUX=. If I add vga mode for 1920×1200 I get it fullscreen but the logo is just plain text. My “cat /prob/fb” shows 0 VESA VGA. I have nvidia 8400GS. I thought could I to the nomodeset trick with the nouveau drivers?
I have provided some photos of my problem in this bug:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/551013
on posts 73,74,75.
Remove vga=0x031b please!
ok I removed. have you any suggestions what can I do to fix it?
here’s mine dmesg:
[ 1.458617] uvesafb: NVIDIA Corporation, G98 Board – 5610002u, Chip Rev , OEM: NVIDIA, VBE v3.0
[ 1.511040] uvesafb: protected mode interface info at c000:c930
[ 1.511043] uvesafb: pmi: set display start = c00cc993, set palette = c00cc9ee
[ 1.511045] uvesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
[ 1.582027] uvesafb: VBIOS/hardware doesn’t support DDC transfers
[ 1.582029] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 1.582265] uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=3584
[ 1.584550] uvesafb: framebuffer at 0xfb000000, mapped to 0xf8100000, using 14336k, total 14336k
[ 1.584553] fb0: VESA VGA frame buffer device
it is with your instructions and 1024×768 res.
Hi, from the dmesg log, it seems uvesafb is loaded and used correctly. However, it seems the videocard is giving a signal the monitor doesn’t like since (if it still doesn’t work for you).
Best is to use a resolution supported by your video bios and your monitor. So does the 1024×768 resolution work fine for you? Hmph maybe even append your refresh rate as well.
Seem like your card and monitor don’t play well with each other, I suggest you google “Input not supported”. This problem does exist even in windows.
1280×1024 also works, but no mather which res I set I get a black vertical line in right or the left of the monitor(depends on resolution) but the logo is centered. and whats the big deal with the vga= mode? I just enter it without uvesafb. and it works the same as with your tutorial. and by the way only changeing the GRUB_GFXMODE= to 1280×1024, 1024×768, 800×600,640×480 or 320×240 I see changes, no need to change uvesafb mode. And maybe is there a way to work the same with nouveau drivers not just with uvesafb?
Erm, this tutorial is for proprietary driver not open-sourced driver. Anyway, have to make a move now, exam in 1 hour time 🙂
[…] for beginners in Linux. There is no need to use the terminal. The first fix was developed by Hoa Nguyen from the Ubuntu community & Softpedia. All credits go to them! All I am doing is passing on the […]
it’s work , thank ^_^
thank you!
it works for me..
but my gdm is now running on tty8..
well, I updated my xorg.conf because there was no hardware only default monitor. I only get 1280x1024x24 as the hihgest res, but also to show it centered I have to change the horizontal position with my monitors built in software while booting. It affects only the plymouth.
I just wanted to ask if I could do something like this with propietary nvidia drivers and nouveau instead of uvesafb: lquiet splash nomodeset video=nouveau:mode….?
Thanks! it ‘s very useful!
Worked like a charm! Cheers!
Hello
My screen’s resolution is 1440×900. I set 1440×900-24 on these files but I get “out of frequency” error while booting? Why?
Uvesafb required supported video bios resolution. Monitor resolution and video bios resolution are kind of different. You can only use the mode available in `sudo hwinfo –framebuffer`. A safest resolution would be 1024×768. Do read the caveats and limitations section of the guide.
doing just this without uvesafb:
GRUB_GFXMODE=1280×1024
GRUB_GFXPAYLOAD_LINUX=1280×1024
I get efifb loading. higher resolutions do not work. hwinfo does not help. I can change the theme it looks quite good but I need 16:9.
I’m giving up on this…
[…] radeon driver I had the same framebuffer conflict. The problem was easily fixed by switching to the uvesafb […]
It works perfect.
Thank you .
Thanks a lot ! .. works fine (and is the only one, that works at all for me on alternate installation (crypted) with nvidia-driver on 1280×1024 ) .
Great !
your “No splash screen but high resolution virutal terminal using EFI framebuffer” solution didn’t work well for me with my ati card until I changed
GRUB_GFXPAYLOAD_LINUX=1366×768
to
GRUB_GFXPAYLOAD_LINUX=1366x768x24
before it would still show the splash screen for a brief sec or two with a really ugly green outline around the ubuntu logo in the splash, and also still had the shutdown splash visible. I did take “splash” out of GRUB_CMDLINE_LINUX_DEFAULT= and even tried “nosplash”. only thing that fixed it was adding the x24. Weird I know…
Well, it kind of worked. I notice a few things compared to how I set it up previously (I had the vga16 and nouveau modules blacklisted), I have an old NV quadro 700 running on old Athlon chip (2200+).
Now I get a lot of messages at 640×480 before it goes to 1280×1024 then shows the splash then goes to my login screen. Also, my VT is no longer green text with the cool color coding in PICO, etc. It is white on black with old school color ls only. Also, the nvidia X (non-free module loaded) is at 1280x1024x24 but the fb is only 16. Do I need to be running nouveau here? I think I had a uvesa 24 bit fb which is why I had the other color enhancements but am unsure. Why is there a difference between what vbeinfo and hwinfo report as modes? Both list the same mode values, but with different numbers. My mode is 1280×1024-16 which is vbeinfo mode number 0x11a and hwinfo mode number 0x031a. I was surprised to find that though the HW supports 24 bit, 16 bit is all that works in the fb. When it does boot and I switch to a VT, the login prompt is not at the top left, but down a number of lines. It does boot and work, though.
Hi! Hey, it worked perfectly! Thank you very much!
I have an nVidia GeForce 8M (so mobile) and this works perfectly using the proprietary drivers.
Thanks.
very good, excellent, factional and beautiful.
Brazil
[…] originais para Hoa Nguyen da Ubuntu community e imagens algumas imagens são do […]
It worked perfectly! Thank you
ty a lot it worked!
why I can’t find v86d??
work fine with ubuntu Lucid ATI Radeon 9200 dual head whit extended desktop.
Thank you
Ciao
Mario
[…] novità!) per il passaggio da Ubuntu 9.04 a 10.04 per chi usa i driver proprietari NVIDIA. Questo ottimo articolo mi ha consentito di poter tornare ad utilizzarli.. Questo era un requisito necessario per tentare […]
at last after days trying other guides. it finally succeeded me with this guide! thanks!
Simple trick for people (desktop users) who suffer from 1cm left picture shift on nVidia cards.
If your monitor native resolution is let’s say 1280×1024 (my case) and you use nvidia driver you may notice a small 1cm shift of the splash screen during boot (and in the terminals all the time). It can be adjusted by calibrating your monitor, but that will result in the shift to the right in GDM and KDE/GNOME/etc.
That’s why I set my framebuffer driver to use lower (but acceptable) resolution of 1024×768 (4:3), while leaving native resolution of 1280×1024 (5:4) for proprietary driver. This lets my LCD panel adjust both properly. Rescaling is unnoticable.
Hope to help someone 🙂
I get a FATAL Error when I do this. It works just as advertised (my bootsplash looks gorgeous again!) but right after I choose Ubuntu from GRUB, during the “flashing cursor” screen prior to the purple bootsplash there is an error message:
FATAL: Error inserting echo (/lib/modules/2.6.32-22-generic/kernel/drivers/staging/echo/echo.ko): unknown symbol in module or unknown parameter (see dmesg)
It stays up for a few seconds, but Ubuntu appears to boot normally and everything besides is working fine. Any suggestions?
Thanks otherwise for the excellent bootsplash fix!
echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
Above is a command that you execute in a terminal!!!
Remove the line from /etc/initramfs-tools/modules
And follow the guide step by step again 😀
But I admire – it was funny 😀
In case this helps anyone, I had to add ‘-k all’, i.e.,
sudo update-initramfs -u -k all
to get the -rt kernel’s initrd to pick up the changes, else only the -generic kernel would display the graphical plymouth splash screen.
Thanks, now my boot’s splash screen is flawlessy (but when I turn of my computer, only the lights from the Ubuntu’s splash screen appears sometimes, oh well) with NVIDIA’s proprietary drivers.
As a positive side effect of this hint, now framebuffer aplications like mplayer with “-vo fbdev2” or “-vo directfb” options now works like a charm. A little slow, but works =D .
[…] dan berhasil di AMD/ATI dan Intel GMA). Sumber tulisan ini sebagian besar dari artikel Softpedia, blog Idyllic Tux, dan Ubuntu […]
Thanks, I was almost unistalling all phymouth packages to get a text boot…
btw, someone here is using a Mobility Radeon 4670 with desktop effects enabled? I spent two days researching on the web for a solution but atm still disabled. I was looking initially for some parameter to xorg.conf but I tried so many different sets and nothing.
I have 3D, and is working absolutely great. Just to you guys have an idea… I tested Nexuiz with the native driver and got around 15~24fps. Enabling restricted driver or using the official driver from ati I get 160~210fps – but no way to enable composite on kde =\.
If I get no solution, I’ll stick to restricted driver… there is no sense to have a card with 1GB DDR3 memory and a terrible performance. But, obviously, I will miss the fancy desktop effects.
Any help is extremely appreciated.
Hi mate, I had same problem with Kwin and desktop effect like you at first. For fglrx driver, you need to edit kwinrc file and change DisableChecks=true. Then type invoke KRunner and run ‘kwin –replace’
~/.kde/share/config/kwinrc
[Compositing]
…
DisableChecks=true
…
You rock! Works like a charm, thank you very much.
[…] Este blog Acceso desde aquí Amiguetes Este blog Acceso desde aquí Amiguetes Solución 2 para ver Plymouth correctamente con drivers de Nvidia ó ATI On 05/19/2010, in Manuales, by Juan manuel Gracias a los comentarios de Bernat y Joaquín en la entrada anterior entrada Solucionar los problemas con Plymouth, hemos encontrado una solución que realmente funciona para Nvidia y ATI además de poder usar el TTY cuando pulsamos Ctrl+Alt+F1 para cuando tengamos problemas con el entonrno gráfico. Lo acabo de probar y funciona sin problemas. Aquí os dejo las instrucciones sacadas de idyllictux. […]
I’ve an external 24″ 1920×1200 screen connected to my laptop. I’m not using the laptop screen (disabled with nvidia-settings).
Can someone confirm that this solution will work with an external screen ?
Thanks
This worked for me!
But when I rebooted my computer, it showed “vga=792 is deprecated…” which I managed to get rid of by following the steps in this thread –> http://ubuntuforums.org/showthread.php?p=8420347
Yes, it’s a bit slower when booting up. But I can live with that. 🙂
idyllictux, thanks much for this terrific and timely post. I can confirm it worked great on a Lenovo T410 laptop running Lucid and nvidia’s v195.36.15 driver. The native resolution for this laptop (1440×900) was not among the ones listed, however, 1024×768-24 worked well.
I have the same problem like Hwoary this my log
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.34-020634-generic root=UUID=758dbf47-0048-407f-91bf-47f5c7b5ded0 ro quiet splash nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap
[ 1.352947] uvesafb: (C) 1988-2005, ATI Technologies Inc. , RV535, 01.00, OEM: ATI ATOMBIOS, VBE v3.0
[ 1.470652] uvesafb: protected mode interface info at c000:a2ac
[ 1.470657] uvesafb: pmi: set display start = c00ca334, set palette = c00ca3f0
[ 1.642251] uvesafb: VBIOS/hardware supports DDC2 transfers
[ 1.686018] uvesafb: monitor limits: vf = 160 Hz, hf = 70 kHz, clk = 110 MHz
[ 1.686135] uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4096
[ 1.686140] uvesafb: cannot reserve video memory at 0xd0000000
[ 1.686764] uvesafb: probe of uvesafb.0 failed with error -5
end this
cat /proc/fb
0 EFI VGA
help me please! Thanks!
Make sure in your grub the following line is commented out.
#GRUB_GFXPAYLOAD_LINUX=
The presence of this line will make your fb to use EFI which is what we don’t want.
THANKS!!!!!
Worked great on both a Dell XPS 1530 and a Sony Vaio VGN-nw11s 😀
Thank you for answering me, but i dont have that line on my GRUB. : s Do you have another solution?
Ok i found the problem when i put this line on the file “/etc/grub.d/00_header” that call EFI. I deleted that line and now is fine!
Thank you for your help!
“set gfxpayload=keep”
[…] Source: Tux’s idyllic life. […]
worked great… no red flickering pixelart on boot nor (un)suspend… many thanks…
btw… anyone knows why hwinfo shows only 4:3 aspects? my laptop has widescreen native res but it’s not shown…
Only fix that worked for me using Nvidia 8800 GTS 512 at 1920×1200 res. Boot did not slow down for this. Thanks
One more question this is normal??
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=4096
[ 1.621020] uvesafb: framebuffer at 0xd0000000, mapped to 0xf8200000, using 16384k, total 16384k
[ 2.294276] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[ 2.599355] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[ 2.833376] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
[ 3.104032] uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
Normal. Don’t worry about it. Happen when you change to VT and back.
Ok, thanks! idyllictux!
Thanks, works great! Too bad I have an SSD-disk, and only see the splash for 2 seconds though 😉
try to change the time delay on the files “/etc/init.d/halt” and “/etc/init.d/reboot”
This works for me too. Suspend seems to work too.
But I still think it is strange that it should be so much more difficult to change the resolution under GRUB 2 than GRUB 1. Or is it not GRUBs fault?
If I only want to change the resolution to my virtual terminal (Plymouth disabled), is this still the easiest way?
A good example for how not to fix something if it’s not broken, Ubuntu 9.10 here I go… I can close the windows on the right side also 🙂 and video works faster, etc…
Here you go 😉
[Lucid] i don’t use plymouth at all.
Change default theme gives the option to switch buttons.
Honest, I don’t get the logic between community requirement of faster boot and at the same time fiddling around configs, this all for 10 or 15 seconds boot time.
thanks a lot 🙂
on my onboard nidia geforce 8200 it works onlys if the monitor ist plugged via dvi or hdmi. via d-sub there ist a black screen instead of the plymouth splashscreen.
I LOVE YOU!!!
i have been trying to figure out why tty1-6 were coming up with a blank screen, i have tried numerous solutions and this was THE ONLY one to work….
much thanks and great work!
running ubuntu 10.04 on a acer aspire 4520 with latest nvidia 195 drivers.
You’re the man! thanks for this 🙂
[…] continue searching with uncle google n finally i found the answer. Tha answer is from this site : [Tux’s idyllic life.]. I will summarize it in this […]
Cheeeeeeeeeeeerrrrrrrrrrs Mate!!!!!!!! Did work really well.
[…] грубо и как-то не эстетично. Покопавшись в сети нашел решение этой проблемы. Редактируем # sudo gedit […]
thanks a ton for this fix, worked perfectly 😀
Thanks for the tips. This worked great for me on a Dell Precision Laptop with nVidia Corporation NV36 [Quadro FX Go1000] video card.
Thanks!
Worked great with the Intel HD Graphics on my Acer Aspire TimelineX 3820TG.
Awesome, worked like a charm. The key that I was missing was using hwinfo to find a resolution that my video card actually supported. Thanks!
[…] 原文地址:https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-termin… 现 简述解决过程: 1. […]
It’s probably worth mentioning that many people with Nvidia cards (at least from the past few years) may need to use the 32-bit color depth rather than 24-bit depth in order for this to work properly. I’m running an Nvidia 9500GT.
For example, this works for my system, flawlessly:
uvesafb:mode_option=1920×1200-32
But this does not:
uvesafb:mode_option=1920×1200-24
Thanks a lot!!
Thank you!
Worked with my NVIDIA 8600GT. 🙂
This didn’t work for me, NVIDIA, but when I backed everything out, the logo was beautiful. I’m not going to pretend I understand why it happened, but it did. Thanks anyway.
Burg users do the same except you edit /etc/default/burg and sudo update-burg at the end.
Awesome tutorial.
Worked awesome thanks !
Unfortunately I can’t logout or use ctrl-alt-Fkey. When I do the brightness is gone and its very tricky to get it back without a reboot.
I got the brightness fn-keys working , now the last thing I need to do is make it possible to logout and/or us access virtual terminal.
Has anyone else had these issues with trying to logout and having it go weird blurry graphics or darkened ?
Also when I shut down the screen turns washy.
Any help greatly appreciated
Sony Vaio F111D with a 310M Nvidia card.
All fixed. Thanks a million.
As mentioned a few times use sudo hwinfo –framebuffer gives you the resolution info you need to plug in.
I’m so amazingly happy that I have the Lynx unleashed !
Love yall
It worked flawlessly on my Thinkpad T61 with nvidia Quadro NVS 140M (1440×900-24 supported). Thanks a lot.
[…] parte dessas sugestões foram retiradas deste artigo. Categoria: Sem categoria | Comentário (RSS) […]
u rock 🙂
Finally something that works!!!
Thank-you
Great!!! Thnaks for your help.
Great job
Works like a charm …card = 8600GTS
I’ve followed this guide and most of my problems solved , now i have 2 problems:
1) GRUB menu doesn’t show up at all , only cursor blinking for like 10 sec then boot directly .
2) Shutdown splash and CRTL+ALT+Fx . both are blurring .
Appreciate any help .
Ubuntu 10.04 + NVIDIA Beta x86_64-256.35 driver.
Sony Vaio VPCF111FX/B.
Work fine on sis mirage 3 too. Thank you!
I had it working perfect. Now the last little glitch is when I use ctrl-alt-fkey to get a virtual terminal the screen goes choppy/wavy.
Logout works fine now etc … but flipping to a virtual terminal brings up bad wavy video.
Can anyone help me solve this last little issue ?
Thanks in advance.
Seems to work perfectly, thanks! I have boot env running at 1280x800x24 smoothly. I do see about 1 or 2 seconds longer in boot but no hanging issues.
(10.04 amd64 with nVidia 9100M)
[…] High resolution Plymouth & Virtual Terminal for ATI/NVIDIA… [Tux's Idyllic Life] […]
For some it can help to install gnome startup-manager. It’s a gui that does what is described in this thread. It may help people who are very new and are afraid to edit scripts in terminal.
I still need help with the same issue Haitham has.
Bad video on shutdown splash and virtual terminals.
Sony Vaio VPCF111FD with 310M Nvidia.
[…] Grande parte dessas sugestões foram retiradas deste artigo. […]
First of all, thanks for this fix! It worked perfectly on kubuntu and took a bit more to get to work on mint’s gnome version, but only due to my error. I only have one real question; would it break this fix if I were to install burg? I’m pretty sure it would, but then again we’re fixing plymouth, not grub, thus why I ask. Please help, thanks again!
Burg users do the same except you edit /etc/default/burg and sudo update-burg at the end.
Hi,
I’ve tried what you posted and also what is in this comment https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-terminal-for-atinvidia-cards-with-proprietaryrestricted-driver/#comment-481 and my virtual terminals still don’t work. They just remain as a black lit screen. Here is my output.
dmesg | grep uvesafb
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=f2962616-ba3c-4b17-a9a2-444cdd2b7d46 ro nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=f2962616-ba3c-4b17-a9a2-444cdd2b7d46 ro nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap
[ 15.101362] uvesafb: NVIDIA Corporation, GT218 Board – 0696a750, Chip Rev , OEM: NVIDIA, VBE v3.0
[ 15.216713] uvesafb: VBIOS/hardware doesn’t support DDC transfers
[ 15.273961] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 15.274422] uvesafb: scrolling: redraw
[ 15.274426] uvesafb: cannot reserve video memory at 0xe1000000
[ 15.274435] uvesafb: probe of uvesafb.0 failed with error -5
cat /proc/fb
0 EFI VGA
sudo hwinfo –framebuffer
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.AnRhIsOMjXB
Hardware Class: framebuffer
Model: “NVIDIA GT218 Board – 0696a750”
Vendor: “NVIDIA Corporation”
Device: “GT218 Board – 0696a750”
SubVendor: “NVIDIA”
SubDevice:
Revision: “Chip Rev”
Memory Size: 14 MB
Memory Range: 0xe1000000-0xe1dfffff (rw)
Mode 0x0300: 640×400 (+640), 8 bits
Mode 0x0301: 640×480 (+640), 8 bits
Mode 0x0303: 800×600 (+800), 8 bits
Mode 0x0305: 1024×768 (+1024), 8 bits
Mode 0x0307: 1280×1024 (+1280), 8 bits
Mode 0x030e: 320×200 (+640), 16 bits
Mode 0x030f: 320×200 (+1280), 24 bits
Mode 0x0311: 640×480 (+1280), 16 bits
Mode 0x0312: 640×480 (+2560), 24 bits
Mode 0x0314: 800×600 (+1600), 16 bits
Mode 0x0315: 800×600 (+3200), 24 bits
Mode 0x0317: 1024×768 (+2048), 16 bits
Mode 0x0318: 1024×768 (+4096), 24 bits
Mode 0x031a: 1280×1024 (+2560), 16 bits
Mode 0x031b: 1280×1024 (+5120), 24 bits
Mode 0x0330: 320×200 (+320), 8 bits
Mode 0x0331: 320×400 (+320), 8 bits
Mode 0x0332: 320×400 (+640), 16 bits
Mode 0x0333: 320×400 (+1280), 24 bits
Mode 0x0334: 320×240 (+320), 8 bits
Mode 0x0335: 320×240 (+640), 16 bits
Mode 0x0336: 320×240 (+1280), 24 bits
Mode 0x033d: 640×400 (+1280), 16 bits
Mode 0x033e: 640×400 (+2560), 24 bits
Mode 0x0345: 1600×1200 (+1600), 8 bits
Mode 0x0346: 1600×1200 (+3200), 16 bits
Mode 0x0347: 1400×1050 (+1400), 8 bits
Mode 0x0348: 1400×1050 (+2800), 16 bits
Mode 0x0349: 1400×1050 (+5600), 24 bits
Mode 0x034a: 1600×1200 (+6400), 24 bits
Mode 0x034b: 1600×900 (+1600), 8 bits
Mode 0x034c: 1600×900 (+3200), 16 bits
Mode 0x034d: 1600×900 (+6400), 24 bits
Mode 0x0352: 2048×1536 (+8192), 24 bits
Mode 0x0360: 1280×800 (+1280), 8 bits
Mode 0x0361: 1280×800 (+5120), 24 bits
Mode 0x0362: 768×480 (+768), 8 bits
Mode 0x0364: 1440×900 (+1440), 8 bits
Mode 0x0365: 1440×900 (+5760), 24 bits
Mode 0x0368: 1680×1050 (+1680), 8 bits
Mode 0x0369: 1680×1050 (+6720), 24 bits
Mode 0x037b: 1280×720 (+5120), 24 bits
Mode 0x037c: 1920×1200 (+1920), 8 bits
Mode 0x037d: 1920×1200 (+7680), 24 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown
cat /etc/default/grub
# If you change this file, run ‘update-grub’ afterwards to update
# /boot/grub/grub.cfg.
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
GRUB_CMDLINE_LINUX_DEFAULT=””
GRUB_CMDLINE_LINUX=”nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap”
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo’
GRUB_GFXMODE=1024×768
GRUB_GFXPAYLOAD_LINUX=1600×900
# Uncomment if you don’t want GRUB to pass “root=UUID=xxx” parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_LINUX_RECOVERY=”true”
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE=”480 440 1″
cat /etc/initramfs-tools/modules
# List of modules that you want to include in your initramfs.
#
# Syntax: module_name [args …]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
uvesafb mode_option=1024×768-24 mtrr=3 scroll=ywrap
cat /etc/issue
Ubuntu 10.04 LTS \n \l
uname -a
Linux carbon 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux
nvidia proprietary driver 195.36.24
what does uvesafb error code -5 mean? I tried googling for that info but couldn’t find anything.
comment out this line #GRUB_GFXPAYLOAD_LINUX=1600×900, then update-grub. That line shouldn’t be present.
great that worked! I now have VTs . The only thing now is that the VT terminal is very wavy/noisy. I guess it’s something though. I’ll keep looking to see if I can fix it.
Previously I added the GRUB_GFXPAYLOAD_LINUX because of that comment I linked to previously. It got my resume from suspend working initially before I added all the uvesafb stuff. However, even with it commented out now the resume from suspend still works.
Thank’s a lot!!!! Hello from Serbia!God bless you!
It works on my laptop with SiS mirage 3 graphics (sis672). Thanks a lot !!!
Thanks.
it works for me.i’m very happy.:-)
god bless you
Thanks a lot! Works on Dell Studio 15.
Thank you so much for this fix!
After trying the other “possible” fixes and being disappointed so many times, your solution worked easily and painless.
Thank you so much. It worked for me. Meow!
Thank you so much for this solution!
It works perfectly for me. Should be suggested to the developers of Ubuntu.
You, my friend, should re-write all how-to’s on the net. All of them.
[…] 我把这一步又改回原来的样子后重启,开机LOGO就恢复那个美美的样子了~ = =唉……感觉我啥毛病都会遇到Orz 这里还是给同样遇到我这问题的人一个参考吧。 转自:http://hi.baidu.com/dongfengxiao/blog/item/9cfd2d230310834392580798.html 国外原文地址 […]
Thanks, it works perfect (notebook msi gx710)
Thank you so much!
My native monitor resolution is 1920×1080 but the highest available for me is Mode 0x031b: 1280×1024 (+5120), 24 bits so I use that instead. It works but is there a way to used my monitor’s native resolution instead? How can I make my monitor’s resolution available? Perhaps, upgrading my vcard?
Thank you! Works neatly @ 1024×768-24 on my Vaio F12 with GeForce GT 330M. But I share the same concern as the above commenter. Is it possible to run 1920×1080 even though “sudo hwinfo –framebuffer” does not list it as an option?
i tried it. i mean. i entered 1920×1080 as the resolution even though its not in the list. i get the very low resolution instead. something like 800×600 in my 1920×1080 monitor.
Yaay. Worked in a jiffy. Reboot dint hag on me. 😛 Very much appreciate your work. Thank You. Thank You. Thank You.
Hey!
Tried your fix, and it works.. in my case i had to set 800×600-24.. asus eee pc netbook with intel GMA950..
Anyway, one strange problem: My mouse cursor disappears when logging in to desktop.. I can see the cursor at the login screen, but when i login, the mouse cursor just disappears.. I can still click things, but the cursor is gone so i kinda have to guess where the cursor is.. One way of bringing it back is to open terminal and run “sudo update-alternatives –config x-cursor-theme” which brings it back instantly, before i even need to make a choice in there.. Undoing the uvesafb changes, as in removing it from grub and initramfs will bring back my awful plymouth, and the mouse cursor stays through login… Which means it must be affected by uvesafb somehow.. Any thoughts?
Nice one fella!
It worked like a charm!
Didn’t work for me.. 😦
I followed exactly what you instructed. But my ubuntu failed to boot and the screen didn’t show anything.
I tried to boot many times but the results always the same, boot failed and nothing showed. Even the recovery mode couldn’t start up.
Glad, I have windows installed (glad?) so I could post my problem.
I have an ASUS K401N notebook with NVIDIA G102M and 256-35 driver installed.
Any solutions?
Works, but disables the “reboot = pci” and it doesnt support 16:9
Worked for 9600M GT, Kubuntu Lucid / 64-bit.
Thank you, Nikos
Worked great! I even got 16:9 native resolution at 1680×1050-24 and “Solar” Splash screen works nice
Running
Ubuntu 10.04 Lucid (64 Bit)
Kernel 2.6.32-24-generic
NVIDIA GeForce 8600 GT
NVIDIA Driver V. 195.36.24
thank you. solved my problem
Nice workaround..I had to use this many times..so I have written a script for it… you can download it here:
http://rapidshare.com/files/415554432/screen.sh
If you don’t trust it, open the file with gedit and try to understand.
It makes an automatic backup of the files that would be changed…
Btw, for the script:
It takes the highest resolution given by hwinfo… and you have to make the file executable(to do this open a terminal, “chmod 777 screen.sh”)
Thanks! This worked perfectly. But not for the exact problem you are writing about.
If you have a sis672 chipset (and have found the 2D drivers) you may notice that your monitor goes all..well….screwy during boot. Looks like the refresh rate is off.
Follow the instructions in the post, and it fixes it.
Positive effect also in 10.10 and nvidia 😉
Will search a bit ubuntu forum and eventually
copy this as a solution 😉
many thx
On ubuntu lucid 10.04.1 .. doesn’t work.. do you think burg has any part in failing this process from workign?
Hi,
I’ve tried your solution for the problem and it almost works.
I’ve got a Sony Vaio VPCF12M1E/H with Nvidia 330m and I’ve installed the latest Nvidia drivers on an Ubuntu 10.04.
uvesafb works at boot time, kernel messages are displayed in standard 80×25 but init messages are displayed in the resolution I’ve chosen from hwinfo output.
The problem is that after Nvidia drivers are loaded and X is started when switching to tty1 the new resolution is used but now the letters are flickering (like a wind effect on horizontal axis 🙂 ).
I’ve tried all the resolutions that make sense with no result. Sincerely I would be satisfied with 80×25 also but without uvesafb I get a black screen.
Any ideas?
Thanks
[…] be nice that the splash screen and moving dot’s are viewable. I should take a further look at another solution/work-around in which the author states he hates the set gfxpayload=keep solution and gives a better […]
thank, really workit newly
Thanks
My monitor resolution is 1360×768 (LG W1953S).
My graphic chip is NVidia GeForce 6150 (onboard), with driver ver 173 on Ubuntu 10.04.
With the resolution 1360×768-24, the Plymouth splash can show, but is left-offset.
However, with that resolution, the GRUB2 OS option can’t show, with the error returned from the monitor: “Out of range” and the virtual terminal’s text is flickering.
This resolution is not in hwinfo’s list.
Any help?
You can’t use the resolution which is not listed in hwinfo. Only use the one which is listed. Cheers.
[…] P.p.s. L’articolo originale. […]
Awesome Howto, but can you please avoid some hair pulling by taking the line break out of the line….
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset video=uvesafb:mode_option=1366×768-24,mtrr=3,scroll=ywrap”
as it MUST all be on one line in /etc/default/grub.
Cheers.
Cam.
thnx for the information
Works great!
Thanks a lot 🙂
I can confirm that this method works fine on Ubuntu 10.10 amd64, kernel 2.6.35-22-generic, NVidia GeForce 9600M GT, nvidia driver 260.19.06, Grub2.
Only difference is that I did not append “nomodeset” in GRUB_CMDLINE_LINUX_DEFAULT as it reminded me of an option for old graphic cards (but actually I don’t know exactly what “nomodeset” means) and it didn’t look necessary. Indeed, it was not.
However after this sucess I tried with “nomodeset” just to see if there was any difference and indeed, after update-grub and update-initramfs -u, there was a difference at shutdown: instead of the Ubuntu logo and the five dots there were only the five dots on a black background. Curious. No difference at startup though.
I don’t know if it is very relevant though, but perhaps is it noteworthy.
I can also confirm that Bruno’s method given in the comments works fine too. Plymouth splash screen and VTs are high-resolution with no use of uvesafb and less tweaking, but for NVidia cards only.
Strangely enough however /proc/fb does not read 0 EFI VGA in my case but 0 VESA VGA, i.e. the same value as with your method. Yet I did revert all the changes brought by your method before trying Bruno’s method; I even uninstalled v86d so uvesafb cannot be used, as far as I understand. And indeed lsmod | grep vesa returns nothing, however dmesg | grep fb (or grep vesa) returns:
[ 0.647670] vesafb: framebuffer at 0xd3000000, mapped to 0xffffc90005100000, using 5120k, total 5120k
[ 0.647674] vesafb: mode is 1440x900x32, linelength=5760, pages=0
[ 0.647676] vesafb: scrolling: redraw
[ 0.647680] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.756660] fb0: VESA VGA frame buffer device
[ 0.756717] efifb: dmi detected MacBookPro5,1 – framebuffer at 00000000c0010000 (1440×900, stride 8192)
So it looks like a vesafb (but not uvesafb) I had no idea about is somehow defaulted to by my system.
Two last notes: 1/ Bruno’s method does not make Grub high-resolution, but it is merely a matter of GRUB_GFXMODE + sudo update-grub to change it, and 2/ it as the same caveat (on my system) as your method + nomodeset (cf. my previous post) i.e. the splash screen during shutdown is ugly with just the five dots without the Ubuntu logo, plus it also has a bunch of error messages. But all in all it’s just for a couple of seconds before the computer shutdowns, so…
Anyway thanks to both of you.
Great! Thank you – worked first time with Ubuntu 10.10, Nvidia GeForce 7600 GS and driver 260.19.06.
In X my resolution is set to 1600×900. But when I use sudo hwinfo –framebuffer, it doesn’t display this resolution. Why is that??
Another thing, there’s error messages showing up with this command:
> hal.1: read hal dataprocess 2168: arguments to dbus_move_error() were incorrect, assertion “(dest) == NULL || !dbus_error_is_set ((dest))” failed in file dbus-errors.c line 280.
This is normally a bug in some application using the D-Bus library.
libhal.c 3483 : Error unsubscribing to signals, error=The name org.freedesktop.Hal was not provided by any .service files
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.464]
Unique ID: rdCR.UKXxIqIgY83
Hardware Class: framebuffer
Model: “(C) 1988-2005, ATI Technologies Inc. M96”
Vendor: “(C) 1988-2005, ATI Technologies Inc. ”
Device: “M96”
SubVendor: “ATI ATOMBIOS”
SubDevice:
Revision: “01.00”
Memory Size: 16 MB
And at last, why it’s showing just 16mb??
Thanks a lot
This didnt work for me. I am a n00b at linux, so i probably did somthing wrong, and now by boot screen is effd up. Can sombody please tell me how to revert this?
Confirmed working here. Splash with dots and hires grub all working fine despite hwinfo not listing my native resolution of 1366×768 🙂
HP Pavillion DV6
NVidia GT 230M
NVidia driver v 260.19.06
Ubuntu Maverick 10.10
I’m new to wubi ubuntu 10.04 lts. Anyone willing to help out.
I have a Lenovo y560
Switchable Graphics
Intel(R) Graphics Media Accelerator
ATI Mobility Radeon HD 5730
I’m having the black screen problem after installing drivers on wubi ubuntu 10.04.
When trying to input these commands. Do I go into command line (press c). Where do I go to enter these commands.
[…] نیست بلکه از تنظیم نشدن درست بعضی از بستههاست. در این پست به خوبی نحوهی رفع مشکل توضیح داده شده […]
Thank-you, this has been bugging me for months, just got around to looking for a fix and hit a result first stop.
[…] I tried to fix it by following steps there: https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-termin… […]
you could also change your plymouth splash screen to what you want by following this:
manual method: http://jechem.blogspot.com/2010/10/how-to-change-splash-screen-in-ubuntu.html
using GUI: http://jechem.blogspot.com/2010/11/cool-plymouth-manager-for-ubuntu-with.html
This is wonderful! I followed these steps on my gateway mx3225 and I was able to get the high quality boot splash! woohoo! Props to you!
Works well with Ubuntu 10.04, and Nvidia GTS 450. Thanks for the article.
[…] o al menos aplicar una solución). Basándome en el “Workaround” publicado en este sitio, voy explicándolo paso a […]
[…] Comments « [Lucid][Ubuntu 10.04] High resolution Plymouth & Virtual Terminal for ATI/NVIDIA cards with prop… […]
Awesome. Worked flawlessly on my HP DV6905ee, running Ubuntu 10.4.
Thank you So MUCH. Didn’t know the boot screen could look so much prettier!
Thnx man, works….:-)
thanks! it works!!!
Hello. I tried your solution with uvesafb, it worked fine. My question is: doesn’t this solution affect my fglrx driver? Will i still be able to run 3D games and watch high-resolution movies?
Yes you are still able to do those things =)
[…] 参考: [1]Known Lucid Lynx issues/bugs with workarounds [2][Lucid][Ubuntu 10.04] High resolution Plymouth & Virtual Terminal for ATI/NVIDIA cards with prop… […]
Sir…
You are a gentlemen and a scholar
The latter by the quality of the information provided and the former by the number of follow up replies.
Thanks
X
… this one goes in my bookmarks 🙂
Haha, thanks. Your reply made my day. Though nowadays, I don’t have many tricks to share anymore which is good since the distro is getting stable =)
Hello.
I am a complete Ubuntu newbie. And I agree with your rant on so-called universal fixes that don’t work at all, or are outdated.
However, since I am such a newbie, I won’t try to to do something radical in [i]etc/default/grub[/i]. The problem is that there is no “video=uvesafb:mode_option=1366×768-24,mtrr=3,scroll=ywrap”, the only “resolution thing” there is is a [i]#GRUB_GFXMODE=640×480[/i].
Also, hwinfo did not list my resolution (1920 x 1200), but it’s not like I got to try it anyway. 😦
Thanks!
Hi, of course there is no such line. You need to append it to this line (i think it is line 9 in grub)
GRUB_CMDLINE_LINUX_DEFAULT=”quiet nomodeset “
Right. Well, I managed to destroy the whole GRUB. Is there an easy way to ‘revert it’, as it says in the top of the article?
Sorry to be of bother. :I
Well, did you keep a copy / back up of your grub? Replace using that copy.
If not you can use this copy
http://pastebin.com/zdLP6cJD
Thanks. 🙂 I got it working again now.
N00bs like me shouldn’t be allowed on the internet.
Hey, don’t be hard on yourself. I was once a noob =D
Grrr. 11.04 is here and still the same problem. Who is asleep at the helm?
Hello every1 Neutral wanted to say hi! Been reading this forum after long at the present time and decided to note at last and maybe provide comunity with some beneficial info
Upgraded my Macbook Pro from Ubuntu 10.10 to 11.04. This worked in Ubuntu 10.10 but not 11.04.
It tried :
GRUB_CMDLINE_LINUX=”quiet splash nomodeset video=uvesafb:mode_option=1280×800-24,mtrr=3,scroll=ywrap”
and setting :
GRUB_GFXMODE=1280×800
This method seems not to work in 11.04 –
What did work for me was using the old VGA codes to set the resolution.
GRUB_CMDLINE_LINUX=”quiet splash vga=792 nomodeset”
and updated GRUB:
sudo update-grub2
(for VGA codes see : http://www.pendrivelinux.com/vga-boot-modes-to-set-screen-resolution )
I had to set a resolution lower than my own 1024×768. Now Ubuntu 11.04 boots with a graphic boot splash screen again. Not the ideal resolution as with uvesafb but much better than waiting for a purple screen to boot.
[…] Original workaround posted April 26, 2010 by idyllictux (cleaned up for formatting) […]
[…] [Lucid][Ubuntu 10.04] High resolution Plymouth & Virtual Terminal for ATI/NVIDIA cards with prop…. […]
Thanks for the writeup. Worked without issue on a fresh Linux Mint 9 installation. Other sites were just linking to a script. Thanks for taking the time to write out the actual steps involved.
Echoing Christiaan’s comment of May 5, 2011 –
– this is an excellent guide that worked perfectly in Kubuntu 10.10 with and ATI Mobility Radeon, but doesn’t for some reason in 11.04. However, using vga modes to set resolution seems to work great.
My /etc/default/grub:
GRUB_CMDLINE_LINUX=”quiet splash vga=838 nomodeset”
…..
GRUB_GFXMODE=1400X1050
My file /etc/initramfs-tools/modules set back to default (in my case, everything commented out); and,
My /etc/initramfs-tools/conf.d/splash with two lines, first a comment explaining the file creation and the second “FRAMEBUFFER=y”.
This works like a charm for me.
Hi Dave,
Sadly it doesn’t work for me. I kept on getting “error inserting vesafb.ko”. =(
Cheers
Great! Thanks man, I got back the original state in appearance and that is what I wanted.
You have the opinion how great system you use but people look at you strange saying that doesn’t look anything professional. Especially because i use encryption so it was a total mess for me. This solved it perfectly. Never hanged and it even seem to be booting with the same speed as before the ati drivers. It wasn’t just ugly but sometimes it was hanging long on the black screen.
My sympathy towards those who couldn’t get it working.
Ubuntu 10.4 and windows 7 dual boot experience. This worked for me in Laptop. No error. But when I tried with a compaq desktop I ended up in a message “home /etc/timidity not ours” and the xserver stopped there. The gfxmode was 800×600 which supports my monitor. With nvidia drivers on the situation is more severe, plymouth returns to my grub2 background picture visible on top of the screen and hangs there. Any solution?
Hi, I think the problem is with timidity daemon. Google for the error message and fix it first.
Cheers
Thank you~! I learned a lot.
Alternative way worked for me only with 1024×768, on 9600GT and SyncMaster 2333HD (16:9, 1920×1080 best).
So I decided to use kernel option instead, ‘quiet splash nomodeset’ without any GFX parameters, even though I cannot see splash rightly, no matter for Server edition because I could use (maybe) 132×43 console screen of shell with colors which is enough for my current use.
In Ubuntu 11.04 all that is needed to fix this problem is described here
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/771905/comments/39
Upon following these steps in 11.04, I was prompted with a blank purple screen. Keyboard input was still read and the startup process proceeded normally in the background, but this was problematic as my drives are encrypted which requires entering in a pass-phrase. I was able to resolve this issue by removing the vt.handoff=7 from the following line in /etc/grub.d/10_linux:
GRUB_CMDLINE_LINUX_DEFAULT=”$GRUB_CMDLINE_LINUX_DEFAULT vt.handoff=7″
After changing that line, running update-grub2 fixed the issue. I hope this is helpful to anyone else experiencing that issue.
My most sincere thanks for making this post
I have now fixed my Asus 901 to get native resolution on tty/console after very many hours of searching and testing
I cannot thank you enough !
I tried this on my 2 computers using lucid; in one (hp laptop) it didn’t work as expected, and in the other (desktop asus m/b) it broke my nic with the patched initramfs, I had to revert everything to get my nic working again.
/etc/default/grub file is not getting updated. /etc/initramfs-tools/modules file is getting updated with the input resolution(asked by the shell script through user input).
$uname -a
Linux user-laptop 2.6.32-32-generic #62-Ubuntu SMP Wed Apr 20 21:54:21 UTC 2011 i686 GNU/Linux
$lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid
Work Around I did. Manually run following lines to fix ugly-plymouth screen
$sudo apt-get install v86d -y
$sudo nano /etc/grub.d/00_header and added following code after line set gfxmode=1024×768
–> set gfxpayload=keep
$sudo gedit /etc/default/grub and added the following code
–> GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap”
–> GRUB_GFXMODE=1024×768-24
$sudo gedit /etc/initramfs-tools/modules and added the following code
–>uvesafb mode_option=1024×768-24 mtrr=3 scroll=ywrap
$echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash
$sudo update-grub2
$sudo update-initramfs -u
–>DONE:)
Also had to uninstall burg-pc, which is an extension to grub2 having new graphic menu system, support sophisticate themes.
-Is there a workaround supporting burg-pc.
-The dots on plymouth keeps moving from first position to last – 3 times before displaying login screen. Can this be reduced to a single loop.
Really looking forward for your script hack.
thank you very much! nice post with details, configured my gtx260 to nice 1680×1050 console
My problem was my monitor displaying black and white stripes pre – login manager and following this guide solved it.
It did remove the stripes but it rendered me with a black screen lasting 10 seconds without a splash sceen at all. I managed to fix this by following this guide: http://www.omgubuntu.co.uk/2011/05/super-boot-manager-eases-burg-grub-plymouth-tweaking-pains/
[Super Boot Manager] I’m not an expert but this program seems fairly unstable from my point of view. I took the risk however to go through with it, that doesn’t mean you should and that it will work.
Pentium 4
Video Card: Nvidia 6200
Drivers: Proprietary: Nvidia 173.14.30
I wish to add further steps which isn’t stated from that link:
1. I started super-boot-manager by running “super-boot-manager” in console.
2. I chose “Plymouth-Manager” -> “Proprietary Drivers”.
3. I selected “Grub2” and pressed “Apply Fix”
good tip, works like a charm on ubuntu 11.10 thanks
[…] Original workaround posted April 26, 2010 by idyllictux (cleaned up for formatting) […]
Thank you very much indeed. I like to have the virtual terminals always available and they were lost after installing Lucid …
I have a ATI Radeon HD 5450 that needs the propietary fglrx module for using compiz. Virtual terminals were lost either using fglrx or radeon xorg modules and were available only using vesa.
Now I have both desktop effects and available virtual terminals!
How I did to work better with ATI proprietary drivers:
1. Run vbeinfo in grub terminal, to choose the best resolution suitable for your computer.
2. Modify the /etc/default/grub accordingly:
– Line GRUB_CMDLINE_LINUX_DEFAULT should contain the word splash
– Uncomment or add the following lines:
GRUB_GFXMODE=1024x768x32
GRUB_GFXPAYLOAD_LINUX=1024x768x32
Put your resolution finded with vbeinfo
3. Modify /etc/initramfs-tools/modules to add the following
drm
modeset=1
4. Install dkms (sudo apt-get install dkms). Remove the file /etc/initramfs-tools/conf.d/splash because you will use dkms for randering.
5. Uninstall and reinstall ati proprietary drivers.
6. Run update-grub and update-initramfs -u
That’s all. You will not get the error ‘possible missing firmware’ anymore.
Coming up on two years old, and this fix is still a godsend for 10.04 LTS-ers.
What I’ve noticed, which is a bit of a PITA, is that regardless of trying my Presario F500’s Nvidia card ‘native’ 1280×800-24 resolution, or the vbeinfo-listed 1024x768x24, there are two delays where system/kernel messages are displayed:
* When switching from the GRUBx menu to Plymouth kicking in.
* When shutting down and waiting on my shutdown splash showing.
I would dearly love to get rid of these; I’m almost done crafting my own Plymouth boot script – “Codename V”. Well-pleased with my results there, but hope I don’t have to fly into the U.S. and brave TSA with a laptop that boots with the message:
“People should not be afraid of their government.”
Governments should be afraid of their people.”
OK, did someone notice that works fine for users who doesn’t connect their monitors trough DVI, but VGA?
This solution works fine but there is something wrong, let me explain well. I know that if my monitor (samsung 2350 23″ with 1920×1080 res) gets a lower resolution for example running bios, of course using DVI port instead of VGA, I got a centered image with black borders all around the image, I mean up, down, left and right. This black borders are like 1 inch. Of course this is not the case if I use VGA port. This didn’t bother me at all. But here is the problem, I can make all the solutions work fine with grub and playmouth but this issue doesn’t fix even if I use native resolution, it keeps showing those black borders like a low res. Of course my solution would be using VGA but I don’t wanna. I pay for a high end video card and monitor. Of couse before using nvidia drivers, playmouth and grub worked at fullscreen with DVI port.
Please let me know how to fix this, btw my video card is Nvidia GT460 with nvidia 260.xx drivers.
try modeset=1 in /etc/initramfs-tools/modules and not nvidia modeset=1
Thank you very much!
Your suggestions are great!
I couldn’t use my ubuntu because of an incorrect configuration of the nvidia drivers while I was attempting to improve the bad graphic quality of my screen…but now all is better than ever!
Wonderful:-)!
Many thanks again!
i just made it exactly as you wrote there, using the 1024×768-24, as it was the “safest” one, and now ubuntu looks horrible. the buttons are all white and big, and there are no icons anymore, but white boxes with black frames (although the resolution is the normal one)
:(((
Worked great on my MacBook Pro 4,1 running Ubuntu 12.04 Precise Beta1 and GRUB, while having 1920×1200 resolution. The splash screen magnified after I installed the current NVIDIA graphics driver. Found this page and everything is much better now.
Thanks.
Thank you, idyllictux!
It worked great on 12.04 LTS dual boot with Windows 7, NVIDIA GeForce GTX 460M, and the most recent proprietary drivers installed. I set the resolution to 1024×800-24 and the grub menu looks just perfect.
However, the plymouth splash screen doesn’t show at boot after the grub menu and before the NVIDIA splash screen. Just a blank screen, for a few seconds. But at shutdown the plymouth shows up in all its glory, with the moving red dots beneath.
Would you happen to know why the plymouth doesn’t show up at boot?
Thanks again!
Hi! I know this is kind of off topic but I was wondering if you knew where I
could find a captcha plugin for my comment form?
I’m using the same blog platform as yours and I’m having trouble finding
one? Thanks a lot!
What’s up to every one, the contents present at this web page are truly awesome for people experience, well, keep up the nice work fellows.
Intructions worked for me. This removed the annoying random black dots on my screen and for an odd reason it also fixed my sound not working on chrome problem (youtube for example).
Do you mind if I quote a few of your posts as long as I provide credit and sources back to your blog?
My blog is in the very same area of interest
as yours and my users would certainly benefit from some of
the information you provide here. Please let me know if this alright
with you. Cheers!
It will be an honour 🙂
It works, thanks a lot!
[…] Lösung habe ich nach langem Suchen und Probieren auf dem englischen Blog Tux’s idyllic life […]
These instructions (with 1280×1024, 16 or 24 bit) repair my splash screen, but when the splash disappears, it reverts to 1024×768 for the desktop. I cannot fix this issue in the System Settings, because it doesn’t recognize my screen. Normally, when I open System Settings > Display, a rectangle appears containing my screen’s brand. Now it just says laptop and I can choose between 1024×768 and an even smaller resolution. Apparently it also gives me Ubuntu2D (evident from the fact that the workspace switcher icon in the launcher is on a gray square, rather than a colored one).
I’ve tried only modifying the grub config, not that other thing, with the same results. I’ve tried only modifying that other thing, not the grub config, but then everything is as it always is: distorted splash screen, perfect desktop.
Maybe some info about how the splash screen is distorted: pixels that are supposed to be close together, are spread all over the screen. So I have five scattered groups of pixels that flash red and white group per group. Also, every second row of pixels on my screen is black. Colors seem to be perfect.
thank you for the guide . I have to install v86d to get it on.
[…] I tried to fix it by following these steps: https://idyllictux.wordpress.com/2010/04/26/lucidubuntu-10-04-high-resolution-plymouth-virtual-termin… […]
This fix worked great much better than the solutions with gfxload=keep
Good lord. This page is still completely relevant and useful. Thank you so much for writing this out with complete explanations. I found so many forum/stack overflow pages with a few commands to run. I tried a ton of them, and I was getting very little results.
I’m running 14.04, and I also had to install v86d from apt, and the kicker was the uvesafb instead of vesafb. How that tidbit didn’t end up in the 9M posts about this, I have no idea.
Running this on 16.04.1 LTS and still relevant and working.
Other solutions I found on the net are not working anymore with 16.04.1 LTS.
Many thanks.