Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!bellcore!texbell!vector!attctc!mic!merlin
From: merlin@mic.UUCP (Merlin Wilkerson)
Newsgroups: comp.unix.i386
Subject: Re: X5 Update - Serial Bugs
Summary: hasn't helped
Message-ID: <290@mic.UUCP>
Date: 10 Oct 89 23:12:07 GMT
References: <[2531618a:210]comp.unix.i386@tronsbox.UUCP> <[2531d5ce:22.1]comp.unix.i386;1@nstar.UUCP>
Reply-To: merlin@mic.UUCP (Merlin Wilkerson)
Organization: Micro Net
Lines: 29

In article <[2531d5ce:22.1]comp.unix.i386;1@nstar.UUCP> akcs.larry@nstar.UUCP (Larry Snyder) writes:
>>Well, I am about ready to give up on ISC 2.0.2 . 
>>If there is anyone who has managed to get a GOOD asy device running from any
>>source, I could really use the help.
>
>Well - I assume you didn't install the X5 kernel configuration guide which
>will solve most if not all of your problems.

    WELL, you know what happens when you ASSume.  I *have* installed the
"X5 kernel upgrade".  It solved exactly zero problems. (other than help
me discover the kernel rebuild bug in kconfig). 
    I followed the docs and had my hopes up.  I put a getty on the
line and recieved a call.  I dialed out with cu with no problem.  
"Allright", I exclaimed.  However, when I disconnected, the RD and SD 
lights were blinking rapidly and the getty process had become 
immortal.  Subsequent calls to cu gave "CAN'T ACCESS DEVICE" errors.
Resets and retest yielded the same results.  
    I would really like a bi-direction modem to work.  After several 
weeks of "going to ship the fix next week" responses form ix tech, and
then it doesn't work, I can understand being ready to give up.
    I just can't believe that ix doesn't think this is a big deal.
Evidently they want serial board manufacturers to solve this problem
for them.  Then they can just stiff-arm the poor fools that think
it should work.  Flame me all you want, but it shouldn't take an
EE, a C expert, a UNIX guru, and an act of GOD to get bidirection
working on a standard serial port.

thanks,
merlin