Fedora :: 13 Kernel 2.6.34.7-63 X86_64 Causes Boot Failure?

Dec 7, 2010

I have just updated my kernel and immediately struck trouble. The kernel update is marked as security update.
When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).

View 14 Replies


ADVERTISEMENT

Fedora :: 2.6.31.6-162.fc12.x86_64 Boot Failure (F12 64bit On Nvidia 730i/9300 Chipset)

Dec 8, 2009

Just got the latest kernel update 2.6.31.6-162 for fedora 12 64bit and it won't boot on my PC. I just get a black screen with some text that doesn't mean anything to me. Computer is a s775 E7200 with nvidia 730i/9300 integrated graphics. I am NOT using hardware graphics drivers at the moment, having decided to stick with Nouveau drivers for a time. What system log tools do I need to identify the problem?

View 2 Replies View Related

Fedora :: Kernel 2.6.31.6-145.f12.x86_64 Update Wont Boot?

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

Fedora :: Boot Failure After Kernel Update / Log In As Usual?

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

Red Hat / Fedora :: Boot Failure After Latest Kernel Update (12)?

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

Fedora X86/64bit :: Boot After Install Gives Kernel Panic Failure

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

Fedora :: Heartbeat Failure [rc=1]. Failed On 14 X86_64?

Nov 19, 2010

after i installed F14 on my box, I'll receive this error on boot log message: Code:Heartbeat not configured: /etc/ha.d/ha.cf not found.Heartbeat failure [rc=1]. Failed.how can i fix it?

View 1 Replies View Related

Fedora :: 0 Byte Initrd File In Kernel Kernel-2.6.27.25-170.2.72.fc10.x86_64

Jul 13, 2009

I'm I seeing this wrong or is the initrd file in kernel-2.6.27.25-170.2.72.fc10.x86_64 a zero byte file and that's why I can't boot with it( get this "kernel panic not syncing VFS unable to mount root fs on known -block (0,0)" message)

View 2 Replies View Related

Debian Configuration :: Kernel Failure Almost On Every Boot

Oct 13, 2010

Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.

View 4 Replies View Related

Ubuntu Installation :: Boot Failure After Kernel Update

Mar 25, 2011

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 Related

Fedora :: Kernel 2.6.31.6-145 X86_64 Grub.conf?

Dec 3, 2009

The latest update changed the default boot from 0 to 1 and added extra parameters to the new kernel boot line.

default=1
timeout=8
splashimage=(hd0,7)/boot/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.31.6-145.fc12.x86_64)
root (hd0,7)

[Code]...

View 1 Replies View Related

Ubuntu Installation :: Wubi Boot Failure After Kernel Upgrade

Nov 27, 2010

I'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

View 4 Replies View Related

Ubuntu :: Boot Failure After Botched Kernel Update / Solution For This?

Mar 3, 2011

So I ran the update manager to install the latest kernel. It goes fine and was sitting at the restart prompt. I was playing minecraft and the entire system locked up - couldn't restart X or anything. Hard restart and I get a multitude of errors mostly dealing with not being able to find things in /dev/... It gives me a command line but I'm lost as to where to go from here to repair my system

View 2 Replies View Related

Ubuntu :: Install An Additional Kernel In 10.10 In Case Of A Boot Failure?

Mar 24, 2011

How do I install an additional kernel in Linux Ubuntu 10.10, in case of a boot failure? Also how do I make the Grub Menu Visible, so that I am able to select multiple kernels. There is an older solution below, but is there a way to do this in Linux Ubuntu 10.10. I just suffered an update failure, possibly due to a corrupt kernel upgrade, which made my system unbootable. The cursor just flashed continuously.

Solution of 2007[URL].... "The next obvious rescue aid is to always have a working kernel installed. I usually work from a kernel updated via yum. Kernels have occasionally been released with flaws that have caused one or more of my machines to not boot. To this end, I always make sure I have at least one perfectly running kernel on a machine. A great way to handle this is to first add plugins=1 in your /etc/yum.conf file. The next step is to take this script (written by Jeremy Katz from Red Hat) and save it as n-installonly.py in /usr/lib/yum-plugins. You can change the number of kernels to retain on the system by changing the tookeep variable (default = 2).

With a known working kernel on your system, you can upgrade safely. If the new kernel is hosed, simply boot the old kernel to solve the issue with the new kernel be it to remove it, recompile it, or update it."

View 3 Replies View Related

Fedora X86/64bit :: Upgrading To Kernel-2.6.31.9-174.fc12.x86_64?

Dec 29, 2009

I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:

[Code]...

View 6 Replies View Related

Fedora :: NVidia Driver For New Kernel 2.6.35.12-88.fc14.x86_64?

Apr 12, 2011

I just responded to a (packagekit?) prompt to update packages, which included new kernel 2.6.35.12-88.fc14.x86_64. I use nVidia on my notebook and usually the new driver is installed automatically. This time, the computer would not boot to the stage that the nVidia logo appears, indicating the driver is not present. I edited grub.conf to take me back a version and I am now running under the previous kernel 2.6.35.11-83.fc14.x86_64. I tried a yum search for kmod-nvidia-2.6.35.12-88.fc14.x86_64 and nothing was found. I have enabled these repos:

[Code]...

View 4 Replies View Related

Fedora X86/64bit :: Booting Updated 2.6.39.1 X86_64 Kernel

Jul 19, 2011

In an attempt to ameliorate some other problems (lm_sensors, and loopback), and based on several forum entries, I decided to update the default f15 kernel (2.6.38.35) using kernel-2.6.39-1.fc16.x86_64.rpm from rawhide. It seemed to install without problems and when I rebooted it seemed to hang just before completing the boot process. The on screen boot messages ended with:

Started Display Manager
Started LSB: daemon for libvirt ........
Starting LSB: suspend/resume libvirt guests on shutdown/boot
[ 12 ......
about a dozen similar lines ending with
[25.030991 hci_cmd_timer: hci0 command tx timeout
then it apparently hangs

However, at that point I can log into to a console using Cntl-Alt-f2, so most, if not all, the crucial boot processes seem to have completed. There is an issue with the nVidia driver that I will deal with by modifying /boot/grub/grub.conf to re-enable nouveau, but I am stumped by what is causing the hang up. There is a certain amount of traffic regarding a similar problem with Ubuntu 11.04, but no solution other than it seems to be related to a BIOS bug (NFI)

what sub-system uses the "hci_cmd_timer" and why it might interfere with the boot process? Has anyone else run into a similar problem with f15?

Is there a better way to get an updated kernel in f15? I do want to keep all the Red Hat patches and back ports, so reluctant to build a kernel from scratch from upstream sources at kernel.org (and maybe just a bit apprehensive ;-})

View 11 Replies View Related

Fedora :: Kernel 2.6.38.8-32.fc15.x86_64 - VirtualBox - Missing Module

Jun 16, 2011

I generally check what updates are being installed. This time sadly I didn't and again this kernel had one missing module. VirtualBox-OSE stopped working. It had been working fine with other upgrades. No it's not a problem with dkms or other stuff. This kernel doesn't have vboxdrv module like other kernels...i verified it...

[Code]...

The 2.6.38.8 version doesn't have vboxdrv module!....hence again I have to roll back to older kernel. So before blindly upgrading....read this message!

View 10 Replies View Related

Fedora X86/64bit :: Cannot Update Kernel (Fedora 10 X86_64)

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

Fedora Networking :: Kernel 2.6.35.10-74.fc14.x86_64, E1000e Driver 1.0.2-k4 Still Had Bugs?

Feb 11, 2011

I just built some machines with the Intel 82574L gigabit ethernet chip, loaded Fedora 14, and discovered a problem with the e1000e driver dying after a few minutes. A little time spent perusing the web told me that the same driver had problems in Fedora 12 and Fedora 13 as well. Congrats to Fedora for the hat trick.As of kernel 2.6.35.10-74.fc14.x86_64, e1000e driver 1.0.2-k4 still had bugs.[URL]

View 6 Replies View Related

Fedora :: Kernel Failure In 11 ?

Jul 24, 2009

Why am i getting this error?

Quote:

Kernel failure message 1:

Kernel failure message 2:

View 1 Replies View Related

Fedora :: Kernel Update Failure ?

Dec 13, 2009

even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?

I don't know here is the message:

View 4 Replies View Related

Fedora :: Received Two Kernel Failure Messages In 11

Mar 4, 2010

I have just installed Fedora 11 to my laptop and it appears I am in trouble. I have received two kernel failure messages, which I post below. What are the consequences of these issues and how can I solve them ?

Message 1:

Message 2:

View 4 Replies View Related

Fedora :: When Login Into FC10 - Kernel Failure ?

Feb 14, 2010

I am getting a problem when login into FC10. It boots correctly an shows the login screen; then, when typing my user and passwd goes to the desktop and shows a KERNEL FAILURE. At this moment, most of the times the PC is blocked and doesnt works any more. One time has continued working without problems.

After the las failure, my system log has this info:

Code:

I have checked my hard disks (fsck) y every thing looks fine. However, i dont know how to fsck the VolGroup0. I cant'get it unmounted.

Code:

View 1 Replies View Related

Fedora :: Cannot Boot Into 2.6.29.6-217.2.7.fc11.x86_64?

Sep 9, 2009

I was on version 2.6.29.6-217.2.3.fc11.x86_64 and it asked me to update so I did. When I restarted I chose this version to install and after a brief loading screen it goes to a black screen with a cursor prompt and pretty much stays there. So I go back to 2.6.29.6-217.2.3.fc11.x86_64 which boots up just fine. But after a while I get some updates that won't install because it says that Packages are not compatible:Install - Linux Kernal 2.6.30.5-43.fc11(x86_64)

ERROR with rpm_check_debug vs depsolve:
kernel-uname-r = 2.6.27.19-170.2.35.fc10.x86_64 is needed by kmod-nvidia-2.6.27.19-170.2.35.fc10.x86_64-180.29-1.fc10.1.x86_64

[code]....

View 1 Replies View Related

Fedora :: Computer Is Running Very Slow And Freezes Up Every Few Seconds - Kernel Failure ?

Jun 24, 2010

I am having a problem with my Fedora11, I am not sure wether it is software or hardware but this looks serious. My computer is running very slow and freezes up every few seconds. Every time I reboot I would get a kernel failure pop-up.

This is what the message says:

Kernel failure message 1:

Kernel failure message 2:

Call Trace:

View 1 Replies View Related

Fedora X86/64bit :: After Udate A 2.6.30.9-99.fc11.x86_64 Does Not Boot?

Dec 3, 2009

I have installed last updates about 3 days ago. After this Fedora kernel 2.6.30.9-99.fc11.x86_64 does not start.booting it the last message I see"ADDRCONF(NETDEV_UP):wlan0: link is not ready" then it stops. I have to boot with a previous kernel version 2.6.30.9-96.fc11.x86_64.

View 2 Replies View Related

Fedora :: Finding Lost /boot Partition On F12 X86_64

Dec 8, 2009

During attempted repair of damaged USB stick with fdisk and parted, an error appears to have changed the partition holding the /boot partition. At one point I possibly typed sda1 instead of sdb1 and appear to have lost my /boot partition.

This is on a HP Compaq Presario CQ50 228CA Portable running only Fedora (No multiboot).

I am able to reach most of the programs and data on the machine with the rescue mode from the F12 x86_64 DVD, chroot /mnt/sysimage command - so the main part of the system is still available. But when the machine starts up all I get is the 'grub:' prompt. In rescue mode I can cd /boot but there is nothing to list, and certainly there is no /boot/grub. fdisk /dev/sda1 p reports 255 heads 63 sectors/tracks 25 Cylinders Units=cylinders of 16065 x 512 = 8225280 Bytes Disk Identifier 0x0000000 - and then nothing under the headings Device, Boot, Start End etc...

Previously /boot was on /dev/sda1 a 194 m patition, with 39m used and 146m available (according to logwatch mail),

My questions:
Are there any commands in the grub program that would help my recovery - I doubt it, because grub is in place and running but I am not sure. Could I using fdisk recover the sda1 partition and it's contents? If so - how? If no, could I use the F12x86_64 to update and hence recover the /boot drive and retain the the LVM volumes both programs and content? If no, is my only option to reload F12 from the start, then rsync in my backup /home directory?

Since there had been a fair amount of customization done on the previous F11 which had been preupgraded to F12 I would prefer any option that would retain the customizations ...

View 3 Replies View Related

Fedora Installation :: LiveUSB Freezes At Boot Menu (15, X86_64)?

Jun 14, 2011

I'm trying to install Fedora 15 from a USB stick. I can boot off it just fine, but most of the menu options don't work:

Boot => Freezes indefinitely
Boot (Basic Video) => Freezes indefinitely
Verify and Boot => Freezes indefinitely

[code]...

View 1 Replies View Related

General :: Debian 686 Kernel Total Networking Failure On IbmX60 But 486 Kernel Works

Feb 11, 2011

The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.

I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.

Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?

Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:

I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.

View 14 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved