Fedora X86/64bit :: Unable To Boot After Kernel Update
Feb 11, 2011
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.
View 14 Replies
ADVERTISEMENT
Dec 19, 2010
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.
View 12 Replies
View Related
May 13, 2011
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies
View Related
Feb 12, 2011
there is no sound in Fedora14 after kernel update (kernel-2.6.35.11-83.fc14). when use kernel-2.6.35.10-74.fc14 , I can listen to music.
View 14 Replies
View Related
May 24, 2011
My main systems runs Fedora 14 x64 with the latest updates (I can't check anymore, but I believe it has the .13.91 x64 kernel). Since this afternoon it became unsuable. First, Opera Browser crashed and the crash report app of the browser showed up. Clicking one of the options there resulted to X crash, if I understood what really went on. No input, mouse or kb, I couldn't go to tty etc. I had to do a hard reset. Next boot proceeded normally up to the point that GNOME desktop is fully loaded. ABRT began reporting numerous kernel oops.
Rebooted again (noticed that init.d fails, so hard reset again) and tried past two kernel versions, same results.
Yum crashes and so does everything. I tried to revert all recent updates with yum history, but yum crashed.
Last update was May 22, and it updated kmod-nvidia.
Quote:
uname -a
Linux innovator 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
initial crash
Package: kernel
[code]...
before the reboot Opera 11.11 had crashed and it's own bug report tool came up. Clicking the "do not report this error now" option probably crashed X, because the screen went black and no input was possible (no mouse or keybord, so I couldn't go to tty either. Had to do a hard reset) Bug Reports:Kernel oops report was uploaded
One of the numerous crashes
Package: kernel
Latest Crash:Τρι 24 Μάι 2011 09:19:56 μμ
[code]...
View 2 Replies
View Related
Feb 19, 2009
I just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
View 14 Replies
View Related
May 31, 2009
Keep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
View 2 Replies
View Related
Sep 1, 2010
This morning, I booted into my administrator account and checked for updates. There were a number (bogofilter, for one) but also a update to the 2.6.32-24 kernel. I installed the updates and rebooted the system. When I rebooted, the thought occurred to me (from reading another thread) that one of the reasons my Zareason desktop boots slower than my laptop (55 seconds vs 35) was that I have an external floppy drive attached, and perhaps the delay was a difference in my system checking for a bootable floppy.
So I went into the BIOS when it was booting to check to see if the floppy was enabled (it wasn't). Then I selected "Exit without saving" and resumed booting. What happened next was instead of seeing the Ubuntu icon and the six dots, I see "Ubuntu 10.04" and four dots. Then I get on the black screen these errors (sorry for any mistyping, I wrote them down on a sheet of paper as I had no other computer available to troubleshoot):
udevadm trigger is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
udevadm settle is not permitted while udev is unconfigured
ALERT! /dev/disk/by-uiid/939af864-c1a8-41d7-9b24-91d25685b6 does not exist. Dropping to shell
Busybox v1.13.3 (Ubuntu 1:1.13:3-1ubuntu11 built-in shell (ash).
Enter 'help' for built-in commands
initramfs
Googling around once I got into work and had computer access, it seems that the problem is GRUB has lost track of what partition I should boot from? Here is a thread which might be relevant: [URL]. Before I left for work, I went into the BIOS again and looked at the CMOS settings--everything looked normal. I once again exited without saving anything. I was going to try selecting an earlier kernel from the GRUB menu on boot, but couldn't remember the key to press.
I found out later today, to enter GRUB 2 it's been changed to the shift key, and not the F2 key like it used to be. One poster on the aforementioned thread said his system would boot ok to the earlier kernel. The thread above has as its solution to either try to tell GRUB where your boot partition is and/or re-installing GRUB. I have /home on a separate partition, so if I need to do a re-install I can do so without it being a major pain. Sda1 is the partition which has the OS.
View 9 Replies
View Related
Oct 24, 2010
I had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
View 9 Replies
View Related
Oct 26, 2010
I have recently run an update and now we are unable to boot the newer kernel. We get stuck as below;
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
Red Hat nash version 5.1.19.6 starting
Unable to access resume device (/dev/VolGroup00/LogVol06)
[Code]...
The kernel version we were at was 2.6.18-194.el5 and the update move us to 2.6.18-194.17.1.el5. I've done some googleing but I'm unable to work out exactly what I need to do. I'm guessing the new kernal is missing a module?
View 3 Replies
View Related
Dec 7, 2009
Initial FC12 install worked great, kernel 2.6.31.5-127.fc12.x86_64 allowed radio kill switch functionality Fn-F11 for wlan and Fn-F12 for bluetooth.The last two kernels have broken that functionality.
Fedora (2.6.31.6-162.fc12.x86_64) broken!
Fedora (2.6.31.6-145.fc12.x86_64) broken!
Fedora (2.6.31.5-127.fc12.x86_64) works!
[code]...
View 1 Replies
View Related
Jun 21, 2009
since upgrading to Fedora 11 I keep getting this error:
Code:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000041
IP: [<ffffffffa01fab94>] sync_request+0x1/0x8de [raid456]
PGD 49435067 PUD 494f6067 PMD 0
Oops: 0002 [#1] SMP
last sysfs file: /sys/devices/virtual/block/md0/md/sync_speed
CPU 0
Modules linked in: ip6table_filter ip6_tables ip6t_REJECT nf_conntrack_ipv6
[Code]...
View 1 Replies
View Related
Mar 29, 2009
Ive loaded 64studio (hda6) grub in MBR, and fed10 grub on its partition (hda8), but from Studio it seems i cant Mount fed10 files to look at the Kernel path from MBR. (studio did not auto pick it up, like it did for Mandriva on hda7)
Does anyone know what it is ? something like kernel /boot/vmlinuz.....and Initrd(hd0,7)/boot.initrd.img .....then i can Edit menu.Lst in MBR grub.
View 4 Replies
View Related
Oct 17, 2010
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code:
make gconfig
make -j4 all (or make all)
make modules_all
make install
The last command edits my grub.conf file and writes this:
[Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
View 11 Replies
View Related
Aug 19, 2009
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies
View Related
Jun 1, 2010
I got a new laptop, this is the one: [URL] and decided that I wanted to go with Fedora instead of Ubuntu with this computer. The laptop runs win 7 64 bit so I'm trying to go with Fedora 64 but it will not boot. I first installed Fedora 12 64 bit from the DVD install and it would go to grub fine but when I boot the fedora os It just stops in the middle of the boot script. When it stops, the last 4 lines are:
kernel_init=0x1fd/0x257
child_rip+0xa/0x20
? kernel_init+0x0/0x257
? child_rip+0x0/x20
I hadn't messed with it for a few weeks and yesterday I saw that 13 was out, so I downloaded and burnt the Fedora 13 64 bit CD. I popped it in, booted the computer and it did the same crap. It didn't stop at the same line but it was around a line with:
? kernel_init
So I guess the kernel isn't loading properly or something. Do ya'll think I would be better off using the 32 bit?
View 4 Replies
View Related
Apr 26, 2009
Just did the most recent set of updates late yesterday (kernel and Nvidia). Since the update I cannot get to a login screen - just blinking cursor. In fact the cursor blinks for a bit then disapears only to reappear as if there are repeated attempts to complete a process unsuccessfully.
The update replaced the xorg.conf. I tied a couple of revisions, inlcuding replacing it with the earlier working xorg.conf. No luck.
Hardware is MSI K9N6GM board with Nvidia Geforce 6100 nforce 430.
View 5 Replies
View Related
Feb 11, 2010
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.
View 11 Replies
View Related
Jul 14, 2009
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.
What can I do?
View 3 Replies
View Related
Aug 10, 2009
The girlfriend did an update a few nights ago. Besides removing her NVidia drivers, it also installed kernel version 2.6.27.29-170.2.78.fc10.i686.
That kernel was causing problems. Now it won't boot at all. How do we remove that kernel altogether?
If we remove it, would simply doing another update from the previous (still working) kernel just try to reinstall that bad kernel?
View 12 Replies
View Related
Jan 21, 2010
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...
View 7 Replies
View Related
Aug 4, 2010
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
View 14 Replies
View Related
Nov 15, 2010
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.
View 5 Replies
View Related
Aug 23, 2009
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
View 2 Replies
View Related
Dec 1, 2009
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.
View 14 Replies
View Related
Apr 12, 2011
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?
View 9 Replies
View Related
Jun 16, 2011
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.
View 4 Replies
View Related
Jul 12, 2011
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.
View 13 Replies
View Related
Mar 14, 2010
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.
View 9 Replies
View Related
Nov 26, 2009
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.
View 3 Replies
View Related
