Subject: Re: DUO 230: Serial Echo
To: Bill Studenmund <wrstuden@loki.stanford.edu>
From: Tom Tarka x3212 <tommy@boulder.vni.com>
List: port-mac68k
Date: 03/10/1997 13:04:00
Well, in this case I was using a "printer" cable, I guess.  So my dilemma
returns.  It seems odd to me that I could do a zterm to zterm connection but that I
couldn't do a 


On Mon, 10 Mar 1997, Bill Studenmund wrote:

> > 
> > 
> > > Try a printer cable. Mac printer cables are wired as null modems
> > > (printers and macs have the same pinouts; that's why you can use the
> > > same LocalTalk boxes on a mac and a printer).
> > 
> > this would (since I am *so* uniformed, as I'm quickly finding!) beg the
> > question, how do I know the different between a printer cable and a 
> > localTalk cable.
> 
> There really isn't a LocalTalk cable. LocalTalk is the networking where
> you plug the little box into the printer port, and daisy-chain the
> boxes to each other. You can use Apple's LocalTalk cables, or PhoneNet
> (using phone-grade twisted pair wiring).
> 
> All I can think of when people talk about "LocalTalk cables" is that they
> are either using a pair of LocalTalk boxes, or using a phone cable with
> a PhoneNet connector on each end. There are some PhoneNet connectors
> which have just one plug (and terminate), so you could get two of those
> and hook them together with a phone cable. It'd work for LocalTalk, but
> not standard serial ports.

Ah, then it seems I was using a printer cable.  So the dilemma returns,
and I present my original question:

I'm trying to get a serial console or boot echo to work from my Powerbook
duo 230 to a 6100/66 running zterm.  I can get a direct connection
going between the two machines if I run zterm on both, but attempting
to turn on Boot echo or serial console results in no output to the other
machine.

My Configuration:

Duo 230, 12/122, 120 = 110 root/usr + 12 swap, Apple MiniDock, external
15", extended keyboard and mouse


Here's what I've done:

The 6100 is running zterm, 9600 N81, with or w/o Xon/Xoff
The Duo:
   some of the kernel/binary combinations attempted:
        a: 1.2 binaries, Daishi kernel
        b: -current (mar ~3) binaries, Daishi kernel
        c: 1.2 binaries, GENERIC25 kernel
        d: -current, GENERIC 25 kernel
   other modifications:
        e: configurations a,b,d with getty running on either or
                both tty01,tty00
   booter modifications:
	f: either or both serial ports set to raw, serial boot echo
        g: either or both serial ports set to raw, serial console

When booting to serial console, the boot gets to the "So I sayz to 
him...", then nothing happens (I suspect this is where it should start
being sent to the serial console?).  Otherwise, with the boot echo on,
nothing happens, although sometimes when using the 1.2 binaries and either
kernel, if I hit return or send a break from the 6100, the NetBSD box will
hang (at a prompt, during boot, whichever).  I'm not sure if this happens with the
-current stuff, I'm not sure that I've tried this. 

Questions I have/potential problems:

1. Perhaps the modem and printer ports are not tty01 or tty00
   (I suspect this is the case for the Daishi kernel, but I'm not sure how to figure this out)
        a. Solution: try serial console without Dock 
	b. Play around in the kernel (clues on how to do this?)


Thanks,
        Tom