Kallisti - Revision history

Adj: /* Serial console port and Open Firmware */

2015-12-16T00:53:15Z

Serial console port and Open Firmware

← Older revision		Revision as of 00:53, 16 December 2015
Line 48:		Line 48:
	== Serial console port and Open Firmware ==		== Serial console port and Open Firmware ==
	Procedure for accessing Open Firmware on the serial port		Procedure for accessing Open Firmware on the serial port
	# Connect serial terminal. Use null modem cable if using another PC. Kermit works well if one finds oneself without a VT102 handy.		# Connect serial terminal. Use null modem cable if using another PC. Kermit works well if one finds oneself without a VT102 handy. (Though a VT102 won't be much help: its serial interface tops out at 19200bps.)
	# Set serial port for 57600 bits/second, no stop bits, 8 data bits, no parity bits, no flow control.		# Set serial port for 57600 bits/second, no stop bits, 8 data bits, no parity bits, no flow control.
	# Power off Xserve		# Power off Xserve
Line 58:		Line 58:

	And what do you do when you're there?		And what do you do when you're there?

	== Random important things ==		== Random important things ==
	* The serial console device seems to be known as '''<code>ttyPZ0</code>''' and runs at 57600 bits/second. Put '''<code>console=ttyPZ0,57600</code>''' on the kernel command line.		* The serial console device seems to be known as '''<code>ttyPZ0</code>''' and runs at 57600 bits/second. Put '''<code>console=ttyPZ0,57600</code>''' on the kernel command line.

Adj: /* Is it really a server? */

2015-12-15T23:11:15Z

Is it really a server?

← Older revision		Revision as of 23:11, 15 December 2015
Line 3:		Line 3:

	== Is it really a server? ==		== Is it really a server? ==
	This remains to be seen. There is nothing equivalent to IPMI over LAN on it. No network attached console or power controls. First attempts at Wake on LAN failed, too. But we'll see what happens as it's being built.		This remains to be seen. There is nothing equivalent to IPMI over LAN on it. No network attached console or power controls. First attempts at Wake on LAN failed, too. And forget about redundant power supplies. But we'll see what happens as it's being built.

	== Whatever for? ==		== Whatever for? ==

Adj: /* Operating System */

2015-12-07T21:35:43Z

Operating System

← Older revision		Revision as of 21:35, 7 December 2015
Line 41:		Line 41:
	Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.		Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.

	OS installation '''did''' happen. Unable to convince Open Firmware to retrieve the yaboot loader from the network, I removed a hard drive from the machine, created an empty Apple Partition Map (yay for [https://www.gnu.org/software/parted/ GNU parted]) and a 1Gibyte HFS ('''not''' HFS+) and the yaboot, yaboot.conf, kernel image, and initial RAM disk image (yay for [http://www.mars.org/home/rob/proj/hfs/ hfsutils]). Open Firmware can boot this just fine, and the Debian installer runs perfectly.		OS installation '''did''' happen. Unable to convince Open Firmware to retrieve the yaboot loader from the network, I removed a hard drive from the machine, created an empty Apple Partition Map (yay for [https://www.gnu.org/software/parted/ GNU parted]) and a 1Gibyte HFS ('''not''' HFS+) and the yaboot, yaboot.conf, kernel image, and initial RAM disk image (yay for [http://www.mars.org/home/rob/proj/hfs/ hfsutils]). Open Firmware can boot this just fine, and the Debian installer runs perfectly. See the "Preparing Files for Hard Disk Booting" section of the Debian installation manual for info on this.

	== Applications ==		== Applications ==

Adj: /* Operating System */

2015-12-07T18:51:30Z

Operating System

← Older revision		Revision as of 18:51, 7 December 2015
Line 41:		Line 41:
	Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.		Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.

	OS installation '''did''' happen. Unable to convince Open Firmware to retrieve the yaboot loader from the network, I removed a hard drive from the machine, created an empty Apple Partition Map (yay for [https://www.gnu.org/software/parted/ GNU parted]) and a 1Gibyte HFS ('''not''' HFS+) and the yaboot, yaboot.conf, kernel image, and initial RAM disk image. Open Firmware can boot this just fine, and the Debian installer runs perfectly.		OS installation '''did''' happen. Unable to convince Open Firmware to retrieve the yaboot loader from the network, I removed a hard drive from the machine, created an empty Apple Partition Map (yay for [https://www.gnu.org/software/parted/ GNU parted]) and a 1Gibyte HFS ('''not''' HFS+) and the yaboot, yaboot.conf, kernel image, and initial RAM disk image (yay for [http://www.mars.org/home/rob/proj/hfs/ hfsutils]). Open Firmware can boot this just fine, and the Debian installer runs perfectly.

	== Applications ==		== Applications ==

Adj: /* Operating System */

2015-12-07T18:49:22Z

Operating System

← Older revision		Revision as of 18:49, 7 December 2015
Line 40:		Line 40:

	Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.		Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.

			OS installation '''did''' happen. Unable to convince Open Firmware to retrieve the yaboot loader from the network, I removed a hard drive from the machine, created an empty Apple Partition Map (yay for [https://www.gnu.org/software/parted/ GNU parted]) and a 1Gibyte HFS ('''not''' HFS+) and the yaboot, yaboot.conf, kernel image, and initial RAM disk image. Open Firmware can boot this just fine, and the Debian installer runs perfectly.

	== Applications ==		== Applications ==

Adj: /* Hardware */

2015-12-06T16:41:22Z

Hardware

← Older revision		Revision as of 16:41, 6 December 2015
Line 9:		Line 9:

	== Hardware ==		== Hardware ==
			'''WARNING: ''' The plastic inside this computer is ''brittle''. I don't think I'm too brutish with my computers. But in poking around inside, I've manage to snap a retaining clip on the battery holder '''and''' on the PCI card riser. :(

	=== Chassis ===		=== Chassis ===

Adj: /* Operating System */

2015-12-04T16:20:24Z

Operating System

← Older revision		Revision as of 16:20, 4 December 2015
Line 37:		Line 37:
	== Operating System ==		== Operating System ==
	Debian 8.''current'' will be installed by over the network.		Debian 8.''current'' will be installed by over the network.

			Actually, the netbooting is not going terribly well. Open Firmware's TFTP client is requesting a file, but never asking for a second block. So the alternative will be getting the yaboot bootloader, its config file, a kernel and the Debian installer initrd image onto a disk partition that Open Firmware can read, then doing most of the install over the network.

	== Applications ==		== Applications ==

Adj: /* Network */

2015-12-04T16:16:05Z

Network

← Older revision		Revision as of 16:16, 4 December 2015
Line 30:		Line 30:
	2 gigabit Ethernet connections. I believe these are Broadcom based, so expect the usual firmware rigamarole to get these working.		2 gigabit Ethernet connections. I believe these are Broadcom based, so expect the usual firmware rigamarole to get these working.

	In addition to the onboard 1000baseT ports, there are 2 Intel based 1000baseT ports on an HP AD194A card in the ~~power~~ PCI-X slot.		In addition to the onboard 1000baseT ports, there are 2 Intel based 1000baseT ports on an HP AD194A card in the lower PCI-X slot.

	=== Manufacturer Support Info ===		=== Manufacturer Support Info ===

Adj: /* Resources */

2015-12-04T06:12:59Z

Resources

← Older revision		Revision as of 06:12, 4 December 2015
Line 53:		Line 53:

	And what do you do when you're there?		And what do you do when you're there?
			== Random important things ==
			* The serial console device seems to be known as '''<code>ttyPZ0</code>''' and runs at 57600 bits/second. Put '''<code>console=ttyPZ0,57600</code>''' on the kernel command line.

	== Resources ==		== Resources ==
	* Google. Google. Google.		* Google. Google. Google.

Adj: /* Network */

2015-06-26T17:35:11Z

Network

← Older revision		Revision as of 17:35, 26 June 2015
Line 29:		Line 29:
	=== Network ===		=== Network ===
	2 gigabit Ethernet connections. I believe these are Broadcom based, so expect the usual firmware rigamarole to get these working.		2 gigabit Ethernet connections. I believe these are Broadcom based, so expect the usual firmware rigamarole to get these working.

			In addition to the onboard 1000baseT ports, there are 2 Intel based 1000baseT ports on an HP AD194A card in the power PCI-X slot.

	=== Manufacturer Support Info ===		=== Manufacturer Support Info ===