kcn_viper
May 28th, 2010, 04:36 PM
Hi All,
I did a clean upgrade to lucid 10.04 from Karmic 9.10. After the installation, the boot was stuck at the purple screen with red and white dots.
I did this on Dell XPS M1530 laptop and there was no problem in Karmic.
1. I found a temporary solution. After being stuck here, I simply go to tty1, login and startx. Now, I could work normally but if I go to tty1 and then to 'Ctrl-Alt-F7', I could still see the purple boot screen whereas 'Ctrl-Alt-F8' brings me to the normal GUI. How do I get rid of this purple boot screen ?
Searching on google suggested:
2. Remove 'quiet splash' and instead use 'nomodeset'. When I did this, I got the black screen with the messages during boot but it still got stuck. Importantly, there was no login prompt at tty1 or other ttys. Some messages towards the end where boot got stuck are below. Please help as I did like a fix to this.
-----start messages
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/45-libnjb5.rules:30
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/45-libnjb5.rules:32
/dev/sda9: clean, 259570/1224000 files, 1649804/4883752 blocks (check in 3 mounts)
/dev/sda8: clean, 151452/1525920 files, 3210148/6102684 blocks
init: ureadahead-other main process (1030) terminated with status 4
init: ureadahead-other main process (1035) terminated with status 4
/usr/local/bin/fusermount
Fuse filesystem already available.
Fuse control filesystem already available.
* Starting AppArmor profiles [180G Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
[174G[ OK ]
* Setting sensors limits [180G [174G[ OK ]
* Starting BandwidthD bandwidthd [180G [174G[ OK ]
[33m*[39;49m Speech-dispatcher configured for user sessions
* Starting VirtualBox kernel modules [180G [174G[ OK ]
* Starting the Winbind daemon winbind [180G [174G[ OK ]
* Starting Common Unix Printing System: cupsd [180G [174G[ OK ]
[33m*[39;49m PulseAudio configured for per-user sessions
* Enabling additional executable binary formats binfmt-support [180G [174G[ OK ]
* Starting web server apache2 [180G [174G[ OK ]
* Checking battery state... [180G [174G[ OK ]
----------end messages.
Thanks,
kcn
I did a clean upgrade to lucid 10.04 from Karmic 9.10. After the installation, the boot was stuck at the purple screen with red and white dots.
I did this on Dell XPS M1530 laptop and there was no problem in Karmic.
1. I found a temporary solution. After being stuck here, I simply go to tty1, login and startx. Now, I could work normally but if I go to tty1 and then to 'Ctrl-Alt-F7', I could still see the purple boot screen whereas 'Ctrl-Alt-F8' brings me to the normal GUI. How do I get rid of this purple boot screen ?
Searching on google suggested:
2. Remove 'quiet splash' and instead use 'nomodeset'. When I did this, I got the black screen with the messages during boot but it still got stuck. Importantly, there was no login prompt at tty1 or other ttys. Some messages towards the end where boot got stuck are below. Please help as I did like a fix to this.
-----start messages
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/45-libnjb5.rules:30
udevd[429]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/45-libnjb5.rules:32
/dev/sda9: clean, 259570/1224000 files, 1649804/4883752 blocks (check in 3 mounts)
/dev/sda8: clean, 151452/1525920 files, 3210148/6102684 blocks
init: ureadahead-other main process (1030) terminated with status 4
init: ureadahead-other main process (1035) terminated with status 4
/usr/local/bin/fusermount
Fuse filesystem already available.
Fuse control filesystem already available.
* Starting AppArmor profiles [180G Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
[174G[ OK ]
* Setting sensors limits [180G [174G[ OK ]
* Starting BandwidthD bandwidthd [180G [174G[ OK ]
[33m*[39;49m Speech-dispatcher configured for user sessions
* Starting VirtualBox kernel modules [180G [174G[ OK ]
* Starting the Winbind daemon winbind [180G [174G[ OK ]
* Starting Common Unix Printing System: cupsd [180G [174G[ OK ]
[33m*[39;49m PulseAudio configured for per-user sessions
* Enabling additional executable binary formats binfmt-support [180G [174G[ OK ]
* Starting web server apache2 [180G [174G[ OK ]
* Checking battery state... [180G [174G[ OK ]
----------end messages.
Thanks,
kcn