Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

SCO 5.0.5 ppp to ISP

0 views
Skip to first unread message

amon...@my-deja.com

unread,
Nov 7, 1999, 3:00:00 AM11/7/99
to
I followed instructions from
http://www.aplawrence.com/Unixart/quickppp.shtml
But my system crash when is trying to start ppp.
I do "cu -x9 isp" and I see starting ppp on ISP site.
I do "ping isp" and after to send the username and password I see
"ISTRIP cleared" and then just CRASH with Kernel_trap E.
My Configuration files are:
ppphosts:
isp:ppp-isp uucp=isp flow=rtscts debug=0 idle=2 reqtmout=3\
conf=5 term=2 nak=10 mru=1500 retry=2 accm=0 authtmout=1
mask=255.255.255.0\
maxslot=16

Devices:
ACU tty2A - 38400 Multitech_MultiModem

Systems:
isp Any ACU 38400 18888374630 ogin: username sword password
Please somebody tell me what I'm doing wrong.
Thanks in Advance.

Sent via Deja.com http://www.deja.com/
Before you buy.

Roberto Zini

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to

Uhm ... have you applied RS505A, OSS497C and OSS600A ?

Just a wild guess,
Roberto
--
---------------------------------------------------------------------
Roberto Zini email : fr...@strhold.it
Technical Support Manager -- Strhold Sistemi EDP Reggio Emilia(ITALY)
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)

amon...@my-deja.com

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
Yes, I applied the patches in the following order.
rs505a, oss600a, oss497c.
Nestor.
In article <38269AD1...@strhold.it>,

Roberto Zini

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
amon...@my-deja.com wrote:
>
> Yes, I applied the patches in the following order.
> rs505a, oss600a, oss497c.

Uhm ... (again :-) shouldn't be the opposite (ie, RS505A,
OSS497C and OSS600A) ? Also, please consider patch
OSS471C; if you happen to have either a Pentium Pro or
a Pentium II processor, strange things could happen with
a bad microcode.

However, this is the first time I've heard of a PANIC while
accessing the serial port, honest !

Best,

Tony Lawrence

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
Roberto Zini wrote:

> However, this is the first time I've heard of a PANIC while
> accessing the serial port, honest !


Well, I have seen this with PAP and dynamic ppp on certain
ISP's. In those cases, I was able to solve it by NOT using
dynamic. I think I posted something about that a while
back, but haven't the patience to search Dejanews for it,
and it may even be that I found some other way around it
later (I honestly just cannot remember!).

--
Tony Lawrence (to...@aplawrence.com)
SCO articles, help, book reviews, tests,
job listings and more : http://www.ApLawrence.com

Evan Hunt

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to

Don't blame me, I voted for amon...@my-deja.com.

>I do "ping isp" and after to send the username and password I see
>"ISTRIP cleared" and then just CRASH with Kernel_trap E.
>[...]

>Please somebody tell me what I'm doing wrong.

Whether you're doing something wrong or not, you should *not* get
a panic, ever. Were you able to save the system dump when you
rebooted?

--
Evan Hunt - evanh at sco dot com

"The wages of sin are death. But after taxes are taken out,
it's just a sort of tired feeling." - Paula Poundstone

Jean-Pierre Radley

unread,
Nov 8, 1999, 3:00:00 AM11/8/99
to
Roberto Zini opined (on Mon, Nov 08, 1999 at 04:06:39PM +0100):

| amon...@my-deja.com wrote:
| >
| > Yes, I applied the patches in the following order.
| > rs505a, oss600a, oss497c.
|
| Uhm ... (again :-) shouldn't be the opposite (ie, RS505A,
| OSS497C and OSS600A) ?

It no longer matters.

In the October 27th revision of TA 110090, it is written:

NOTE: OSS497B, the Core OS Supplement for OpenServer Release
5.0.5, has been superseded by OSS497C. OSS497C may be
installed before or after OSS600A. In the past, it had been
recommended that OSS497B be installed right _before_ OSS600A.

--
JP

Roberto Zini

unread,
Nov 9, 1999, 3:00:00 AM11/9/99
to

As usual, thanks to JP for the info (I've completely missed 'em) !

amon...@my-deja.com

unread,
Nov 9, 1999, 3:00:00 AM11/9/99
to
In article <807djn$j8g$1...@hobbes.sco.com>,
Well, seems like the PANIC problem was fixed it, I comment it
out *routed* from /etc/tcp file.
Now the modem is continuosly dial-in to the ISP, but I may be is because
I
have Vision running in that server, isn't?
Thanks for the help.

Buddy Z

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to
Well, you will have to put rather bizarre entries into your /etc/hosts to
make it work right.
Actually, VisionFS version 1.0-1.2 has broken nsm* binaries.
You can download fixes from SCO ftp site.
There's also an article on this in SSL, try to look for "nsmsrv".
This article has not a singe "ppp" entry (believe me or not, they refer to a
"phone line"), that's why it took me a couple of months to find a solution
for this problem. Finally, somebody in this group pointed me to lsof and
lsof pointed to nsmsrv.

God bless SCO support.

Buddy Z.

Evan Hunt <ev...@sco.COM> wrote in message
news:80am85$67v$1...@hobbes.sco.com...


>
> Don't blame me, I voted for amon...@my-deja.com.

> >Now the modem is continuosly dial-in to the ISP, but I may be is because
> >I have Vision running in that server, isn't?
>

> Yes, VisionFS can cause that. It's most likely trying to do a DNS
> lookup on some system name configured in your current.prf file. If you
> edit /etc/resolv.conf so that it says "hostresorder local bind", and
> put all relevant hostnames into /etc/hosts, that should obviate the
> need for VisionFS to do a DNS lookup, and might fix the problem.

Evan Hunt

unread,
Nov 10, 1999, 3:00:00 AM11/10/99
to
0 new messages