解决Linux安装问题-优快云博客

新主机:

CPU: AMD 闪龙2800+

主板:昂达N61V (芯片组nVIDIA MPC61)

安装fc5

插入第一张光盘,在:kernel_thread_helper+0x4/0xb 就在这里就停住不动了.诸处寻因不得果.

开始以为主板不支持linux,后得知只要芯片组支持就可以了,而且这个芯片组是支持了,因为据说安装uBUNTU没问题.

后改装 Hiweed GNU/Linux,是一套计算机操作系统，基于 Debian 和 Ubuntu 构建.Desktop 版本不用安装就能直接在光盘上运行.

于是下载刻盘安装:

[4294668.019000]..MP-BIOS bug:8254 timer not connected to IO-APIC
[4294668.019000] Kernel panic - not syncing: IO-APIC + timer doesn't work!Boot with apic=debug and send a report.Then try booting with the 'noapic' option
[4294668.019000]又停住了.

上网搜得MP-BIOS bug:8254 timer not connected to IO-APIC 的解决办法:

重启电脑,按DEL(或其它相关键)进入BIOS设置,将ACPI项设为disable.

现在可以进入Hiweed了.而且安装fc5的问题也解决了.

详情如下:全文见http://download.nvidia.com/XFree86/nforce/1.0-0301/KnownProblems.html

Network and other devices randomly stop working when ACPI is enabledThis problem may be caused by an incorrect ACPI table entry that causes the timer interrupt to be incorrectly configured.

If the kernel console boot trace (viewable using dmesg) contains messages such as these:

..MP-BIOS bug: 8254 timer not connected to IOAPIC ...trying to set up timer (IRQ0) through the 8259A . failed. ...trying to set up timer as Virtual Wire IRQ... failed. ...trying to set up timer as ExtINT IRQ... works.

then the incorrect ACPI table entry is present. On 2.6 kernels, this can be worked around by specifying the 'acpi_skip_timer_override' boot line option. An alternative workaround is to disable ACPI in the BIOS or by using the 'acpi=off' boot line option.

另搜得日志一篇,讲升级后的硬件安装linux出现的问题,有点用:http://larrythecow.org/

Hardware Upgrade

I upgraded my hardware to a brand new energy efficient dualcore AMD and that's where the problems began. Since I don't and will not use SLI I ordered the cheap Asus M2N-E mainboard and since Kingston memory wasn't available I ordered GEIL memory instead, they are much more cheaper also. I got a 2GB kit for the same price as the kingston 1GB kit would have cost.

I had an nforce board before so the upgrade act wasn't that complicated, I just shifted the old harddrive into the new computer and Gentoo bootet up without a problem.. well at least that's what I first thought.

The computer hardlocked while emerging wine and a futher investigation showed that the memory was running with "auto" setting in the Asus bios. Manually setting the CAS-Latency to the right values resulted in a bios hardlock every time you entered the memory settings. So I restored the bios defaults, bootet up Windows and flashed the bios with the latest available rev. 0203 version, this time I could setup the CAS-Latency and all worked fine as far as I bootet up Gentoo, which resulted in a kernel panic "MP-BIOS bug: 8254 timer not connected to IO-APIC". I connected my HDD to the old computer and it bootet up fine, then I added the "noapic" kernelparameter to lilo and now my computer is up and running again, yay!

by psy@arcticnightfall.de (Timo Gurr) at August 16, 2006 10:37 PM :: Germany