Date: Sun, 23 Aug 1998 14:37:25 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: FreeBSD/Alpha make buildworld stops at groff Message-ID: <13792.23270.918856.724787@grasshopper.cs.duke.edu> In-Reply-To: <9098.903870165@time.cdrom.com> References: <13789.49021.995565.325186@grasshopper.cs.duke.edu> <9098.903870165@time.cdrom.com>
index | next in thread | previous in thread | raw e-mail
Jordan K. Hubbard writes:
> > How far do you get, exactly? Do you have an Intel or Cypress SIO?
> > (show config from the SRM console prompt will tell you).
>
> Good question! ``show config'' just shows "Device: 2, Name: COM1,
> Type: Embedded, Enabled: Yes, BaseAddr: 3f8, IRQ: 4, DMA: None"
> [simimar entry for COM2, with the expected addr/IRQ diffs].
>
> Not very instructive on the topic of chipsets and such. :(
I wasn't terribly clear. I was referring to the PCI chip at bus 0,
slot 7 which handles the ISA bridging.. On some (newer, non-buggy)
miata GL's, its:
Bus 00 Slot 07: Cypress PCI Peripheral Controller
On the older miata's with the pyxis dma & other bugs, its:
Bus 00 Slot 07: Intel SIO 82378
Another tip is to make sure your firmware is up-to-date. I'm running
V6.7-250 Feb 19 1998 11:57:45 (from show version) on my old, buggy
miata. Yet another tip is to try cold-booting the machine.
> OK, I've gotten this far now - I'll work on compiling up a gdb on the
> x86 which understands alpha (Doug sent me a configure line earlier)
> and start running serial cables. :)
Speaking of this, does anybody know how to recover a serial line on a
3.0-current/i386 host after a gdb remote attach times out? If I
fumble on setting the baud rate properly, or make some other screwup,
gdb leaves the line 'busy' & I cannot seem to get it back w/o
rebooting my destop machine (which is running a 3.0-current kernel
from sources cvsupped circa July 20th). This is both with the gdb
from Doug's directory on freefall & with one I built myself.
Nobody has the file open, tip, kermit, etc all fail to open it. There
are no lock files that I can find. A ktrace of tip trying to open it
looks like:
2406 tip CALL open(0x12030,0x2,0xa)
2406 tip NAMI "/dev/cuaa0"
2406 tip RET open -1 errno 16 Device busy
Thanks,
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13792.23270.918856.724787>