BT4 will not start up.

Printable View

05-01-2010, 05:38 PM
edwinem

BT4 will not start up.

So I have decided to try out BT4 on one of my laptops. I was able to install it with no problem, and everything seemed to be fine. However, as soon I as try to start up BT4 I encounter problems. The error message i get is FATAL: Could not open lib/module/2.6.32-21-generic/modules.dem.temp for writing: No such file or directory. After a few other messages it gives me a shell with the name (initramfs).

Other information:
My computer is an HP pavilion dv6500.
I know it runs ubuntu since that is what has been running on it in the past.
BT is not conflicting with any other OS since it is the only one.

If you need the full message it says I will type it up. (Is just a little bit long). I also believe the above message is the main problem.
05-01-2010, 07:12 PM
StreaM

Re: BT4 will not start up.

Did you burn it to a DVD? You may need to burn it again. You have to burn it real slow. Like 2x.

Check out this thread.

I’ve just burned my iso and it will not boot?
05-01-2010, 09:21 PM
halfdone

Re: BT4 will not start up.

When you start your computer that have BT4 installed. In GRUB you can choose to start BT4 "Ubuntu 8.10, kernel 2.6.30.9" or BT4 in recovery mode "Ubuntu 8.10, kernel 2.6.30.9 (recovery mode)" try it.
05-01-2010, 09:53 PM
edwinem

Re: BT4 will not start up.

I have tried both the normal boot and the recovery mode. They both give me the same error.
05-02-2010, 08:09 AM
Archangel-Amael

Re: BT4 will not start up.

Quote:

Originally Posted by edwinem

I have tried both the normal boot and the recovery mode. They both give me the same error.

Check the forum faq section for more info on "getting started".
05-02-2010, 05:02 PM
edwinem

Re: BT4 will not start up.

I believe the difference to be that they can not even get BT4 working on the live cd. I have been able to do this. And everything seems to be fine till I boot BT4 from my hard drive after the install. I have done some further research on the problem and it seems to be something wrong with how ubuntu/debian starts up sometimes. However, I can not find a method that can be used to fix the problem.