Being the person who's touched the serial ports most recently,
I should probably speak up. :-)

> > Is it just me, or has serial i/o stopped working altogether in 1.1??
> That's strange.  It works fine in 1.1-Alpha

They work fairly well in 1.1. We still have a few bugs to work on, but
the ports work well enough to make my DeskWriter happy. :-)

> I have
> > been running 1.1 since it was released, not needing to use my serial ports
> > for anything.  I know they worked under 1.0.  Now, however, this results:
> > 
> > wallace# cu -l /dev/tty00
> > cu: open (/dev/tty00): Permission denied
> > cu: /dev/tty00: Line in use
> > Exit 1
> > wallace#
> 
> The second cu line appears to be in response to the first.  My guess 
> would be incorrect access priviledges for the tty00 file.  Login as 
> root and try a chmod u+x tty00.  Not sure, but I suspect it needs to 
> execute as well as read & write.

I agree it's probably a permissions problem. Though to be honest, I've
never gotten cu to work. I use tip instead, and it seems fine.

> > I am positive no other process is using /dev/tty00 (so the "Line in use"
> > certainly isn't valid).  Also, I have noticed that when I check the "serial
> > boot echo" box in the booter, nothing comes out the port (at least, not that
> > I can see on my PowerMac).  It should come out the modem port, right?
> 
> To my knowledge, serial boot echo has been dead for a long time.  The 
> serial console works, though.  Just remember to set it to whichever port 
> you plug into.

Serial Echo should come out the printer port, and does in my latest
serial code. Unfortunately this version didn't make it into 1.1 . :-(
Serial console does/doesn't work either, for the same reasons. Note:
there's a difference between being able to log in over a tty port
(which 1.1 can do) and serial console. The differences are the echoing
of boot info, and being able to come up single-user.

Hopefully we can get the latest ser.c into current soon. :-)

Take care,

Bill