On Thursday 14 February 2002 02:27 pm, [EMAIL PROTECTED] wrote: > I just reinstalled Debian 2.2.r3 from disk, and now I can't get any > internet programs to connect to the modem (which was working fine before). > Mozilla gives "<web address> can't be found" error message and Lynx gives > "unable to connect to remote host" error message. Modem never dials.
if any web oriented app tells you it can't provide what it should when you know it should, that a dns resolution problem, which would definitely occur in the event of the modem not making a connection. > > - Pppconfig autodetects the modem on /dev/ttyS2, and the pppconfig file has > been set to accept demand dialing; if pppconfig detects the modem with no errors, then the modem is functional. > - setserial has the modem set to irq 5 (runs on boot); > - the modem itself is jumpered to irq 5; > - wvdialconf autodetects the modem on /dev/ttyS2; > - wvdial actually works and connects the modem to the net, although PAP > authentication seems to have trouble with the secrets file; > - output on boot includes the following lines: > > 307 ? S< 0:00 /usr/sbin/diald > Starting http cache proxy server:wwwoffled. > WWWOFFLE NOW IN AUTODIAL MODE. > > I've followed the instructions on /usr/doc/diald/README.Debian by > configuring /etc/diald/connect and making a /dev/modem symlink to > /dev/ttyS2. I've done everything I can think of that I did the first time > around to get the system set up for internet access, but it isn't working. > how do you know that the modem isn't dialing? > Changes to my system from the way I had it configured before: > > - I now use "debian" as my hostname instead of "localhost" it would be better to use a more distinctly personal name for your machine, like k-debian, or any variation that renders any address referencing to your box easily understood. > > - I now have parport and parport-autodetect compiled into kernel. Parport- > autodetect finds my printer on irq 7, so there shouldn't be an irq > conflict; however > > - syslog is giving the following messages: > insmod: /lib/modules/2.2.17/misc/lp.o: invalid parameter parm_irq > insmod: /lib/modules/2.2.17/misc/lp.o: insmod char-major-6 failed > modprobe: modprobe: Can't locate module sound-slot-0 > modprobe: modprobe: Can't locate module sound-service-0-3 these messages are not related to the connection problem. manually configure wvdial (/etc/wvdial.conf) for your connection without forcing it to rely on any additional secrets file and run that in a console. do a ps aux|grep ppp* and post the results. have you configured /etc/resolv.conf in order to reach your isp's nameservers?
