wvdial/pppd negotiation fails (ltmodem)

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

I installed 1.4 rc1 on a Toshiba laptop and I am trying to connect to an isp using the integrated Lucent winmodem. I am using ltmodem-8.22_alpha5, wvdial-1.53 and ppp-2.4.1. Wvdial works, identifies the prompts from the isp and starts pppd, which always dies with exit status 10 ('one or the other side did not get ip connection up'). Ltmodem, wvdial and ppp worked on this same machine under Mandrake (probably slightly older software versions). The lt-modem website says the kernel modules 'likely' will not work correctly when compiled with ggc 3.2, but they did compile cleanly and I do not think I would get as far as ppp negotiation if the modem driver did not work. Is there something about Gentoo's default ppp configuration that I have missed? I am configuring my first Gentoo system and apart from this problem I have been impressed so far.

Mikko

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

Sorry to reply to my own message. Could the problem be that pppd does not have permissions to access /dev/tts/LT0 (the winmodem device?). The permissions are

crw------- 1 root root 62, 64 Jan 1 1970 LT0

As far as I can tell, pppd is suid root, but I am still not quite sure if it will use root privileges for device access when started by wvdial. This is ls -l /usr/sbin/pppd

-r-sr-xr-x 1 root root 239928 Oct 26 01:19 /usr/sbin/pppd

Mikko

timbo · Posted: Sun Oct 27, 2002 8:32 pm Post subject:

To get wvdial and pppd to work properly I had to put the user into the tty, uucp and dialout groups.

Regards
Tim

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

I put root in groups tty, dialout and uucp and the ran wvdial as root. No luck. Seems like the phone company hangs up on me for some reason. This is what I get in the system log (now that I figured out when and where metalog was writing it):

Oct 28 21:19:52 [pppd] Using interface ppp0
Oct 28 21:19:52 [pppd] Connect: ppp0 <--> /dev/tts/LT0
Oct 28 21:19:54 [pppd] LCP terminated by peer
Oct 28 21:19:57 [pppd] Connection terminated.
Oct 28 21:19:57 [pppd] Exit.

I am trying to connect to a phone company modem bank that does not require real authentication, i.e. accepts anything as login and password. In the backup of the old Mandrake system that used to live in the laptop, wvdial had written the login and password (wvdial requires them even if it does not matter what they are) in /etc/ppp/{pap,chap}-secrets. They do not appear in these files on Gentoo. I run wvdial as root and the secrets files have rw access for root. /etc/ppp/options is simply

lock
debug

and this worked on Mandrake with the same version of pppd but and older version of wvdial (1.42 as opposed to Gentoo's 1.53). Any ideas why wvdial might not write the secrets files?

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

This thread is turning out to be my monolog. Sorry about that. Just realized that there is a file /etc/ppp/peers/wvdial-pipe than contains the following:

noauth
name wvdial

plugin passwordfd.so

defaultroute
replacedefaultroute

There is no passwordfd.so anywhere in the system. The previous Mandrake setup did not have wvdial-pipe at all, only /etc/ppp/peers/wvdial, which also present on Gentoo. This file only has 'noauth' and 'name wvdial' lines in it. What is passwordfd.so? Why is it missing?

Mikko

mhuhtala · n00b Joined: 27 Oct 2002 Posts: 16 Location: Finland

I'll finish my monolog here. I finally got wvdial to work, by putting login and password (anything in my case) in /etc/ppp/chap-secrects and /etc/ppp/pap-secrets. Wvdial is supposed to do this and I still do not know why it will not. Permissions should be ok.

Mikko

timbo · Posted: Thu Oct 31, 2002 8:16 am Post subject:

mhuhtala

Good to see it's going now. I've had to sometimes just play around with things to make them work too.

Regards
Tim

Auka · Posted: Sat Nov 02, 2002 11:14 am Post subject:

Hello!

Errm, wait! Compiling the ltmodem ebuild using GCC 3.2 really works for you?!
Sadly it doesn't for me, and also not with the tarball one can download from the official homepage! I really wonder what I am doing wrong.

I am using Gentoo 1.4rc1, latest gcc and glibc.

[...]
To begin compilation of lt_modem.o and lt_serial.o, Enter
gcc -D__KERNEL__ -I/lib/modules/2.4.19-gentoo-r9/build/include -Wall -Wstrict-prototypes -O3 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -DMODULE -DLT_VERSION=8.22a5 -DLINUX -DNO_EEPROM -DLT_SERIAL_MODULE=lt_serial -c -o ltmodem.a ltmodem.c
`-m486' is deprecated. Use `-march=i486' or `-mcpu=i486' instead.
cc1: warning: -malign-loops is obsolete, use -falign-loops
cc1: warning: -malign-jumps is obsolete, use -falign-jumps
cc1: warning: -malign-functions is obsolete, use -falign-functions

ld -r -o lt_modem.o ltmodem.a ltmdmobj.o
gcc -D__KERNEL__ -I/lib/modules/2.4.19-gentoo-r9/build/include -Wall -Wstrict-prototypes -O3 -fomit-frame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -DMODULE -DLT_VERSION=8.22a5 -DLINUX -DNO_EEPROM -DLT_SERIAL_MODULE=lt_serial -c -o serial-lt-2.4.a serial-lt-2.4.c
`-m486' is deprecated. Use `-march=i486' or `-mcpu=i486' instead.
cc1: warning: -malign-loops is obsolete, use -falign-loops
cc1: warning: -malign-jumps is obsolete, use -falign-jumps
cc1: warning: -malign-functions is obsolete, use -falign-functions
serial-lt-2.4.c:6043: unknown field `wait_key' specified in initializer
serial-lt-2.4.c:6043: warning: initialization from incompatible pointer type
make: *** [serial-lt-2.4.a] Fehler 1

Checking for driver products:
-rw-r--r-- 1 root root 559362 2002-11-02 11:55 lt_modem.o

Compilation of lt_serial.o failed,
[...]

I just even filed a bugreport! (
https://bugs.gentoo.org/show_bug.cgi?id=10089)

treehugger · n00b Joined: 08 Aug 2003 Posts: 38 Location: Florida, US

I don't know if this helps and I know this is really old now, but I couldn't compile ltmodem with ac-sources but I can with gentoo-sources.

darkcoder · Posted: Mon Sep 15, 2003 5:22 am Post subject:

the problem is not ac-sources itself, but the kernel version. There is an existing bug that prevents the hsflinmodem from compiling on kernels greater than 2.4.20. Conexant is aware of the problem, and a patch is available. While it is not available on the page, you can email them and they will send you a copy. I'm using it with ac-sources-2.4.22-ac1 without problems.
_________________
Not bleeding edge.... No pain no game :twisted: