update to new kernel ,bootup still boot old kernel?
location: linuxquestions.com - date: June 21, 2003
I have a pc dual boot by win2000 boot loader , which the linux that
I am using is Redhat 8 , kernel 2.4.18-14 , I have updated using the
RH up2date , then after reboot (I reboot many times)
it show a information at the Redhet Network Notification Alert that
"Your system is currently running kernel 2.4.18-14, but the newest
installed kernel is kernel 2.4.20-18.8 . It is recommended that you
reboot at the first opportunity to test this new kernel."
I have installed and checked from this update Notification tools as well
as the /boot found the new kernel is installed . But I just can't get
the new kernel to bootup . (I also looked inside the /boot/grub/grub.conf and
found some lines for the new kernel that I installed ,I don't care to make
any changes to it . Because I not sure what those line about. )
title Red Hat Linux (2.4.20-18.8)
kernel /vmlinuz-2.4.20-18.8 ro root
Security update (new kernel) breaks VMWare Player
location: ubuntuforums.com - date: August 20, 2013
So this morning, Software-Updater wants to install security updates, and shows me it will install a new kernel, 3.8.0-29-generic -- so I proceed with the update. Reboot. No incidents.
Then I go to use my computer for some actual work, launch VMPlayer (latest version, 5.0.2), and VMWare tells me it needs to install a few modules into the kernel. Makes sense. Anyone who's ever used VMPlayer has seen this every time a new Linux kernel is installed. So I proceed. VMWare reports errors, can't go on with the install. Meaning, can't use VMPlayer. At all. Same exact behavior under Unity or MATE desktop.
I reboot into the previous kernel, 3.8.0-27-generic. Run VMPlayer. Runs fine. Start an actual VM, runs fine.
On a hunch that doesn't take much genius, I run the vmware installer, uninstall VMPlayer, while still in 3.8.0-27-generic.
Reboot into 3.8.0-29-generic. Reinstall VMPlayer. Now it works. Run a VM, runs fine.
YAY! The old brute-force Windows uninstall/reinstall method w
New kernel 2.6.3711 and today's update
location: ubuntuforums.com - date: December 23, 2010
Things seem to be improving well after todays update. I enjoy moving a window into the left panel and watching it hide. Now I am sure some ccsm changes will break everything, but so far so good.
New kernel computer freezing boot time CPU error message
location: linuxquestions.com - date: June 14, 2012
A few days ago I was messing around with slackpkg for the first time. Along with various other packages, I upgraded the kernel, unfortunately my computer has started freezing when programs max out the CPU, and Im also getting the following error (but only occasionally) in the boot messages:
CPU 0: Machine Check Exception: 004
Kernel panic -not syncing: CPU context corrupt.
I guess there's a strong possibility that this isnt just a coincidence, and that the new kernel has screwed something up.
Am I OK just upgradepkg-ing back to my previously installed kernel? (which was an offical Slackware packaged kernel 126.96.36.199 smp i686)
/boot/ is full, but linuximageserver is demanding to install a new kernel anyway!
- date: December 8, 2011
Hi, server guys! I've got a little problem. Apt-get is demanding that I install the new kernel dependencies for linux-image-server, yet I don't really want to. We're not even running on the other updated kernels its downloaded. My only problem is that I can't just install it and ignore the update, because our /boot/ drive is 100% full (which is another issue). Is there a way to manually remove the old kernels to save space, or just make linux-image-server stop demanding I download a new kernel?
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
linux-image-server : Depends: linux-image-2.6.38-13-server but it is not installed
E: Unmet dependencies. Try using -f.
:~# apt-get -f install
(Reading database ... 94318 files and directories currently installed.)
Unpacking linux-image-2.6.38-13-server (from .../linux-image-2.6.38-13-server_2.6.38-13.52_amd64.deb) ...
dpkg: error proces
3.0.0.06 kernel update from last night = hung boot process
location: ubuntuforums.com - date: July 22, 2011
Running 64 bit version. Did the update last night (21 July) and boot now hangs on Battery state check [OK] in infinite loop.
Booting from previous kernel 3.0.0-5 returns to Unity3d (running on nouveau drivers with no nvidia modules installed/loaded.) Quick search for matching strings here in forum +1 yield no similar problems.
The loop can be broken by simple Ctl-Alt-Del which shuts down process and returns to grub after restart. Only way to get to GUI is via "boot previous linux versions."
Is old config compatible with new kernel?
location: linuxquestions.com - date: October 30, 2011
Is config from older version of Linux kernel compatible with a newer kernel? Would I have any problem if I build new kernel with my old, tailored to my needs config?
New kernel 2.6.3511 will not boot
location: ubuntuforums.com - date: July 26, 2010
Well, with today's new kernel update to 35-11, I can no longer boot Maverick. It just stays on the plymouth splash screen and after 30 seconds or so, all activity seems to stop. I attempted three times.
Any suggestions on how to get around this? Or, just do a full reinstallation from an iso?
GRUB won't boot new kernel!
location: ubuntuforums.com - date: October 29, 2011
So I've installed GRUB2 through Lubuntu 11.10, using Grub-Customizer, to the MBR. Everythings great, it's found all my OS's, no problem.
Now though, one OS (ArchBang) updated its kernel! I've gone back to Lubuntu, used the "update-grub" command, looked through grub-customizer, as well as ubuntu-tweak to delete the old kernels of AB, to no avail. I've been looking but haven't found a solution that works for me -- any ideas? please?
Debian Squeeze failed to boot after new kernel
location: linuxquestions.com - date: October 27, 2012
I have been trying to install Click modular router. For that purpose I installed Debian 6 in virtual box. In Debian I build and installed linux kernel 2.6.19. Everything is done smoothly until I reboot my VM and select Kernel 2.6.19. I get the following message:
Page: 1 2 3 4 5 6 7 8 9 10