*BSD News Article 17448


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:3229 comp.os.386bsd.bugs:961
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!cs.utexas.edu!geraldo.cc.utexas.edu!thumper.cc.utexas.edu!not-for-mail
From: vax@thumper.cc.utexas.edu (Vax)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs
Subject: Patchkit 0.2.4 breaks lpt, lpa, help me fix it.
Date: 23 Jun 1993 20:00:39 -0500
Organization: The University of Texas - Austin
Lines: 32
Message-ID: <20aubn$oeq@thumper.cc.utexas.edu>
NNTP-Posting-Host: thumper.cc.utexas.edu

PROBLEM DESCRIPTION:

I installed "interruptless-lpt.shar" from agate on the system at one point,
it worked fine.  But I upgraded to patchkit 0.2.4 from a virgin
/usr/src and /usr/include directories, and then I got an interesting error.
"status 0" from the lpt port, whenever I tried to access it.
Well, I realized the interrupt was 5 not 7, (I have it intentionally on 5),
so I set it up that way in the config file, also changing IO_LPT3 to IO_LPT1
(was that someone's idea of a joke?).  So now I remade and reinstalled the 
kernel, and I see that LPT1 and LPA1 are recognized on bootup, but
now I'm getting a "status 7f" instaead of status 0.  No dice.
Oh yeah, each status message was followed by a "/dev/lpt0: device busy"
message.  Blah.

RELATED INFO (POSSIBLY?):

Just yesterday, I noticed a single "stray intr" on the console, too.
Only seems to happen once every two days or so.
Also, I STILL get SILO overflows on my com ports, I have a 16550 on each,
I'm trying to run at over 19200 and can't, at 19200 if I ftp out I can't
send any data or else it kills the line, but i can get stuff just fine.
SILO overflows occur every few hours of heavy use & downloading.
Note that 19200 would be fast enough if my modem didn't compress.

EXTRANEOUS HELP REQUESTS:

Also, (this is the last bug, I promise) nothing that uses UDP sockets seems
to work over slip; archie, xarchie and others all hang, FSP works if I set
FSP_BUF_SIZE to 512 (or numbers lower than 1024).  Any fix for this?
-- 
Protect our endangered bandwidth - reply by email.  NO BIG SIGS!
VaX#n8 vax@ccwf.cc.utexas.edu - finger for more info if you even care.