[lug] Dialup modems and Linux

[Chan Kar Heng]

here're some things to check... they're pretty basic.. and you'd probably
know them all pretty well... but worth a try anyway.

typing atz or at&v in minicom would produce response from the modem,
with OK or the modem settings displayed respectively..

with the modem plugged in and minicom running, a call to that line
should cause the screen to display something like "RING"?

is anything else using IRQ3 on your machine? (assuming your COM2
*is* using IRQ3...)

thing is, actually, the lack of response from minicom and some other
programs seem to indicate an IRQ config problem for your modem..
but since it's on COM2... it should be pretty standard and should work fine..

last case to try.. have a friend use minicom... with a working modem of
course.. :)   and then you try dialing your friend using minicom. try the
other way too... it should work and u ought to be able to see what each
other type and more if local echo is turned on.



At 2002/09/07 06:15, you wrote:
>Justin-lists wrote:
>>Well, I took out the pci modem and put it back in the box so I can return it to the store I bought it from this weekend. I put my isa modem back in the linux box and I'm stuck at the point where minicom dials the isp and disconnects just as the tones stop. I couldn't get any further than that and logs don't tell me anything and nothing diagnostic wise gets printed to the minicom window. I put my login/passwd in pap/chap-secrets and tried all the /dev/ttyS* ports. It seems that the modem only works (in minicom) under /dev/ttyS1, which makes sense because the modem comes up as com2 in windows. However, when I try wvdial and set the modem to /dev/ttyS1 in wvdial.conf, it fails to initialize the modem. It just says modem not responding.
>
>Justin, can you post the output of "setserial -a /dev/ttyS1"? Also, change the phone number and name/pass in /etc/wvdial.conf, and post the remaining contents? If possible, you mentioned an initialization string, post that too if you can. I think Wayde is right, your modem is basically doing what it should, the only thing I can think of at the Linux side (other than data configurations like passwords) that might interfere is the wrong serial port setting.
>
>D. Stimits, stimits AT attbi.com
>
>
>>Justin
>>--
>>glow at jackmoves.com
>>
>>---------- Original Message -----------
>>From: Mr Viggy <LittleViggy at alum.manhattan.edu>
>>To: lug at lug.boulder.co.us
>>Sent: Thu, 05 Sep 2002 08:23:10 -0600
>>Subject: Re: [lug] Dialup modems and Linux
>>
>>>I'd be willing to bet dollars to donuts that the PCI card you have is a Winmodem.  I have two, actually one is my DSL router (internal)
>>>.  Both show up under lspci.  The modem *is* based on the Lucent chipset, and the Lucent "Linmodem" drivers work great with it. However, there are no drivers for the DSL router card, so that one just sits in the machine, silently...
>>>
>>>Viggy
>>>
>>>Justin-lists wrote:
>>>
>>>>Well, the pci modem is the one that I got absolutely nowhere with. I have been messing with it here now for a little bit with no luck. I can see 
>>the 
>>>>pci modem in the /proc/pci output as well as lspci. It shows up with the name that kudzu found during bootup, that is how i identified it. I have tried every /dev/ttyS* in my wvdial.conf file and nothing works. It 
>>either 
>>>>tells me "modem not responding" or "input/output error". Plus, wvdialconf will only scan /dev/ttyS0 for some reason and nothing else, of course it says there is no modems detected. 
>>>>I am giong to put the isa modem back in right now. Hopefully if I mess 
>>with 
>>>>teh authentication stuff I can make some progress with that.
>>>>
>>>>Justin
>>>>
>>>>
>>>>
>>>>
>>>>>As Wayde mentioned, for this particular modem, it sounds more and more like authentication. There may be something else in the way,
>>>>>perhaps a serial port setting meant it couldn't authenticate right even if it had the settings...but most likely I would say that it was a software response such as password that was missing in the initial exchange. You were very close to getting it working at that point.
>>>>>
>>>>>On thing you may find useful to post, in addition to all of the stuff from earlier about /proc/pci and lspci, is the output of "setserial -a /dev/modem" (or any device you are curious about that is a serial port...this "-a" by itself means it prints all of the current settings for viewing).
>>>>>
>>>>>D. Stimits, stimits AT attbi.com
>
>
>
>_______________________________________________
>Web Page:  http://lug.boulder.co.us
>Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>Join us on IRC: lug.boulder.co.us port=6667 channel=#colug