Thanks very much to those who took your time to help me out with this problem. I finally got my modem to respond.
I notice that other people were having similar problem so this is all I did: I went to Windows and found out where my modem was(COM and IRQ). So I found out it was in Com3(ttyS2 in Debian) and using IRQ 5. I typed: <setserial -a /dev/ttyS2> to find out that the kernel was looking for ttyS2 in IRQ 4. So I used this command to assign ttyS2 to IRQ 5: <setserial /dev/ttyS2 irq5> and this solved my problem. After this command I ran wvdial and I heard the modem dialing out. I'm now a happy girl thanks to all who helped from this list. I think they should have these instructions on the web in the section "Configuring PPP", or maybe another section, "Configuring your serial ports" or something. I went through the installation mannual on the web and found nothing on this issue. Again, thanks very much for all your time and input. \_\_\_\_\_\_\_\_\_\_\_\_ \_ Isabelle Poueriet \_ \_ [EMAIL PROTECTED] \_ \_ http://www.bway.net \_ \_\_\_\_\_\_\_\_\_\_\_\_ Q. How many Microsoft Engineers does it take to screw in a light bulb? A. None. They declare "darkness", the standard. On 26 Jun 1999, John Hasler wrote: > Isabelle Poueriet writes: > > This is really confusing. I thought the garbage test I was receiving when > > I typed pppd was a sign that the modem sent a signal. > > That was coming from pppd itself. > > Type 'setserial -a /dev/ttyS2' and report the results. > -- > John Hasler > [EMAIL PROTECTED] (John Hasler) > Dancing Horse Hill > Elmwood, WI >
