Re: Re: thanx
Posted by
Ray Henry
on 2002-04-21 13:30:00 UTC
Hi Hoyt
From: batwings@...
<s>
number of bits, and parity. They will never understand what they are
expected to be called. It is Linux that needs to know where the channel is
to the modem. So in your dialer program you tell Linux that the modem is
connected to /dev/ttyS0 (MS COM0) and it WILL look for it there.
Internal modems need to be the non "winmodem" kind or you will have a bitch
of a time finding the correct drivers for it.
If you are using KDE then the dialer program is probably kppp. You can test
this by starting a terminal and typing in kppp <enter> and you should see the
front page of the dialer. Select setup and new if you are not already there,
and enter the isp info. Unless your isp is pretty special you can use
dynamic IP address, default gateway, and enter it's domain name in dns. The
ok button should get you back to configuration.
Select device and enter /dev/ttyS0 or /dev/ttyS1 depending on which serial
port you have it connected to. I don't trust /dev/modem because sometimes
the install doesn't set up the correct links. Select the modem tab. Set the
volume where you want it and press querry modem. If you see "for modem" and
ready" answers then you know that Linux sees the modem and can communicate
with it. If you don't, or you get a "sorry, the modem doesn't respond"
message you know that you need to change the device name. When you get kppp
talking to the modem you can press okay and try it using the connect button.
Autoconfig doesn't always do what it's supposed to do.
Hope this helps
Ray
From: batwings@...
<s>
>Setserial reports the usual things on ttyS0 amd ttyS1: 16550 UART, theExternal modems don't need to understand much at all. A bit about speed,
>right ports and the right IRQs. Modem is configged to the right IRQ on
>jumper but seems to have no COM setting jumpers. However, it was recognized
>during bootup.
>>No. Your modem should be, "ttyS0", or possibly on an older system, "cua1".
>>Type:
>>
>> man setserial
>Yeah I did that and it's not clear if I want to change anything or not. How
>do I make modem understand what /dev/tty?? or whatever, it is expected to be?
number of bits, and parity. They will never understand what they are
expected to be called. It is Linux that needs to know where the channel is
to the modem. So in your dialer program you tell Linux that the modem is
connected to /dev/ttyS0 (MS COM0) and it WILL look for it there.
Internal modems need to be the non "winmodem" kind or you will have a bitch
of a time finding the correct drivers for it.
If you are using KDE then the dialer program is probably kppp. You can test
this by starting a terminal and typing in kppp <enter> and you should see the
front page of the dialer. Select setup and new if you are not already there,
and enter the isp info. Unless your isp is pretty special you can use
dynamic IP address, default gateway, and enter it's domain name in dns. The
ok button should get you back to configuration.
Select device and enter /dev/ttyS0 or /dev/ttyS1 depending on which serial
port you have it connected to. I don't trust /dev/modem because sometimes
the install doesn't set up the correct links. Select the modem tab. Set the
volume where you want it and press querry modem. If you see "for modem" and
ready" answers then you know that Linux sees the modem and can communicate
with it. If you don't, or you get a "sorry, the modem doesn't respond"
message you know that you need to change the device name. When you get kppp
talking to the modem you can press okay and try it using the connect button.
Autoconfig doesn't always do what it's supposed to do.
Hope this helps
Ray
On Sunday 21 April 2002 11:04 am, you wrote:
> Message: 13
> Date: Sun, 21 Apr 2002 07:42:49
> From: batwings@...
> Subject: Re: thanx
>
> At 07:47 PM 4/20/02 -0700, you wrote:
<s>
> I must not be making myself clear. I'm using the dialer setup that came
> with Linux RH 7.1, whatever that is. During its autoconfig option, it tries
> EVERY port in sequence. It recognizes a modem on NONE of them. However, the
> modem is recognised during bootup, which gives me a screen asking if to
> config it, which I affirm. I have also set the port directly in the little
> window in dialer setup, also with no effect. Modem is a good one, and
> anyway this is the second modem I've tried. Any more clues?
Discussion Thread
Marty Escarcega
2002-04-11 16:40:08 UTC
FS: Bridgeport CNC Mill, Tempe, AZ
batwings@i...
2002-04-11 19:32:18 UTC
linux box
Bill Vance
2002-04-11 20:22:59 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Brian Pitt
2002-04-11 20:56:28 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Stan Stocker
2002-04-11 20:59:46 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Jon Elson
2002-04-11 23:48:13 UTC
Re: [CAD_CAM_EDM_DRO] linux box
batwings@i...
2002-04-12 04:51:55 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Matt Shaver
2002-04-12 08:00:53 UTC
Re: [CAD_CAM_EDM_DRO] linux box
batwings@i...
2002-04-12 19:16:53 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Jon Elson
2002-04-12 22:48:55 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Ray Henry
2002-04-13 12:12:04 UTC
Re: Re: linux box
batwings@i...
2002-04-14 03:51:06 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: linux box
Brian Pitt
2002-04-14 12:03:21 UTC
Re: [CAD_CAM_EDM_DRO] Re: Re: linux box
Ray Henry
2002-04-14 13:03:43 UTC
Re: Re: Re: Re: linux box
batwings@i...
2002-04-14 18:41:16 UTC
linux box
batwings@i...
2002-04-14 18:41:16 UTC
linux box
Alan Marconett KM6VV
2002-04-14 19:03:01 UTC
Re: [CAD_CAM_EDM_DRO] linux box
batwings@i...
2002-04-15 04:51:37 UTC
Re: [CAD_CAM_EDM_DRO] linux box
Alan Marconett KM6VV
2002-04-15 11:58:07 UTC
Re: [CAD_CAM_EDM_DRO] linux box
batwings@i...
2002-04-16 20:13:14 UTC
intersting day
Bill Vance
2002-04-16 21:55:27 UTC
Re: [CAD_CAM_EDM_DRO] intersting day
Jon Elson
2002-04-16 22:59:53 UTC
Re: [CAD_CAM_EDM_DRO] intersting day
Brian Pitt
2002-04-16 23:28:33 UTC
Re: [CAD_CAM_EDM_DRO] intersting day
n4onl
2002-04-17 02:19:34 UTC
Re: intersting day
batwings@i...
2002-04-17 06:36:33 UTC
thanx
Ray Henry
2002-04-17 07:07:02 UTC
Re: intersting day
batwings@i...
2002-04-17 11:43:13 UTC
curve fitting
Bill Vance
2002-04-17 12:41:19 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Unterhausen Umberto
2002-04-17 13:47:55 UTC
Re: thanx
batwings@i...
2002-04-18 04:47:07 UTC
Re: [CAD_CAM_EDM_DRO] thanx
batwings@i...
2002-04-18 11:19:18 UTC
Re: [CAD_CAM_EDM_DRO] Re: intersting day
Bill Vance
2002-04-18 11:45:14 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Jon Elson
2002-04-19 01:56:01 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Paul
2002-04-19 02:50:28 UTC
Re: [CAD_CAM_EDM_DRO] Realtime and EMC (was intersting day)
ballendo
2002-04-19 06:52:53 UTC
Re: curve fitting
imserv1
2002-04-19 08:22:52 UTC
Re: curve fitting
batwings@i...
2002-04-19 16:51:34 UTC
Re: [CAD_CAM_EDM_DRO] Re: curve fitting
batwings@i...
2002-04-20 16:58:58 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Bill Vance
2002-04-20 19:46:56 UTC
Re: [CAD_CAM_EDM_DRO] thanx
batwings@i...
2002-04-21 04:43:25 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Jon Elson
2002-04-21 10:13:51 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Bill Vance
2002-04-21 10:34:58 UTC
Re: [CAD_CAM_EDM_DRO] thanx
Ray Henry
2002-04-21 13:30:00 UTC
Re: Re: thanx
batwings@i...
2002-04-22 05:16:16 UTC
Re: [CAD_CAM_EDM_DRO] thanx