Difference between revisions of "Pegasos"

From Earlham CS Department
Jump to navigation Jump to search
Line 1: Line 1:
−
==Netbooting==
+
==SmartFirmware==
−
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:
+
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 good tutorials for a variety of boot configurations.
 +
 
 +
You can save environment variables in SmartFirmware by editing the nvramrc script.
 +
* To begin editing, type <code>nvedit</code> and make any desired changes.
 +
* Use the commands below to navigate the editor; arrow keys do not work.
 +
** control-e - end of line
 +
** control-n - next line
 +
** control-f - forward
 +
** control-b - back
 +
** control-c - exit
 +
*When finished, hit control-C to exit the editor.
 +
*Finally, type <code>nvstore</code> to save your changes.
 +
 
 +
===Netbooting===
 +
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:dhcp,0.0.0.0,,0.0.0.0
 
setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0
Line 6: Line 20:
 
(The double comma indicates an empty boot file name--it is supplised by the DHCP server.)  <code>eth</code> is an alias for the 100Mbit ethernet device and <code>geth</code> is an alias for the Gigabit device.  Now to boot, simply type <code>boot</code> and hit return. The red cables are hooked up to the 100baseT interfaces, and the yellow ones are hooked up to the 1000baseT interfaces.
 
(The double comma indicates an empty boot file name--it is supplised by the DHCP server.)  <code>eth</code> is an alias for the 100Mbit ethernet device and <code>geth</code> is an alias for the Gigabit device.  Now to boot, simply type <code>boot</code> and hit return. The red cables are hooked up to the 100baseT interfaces, and the yellow ones are hooked up to the 1000baseT interfaces.
  
−
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.
+
===Booting from disk===
−
 
+
The current working boot configuration is as follows:
−
nvedit commands:
+
<pre>
−
* control-e - end of line
+
boot-device = hd:0                                                             
−
* control-n - next line
+
boot-file = /boot/vmlinuz-2.6.8-powerpc root=/dev/hda1 console=ttyS1,115200n1
−
* control-f - forward
+
</pre>
−
* control-b - back
+
You can modify these variables using the <code>setenv</code> command; optionally saving them in nvramrc according to the above instructions.
−
* control-c - exit
 

Revision as of 13:56, 12 April 2006

SmartFirmware

The Open Desktop Workstations (ODWs) use SmartFirmware. The SmartFirmware user manual has good tutorials for a variety of boot configurations.

You can save environment variables in SmartFirmware by editing the nvramrc script.

  • To begin editing, type nvedit and make any desired changes.
  • Use the commands below to navigate the editor; arrow keys do not work.
    • control-e - end of line
    • control-n - next line
    • control-f - forward
    • control-b - back
    • control-c - exit
  • When finished, hit control-C to exit the editor.
  • Finally, type nvstore to save your changes.

Netbooting

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.) eth is an alias for the 100Mbit ethernet device and geth is an alias for the Gigabit device. Now to boot, simply type boot and hit return. The red cables are hooked up to the 100baseT interfaces, and the yellow ones are hooked up to the 1000baseT interfaces.

Booting from disk

The current working boot configuration is as follows: 

boot-device = hd:0                                                              
boot-file = /boot/vmlinuz-2.6.8-powerpc root=/dev/hda1 console=ttyS1,115200n1

You can modify these variables using the setenv command; optionally saving them in nvramrc according to the above instructions.

Retrieved from "https://wiki.cs.earlham.edu/index.php?title=Pegasos&oldid=1558"