Fedora :: Kernel Update Hangs System During Boot / Solve It?
Sep 4, 2010
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?
The most recent kernel update, to version 2.6.38-11 has been a horror. It hangs on boot up. Sometimes I can get to the log in screen, then it hangs there as well. However, after 3-5 reboots (which is absolutely annoying to do when I just want to use my computer), it sometimes loads up finally. However, if I go to older Linux version in the Grub menu, then I can select 2.6.38-10 and it runs just fine.
So I am looking for a way to fix this problem, whether it be removing the most recent kernel update, or making 2.6.38-10 boot up by default. I noticed that the kernels are listed in the synaptic package manager, but I am afraid to remove the most recent one via synaptic. Is it as simple as removing the Linux version and headers I don't want, or are there other things I need to do in order to make 2.6.38-10 my default kernel at start-up?
I did a fresh install of Ubuntu 10.04 on a desktop. I then did the system updates and on the reboot the system now hangs at the splash screen before the login screen. I only get a blinking cursor on the text-based terminals. I don't see the grub menu, I assume because Ubuntu is the only OS on this machine. So I can't boot to single user or text-only mode.
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 installed lucid the other day on my laptop, the first time it booted after installing it gave two error messages (unfortunately I can't remember what they said). The errors stopped appearing after that but once I select Ubuntu from the boot menu, it just hangs on a black screen for a good 15 seconds at the least before it runs the plymouth screen for like 2 seconds (the progress bar is already full) and then goes into the login screen. Here is my boot chart:
http://akgenome.com/files/bootchart.png
I was wondering if anyone can tell from that what is causing the issue and perhaps how to fix it? The boot log is like 3 lines long and is completely normal.
I am unable to boot with kernel 2.6.35.13-92.fc14.x86_64 which was installed while applying software updates. It hangs with the last message issued "Registering binary handler for Windows Applications". Searching led to it being related to a problem with the nvidia drivers. I followed the directions in several posts - delete /etc/X11/xorg.conf, reboot, run nvidia-xconfig, reboot and all is fine, but not in my case. The first reboot works but the screen is wrong. There is a 1 inch wide black border around the presentation window. If I then do the nvidia-xconfig and reboot, i am back to where I was before - boot hangs after issuing "Registering...". If I boot to the last good kernel, everything works fine. This happened to me once before and I was able to fix it by rebuilding the nvidia kernel (I think that was what I had to do), but I can't find out how to do that. I have akmod and kmod installed which are supposed to take care of this problem. I booted to kernel 13-92 recovery mode, deleted the xorg.conf file and ran nvidia-xconfig from there. Still fails. I don't know what to list here, but I will do my best to supply whatever is necessary.
I have just made a clean installation of FC12. The only change I have made for now is to disable the NetworkManager and set a static ip address. My problem is that when I click "shutdown" it doesn't complete the shutdown and hangs due to some kind of kernel error. Then I have to use the power-switch to shut it down. It doesn't happen every time, but it happens often (every 3rd shutdown or so).
I get this error-messages on the screen: Code: Unmounting file systems:[OK] Halting system... --------[ cut here ]----------- kernel BUG at kernel/time/clockevents.c:262! invalid opcode: 0000 [#1] SMP last sysfs file: /sys/mmodule/ip6_tables/refcnt Modules linked in: {long list} Pid: 1809, comm: hal Not tainted (2.6.31.12-174.2.22.fc12.i686 #1) OptiPlex GX270 This is exactly whats described here: [URL].
Ran the updater, went to boot to Win7 to use Photoshop and realized that the grub menu was gone. Ubuntu boots by default now. I tried running "sudo update-grub" at a virtual terminal and while it listed the various linux kernels ok, it then got caught in a loop spitting out some crazy looking errors. I rebooted and Ubuntu came up fine. I tried running "sudo update-grub" again from the gnome terminal and it hangs the whole computer for a few minutes and finally gives me this:
Have had a clean perfectly working copy of 2.6.31.6-166 for months and after two updates to 2.6.31.12-174.2.3 and 2.6.31.12-174.2.19, neither of the newer kernel versions will allow machine to boot properly. Start-up hangs at the preload daemon with a flickering screen. To use machine, must use grub chooser and choose the original base kernel.
Running on Tyan h2000m board, opteron 2356, Nvidia 9800 GTX+ and 12GB of dram with SELinux security enabled.
I just installed Ubuntu Lucid yesterday, and I'm dual-booting with Windows 7. (They're on separate physical drives if that's relevant.) I've discovered that whenever I restart the computer, it doesn't matter if it's from Windows or Ubuntu or just hitting the reset button, it hangs at "Loading Operating System." If I start it cold, though, it usually works fine. I tried Googling but I couldn't seem to find anybody else with this problem. I'm guessing it's a GRUB problem? Does anybody know how to fix it?
Can't boot after upgrade to 2.6.31-19 kernel. Boot procedure stops on "Mounting root file system..." stage with message: /init: line 218: syntax error: 0xhda1.
Linux distro: Mandriva One 2010.0-KDE kernel(after update):-> 2.6.31.12-desktop586-1mnb Pentium 4 3.4GHz
Used to boot to kenrel 2.6.31.6 for the past 2 months updating my system whenever i was asked to-NO PROBLEMS so far(till yesterday in fact)Mandriva yesterday, offered a list of system updates including the kernel 2.6.31.12 and the respective Nvidia drivers.Boot to that kernel computer reacted as usual and everything seemed to run properly. HOWEVER,when i tried to shutdown the system everything powered off(hdd-keyboard) except the CPU(and the power supplier).I restart(manually) the system boot in and try to reboot it-NO Problem-logout NO Problem but FAILED TO SHUTDOWN PROPERLY AGAIN.
I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
I've run today command: "sudo yum update" and I've noticed that the new kermel have been installed (2.6.31.12-174.2.3.fc12.x86_64). After that installation .. my camputer has several errors while booting and it doesn't want to start. So while booting I can see Code...
I ran the update through yum (replicated results twice) and whenever I boot to the new kernel it either freezes on the F logo or screen goes black right after f logo. No commands work whatsoever (tried em all). I can boot to an older kernel (2.6.33.3-85.fc13.x86_64). the ones that fail are: 2.6.33.6-147.fc13.x86_64 and 2.6.33.6-147.2.4.fc13.x86_64.
The Fedora error system gave me a bug report I submitted, here's what I got:
Package: kernel Latest Crash:Tue 03 Aug 2010 09:46:33 PM Command: not_applicable Reason: BUG: unable to handle kernel NULL pointer dereference at 00000000000005b8 Bug Reports:Kernel oops report was uploaded
After updating my kernel from 2.6.34.7-56.fc13.i686 to 2.6.34.7-61.fc13.i686 I can't boot anymore. The error message says: "No root device found Boot has failed, sleeping forever." I'm booting from 2.6.34.7-56.fc13.i686 now but I would like to sort this thing out. What should I do? File a bug? I never did that, so I don't know where to go.
After running update last night from 2.6.35.9-64 to 2.6.35.10-68 my laptop fails to start. Boot process goes most of the way to startup and then hangs just before login screen. Not sure what else to give as far as info.
rpm -ivh kernel-2.6.29.6-217.2.16.fc11.i686.PAE.src.rpm error: open of kernel-2.6.29.6-217.2.16.fc11.i686.PAE.src.rpm failed: No such file or directory
rpm -ivh kernel-2.6.29.6-217.2.16.fc11.i686.PAE.src.rpm No package kernel-2.6.29.6-217.2.16.fc11.i686.PAE.src.rpm available.
The best word that suits me to introduce is I am a novice! :-) but it is the difficult part get over with the new things and learnings!
Well once such situation made me introduce me to you is "Kernel Crash". I've recently installed Fedora 14 64 bit version on my HP HDX premium series, since then this Kernel crash is chasing me down! code...
I have recently updated my Fedora 11 installation which replaced my older 167 kernel with the newer 217 kernel. However, the 217 kernel will not boot completely. It will show the splash loading screen, and then will switch to a rapidly blinking cursor. This cursor blinks for about 5 seconds and then disappears. I can access terminals using ALT+F2, etc. I can log in to these terminals, but init commands do not complete (something about a binary handler). I'm not sure if something is conflicting with an update to X or what is wrong. The most recent kernel that I managed to get to work was Kernel 167, however I cannot find this kernel for download.
Sys info: AMD Athlon 64 X2 4800+ 3GB RAM nVidia GeForce 8600GT with proprietary drivers 320GB Hard Disk with windows and linux partitions Fedora 11 32-bit i586
I tried to update my f12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK but when I restated my computer it spit up an error and wouldn't boot"Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory"Luckily the old kernel still works.
I do have the disk encryption set, could this be related to that? Updated my laptop today with the xx.6-145.f12.PAE kernel and now it's borked to. Same problems.12/07/2009OK today's kernel update seemedto fix the problems and now all is well, execpt for my inkscape not working problem. But I put ubuntu 9.10 in a VBox and it works. So for now that's my work around.
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
Hello, i recently update the kernel in fedora through the GUI update manager and after restarting the new kernel wouldn't boot and i had to reboot into the old one. it freezes right after Plymouth finishes and the login screen should show up it just completely freezes, i do have proprietary nvidia drivers could it be that?
I upgraded the kernel of my machine with a yum update, and now it will not boot. I am running Fedora 14 on a 64 bit machine. I really really need it to boot. Help!
I did Ctrl+Alt+F2 and managed to log in. I have kernel x86_64 2.6.35.12-90.fc14 installed. How do I log in as usual? I never get to a login screen.
I have just updated my kernel to version 2.6.38.8-35 in Fedora 15, it now refuses to boot that kernel. I just get a lot of text on the screen and nothing happens. I can ctrl-alt-fn to get to a prompt, but I do not know how to fix the nvidia problem.
When I edit Xorg.conf and replace 'nvidia' with 'nv' the new kernel boots but only to fallback mode, trying to then re-install the nvidia drivers shows them to be already installed and I can get no further.
Dual Boot: Fedora 12 and XP Dell 505I've had trouble with the latest kernel update.I updated a bunch of packages recently (including Xorg and kernel), and noticed a severe flickering after the update on my center monitor (Samsung T260 - the laptop display did not exhibit the flickering behavior). I backed out all the changes and started updating package by package. After I updated the kernel (again) I rebooted and here's where the fun part is -
I no longer get anything, except the cursor. No grub menu, no grub prompt. I rebooted and ran the rescue disk and followed the procedurery and point grub at the right boot partition - see here. However (obviously or I wouldn't be posting) that failed to work. I still get a blinking cursor and dead system on boot up.
Boot of a new minimal system hangs on "Stopping save kernel messages" or "stopping system v runlevel compatibility". I have ubuntu minimal iso x86_64 from usb stick created with unetbootin (don't have a cd drive on the machine in question), and after that I didsudo aptitude install gnome-terminal network-manager-gnome gdm geditsudo rebootnever got a system back. Annoyingly I can't boot into the recovery mode either, and it seems the keyboard is only semi-responsive (i.e. many dead keys when at the grub menu).qualms about reinstalling, but I've done this a few times and ended up at the same place every time.
It appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.