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:
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.
I'm I seeing this wrong or is the initrd file in kernel-18.104.22.168-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)
I upgraded to fedora 10 using yum but i have a problem, the installation went fine and after rebooting i got a login screen. I typed in my user name and password and after a second it returns to the login screen. Im sure the username and password are correct. If i type in another password i get an error message. So how can i log in?
This is what i did to upgrade to Fc10:
Then i got an upgrade wizzard and selected Fedora 10 and than reboot.
In the grub menu only one kernel is present which is the Fc10 so couldn't use the old one.
I've tried to edit the kernel with single for single user that works gives me a command line but im just not experienced enough to figure out how i can use the command line to login.
After the Upgrade of my Fedora Insatallation (FC 10 => 12) I have some problems with Gnome and the Login via console. The system actually boots fine and all kind of services like Postfix, IMAP, Samba, SSHD, Apache, etc. are avialable normally.
If I try however to work directly on the server I only see the completed Fedora progress icon and not as hoped for, the Login to Gnome. Also the attempt to change to a plain console with ALT-CTRL-F1 fails.
Since actually everything seems to work quite fine, I am somewhat helpless, according to should I look for, to get Gnome and the Console Login working again.
I just tried to update to kernel 22.214.171.124-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.
I recently upgraded from FC7 to FC10 (Also, the Kernel from 126.96.36.199 to 188.8.131.52).I did the upgrade through Yum (First installed the fc10 rpms, then did yum upgrade).Now the new Kernel won't boot.These are the options in GRUB for the new Kernel
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 ?
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-184.108.40.206-63 lines, so that the default is now the previous kernel (220.127.116.11-61).
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.
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.
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.
Well, to start off my graphics card didn't work but I got that fixed.
When I start up and the login screen appears it no longer says my username and Other.. under it. It only displays Other.. I have to click that type in my username and then my password. When I log on the Auto Bug Reporting tool pops up and says 3 things crashed
I can't change my system time, shutdown or reboot under system or my username in the top right hand corner. I have to su and manually type reboot or shutdown to shutdown. It is like the computer is completely restricting me from using it.
When I try to get into my firewall an error comes up
After upgrading several packages (can't remember which now) I can't login with the graphical login. It accepts the password, starts to load, but then dies and dumps me back at the login prompt again.Attempting to login from the prompt, sometimes works (there is specific condition), and when it does, I then attempt to "startx". OK, it complains the display is already in use, so I then "startx -- :1". Everything starts to load, but then fails again like the graphical login.
checking /var/log/Xorg.1.log I see no errors [EE].checking /home/***/.xsession-errors I see the following.xauth: file /home/***/.serverauth.15914 does not existI have also tried as another forum suggested and rename the .kde4 and the .skel directories to something else. Login via graphical and prompt still both fail.I have also tried logging in with another window manger. That also fails.However, I have also tried creating a new user and logging in. That works. It is from this user account that I write the postI have attempted copying over all of the application settings from the corrupted user account, but some things are missing and there are various personal project directories and permissions that are causing issues. Therefore I would like to repair the corrupted account. Where do I begin to fix the corrupted account?OS: Linux 3.0.1-40-desktop i686System: openSUSE 11.4 (i586)KDE: 4.6.5 (4.6.5) "release 4"Video: nouveau
I just installed Ubuntu 10.10 and when I try to log in to the regular desktop environment, only the backsplash coloring is there. I can, however log into safe mode and see the GUI there. Occasionally, I will get the treat of using the regular desktop environment, but it will ultimately freeze, and if I go to a different runlevel and restart gdm, the same thing happens....only backsplash. Here's what I've looked into, all of which has failed by the way: gdm.conf, URL... even though that "fix" was for an earlier release, and of course reinstalling a few times. *Sigh*I'm running it on a Toshiba Satellite L25-S1217, Intel Celeron, 874MB RAM, and 60GB HD with the stock Radeon graphics card.
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.
I 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: 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
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 18.104.22.168 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.
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
When I try to login to my Ubuntu Server, I get the following error: PAM Failure, aborting: Critical error - immediate abort This occurs when I try to log in locally, or via SSH. I have tried logging in using every account and all create the same error. Ubuntu server edition 11.
I 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:
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?