Hi List, hi Carsten
Since yesterday I can no longer connect. I haven't changed a thing, so I
wonder whats going on (I'm suspecting my provider to have changed
something, but what? :()
Why is modprobe searching for this module?
(I'm running a 7.1 with a 2.4.5 kernel)
That's how it looked yesterday
Jun 30 17:17:31 metropolis su: FAILED SU (to schlpbch) konqi on /dev/pts/1
Jun 30 17:17:38 metropolis su: (to root) konqi on /dev/pts/1
Jun 30 17:17:38 metropolis PAM-unix2[26077]: session started for user
root, service su
..
Jun 30 17:18:19 metropolis modprobe: modprobe: Can't locate module
sound-service-0-3
Jun 30 17:18:27 metropolis pppd[26119]: pppd 2.4.0 started by konqi, uid 501
Jun 30 17:18:27 metropolis pppd[26119]: Perms of /dev/ttyS0 are ok, no
'mesg n' neccesary.
Jun 30 17:18:27 metropolis pppd[26119]: using channel 5
Jun 30 17:18:27 metropolis pppd[26119]: Using interface ppp0
Jun 30 17:18:27 metropolis pppd[26119]: Connect: ppp0 <--> /dev/ttyS0
Jun 30 17:18:27 metropolis pppd[26119]: sent [LCP ConfReq id=0x1
<pcomp> <accomp>]
Jun 30 17:18:27 metropolis pppd[26119]: rcvd [LCP ConfReq id=0x1
<auth chap MD5> <pcomp> <accomp>
]
Jun 30 17:18:27 metropolis pppd[26119]: sent [LCP ConfRej id=0x1 ]
Today I get:
metropolis /etc/ppp# wvdial
--> WvDial: Internet dialer version 1.41
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2
ATQ0 V1 E1 S0=0 &C1 &D2
OK
--> Modem initialized.
--> Dialing bluewin .
--> Idle Seconds = 180, disabling automatic reconnect.
--> Sending: ATDT0840840111
--> Waiting for carrier.
ATDT0840840111
CONNECT 64000/ISDN/V120
Entering PPP mode.
OK
--> Modem initialized.
--> Dialing bluewin .
--> Idle Seconds = 180, disabling automatic reconnect.
--> Sending: ATDT0840840111
--> Waiting for carrier.
ATDT0840840111
CONNECT 64000/ISDN/V120
Entering PPP mode.
Async interface address is unnumbered (Loopback1)
Your IP address is 62.202.25.50. MTU is 1500 bytes
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Sun Jul 1 23:09:41 2001
--> pid of pppd: 2611
--> Disconnecting at Sun Jul 1 23:09:41 2001
--> The PPP daemon has died: Fatal pppd error (exit code = 1)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd
--> man pages for more information.
Jul 1 22:59:33 metropolis pppd[1342]: Exit.
Jul 1 23:00:03 metropolis su: (to konqi) schlpbch on /dev/pts/1
Jul 1 23:00:03 metropolis PAM-unix2[1374]: session started for user
konqi, service su
Jul 1 23:00:12 metropolis pppd[1392]: Plugin /usr/lib/passwordfd.so loaded.
Jul 1 23:00:12 metropolis pppd[1392]: pppd 2.4.0 started by konqi, uid 501
Jul 1 23:00:12 metropolis pppd[1392]: Perms of /dev/ttyS0 are ok, no
'mesg n' neccesary.
Jul 1 23:00:12 metropolis modprobe: modprobe: Can't locate module
tty-ldisc-3
Jul 1 23:00:12 metropolis pppd[1392]: Couldn't set tty to PPP
discipline: Invalid argument
Jul 1 23:00:12 metropolis pppd[1392]: Exit.
Jul 1 23:00:26 metropolis PAM-unix2[1374]: session finished for user
konqi, service su
Jul 1 23:02:30 metropolis pppd[1404]: Perms of /dev/ttyS0 are ok, no
'mesg n' neccesary.
Jul 1 23:02:30 metropolis modprobe: modprobe: Can't locate module
tty-ldisc-3
Jul 1 23:02:30 metropolis pppd[1404]: Couldn't set tty to PPP
discipline: Invalid argument
Jul 1 23:02:30 metropolis pppd[1404]: Exit.
I should commit a patch to the KDE CVS, so help is really appreachated.
Andreas
--
Hack on, hack strong, 'til the break of dawn.
Andreas Schlapbach schlpbch@iam.unibe.ch ¦¦ schlpbch@kde.org
http://www.iam.unibe.ch/~schlpbch
