Hello, I installed SuSE 8.1 on my spare PC yesterday, and I'd like to get its ltmodem working if poss. I've had it working with with various flavours of Mandrake & RedHat in the past, and it's worked very reliably. So, after a quick uname check, I downloaded ltmodem-kv_2.4.19_4GB-8.26a9-1.i386.rpm and attempted to install it. No joy - it complains that "k_deflt = 2.4.19-4GB" is needed. Now, I do have k_deflt installed, but it's k_deflt-2.4.19-74. Yet uname reports that my kernel is 2.4.19-4GB, and in fact many of the files provided by k_deflt-2.4.19-74 have "2.4.19-4GB" in their path. I did try experimenting by installing the ltmodem rpm with --nodep, but my box froze when I tried to dial out. Anyone actually got an ltmodem running under SuSE 8.1? Thanks, James
On Mon, 21 Jul 2003 16:46:02 +0100
James Gibbon
Hello,
I installed SuSE 8.1 on my spare PC yesterday, and I'd like to get its ltmodem working if poss. I've had it working with with various flavours of Mandrake & RedHat in the past, and it's worked very reliably.
So, after a quick uname check, I downloaded ltmodem-kv_2.4.19_4GB-8.26a9-1.i386.rpm and attempted to install it. No joy - it complains that "k_deflt = 2.4.19-4GB" is needed.
Now, I do have k_deflt installed, but it's k_deflt-2.4.19-74. Yet uname reports that my kernel is 2.4.19-4GB, and in fact many of the files provided by k_deflt-2.4.19-74 have "2.4.19-4GB" in their path.
I did try experimenting by installing the ltmodem rpm with --nodep, but my box froze when I tried to dial out.
Anyone actually got an ltmodem running under SuSE 8.1?
I ran into the same problem on my 8.2 laptop. I simply told YaST to
ignore the conflict and proceed. Ltmodem works fine.
I am having a problem with kppp, but I have not double checked the FAQ.
(In this case, the daemon dies after receiving the connect message).
--
Jerry Feldman
Jerry Feldman wrote:
Anyone actually got an ltmodem running under SuSE 8.1? I ran into the same problem on my 8.2 laptop. I simply told YaST to ignore the conflict and proceed. Ltmodem works fine.
I am having a problem with kppp, but I have not double checked the FAQ. (In this case, the daemon dies after receiving the connect message).
Thanks Jerry, your post gave me the encouragement to try it again, this time it worked fine. I hate ignoring dependencies when installing stuff, but my ltmodem works nicely under SuSE 8.1 now. However initially I ran into the old problem of pppd dying after connect, too - I don't know if it's the same issue as your problem, but I've fixed this before, and for me .. # echo plugin passwordfd.so > /etc/ppp/peers/kppp .. did the trick. On a related point, anyone know of an 'rpm editor' that will allow dependencies to be modified, removed or whatever from a package file? James
On Mon, 21 Jul 2003 23:31:29 +0100
James Gibbon
Jerry Feldman wrote:
Anyone actually got an ltmodem running under SuSE 8.1? I ran into the same problem on my 8.2 laptop. I simply told YaST to ignore the conflict and proceed. Ltmodem works fine.
I am having a problem with kppp, but I have not double checked the FAQ.(In this case, the daemon dies after receiving the connect message).
Thanks Jerry, your post gave me the encouragement to try it again, this time it worked fine. I hate ignoring dependencies when installing stuff, but my ltmodem works nicely under SuSE 8.1 now.
However initially I ran into the old problem of pppd dying after connect, too - I don't know if it's the same issue as your problem, but I've fixed this before, and for me ..
# echo plugin passwordfd.so > /etc/ppp/peers/kppp
.. did the trick.
The specific error message I get is:
Jul 21 18:38:30 lap pppd[2706]: Plugin passwordfd.so loaded.
Jul 21 18:38:30 lap pppd[2706]: no device specified and stdin is not a
tty
I have /etc/ppp/peers/kppp set to plugin passwordfd.so
I have the setuid bit set on /usr/sbin/pppd and /opt/kde3/bin/kppp
This pops up just after receiving the connect from the host.
I also stopped the LAN connection.
Several years ago, I used WVDIAL successfully.
--
Jerry Feldman
Jerry Feldman wrote, On 07/22/2003 07:27 AM:
The specific error message I get is: Jul 21 18:38:30 lap pppd[2706]: Plugin passwordfd.so loaded. Jul 21 18:38:30 lap pppd[2706]: no device specified and stdin is not a tty
I have /etc/ppp/peers/kppp set to plugin passwordfd.so I have the setuid bit set on /usr/sbin/pppd and /opt/kde3/bin/kppp
Do you have kppp setup to use /dev/modem? Since it is a sofy link to the real device, like maybe /dev/ttyxxx1 or something, just set kppp to use the actual device instead of the link (or make sure /dev/modem is linked to the right device (forget the ttyxxx for a linmodem). Also, make sure your firewall isn't blocking your dialup. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Jerry Feldman wrote, On 07/22/2003 07:27 AM:
The specific error message I get is: Jul 21 18:38:30 lap pppd[2706]: Plugin passwordfd.so loaded. Jul 21 18:38:30 lap pppd[2706]: no device specified and stdin is not a tty
I have /etc/ppp/peers/kppp set to plugin passwordfd.so I have the setuid bit set on /usr/sbin/pppd and /opt/kde3/bin/kppp
Do you have kppp setup to use /dev/modem? Since it is a sofy link to the real device, like maybe /dev/ttyxxx1 or something, just set kppp to use the actual device instead of the link (or make sure /dev/modem is linked to the right device (forget the ttyxxx for a linmodem). Also, make sure your firewall isn't blocking your dialup. After playing around a bit, I was able to get the debug output. First, the kppp setup would not let me enter the actual device name (eg. /dev/ttyLT0). But, I was able to turn debug on enough. The problem was
On Tue, 22 Jul 2003 08:19:45 +0800
"Joe Morris (NTM)"
participants (3)
-
James Gibbon
-
Jerry Feldman
-
Joe Morris (NTM)