when it is booting (core 6) than after starting all the services ... it is taking almost 10 minutes to get the login screen displayed ..
dun know why it is so ,, is this the problem with me or with any other too ..

i m finding it very boring waiting for the login screen

Use the nosplash boot option when booting, to prevent the graphical splash screen from showing, and see the messages; what procedure is taking that long?

True, Fedora Core is a slow booter, but it shouldn't take 10 minutes in any case. You can speed up the normal boot process by turning off unneeded services (which you should turn off anyway) and if you want to go further, you could compile your own kernel and leave out everything you don't need; this makes the kernel smaller and usually faster to boot.

In your case I guess some init script or other procedure is failing or not doing something right and keeps you waiting for some time X before 'letting go', causing the boot process to be slow. On some older RedHats sendmail was always a troublemaker if it wasn't configured properly, and took many minutes to boot. But whatever the reason, use nosplash kernel boot option and see what is the last message before the long wait: what slows down the boot process. And/or read your logfiles in /var/log/.

FC6 may be a slow booter but I've noticed a significant drop in that time when more recent hardware, like SATA drives, are used. might it be the case that you have an old or slow machine. If your machine is fairly new I would agree that it is a software issue like b0uncer wrote.

m runnin on a 2.93Ghz machine /256 mb RAM .P4 processor /

i dun think that its a bad configuration to work out.. core 5 was working fine ...
my hal service is failing ..also the system message bus was gettin initialized aaftr a long so i removed it from the startup ..

is this the problem ????

If FC5 ran fine then I would expect the same of FC6.

Since you mentioned that services are failing I would suggest that you fix those failing services. If anything fails or is failing they will either prevent or delay the boot time for FC and leave you wondering "what's wrong with my machine".

I think that HAL is a very important service that a lot of other services require to run. So if HAL doesn't start correctly then all of the dependent services will fail to start too and take up even more time to push aside at boot.

I am having the same problems. Here is some output from /var/log/messages ... note the long delays. Anyone have a suggestions? Any way to not have the system wait so long? (after the long delay, the system runs fine - I am using it now). Notice the long delay 14:40 -- 14:47

Feb 7 14:40:14 localhost kernel: ata1: soft resetting port
Feb 7 14:40:14 localhost kernel: ata1: softreset failed (port busy but CLO unavailable)
Feb 7 14:40:14 localhost kernel: ata1: softreset failed, retrying in 5 secs
Feb 7 14:40:19 localhost kernel: ata1: hard resetting port
Feb 7 14:47:17 localhost kernel: ata1: port is slow to respond, please be patient (Status 0x80)
Feb 7 14:47:17 localhost kernel: ata1: port failed to respond (30 secs, Status 0x80)
Feb 7 14:47:18 localhost kernel: ata1: COMRESET failed (device not ready)
Feb 7 14:47:18 localhost kernel: ata1: hardreset failed, retrying in 5 secs
Feb 7 14:47:18 localhost kernel: ata1: hard resetting port
Feb 7 14:47:18 localhost kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 7 14:47:18 localhost kernel: ata1.00: configured for UDMA/100

Could this in any way be related to the way you have your sata disks configured in BIOS?

Personally, I have mine configured as IDE (not as AHCI); have to, in fact, because my XP is on the same controller and it can't stand AHCI. And here's what I noticed with those settings: Fedora (but not Debian, Mandriva, Suse, ...) would be awfully slow in IDE mode (not to mention the extremely slow internet) and fast as lightning whenever I switched to AHCI. Unfortunately, what with the XP thing, I could not run in AHCI mode without going into BIOS every time I switched OS.

But then just recently I found a very very easy solution: I simply upgraded my kernel to 2.6.19 (FC6 DVD has 2.6.18 something) and now IDE mode is just as fast as AHCI. I Hope that helps.

I am VERY new to Linux,so I apologize for my newbie questions....but here goes:

Are you saying that I need to manually upgrade my kernel...overriding yum updater? How do I do that? (and, even more trivially how do I tell which kernel I am running?). One more piece of info: I am doing a dual boot - I have added Fedora Core 6 to my Windows laptop.

I think that upgrading your kernel will be a very daunting task for a new user like yourself. I suggest that if you are just experimenting with Fedora Core then try it as a virtual machine. Virtual machines may be something new to you but it's like running a computer on top of another computer, or in your case, running fedora core on top of windows.
Try going to www.vmware.com and learn about what they do and what virtualization is. Their software is open source so you'll be able to run it without a hassle.
The reason why I mention virtualization is that you won't have to worry about hardware support with VMware. Everything installs just nicely especially if you have a firm grasp of computers. So you can bypass the strange hardware errors for now, get what you want out of Fedora Core, and then, if you so chose, try to solve the problem between your hardware and Fedora Core.

boblux,

Dual-booting should not be the problem (fyi, I am "hexa-booting" (yup, that is six OSes on one box).

To find out which kernel you're running you should open up a terminal (search your menus for one) and type

uname -r

this will return the kernel version.

If it is a 2.6.19, you've already got the latest one. If not, again in your terminal, type:

su -
(root password)
yum update kernel kernel-devel kernel-headers

You will see some downloading (possibly more than you actually asked for) and then you will be prompted to type y or n (yes or no) to accept or refuse the install.

If you are really lazy you would use

yum -y update etc

In this case yum simply does its job without asking for any further confirmation (but that is not recommended, especially for beginners).

narendra.pant

I see you scratching your head. (smiley)

If you want to get things happenin', you should list your hardware specs. Don't leave anything out. Because if you don't provide explicit details, you'll be scratching your head forever, then you'll be bald.

"Im runnin on a 2.93Ghz machine /256 mb RAM .P4 processor /"

That is pretty vague!
What make & model is allot more informative, as an expert can go on-line to the manufactures web site and get the specs if you can't provide.

With such info, it is easier to give good advice.

PS: Updating the kernel is cake walk!

actually i got the problem solved ..
it was some unknown problem.. when i reinstalled it was rocking ...

newas thanks.. for the advise ,, n bald wishes 2

If I were to scratch my head like that, I would be bleedin'.

Yeah:

I've had to do many re-installs of FC6 in an effort to get things right, and found even with using all the same steps and configurations, every new install yielded different results. As of right now, I'm thinkin' of doing another.
But, I have three Linux distributions I'm using and still rather be in FC6.

i did the same

it was my third try ..n each time i got some improvement on the previous one ..
newas comtinue scratchn ur head ,, god bless yu with new hair or a bald pot
--------

holding the thread here .. no jokes now

I was getting this too, and a friend had me add "all-generic-ide" to the end of the kernel line in grub.conf. This did the trick.