UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a Kubuntu 6.06 installation patched current that often, but not always, hangs at a random spot during the boot sequence when the graphical Kubuntu boot sequence screen is up. Often it occurs after "Mounting root filesystem," but it has also occurred after "Setting up ALSA utils" and at other spots. When this occurs, the screen freezes and the machine will not respond to Ctrl+Alt+Del. If I force a reboot by cutting power, often on the second attempt it will boot just fine.
I would blame the hardware, except that it was fine before the upgrade from Breezy, and it never crashes once I get it to boot (it will stay up for weeks at a time). Since it seems to occur more often on the mounting root filesystem entry, I am tempted to think something's wrong with one of the disks (two HDDs in a RAID 1 configuration managed by mdadm). However, fsck ran over the disk on boot the other day, and it found no errors.
Can anyone suggest what I can do to diagnose this problem? Also, what's the best way to run fsck over the drives--do I need to boot from the live CD, and then what?
You could try passing the options 'noapic nolapic' to the kernel at boot time, although it does seem strange that this issue would appear when breezy was fine. Let us know if that's any help.
You could try passing the options 'noapic nolapic' to the kernel at boot time, although it does seem strange that this issue would appear when breezy was fine. Let us know if that's any help.
This is something I haven't done before. Can you tell me how? Thanks.
When the grub screen appears, before it starts booting Linux, press 'e' to edit the currently selected boot option. On the line that begins something like 'kernel /boot/vmlinuz-2.6...' add ' noapic nolapic' to the end.
Modifications made here will only be effective for the current boot. It does not affect your menu.lst file. If the extra options do help, you will need to edit your menu.lst to make sure they get used every time.
When the grub screen appears, before it starts booting Linux, press 'e' to edit the currently selected boot option. On the line that begins something like 'kernel /boot/vmlinuz-2.6...' add ' noapic nolapic' to the end.
OK... I tried this. It's the same as without these parameters. Sometimes the boot sequence completes, and sometimes it hangs, again at random spots. What is the effect of including noapic and nolapic?
Are there any other troubleshooting steps I might try?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.