Re: Getting ppp to work under kernel 2.1.120

Michel Catudal (bbcat@netonecom.net)
Fri, 11 Sep 1998 00:01:09 -0400

Bruce A. Locke wrote:
>
>
> Just a reminder: there are known problems involving ppp and its compression.
> For instance because of these problems I cannot connect to a certain
> bay networks terminal server(?).
>
> Upgrade to ppp 2.3.5. If the problem persists and the log files keep saying
> LCP timeouts, there is nothing you can do but wait. According to one of the
> PPP guys it is a known problem (not sure if they found the cause yet) and
> they are working on a patch.
>
> BTW, the PPP changes that introduced this problem were included in 2.1.109.
>
> Again this is probably not the cause of the problem of the person who began
> this thread (too little information to even take a guess) but I thought it
> needed reminding to stop the "PPP is 100% A-ok" theme that I keep seeing on
> here.
>
> Just a thought...
>
> -- Bruce A. Locke
>

Just to back what you are saying here is a log of what is happening
on my system when I connect to the net with kernel 2.1.120
This is when it actually connected. Often I have to reboot so it
would connect.
I have ppp-2.3.5-1 and run RedHat 5.1 with fixes dating about
a month ago. This is on a 686 From IBM at 230Mhz with 40M of Ram.
In this case once it connected I'm OK except that for the 2 hrs or
so that I was connected it would repeat that stupid message that
you see every 30 seconds or so. Very annoying to say the least.
If for some reason the line goes dead, it is not always possible
to reconnect and even to get back to XFree86 if I get out of it.
I get a blank screen with an X. This situation I last described doesn't
always occur, it did yesterday and I had to reboot just to be able
to get back in X. I couldn't even shut off the modem with ifdown ppp0.
Removing the line from the wall did the trick. This didn't make the
ppp recover which was done with a reboot.

To get the system to work correctly I had to go back to 2.0.34 which
works without a problem, except for the lack of support for the plug
and pray.

This isn't the only thing that is shot in the kernel, the modules,
none of them will load despite the script file that is there to find
them. That same script works with kernel 2.0.34

Sep 9 21:32:52 localhost pppd[471]: Using interface ppp0
Sep 9 21:32:52 localhost pppd[471]: Connect: ppp0 <--> /dev/modem
Sep 9 21:32:58 localhost pppd[471]: Remote message: Login Succeeded
Sep 9 21:32:58 localhost pppd[471]: local IP address 207.142.161.143
Sep 9 21:32:58 localhost pppd[471]: remote IP address 207.142.161.5
Sep 9 21:33:21 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
at 115200
Sep 9 21:33:21 localhost pppd[521]: pppd 2.3.5 started by root, uid 0
Sep 9 21:33:21 localhost pppd[521]: Device modem is locked by pid 471
Sep 9 21:33:21 localhost pppd[521]: Exit.
Sep 9 21:33:51 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
at 115200
Sep 9 21:33:52 localhost pppd[538]: pppd 2.3.5 started by root, uid 0
Sep 9 21:33:52 localhost pppd[538]: Device modem is locked by pid 471
Sep 9 21:33:52 localhost pppd[538]: Exit.
Sep 9 21:34:22 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
at 115200
Sep 9 21:34:22 localhost pppd[545]: pppd 2.3.5 started by root, uid 0
Sep 9 21:34:22 localhost pppd[545]: Device modem is locked by pid 471
Sep 9 21:34:22 localhost pppd[545]: Exit.

-- 
Tired of Windows' rebootive multitasking?
then try Linux's preemptive multitasking
http://www.netonecom.net/~bbcat/
We have software, food, music, news, search,
history, electronics and genealogy pages.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html