bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) (10/05/89)
There appears to be a problem with Support Level Supplement (SLS) xnx128.
It is supposed to correct the problems associated with internal modems
under SCO XENIX 286 2.2.3 and SCO XENIX 386 2.3.1, instead it corrupts
libio.a and causes the following error upon the next reboot...
TRAP 0000000E in SYSTEM, error code=00010002
eax=FFFF0000, ebx=00014E1C, ecx=0200001A, edx=000000A1
esi=00014B60, edi=00000000, ebp=060005EC, fl=00010297
uds=00030018, es=00000018, fs=00070000, gs=00000000, tr=00000050
pc=00010020:00012244, ksp=060005CC
kernel: PANIC: non-recoverable kernel page fault
I am running SCO XENIX 386 2.3.1 with an AST Fourt-Port card. I was
hoping this supplement would allow me to install some internal modems.
Fortunately the update backed up the original /usr/sys/io/libio.a, so I
was able to restore it to its original condition and compile/link a new
kernel. Has anybody else on the net experienced this problem?
Do you folks at SCO (Ross?) have a fix for this?
--Carmen
--
Carmen Hardina, Assistant System Administrator
INET: islenet!manapua!carmen@uhccux.uhcc.Hawaii.Edu
UUCP: {uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!islenet!manapua!carmenbblue@toshi.cts.com (Bill Blue) (10/06/89)
In article <5019@uhccux.uhcc.hawaii.edu> bt455s39@uhccux.uhcc.hawaii.edu (Carmen Hardina) writes: >There appears to be a problem with Support Level Supplement (SLS) xnx128. >It is supposed to correct the problems associated with internal modems >under SCO XENIX 286 2.2.3 and SCO XENIX 386 2.3.1, instead it corrupts >libio.a and causes the following error upon the next reboot... >kernel: PANIC: non-recoverable kernel page fault I ran across this a couple of weeks ago and reported it to sco!rosso, who told me they were unaware of any problems and that I should send info about it to sco!support. I never did, though. The problem of the getty messages that prompts the need for xnx128 can be caused by a modem that is sending response codes to the getty when it should really be silent (like when answering a ringing line). On external modems the problem can *also* be caused by the RI line of the serial cable being connected through, as might happen in a straight-through cable (pin 22 on a 25 pin and pin 9 on a 9 pin connector). Just lift that line and all is well. After discovering this, I went all through the manuals trying to find a reference to *anything* other than the modem sending result codes, and couldn't. Can anyone point me to where this is discussed? --Bill
jca@pnet01.cts.com (John C. Archambeau) (03/05/90)
Hmm, maybe SCO will make a special upgrade policy to SCO Xenix 386 users
allowing you to upgrade to SCO Unix for a nominal fee once this "we're
abandoning it" policy takes effect. If SCO is smart (which I doubt), maybe
they will. Obviously, Xenix 286 users will be out in the cold since there's
no SCO Unix 286 out there (that I've seen). Of course, for those of us who
are use to being abandoned by software companies are probably sighing with
that "here we go again" tone again. What ticks me off is that I'm about to
buy SCO Xenix 386 and a 386(SX) machine just for running Xenix until I get
a full blown 386 machine. I can understand SCO wanting their Unix to
catch on, but get a clue guys, we don't want to get our bank accounts bled dry
in the process nor get gutted completely with respect to support. Are you
listening SCO? Maybe SCO will have a fire sale on Xenix for those of us that
don't want to buy their Unix product yet. Regardless of what does happen, I
will be buying SCO Xenix 386 over SCO Unix 386 when my 386(SX) machine is
here even if it means buying a used master set from somebody who doesn't
want to deal with this policy that SCO is imposing. Maybe they don't want to
yell at SCO when something doesn't work, but I can (and sometimes enjoy doing
it) and some people swear that I'm possessed by Sam Kinison when I'm dealing
with a real assinine company. Could it be that I'm good at yelling?
Nah... ;)
Fortunately the companies who I've dealt with over support for customers and
even end user are nice for the most part. Even Novell is nice to me and they
have yet to see me yell to the point where I make the windows shake, but it
seems like SCO might, especially if I'm an end user of their product.
// JCA
/*
**--------------------------------------------------------------------------*
** Flames : /dev/null | My opinions are exactly that,
** ARPANET : crash!pnet01!jca@nosc.mil | mine. Bill Gates couldn't buy
** INTERNET: jca@pnet01.cts.com | it, but he could rent it. :)
** UUCP : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
**--------------------------------------------------------------------------*
*/