[Gutsy] Slow startup and black screen during Kubuntu's startup on a Dell Inspiron 1521

[Gustavo Narea]

I have a Dell Inspiron 1521 and Kubuntu's start-up is extremely slow. Also, I cannot see the usplash, but only a black screen.

This laptop has an ATI video card and it's using the restricted drivers.

Please let me know how can I help.

[JeffH (jeffh0821)]

Ditto - IBM ThinkPadd T40 - ATI Video, Restricted Drivers.

Let me know if any logs are needed.

- Jeff

[Jack Deslippe (jdeslip)]

I have the same problem on Dell Latitude 810.

[Gustavo Narea (gnarea)]

I forgot to add that this only happens under 64-bit computers running the 32-bit edition of Kubuntu (or, is it just a coincidence?)

[Björn (bjoernw)]

no. it happens also with gutsy 64 bit

[Björn (bjoernw)]

i mean: usplash shows and speed seems to be normal, but there's a black screen and a freezed desktop for some seconds after gdm login

[Saivann Carignan (oxmosys)]

This bug has been already reported as bug #61711. The slow computer startup in Gutsy is caused by the fact that ubiquity often install a /etc/usplash.conf file that contains wrong values ( bug #150930 ) and by the fact that usplash seems to have a lot of trouble while booting the system in that situation.

Generally, you can fix this problem by changing the values in /etc/usplash.conf to :

xres=1024
yres=768

and after this, run sudo update-initramfs -u

Björn : Assuming that the black screen just appears before GDM appears and that the desktop is just freeze for some seconds after booting, I would say that it's normal. However, if this situation is the cause of problems or really seems not normal, I suggest that you open a bug report for that specific case.

[Saivann Carignan (oxmosys)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #61711, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.