Difference between revisions of "Pegasos"

From Earlham CS Department
Jump to navigation Jump to search
(Netbooting: add 0.0.0.0 magic)
Line 1: Line 1:
 
==Netbooting==
 
==Netbooting==
The [http://www.pegasosppc.com/odw.php Open Desktop Workstations] (ODWs) use SmartFirmware.  The SmartFirmware [http://www.pegasosppc.com/manuals/SFUserManual.pdf user manual] has a good netbooting tutorial, but the ODWs we have don't seem to support DHCP. As such, configure the boot-device explicitly with the server IP, file name, client IP, and timeouts, like so:
+
The [http://www.pegasosppc.com/odw.php Open Desktop Workstations] (ODWs) use SmartFirmware.  The SmartFirmware [http://www.pegasosppc.com/manuals/SFUserManual.pdf user manual] has a good netbooting tutorial.  The DHCP support in the firmware is slightly buggy and requires inserting a client and server IP of 0.0.0.0 in the boot-device string, like so:
 
<pre>
 
<pre>
setenv boot-device eth:159.28.234.1,vmlinuz.chrp,159.28.234.140,,3,3
+
setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0
 
</pre>
 
</pre>
 +
(The double comma indicates an empty boot file name--it is supplised by the DHCP server.)
  
 
This can be saved in the firmware by editing the nvramrc script.  To begin editing, type <code>nvedit</code> and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use).  When finished, hit control-C to exit the editor.  Then, type <code>nvstore</code> to save your changes.
 
This can be saved in the firmware by editing the nvramrc script.  To begin editing, type <code>nvedit</code> and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use).  When finished, hit control-C to exit the editor.  Then, type <code>nvstore</code> to save your changes.

Revision as of 01:45, 9 February 2006

Netbooting

The Open Desktop Workstations (ODWs) use SmartFirmware. The SmartFirmware user manual has a good netbooting tutorial. The DHCP support in the firmware is slightly buggy and requires inserting a client and server IP of 0.0.0.0 in the boot-device string, like so:

setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0

(The double comma indicates an empty boot file name--it is supplised by the DHCP server.)

This can be saved in the firmware by editing the nvramrc script. To begin editing, type nvedit and add the above command to the end of the list (change 'eth' to the devalias of whatever ethernet device you wish to use). When finished, hit control-C to exit the editor. Then, type nvstore to save your changes.