I am reeeeeeallly sorry to return to an issue that so many unsophisticated users (like me) have struggled with.
If I wanted to update programs but NOT update my kernel as I have an old laptop and worry abt newer kernels) how would I stop the kernel updating.
Hi, thanks for the quick reply!Like I said, I have no problems with installation and use on standard kernel. However, during installation on LTS kernel, I get errors while compiling kernel modules. I am told to check "/tmp/vbox-install.log" to find out what went wrong. This is the message :"Makefile:90: *** Error: unable to find the sources of your current Linux ke
The most recent update fails after updating to kernel 3.2.0.25.27. I get "Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" when booting.
I can successfully boot by choosing a previous kernel from grub.
How do I fix the update? do i just uninstall and reinstall the kernel?
To make a long story short, I added the rpmfusion repos so that I could install the nvidia drivers and downloaded whatever updates appeared. Initially after rebooting, I kept getting "No root device found" which I've managed to solve but now it keeps locking up after "Starting atd".
The developers behind the Tails project proudly announced on November 13 the immediate available for download of the Tails 0.14 Linux operating system.
Tails 0.14 is powered by Linux kernel 3.2.32, which offers support for multi-core CPUs and more than 4GB of system RAM.
"Tails, The Amnesic Incognito Live System, version 0.14, ... (read more)
On Saturday I ran online update, which included a kernel update (now 2.6.31.8-0.1.1 x86_64). Afterwards, I set out to recompile the VMWare module, as is always required, but it complained about not finding the kernel headers for the "desktop" kernel.
Kuno wrote:You know, you could just enable the liquorix-repos and install the latest liquorix-kernel, which is: 3.8-4.dmz.2-liquorix-amd64. Siduction is much better. They store all their kernels for a long time, so it`s possible to upgrade in steps and revert back to the last one that worked, when and if you get to a kernel that introduces new issues, like all 3.7 and 3.8 kernels do for me.
Hi,
(apologies if this duplicates something else - I have had a good search, and none of the other threads / "solutions" I've been able to find matches my issue or works for me)
I have not been able to run any of the new kernels since 3.3.4-5.
Email this page
