Kernels failing to install as of yesterday

[devin-a-hudson]

Here is the pastebin of my terminal output: http://pastebin.com/CfUc3ymr

This install of Ubuntu 14.04 dev was made about a week ago. I don't have any ppa's providing alternative kernels or other major package changes.

Would anyone know how to fix this issue?

Thanks.

[zika]

sudo apt-get update
sudo apt-get install -f
sudo apt-get dist-upgrade

Be carefull when answering to the question for the last command...

[varunendra]

Not sure why this should cause an error -

/usr/sbin/grub-mkconfig: 11: /etc/default/grub: i915.i915_enable_rc6=1: not found

..but try removing that entry from you /etc/default/grub file using a live CD/USB, then try what zika suggested above.

You may also have to do -

sudo dpkg configure -a
sudo dpkg --configure -a

..from recovery mode > root shell, after removing the offending entry from the /etc/default/grub file.

[ventrical]

Here is the pastebin of my terminal output: http://pastebin.com/CfUc3ymr

This install of Ubuntu 14.04 dev was made about a week ago. I don't have any ppa's providing alternative kernels or other major package changes.

Would anyone know how to fix this issue?

Thanks.

  sudo -i dpkg --configure -a

[devin-a-hudson]

Not sure why this should cause an error -

/usr/sbin/grub-mkconfig: 11: /etc/default/grub: i915.i915_enable_rc6=1: not found

..but try removing that entry from you /etc/default/grub file using a live CD/USB, then try what zika suggested above.

You may also have to do -

sudo dpkg configure -a
sudo dpkg --configure -a

..from recovery mode > root shell, after removing the offending entry from the /etc/default/grub file.

These instructions seemed to have worked!

Thank you, and everyone else that offered help

[varunendra]

Glad it worked.

And Thanks for the feedback! It helps not only us build out confidence in a particular solution, but also helps others by indicating which of the suggested solutions worked.

PS:
If you really need that driver parameter, you should be able to add it again to grub now. Or more safely, you can write a .conf file in /etc/modprobe.d directory to load that parameter. That is usually an easier way, but may fail if the driver is loaded BEFORE the files in that directory are parsed. Let me know if you really need that parameter and wish to try the other method.

[zika]

Glad it worked.

And Thanks for the feedback! It helps not only us build out confidence in a particular solution, but also helps others by indicating which of the suggested solutions worked.

PS:
If you really need that driver parameter, you should be able to add it again to grub now. Or more safely, you can write a .conf file in /etc/modprobe.d directory to load that parameter. That is usually an easier way, but may fail if the driver is loaded BEFORE the files in that directory are parsed. Let me know if you really need that parameter and wish to try the other method.

I do find that it is easier and even safer to use parameters such as the one mentioned above in the kernel boot line because, once the need for it die or there is a change that should be made, it is much easier to change it in Grub (on boot) than to get stuck with it and have to do chroot ... Speaking from experience not just from the top of my (almost empty, old) head...

[varunendra]

it is much easier to change it in Grub (on boot) than to get stuck with it and have to do chroot..

Yup, I completely agree, that is an advantage in Grub boot line parameters. Besides, some parameters may not work with the .conf file method at all.

It is just usually easier to tell newbies how to boot with a live media and delete or modify a .conf file, than to explain how to get the grub menu > identify and edit the boot line, and boot. That, plus the two steps (edit /etc/default/grub + update-grub) Vs a single step (echo "..." | tee /etc/modprobe.d/file.conf) while creating it.

PS:
I had actually thought of removing the term 'safer' before posting, forgot it. Thanks, zika, for bringing it up. Going to correct it now.

[zika]

the two steps[/B] (edit /etc/default/grub + update-grub) Vs a single step (echo "..." | tee /etc/modprobe.d/file.conf) while creating it.

With sed (+ tee && etc) even that becomes one-liner...