Couldn't find interface ppp0: No such device

when I run kppp and pushed the 'connect' button, I got the following
messages:
[root@localhost ~]# kppp
kbuildsycoca running...
ScimInputContextPlugin()
Opener: received OpenLock

Opener: received OpenDevice
Opener: received ExecPPPDaemon
In parent: pppd pid 4159
Couldn't find interface ppp0: No such device
Kernel supports ppp alright.
Couldn't find interface ppp0: No such device

at the same time, I got the following messages in the ppp log:

Sep 16 17:30:26 localhost pppd[4373]: pppd 2.4.3 started by root, uid
0
Sep 16 17:30:26 localhost pppd[4373]: Using interface ppp0
Sep 16 17:30:26 localhost pppd[4373]: Connect: ppp0 <--> /dev/ttyS3
Sep 16 17:30:56 localhost pppd[4373]: Terminating on signal 15
Sep 16 17:30:57 localhost pppd[4373]: Hangup (SIGHUP)
Sep 16 17:30:57 localhost pppd[4373]: Modem hangup
Sep 16 17:30:57 localhost pppd[4373]: Connection terminated.
Sep 16 17:30:57 localhost pppd[4373]: Exit.

what should I do?
any reply will be welcomed,thks a lot!

BEST REGARDS
crocodilian

abelard <(E-Mail Removed)> wrote:
> when I run kppp and pushed the 'connect' button, I got the following
> messages:
> [root@localhost ~]# kppp
> kbuildsycoca running...
> ScimInputContextPlugin()
> Opener: received OpenLock

> Opener: received OpenDevice
> Opener: received ExecPPPDaemon
> In parent: pppd pid 4159
> Couldn't find interface ppp0: No such device
> Kernel supports ppp alright.
> Couldn't find interface ppp0: No such device

It appears that kppp is confused.

> at the same time, I got the following messages in the ppp log:

> Sep 16 17:30:26 localhost pppd[4373]: pppd 2.4.3 started by root, uid
> 0
> Sep 16 17:30:26 localhost pppd[4373]: Using interface ppp0
> Sep 16 17:30:26 localhost pppd[4373]: Connect: ppp0 <--> /dev/ttyS3
> Sep 16 17:30:56 localhost pppd[4373]: Terminating on signal 15
> Sep 16 17:30:57 localhost pppd[4373]: Hangup (SIGHUP)
> Sep 16 17:30:57 localhost pppd[4373]: Modem hangup
> Sep 16 17:30:57 localhost pppd[4373]: Connection terminated.
> Sep 16 17:30:57 localhost pppd[4373]: Exit.

Best guess, the initial LCP request is repeated 10 times at intervals
of 3 seconds with no response forthcoming and pppd terminated. LCP is
short for "Link Control Protocol" which is used to negotiate certain
properties of a PPP link. This kind of "timeout" occurs when one side
or the other doesn't receive what is sent to it or what it receives
is broken in transit. Adding "debug" to /etc/ppp/options will likely
result in a log showing the LCP requests.

There are various things that might cause this to happen, mostly
at the serial/modem level. Unfortunately I know little about kppp
except the usual for such programs: when it works it's easy to use
and when it doesn't it's hard to debug.

> what should I do?

Provide more information. Does the modem appear to dial out and
connect? Is the number dialed correct? Is it a real modem or
a winmodem? (Good luck if it's a winmodem) Is /dev/ttyS3 correctly
configured for the actual UART, port number, and IRQ of the serial
device? (setserial -bg /dev/ttyS3, compare to serial device specs)

Configure kppp to log the modem initialization and the modem's line
negotiations if possible. Post.

Here is a logging recipe for pppd and chat (the program for making
the serial connection that comes with pppd). Dunno about kppp.

Add the line

daemon.*;local2.* /var/log/ppp.log

to /etc/syslog.conf, do "killall -HUP syslogd" to get syslogd to reread
that file, and temporary add the pppd option "debug" to /etc/ppp/options.
Then try to make a connection and post the resulting log file.

> any reply will be welcomed,thks a lot!

> BEST REGARDS
> crocodilian

Regards-
--
Clifford Kite