[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sheflug] More on the modem problem.



Looks to me like your modem just ain't talking.

What port is it on? Most distros link whatever it is to /dev/modem, but
yours might not have. Mine never gets links, because it has a nasty hack
of a firmware and doesn't respond correctly.

With KPPP there really is no need to be editing files manually. These
are all configurable through KPPP itself. Plus, the problem you describe
doesn't sound like a problem with the chat script anyway.

The equivalents to COM ports on linux are:

COM1: /dev/ttyS0
COM2: /dev/ttyS1
etc

Check to make sure you have read/write access to them. My machine has
these ports read/write to group dialup, and if you aren't in that group,
you can't dial up! 

Finally, it may be that you are looking at the right port, but something
ain't right. Get a terminal emulator (minicom is a good one) and point
it at the relevant serial port. See if typing:

ATI0
ATI1
ATI2

brings anything back.

Craig

On Thu, 2002-01-03 at 17:44, Damian Bamforth wrote:
> hi again. Thanks to Will, I can now write to my windows partition, which helps as
> far as cutting and pasting error messages goes, anyway. :)
> 
> Still no joy with the modem, though. I have changed the phone number in
> ppp.chat.to  to the correct one. I have also entered commands ATM1 and ATL3 into
> this file, and then, this making no difference,  also into the file
> etc/ppp/starter/modems/modem.
> 
> The error message contained in dev/fd1/1 is as follows :
> 
> send=accounts
> resp=200-account1/btfree
> resp=200 Okay
> send=select account1
> resp=200 Okay
> send=auth -
> resp=200 Okay
> send=select account1
> resp=200 Okay
> send=auth -
> resp=200 Okay
> message Initializing Modem...
> send=dial
> resp=200 Okay
> mesg=101 /dev/modem
> message Using modem /dev/modem
> mesg=103 Dialling via /dev/modem
> message Dialing
> mesg=100 Initializing...
> message Initializing Modem...
> mesg=406 timeout in chat script
> mesg=107 Hanging up
> KPPPWidget::disconnected()
> KPPPWidget::disconnected()
> message Hangup
> mesg=*À
> KCharset: Wrong charset!
> 
> Can anyone see anything in the above, which wouldgive a clue as to why I can't
> get my modem working? It works fine in windows (the speaker works fine as well),
> and it is a hardware modem (US Robotics).
> 
> Thanks,
> Damian
-- 

Craig Andrews

"Though my opinion may have changed, the fact that I am right has not"

___________________________________________________________________

Sheffield Linux User's Group - http://www.sheflug.co.uk . 
To unsubscribe from this list send mail to 
shef-lug-request@list.sheflug.org.uk with the word
"unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.