File:  [NetBSD Developer Wiki] / wikisrc / ports / hp300faq.mdwn
Revision 1.3: download - view: text, annotated - select for diffs
Mon Jan 13 08:02:37 2014 UTC (7 years, 8 months ago) by ryoon
Branches: MAIN
CVS tags: HEAD
Fix horribly broken anchors. Use ikiwiki way

    1: [[!meta title="NetBSD/hp300 Frequently Asked Questions"]]
    2: 
    3: [[!toc startlevel=1 levels=2]]
    4: 
    5: * * * * *
    6: 
    7: # General Questions
    8: 
    9: ## My screen went black after some initial bootrom messages
   10: 
   11: This means your framebuffer is not supported. Hook up a serial terminal,
   12: 9600 bps, 8 bits, no parity, 1 stop bit, xon/xoff flow control.
   13: 
   14: Contact `<port-hp300@NetBSD.org>`{.email} if you'd like to work on
   15: writing a driver for your framebuffer.
   16: 
   17: ## Can NetBSD/hp300 boot across the network?
   18: 
   19: HP 9000/300-series workstations support network booting with Boot ROM
   20: Revision B or later. (This includes any Boot ROM with a numeric
   21: revision). The HP Boot ROM uses the **HP Remote Maintainance Protocol**
   22: to download the boot code from the server. The server must run a daemon
   23: capable of responding to HP RMP boot requests. If your server runs
   24: NetBSD, it has
   25: *[rbootd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?rbootd+8+NetBSD-6.0+i386)*
   26: in the base system. If your server runs another OS, like Linux or
   27: Solaris, you can try [YAMAMORI Takenori's *sun-rbootd*
   28: package](http://www15.big.or.jp/~yamamori/sun/netbsd-hp_e.html).
   29: 
   30: To set up your NetBSD/hp300 workstation, follow the
   31: *[diskless(8)](http://netbsd.gw.com/cgi-bin/man-cgi?diskless+8+NetBSD-6.0+i386)*
   32: man page. For more detailed instructions, see the [Diskless
   33: HOW-TO](../../docs/network/netboot/) and its [Setting up the rbootd
   34: server section](../../docs/network/netboot/rbootd/).
   35: 
   36: ## How can I change Ethernet media types on 4xx models?
   37: 
   38: Series 400 machines have two Ethernet media types built into the
   39: motherboard. You may only use one at a time. When your Series 400
   40: workstation goes through the self-test when powered on or rebooted, it
   41: will say one of the following:
   42: 
   43: ~~~~ {.programlisting}
   44: HP98643 (LAN) at 21, AUI
   45: HP98643 (LAN) at 21, Thin
   46: ~~~~
   47: 
   48: If the wrong type of network is selected, you will need to change the
   49: Ethernet port. You will need to open the case (4XXt, 4XXdl, 4XXe) or
   50: remove the motherboard (4XXs) to access the jumper. Be sure to use
   51: static-prevention measures, as you could easily fry your motherboard
   52: from carelessness. If you are uncomfortable with this, ask a friend who
   53: is aware of these issues. There is a block of 8 jumpers at the rear of
   54: the motherboard, labeled AUI/Thin. You will need to put the jumpers in
   55: the position necessary for your type of Ethernet.
   56: 
   57: ## What `TERM`{.code} type is needed for the console?
   58: 
   59: If you're using a local console on NetBSD 5.x or prior, and you're
   60: running csh or tcsh, you'll need to make sure you run:
   61: 
   62: ~~~~ {.programlisting}
   63: setenv TERM hp300h
   64: ~~~~
   65: 
   66: Otherwise many things won't work, including vi.
   67: 
   68: On NetBSD -current with wscons support (including future 6.0 and later
   69: releases), use `wsvt25`{.code} for `TERM`{.code} environment variable as
   70: other wscons ports.
   71: 
   72: ## What is the situation with X11 on the hp300?
   73: 
   74: NetBSD 5.x includes all X11R6 clients, but there is no functional
   75: server.
   76: 
   77: NetBSD 6.0 (and later releases) will have Xorg server based on generic
   78: wsfb driver.
   79: 
   80: ## Models 345 and 425e having problems with internal hard drives
   81: 
   82: The SCSI cable in these models is **not** notched to specify which way
   83: it should be plugged in. The symptom is being unable to boot due to a
   84: SCSI register test failing. If you are *certain* that your hard drive
   85: works properly on another machine, then flip one end of the SCSI cable
   86: over.
   87: 
   88: The only other models that accept internal hard drives are the 362, 382,
   89: 4XXt, and 4XXs which do not have this uncertainty in cabling.
   90: 
   91: ## What are the Model 362 and 382?
   92: 
   93: These models were designed as instrument controllers, unlike the rest of
   94: the Series 300 and Series 400 systems which were intended as
   95: workstations or servers. The 362 and 382 are 19" rackmount units with
   96: very PC-like properties.
   97: 
   98: They have 72 pin SIMM slots (with parity on 362, with ECC on 382), two
   99: SCSI drive bays (usually HD and SCSI floppy), serial, parallel (not
  100: currently supported by NetBSD), HPIB, sound, HP-HIL, one DIO-I slot, and
  101: a VGA-style video connector. The 362 has 2 SIMM slots and you can
  102: install SIMMs one at a time. The 382 has 4 SIMM slots and you must
  103: install in pairs. Both models accept only 1, 4, and 8 MB SIMMs.
  104: 
  105: 382 has three serial ports using the Utility Chip like the Series 400
  106: models. Only one is accessible unless you build or buy the [special
  107: cable](#serialsplit).
  108: 
  109: 362 has only 640x480 8bpp VGA like graphics chip. 382 was shipped with
  110: three different graphics chipsets (all 8 bpp): 640x480 at 60 Hz,
  111: 1024x768 at 75 Hz, and 1280x1024 at 72 Hz. These on-board graphics are
  112: not supported by NetBSD 5.x and prior, but you can install a DIO-I
  113: framebuffer and disable the on-board video (there's a jumper on the
  114: motherboard).
  115: 
  116: Since the system was designed as a controller, Ethernet and external
  117: SCSI are optional and are in the form of a small card that plugs into
  118: the motherboard. The card is roughly the size of two PCMCIA cards
  119: stacked together. You can, of course, use a DIO-I Ethernet card.
  120: 
  121: Oddly, the motherboard is the same shape and size as a DIO-II card and
  122: has DIO-II connectors. Jarkko Teppo reports that you can even put the
  123: motherboard into a normal DIO-II chassis and use it as a "normal" Series
  124: 300 system. The only problem he encountered was the physical size of the
  125: Ethernet option. See [Jarkko Teppo's
  126: report](http://mail-index.NetBSD.org/port-hp300/1999/07/16/0000.html)
  127: for more info.
  128: 
  129: ## What does 'UNEXPECTED USE OF FFFFFFC4' mean?
  130: 
  131: This is the output of one of a set of temporary, informational only,
  132: exception handlers installed by the Boot ROM before an OS has been
  133: loaded. The address printed varies depending on the type of exception.
  134: The most likely cause here is trying to boot a kernel that is
  135: incompatible with the hardware. You will get something like this, for
  136: example, if you attempt to boot an HP-UX 7.0 or earlier kernel on a
  137: 68040 machine (which requires at least 7.05). If you're going to install
  138: NetBSD, you probably don't need to worry about this message, though it
  139: is possible (but unlikely) that it indicates hardware trouble or a
  140: corrupt bootloader.
  141: 
  142: * * * * *
  143: 
  144: # Boot ROM Information
  145: 
  146: ## What commands does the HP Boot ROM understand?
  147: 
  148: All the early hp300 Boot ROMs are very primitive and only allow a few
  149: simple operations. You can only interact with it after it is first
  150: powered on -- if you reboot the machine, it will ignore anything you
  151: type and start loading the same OS you previously booted.
  152: 
  153: At any time after it recognizes the keyboard, while it is doing its self
  154: test or searching for a bootable system, you can hit `reset`{.code} to
  155: return it to a cold-boot configuration. On HIL keyboards, this is
  156: `<control>-<shift>-break`{.code}, where `break`{.code} is the key in the
  157: upper left (where escape is on sane keyboards). There is no equivalent
  158: over serial terminal -- you'll need to power-cycle your machine.
  159: 
  160: After it beeps (i.e. recognizes the HIL keyboard), press
  161: `<return>`{.code} twice to get the list of bootable devices. To perform
  162: simple hardware checks, hit `<control>-C`{.code} before it starts
  163: booting an OS. You can then type `T`{.code} to perform an extended self
  164: test or `L`{.code} to perform the extended self test infinitely until it
  165: finds a fatal error or `L`{.code} is typed again.
  166: 
  167: The newer HP Boot ROM, present on Series 400 machines and some of the
  168: later 300s (345, 362, 375, 380, 382, 385) is capable of a little bit
  169: more. To select which device to boot from, press `<return>`{.code} once,
  170: after it beeps twice (i.e. recognizes the HIL keyboard). To get to a
  171: configuration and test menu, press:
  172: 
  173: ~~~~ {.programlisting}
  174:  C <return>
  175: ~~~~
  176: 
  177: This will allow you to configure interrupt levels, select codes, and
  178: serial console properties. You can also hit `<control>-C`{.code} to get
  179: to a menu of extended tests with several fancy options.
  180: 
  181: For more information, Michael Wolfson has scanned in parts of the [HP
  182: Apollo 9000 Series 400 HP-UX Owner's
  183: Guide](http://www.nosflow.com/~mw/hp300/400.manual/), which has some
  184: good information on this topic. Also, the [HP Computer
  185: Museum](http://www.hpmuseum.net/index.php) has various useful manuals
  186: and informations for many HP 9000 models.
  187: 
  188: ## What order does the Boot ROM use to search for bootable devices?
  189: 
  190: From the *Configuration Reference Manual*, 98561-90020:
  191: 
  192: **Revision A Boot ROM Specifications**
  193: 
  194: The boot ROM can load a ROM system or a file from a LIF or SRM "SYSTEM"
  195: type file having a name of the form SYSa, where "a" is typically an
  196: ASCII letter, but may be any character legal in a file name.
  197: 
  198: ROM systems are assigned a single letter ID (only "B", for BASIC, is
  199: presently supported on Series 300).
  200: 
  201: All system files found are assigned an ID of the form "nna", where "a"
  202: is either the same letter "a" mentioned above (if an ASCII letter), or
  203: "Z" (if not an ASCII letter). "nn" is a number of the form " 1" to "99"
  204: denoting the order of occurrence of systems which result in the same ID
  205: letter "a". The range of system IDs is " 1A" to "99Z".
  206: 
  207: The boot ROM loads the first system found unless characters (other than
  208: that system's ID) are typed on the boot control keyboard (see below).
  209: The search order used by the boot ROM is:
  210: 
  211: -   For select codes 7 thru 31: disc or tape (HPIB) at bus address 0,
  212:     unit 0, volume 0
  213: 
  214: -   SRM at select code 21, node 0, volume 8, "/SYSTEMS" directory
  215: 
  216: -   98259A Bubble system at select code 30
  217: 
  218: -   98255 EPROM "disc"-type system at unit 0 (lowest address of all
  219:     98255s installed)
  220: 
  221: -   ROM systems (from lowest to highest ROM address)
  222: 
  223: -   For select codes 0 thru 31, bus addresses 0 to 7, units 0 to 16,
  224:     volumes 0 to 7: all remaining discs or tapes (HPIB)
  225: 
  226: -   For select codes 0 thru 31, nodes 1 thru 62, volumes 1 to 50: any
  227:     other SRM system files in "/SYSTEMS" directories
  228: 
  229: -   For select codes 0 thru 29, and 31: remaining 98255 Bubble systems
  230: 
  231: -   Remaining 98255 "disc"-type EPROM units.
  232: 
  233: Revision B and later also support booting over the network, using a
  234: 98643 card or built-in Ethernet. For older systems, the best choice is
  235: to make your boot drive on HPIB at address 0. Remember, you'll need to
  236: capitalize the letters.
  237: 
  238: **Newer Boot ROM Search Order**
  239: 
  240: The newer machines (Models 345, 362, 375, 380, 382, 385, and Series 400)
  241: have a different boot order. From *HP Apollo 9000 Series 400 HP-UX
  242: Owner's Guide*, A1630-90006:
  243: 
  244: > The Scan for Systems selection searches mass storage devices for an
  245: > operating system to boot. The first mass storage device found with an
  246: > HP-UX Compatible operating system on it boots. Mass storage devices
  247: > are searched by the priority shown in this table.
  248: 
  249: Priority Level
  250: 
  251: Device
  252: 
  253: Select Code
  254: 
  255: Bus Address
  256: 
  257: Unit Number
  258: 
  259: 1
  260: 
  261: SCSI
  262: 
  263: 0-31
  264: 
  265: 7-5
  266: 
  267: 0
  268: 
  269: 2
  270: 
  271: HP-IB
  272: 
  273: 0-31
  274: 
  275: 7-5
  276: 
  277: 0
  278: 
  279: 3
  280: 
  281: SRM
  282: 
  283: 14
  284: 
  285: N/A
  286: 
  287: N/A
  288: 
  289: 4
  290: 
  291: LAN
  292: 
  293: 21
  294: 
  295: N/A
  296: 
  297: N/A
  298: 
  299: 5
  300: 
  301: Bubble RAM
  302: 
  303: 30
  304: 
  305: N/A
  306: 
  307: N/A
  308: 
  309: 6
  310: 
  311: EEPROM
  312: 
  313: N/A
  314: 
  315: N/A
  316: 
  317: 0
  318: 
  319: 7
  320: 
  321: SCSI
  322: 
  323: 0-31
  324: 
  325: 4-0
  326: 
  327: 0
  328: 
  329: 8
  330: 
  331: HP-IB
  332: 
  333: 0-31
  334: 
  335: 4-0
  336: 
  337: 0
  338: 
  339: 9
  340: 
  341: SRM
  342: 
  343: Other than 14
  344: 
  345: N/A
  346: 
  347: N/A
  348: 
  349: 10
  350: 
  351: LAN
  352: 
  353: Other than 21
  354: 
  355: N/A
  356: 
  357: N/A
  358: 
  359: 11
  360: 
  361: Bubble RAM
  362: 
  363: Other than 30
  364: 
  365: N/A
  366: 
  367: N/A
  368: 
  369: 12
  370: 
  371: EEPROM
  372: 
  373: Other than 0
  374: 
  375: N/A
  376: 
  377: 0
  378: 
  379: So, for these newer systems, your best bet is to make your boot drive a
  380: SCSI drive at address 6 (7 is the system controller on the motherboard).
  381: 
  382: It is also possible to configure the Boot ROM to default to a specific
  383: device from the configuration menu.
  384: 
  385: ## Switching your Series 400 machine from Domain to "HP-UX Compatible Boot Mode"
  386: 
  387: This step is necessary, since NetBSD can only boot a Series 400 machine
  388: when it's set up in "HP-UX Compatible Boot Mode". If, when you power on
  389: your machine, it does **not** present a menu as follows, then you need
  390: to follow the instructions below:
  391: 
  392: ~~~~ {.programlisting}
  393: Copyright 1990,                         
  394: Hewlett-Packard Company.                
  395: All Rights Reserved.                    
  396:                                         
  397: BOOTROM  Series 400  Rev. 1.1           
  398: MD12 REV 1.2 1990/08/07.14:27:08        
  399: MC68030 Processor                       
  400: MC68882 Coprocessor                     
  401: Configuration EEPROM                    
  402: Utility Chip at 41                      
  403: HP-HIL.Keyboard
  404: [...]
  405: ~~~~
  406: 
  407: First, you'll need either a Domain keyboard or a HIL keyboard (the Boot
  408: ROM knows how to use either, even if NetBSD doesn't yet). Now, put your
  409: machine into "service mode". For a 4XXs, there's a toggle switch on the
  410: back of the machine (near the top). For a 4XXt or 4XXdl, there's a green
  411: button on the front, behind the silly door. For a 425e, there's a toggle
  412: switch on the back of the machine (in the middle). Once you're in
  413: "service mode", the other green LED will light up. Reset the machine.
  414: You may then need to hit return to get the Domain boot prompt. At that
  415: prompt, you can type `H`{.code} to get a list of available commands. You
  416: need to type the following things to convert to HP-UX mode:
  417: 
  418: ~~~~ {.programlisting}
  419: CF
  420: 2
  421: 2
  422: P
  423: E
  424: ~~~~
  425: 
  426: [This](domain.commands.html) is the full procedure captured from a
  427: serial console.
  428: 
  429: Be sure to turn **off** "service mode" when you're done. I found it
  430: prevented me from selecting which device I wanted to boot from.
  431: 
  432: ## Where could I get a more recent Boot ROM for my 400s or 400t?
  433: 
  434: Michael Wolfson has images of the HP 425/433 Boot ROM in HP-UX mode.
  435: This is necessary when upgrading a 400 to a 425/433
  436: 
  437: See [The fatmac HP9000/300
  438: guide](http://www.nosflow.com/~mw/hp300/upgrade/) for instructions on
  439: upgrading.
  440: 
  441: * * * * *
  442: 
  443: # Serial Port Information
  444: 
  445: ## What are the different types of serial ports, and how do I access them? ([top](#))
  446: 
  447: NetBSD -current has switched to using the
  448: [com(4)](http://netbsd.gw.com/cgi-bin/man-cgi?com+4+NetBSD-6.0+i386)
  449: driver for [dca](http://man.NetBSD.org/man/dca+4.hp300+NetBSD-1.6) and
  450: [apci](http://man.NetBSD.org/man/apci+4.hp300+NetBSD-1.6) devices. This
  451: covers all built-in serial ports and some DIO serial interfaces. With
  452: this change, the device files have changed. All DCA and APCI serial
  453: ports are `/dev/ttyC[0123]`{.code} and all DCM serial ports are
  454: `/dev/ttyM[0123]`{.code}.
  455: 
  456: The APCI device (found on-board Series 400 systems) is a four-port
  457: serial mux interface. The first port connects directly with the Domain
  458: keyboard. The second port is accessible using normal DB25 pinouts and
  459: acts as the serial console (when set). The remaining two ports require
  460: use of a break-out cable.
  461: 
  462: Additionally, see the [NetBSD Serial Port
  463: Primer](../../docs/Hardware/Misc/serial.html) for information on the
  464: wiring and pinouts of various serial cables.
  465: 
  466: *device name*
  467: 
  468: *location*
  469: 
  470: *pre-2.0 device file*
  471: 
  472: *max speed*
  473: 
  474: *hardware handshaking*
  475: 
  476: *FIFO*
  477: 
  478: *serial console*
  479: 
  480: *comments*
  481: 
  482: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)0
  483: *(formerly `dca0`{.code})*
  484: 
  485: built-in
  486: 
  487: /dev/tty0
  488: 
  489: 19200
  490: 
  491: no
  492: 
  493: no
  494: 
  495: DIP switches
  496: 
  497: 318, 319, 320, 330, 340, 350, 360, 370
  498: 
  499: located on Human/System Interface board, requires [special
  500: cable](dca.cable.html)
  501: 
  502: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)0
  503: *(formerly `dca0`{.code})*
  504: 
  505: built-in
  506: 
  507: /dev/tty0
  508: 
  509: 38400
  510: 
  511: yes
  512: 
  513: yes
  514: 
  515: config Boot ROM
  516: 
  517: 345, 362, 375, 380, 382, 385, 400 Series *(except 425e)*
  518: 
  519: located on motherboard
  520: 
  521: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)1
  522: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)2
  523: *(formerly `apciN`{.code})*
  524: 
  525: built-in
  526: 
  527: /dev/ttya0 /dev/ttya1
  528: 
  529: 19200
  530: 
  531: yes
  532: 
  533: no
  534: 
  535: no, (425e: yes)
  536: 
  537: 382, 400 Series
  538: 
  539: requires [break-out cable](serial.splitter.html)
  540: 
  541: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)N
  542: *(formerly `dcaN`{.code})*
  543: 
  544: 98644A DIO-I card
  545: 
  546: /dev/ttyN
  547: 
  548: 19200
  549: 
  550: yes
  551: 
  552: no
  553: 
  554: DIP switches
  555: 
  556: hardware handshaking only for transmit
  557: 
  558: [com](http://man.NetBSD.org/man/com+4.hp300+NetBSD-current)N
  559: *(formerly `dcaN`{.code})*
  560: 
  561: 98626A DIO-I card
  562: 
  563: /dev/ttyN
  564: 
  565: 19200
  566: 
  567: yes
  568: 
  569: no
  570: 
  571: DIP switches
  572: 
  573: hardware handshaking only for transmit
  574: 
  575: [dcm](http://man.NetBSD.org/man/dcm+4.hp300+NetBSD-current)N
  576: 
  577: 98642A DIO-I card
  578: 
  579: /dev/tty0[0-3]
  580: 
  581: 19200
  582: 
  583: yes
  584: 
  585: yes, 128/16 bytes
  586: 
  587: DIP switches
  588: 
  589: Only port 0 has flow control, only port 1 does console Uses
  590: [RJ-11](dcmpinouts.html) jacks
  591: 
  592: [dcm](http://man.NetBSD.org/man/dcm+4.hp300+NetBSD-current)N
  593: [dcm](http://man.NetBSD.org/man/dcm+4.hp300+NetBSD-current)N+1
  594: 
  595: 98638 DIO-II card
  596: 
  597: /dev/tty0[0-3], /dev/tty0[4-7]
  598: 
  599: 19200
  600: 
  601: yes
  602: 
  603: yes, 127/16 bytes
  604: 
  605: no
  606: 
  607: Appears to kernel as two 98642 boards
  608: 
  609: [dcl](http://man.NetBSD.org/man/dcl+4.hp300+NetBSD-current)N,
  610: *(not supported)*
  611: 
  612: 98628A DIO-I card
  613: 
  614: /dev/ttyN
  615: 
  616: 19200
  617: 
  618: yes
  619: 
  620: yes, 256 bytes
  621: 
  622: jumper
  623: 
  624: weird centronics connector goes to normal db25
  625: 
  626: ## Setting up a serial console on a 98561, 98562, 98626, 98628, 98642, or 98644
  627: 
  628: Turn off power to your system before removing any cards. Remove the card
  629: with the serial interface.
  630: 
  631: -   **`98561-66530`{.code}** (Human Interface)
  632: 
  633:     Locate the bank of 4 DIP switches, One of them should be labeled
  634:     REM, Set the switch to ?
  635: 
  636: -   **`98562`{.code}** (System Interface)
  637: 
  638:     Locate the middle bank of DIP switches (4 switches), The third
  639:     switch is labeled REM, Set the switch to one (depress the end
  640:     labeled one), *Note: you need a [special cable](dca.cable.html)*
  641: 
  642: -   **`98626`{.code}** (dca)
  643: 
  644:     Locate the jumper by the two banks of DIP switches, Remove the
  645:     jumper
  646: 
  647: -   **`98628`{.code}** (dcl)
  648: 
  649:     Locate the bank of DIP switches by the card-edge connector, The last
  650:     switch (labeled 7) is the remote switch, Set the switch to zero
  651:     (depress the end labeled zero)
  652: 
  653: -   **`98642`{.code}** (dcm)
  654: 
  655:     Locate the 8 DIP switches, The first switch (labeled 1) is the
  656:     remote switch, Set the switch to one (slide the bump to one). *Note:
  657:     According to the manual, the Boot ROM on older machines does not
  658:     know how to use this for console, but NetBSD (and HP-UX) will, so
  659:     you won't see anything until the bootloader loads.*
  660: 
  661: -   **`98644`{.code}** (dca)
  662: 
  663:     Locate the 10 DIP switches, The last switch (labeled 1) is the
  664:     remote switch. Set the switch to one (depress the end labeled one)
  665: 
  666: Now, reinsert the card and power on your machine. All console messages
  667: will be sent over the serial port at 9600 bps, 8 bits, no parity, 1 stop
  668: bit. Theoretically, you should be using a null-modem cable, but I found
  669: that for my 98562, I needed a non-null modem cable.
  670: 
  671: ## Setting up serial console on a Model 340
  672: 
  673: Turn off power to your system. There are four DIP switches visible
  674: through the rear panel, flip the third switch from the left to one. Turn
  675: on your system.
  676: 
  677: Now, all console messages will be sent over the serial port at 9600 bps,
  678: 8 bits, no parity, 1 stop bit.
  679: 
  680: ## Setting up serial console on a Series 400 machine or a 345, 362, 375, 380, 382, or 385
  681: 
  682: This procedure does not work on the 425e, since it does not support
  683: serial console in the Boot ROM.
  684: 
  685: Wait until your system beeps twice (this is to let you know it's
  686: recognized the keyboard). Type `C<return>`{.code} and wait until the
  687: configuration menu shows up. Then type in the following set of commands:
  688: 
  689: ~~~~ {.programlisting}
  690: 1
  691: 5
  692: 3
  693: R
  694: X
  695: N
  696: ~~~~
  697: 
  698: [This](serialconsole.html) is the full procedure captured from a serial
  699: console on my 400s. [This](serialconsole380.html) is the procedure
  700: captured from a serial console on Ian Clark's 380 (and should be the
  701: same on any 345, 362 375, 380, 382, or 385). The number you type for
  702: selecting the serial settings in the menu might be different on 362 or
  703: 382 models without the optional Ethernet.
  704: 
  705: Now, your machine will reset and then send all console messages over the
  706: serial port at 9600 bps, 8 bits, no parity, 1 stop bit. Use a null-modem
  707: cable.
  708: 
  709: If you want to convert from serial console to monitor/keyboard console,
  710: follow the same procedure, except type `L`{.code} instead of `R`{.code}.
  711: 
  712: You may also *temporarily* override this setting by typing
  713: `L<return>`{.code} or `R<return>`{.code} after your system beeps twice
  714: and recognizes the keyboard. This will work even if you have a Domain
  715: keyboard.
  716: 
  717: Since the hardware takes care of this console, you do **not** add an
  718: entry for the console in `/etc/ttys`{.code}. That would be bad.
  719: 
  720: ## How do I build the cable to get at the hidden serial ports on a Series 400 machine?
  721: 
  722: Build the funky [cable](serial.splitter.html). Otherwise, just using a
  723: normal DB25 serial cable will work fine if you only want one serial
  724: port.
  725: 
  726: ## Does my System Interface Board really need a special DB9 serial cable?
  727: 
  728: Yes. A normal DB9\<-\>DB25 adaptor will *not* work. This cable is HP
  729: part number [98561-61604](dca.cable.html).
  730: 
  731: * * * * *
  732: 
  733: # Other sources of information
  734: 
  735: ## Other sources of information
  736: 
  737: -   [HP9000/300 hardware
  738:     FAQ](http://www.nosflow.com/~mw/hp300/FAQ/rossspon/hp300faq.htm) -
  739:     maintained by Ross Sponholtz.
  740: 
  741: -   [The fatmac HP9000/300 guide](http://www.nosflow.com/~mw/hp300/) -
  742:     made available by Michael Wolfson
  743: 
  744: -   [hp300 series HW brain dump by Mike
  745:     Hibler](http://mail-index.NetBSD.org/port-hp300/1994/12/15/0007.html)
  746: 
  747: -   [HP Computer Museum](http://www.hpmuseum.net/index.php)
  748: 
  749: -   [Diskless NetBSD HOW-TO](../../docs/network/netboot/)
  750: 
  751: -   [NetBSD Serial Port Primer](../../docs/Hardware/Misc/serial.html)
  752: 
  753: -   [port-hp300 mail list](../../mailinglists/#port-hp300) - if you have
  754:     any additional questions please subscribe.
  755: 
  756: -   [General NetBSD Documentation](../../docs/) - questions not specific
  757:     to NetBSD/hp300.

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb