Ubuntu :: Upgraded System To 10.10 - Does Not Boot Into New Kernel
Jan 8, 2011
I upgraded a PC from 10.04.1 to 10.10 and it will not boot into the new kernel. Because the system started as Ubuntu 7.10, it is using Grub 1.
It gets to the point where it displays "Starting up..." then displays a flashing cursor at the upper left of the screen, it does nothing further.
Yet it will boot into the previous kernel from the 10.04.1 installation, but X will crash if I login using the XFCE desktop, yet it will log into LXDE without a problem.
Is this a known issue (not booting up with new kernel)?
The CPU is an AMD Athlon 32-bit which does have CMOV (per cat /proc/cpuinfo). I have also manually run various apt-get commands to upgrade/update everything, no change resulted.
This the second time it has happened after the security upgrade to kernel 2.6.31-19 with a clean shut down it goes into the grub menu and will not boot.
I upgraded from Ubuntu Desktop 10.04 to Ubuntu Studio 10.04 and running a dual boot system with Windows. On the grub screen there are four listings now for Ubuntu. Two recover modes and two ubuntu modes. Is this normal? Going to reboot and see if I can get a picture of it.
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
I had upgraded to 10.04 but can not use kernel 2.6.32-22.32+, I had to go back to kernel 2.6.31-21. because of the default video driver had change from the one kernel to the other, and I do not know how the correct it. In 2.6.32-22 the font would change and to a smaller size and I can barely view anything because it looks like some two year old puke a box of crayons all over the screen.
Second issue is it does not matter what power-saving mode I am in, in 5 minutes time it with go into suspension. Or right after coming out of hibernate, it will go into suspension indefinitely and no coming out of it and must to a hard boot.
I just upgraded the kernel from 2.6.32-24 to 2.6.32-25. When it was finished it logged me out of XFCE without warning (is that normal)? Now if I try to log in to XFCE the screen goes blank and I just get returned to the login screen. I can log in to GNOME however. I get the same problem if I boot into -24 or -25.
I'd like to upgrade a live ISO file before burning a new CD.
So, following the instructions in "How to Customise the Ubuntu Desktop CD", I chrooted to the squashfs and ran "apt-get update/upgrade/dist-upgrade", expecting apt-get to upgrade the chroot kernel... only to find out that apparently, even when being chrooted, this command upgrades the actual kernel. I guess it makes sense, but I was under the - wrong - impression that chroot would build a filesystem totally isolated from the underneath host.
So I rebooted to use this new kernel:
Next, since the Nouveau video driver requires the kernel header files, I ran the following:
Code:
I don't understand why apt-get upgrades the kernel but won't install its header files.
I'd like to upgrade a live ISO file before burning a new CD.
So, following the instructions in "How to Customise the Ubuntu Desktop CD", I chrooted to the squashfs and ran "apt-get update/upgrade/dist-upgrade", expecting apt-get to upgrade the chroot kernel... only to find out that apparently, even when being chrooted, this command upgrades the actual kernel. I guess it makes sense, but I was under the - wrong - impression that chroot would build a filesystem totally isolated from the underneath host.
So I rebooted to use this new kernel:
Code: # uname -r 2.6.32-24-generic
Next, since the Nouveau video driver requires the kernel header files, I ran the following:
Code: # apt-get install linux-headers-$(uname -r) Reading package lists... Done Building dependency tree Reading state information... Done
System continues to boot OK and everything seems to work fine as I expect. I am not sure what the above causes. It looks related to USB, but I am not sure. lsusb gives:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I recently upgraded my Debian kernel to 2.6.35 via backports and reinstalled my graphic driver. But when I try to use certain apps, it just sits there in the taskbar trying to load for a couple minutes, then automatically closes itself. Specifically I've noticed the nvidia x-server menu and open office doing this, while they both worked fine before I upgraded the kernel. some apps will do this, while others will work fine.
I upgraded to 2.6.35-30.56 last night and now my system's a little flaky. Everything seems to be running ever-so-slightly slower and fullscreen flash is now choppy. The weird thing is the Grub menu upon bootup only shows the latest kernel, but not the previous kernels. Doing an "ls" of the /boot folder only shows this newest kernel. I'd like to revert back to the previous kernel but don't know how.
I;m installing RTAI and I get this message. I can't seem to find the solution, because I really don't know exactly what the main problem is. There are a list of error,s and warnings that I 'm not sure from where should I tackle the problem: Here is what I get when I boot my 2.6.31.8 kernel with GRUB. (I used the RTAI x86 compatible patch):
I just installed kernel version 2.6.26-rc2.5.1, but "uname -r" is still giving me 2.6.36-rc2-5-default. Am I booting with the new kernel? How can I tell? If not, how do I create a new boot option?
each time i upgrade my kernel, my installation of lirc fails to work after the upgrade, and i have to re-compile (against new kernel) and install the lirc modules... which i do via something like:
When I first did my install of Slackware 13.37, I installed the 2.6.38.4 kernel from /testing.
I did a "upgradepkg testing/kernel*.t?z"
Well just now I realized that there was a kernel-headers package in /testing, and I've heard that you should only use the kernel headers that glibc was compiled with.
So did I make a mistake installing the kernel-headers from /testing?
And if I revert back to the stock kernel-headers package, will I have to recompile all the programs I've compiled with the 2.6.38.4 headers?
For portability reasons; I am building a standalone kickstart ISO; based of Cent5.2. I am to the point where I can load my ks file (linux ks=cdrom:/ks.cfg), it reads it fine; and performs the install as I want.
Where I am having a problem; is a good way to have the install use upgraded RPM's, not the base; specifically a kernel with a few needed tweaks in it; which is packaged in an rpm.
I attempted to place my kernel rpm's into the CentOS directory and rerun creatrepo; but I simply managed to corrupt the base repo on the install media.
I have kernel 2.6.26 and I think I need 2.6.27, but update manager says my system is up-to-date. How do I get an upgraded kernel? I have a wireless card but I cannot find anything in the UI to enable it, or connect to my home net. Would Debian come with a connection manager with an oddball name?
I have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update. Anyone else having this problem?
I have updated to the new kernel that was available from 11.2 and now I cant use my system.
It boots up into kde 4.3.5 and then right when its just finishing it freezes everytime and I hear that last tone of the bootup sound ring continually until I force a shutdown. Anyone else have this issue with the update?
i upgraded ubuntu from 9.10 (pretty sure it was .10...) and now my machine goes through the bios and i get a black screen w/a blinking cursor instead a boot choice to ubuntu or windows 7. system worked fine prior to upgrade... reading lots of things it appears i likely have a problem with grub2 (soemone correct me if i'm off base?) so i've been trying to restore and reinstall grub 2 (using this and silmilar threads: [URL]), got frustrated and reinstalled 10.04 over the upgrade install. same blinking cursor... i did the following from this thread: [URL]
[Code]...
i've gotten that response from trying to reinstall/repair grub 2 also. i'm near wit's end and am near completely wiping hdd and reloadng w7 OS.
I have a dual boot laptop with OpenSUSE and Ubuntu. The boot loader used is Ubuntus Grub that came with the Ubuntu installation.
I have done a zypper dup and upgraded to OpenSUSE 11.4. When I reboot my system I can no longer boot into OpenSUSE, Grub says something about a missing kernel.
I think I understand whats wrong here; the OpenSUSE entry in Grubs table hasn't been updated with the changes brought in by the zypper dup (new kernel i guess).
I'm I correct to assume this? How do I fix the problem? Booting into Ubuntu I tried to find /boot/grub/menu.lst to examine it by I cannot find it. I know Ubuntu use a newer version of Grub, does it have a different file layout?
I recently upgraded my system from 13.0 to -current using slackpkg. However, I did not go through warnings on the web regarding the exact procedure to be followed (first running install-new and then upgrade-all). I just did a upgrade-all and then rebooted the system. And then the system would not boot and gives a libblkid.so.1 related error. Upon googling, I found suggestions as to booting from the install dvd 13.0, installing the old version of e2fsprogs and then reboot and doing the neccessary changes [URL]... Me being a linux newbie, don't know how exactly to do these things. Can anybody direct me with the list of commands/things to be done to solve this issue?
I upgraded 9.10 to 10.04 and now it won't boot. The way 9.10 used to boot was after turning on the computer it would go through the bios screen and then a screen would come up and list both operating systems, Windows Xp and Ubuntu. XP would be highlighted and would normally boot if I did not change the highlighted area. If I changed the highlighted area to Ubuntu it would boot into Ubuntu 9.10. Now after doing the upgrade, it gets to the same screen with the two operating systems listed.
When I change the highlighted to Ubuntu an error message is briefly displayed and then it goes back to the screen that lists both operating systems. I think the error message says something like couldn't find Ubuntu, or something similiar to that. Windows XP runs fine when I highlight Windows XP in that first screen, but I want to be able to run Ubuntu. I have Ubuntu on a secondary drive, but shouldn't it have rewritten the upgraded files on that same drive that had 9.10 on it?
i just upgraded from 9.10 to 10.04 and now i cant get win xp to boot. win xp will show up on the grub list but when i select it all i get is a blank screen with a cursor flashing in the top left corner. i dunno whats happend, i have never had many problems with dual boot.
