Alas, it didn't work. Actually, it did get minicom to the same level as
screen... now I'm getting the same thing in both. Here's cut&paste from
my xterminal to show what I'm getting.
pyright.t-Packary. 1992.
OM rev. C ROM re400 MB o configutested.
ing a syboot.
selectio and holCAPE keyection process s
ing for l Boot D
To termarch, press and e
------------------------------------------ EAGATE S
Bootecifis
xit and continue boot se?) Helect fro
That's what I'm seeing (80 chars wide). Is this possibly due to a
non-null-modem cable? If so I can go buy an adapter. I'd rather not if I
already have a null-modem cable though. Any other ideas? I got to the
BOOT_ADMIN> prompt and typed path console rs232_a.9600.8.none and then
restart, and it restarted, but didn't change anything.
Thanks,
Hans :)
On Mon, May 06, 2002 at 04:43:36PM +0100, Matthew Wilcox cried:
> On Mon, May 06, 2002 at 09:39:28AM -0600, Hans Fugal wrote:
> > So I dug around and found a cable, and it very well could be a
> > null-modem cable. I plug it into the serial ports and fire up the
> > machine. I haven't figured out how to make minicom talk to it, but I
> > have screen talking to the hp, in a manner of speaking. I can see parts
> > of words but never everything. I started screen thus:
> > screen /dev/ttyS1 9600,cs8
> > I tried using minicom by setting the serial port, baud, and 8-N-1, but
> > it never shows anything on the screen. So, if I don't have a null-modem
> > cable is it possible to see some stuff, or is it likely that I have a
> > null-modem cable and I'm just not doing something right?
>
> You need to disable hardware & software flow control with minicom.
>
> --
> Revolutions do not require corporate support.
--
YAAH! DEATH TO OATMEAL!
-- Calvin
Attachment:
pgpI9Jos9TjzP.pgp
Description: PGP signature