mishcopal: are you booting up the PC and then later powering up the modem or
is the modem powered up and all the cabling is hooked up to the PC at the time
the PC is booted up? udev is what makes the device files under /dev in FC5,
I just wonder if maybe udev doesn't make the /dev/ttyS# files if the
modem isn't alive at boot time. But that's a hint I read about on a ubuntu
forum so I'm not sure if that relates to fedora
https://wiki.ubuntu.com/DialupModemH...07c8fb24478187
I guess that's unlikely because my PC doesn't even have serial ports
to plug a modem into and my /dev directory has the ttyS{0,1,2,3} files
have you actually used "ls" to confirm the serial devices are there under
/dev before you try kppp? Expect to see:
Code:
ls -l /dev/ttyS?
crw-rw---- 1 root uucp 4, 64 Jun 9 20:07 /dev/ttyS0
crw-rw---- 1 root uucp 4, 65 Jun 9 20:07 /dev/ttyS1
crw-rw---- 1 root uucp 4, 66 Jun 9 20:07 /dev/ttyS2
crw-rw---- 1 root uucp 4, 67 Jun 9 20:07 /dev/ttyS3
The thing about needing a reboot for kppp to start again might
be related to secondary processes kppp starts: pppd is the
big one. pppd makes a lock file(s) in /var/run/ppp. If kppp has
a problem, make sure /var/run/ppp/*.pid files are gone
and the pppd process itself is killed off. When you reboot,
there's a init script that cleans up /var/run and /var/lock
areas of these lock files and the reboot cleans out hung
processes for sure too.
I can't actually try any of this right now because my PC is
legacy free and doesn't even have a serial port (I have
a nice external modem though from earlier pc's)
Mark