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 RepliesI 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 RelatedHardware at issue is an nVidia GeForce 9600 GT. Issue occurs regardless whether the driver is downloaded and installed from nVidia, or installed via Synaptic courtesy of the new dkms package in the repositories.
It should also be noted that the issue only arose after an update today, as follows:
I do not believe it is related to the last three items in that list. Because everything worked perfectly before todays update, it would appear that one of those other updates is causing KDM and nVidia to not want to co-operate with each other.I also notice that, new to the boot sequence, the system is booting with "concurrency" - never seen that scroll by before - which may have something to do with it too.
OK, what happens. KDM "fails" to start when booting the computer. Symptoms : At the appropriate spot in the boot sequence, the screen goes black (as usual), but then, instead of the cycling cursor followed by the logon screen, the nVidia logo appears, and after about 7 or 8 seconds, the screen goes black for about a second, then drops me back at the console. From there, I can log in as root.
Now, the thing is, KDM is actually running, but using <control> <alt> <F7> only brings me to a blank black screen. By issuing the command /etc/init.d/kdm restart, I come up to a normal logon and can proceed as usual. As well, if I delete xorg.conf, system boots OK.
Looking at the system log, we find :
And then some way past that we get :
Should mention that was using the latest stable driver from nVidia (195.36.24), but in the hope that maybe something in the latest beta may solve the issue, installed that, but the answer is nope And yes, completely uninstalled the nVidia drivers between each test of the nVidia driver, the same driver in the repositories and the latest beta driver, before anyone mentions.
I'm running Squeeze and I've been running into the r8169 hang problem (see [url]for example). A temporary (until the driver foibles in the kernel are resolved) solution that seems to be working for many people is passing the boot option "pcie_aspm=off" to the kernel.
Apparently, either I don't understand grub2 at all or my kernel doesn't like me very much. I put the option in grub.cfg like so:
However, it appears that the kernel, for whatever reason, is either not being given this boot option or it's not interpreting it correctly. When I run lspci -vv I get this for my r8169 ethernet card:
The relevant section is LnkCtl:�ASPM L0s L1 Enabled; indicating that ASPM is still on.
I have squeeze and I've created my own custum kernel. Howto configure grub 2 to boot with this custom kernel automaticaly?
View 5 Replies View Relatedsince upgrading the squeeze kernel from 2.6.26-2-686 to 2.6.32-5-686 I�ve been unable to boot my HP D510S/845G without attached monitor. As this computer serves as router and print/faxserver, there is/was neither a monitor nor a keyboard/mouse attached. With monitor everything works fine, without monitor the computer hangs somewhere. Unfortunately it hangs without logging anything in /var/log.
Reinstalling xorg and xserver-xorg didn�t change anything, neither was the new xorg.conf from dpkg-reconfigure -phigh xserver-xorg of any use. (After booting with attached monitor I disconnected the monitor and ran dpkg-reconfigure) Maybe disabling Xorg would solve the problem, but I want to be able to log in via vnc and use a GUI - for example to configure mythtv. Up to the kernel-update everything was working fine, so I think some changes to the new kernel are responsible. how to fix it or how to start logging earlier in the boot process?
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.
I use a static compiled kernel and a fully encrypted disk apart from a boot partition. I have recompiled and installed kernels many times. When I tried with the latest kernel from Testing, 4.2.6, the system will not boot. Not only that but the previous kernel now does not boot. However, a stock modular kernel does boot. The static kernel hangs at:
Code: Select allVolume group "dk" not found
Cannot process volume group dk
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Reading all physical volumes. This may take a while...
/run/lvm/lvmetad.socket: connect failed: No such file or directory
[Code] ....
And after giving the password the boot continues successfully. How to diagnose it further?
I've got a fresh install of Squeeze on a 32bit host and I have been unable to boot into XEN/dom0.The Xen Kernel is "linux-image-2.6.32-5-xen-686" (pvops) and Hypervisor is xen-hypervisor-4.0-i386.The system default installed with grub2.It boots quite happily in normal mode, using the above Kernel, but just reboots itself if I try run it as Xen/dom0. (reboots within a second of pressing <enter> ... there is no messages displayed on the screen that I have noticed)The relevant menu (generated by /etc/grub.d/20_linux_xen) entry for running Xen is as below;
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386' --class debian --class gnu-linux --class gnu --class os --class xen {
insmod part_msdos
[code]....
I need to install any version of Debian with the Debian Kernel version 2.6.22-3-686. I don't mind what version of Debian it is, I just need it to have this specific kernel! Debian Etch comes with 2.6.18-4-686 and Lenny comes with 2.6.26-2-686 so the kernel I need is obviously somewhere in between.
I have tried using the following commands to see if kernel 2.6.22-3-686 is available for download via the apt-get method in both Debian Etch and Lenny but it is not...
apt-cache search linux-kernel
apt-cache search linux-source
So does anyone know where/how I can download specific kernels and install them for use? I have a computer sitting next to me that has multiple kernels as an option on boot, and they all boot into the same system, however I do not know the person who set up the computer so cannot ask them how they did it
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:"
"Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
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 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.
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 RelatedDual 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'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'm a beginner + in debian (ie I know how to launch basic command under a shell), and I very new to configuration problem.I have a running perfectly file server for probably more than 2 years that I never touch. That's the debian problem, when it's unning, it's forever, no reboot at all.I recently bought 2 new sata drive 1TB5, that I add to my system by adding to my old system a SATA PCI board without any problem.But, one of these 3 month old drive is already dead.So I try to replace it and that's where problem started.....First I did a#mdadm --manage /dev/md1 --remove /dev/sdb1, of course without sucess because sdb is dead
#mdadm --detail /dev/md1
/dev/md1:
Version : 00.90.03
[code]...
I am experimenting with installing a bare minimum, network capable installation of Debian Squeeze. Right now, I am having trouble getting proper host name resolution. I have provided the output of ping (which is able to resolve names), wget (which is unable to resolve names), and the contents of the files I believe to be relevant to the problem. When I installed Debian, I installed *only* the SSH Server from the list of available configurations. Since then, I have installed mdns4, dnsmasq, mdns-scan, and libnss-mdns to get name resolution to work with no success so far. All packages were installed with no recommends -- aptitude -R package name. What am I missing to get host name resolution working?
[Code]...
I'm testing to log in using openldap authentication on jessie by following article from [URL] ..... and when I try to log in from ldap client (another debian 8 VM), it failed with
Code: Select allFeb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server
Feb 3 09:25:33 clt nscd: nss_ldap: failed to bind to LDAP server ldap:///192.168.191.120: Can't contact LDAP server
Feb 3 09:25:33 clt nscd: nss_ldap: reconnecting to LDAP server...
Feb 3 09:25:33 clt nscd: nss_ldap: could not connect to any LDAP server as cn=admin,dc=test,dc=lab - Can't contact LDAP server
[Code] ....
test result from client with ldapsearch
Code: Select all# ldapsearch -h 192.168.191.120 -D cn=admin,dc=test,dc=lab -W -x -b 'dc=test,dc=lab' 'userName=*'
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base <dc=test,dc=lab> with scope subtree
# filter: userName=*
[Code] .....
This 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'm new to Debian and installed it with Cinnamon because I want to learn some OpenCL programming in Linux. I have a Nvidia GT 525M GPU. Once the operating system is installed, I followed [URL] ..... article to install the proprietary Nvidia drivers. As the forum suggested, instead of creating an Xorg server configuration file, I installed Bumblebee according to [URL]..... article.
But when I restarted my machine after completing all the steps when I try to log in I get the follwoing message:
"failed to load session 'cinnamon'"
I cannot login as normal user or root.
I've just installed 'Testing' on a VMware server and after I completed the install with no problems, the system booted into the kernel and I noticed the following start up process error:
startpar: service(s) returned failure: udev...failure!
I have not seen this before and am not sure if it's related to the fact that this is a virtual machine and not a physical server or something else.
Here is a Screenshot.
I am trying to login as root but i end up with an error that says: su: Authentication failure
View 10 Replies View Relatedi have this problem i install android sdk, and i install libreries: libstdc++5, lib32stdc++6, lib32ncurses5 and libstdl1.2-dev,
now if i use ldd comand don't have problem, but when i use eclipse and i compile a simple example (hello word example), i have this
error: [Emulator] SDL init failure, reason is: No available video device i have a notebook toshiba satellite A300-1RI whit ATI Radeon 3650, i install the amd driver and all work well.
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 Related