📄 doc101.htm
字号:
<html><body><a href="doc102.html"><img src=../icons/next.gif alt="Next"></a><a href="doc000.html"><img src=../icons/up.gif alt="Up"></a><a href="doc100.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.5">D.5 How To Load MILO</a></h2><title>How To Load MILO</title><a name="i266"><p>The most commonly supported method of loading MILO is from the Windows NTARC firmware as most shipping systems support this. However, there area wide variety of loading MILO. It may be loaded from:<ul><li> a failsafe boot block floppy,<li> Windows NT ARC firmware, <li> Windows NT AlphaBIOS, <li> Digital's SRM console, <li> an Alpha Evaluation Board Debug Monitor,<li> flash/ROM.</ul><p><h3><a name="sD.5.1">D.5.1 Loading MILO from the Windows NT ARC firmware</a></h3><title>Loading MILO from the Windows NT ARC firmware</title><a name="i267"><a name="i268"><p>Most, if not all, Alpha AXP based systems include the Windows NTARC firmware and this is the prefered method of booting MILO and thusLinux. Once the Windows NT firmware is running and you have the correctMILO image for your system, this method is completely generic.<p>The Windows NT ARC firmware is an environment in which programs can runand make callbacks into the firmware to perform actions. The Windows NTOSLoader is a program that does exactly this.Linload.exe<a name="i269"> is a much simpler program which does just enough to load and execute MILO.It loads the appropriate imagefile into memory at 0x00000000 and then makes a swap-PAL PALcall toit. MILO, like Linux, uses a different PALcode to Windows NT which is why theswap has to happen.MILO relocates itself to 0x200000 and continues on through thePALcode reset entry point as before.<p>Before you add a Linux boot option, you will need to copy linload.exe and the appropriate MILO that youwish to load to someplace that the Windows NT ARC firmware can read from. In the following example, I assume that you are booting from a DOS format floppydisk:<p><ol><li> At the boot menu, select <tt>"Supplementary menu..."</tt><li> At the <tt>"Supplementary menu"</tt>, select <tt>"Set up the system..."</tt><li> At the <tt>"Setup menu"</tt>, select <tt>"Manage boot selection menu..."</tt><li> In the <tt>"Boot selections menu"</tt>, choose <tt>"Add a boot selection"</tt><li> Choose <tt>"Floppy Disk 0"</tt><li> Enter <tt>"linload.exe"</tt> as the osloader directory and name<li> Say "yes" to the operating system being on the same partitionas the osloader<li> Enter "" as the operating system root directory<li> I usually enter <tt>"Linux"</tt> as the name for this boot selection<li> Say "No" you do not want to initialise the debugger at boot time<li> You should now be back in the <tt>"Boot selections menu"</tt>, choose the<tt>"Change a boot selection option"</tt> and pick the selection you just createdas the one to edit<li> Use the down arrow to get <tt>"OSLOADFILENAME"</tt> up and then type in thename of the MILO image that you wish to use, for example <tt>"noname.arc"</tt>followed by return.<li> Press ESC to get back to the <tt>"Boot Selections menu"</tt><li> Choose <tt>"Setup Menu"</tt> (or hit ESC again) and choose <tt>"Supplementary menu,and save changes"</tt> option<li> ESC will get you back to the <tt>"Boot menu"</tt> and you can attempt to bootMILO. If you do not want Linux as the first boot option, then you canalter the order of the boot options in the <tt>"Boot selections menu"</tt>.</ol><p>At the end of all this, you should have a boot selection that looks something like:<p><blockquote><font size=-1><tt><pre>LOADIDENTIFIER=LinuxSYSTEMPARTITION=multi(0)disk(0)fdisk(0)OSLOADER=multi(0)disk(0)fdisk(0)\linload.exeOSLOADPARTITION=multi(0)disk(0)fdisk(0)OSLOADFILENAME=\noname.arcOSLOADOPTIONS=</pre></tt></font></blockquote><p>You can now boot MILO (and then Linux). You can loadlinload.exe<a name="i270">and MILO directly from a file system that Windows NT understands such as NTFS<a name="i271"> or DOS on a hard disk.<p>The contents <tt>OSLOADOPTIONS</tt> are passed to MILO which interpretsit as a command. So, in order toboot Linux directly from Windows NT without pausing in MILO, you couldpass the following in <tt>OSLOADOPTIONS</tt>:<p><blockquote><font size=-1><tt><pre>boot sda2:vmlinux.gz root=/dev/sda2</pre></tt></font></blockquote><p>See <a href="doc102.html#sD.6">D.6</a> for moreinformation on the commands available.<p>Another (rather sneaky) way of loading of loading MILO via the WNT ARC firmwareis to put MILO onto an MS-DOS floppy and call it <tt>fwupdate.exe</tt> and then choosethe "Upgrade Firmware" option.<p><h3><a name="sD.5.2">D.5.2 Loading MILO from the Windows NT AlphaBIOS</a></h3><title>Loading MILO from the Windows NT AlphaBIOS</title><p>With the introduction of the XLT series, Digital changed the systemconsole interface for its NT systems from ARC to AlphaBIOS. AlphaBIOSis a screen-oriented interface which should be more familiar to PCusers. This change in console interface necessitates a change insetup procedure for those who wish to run Linux/Alpha on AlphaBIOS-basedsystems.<p>The first thing you must do is to install the latest version of AlphaBIOSon your system. This can be obtained from Digital's "System Software andDriver Updates" Web page,<br><tt><a href="http://www.windows.digital.com/support/sysoft.htp">http://www.windows.digital.com/support/sysoft.htp</a></tt>.Download the ZIP file, unzip it, and install it as follows:<p><ul><li> Copy the files to a FAT-formatted floppy<li> Turn on the system and insert the floppy. At the openingscreen, press F2 to go into setup mode<li> Select "Upgrade AlphaBIOS"<li> Follow the directions on the screen</ul><p>Once your AlphaBIOS is at the latest revision level, you can startbootstrapping your system as follows:<p><ul><li> Create a FAT-formatted floppy with the following files:<ul><li> linload.exe (from this directory)<li> milo (the version appropriate to your system)</ul><li> Turn on the system and insert the floppy. At the openingscreen, press F2 to go into setup mode<li> Select "Utilities->OS Selection Setup..."<li> Press INSERT to add a new operating system selection<li> For "Boot Name", enter something like "Linux". Press TABto get over to the next field.<li> Press down-arrow until the selection for "Boot File" is "A:".TAB over to the next field<li> Enter "linload.exe". TAB *twice* (i.e. skip the OS Pathload device -- it's irrelevant)<li> Enter "" for the OS Path load file<li> Press ENTER to add the selection.</ul><p>At this point, AlphaBIOS will probably put up a big, unfriendly dialogbox labelled "Warning: Operating System Selection not valid!". Ignorethis error (it's only a problem for NT) and press ENTER to continue.<p><ul><li> Press F10 to save the changes you just made; press ENTER toconfirm the changes.<li> Press ESC twice to get back to the opening screen.<li> Use the up and down arrows to select the boot selection youjust added, and press ENTER to boot it.<li> AlphaBIOS will load linload, which will in turn load MILO.When you get to the MILO prompt, proceed as you would for anormal ARC-based system installation.</ul><p>If you dedicated the first partition of your first disk drive to a smallFAT partition for booting (as the installation procedure advises you to),then once Linux is installed you should copy linload.exe and milo tothis partition. Once you shut down, you can then modify the Linux menuselection to load MILO from this partition as follows:<p><ul><li> At the opening screen, select F2 to go into setup mode<li> Select "Utilities->OS Selection setup"<li> Highlight the entry for Linux, then press F6 to edit it.<li> TAB over to the device portion of the "Boot File" line.Use the up and down arrow keys to select the hard-diskpartition where linload and milo reside (typically"Disk 0 Partition 1" or "Disk 1 Partition 1"). PressENTER to confirm the selection<li> If you wish to auto-boot linux after MILO is loaded, thenTAB over to the "OS Options" line and enter the MILO commandto boot the system, e.g. "boot sda2:vmlinux.gz"Press ENTER to confirm the selection.<li> Press F10 to save the changes. Press ENTER to confirm.</ul><p>Once you have done this, booting and running Linux on an AlphaBIOS basedsystem should be very similar to doing so on an ARC system.<p><h3><a name="sD.5.3">D.5.3 Loading MILO from the Evaluation Board Debug Monitor</a></h3><title>Loading MILO from the Evaluation Board Debug Monitor</title><p>Evaluation boards (and often designs cloned from them) includesupport for the Alpha Evaluation Board Debug Monitor. Consultyour system document before considering this method of bootingMILO. The following systems are <em>known</em> to include Debug Monitorsupport:<ul><li>AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>)<li>EB64+ (Section <a href="doc101.html#sD.5.7.4">D.5.7.4</a>)<li>EB66+ (Section <a href="doc101.html#sD.5.7.3">D.5.7.3</a>)<li>EB164 (Section <a href="doc101.html#sD.5.7.6">D.5.7.6</a>)<li>PC164 (Section <a href="doc101.html#sD.5.7.7">D.5.7.7</a>)</ul><p>Before you consider this method, you should note that the earlyversions of the Evaluation Board Debug Monitor did not include videoor keyboard drivers and so you must be prepared to connect anothersystem via the serial port so that you can use the Debug Monitor.Its interface is very simple and typing help shows a whole heapof commands. The ones that are most interesting includethe word <tt>boot</tt> or <tt>load</tt> in them.<p>The Evaluation Board Debug Monitor can load an image either via the network(netboot) or via a floppy (flboot). In either case, set the bootaddress to 0x200000 (<tt>> bootadr 200000</tt>) before booting theimage. <p>If the image is on floppy (and note that only DOS formatted floppiesare supported), then you will need to type the following command:<p><blockquote><font size=-1><tt><pre> AlphaPC64> flboot <MILO-image-name></pre></tt></font></blockquote><p><h3><a name="sD.5.4">D.5.4 Loading MILO from a Failsafe Boot Block Floppy</a></h3><title>Loading MILO from a Failsafe Boot Block Floppy</title><p>Only the AxpPCI33 is <em>known</em> to include failsafe boot blockfloppy support (Section <b><font size=+1>??</font></b>).<p>If you do not have a standard pre-built MILO .dd image, then you may need tobuild an SRM boot block floppy. Once you have built MILO, you need to do the following on Digital Unix box:<p><blockquote><font size=-1><tt><pre> fddisk -fmt /dev/rfd0a cat mboot bootm > /dev/rfd0a disklabel -rw rfd0a 'rx23' mboot bootm</pre></tt></font></blockquote><p>Or on a Linux box:<p><blockquote><font size=-1><tt><pre> cat mboot bootm > /dev/fd0 </pre></tt></font></blockquote><p> If you have a standard MILO image available (say <tt>MILO.dd</tt>)then you would build a boot block floppy using the following command:<p><blockquote><font size=-1><tt><pre> dd if=MILO.dd of=/dev/fd0 </pre></tt></font></blockquote><p><h3><a name="sD.5.5">D.5.5 Loading MILO from Flash</a></h3><title>Loading MILO from Flash</title><p>There are a number of systems where MILO can be blown into flashand booted directly (instead of via the Windows NT ARC firmware):<ul><li>AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>)<li>Noname (Section <a href="doc101.html#sD.5.7.1">D.5.7.1</a>)<li>EB66+ (Section <a href="doc101.html#sD.5.7.3">D.5.7.3</a>)<li>EB164 (Section <a href="doc101.html#sD.5.7.6">D.5.7.6</a>)<li>PC164 (Section <a href="doc101.html#sD.5.7.7">D.5.7.7</a>)</ul><p><h3><a name="sD.5.6">D.5.6 Loading MILO from the SRM Console</a></h3><title>Loading MILO from the SRM Console</title><a name="i272"><p>The SRM (short for System Reference Manual) Console knows nothing about filesystems or disk-partitions, it simply expects that the secondary bootstrap loader occupies a consecutive range ofphysical disk sectors starting from a given offset. The information describingthe secondary bootstrap loader (its size and offset) is given in the first 512 byte block. To load MILO via the SRM you must generate that structure on a device which the SRM can access (such as a floppy disk).This is what <tt>mboot</tt> and <tt>bootm</tt>, <tt>mboot</tt> is the first block (orboot description) and <tt>mboot</tt> is the <tt>MILO</tt> image rounded up to a512 byte boundary.<p> To load MILO from a boot block device, either build <tt>mboot</tt>and <tt>bootm</tt> and push them onto the boot deviceusing the following command:<p><blockquote><font size=-1><tt><pre> $ cat mboot bootm > /dev/fd0</pre></tt></font></blockquote><p>Or, grab the appropriate <tt>MILO.dd</tt> from a web site and write it onto theboot device using either <tt>RAWRITE.EXE</tt> or <tt>dd</tt>.<p> Once you have done that you can boot the SRM console and use one of itsmany commands to boot MILO. For example, to boot MILO from a boot block floppyyou would use the following command:⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -