werdberd
November 9th, 2009, 05:13 AM
So as of a few minutes ago I have a freshly upgraded and newly non-functional Ubuntu 9.10. Grub loads and then usplash comes up, but instead of the pulsing white Ubuntu logo you'd expect it's just like a static image with no animated pulsing. After about 30-45 seconds usplash disappears and all that's left is a blinking cursor in the upper lefthand portion of the screen. No hard drive activity, it just sits like that forever.
Loading a kernel in rescue mode gets me to a text-based login prompt where I can login and attempt to start gdm. When I do this I'm told gdm is started/running only gdm never actually comes up and it's not in the list of running processes. Anyone have a clue what's going on here?
edit: Okay so I just tried 'sudo /usr/sbin/gdm' for the heck of it and gdm came up. Before I was trying 'start gdm' which did not a whole lot. I logged in and aside from sound being muted (still works after unmuting, thank goodness...) everything was pretty much in working order. But why on earth is usplash seemingly hanging the boot process and gdm not coming up when using 'start gdm'?
edit 2: In trying to get my system to actually boot properly using the default kernel entry, I thought it might be a good idea to get the kernel command line as close as possible to that of the one used in the rescue mode. So the only real difference is that when I remove 'resume=UUID=7ae6109b-6d75-4e93-93d4-0466804c97b4 resume_offset=557056' from the line of kernel parameters the system boots up normally and when it's not removed it just hangs at usplash. None of this makes much sense because I was using Grub2 on Jaunty before I upgraded to Karmic and everything was fine. Now unless or until this is fixed I can't resume from hibernate...
Loading a kernel in rescue mode gets me to a text-based login prompt where I can login and attempt to start gdm. When I do this I'm told gdm is started/running only gdm never actually comes up and it's not in the list of running processes. Anyone have a clue what's going on here?
edit: Okay so I just tried 'sudo /usr/sbin/gdm' for the heck of it and gdm came up. Before I was trying 'start gdm' which did not a whole lot. I logged in and aside from sound being muted (still works after unmuting, thank goodness...) everything was pretty much in working order. But why on earth is usplash seemingly hanging the boot process and gdm not coming up when using 'start gdm'?
edit 2: In trying to get my system to actually boot properly using the default kernel entry, I thought it might be a good idea to get the kernel command line as close as possible to that of the one used in the rescue mode. So the only real difference is that when I remove 'resume=UUID=7ae6109b-6d75-4e93-93d4-0466804c97b4 resume_offset=557056' from the line of kernel parameters the system boots up normally and when it's not removed it just hangs at usplash. None of this makes much sense because I was using Grub2 on Jaunty before I upgraded to Karmic and everything was fine. Now unless or until this is fixed I can't resume from hibernate...