Couldnt set tty to PPP discipline
 

i upgraded to slack 10 (from 9.1) over the weekend, and have just been setting up everything again one of the first things i did was upgrade the kernel to 2.6.7 and it worked first time!! :)

i finished setting up everything then ran throught the PPP script as usual, it dailed up (standard 56k) no problems

#serial connection established.
(then)
Couldn`t set tty to PPP discipline: Invalid argument

and the modem clicks off

i rechecked the script, name servers etc and the same thing happened.

google and the forum search werent helpful


thanks for your help

Try to copy the tty/ppp modules parameters from your /etc/modules.conf to your /etc/modprobe.conf as kernel 2.6.7 use modprobe.conf

there is nothing in the /etc/modules.conf or /etc/modprobe.conf

:( , anything else you can think of?

I am in the exact same boat. I got slackware 10 installed, upgraded the kernel to 2.6.7, downloaded the latest ltmodem source for kernel 2.6 at http://linmodems.technion.ac.il/pack...-alk-4a.tar.gz, compiled and set up my kernel, and compiled and set up the modem driver... Using kppp, all I keep getting is exit code 1 on PPP, and if I check details I get the "Couldn't set tty to PPP discipline" message. I also downloaded wvdial and wvdialconf and the necessary libraries under windows, compiled and set them up under linux, and got the same problem.

I've ran across this error before on the 2.4 kernel, but somehow got it to work right by some fluke, I don't recall what I did. I haven't been as lucky this time.

Hey, I found a solution!

For me, the problem turned out to be my own doing. I compiled PPP into my kernel, but I did not compile PPP's serial support, which is required if you want to use a dial-up modem. You probably recall that under Windows the modem took its own COM port, even if it didn't match up with a serial port on the computer? Same thing here essentially - if you don't have serial support, then PPP will just totally crash.

Have fun!

- Vultaire