If you enter MP-BIOS bug :8254 timer not connected to IO-APIC fedora into http://google.com/linux

you will find a variety of explanations and solutions.

Adding acpi=noirq or noapic or nolapic to the kernel boot line seems to work.

Also, see here: http://www.linuxquestions.org/questi...02#post2924602

Welcome to LQ!

You should also know that Fedora 8 is an old distribution, and no longer supported. (It's so old that support for Fedora 9 will be dropped next month!)

The latest release of Fedora (Fedora 11) should be available for downloading next week.

Fedora follows a fairly aggressive release schedule, with new releases every six to nine months, and support for any release more than one release less than the current release is usually terminated a month after the current release in made. (See https://fedoraproject.org/wiki/Releases/Schedule for details.)

As to your timer bug, you could also try the enable_8254_timer option on the GRUB kernel line. (I had a Gateway laptop that displayed that "bug" message, and that "enable" option fixed it.)

Here's a copy of the /boot/grub/grub.conf file I used on that laptop that I found in an old post of mine. (Note that I was using FC6 back then.)

hello.
before I used fc10 but when I wanted to install a package it showed that need many packages
and some of them were from fc10 and it should had them so I want to use fc8 .
do you have any idea to fix my fc10
thanks (PTrenholme)
Bye

and I forget to ask a question .
when I should type this note.
pleaseeeeeee help.

and Iforgot to ask another queston.
when I should type this text.
please answere me.
bye bye

Depending on how you installed your Fedora 10 system, you may or may not have installed all the packages you needed to get some package running. When yum tells you that it needs to install some packages, well, that's because you need to install them.

In other word, there's nothing to "fix." Just let your system access the repositories over the Internet, and the needed packages will be downloaded.

Note that I can't be any more specific since you failed to include either the name of the package(s) that caused your problem or the packages you needed to install.

I don't understand the meaning of the above post you made. (For one thing, there is no question in the note. Perhaps you forgot the question mark?)

You also forgot that there's an "Edit" button. There's no need to post three in a row. Please, next time instead edit the post and add whatever else you need to add.

oh.
please excuse me I sent 3 replies and I didn't want to send 3 post
and also when I sent them it didn't show them.
please excuse me ,pleaseeeeeeee .
I'm sorry(PTrenhome and i92guboj).
and PTrenholme ,when I asked when Ishould type this not,my mean was
when I should type that code in your first reply?

Ah. Sorry, I thought that it was clear that I was referring to th /boot/grub/grub.conf file contents. (Note the first line - the command - in the block.)

Anyhow, that output was, as I said, an example only. It was very specific to the old laptop that I discarded several years ago.

What I was suggesting was that you modify the kernel line in your GRUB configuration file to include the enable_8524_timer option. The point in the listing I posted was only to show you one way that the suggestion could be implemented.

Note, however, that GRUB includes a simple, keyboard only, editor that can be used to make temporary changes in your GRUB boot configuration file. (The instructions are printed at the bottom of the GRUB menu screen, and easily accessed by pressing the "Escape" key when the menu is first displayed.) So, to test a change to the GRUB configuration, just press "Escape" when the menu is displayed, use the arrow keys to select the OS boot line, and press "e" (or the equivalent key on your keyboard) to see the boot stanza for that OS. Then highlight the kernel line in that stanza, press "e" to edit it, add the enable_8524_timer option, press "Enter" to return the the full stanza listing, and then "b" to boot from the modified stanza to test it.

If the test is successful, you will then need to use whatever editor you wish to use to edit /boot/grub/grub.conf. (You must, of course, have "root" access to edit that file.)

The point in trying a temporary change is, of course, that, if it doesn't work, then your actual configuration file is unchanged so you're no worse-off then you were before you tried the change.