Fedora core 18.104.22.168.771_FC2 updated kernel gets stuck at boot!
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
No idea, but which Intel processor is in you Dell box? If its a "Pentiun 4," you should probably be using an I686, smp, core version. And why the older FC2 release instead of FC3?
So I suggest you try downloading 2.6.10-1.770_FC3smp (if you have a P4) and installing it.
But, as I said, I have no idea if this would help.
Oh, I do recall that there was a post similar to yours where the boot seemed to "hang" when it was, in fact, just waiting for keyboard input. Try booting without the "rhgb" and "quiet" options to see what the boot loader is actually doing. (You can select the "edit" option at the GRUB prompt to change your boot options.)
What is smp?.. tIts a P4 3.2 Ghz. I sort of fixed the problem.. but i dunno what it means..
i restarted in the 2.6.5 version and went to /etc/sysconfig/clock and changed the UTC=false and ARC=false values to UTC=true and ARC=true.. and now the computer restarts just fine ( although the clock time in the lower right corner is at some weird time)
Well, again I can't help there. Except to say that those setting should have been set correctly if you had installed a build for your hardware. (See below.)
The SMP stands for "symetric multi-processor" and the I686 means "P4." The point is that Intel implemented "hyper-thread" as, essentially, a dual-processor chip. So when you install FC3 for I686, smp, you're installing software that will use the "hyper-threading" and the full P4 instruction set. This, generally speaking, is a "good thing."
Well, you got me courious, so I "googled" ARC. This stands fro "Adaptive Replacement Cache," and I think what you did was, in essence, tell the CPU to use it L1 (or, perhaps, L2 -- I'm somewhat quessing here) cache differently.
Anyhow, FYI, I'm running a "3.06Gh, P4, Hyperthread" processor using 2.6.10-1.770_FC3smp, and I get this
By the way, I think UTC means "Universal Time Code," which used to be "GMT" before it was foune to not be PC to refer to "Grenwitch, England, GB" as the standard for time references. Setting UTC to "true" probably just set your time to 8 hours ahead of LA time.
Well, unless someone put an Alpha processor into your Dell box, I can't see how the ARC (which, I see, is NOT what I found on Goggle -- thanks for the correct information) setting would make any difference.
And I can't see how ANY clock setting would effect your booting.
My guess -- and it's only a guess -- is that the system was attempting to install a new driver, or access some hardware, when it hung, and that device or hardware was marked as "unavailable" or "not installed" so the next boot skipped that step. (If I'm correct, you could set you clock settings back to "off," and still boot with no problem.)
My recollection is that there are two more steps in the boot after the clock is initialized. Perhaps there was a problem there.
Oh, you know, I think the clock initialization may attempt to access an Internet or network time server for a time check. Perhaps it wasn't "hung," but just waiting for a connection time-out. And then it marked that connection as unavailable, so it no longer waits for it. (When I installed FC3, there was an active time server on our local network, and the proxy server was running and available, so -- if that's what's happening -- I didn't see any "hang." Although the "time" initialization does seem to take a while.)
As far as I can make out, the hardware RTC (realtime clock) interface on the SC420 is not 100% standard. It's got to be a v-e-r-y subtle difference, since FC2 2.6.9 boots just fine on an SC420, and 2.6.10 chokes on RTC set.