Hot answers tagged kernel
You didn't install the kernel source code, only kernel headers (usually ending in .h), which declare kernel interfaces exposed to user space. You can get the kernel source code files (including those ending in .c) by installing linux-source or by downloading the code repository (either through Git or with a click on the “snaphot“ link behind the newest ...
Now that 14.10 has been released, there is an easier and better way to get 3.16 on Ubuntu 14.04: sudo apt-get install linux-image-generic-lts-utopic This package will always depend on the latest 3.16 image available. (This method may not have been ready at the time of this article.)
As to answer why , refer to the file /etc/apt/apt.conf.d/01autoremove-kernels As you can see, apt is told to never autoremove the kernels , as told by another (script) file, /etc/kernel/postinst.d/apt-auto-removal. And here it is: If your script-fu is good enough you could edit it to save only couple kernels, though I can't help you there as my script ...
I suspect that your relatively new device is not covered in the relatively old 12.04 kernel. I suggest you get a temporary internet connection. Open a terminal and run: uname -r Is your kernel version annotated '-pae'? If so, please do: sudo apt-get install linux-backports-modules-cw-3.10-precise-generic-pae If not, do: sudo apt-get install ...
You would probably like to take a look at this article.
I had the same problem and did the following: Boot in recovery mode, kernel 3.13.0-40 sudo apt-get clean; sudo apt-get update sudo apt-get install fglrx (I'm using AMD graphics, so you might not have to do this) and then I was able to boot again (now in .43) :) Hope this works for you
A general recipe to set permissions on kernel modules access is to add a file to /etc/udev/rules.d. For example, you can create a file /etc/udev/rules.d/99-kvm.rules with the following text: KERNEL=="kvm", GROUP="kvm-users"
Only top voted, non community-wiki answers of a minimum length are eligible