doc105.htm
来自「Reh Hat user manual. really goooood」· HTM 代码 · 共 84 行
HTM
84 行
<html><body><a href="doc106.html"><img src=../icons/next.gif alt="Next"></a><a href="doc000.html"><img src=../icons/up.gif alt="Up"></a><a href="doc104.html"><img src=../icons/previous.gif alt="Previous"></a><a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a><a href="doc123.html"><img src=../icons/index.gif alt="Index"></a><hr><h2><a name="sD.9">D.9 Problem Solving.</a></h2><title>Problem Solving.</title><p>Here are some common problems that people have seen, together with thesolutions.<p><b>Reading MS-DOS floppies from the Evaluation Board Debug Monitor.</b> <p> Some of the older versions of the Evaluation Board Debug Monitor (pre-version 2.0)have a problem with DOS format flopies generated from Linux.Usually, the Debug Monitor can load the first few sectors all right, but then goesinto an endless loop complaining about "bad sectors." Apparently,there is an incompatibility between the DOS file system as expected bythe Debug Monitor and the Linux implementation of DOSFS. To make thelong story short: if you run into this problem, try using DOS to writethe floppy disk. For example, if loading the file <tt>MILO.cab</tt>doesn't work, use a DOS machine, insert the floppy and then do:<p><blockquote><font size=-1><tt><pre> copy a:MILO.cab c: copy c:MILO.cab a: del c:MILO.cab</pre></tt></font></blockquote><p> Then try booting from that floppy again. This normally solves the problem.<p><b>MILO displays a long sequence of <tt>O></tt> and does not accept input.</b><p>This usually happens when MILO was built to use COM1 as a secondary consoledevice. In such a case, MILO echo output to COM1 and accepts input fromthere also. This is great for debugging but not so great if you havea device other than a terminal connected.If this happens, disconnect the device or power it down until the Linuxkernel has booted.Once Linux is up and running, everything will work as expected.<p><b>MILO complains that the kernel image has the wrong magic number</b><p> Older versions of MILO did not support the ELF object file format and socould not recognise an ELF image and this might be your problem.If this is reported, upgrade to the latest MILO that you can find. All2.0.20 and beyond MILOs support ELF.On the other hand it could be that the image is indeed damaged. You shouldalso note that MILO does not yet automatically distinquish between GZIP'dand non-GZIP'd images; you need to add the ".gz" suffix to the file name.<p><b>MILO prints "...turning on virtual addressing and jumping to the Linux Kernel" andnothing else happens</b><p>One obvious problem is that the kernel image is wrongly built or is built for anotherAlpha system altogether.Another is that the video board is a TGA (Zlxp) device and the kernel has been builtfor a VGA device (or vice versa).It is worth building the kernel to echo to COM1 and then connecting a terminal tothat serial port or retrying the kernel that came with the Linux distribution that youinstalled.<p><b>MILO does not recognise the SCSI device</b><p>The standard MILO images include as many device drivers as are known to be stablefor Alpha (as of now that includes the NCR 810, QLOGIC ISP, Buslogic and Adaptec 2940sand 3940 cards). If your card is not included, it may be that the driver is not stableenough on an Alpha system yet. Again, the latest MILO images are worth trying. Youcan tell which SCSI devices a MILO image has built into it by using the "show" command.<p><p><hr><a href="doc106.html"><img src=../icons/next.gif alt="Next"></a><a href="doc000.html"><img src=../icons/up.gif alt="Up"></a><a href="doc104.html"><img src=../icons/previous.gif alt="Previous"></a><a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a><a href="doc123.html"><img src=../icons/index.gif alt="Index"></a><hr></body></html>⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?