News:

Wieners, Brats, Franks, we've got 'em all.

Main Menu

Not booting (UBUNTU)

Started by CrAz3D, May 01, 2008, 07:15:15 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

CrAz3D

It ends flashing the command entry prompt thing.

At one point it says "kaboom" ... no fucking kidding.  I'm on the live cd now, I'll reboot to get the exact error in a bit.

How do I reload the boot files (I think that's what is wrong)?

Ender

Something like that happened to me around a year ago when I downloaded a certain set of updates. I was lazy and just reinstalled. IIRC I didn't get a "kaboom" message though. Maybe that's new.

Did you do anything that could have precipitated it? Did you mess with grub, or even do something as innocent as applying an update? Or did it just come out of the blue?

CrAz3D

oooh, I did update, guess thats possible :(

rabbit

Kaboom sounds like Ubuntu's version of "Kernel Panic" which is super-mega-bad.  There should be messages in /var/log/kern.log, /var/log/faillog, or /var/log/boot.

Ender

maybe the computer saw deep inside craz3d's soul... and died.

c0Ld

Try hitting ESC at Grub and use an older kernel version.

CrAz3D

Quotecommand-not-found crashed
No module named CommandNotFound
Traceback (most recent call last):
File "/usr/lib/command-not-found", line 10, in <module> from CommandNotFound
ImportError: No module named CommandNotFound
Python: command not found
root@UBUNT-laptop:~#


That's what I see.

I cant load an older kernel

Ender

I'll act as translator:

"I refuse to service you while you hunt, drink, and take away girls' virginity."

Sidoh

Is this the error you're referring to in the original post, Crazed?  If so, it's not a big deal.  CommandNotFound is a python script that searches the package lists for a command that wasn't found in your path.  Ubuntu automatically executes it with the command you tried as an argument when it doesn't find a command you type.  It's crashed on me a few times too, but it's a pretty rare occasion.  If it happens regularly, you're either using an outdated version or you've found a bug.

If this isn't the error you were originally referring to, I think we'll probably need some more output before we're able to determine what's going on.

CrAz3D

Thats the original error.

It doesnt load gnome after that point.

pxc

If you're getting dropped at a root prompt, it's not a kernel panic, but it does sound like X isn't loading. Try running "startx" from the console it drops you to and press enter. If that fails, chances are your kernel got upgraded but your video card's driver modules did not. If that's the case, here's how I would fix it from that root prompt.

apt-get update && apt-get upgrade
if that doesn't do it, try using DPKG to rebuild your kernel modules. If you have Nvidia, do dpkg-reconfigure nvidia-glx-new

If you have an ATi card, try dpkg-reconfigure xorg-driver-fglrx

I also noticed the existence of nvidia-glx-new-envy and xorg-driver-fglrx-envy packages, so if the above doesn't work try installing or reconfiguring those.