[lug] looking for strings,
carl.wagner at level3.com
Thu May 24 15:16:12 MDT 2001
I assume you are saying that you are getting a "No Carrier" message back.
If that is the case, does your ISP support 14.4?
If it is an issue where you are not getting the message but some cryptic code,
you should look for "verbose result codes" ([Xnn] or [Vn]).
So you did a
You may want to check out:
at &v should show you your modem settings.
Jeff Howell wrote:
> Sounds to me like the modem is broken. Perhaps a bent pin. Might try
> plugging a phone into the lineout jack and see if you get a tone just to
> test that.
> for a in `your_base`
> chown us:us $a
> exit 0
> Rob Mohr wrote:
> > I can't solve a no carrier modem issue.
> > I read the HOWTO and then deleved into the BLUG archives. About ten pages
> > of info, the one tid bit that I used was to change out a V4 to a V1
> > setting on the initial dial string.
> > Everything is via minicom. And I can step through checks ATI0-ATI20 with
> > most coming back OK and one number kicking out Parallel 16550 EXT HYB
> > V32BIS V42BIS. The AT&8 kicks out the Active register, the Stored 1 & 2
> > register settings. Below that load of info are four slots for telephone
> > numbers. 0 emtpy 1=2305336 2= empty 3=3etmpy and I don't know where that
> > number applies, I did not key it into the dialer or elsewhere. This page
> > then ends with OK.
> > I did a google search on "NO CARRIER" +modem +linux and did not seem to
> > pull up anything of use save for much discussion about setserial.
> > I do suspect I have an issue with the initial strings, but I did not find
> > any good info on how to change the initialization strings.
> > The modem is date stamped AST Research 1994, which should mean that it is
> > not a winmodem issue. It is 14.4K; a real pokey modem.
> > Is there an O'Reilley book that might offer a few leads? My Linux books
> > just have a bare one page on minicom, and I don't have the modem manual.
> > One last thing, I did wipe out the locked file entry thinking that might
> > be causing a snag, but then I put it back, /var/lockfile.
> > Don't spend too much brain effort here, as the utility of a working modem,
> > on this 486 box, it not a critial matter to me. It is just the exercise
> > of getting it right; working.
> > eof
> > _______________________________________________
> > Web Page: http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
More information about the LUG