My computer uses the Windows bootloader, as configured in the boot.ini file. Boot.ini calls Linux to start. Linux's bootloader Grub takes over and presents me with a menu giving me the choice of different Linux kernels in normal or recovery modes as well as a last opportunity to choose to continue booting Windows. During the update from Ubuntu 9.04 to 9.10, which worked as planned, this did not change. So I am still with Grub as opposed to the newer Grub2 which would have been installed on a fresh installation (as well as with ext3 file systems and not ext4). Now, this Grub has a configuration file called menu.list . In here, you can change the options quiet and splash to noquiet and nosplash. This will turn off the usplash screen (which is the first graphical part during the boot process) and let you see a lot of text flying by describing the progress of your boot process. Basically, I did this to be able to see the difference between recovery mode and normal mode, as there is no boot.log to be found and demsg looks alike in the two cases as far as I could tell. By the way, it took me quite a while to figure out how to switch off usplash, because so many sites state that usplash has been replaced by xsplash in Karmic. Well, this is not the case, Karmic uses both, hence the confusion.
And, hi day, yippy yeah!!! All my problems are gone! Just switched off the usplash screen, and Karmic will not freeze anymore and have no more graphics problems. I can even use the pretty desktop effects without problems now. To make a long story short, on my system configuration, there seems to be a bug either in usplash, or the radeon driver, or some incompatibility between the two. Turn off usplash (which you don't need anyways), and my system doesn't freeze anymore! I'd like to have the tags usplash and radeon added to this bug and file it against usplash for investigation. -- [To Be Filled By O.E.M. To Be Filled By O.E.M.] late resume failure Ubuntu freezes after login. Fine horizontal stripes on the login screen indicate a graphics problem. Mouse still moves but doesn't respond. Reboot by Alt+PrintScreen+B necessary. Workaround: log into a recovery session, fallback to root shell with network, gdm start, login normally, no problem will occur. https://bugs.launchpad.net/bugs/479339 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
