I updated my kernel from 2.6.38-8 last week via the Update Manager. Now my IBM Thinkpad Z60t just sits there with my Caps Lock indicator blinking below a black screen if I try to boot into Linux 2.6.38-10. I can go to the "Previous Versions" sub-menu, click on "Linux 2.6.38-8" and it boots just fine. I'm running Xubuntu Natty.
No kernel updates available since this happened..
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
[root@noname boot]# uname -r
2.6.18-164.11.1.el5
My /boot/grub/menu.lst looks like:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I can't see anything wrong and I did not change/try anything.
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 used dual boot system (xp + ubuntu 10.04) and decided to replace them with jolicloud os and then it started In about 86% of jolicloud install it showed me error of hdd partition. I tried different versions of partion type, used also option to install on entire hdd - none of my tries actually worked (also with many hdd formating tries) so I was able to use only usb as live user for Jolicloud, and i burned ubuntu iso on disk - on boot up showed boot up error, i checked BIOS and everything seemed to be ok with boot order. So after many tries i took my old Gutsy Gibon 7.10 live cd. I first updated it with LTS version (8.04 Hardy Heron) and after that I updated it to 10.04 but it seemed to not finish when i saw some error in terminal and installer was exiting 13 minutes before finish then it had kernel panic - fuuuuck! After that i tried to download small versions of linux like Austrumi and puppy linux , but it showed me boot error or cd didnt even open install dialog without showing boot error.
View 1 Replies View RelatedThis 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.
View 9 Replies View RelatedI installed mythbuntu from a live CD on an old machine with an IDE hard disk just to play with it. It worked a treat, so I bought an Acer Aspire Revo R3610 and used dd to copy the old HD contents to the new one, and then gparted to resize the ext4 partition.
On boot I got - Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
I checked every grub2 command and it all looked fine. I then tried booting the original kernel that the live CD installed (2.6.31-14) and it booted! I tried 2/6/31-17 again, and got the panic.
After much googling, I found a suggestion to do - sudo update-initramfs -k all -c -v and this worked.
Is this expected behaviour? One of the delights of Linux is that installs move smoothly between machines, but this one didn't. Was this due to the old machine using IDE and the new one AHCI SATA? How do I get an initramfs that's flexible and will boot smoothly on any given hardware?
New kernel Fails to boot. video driver is current and I tried reinstall . The .19 Kernel works fine
View 2 Replies View RelatedI recently updated the kernel of lucid from 2.6.32-22 to the ""-23 release through update manager. Now whenever i try to boot the new kernel from GRUB the screen goes black and the computer stops responding with the caps lock and scroll lock lights flashing on the keyboard.
I can still boot into ""-22 fine and keep using ubuntu.
My first thought that the problem was the newer kernel itself so I tried to update to 2.6.33-5 from [url]but the same boot problem exists within this one also.
Because it goes straight into the black screen after GRUB I have no way of telling what has happened without error messages. Would this appear in any log files and if so which ones?
Had an issue after update in the nvidia module was not loading, after much messing about i found that system had installed kernel 2.6.32-24 but this had been added to grub even after running update-grub even though kernel was in /boot ?
It was booting into 2.6.31-17 fine
i removed 2.6.32-24 with apt-get remove and then reinstalled.
Now on reboot i can menu entry for 2.6.32-22/24 and 2.6.31-17 but none will load, just error 15 file not found?
I had done the upgrade from 10.04 to 10.10 online and couldn't boot to newest kernel and had to select the previous one in GRUB. From what I have read it may be because of NVIDIA drivers or some conflict. Anyways,I did a fresh install of 10.10 from the Live CD overriding my 10.04-to-10.10-online-updated partition so I do not have an option to boot older Linux kernels now. I was wondering if the Live CD could be used to install any previous linux kernels for the new installed Ubuntu 10.10 system.
View 8 Replies View RelatedI recently upgraded Linux kernel headers for version 2.6.35 on x86/x86_64 from 2.6.35-22 to 2.6.35-23. and my system will not reboot to the upgraded kernel. To reboot I have to force shutdown my Toshiba L-450 laptop and the restart. This brings me to the GRUB screen were I can choose to use the previous 2.6.35-22. Normally do not see the GRUB screen as I am only running Ubuntu 10.10 64 bit on this computer. I have tried reinstalling linux-headers-2.6.35-23 and linux-headers-2.6.35-23-generic and got the same result.
View 4 Replies View RelatedI couldn't get 10.10 to boot (live or after install). I was able to install and boot 9.10 normally. Then I ran upgrade to 10.10 and I started getting the same problem trying to boot as with 10.10 disk. I found I could boot with 2.6.32 left from 9.10 but it will not boot 9.6.35 kernels. On a normal restart when automatically trying to boot the latest 9.6.35, I get this message before switching to an unresponsive black screen with no further hard drive activity:
GRUB loading
syntax error
Incorrect command
syntax error
error: file not found
[Linux-bzimage, setup=0x3400, size=0x420c50]
[Code]...
I have been searching for a solution and so far have not found anything that worked. I'm a pretty basic user so I'm not sure what is going on.
How do I remove the extra Kernels from my boot menu as listed below?
View 3 Replies View RelatedUpdate manager reported some updates including kernel update to version 2.6.31-19.
after update system won't boot. it crashes into bash shell. I've manually loaded kernel version 16 with following command code...
same thing happened when version 17 came up. I definitely NEVER again going to update kernel. What do I need to do now? should I uninstall latest kernel...if that is possible?
After getting everything running nicely on 10.10 (after dozens of installs - long story, partially raid problem, partially noob, partially partitioning and Windows), I'm stuck with an unbootable 10.10.I selected all the "important security updates" when the update manager told me I needed to update everything. Upon rebooting, and picking ubuntu in grub, I get:
Error: unknown command 'record fail'Error: cannot read the Linux header Error: you need to load the kernel first Not exactly sure why at this point. Can anyone point me in the right direction? I can probably get in either through a 10.04 version that I have on another HDD, or through the livecd.
Note: if it's important, I did not elect to install the ATI proprietary drivers, and this is also the first update that I've done after installing medibuntu - a few boot cycles in between, so I don't think it's related.
I've been trying to get Ubuntu on my beloved 4 year old Acer desktop that's been chugging like a tank. However, after either a fresh install or upgrade, I would get the following error:"Kernel panic - not syncing: VFS: Unable to mount to root FS on unknown-block(0,0)".I've looked here and there, and one of the issues it would seem is the kernel not recognizing my hard drive if I'm correct. One of the suggestions was to upgrade the kernel however, I have no idea how to do such a thing if I can't get into the OS.
View 9 Replies View RelatedI had problems with booting my PC after kernel updates several times. In the past I just reinstalled Ubuntu and after several tries with running Update Manager things were working again.This time I applied another recommended set of updates, including a kernel upgrade and got the usual "Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)"After booting from a LiveCD and running boot_info_script I rebooted again and this time I am getting tons of errors which seem to be generated while running grub. After a few minutes of 'error: syntax error' and 'error: Incorrect command' scrolling through my screen, grub gives my a grub> prompt... Not what I expected!Here is the output of the boot_info_script:
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for (,msdos1)/boot/grub.
=> Grub 2 is installed in the MBR of /dev/mapper/isw_cagifdjehe_Volume0 and
[code]...
I have two RAIDed disks (mirrored and showing OK during POST). The disk shows above as a6071eb5-6fc6-45b3-babb-c1a2156278d7. Ubuntu 10.10 installs fine from a LiveCD, but gets broken by kernel updates. I can see the original 1 TB disk when I start with the LiveCD and I can access all the files.
After a kernel update ubuntu would not boot. So found this procedure using the live update cd. Update grub.cfg & delete everything down to but not including the first line that starts with 'menuentry' . Then boot works ok. A couple of weeks ago it started on my notebook. Is anyone @ hq listening & able to fix this problem permanently?
View 9 Replies View RelatedI have just installed Ubuntu 10.04 where kernel 2.6.32-30-generic-pae is default. Also installed the latest stable kernel version 2.6.38.3
I need to have the latest kernel version in boot screen without affecting the older. What are all things I need to update ?
this is a new problem with issues that started when I upgraded to 10.10. Originally, GRUB wouldn't load after that upgrade, but that was fixed here. Once GRUB was working properly, there was a problem with the 2.6.35-28 generic kernel. When I tried to boot through it, I would only get an ubuntu command line.
Luckily the older 2.6.32-22 generic kernel worked just fine and I could log in and load my ubuntu desktop with no issues. I decided to upgrade to 11.04 to see if that would correct whatever was going on. The installation was completed without any apparent issues, GRUB works, XP Pro works, and the older 2.6.32-22 generic kernel allows me to boot into 11.04.
Unfortunately, another new kernel, 2.6.38-8 generic, is not working properly. I snaped some pictures of what happens when I try to use this kernel:
[URL]
The first is GRUB/ The selection The second is the loading graphic The third is a command line where it freezes (note: this is not the same command line screen/environment that I was referring to with the 10.10 new kernel)
Here's the deal: I've done a fresh F12 install on my T61. Told the installer to Encrypt the Hard Disk. The installation went fine. The kernel was 2.6.31.5. I ran a yum update, which added another kernel - 2.6.32.11, but I can't boot from that one. The newer kernel throws a an "Uncompression error -system halted" immediately.
View 3 Replies View RelatedI used the update manager to update the kernel and whatever the other recommended updates were yesterday. I shut the computer down overnight and now when i try to boot into Ubuntu 9.10 i get a basic grub shell and when i try commands like "boot" it tells me there is no kernel loaded. I installed Ubuntu with Wubi so it is a dual boot system.
I've tried to access the Linux volume with a live OpenSuse 11 CD but there is no device to mount. It sees the entire hard-drive as if it hasn't been partitioned. I don't necessarily need to fix the installation. I just need to get my files back.
I seem to have determined a few other things about my "only gets as far as a GRUB command line" problem:To recap, sda3 (GRUB hd0,2) is the main Linux partition; sda9 (GRUB hd0,8) is the boot partition.GRUB is 0.92.Installation was from an 8.04LTS live CD (at least, that's what the envelope says it is)/"/boot/grub" (i.e., "/grub" on sd9/hd0,8) contains a "menu.lst" file. I modified it (had to do a "sudo gedit" from a command line!) to (1) comment out the line that hides the boot menu, (2) change the timeout from 3 seconds to 90, and (3) add a menu line based on my succesful manual IPL of DOS.
It still boots to a GRUB command line. If I do a "configfile /grub/menu.lst," a boot menu comes up. DOS will successfully IPL, but Linux still gets a "no setup signature found," (ditto for "recovery mode"), which suggests either a bad kernel, or a kernel that's too big for the GRUB to handle.Why would it be finding its way to grub, but not finding the boot menu file?Why would the live CD come up just fine, yet the GRUB and kernel it installs fail?
I'm currently running Karmic 9.10 in dual boot with Windows 2000. My computer has automatically updated and installed kernels 2.6.31-17, -19 and -20 (They show up in Synaptic as installed).
However, the newest kernel choice in my GRUB menu is 2.6.31-16-generic (followed by -15 and -14). These all start without any errors.
Question: Why haven't the newer updates shown up in GRUB for booting purposes?
Could it be a question that I didn't answer correctly some time back about accepting or not accepting an update or change in GRUB?
How can this be changed? The new kernels do not show up in Start-Up Manager either.
I have winxp and ubuntu 10.04 dualboot. They were working ok. Today I removed old *21 kernel image and headers so grub updated the confs. That's all I did that could cause the win no longer boot. It starts booting, the screen goes black and the PC reboots. I tried safe mode, it started to load some dlls as it usually shows in safe mode but then still reboot.
Code:
$ sudo fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[Code]....
I am using Ubuntu Lucid Lynx 10.04 (64 bits) in my Asus U30JC laptop (Core i3 M350, intel 4500MHD + nvidia 310M with nvidia Optimus, 4GB RAM). I am content with Lucid and I don't want to upgrade to 10.10 for now. However I read that the new 2.6.36 kernel has some good improvements, such as improving system interactivity while intensive I/O (such as copying large files), and improved energy management for i3/i5 processors (which I hope translates into more battery time, which is a problem of Ubuntu vs Win7 in my laptop).
I discovered I had 2 options: compile the kernel myself, or use the Ubuntu Kernel PPA (maintained by the Ubuntu Kernel Team). I decided to use the PPA, so I added it to my software sources and installed the generic"linux-lts-backport-natty" kernel (2.6.36-1).
Package installation went fine, and after reboot, I could log in to the desktop no problem. Everything seemed fine, but after a few minutes, the system freezes completely: mouse did not move, none of the indicators moved, even Ctrl + Alt + F1 did not work.Where is the log file where there might be a message related to the freeze? Do you think that the kernel developers would try to fix a bug that probably only affects people running the 2.6.36-1 kernel on a distribution that was not built around it?
I just upgraded to 10.10 and now I am faced with a choice at boot up of which kernel I would like to boot (or recovery mode, or memtest).I am wondering how to default to the newest kernel without this prompt.
View 6 Replies View RelatedI've been running Ubuntu 10.04 AMD64 on our home theater PC through a wubi installation. Yesterday the system update installed a new kernel and today there is a problem booting the computer so I'm reluctantly using Windoze to type this. there isn't much information: the computer has always booted fine before the kernel update. When I select Ubuntu in the boot menu the screen goes black and the computer restarts. No error messages, no GRUB menu, just a blank screen before restart.
Computer: Dell Hybrid 140G, Intel Core 2 Duo T5800, 4GB RAM
I have Ubuntu 10.10 installed on my laptop.Its a dual boot with XP, have been using ubuntu/xp for a while now..Till now i always used to remove older kernel images after ubuntu update, then update grub and do "sudo apt-get autoclean" never had any problem at all.i skipped the second step, i removed the old kernel image and did "Autoclean" on apt-get but forgot to update grub.
Now after i have reboot, when grub loads i can see only 2 "Memtest" lines in grub list and 1 "windows xp" line.the "Linux kernel generic" line is missing. I can boot in xp (have done just that to post this) but since there is no line in grub list to boot into Ubuntu, cant boot in Ubuntu.Is there any option, something i can do at "Grub" to boot into Ubuntu?
I just upgraded to Fedora 12 x86_64 via yum upgrade. However I have problems with booting. The new FC12 kernel won't boot. Boot output is something like
Code:
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sda to RAID set "sil_ajabaccaaidg
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sdb to RAID set "sil_ajabaccaaihe
No root device found Boot has failed
I resized boot partition to 400MB, formatted it as ext4 and recopied all files, modified fstab to update boot partition's UUID. Tried to set a boot flag on boot, still, I can only boot with the old kernel from Fedora 11. Is it a Fedora 12 kernel's bug or something wrong with my setup? I don't use any RAID, and the sil error is present with Fedora 11 kernel also.