Pegasos - Revision history

Charliep: /* Upgrading the firmware */

2006-11-03T19:44:48Z

Upgrading the firmware

← Older revision		Revision as of 19:44, 3 November 2006
Line 62:		Line 62:
	5) Undo the dhcpd and <code>boot-file</code> changes. Restart dhcpd.		5) Undo the dhcpd and <code>boot-file</code> changes. Restart dhcpd.

			The current nvscript for clients (lf1-lfn) as of July 20 2006:
	The current nvscript as of July 20 2006:
	1: devalias eth /pci@80000000/ethernet@D		1: devalias eth /pci@80000000/ethernet@D
	2: devalias geth /ethernet/port1		2: devalias geth /ethernet/port1
	3: setenv boot-file vmlinuz-2.6.15.6 ip=dhcp root=/dev/nfs init=/linuxrc console=ttyS1,115200n1		3: setenv boot-file vmlinuz-2.6.15.6 ip=dhcp root=/dev/nfs init=/linuxrc console=ttyS1,115200n1
	4: setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0		4: setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0

Charliep: /* Booting from disk */

2006-11-03T16:17:06Z

Booting from disk

← Older revision		Revision as of 16:17, 3 November 2006
Line 45:		Line 45:
	<pre>		<pre>
	boot-device = hd:0		boot-device = hd:0
	boot-file = /boot/vmlinuz-2.6.~~8-powerpc~~ root=/dev/hda1 console=ttyS1,115200n1		boot-file = /boot/vmlinuz-2.6.15.6 root=/dev/hda1 console=ttyS1,115200n1
	</pre>		</pre>
	You can modify these variables using the <code>setenv</code> command; optionally saving them in nvramrc according to the above instructions.		You can modify these variables using the <code>setenv</code> command; optionally saving them in nvramrc according to the above instructions.

Lemanal at 20:07, 20 July 2006

2006-07-20T20:07:33Z

← Older revision		Revision as of 20:07, 20 July 2006
Line 61:		Line 61:

	5) Undo the dhcpd and <code>boot-file</code> changes. Restart dhcpd.		5) Undo the dhcpd and <code>boot-file</code> changes. Restart dhcpd.


			The current nvscript as of July 20 2006:
			1: devalias eth /pci@80000000/ethernet@D
			2: devalias geth /ethernet/port1
			3: setenv boot-file vmlinuz-2.6.15.6 ip=dhcp root=/dev/nfs init=/linuxrc console=ttyS1,115200n1
			4: setenv boot-device eth:dhcp,0.0.0.0,,0.0.0.0

Charliep at 16:32, 14 June 2006

2006-06-14T16:32:52Z

← Older revision		Revision as of 16:32, 14 June 2006
Line 1:		Line 1:
	==Serial Console==		===Serial Console===
	Use a serial console to connect to LittleFe/PPC. Currently this is done by running:		Use a serial console to connect to LittleFe/PPC. Currently this is done by running:
	<pre>		<pre>
Line 10:		Line 10:
	Also see http://wiki.cs.earlham.edu/index.php/Little-Fe_PPC for instructions on setting-up Little-Fe/PPC boards.		Also see http://wiki.cs.earlham.edu/index.php/Little-Fe_PPC for instructions on setting-up Little-Fe/PPC boards.

	==SmartFirmware==		===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 good tutorials for a variety of boot configurations.		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.

Line 48:		Line 48:
	</pre>		</pre>
	You can modify these variables using the <code>setenv</code> command; optionally saving them in nvramrc according to the above instructions.		You can modify these variables using the <code>setenv</code> command; optionally saving them in nvramrc according to the above instructions.

			===Upgrading the firmware===
			These notes come from http://www.bplan-gmbh.de/news/update_en.html Make sure that you have a stable power supply, cables, etc. during this process. If you loose connectivity or power you will probably zorch the motherboard.

			1) Put the new firmware in /boot on lf0.

			2) Set the <code>boot-file</code> variable to point to the new firmware image name.

			3) Change the <code>filename</code> in /etc/dhcpd3/dhcpd.conf on lf0 to point to the new firmware image name. Restart dhcpd.

			4) Reboot the board, follow the on-screen prompts.

			5) Undo the dhcpd and <code>boot-file</code> changes. Restart dhcpd.

Charliep: /* SmartFirmware */

2006-06-13T19:12:27Z

SmartFirmware

← Older revision		Revision as of 19:12, 13 June 2006
Line 21:		Line 21:
	** control-b - back		** control-b - back
	** control-c - exit		** control-c - exit
			** control-d - delete character
	*When finished, hit control-C to exit the editor.		*When finished, hit control-C to exit the editor.
	*Finally, type <code>nvstore</code> to save your changes.		*Finally, type <code>nvstore</code> to save your changes.

Tmcnulty: /* Netbooting */

2006-05-30T15:39:05Z

Netbooting

← Older revision		Revision as of 15:39, 30 May 2006
Line 25:		Line 25:

	===Netbooting===		===Netbooting===
			'''For information on netbooting Little-Fe/PPC, see the [[Little-Fe PPC]] page.'''

	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 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>

Charliep at 16:24, 23 May 2006

2006-05-23T16:24:37Z

← Older revision		Revision as of 16:24, 23 May 2006
Line 7:		Line 7:

	Also see http://www.ppczone.org/article.php?article=serialconsole		Also see http://www.ppczone.org/article.php?article=serialconsole

			Also see http://wiki.cs.earlham.edu/index.php/Little-Fe_PPC for instructions on setting-up Little-Fe/PPC boards.

	==SmartFirmware==		==SmartFirmware==
Line 26:		Line 28:
	<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
	~~setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1~~
	</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 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.

Charliep: /* Netbooting */

2006-05-23T12:10:26Z

Netbooting

← Older revision		Revision as of 12:10, 23 May 2006
Line 28:		Line 28:
	setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1		setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1
	</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.

			In order for the board to boot on power-up you must set a variable at the <code>ok</code> prompt:
			<pre>
			setenv auto-boot? true
			</pre>

			The red cables are hooked up to the 100baseT interfaces, and the yellow ones are hooked up to the 1000baseT interfaces

	===Booting from disk===		===Booting from disk===

Charliep: /* Netbooting */

2006-05-23T12:02:52Z

Netbooting

← Older revision		Revision as of 12:02, 23 May 2006
Line 26:		Line 26:
	<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
			setenv boot-file vmlinuz-2.6.15.6 init=/linuxrc root=/dev/nfs ip=dhcp console=ttyS1,115200n1
	</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

Tmcnulty at 19:00, 19 May 2006

2006-05-19T19:00:52Z

← Older revision		Revision as of 19:00, 19 May 2006
Line 27:		Line 27:
	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
	</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 firmware settings necessary to boot <code>lf[1-n]</code> 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>~~
	~~After this is setup, type <code>setenv auto-boot? true</code> at the main firmware prompt (not in <code>nvedit</code>).~~

	===Booting from disk===		===Booting from disk===