[lug] Dialup modems and Linux

Thu Sep 5 08:48:31 MDT 2002

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

--
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
> >>
> >>
> >>>Justin
> >>>
> >>>--
> >>>glow at jackmoves.com
> >>>
> >>>
> >>>---------- Original Message -----------
> >>>From: "J. Wayde Allen" <wallen at lug.boulder.co.us>
> >>>To: lug at lug.boulder.co.us
> >>>Sent: Wed, 4 Sep 2002 13:24:54 -0600 (MDT)
> >>>Subject: Re: [lug] Dialup modems and Linux
> >>>
> >>>
> >>>
> >>>>On Wed, 4 Sep 2002, Justin-lists wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hmm, I'll check the /proc/pci tonight as well as try some of the other
> >>>>>tools. I will also try the other ttyS* ports. Thanks for all the help.
> >>>>
> >>>>I skimmed your original post pretty fast so don't remember what all you
> >>>>have done.  I think you said that you tried something like minicom 
> >>>>and that the modem dialed and connected?  This is a place I like to 
> >>>>start just to verify that the modem system can control the modem and 
> >>>>connect to the server.  It also lets you see what the modem server 
> >>>>types back to you.  This way you can verify that the connection is 
> >>>>made, whether or not it is noisy and/or error prone, and what should 
> >>>>go into the chat script.
> >>>>
> >>>>(Personally, I think that the growing reliance on configuration 
> >>>>wizards is starting to make Linux a bit harder rather than easier to 
> >>>>use.  It is a double edged sword.)
> >>>>
> >>>>- Wayde
> >>>> (wallen at lug.boulder.co.us)
> >>>>
> >>>>_______________________________________________
> >>>>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
> >>>
> >>>------- End of Original Message -------
> >>>
> >>>_______________________________________________
> >>>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
> >>>
> >>
> >>_______________________________________________
> >>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
> > 
> > ------- End of Original Message -------
> > 
> > _______________________________________________
> > 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
> > 
> > .
> > 
> 
> _______________________________________________
> 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
------- End of Original Message -------