Whenever Update mgr updates the kernel, on reboot I get the following error for the new kernel.
Bad or missing file.
Using grub, select the previous kernel. Boots fine, even though I would have gotten the same error after that kernel update. I always have to use grub to select the last kernel.
always after runnung ubuntu for a few days, I get the problem that the kernel gets a problem with my home partition and remounts it readonly. I actually cannot remount it readwrite again, but have to reboot the system. This rebooting causes some orphaned inodes to be found on the reboot, but I cannot determin any errors on the harddisk. No errors in SMART, etc.
I'm not sure exactly when this broke. I had no problem with audio cds before with Fedora 11. I normally just rip new cds and play from the HDD encoded file. I believe the last time it worked was earlier this week. Now all of a sudden when I load either of my DVD-ROM or DVD-RAM with an audio cd it reads it and then does not mount it. I have no problem with DVDs or Data CDs or Data DVDs.
So, im now using slackware 64b - current to Mon Jun 10 21:51:54 UTC 2013, which contains the 3.9.5 kernel, and i noticed that there have been some updates in the current ftp that contains version 3.9.7, my question is, if i update to current what happens to the kernel version im currently using, is gonna be replaced entirely or is gonna be saved somewhere, and what will happen to the AMD driver th
I've just upgraded the linux kernel from 3.4.6-2 to 3.5.0-2 and am now unable to boot the new kernel. The boot process ends with the following message displayed:
fixing recursive fault but reboot is needed
If I reboot the machine I get the same message. I can still boot into the the old kernel with no problem.
After install of F16 all was well but ran a yum update and rebooted to the newer (3.4.xxx x86_64) kernel and screen goes blank after grub menu. Could choose the original F16 (3.1.xxx_x86_64) kernel at grub and it would boot fine.
I decided to give F17 a try...
After a clean F17 installation all is working fine... Then run yum update and reboot into latest kernel...