version 1.5, 1998/06/19 15:06:31 |
version 1.6, 1999/12/19 15:58:19 |
|
|
<meta name="description" content="the OpenBSD/hp300 FAQ page"> |
<meta name="description" content="the OpenBSD/hp300 FAQ page"> |
<meta name="keywords" content="openbsd,hp300"> |
<meta name="keywords" content="openbsd,hp300"> |
<meta name="distribution" content="global"> |
<meta name="distribution" content="global"> |
<meta name="copyright" content="This document copyright 1998 by OpenBSD."> |
|
</head> |
</head> |
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E"> |
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E"> |
|
|
<h2>OpenBSD/hp300 FAQ</h2> |
Here are some frequently asked questions (and answers) specific |
|
to OpenBSD/hp300. |
|
|
|
<h2><a name="top">OpenBSD/hp300 Frequently Asked Questions</a></h2> |
|
<font face="helvetica, arial, sans-serif"><ul> |
|
<li><a href="#netboot">Can OpenBSD/hp300 boot across the network?</a></li> |
|
<li><a href="#hp300h">What <tt>TERM</tt> type is needed for the console?</a></li> |
|
<li><a href="#x11">What is the situation with X11 on the hp300?</a></li> |
|
<li><a href="#unexpected_use_of">What does 'UNEXPECTED USE OF FFFFFFC4' mean?</a></li> |
|
<li><a href="#hp_support">When will HP stop supporting the hp300/400?</a></li> |
|
</ul></font> |
|
<h2>Boot ROM Information</h2> |
|
<font face="helvetica, arial, sans-serif"><ul> |
|
<li><a href="#bootrom">What commands does the HP Boot ROM understand?</a></li> |
|
<li><a href="#bootsearch">What order does the Boot ROM use to search for bootable devices?</a></li> |
|
<li><a href="#domain">Switching your Series 400 machine from Domain to "HP-UX Compatible Boot Mode"</a></li> |
|
<li><a href="#bootrom2">Where could I get a more recent Boot ROM for my 400s or 400t?</a></li> |
|
</ul></font> |
|
<h2>Serial Port Information</h2> |
|
<font face="helvetica, arial, sans-serif"><ul> |
|
<li><a href="#serialdefs">What are the different types of serial ports, and how do I access them?</a></li> |
|
<li><a href="#serialconsole">Setting up a serial console on a 98561, 98562, 98626, 98628, 98642, or 98644</a></li> |
|
<li><a href="#serialconsole340">Setting up serial console on a Model 340</a></li> |
|
<li><a href="#serialconsole400">Setting up serial console on a Series 400 machine or a 345,375, 380, 382, or 385</a></li> |
|
<li><a href="#serialsplit">How do I build the cable to get at the hidden serial ports on a Series 400 machine?</a></li> |
|
</ul></font> |
|
|
|
|
|
<h2>Other sources of information</h2> |
|
<ul> |
|
<li><a href="http://fatmac.ee.cornell.edu/hp300/FAQ/rossspon/hp300faq.htm">HP9000/300 |
|
hardware FAQ</a> - maintained by Ross Sponholtz. |
|
<li><a href="http://fatmac.ee.cornell.edu/hp300/">The fatmac HP9000/300 |
|
guide</a> - made available by Michael Wolfson |
|
<li><a href="faq/">General OpenBSD FAQ</a> |
|
- questions not specific to OpenBSD/hp300. |
|
</ul> |
|
|
<hr> |
<hr> |
|
<h2>OpenBSD/hp300 Frequently Asked Questions</h2><hr> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="netboot">Can OpenBSD/hp300 boot across the network?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
HP 9000/300-series workstations support network booting with |
|
Boot ROM Revision B or later. (This includes any Boot ROM with a numeric |
|
revision). The HP Boot ROM uses the |
|
<b>HP Remote Maintainance Protocol</b> to download the boot code |
|
from the server. The server must run a daemon capable of responding |
|
to HP RMP boot requests, <i><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rbootd&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html">rbootd(8)</a></i>. |
<p> |
<p> |
|
To set up your OpenBSD/hp300 workstation, follow the |
|
<i><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=diskless&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">diskless(8)</a></i> man page. |
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="hp300h">What <tt>TERM</tt> type is needed for the console?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
If you're using a local console, and you're running csh or tcsh, you'll |
|
need to make sure you run: |
|
<pre>setenv TERM hp300h</pre> |
|
Otherwise many things won't work, including vi. |
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="x11">What is the situation with X11 on the hp300?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
We currently have all X11R6 clients, with an X11R5 server. |
|
The standard OpenBSD distribution includes an old BSD 4.4 Xserver which is |
|
buggy and slow. If you wish to instead use the HP-UX 9.10 X11R5 |
|
server, |
|
Michael Wolfson has <a href="http://fatmac.ee.cornell.edu/hp300/X11/">more |
|
details</a>. |
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="unexpected_use_of">What does 'UNEXPECTED USE OF FFFFFFC4' mean?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
This is the output of one of a set of temporary, informational only, |
|
exception handlers installed by the Boot ROM before an OS has been loaded. |
|
The address printed varies depending on the type of exception. |
|
The most likely cause here is trying to boot a kernel that is incompatible |
|
with the hardware. You will get something like this, for example, if you |
|
attempt to boot an HP-UX 7.0 or earlier kernel on a 68040 machine |
|
(which requires at least 7.05). If you're going to install OpenBSD, you |
|
probably don't need to worry about this message, though it is possible (but |
|
unlikely) that it indicates hardware trouble or a corrupt bootloader. |
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="hp_support">When will HP stop supporting the hp300/400?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
Motorola 68K-based |
|
HP-UX entered 'support-life' on October 1, 1997 and will continue until |
|
October 1, 2002, while 'support-life' began for |
|
HP/Apollo Domain |
|
on March 1, 1997, and will continue until January 1, 2001. There's a |
|
brief <a href="http://www.hp.com/ssg/vintage/index.html">page</a> on HP's |
|
website about this. HP still sells |
|
<a href="http://www.hp.com/visualize/programs/y2k/y2k_menu/y2k_upgr/300_400.html"> |
|
HP-UX 9.10</a> under the guise of a Y2K upgrade kit. |
|
<p> |
|
Anyone can <a href="http://us-support.external.hp.com/wpsl/bin/doc.pl/screen=coreAboutService"> |
|
browse or download patches</a> from HP's site without requiring a support |
|
contract. (Not that any of this matters to OpenBSD/hp300 users of course) |
|
|
|
</dd></dl></p> |
|
<hr> |
|
<h2>Boot ROM Information</h2><hr><p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="bootrom">What commands does the HP Boot ROM understand?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
All the early hp300 Boot ROMs are very primitive and only allow a few |
|
simple operations. You can only interact with it after it is first |
|
powered on -- if you reboot the machine, it will ignore anything you type |
|
and start loading the same OS you previously booted. |
|
<p> |
|
At any time after it recognizes the keyboard, while it is doing its self |
|
test or searching for a |
|
bootable system, you can hit <tt>reset</tt> to return it to a cold-boot |
|
configuration. On HIL keybaords, this is |
|
<tt><control>-<shift>-break</tt>, |
|
where <tt>break</tt> is the key in the upper left (where escape is on sane |
|
keyboards). There is no equivalent over serial terminal -- you'll need to |
|
power-cycle your machine. |
|
<p> |
|
After it beeps (i.e. recognizes the HIL keyboard), press |
|
<tt><return></tt> twice to get the list of bootable devices. |
|
To perform simple hardware checks, hit <tt><control>-C</tt> before |
|
it starts booting an OS. You can then type <tt>T</tt> to perform an |
|
extended self test or <tt>L</tt> to perform the extended self test |
|
infinitely until it finds a fatal error or <tt>L</tt> is typed again. |
|
<p> |
|
The newer HP Boot ROM, present on Series 400 machines and some of |
|
the later 300s (345, 375, 380, 382, 385) is capable of a little bit more. |
|
To select which device to boot from, press <tt><return></tt> once, |
|
after it |
|
beeps twice (i.e. recognizes the HIL keyboard). To get to a configuration |
|
and test menu, press: |
|
<pre> |
|
C <return> |
|
</pre> |
|
This will allow you to configure interrupt levels, select codes, and |
|
serial console properties. You can also hit <tt><control>-C</tt> to |
|
get to a menu of extended tests with several fancy options. |
|
<p> |
|
For more information, Michael Wolfson has scanned in parts of the |
|
<a href="http://fatmac.ee.cornell.edu/hp300/400.manual">HP Apollo 9000 |
|
Series 400 HP-UX Owner's Guide</a>, which has some good |
|
information on this topic. |
|
<p> |
|
|
|
<a name="bootorder"> </a> |
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="bootsearch">What order does the Boot ROM use to search for bootable devices?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
From the <i>Configuration Reference Manual</i>, 98561-90020: |
|
<p> |
|
<cite><h3>Revision A Boot ROM Specifications</h3> |
|
The boot ROM can load a ROM system or a file from a LIF or SRM |
|
"SYSTEM" type file having a name of the form SYSa, where "a" is typically |
|
an ASCII letter, but may be any character legal in a file name. |
|
<p> |
|
ROM systems are assigned a single letter ID (only "B", for BASIC, is |
|
presently supported on Series 300). |
|
<p> |
|
All system files found are assigned an ID of the form "nna", where "a" is |
|
either the same letter "a" mentioned above (if an ASCII letter), or "Z" |
|
(if not an ASCII letter). "nn" is a number of the form " 1" to "99" |
|
denoting the order of occurence of systems which result in the same ID |
|
letter "a". The range of system IDs is " 1A" to "99Z". |
|
<p> |
|
The boot ROM loads the first system found unless characters (other than |
|
that system's ID) are typed on the boot control keyboard (see below). The |
|
search order used by the boot ROM is: |
|
<p> |
|
<ul><li>For select codes 7 thru 31: disc or tape (HPIB) at bus address 0, |
|
unit 0, volume 0 |
|
<li>SRM at select code 21, node 0, volume 8, "/SYSTEMS" directory |
|
<li>98259A Bubble system at select code 30 |
|
<li>98255 EPROM "disc"-type system at unit 0 (lowest address of all 98255s installed) |
|
<li>ROM systems (from lowest to highest ROM address) |
|
<li>For select codes 0 thru 31, bus addresses 0 to 7, units 0 to 16, |
|
volumes 0 to 7: all remaining discs or tapes (HPIB) |
|
<li>For select codes 0 thru 31, nodes 1 thru 62, volumes 1 to 50: any |
|
other SRM system files in "/SYSTEMS" directories |
|
<li>For select codes 0 thru 29, and 31: remaining 98255 Bubble systems |
|
<li>Remaining 98255 "disc"-type EPROM units. |
|
</ul></cite> |
|
<p> |
|
|
|
Revision B and later also support booting over the network, using a 98643 |
|
card or built-in ethernet. |
|
For older systems, the best choice is to make your boot drive on HPIB at |
|
address 0. Remember, you'll need to capitalize the letters. |
|
<p> |
|
<h3>Newer Boot ROM Search Order</h3> |
|
The newer machines (Models 345, 375, 380, 382, 385, and Series 400) have a |
|
different boot order. From <i>HP Apollo 9000 Series 400 HP-UX Owner's |
|
Guide</i>, A1630-90006: |
|
<p> |
|
<cite>The Scan for Systems selection searches mass storage devices for an |
|
operating system to boot. The first mass storage device found with an |
|
HP-UX Compatible operating system on it boots. Mass storage devices are |
|
searched by the priority shown in this table.</cite> |
|
<p> |
|
<table border="1" cellspacing="1" cellpadding="5"> |
|
<tr><td>Priority Level</td> |
|
<td>Device</td> |
|
<td>Select Code</td> |
|
<td>Bus Address</td> |
|
<td>Unit Number</td></tr> |
|
|
|
<tr><td>1</td> |
|
<td>SCSI</td> |
|
<td>0-31</td> |
|
<td>7-5</td> |
|
<td>0</td></tr> |
|
|
|
<tr><td>2</td> |
|
<td>HP-IB</td> |
|
<td>0-31</td> |
|
<td>7-5</td> |
|
<td>0</td></tr> |
|
|
|
<tr><td>3</td> |
|
<td>SRM</td> |
|
<td>14</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>4</td> |
|
<td>LAN</td> |
|
<td>21</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>5</td> |
|
<td>Bubble RAM</td> |
|
<td>30</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>6</td> |
|
<td>EEPROM</td> |
|
<td>N/A</td> |
|
<td>N/A</td> |
|
<td>0</td></tr> |
|
|
|
<tr><td>7</td> |
|
<td>SCSI</td> |
|
<td>0-31</td> |
|
<td>4-0</td> |
|
<td>0</td></tr> |
|
|
|
<tr><td>8</td> |
|
<td>HP-IB</td> |
|
<td>0-31</td> |
|
<td>4-0</td> |
|
<td>0</td></tr> |
|
|
|
<tr><td>9</td> |
|
<td>SRM</td> |
|
<td>Other than 14</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>10</td> |
|
<td>LAN</td> |
|
<td>Other than 21</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>11</td> |
|
<td>Bubble RAM</td> |
|
<td>Other than 30</td> |
|
<td>N/A</td> |
|
<td>N/A</td></tr> |
|
|
|
<tr><td>12</td> |
|
<td>EEPROM</td> |
|
<td>Other than 0</td> |
|
<td>N/A</td> |
|
<td>0</td></tr> |
|
</table> |
|
<p> |
|
So, for these newer systems, your best bet is to make your boot drive a |
|
SCSI drive at address 6 (7 is the system controller on the motherboard). |
|
<p> |
|
It is also possible to configure the Boot ROM to default to a specific |
|
device from the configuration menu. |
|
<p> |
|
<a name="domaintohpux"> </a> |
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="domain">Switching your Series 400 machine from Domain to "HP-UX Compatible Boot Mode"</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
This step is necessary, since OpenBSD can only |
|
boot a Series 400 machine when it's set up in "HP-UX Compatible Boot |
|
Mode". If, when you power on your machine, it does <b>not</b> present a |
|
menu as follows, then you need to follow the instructions below: |
|
<pre> |
|
Copyright 1990, |
|
Hewlett-Packard Company. |
|
All Rights Reserved. |
|
|
|
BOOTROM Series 400 Rev. 1.1 |
|
MD12 REV 1.2 1990/08/07.14:27:08 |
|
MC68030 Processor |
|
MC68882 Coprocessor |
|
Configuration EEPROM |
|
Utility Chip at 41 |
|
HP-HIL.Keyboard |
|
[...]</pre> |
|
|
|
First, you'll need either a Domain keyboard or a HIL keyboard (the Boot |
|
ROM knows how to use either, even if OpenBSD doesn't yet). |
|
Now, put your machine into "service mode". For a 4XXs, there's a toggle |
|
switch on the back of the machine (near the top). For a 4XXt or 4XXdl, |
|
there's a green button on the front, behind the silly door. For a 425e, |
|
there's a toggle switch on the back of the machine (in the middle). |
|
Once you're in "service mode", the other |
|
green LED will light up. Reset the machine. You may then need to hit |
|
return to get the Domain boot prompt. At that prompt, you can type |
|
<tt><b>H</b></tt> to get a list of available commands. You need to type |
|
the following things to convert to HP-UX mode: |
|
|
|
<pre><b>CF |
|
2 |
|
2 |
|
P |
|
E</b></pre> |
|
<a href="domain.commands.html">This</a> is the full procedure captured |
|
from a serial console. |
|
<p> |
|
Be sure to turn <b>off</b> "service mode" when you're done. I found it |
|
prevented me from selecting which device I wanted to boot from. |
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="bootrom2">Where could I get a more recent Boot ROM for my 400s or 400t?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
Michael Wolfson has images of the HP 425/433 Boot ROM in HP-UX mode. |
|
This is necessary when upgrading a 400 to a 425/433 |
|
<p> |
|
See <a href="http://fatmac.ee.cornell.edu/hp300/upgrade">The fatmac |
|
HP9000/300 guide</a> for instructions on upgrading. |
|
|
|
</dd></dl></p> |
|
<hr> |
|
<h2>Serial Port Information</h2><hr><a name="serialinfo"> </a> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="serialdefs">What are the different types of serial ports, and how do I access them?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
<table border="1" cellspacing="1" cellpadding="5"> |
|
<tr><td><i>device name</i></td> |
|
<td><i>location</i></td> |
|
<td><i>device file</i></td> |
|
<td><i>max speed</i></td> |
|
<td><i>hardware handshaking</i></td> |
|
<td><i>FIFO</i></td> |
|
<td><i>serial console</i></td> |
|
<td><i>comments</i></td></tr> |
|
|
|
<tr><td> |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dca&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html"> |
|
dca0</a></td> |
|
<td>built-in</td> |
|
<td>/dev/tty0</td> |
|
<td>19200</td> |
|
<td>no</td> |
|
<td>no</td> |
|
<td>DIP switches<br>non-null cable</td> |
|
<td>for 318, 319, 320, 330, 340, 350, 360, 362, 370<br>located |
|
on Human/System Interface board</td></tr> |
|
|
|
<tr><td> |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dca&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html"> |
|
dca0</a></td> |
|
<td>built-in</td> |
|
<td>/dev/tty0</td> |
|
<td>38400</td> |
|
<td>yes</td> |
|
<td>yes</td> |
|
<td>config Boot ROM</td> |
|
<td>for 345, 375, 380, 382, 385, 400 Series (except 425e)<br>located on |
|
motherboard</td></tr> |
|
|
|
<tr><td> |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dca&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html"> |
|
dcaN</a></td> |
|
<td>98644A DIO-I card</td> |
|
<td>/dev/ttyN</td> |
|
<td>19200</td> |
|
<td>yes</td> |
|
<td>no</td> |
|
<td>DIP switches</td> |
|
<td>hardware handshaking only for transmit</td></tr> |
|
|
|
<tr><td>dcaN</td> |
|
<td>98626A DIO-I card</td> |
|
<td>/dev/ttyN</td> |
|
<td>19200</td> |
|
<td>yes</td> |
|
<td>no</td> |
|
<td>DIP switches</td> |
|
<td>hardware handshaking only for transmit</td></tr> |
|
|
|
<tr><td> |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dcl&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html"> |
|
dclN</a></td> |
|
<td>98628A DIO-I card</td> |
|
<td>/dev/ttyN</td> |
|
<td>19200</td> |
|
<td>yes</td> |
|
<td>yes<br>256 bytes</td> |
|
<td>jumper</td> |
|
<td>weird centronics connector goes to normal db25</td></tr> |
|
|
|
<tr><td>apci0<br>apci1</td> |
|
<td>built-in</td> |
|
<td>/dev/ttya0<br>/dev/ttya1</td> |
|
<td>19200</td> |
|
<td>no</td> |
|
<td>no</td> |
|
<td>no</td> |
|
<td>for 400 Series machines (except 425e), requires <a |
|
href="serial.splitter.html">break-out cable</a></td></tr> |
|
|
|
<tr><td>apci0<br>apci1<br>apci2</td> |
|
<td>built-in</td> |
|
<td>/dev/ttya0<br>/dev/ttya1<br>/dev/ttya2</td> |
|
<td>19200</td> |
|
<td>no</td> |
|
<td>no</td> |
|
<td>config Boot ROM</td> |
|
<td>for 425e, apci0 supports serial console, apci1 and apci2 require |
|
<a href="serial.splitter.html">break-out cable</a></td></tr> |
|
|
|
<tr><td> |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dcm&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html"> |
|
dcmN</a></td> <td>98642A DIO-I card</td> |
|
<td>/dev/tty0[0-3]</td> |
|
<td>19200</td> |
|
<td>yes</td> |
|
<td>yes<br>128/16 bytes</td> |
|
<td>DIP switches</td> |
|
<td>Only port 0 has flow control<br>Only port 1 does console<br> |
|
Uses <a href="dcmpinouts.html">RJ-11</a> jacks</td></tr> |
|
|
|
<tr><td>dcmN<br>dcmN+1</td> |
|
<td>98638 DIO-II card</td> |
|
<td>/dev/tty0[0-3]<br>/dev/tty[4-7]</td> |
|
<td>19200</td> |
|
<td>yes</td> |
|
<td>yes<br>127/16 bytes</td> |
|
<td>no</td> |
|
<td>Appears to kernel as two 98642 boards</td></tr> |
|
</table> |
|
|
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="serialconsole">Setting up a serial console on a 98561, 98562, 98626, 98628, 98642, or 98644</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
Turn off power to your system before removing any cards. Remove the |
|
card with the serial interface. |
|
<p> |
<ul> |
<ul> |
<li>How do I change the hp400 boot ROM mode from Domain/OS to HP-UX? |
<p><li><b><tt>98561-66530</tt></b> (Human Interface)<br> |
<br>Remove the Domain keyboard, replacing it with a HIL model. |
Locate the bank of 4 DIP switches<br> |
Press the <i>service</i> switch on the front panel; the LED will light, |
One of them should be labeled REM<br> |
then press the <i>reset</i> switch on the back of the machine. |
Set the switch to ?<br> |
The system should then boot into <b>MD</b> mode, and display a <b>></b> |
<p><li><b><tt>98562</tt></b> (System Interface)<br> |
prompt. If the prompt does not display, try pressing <i>return</i> a few |
Locate the middle bank of DIP switches (4 switches)<br> |
times; when the prompt appears, type <b>hp</b> and press <i>return</i>. |
The third switch is labeled REM<br> |
Your system should then reset and display the HP-UX style ROM messages. |
Set the switch to one (depress the end labeled one)<br> |
<li>How do I change the hp400 boot ROM mode from HP-UX to Domain/OS? |
<i>Note: you need a non-null cable</i> |
<br>You may want to seek professional psychological help. |
<p><li><b><tt>98626</tt></b> (dca)<br> |
<li>How do I set the serial port to be the console on a 300-series machine? |
Locate the jumper by the two banks of DIP switches<br> |
<br>For anything before the hp380, you need to set the <b>remote</b> bit |
Remove the jumper<br> |
on the motherboard or serial card; settings are different for every model |
<p><li><b><tt>98628</tt></b> (dcl)<br> |
and beyond the scope of this document. For the hp380 and above (including |
Locate the bank of DIP switches by the card-edge connector<br> |
the 400 series), simply press the <i>space bar</i> during the ROM configuration |
The last switch (labeled 7) is the remote switch<br> |
so that the boot menu appears; at the prompt type <b>C</b> and press |
Set the switch to zero (depress the end labeled zero) |
<i>return</i>. The configuration menu will appear, from where you can |
<p><li><b><tt>98642</tt></b> (dcm)<br> |
put the serial port into <b>remote</b> mode. |
Locate the 8 DIP switches<br> |
|
The first switch (labeled 1) is the remote switch<br> |
|
Set the switch to one (slide the bump to one)<br> |
|
<i>Note: According to the manual, the Boot ROM on older machines |
|
does not know how to use this for console, but OpenBSD (and HP-UX) |
|
will, so you won't see anything until the bootloader loads.</i> |
|
<p><li><b><tt>98644</tt></b> (dca)<br> |
|
Locate the 10 DIP switches<br> |
|
The last switch (labeled 1) is the remote switch<br> |
|
Set the switch to one (depress the end labeled one)<br> |
</ul> |
</ul> |
</p> |
<p> |
|
Now, reinsert the card and power on your machine. All console messages |
|
will be sent over the serial port at |
|
9600 bps, 8 bits, no parity, 1 stop bit. Theoretically, you should be |
|
using a null-modem cable, but I found that for my 98562, I needed a |
|
non-null modem cable. |
|
|
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="serialconsole340">Setting up serial console on a Model 340</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
Turn off power to your system<br> |
|
There are four DIP switches visible through the rear panel<br> |
|
Flip the third switch from the left to one<br> |
|
Turn on your system |
<p> |
<p> |
This document is under development and will continue to be revised. |
Now, all console messages will be sent over the serial port at 9600 bps, |
</p> |
8 bits, no parity, 1 stop bit. |
|
|
|
<a name="serial400"> </a> |
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="serialconsole400">Setting up serial console on a Series 400 machine or a 345,375, 380, 382, or 385</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
Wait until your system beeps twice (this is to let |
|
you know it's |
|
recognized the keyboard). Type <tt><b>C<return></b></tt> and wait |
|
until the configuration menu shows up. Then type in the following set of |
|
commands: |
|
<pre><b>1 |
|
5 |
|
3 |
|
R |
|
X |
|
N</b></pre> |
|
<p> |
|
<a href="serialconsole.html">This</a> is the full procedure captured from |
|
a serial console on my 400s. It may be slightly different for the 300 |
|
series machines (345, 375, 380, 382, 385). |
|
<p> |
|
Now, your machine will reset and then send all console messages over the |
|
serial port at |
|
9600 bps, 8 bits, no parity, 1 stop bit. Use a null-modem cable. |
|
<p> |
|
If you want to convert from serial console to monitor/keyboard console, |
|
follow the same procedure, except type <tt><b>L</b></tt> instead of |
|
<tt><b>R</b></tt>. |
|
<p> |
|
You may also <i>temporarily</i> override this setting by typing |
|
<tt><b>L<return></b></tt> or <tt><b>R<return></b></tt> after |
|
your system beeps twice and recognizes the keyboard. This will work even |
|
if you have a Domain keyboard. |
|
|
|
<p> |
|
Since the hardware takes care of this console, you do <b>not</b> add an |
|
entry for the console in <tt>/etc/ttys</tt>. That would be bad. |
|
|
|
</dd></dl></p> |
|
<p><dl><dt> |
|
<font face="helvetica, arial, sans-serif"><h3><a name="serialsplit">How do I build the cable to get at the hidden serial ports on a Series 400 machine?</a> |
|
<font size="-1">(<a href="#top">top</a>)</font></h3></font> |
|
</dt><dd> |
|
|
|
Build the funky <a href="serial.splitter.html">cable</a>. Otherwise, just |
|
using a normal DB25 serial cable will work fine if you only want one |
|
serial port. |
|
|
|
|
|
|
|
</dd></dl></p> |
|
|
|
<hr> |
|
|
|
<p> |
<a href=hp300.html><img height=24 width=24 src=back.gif border=0 alt="OpenBSD/hp300"></a> |
<a href=hp300.html><img height=24 width=24 src=back.gif border=0 alt="OpenBSD/hp300"></a> |
<a href=mailto:www@openbsd.org>www@openbsd.org</a> |
<a href=mailto:www@openbsd.org>www@openbsd.org</a> |
<br> |
<br> |
<small>$OpenBSD$</small> |
<small>$OpenBSD$</small> |
|
</p> |
|
|
</body> |
</body> |
</html> |
</html> |