Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I have three Linux kernels installed: 12, 16 and 17. Kernel 12 and 16 are working fine. But when I try to boot into linux-image-generic 3.0.0.17.20, a red screen appears and after that, nothing happens.

I think this is caused by an update. Here's a screenshot of the updates I applied today:

I'm using Ubuntu 11.10 32 bit. I'm dual booting with Windows 7 64 bit.

share|improve this question
add comment

3 Answers 3

I just had to solve this a few days ago.

When you get to the bootloader (GRUB), and are given the option, pick the one titled "More kernels" or something like that.

Then, once you've done that, pick the one that ends in -12 (or whichever one is lowest) (not recovery).

After that, you should be good to go.

share|improve this answer
    
@CuriousApprentice Now that you have a working system, you should be able to reboot and it'll work. –  jrg Apr 14 '12 at 13:29
add comment

I don't know if this will work, but if it was me I would try uninstalling and then re-installing.

First, boot using the linux-image-3.0.0-16-generic kernel as you have been and open up a terminal (command) window.

Then try to completely uninstall the kernel which will not boot for you using
sudo apt-get purge linux-image-3.0.0-17-generic

I frankly do not know whether removing the kernel headers makes a difference or not. But since I'm somewhat OCD I would also do
sudo apt-get purge linux-headers-3.0.0-17 linux-headers-3.0.0-17-generic

Assuming the above went well I would then try to re-install using
sudo apt-get install linux-image-3.0.0-17-generic
sudo apt-get install linux-headers-3.0.0-17 linux-headers-3.0.0-17-generic

The above is just a guess on my part, but since you say 3.0.0.17 is not working for you anyway it might be worth trying.

share|improve this answer
    
Ok I succeded to remove linux-image-3.0.0-17-generic –  Curious Apprentice Apr 14 '12 at 20:19
    
And when you re-installed it? Were you able to boot with it then? (That's the part I was worried about). –  irrational John Apr 14 '12 at 23:42
    
Nope, I could not. But I found the reason of the problem and its solution. Thanks anyway John. –  Curious Apprentice Apr 15 '12 at 3:17
    
If possible could you update your question (or answer it) with the solution you found to your problem? Just in case it might be of use to someone else who finds your question via a search. –  irrational John Apr 15 '12 at 3:42
add comment
up vote 0 down vote accepted

Okay ! finally I found the problem. The problem does not caused by any updates. The problem was caused by Gparted.

While installing Gparted , never checked the ntfsprogs addon. This ughly addon removes a essential program "ntfs-3g" which gives us the write capability to the windows partitions.

While Installing Gparted I checked "ntfsprogs" and it replaced ntfs-3g. Thats why I could not boot into linux-image-generic 3.0.0.17.30

Now If you have already messed up your system like me, then open synaptic and Install "ntfs-3g". It will automatically remove ntfsprogs and you will be able to boot into image 17 again.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.