Feisty boots slowly

Another thread, another problem...

Ubuntu has been slower than usual in terms of booting up; something I was already trying to solve. Now it takes 2 minutes to boot Ubuntu where it takes XP less than 45 seconds.

The problem has to do, I think, with the KDE service kinit. I have Amarok and JuK installed, both of which are great programs. At first with JuK I noticed that in order to run KDE programs, Ubuntu had to keep KDE processes running alongside GNOME, but at least there weren't any problems. But after installing Amarok, the problem has become more noticeable.

I did some reading around and someone advised pressing CTRL-ALT-F1 during the Ubuntu bootsplash. The boot hanged for a loooong time on the following line:

"kinit: no resume image, doing normal boot..."

So it seems that the KDE service responsible for starting up KDE processes is trying to do the booting, but it just fails. What I'd like to figure out is how to stop this and get rid of all KDE processes until I actually need to use these two KDE programs.

 

Run fsck from a Console through a LiveCD

Code:

#fsck -yv /dev/XdY

where X and Y need to be known by you for your root fs.

 

kinit is kernel init, it has nothing to do with KDE. I'm not schooled in Suspend, but I think it has something to do with that. There is a bug, though, and here's a forum thread.

Actually, it may be network related, check the third page of that forum thread.

 

There doesn't seem to be a tried-and-true solution for this bug... probably b/c so few people have encountered it or noticed it before.

Guatam, what does that command do? I'd like to know what a command does before I use it, especially when it concerns the kernel. That's experience talking.

 

I just have all the interfaces in /etc/network/interfaces commented out. The knetworkmanager program will enable them as I need them. You are probably running into a long timeout with a failing DHCP attempt.

 

Eh? You think I gave you like a self-destruct command or something?

fsck is a Filesystem check. It's a good tool, and runs on it's own every 30-33 mounts of your root fs. Sometimes stuff gets corrupt, and it fixes it. Think of it like Windows ScanDisk, except that it's NOT the same.

BUT I mention to run it while on LiveCD because you DON'T want to run it while your root fs is mounted. Being logged into X and having access to the partition with the fs means you are mounted. fsck runs pre-mounting every 30 boots, so to emulate that, use the LiveCD.

 

ok, today i think i figured it out. this only works on the PC's first startup from being off, and not a restart. This time i had my Wifi switch turned off and it didnt hang/stall half way through the splash screen as it normally does. I flipped the wifi on button once my desktop was up and keyring manager poped up, put password in like normal and was away.

I think its a DHCP think too. I'll set my IP to static and see what happens.



EDIT: ok that didnt work, yeah maybe it is looking for some resume image? like a hibernation file.... which would explain why my pc's first boot of the day into ubuntu is quick, and restarts are slow.

Insane