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?
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is: /sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current. What i missing in kernel?
After updating to kernel-18.104.22.168-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again. This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
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
Finally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-22.214.171.124-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
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.
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?
I just updated my kernel to kernel-126.96.36.199-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 (188.8.131.52-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 (184.108.40.206-85.fc13.x86_64). the ones that fail are: 220.127.116.11-147.fc13.x86_64 and 18.104.22.168-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 22.214.171.124-56.fc13.i686 to 126.96.36.199-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 188.8.131.52-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 184.108.40.206-64 to 220.127.116.11-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.
I 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 tried a number of times to install dual boot with Win2k. I keep getting errors at the stage of setting up the partition for the install. When I try to choose ext4 it says Fedora cannot be installed on a bootable drive, fix the problem. I don't see how to fix it...it does not say what to do or change.
I have had other linux installed in the same partition without a problem. What gives?
150GB drive for both OS's Separate drive for data, not involved in the install.
| 72GB NTFS Win2K | 76 GB free for ext3 and swap |
I tried to update my f12 today. In the list it showed an update for kernel-18.104.22.168-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/22.214.171.124-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.
I have just updated my kernel to version 126.96.36.199-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.
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.
Since doing the update which included kernel "188.8.131.52-141 fc12-i686 PAE" I can no longer boot into my usual 1280x960 desktop. I can set it using NVidia settings but even though this offers to modify xorg.conf it fails to do so. I have tried running as root and it doesn't then give an error message but when I look at xorg. conf there is no section.showing any specific screen size. It worked ok before the update. In case it is relevant the video card is a Quadro FX1400 with KDE. Also the whole program seems rather unstable since the update.
I have a problem with the kernel update to 184.108.40.206. 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'm not sure what caused it, but it happened right after running 'yum update'. It may be because it installed a new kernel, and there are now two kernels listed in my grub.conf and at boot; 2.6.31 and 2.6.32. System boots through a list of things it's starting up and stalls out at ATL or ADL or ADM maybe. It hangs there for a minute or so then flickers. This happens every time at boot. It's a bit difficult to post more information since I can't get past that part of the boot process, and I can't seem to be able to skip it either. It may be worth mentioning that this is a mini-itx motherboard. Intel Atom 330 1.6, 2GB DDR2, onboard GeForce 9400m. It's a zotac ionitx-a-u. I've installed a fresh copy of Fedora 12 lxde.
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.
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".
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img: