Ubuntu :: 11.04 Hangs On Boot - Start With Older Kernel Works?
Sep 1, 2011
I've recently upgraded to Natty (11.04).The problem that is now occurring, and reoccurring, is like this:- Computer boots, but hangs on a purple screen (nothing on it). Nothing happens, after 15 minutes or so I give up waiting and hard reset.- Boot via Grub (holding shift) into recovery-mode: works fine, but I want the GUI, so I reboot.- After reboot the system hangs again, as mentioned before.- Hard reset again, and booting a previous kernel (2.6.32.8 ): works fine!- Restart again, boots in most recent kernel (2.6.38.10): works fine now.- Try to shutdown/restart again, problem re-occurs every time. So I use the workaround with the extra startup with the older kernel again.and finally typing this.
It hangs after mounting my root partition, and switching to framebuffer. And ctrl-alt-del causes a normal shutdown - everything gets told to exit.
This where it hangs:
[URL]
This is my config:
[URL]
lspci output:
[URL]
Based on the mainline defaults. I made sure ext4 is compiled in, SCSI, SATA and PATA support... sda1 is my root partition. sdb1 is a data drive. The drives are SATA.I need to rebuild from source to test some stuff for wayland.
I'm running an LMDE install, but with the Sid repositories.Everything has been fine until yesterday's updates, after which I can't boot normally. The boot hangs at the login screen, and nothing works - not the mouse, the keyboard, the touchpad, nothing, and it requires holding the power switch to get out. I can boot to a root recovery console, but networking doesn't work at all there. I can run startx there and get an X desktop as root, and networking still doesn't work. No wireless, no ethernet, no nothing. From the recovery console I can run shutdown, and when prompted for a password, can enter Ctrl-D, which immediately drops me back to X, to the normal login screen, which now works normally, and I get a normal X session in which everything works. This is the same for all installed kernels, including 3 versions of the Liquorix kernel and the standard Squeeze kernel. It would appear to be something in my settings in /home, but I can't find anything that looks suspicious. I ran smxi again after booting through the root console, without any improvement.
Running Ubuntu Server 10.04 32 bit. Sometimes when I reboot it does not start up, It seems to be going through the boot process but then just hangs. I have had a look at the log files and can't see anything, but I'm not really sure what I am looking for.
The most recent kernel update, to version 2.6.38-11 has been a horror. It hangs on boot up. Sometimes I can get to the log in screen, then it hangs there as well. However, after 3-5 reboots (which is absolutely annoying to do when I just want to use my computer), it sometimes loads up finally. However, if I go to older Linux version in the Grub menu, then I can select 2.6.38-10 and it runs just fine.
So I am looking for a way to fix this problem, whether it be removing the most recent kernel update, or making 2.6.38-10 boot up by default. I noticed that the kernels are listed in the synaptic package manager, but I am afraid to remove the most recent one via synaptic. Is it as simple as removing the Linux version and headers I don't want, or are there other things I need to do in order to make 2.6.38-10 my default kernel at start-up?
I am using SUSE 11.2. And I am really baffled with a strange NFS problem.I have set up the fstab on the client and exports on the server correctly, because if I manually run # /etc/init.d/nfs startStarting NFS client services: sm-notify doneI can see and use the NFS partition perfectly, there is no problem at all.But nfs cannot successfully start at boot. In yast, I have enabled nfs in "System Services (Runlevel)" at runlevel 3 and 5. So it should run automatically, but I always get the following error message:
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 have a problem with the kernel update to 2.6.34.6. 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 have updated to the new kernel that was available from 11.2 and now I cant use my system.
It boots up into kde 4.3.5 and then right when its just finishing it freezes everytime and I hear that last tone of the bootup sound ring continually until I force a shutdown. Anyone else have this issue with the update?
After a massive meltdown with the upgrade, I finally got the system put back together. Had to reinstall grub. It now defaults to a version that says "Generic - pae". When choosing this from the grub menu, it always hangs on the Ubuntu splash screen; however, I found that when I choose "previous Linux versions" from the grub menu, then choose the Ubuntu-generic, everything works fine - other than my initial bad impression of unity - but it works, at least.
why my default choice in grub doesn't work, and what I need to do to fix it? Below is a cut and paste from /boot/grub/grub.cfg. The first entry is the one that does NOT work, and the first entry after "submenu" is the entry that DOES work.
menuentry 'Ubuntu, with Linux 2.6.38-8-generic-pae (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os { recordfail set gfxpayload=$linux_gfx_mode
Recently i've upgraded my fedora 11 to 12 using the preupgrade command and now I have a problem booting! when i start the interactive boot it hangs after trying to run the service local, it looks as if its trying to boot because the cursor blinks really fast then blinks normally after a few seconds. no error was stated during the event. what seems to be the problem here?
I'm looking to install an older kernel in Maverick - something like 2.6.32 maybe? Just wondering if there's a way to do it without compiling myself. I upgraded my system without checking everything. I use it as a MythTV box and the 2.6.35 kernel breaks my remote control in a manner that appears to be unfixable at the moment, if the forums on the problem are right. I figure an older kernel will get me out of the jam, but I'm not sure how to go about it (there aren't any in the standard repos).
Code: apt-get source linux-image-2.6.32-21-generic Reading package lists... Done Building dependency tree Reading state information... Done Picking 'linux' as source package instead of 'linux-image-2.6.32-21-generic' NOTICE: 'linux' packaging is maintained in the 'Git' version control system at: kernel.ubuntu.com/git-repos/u...untu-lucid.git Need to get 86.7MB of source archives. Get:1 pt.archive.ubuntu.com/ubuntu/ lucid-updates/main linux 2.6.32-24.39 (dsc) [5,568B] Version 2.6.32-24 is downloaded instead... What command can I use to download 2.6.32-21 - and not a newer one?
Is there any legal way to install an older version of linux-kernel (say 2.6.35) on 11.04? By legal I mean - no source-compiling and third-party repo adding.
A few days ago yast did update my computer to a new kernel-desktop 2.6.31.12-0.1.1.
My mainboard is an ASUS P4P800-VM with Intel ICH5 chipset. This new kernel is not able, to poweroff my computer. Older kernels were able to poweroff the computer.
How can I roll back to the older kernel? Yast does only offer the recent kernel.
In /boot there are only files of the recent kernel.
ASUS P4P800 Intel Pentium 4 HT, 3000 MHz, Frontside 800 MHz/Cache 1 MB 3 GB Ram AGP nVidia 7600GS/512 MB, nVidia driver 190.53, installed from yast. PCI WLan TP-Link 951N (Atheros chipset, WLan N, driver ath9 was automatically installed)
How can I install older fedora kernel? Because I accidentally removed the working kernel among three kernels. I've tried yum install kernel-2.6.30.10-105.2.4.fc11.i586 but fails.
My company offers Linux preloads in RHEL, Fedora and Ubuntu. I have Fedora 13 installed on my laptop. I want to install it on a desktop but the 2.6.33 kernel hangs the desktop when the Fedora 13 or Ubuntu Lucid DVD boots. I have the Ubuntu Jaunty preload on the desktop but would prefer Fedora. The preload includes a few apps for my job that aren't included with Ubuntu. Is it possible to select an older kernel to boot to and/or use that during the install? I think it is the SCSI controller causing this. I have the same model machine at home configured the same way except the onboard SCSI is disabled, I am using SATA drives in it.
I am an experienced Linux admin and have been using SuSE for many years. My development machine has had every version of SuSE since '02 and although it is a little old, is in good working order. (AMD 2400, 2 gig RAM, 160 Gig IDE disks - SuSE on disk 2) (OpenSuSE 11.1 with the latest kernel works perfectly. This install is on a spare HDD prior to doing a full install on my usual HDD.)
When I try to install SuSE 11.2 from DVD, the load kernel operation hangs at 97% (using both normal and safe kernel), however, I can install from live CD without any problem. I have tried the same DVD on a few "older" machines and had the same problem. I initially thought it was the actual DVD but re-burning has the same problem. I have also tried another DVD writer - same problem.
I used to keep a back level kernel on all my systems along with the latest upgraded kernel. How is that done using Yast/zypper? I don't see an option to keep the older version.
i just updated my mainboard, because of a failure in the grafic chip. Now I have a icore 7-2600K CPU with 16GB memory.The system will not boot with the latest kernel version Kernel 2.6.38.11 - Kernel 2.6.38.10 . It crashed and resets the system.
But when I am using Kernel 2.6.35.30, then it works, as you can see. As well the kubuntu 64bit CDROM does not work. Crashed as well.
Its on an older laptop, a Toshiba Sattelite M50-252. A friend of mine had this laying around, and it wasn't running windows very well. So I installed Ubuntu 9.10 on it and it was performing decently enough for browsing and mailing.
On Ubuntu 9.10 there was a problem sending large images for printing. It would make the printer (A brother HL-4050 CDN, placed on the network) say out-of-memory. Same print job from windows would not make this error. Upgrading the system to Ubuntu 10.04 worked.
Actually, I had before tried 10.04 on the machine but ended up formatting and reinstalling 9.10. This was because browsing on 10.04, no matter what browser, would simply hang randomly. A search on google could be performed, and some pages loaded. But some pages didn't load at all or only a few % of them, and the browser would just claim to be "resolving host".
On 9.10, on all 3 installs i've done on the machine, this problem was NOT to be found.
Here goes the real issue: 4 days ago I installed 10.04 to test again(6 months after its release, lots of updates has been done), and browsing worked great. The laptop has been used a lot since then and now yesterday it started stalling again. The most interesting thing is that APT-GET works fine. New software downloads with a snap. Also WGET with a single file works (although it seems to hang at the resolve once in a while).
Why on earth did it suddenly start to behave like this? Nobody with even the knowledge of using SUDO has been using the machine and it has been used ONLY for browsing. Automatic updates are disabled as well. Even weirder, this happens both using the wireless network card and cable.
I have no idea whats going on. Ubuntu 9.10 works always. 10.04 worked the second time (after a few months of updates) but started stalling after a few days. The system itself runs perfectly well, and there is nothing wrong with apt-get and so on as i said.
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 need to prevent that the latest kernel update removes the only kernel that still works in my computer. how can i do this? Currently I have 3 linux kernels versions:
But only the oldest works. With the new update there is a new kernel version (2.6.32-24) that possibly will not boot (like previous 2.6.32-* kernels) and also I expect that, as in previous updates, the oldest kernel will become inaccessible, thus rendering my ubuntu unbootable.
PS: unsolved threads on the underlaying problem: Can't boot default kernel after upgrading from 9.xx to 10.04 lucid Upgrade to 10.04 freezes on the Ubuntu screen
I am building a series of custom kernels...for one of them i am using a kernel that is older than my currently installed ones.
I am using rpm to install this kernel and it will not install, period. i don't get why i can't install this....what does it matter that i am installing an older kernel? and why is fedora/rpm designed to not let me do this?
Code:
There should be an easy way to get around this, but i haven't figured it out yet. i've googled around, no luck. i bounce between kernel versions all the time without problems on my system, so why is rpm setup for strict versions on a kernel? and is there no way around this, and i just have to delete all three of those kernels, i don't really want to. 2 of them are awesome and i shouldn't have to build them again, that would be complete crap! and i wouldn't have this problem on my debian setup, so why fedora? (i generally think fedora is better)
I just did an upgrade and it included the kernel. As time goes by, I will be stuck with a lot of kernels to choose from, and lower disk space. How do I remove an older kernel and everything it's related to it without breaking stuff?
I just had a hard drive failure on my mythtv box that I had been running F14 on. I reinstalled F14 and just got about everything up and running like normal again except that I upgraded the kernel by mistake when I was upgrading everything else to current levels. The problem is that I run a hauppauge pvr150 on this mythtv box, and the code for capturing on this card is broken on the latest kernel version. I have the kernel headers and development files installed for the newest kernel that I can't really use, but I didn't install the kernel headers for the older kernel before the upgrade. Now, I am looking for a way to forcefully install the older kernel development files so that I can compile my the proprietary nvidia drivers against it for my adapter. I downloaded the rpm files from the fedora 14 repository directly. Is there an option for rpm that I can use to force the installation?
I would like to add latest tc+esfq functionality to machines running older distributions, FC3, FC5 etc. I am told I should down load the latest kernel and recompile with the proper patches which I can do. Are there problems with using latest kernels with older distributions, they are all running 2.6.x, but the x has of course gone up since FC3.
