Fedora :: Kernel Failure In 11 ?
Jul 24, 2009Why am i getting this error?
Quote:
Kernel failure message 1:
Kernel failure message 2:
Why am i getting this error?
Quote:
Kernel failure message 1:
Kernel failure message 2:
even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?
I don't know here is the message:
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:
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).
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:
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.
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.
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 RelatedI 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:
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.
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 RelatedI just installed OpenSUSE 11.4 x64 as a fresh full-install last week. Seems to be running great, up until the last couple days when I installed AVG. Every time I do a avgscan, it runs for 20 to 60 min, and then causes the PC to reboot. The only thing I can find is the following event in the /var/log/messages:
Code:
May 1 11:45:01 linuxbox sntp[7653]: Started sntp
May 1 11:45:59 linuxbox kernel: [38429.349995] iTCO_wdt: Unexpected close, not stopping watchdog!
May 1 11:46:00 linuxbox kernel: [38430.111688] PM: Marking nosave pages: 000000000009d000 - 0000000000100000
[Code].....
I get this result every time I try to do a virus scan. I also have seen this result once when doing a large scp transfer from another Suse box. The AVG log just terminates and gives no warnings as to what's going wrong.
Are there any other logs I can check out to try to troubleshoot this further???
I'm running the 64 bit version of Ubuntu 9.10 on an AMD64 dual core platform with all the most recent upgrades installed. After the most recent Kernel upgrade version 2.6.31.20 the computer failed to boot correctly. Extremely slow getting to the desktop and a general failure to preload any programs that I load on boot. I had to uninstall and revert back to the previous Linux headers which solved the problem. If it makes any difference I have the machine setup as an apache2 server along with my standard desktop environment.
View 1 Replies View RelatedI successfully installed Ubuntu 9.10 Netbook Remix on an Asus EeePC in a dual boot mode with Windows XP. Because the computer has no CD drive, I used a USB stick to download the files for installation. Twice now, after upgrading to a new kernel (2.6.31-17 and 2.6.31-19 I think), when rebooting after the upgrade and selecting Ubuntu from the operating system menu, I get a message:
sh:grub>
along with a notice about limited shell commands being available. The ls command results in:
(loop0) (hd0,3) (hd0,2) (hd0,1)
In trying some of the other commands, I get a message that a linux kernel isn't loaded. The computer still runs Windows fine - or at least as fine as Windows ever runs. I'd like to recover Ubuntu without doing another full installation.
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 RelatedThis error message appears in the varlog
The situation is I removed the ADSL card from my desktop as I have no use for it for the moment. I am guessing that the motherboard is still trying to detect the Sangoma ADSL card. What is the best way to resolve this problem, uninstall the drivers for the ADSL card or change the settings in the system configuration files?
The system is not affected by this removal, just get prompted regularly about this error as configured in the kerneloops client.
I have a brand new installation of 13.37 but I can't seem to get the nvidia-kernel (64 bit only) Slackbuild from slackbuilds.org to build. I have the nvidia driver installed and working on 13.1 so I am not desperate yet: although I thought that it could just be something with the older Nvidia driver so I waited for the updated release but it fails in the same way.I have uninstalled xf86-video-nouveau and installed xf86-video-nouveau-blacklist-noarch-1.txz from /extra.I have also installed libvdpau from SBo. The nvidia-driver Slackbuild builds fine.I am using the stock 2.6.37.6 huge kernel but have also tried the 2.6.38.4 kernel from /extra and the 2.6.38.7 kernel from Slackware-current.Here is the error message I am seeing:
Code:
root@DarkStar:/home/server/Utils/Packages/Slackware/13.37/64/nvidia-kernel# SRCSUFFIX="-no-compat32" ./nvidia-kernel.SlackBuild
[code]....
Debian 5.0. Lately after login following warning popup;Your system had a kernel failure
There is diagnostic information availiable for this failure. Do you want to submit this infomation to the www.kerneloops.org
-> Yes
$ uname -aLinux vm0.debian50 2.6.26-2-686 #1 SMP Wed May 12 21:56:10 UTC 2010 i686 GNU/Linux
Reboot to old kernel 2.6.26-1 the said warning doesn't popup. Reboot again to kernel 2.6.26-2 and after login no kernel failure warning popup. I did it twice. IIRC I encountered this problem before.
I have a flash drive that I regularly use on my laptop. If I unplug the flash drive without first unmounting it, I get a popup notification of a kernel failure (with diagnostics sent to kerneloops.org). Then, if I attempt to shut down the system via the console, it hangs on "The system is going down for halt/reboot NOW!" and doesn't actually shut down. Using Gnome's graphical System > Shut Down feature just logs me out and sends me to the login screen; the shutdown feature from there does nothing. I have to disconnect the power cord on the laptop in order to shut it down, and I don't like doing this.
System: 32-bit Debian Squeeze stable with kernel version 2.6.32-5-686, running Gnome 2.30.2, on an Acer Aspire 5570z.
I use Keepassx to store my passwords and keep the keyfile for my password database on the flash drive in question. I mention this just in case it helps determine what's causing the failure.
dmesg has quite a bit to say about this:
I just installed the lenny (amd64) on my new core i7 870 computer (with netinst), but the kernel failure message appeared everytime I booted into gnome. I don't know how to solve this problem. Sorry I don't have much experience with installing linux, though I have been its user for a few years.
View 4 Replies View RelatedI was updating the kernel and left the computer to let it do its business. There was power failure and I don't know if the update completed or if it was in the middle of it. Now if I start the computer, it freezes up at the login screen. I tried to recover from grub, by selecting "Ubuntu, with Linux 2.6.32-21-generic (recovery mode)". There were no prompts for input after this. The recovery screen is not updating anything after:
[2.348886] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[2.349015] EXT4-fs (sda1): write access will be enabled during recovery
[2.577641] EXT4-fs (sda1): recovery complete
[2.578072] EXT4-fs (sda1): mounted filesystem with ordered data mode
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
When I come out of that screen (ctrl-alt-del), the problem repeats.
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
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 RelatedHow 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."
I learned yesterday that doing a massive upgrade on my system while moving was a BAAAD idea.The upgrade process was going along just fine, it was all downloaded and was actually installing that last time I saw it. I unplugged my laptop to move a bookcase out, and completely forgot to plug it back in. After I got back from moving a load, I found my computer was off. I tried to boot up, and I got an error that kind of freaked me out. It reads as follows:
Code:kernel panic not syncing vfs unable to mount root fs on unknown-block(0,0)I'm able to get to grub just fine, and my windows partition loads up just fine, but any of the linux kernels fail similarly when I attempt to load them.I'm sure that I can fix this, I just have no idea how. Probably has something to do with a live cd.
I want to load the package madwifi under opensuse from Index of /suse/11.1, but RealPlayer did not function correctly. The reason why I want to use madwifi is that I cannot start my internet with opensuse 11.1 using motherboard from asus with the ethernet adapter from Atheros AR 8121/AR8113 PCI-E Version 1.0.0.5. When I compile the delivered Linux drivers I got the failure message "Makefile:61: Linux kernel source not found". So I decided to take rpm from opensuse within madwifi. How/Where can I get the corrosponding madwifi elsewhere?
View 4 Replies View RelatedI get this error message with KINO.
WARNING: raw1394 kernel module not loaded or failure to read/write /dev/raw1394!
I have installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
View 6 Replies View RelatedI recently realised that I could use Linux to "revive" old machines, and have set it as my goal to actually get all old PCs in my house working again using different variants of Ubuntu, while learning how to use the OS in the process.And now I got stuck while installing the OS on an old Laptop. It's an HP Omnibook XE-3, with a Pentium III 1066 MHz cpu and, supposedly, 256 MB of RAM. However, for some reason the computer only reads 248 MB, so I've been forced to resort to an alternative disc installation. Since the old HP has a broken CD tray, I've been using an external hard drive to boot the image, created with Ubuntu's startup disk creator, instead of an actual CD rom (I doubt that makes a difference, but just in case)
There are two main issues which have really left me with no obvious (for a newbie) alternatives. Firstly, when the text installation procedure reaches the "Installing base system" part, an error message appears saying that no kernel could be found on my Drive, so the installation fails. If I try to skip installing a kernel temporarily, it lags horribly and produces multiple errors, dying shortly after.The second problem is that I can't actually do a command line boot to try and manually figure out a way around this. Selecting the command line installation mode on the main installation menu changes nothing, and it's a normal text install which runs instead.Unable to access the command line,why my kernel is apparently missing.
I am using Fedora 8 in my PC and i'm trying to create a shared memory (below is the sample program) i'm getting error while creating shared memory. Can anyone pl tell what is the possible cause for this.
View 2 Replies View Related