OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

Post by Moe Tr » Mon, 20 Apr 2009 00:31:40



On Fri, 17 Apr 2009, in the Usenet newsgroup comp.os.linux.networking, in


>I have researched this for hours and hours and am getting no where.

man pppd      Look at the section 'EXIT STATUS'

       2      An  error  was  detected  in processing the options
              given, such as two mutually exclusive options being
              used.

then add the option 'dryrun' or 'dump' to /etc/ppp/options

Quote:>I just installed OpenSuse 11.1 (KDE). I setup kinternet and setup my
>ISP with username and password and correct dialout number.
>It also detected my UsRobotics 56k modem just fine as it is connected
>via a serial cable. The problem is that no matter what I do it won't
>dial.

The error message says you have some options that do not work together.
Without knowing what options you have, we can't say. Note also that
SUSE had altered the pppd package to add two or three options that the
maintainers found unsatisfactory and rejected.

Quote:>I have check permissions on pppd, pap-secrets, chap-secrets to no
>avail. I know this modem works fine as it was working under Ubuntu
>just the other day.

It's not permissions, or the modem. See the man page for pppd and
read what the options that you have enabled do.

        Old guy

 
 
 

OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

Post by Moe Tr » Mon, 20 Apr 2009 05:32:32


On Sat, 18 Apr 2009, in the Usenet newsgroup comp.os.linux.networking, in


>I added the word dump to /etc/ppp/options but don't know where to look
>from there. Does that create a log file somewhere I can look at?

What it _should_ do is to provide output to the place where you are running
the command (stdout), but I guess Kinternet is stealing that device.
Become root, and _move_ the file /etc/syslog.conf to a safe spot, and make
a copy of it:

       [compton ~]#
       mv /etc/syslog.conf  /etc/syslog.conf.original
       cp /etc/syslog.conf.original /etc/syslog.conf
       [compton ~]#

Now add the following line to /etc/syslog.conf (you have to be root to do
this as well) using your favorite editor:

   daemon.debug     /tmp/some.file.name

and then check that your editing has ONLY added that one line:

      [compton ~]$ diff /etc/syslog.conf.original /etc/syslog.conf
      19a20
      >daemon.debug     /tmp/some.file.name
      [compton ~]$

The '19a20' may show different numbers, as 'diff' is telling that the
only difference in those two files is the addition of line 20 which
says mumble, mumble, and so on.  As long as this is the ONLY change
you make, we're fine. If you*up, you can run that 'cp' command
again, to copy the original back.  Once you've got this line added,
tell the syslog daemon to re-read the configuration file

     killall -HUP sysklogd

and then run Kinternet. This should put data into the file you've
identified (/tmp/some.file.name).   After you're finished with this
task, you can move the original /etc/syslog.conf to stop adding the
log data to the temporary log file.

Quote:>Also, do you know which file gets updated when I'm using Kinternet?
>When I was using Ubuntu, I got it all to work using wvdial.

Sorry - I'm a dinosaur, and use a simple three line script to run
dialout. I don't use KDE or Gnome, as I got rid of DOS/windoze back
in 1992.

Quote:>I find it so frustrating that most distros of Linux seem to make
>you fight hard to get dial-up to work.

Yes, dialup is getting less popular, and no one ever developed a good
simple tool to run pppd.  Every application author seems to have been
caught up in the mystique that using *nix is complicated and dialin is
no exception. They seem to miss the fact that when microsoft invented
the telephone in 1995, they forced all of the ISPs in the world to use
a simple non-shell based connection mechanism.  Copying the function
of windoze DUN into a *nix tool should be easy, but everyone is off
doing their own thing even if they haven't got a clue as to how simple
it could be.

Quote:>What distro of Linux would you recommend for dial up users and user
>friendliness?

That would be an opinion, and the question has been asked many, many
times. The answers vary as each person is sure that the distribution
they are using is the best - after all, why would they use anything
else?   If you've been to www.distrowatch.com, you would find that
there are over three hundred different distributions, and probably
a thousand opinions of which one of those is the right one.

        Old guy

 
 
 

OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

Post by Günther Schwar » Wed, 22 Apr 2009 04:50:27



> Also, do you know which file gets updated when I'm using Kinternet?
> When I was using Ubuntu, I got it all to work using wvdial.

> I find it so frustrating that most distros of Linux seem to make you
> fight hard to get dial-up to work.

If you have a working wvdial.conf on Ubuntu your chances are high that
it will work with SuSE Linux as well. You might have to run it as root.
But then there is no need to use Kinternet if you do not like it.
As the subject line gives 11.1: install all patches, pray and read
https://bugzilla.novell.com/show_bug.cgi?id=429772#c22
This is related to name resolution, so it won't be the source of your
problem.

Gnther

 
 
 

OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

Post by Günther Schwar » Fri, 24 Apr 2009 03:31:41



> This is what <Gnther Schwarz> shared with us today ...
>>If you have a working wvdial.conf on Ubuntu your chances are high that
>>it will work with SuSE Linux as well.
> Thanks for your reply. I will try the patches and am hoping I can get
> those from a windows computer that does work on dialup.
> I don't need to use kinternet but wouldn't mind using a gui for
> dialing rather than more typing. But heck, what's a few more
> keystrokes?

For me it is faster to set up and use wvdial as compared to kinternet.

Quote:> I have browsing the internet and see that there are many many people
> with similar issues using modems. Thanks also for the bugzilla report.
> That may be most of the problem but am uncertain at this point.

> The only way for me to get broadband is satellite where I live. It is
> pricey but I may be forced to switch.

Mobile broadband (3G) does get more and more common as well as
affordable. But not in remote areas, of course ;-)
In case Ubuntu works just fine while SuSE Linux doesn't I'd rather
change the distribution than spending a lot of time with debugging. You
might also run the modem on an embedded router with OpenWRT or the
like. This way the modem has to be configured just once, and all
systems have simultaneous net access.

Gnther

 
 
 

OpenSuse 11.1 Kinternet error: "pppd[0] died: pppd options error (exit code 2)

Post by Moe Tr » Sat, 25 Apr 2009 04:56:05


On Wed, 22 Apr 2009, in the Usenet newsgroup comp.os.linux.networking, in


>> I don't need to use kinternet but wouldn't mind using a gui for
>> dialing rather than more typing. But heck, what's a few more
>> keystrokes?
>For me it is faster to set up and use wvdial as compared to kinternet.

[galileo ~]$ cat /etc/ppp/options | column
lock            crtscts         nodetach        defaultroute
/dev/modem      modem           115200          noipdefault
[galileo ~]$ ls -l /etc/ppp/*ap-secrets /etc/resolv.conf
-rw-------   1 root     root       99 Jun 16  2008 /etc/ppp/chap-secrets
-rw-------   1 root     root       94 Jun 16  2008 /etc/ppp/pap-secrets
-rw-r--r--   1 root     root       49 Jun 16  2008 /etc/resolv.conf
[galileo ~]$ cat /usr/local/bin/dialin.example

ABORT BUSY \"\" AT\&F1 OK ATDT26662902 CONNECT \"\c\d\""
[galileo ~]$

Watch the quotes and backslashes in the dialin file. That is all one
long line, 119 characters long. You could make it into two lines:


ABORT BUSY \"\" AT\&F1 OK ATDT26662902 CONNECT \"\c\d\""

but make sure nothing follows the \ at the end of the first line - it's
hiding the line break.  (The 'connect' option expects one argument, and
is quoted to hide spaces, etc.  However, /usr/sbin/chat also needs some
stuff to be quoted, and the backslashes are hiding the quote characters
and ampersand ['&'] from the 'connect' string and shell.)  The dialin
file is one of 12 here, because I have several ISPs, each one having
several different phone numbers.   Here, the /etc/ppp/options file
contains only the "common to all ISP" options (one option per line).
Note that the string that follows the 'user' (here,

entry in /etc/ppp/*ap-secrets depending on the authentication scheme
(PAP or CHAP) used by your ISP.   Each dialin file differs in username
and telephone number, so all I have to remember is that 'dialin0'
through 'dialin3' gets one ISP, and so on.      So terribly hard to do.

Quote:>In case Ubuntu works just fine while SuSE Linux doesn't I'd rather
>change the distribution than spending a lot of time with debugging.

Yeah, Ubuntu (actually Debian) made fewer ``improvements'' to the ppp
package than SUSE did.

        Old guy

 
 
 

1. tinyX gives "xinit: Unknown error (errno 0): Client error." error and dies

I am trying to set up tinyX on a system I have at home. The system is
a 386SX/16 with 8 megs of RAM, 12 megs of swap space, and around 160
megs of hard drive space. It has a generic 256K video card and a Dell
13 inch monitor. (Not much of a system, I know, but I got it for
free). When I try to start up tinyX, the X server starts up (I see the
dithered background with the X cursor), and then it dies. Below is the
output it produces on the console as it is starting and dying:

Script started on Sun Oct  1 14:31:24 1995
dogbert:/usr/X386# startx

XFree86 Version 2.0 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Operating System: Linux
Configured drivers:
  VGA16: server for 4-bit colour VGA (Patchlevel 0):
      et4000, generic
(using VT number 9)

Xconfig: /usr/X386/lib/X11/Xconfig
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Microsoft, device: /dev/ttyS0, baudrate: 1200
(**) FontPath set to "/usr/X386/lib/X11/fonts/misc/"
(--) VGA16: chipset:  generic
(--) VGA16: videoram: 256k (using 256k)
(--) VGA16: clocks:  25.50  28.32  35.50   0.00
(--) VGA16: Maximum allowed dot-clock: 90MHz
(**) VGA16: Mode "640x480": mode clock =  28.322, clock used =  28.322
(**) VGA16: Virtual resolution set to 800x600

waiting for X server to shut down

xinit:  Unknown error (errno 0):  Client error.
dogbert:/usr/X386#

Does anyone have any idea what is causing it to die like this?
Suggestions are greatly appreciated. Obviously it would be better if I
were running on a faster machine, but I can't afford to upgrade just
yet, so if anyone can suggest how to get this working in the meantime,
I would be most grateful.

TIA,

/Matthew

--
Matthew Cravit,               | "Cum catapultae proscriptae erunt tum
DePaul University, Chicago IL |  soli proscripti catapultas haberunt."

2. Problem running tksh on Redhat Linux

3. pppd "ktune" & "proxyarp" options

4. Help on Linux installer

5. pppd: The pppd daemon died unexpectedly.

6. what dir

7. Ghostview ==> Ghostscript "Unrecoverable error: exit code 1"

8. ET4000 w32p & 16bpp

9. PPPD problem (dies waiting for PPPD to come up)

10. pppd[212]: lcp_reqci: rcvd unknown option 19; pppd[212]: input: Unknown protocol (80fd) received!

11. "pppd[xxx]: tcgetattr: I/O error"

12. "bad frames" error using pppd

13. "No free pty′s found" Error message by PPPD