FedoraThis forum is for the discussion of the Fedora Project.
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.
Hi, I have a same case as of kevalvora, My PC specs are ditto same... I think the solution to this crash is to enable your CD/DVD drive as Master and physically uninstall any Modem/LAN cards from your system. Then check it out... I will let you know by doing this....
Another thing,, kevalvora are you using IDE Hard drive or SATA ??
rajibghosh thank you so much.....its been approximately 1 month i was with this problem.....now its solved.......thank you so much
So, basically we are turning our Multi Core Processors to Single Cores rite?
As mentioned earlier, switching the computer to work in Single-Processor mode got things running with the default i686 kernel on Fedora Core 9 DVD. So figured, a kernel update/build could help. Update is simpler.
A BIOS update could help, but I was already running what Intel had on offer on their website (BIOS Update 1087 [GC11020M.86A] 1087 1/30/2007).
After fighting with 'Update System' and 'NetworkManager', managed to download Kernel Update.
Upgraded my machine (Intel Pentium-D on Intel D102GGC2 motherboard, 512x2 DDR2, 160GB PATA HDD) from 2.6.25-14.fc9.i686 to 220.127.116.11-86.fc9.i686.
Enabled multi-processor support in BIOS and restarted the machine. Voila! Machine booted up beautifully.
Could login. System monitor showed dual-cpu.Then the keyboard got stuck. The mouse got stuck soon afterwards. Both are PS/2 units connected via IoGear KVM switch.
Connected the peripherals directly to the computer and restarted. No luck. 5 minutes into system, the peripherals would get stuck again.
I noticed this message at computer start everytime:
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ... failed.
...trying to set up timer as Virtual Wire IRQ... works
So figured that their could be a problem between the kernel and PS/2 controller.
Connected a USB mouse to the computer and re-started. Worked beautifully. Although the PS/2 keyboard got stuck, the USB mouse kept working. Swapped the PS/2 keyboard with a USB one, and here I am ... typing out a report on my PC running FC9.
P.S: I guess I will have to build the kernel after all to enable PS/2 functionality.
Installed in 20 minutes flat. The usual "8254 timer bug" message at boot up. But the OS started.
Loaded the default gnome desktop. An icon on the taskbar informed that Non-OpenSource drivers were available for my PC.
One-click install for the ATI drivers. Enabled full-desktop effects (Compiz). No xorg.conf edits.
The Network Manager didn't act up either. Detected that the machine was connected, received an IP and business as usual. Didn't have to disable the service as I had to do on FC9.
Looks like the 1 month I waited for release of FC9 (instead of dnloading FC8) was a total waste.