Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:1757 comp.os.386bsd.bugs:524 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!bogus.sura.net!udel!sbcs!stark.UUCP!gene From: gene@cs.sunysb.edu!stark (Gene Stark) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Subject: Re: silo overflows and failed fixes -- trying syscons-0.2 and trap 12 Date: 19 Apr 93 07:27:43 Organization: Gene Stark's home system Lines: 46 Message-ID: <GENE.93Apr19072743@stark.uucp> References: <1993Apr18.202524.12821@csi.com> NNTP-Posting-Host: stark.uucp In-reply-to: bkp@csi.com's message of Sun, 18 Apr 1993 20:25:24 GMT In article <1993Apr18.202524.12821@csi.com> bkp@csi.com (Brian K. Pheiffer) writes: > I've been running a 486DX (with patch level 0.2.2, Orchid Prodesigner > IIs, 3com 3c503 at 0xDC000, com1, com2, com4 at irq 5, 32Mb, Maxtor IDE > 230 Mb) with no problem except silo overflows. I've been trying > different ways to fix this problem but keep hitting a wall. > > I first tried Gene Stark's mods to CGD's comkit. This booted and > worked fine except I wasn't able to use my com ports *at all*. Every > command (tip,cu,kermit) would hang trying to open the port. First make sure that you have the "bidir" option set properly and that you are using the right minor device (callin, callout) as per the instructions that come with CGD's driver (not included in my kit). If that doesn't work, then check your cables. CGD's driver is very fussy about having the carrier detect signal present in some form. If you connect to a device that does not generate the carrier detect, or if you do not use a modem cable that transmits the carrier detect, a process trying to open the device will hang (ps alx shows "ttopen", I think). Also you can check if this is your problem by doing "stty -f /dev/com??? clocal", before trying to open the device. You must make sure that getty is *not* running and *will not* run when you do this, because getty has a tendency to turn the clocal flag back off again whenever it feels like it. If it turns out that this was your problem, then fix your cables. Either get full modem cables that transmit the carrier detect signal, or make sure that you have CD jumpered to DTR/DSR. > I saw that his was based on patchkit 0.2.2 + syscons-0.2 so I tried > installing syscons-0.2. I rebuilt the kernel and right before the > fsck check on reboot -- the kernel paniced with: I don't know about this, sounds like maybe you got something wrong with the rebuild. > So that wasn't optimal. I also tried CGD's com-beta.0.2.1 patches, > but they also had the same problem as Stark's: I couldn't open the > devices. This is why I suspect the cable problems. -- stark@cs.sunysb.edu