error during booting(Linux)
I am having a trouble which I thought not to post in any forum.(since many people already have this problem)
Whenever I boot my Ubuntu 7.10, during boot I get the error
My system boots after showing this error. I didn't much cared for this for a while. But now I'm getting curious why do I get this error. And on the net I'm finding only solution which only bypasses this error.
I also found an interesting information about this, in which someone told that this error is because the linux distro is not up to date with the hardware. Well this is something not very common, as I'm having the latest ubuntu version.
If someone finds a solution for this error do inform me. TIA...
Whenever I boot my Ubuntu 7.10, during boot I get the error
..MP-BIOS bug: 8254 timer not connected to IO-APICMy system boots after showing this error. I didn't much cared for this for a while. But now I'm getting curious why do I get this error. And on the net I'm finding only solution which only bypasses this error.
I also found an interesting information about this, in which someone told that this error is because the linux distro is not up to date with the hardware. Well this is something not very common, as I'm having the latest ubuntu version.
If someone finds a solution for this error do inform me. TIA...
Comments
Try the following:
1. (As root, or use sudo)
sudo cp /boot/grub/menu.1st /boot/grub/menu.1st.old (make a backup of the file)
sudo gedit /boot/grub/menu.1st
Make sure you have #defoptions=noapic.
2. Run
update grub
and reboot your system. Now, using dmesg you can view the output and verify whether you still get the error.
Second Alternative
Turn of APIC (Advanced Programmable Interrupt Controller..for "advanced" interrupt (IRQ) management) in the BIOS on bootup. I don't think you'll have a problem without it, but give it a shot.
In a subsequent reply, I will try to zero down on the cause of this error. Let me know if these fixes work. You could also try and update ubuntu..maybe the new kernel updates have patched this error.