Difference between revisions of "Pegasos"
| Line 28: | Line 28: | ||
</pre> | </pre> | ||
(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. | ||
| + | |||
| + | ====Netbooting the Unified Root==== | ||
| + | As of May 18, 2006, these are the current client firmeware settings necessary to boot lf[1-n] via the Debian unified root setup. These must be set on every single client node in order to netboot successfully. If they are not there already, add or correct the following lines in <code>nvedit</code>: | ||
| + | <pre> | ||
| + | setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0 | ||
| + | setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1 | ||
| + | </pre> | ||
===Booting from disk=== | ===Booting from disk=== | ||
Revision as of 17:14, 18 May 2006
Contents
Serial Console
Use a serial console to connect to LittleFe/PPC. Currently this is done by running:
minicom -o lf0
on ACL13, after verifying that the serial cable is connected properly (it should be connected between the serial port labelled '2' on the back of ACL13 and only serial port on the ODW board in question).
Also see http://www.ppczone.org/article.php?article=serialconsole
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
nveditand 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
nvstoreto 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.
Netbooting the Unified Root
As of May 18, 2006, these are the current client firmeware settings necessary to boot lf[1-n] via the Debian unified root setup. These must be set on every single client node in order to netboot successfully. If they are not there already, add or correct the following lines in nvedit:
setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0 setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1
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.
