Bitemelarry - Revision history

Adj: /* Debian on this machine */

2014-02-28T17:35:25Z

Debian on this machine

← Older revision		Revision as of 17:35, 28 February 2014
Line 62:		Line 62:
	== Debian on this machine ==		== Debian on this machine ==
	Debian wheezy is also installed on this machine. Non-free firmware is needed to get the on-board and PCI expansion card Ethernet adapters working. The 4 port onboard Ethernet is a Broadcom Tigon 3. Firmware for this adapter can be found in the firmware-linux-nonfree package. The add-on PCI-X card is a 4 port Sun Quad Gigaswift adapter. It uses the "cassini" driver and needs the "cassini.bin" firmware blob. This firmware blob is distributed as an Intel HEX (ihex) file in the Linux kernel source tree. The binary file can be generated by		Debian wheezy is also installed on this machine. Non-free firmware is needed to get the on-board and PCI expansion card Ethernet adapters working. The 4 port onboard Ethernet is a Broadcom Tigon 3. Firmware for this adapter can be found in the firmware-linux-nonfree package. The add-on PCI-X card is a 4 port Sun Quad Gigaswift adapter. It uses the "cassini" driver and needs the "cassini.bin" firmware blob. This firmware blob is distributed as an Intel HEX (ihex) file in the Linux kernel source tree. The binary file can be generated by
	cd DIRECTORY_CONTAINING_cassini.bin.ihex; objcopy -Iihex -Obinary cassini.bin.ihex cassini.bin~~</code>~~		cd DIRECTORY_CONTAINING_cassini.bin.ihex; objcopy -Iihex -Obinary cassini.bin.ihex cassini.bin

	Booting Debian on this machine is done by running <code>'''boot disk1'''</code> at OpenBootPROM's <code>'''ok '''</code> prompt. (If the silo boot loader is unable to start the kernel with a message about an instruction fault, try again after powering the system off completely. See [https://launchpad.net/ubuntu/+source/silo/+bug/40119 https://launchpad.net/ubuntu/+source/silo/+bug/40119] for some info on this.)		Booting Debian on this machine is done by running <code>'''boot disk1'''</code> at OpenBootPROM's <code>'''ok '''</code> prompt. (If the silo boot loader is unable to start the kernel with a message about an instruction fault, try again after powering the system off completely. See [https://launchpad.net/ubuntu/+source/silo/+bug/40119 https://launchpad.net/ubuntu/+source/silo/+bug/40119] for some info on this.)

Adj: /* Debian on this machine */

2014-02-25T22:21:29Z

Debian on this machine

← Older revision		Revision as of 22:21, 25 February 2014
Line 63:		Line 63:
	Debian wheezy is also installed on this machine. Non-free firmware is needed to get the on-board and PCI expansion card Ethernet adapters working. The 4 port onboard Ethernet is a Broadcom Tigon 3. Firmware for this adapter can be found in the firmware-linux-nonfree package. The add-on PCI-X card is a 4 port Sun Quad Gigaswift adapter. It uses the "cassini" driver and needs the "cassini.bin" firmware blob. This firmware blob is distributed as an Intel HEX (ihex) file in the Linux kernel source tree. The binary file can be generated by		Debian wheezy is also installed on this machine. Non-free firmware is needed to get the on-board and PCI expansion card Ethernet adapters working. The 4 port onboard Ethernet is a Broadcom Tigon 3. Firmware for this adapter can be found in the firmware-linux-nonfree package. The add-on PCI-X card is a 4 port Sun Quad Gigaswift adapter. It uses the "cassini" driver and needs the "cassini.bin" firmware blob. This firmware blob is distributed as an Intel HEX (ihex) file in the Linux kernel source tree. The binary file can be generated by
	cd DIRECTORY_CONTAINING_cassini.bin.ihex; objcopy -Iihex -Obinary cassini.bin.ihex cassini.bin</code>		cd DIRECTORY_CONTAINING_cassini.bin.ihex; objcopy -Iihex -Obinary cassini.bin.ihex cassini.bin</code>

			Booting Debian on this machine is done by running <code>'''boot disk1'''</code> at OpenBootPROM's <code>'''ok '''</code> prompt. (If the silo boot loader is unable to start the kernel with a message about an instruction fault, try again after powering the system off completely. See [https://launchpad.net/ubuntu/+source/silo/+bug/40119 https://launchpad.net/ubuntu/+source/silo/+bug/40119] for some info on this.)

Adj: /* Battery */

2014-02-25T22:17:57Z

Battery

← Older revision		Revision as of 22:17, 25 February 2014
Line 59:		Line 59:

	Battery replacement was pretty painless. Sun had built this machine using a '''B'''R2032 cell, but none were available at the local Walgreen's or Batteries+ stores. A '''C'''R2032 has been serving just fine for 3 weeks now. (Some web references say the BR2032 will last a much longer time in this application, but a couple of years will be plenty for this machine.)		Battery replacement was pretty painless. Sun had built this machine using a '''B'''R2032 cell, but none were available at the local Walgreen's or Batteries+ stores. A '''C'''R2032 has been serving just fine for 3 weeks now. (Some web references say the BR2032 will last a much longer time in this application, but a couple of years will be plenty for this machine.)

			== Debian on this machine ==
			Debian wheezy is also installed on this machine. Non-free firmware is needed to get the on-board and PCI expansion card Ethernet adapters working. The 4 port onboard Ethernet is a Broadcom Tigon 3. Firmware for this adapter can be found in the firmware-linux-nonfree package. The add-on PCI-X card is a 4 port Sun Quad Gigaswift adapter. It uses the "cassini" driver and needs the "cassini.bin" firmware blob. This firmware blob is distributed as an Intel HEX (ihex) file in the Linux kernel source tree. The binary file can be generated by
			cd DIRECTORY_CONTAINING_cassini.bin.ihex; objcopy -Iihex -Obinary cassini.bin.ihex cassini.bin</code>

Adj: /* Battery */

2014-02-25T18:41:33Z

Battery

← Older revision		Revision as of 18:41, 25 February 2014
Line 57:		Line 57:
	== Battery ==		== Battery ==
	At power on, this machine is now reporting <code>SC Alert: VOLTAGE_SENSOR @ MB.BAT.V_BAT has exceeded low warning threshold.</code> It seems that the motherboard battery is a generic 3 volt Lithium 2032 cell. It is located in a socket somewhere on the motherboard. Replacement with a new part should be quite simple.		At power on, this machine is now reporting <code>SC Alert: VOLTAGE_SENSOR @ MB.BAT.V_BAT has exceeded low warning threshold.</code> It seems that the motherboard battery is a generic 3 volt Lithium 2032 cell. It is located in a socket somewhere on the motherboard. Replacement with a new part should be quite simple.

			Battery replacement was pretty painless. Sun had built this machine using a '''B'''R2032 cell, but none were available at the local Walgreen's or Batteries+ stores. A '''C'''R2032 has been serving just fine for 3 weeks now. (Some web references say the BR2032 will last a much longer time in this application, but a couple of years will be plenty for this machine.)

Adj: /* Operating System */

2014-01-21T16:29:04Z

Operating System

← Older revision		Revision as of 16:29, 21 January 2014
Line 54:		Line 54:
	=== Operating System ===		=== Operating System ===
	The Solaris 10 update 11 SPARC installation failed to include the proper drivers for the SCSI card in the machine. Watch for something like "glm: cannot load driver" followed by a "panic[cpu0]/thread=180e000: vfs_mountroot: cannot mount root". [http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html] got me through getting the correct drivers installed. Net-booting the install kernel, importing zpool for direct attached drives, getting ZFS root mounted, chrooting into it, getting /proc and /dev/fd and /etc/mntent mounted inside chroot were all needed before pkgadd would run correctly.		The Solaris 10 update 11 SPARC installation failed to include the proper drivers for the SCSI card in the machine. Watch for something like "glm: cannot load driver" followed by a "panic[cpu0]/thread=180e000: vfs_mountroot: cannot mount root". [http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html] got me through getting the correct drivers installed. Net-booting the install kernel, importing zpool for direct attached drives, getting ZFS root mounted, chrooting into it, getting /proc and /dev/fd and /etc/mntent mounted inside chroot were all needed before pkgadd would run correctly.

			== Battery ==
			At power on, this machine is now reporting <code>SC Alert: VOLTAGE_SENSOR @ MB.BAT.V_BAT has exceeded low warning threshold.</code> It seems that the motherboard battery is a generic 3 volt Lithium 2032 cell. It is located in a socket somewhere on the motherboard. Replacement with a new part should be quite simple.

Adj: /* Lights Out Management */

2014-01-17T17:20:49Z

Lights Out Management

← Older revision		Revision as of 17:20, 17 January 2014
Line 12:		Line 12:

	Setting the ALOM for DHCP is a matter of getting a user with "cuar" permissions, connecting to the ALOM on the serial console or over the network, and running '''<code>setupsc</code>''' from the ALOM's shell. It will ask a lot of questions. Most can safely be ignored for now. The DHCP enable option is pretty obvious, though. Re-setting the configuration of the ALOM is accomplished by running '''<code>setdefaults</code>''' from the ALOM shell.		Setting the ALOM for DHCP is a matter of getting a user with "cuar" permissions, connecting to the ALOM on the serial console or over the network, and running '''<code>setupsc</code>''' from the ALOM's shell. It will ask a lot of questions. Most can safely be ignored for now. The DHCP enable option is pretty obvious, though. Re-setting the configuration of the ALOM is accomplished by running '''<code>setdefaults</code>''' from the ALOM shell.

			Factory default credentials for ALOMs of this generation are '''<code>admin</code>''' / '''<code>admin</code>'''.

	=== CPU ===		=== CPU ===

Adj: /* Lights Out Management */

2013-04-14T16:56:26Z

Lights Out Management

← Older revision		Revision as of 16:56, 14 April 2013
Line 11:		Line 11:
	If you feel the urge to update the ALOM firmware, be sure the system firmware requirements are met. I had OpenBoot version 4.8.something and ALOM verison 1.0. Updating to ALOM 1.6 required a more recent OpenBoot. The more recent OpenBoot's requirement for ALOM >= 1.2.x wasn't mentioned until the very end of the OpenBoot update document. The machine seems to have survived, but the unmatched dependencies were a cause of concern for a while.		If you feel the urge to update the ALOM firmware, be sure the system firmware requirements are met. I had OpenBoot version 4.8.something and ALOM verison 1.0. Updating to ALOM 1.6 required a more recent OpenBoot. The more recent OpenBoot's requirement for ALOM >= 1.2.x wasn't mentioned until the very end of the OpenBoot update document. The machine seems to have survived, but the unmatched dependencies were a cause of concern for a while.

	Setting the ALOM for DHCP is a matter of getting a user with "cuar" permissions, connecting to the ALOM on the serial console or over the network, and running ~~the~~ '''<code>setupsc</code>'''' from the ALOM's shell. It will ask a lot of questions. Most can safely be ignored for now. The DHCP enable option is pretty obvious, though. Re-setting the configuration of the ALOM is accomplished by running '''<code>setdefaults</code>''' from the ALOM shell.		Setting the ALOM for DHCP is a matter of getting a user with "cuar" permissions, connecting to the ALOM on the serial console or over the network, and running '''<code>setupsc</code>''' from the ALOM's shell. It will ask a lot of questions. Most can safely be ignored for now. The DHCP enable option is pretty obvious, though. Re-setting the configuration of the ALOM is accomplished by running '''<code>setdefaults</code>''' from the ALOM shell.

	=== CPU ===		=== CPU ===

Adj: /* Operating System */

2013-04-12T15:50:46Z

Operating System

← Older revision		Revision as of 15:50, 12 April 2013
Line 51:		Line 51:

	=== Operating System ===		=== Operating System ===
			The Solaris 10 update 11 SPARC installation failed to include the proper drivers for the SCSI card in the machine. Watch for something like "glm: cannot load driver" followed by a "panic[cpu0]/thread=180e000: vfs_mountroot: cannot mount root". [http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html http://ssl-lab.blogspot.com/2010/12/set-controls-for-heart-of-sun.html] got me through getting the correct drivers installed. Net-booting the install kernel, importing zpool for direct attached drives, getting ZFS root mounted, chrooting into it, getting /proc and /dev/fd and /etc/mntent mounted inside chroot were all needed before pkgadd would run correctly.

Adj: /* mass storage */

2013-04-12T15:43:38Z

mass storage

← Older revision		Revision as of 15:43, 12 April 2013
Line 18:		Line 18:

	=== mass storage ===		=== mass storage ===
			There are two 3.5 inch bays for SCA SCSI drives in the front of the chassis.

	== Software ==		== Software ==
	=== network boot ===		=== network boot ===

Adj: /* Lights Out Management */

2013-04-12T15:41:37Z

Lights Out Management

← Older revision		Revision as of 15:41, 12 April 2013
Line 6:		Line 6:

	ALOM login credentials have not yet been re-set. This should be possible after Solaris is installed using '''<code>setdefaults -a</code>''' or something similar.		ALOM login credentials have not yet been re-set. This should be possible after Solaris is installed using '''<code>setdefaults -a</code>''' or something similar.

			ALOM login credentials can be re-set (or a new user ALOM user can be added) with software included with Solaris. '''<code>/usr/platform/$(uname -i)/scadm</code>''' will be your friend, here. It has a helpful "'''<code>help</code>'''" option.

			If you feel the urge to update the ALOM firmware, be sure the system firmware requirements are met. I had OpenBoot version 4.8.something and ALOM verison 1.0. Updating to ALOM 1.6 required a more recent OpenBoot. The more recent OpenBoot's requirement for ALOM >= 1.2.x wasn't mentioned until the very end of the OpenBoot update document. The machine seems to have survived, but the unmatched dependencies were a cause of concern for a while.

			Setting the ALOM for DHCP is a matter of getting a user with "cuar" permissions, connecting to the ALOM on the serial console or over the network, and running the '''<code>setupsc</code>'''' from the ALOM's shell. It will ask a lot of questions. Most can safely be ignored for now. The DHCP enable option is pretty obvious, though. Re-setting the configuration of the ALOM is accomplished by running '''<code>setdefaults</code>''' from the ALOM shell.

	=== CPU ===		=== CPU ===