problem with elsa microlink and mgetty (debian 2.1)

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Sun, Apr 25, 1999 at 04:34:33PM +0200, Stephan Witoszynskyj wrote:
> 
> i'm trying to use my elsa microlink tqv (33k) modem with mgetty under
> debian linux 2.1. actually i had it working on another machine before
> under SuSe linux 4.1.
> 
> after mgetty sends ATI to the modem, i just get Warning: got alarm signal!
> mdm_read_byte: read returned -1: Interrupted system call. 
[..]

Now let's look at the log file...

> 04/25 16:00:30 yS2  locking the line
> 04/25 16:00:30 yS2   makelock(ttyS2) called
> 04/25 16:00:30 yS2   do_makelock: lock='/var/lock/LCK..ttyS2'
> 04/25 16:00:30 yS2   lock made
> 04/25 16:00:31 yS2   tio_get_rs232_lines: status: RTS DTR
> 04/25 16:00:31 yS2  WARNING: DSR is off - modem turned off or bad cable?

This might hint at a bad serial cable, or it might be harmless.

> 04/25 16:00:31 yS2  lowering DTR to reset Modem

Try switching that off in mgetty.config ("toggle-dtr no").

> 04/25 16:00:31 yS2   tss: set speed to 38400 (017)
> 04/25 16:00:31 yS2   tio_set_flow_control( HARD )
> 04/25 16:00:31 yS2   waiting for line to clear (VTIME), read:
> 04/25 16:00:32 yS2  send: \dATQ0V1H0[0d]
> 04/25 16:00:32 yS2  waiting for ``OK''
> 04/25 16:00:32 yS2   got: [00]
> 04/25 16:00:52 yS2  timeout in chat script, waiting for `OK'

Somehow your serial port doesn't "see" this AT command and modem echo,
but...

> 04/25 16:00:52 yS2  init chat timed out, trying force-init-chat
> 04/25 16:00:52 yS2  send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
> 04/25 16:00:56 yS2  waiting for ``OK''
> 04/25 16:00:56 yS2   got: ATQ0V1H0[0d][0d][0a]OK ** found **

24 seconds later, the command IS there, and the OK response is there as 
well.  This is strange.

> 04/25 16:01:01 yS2   force-init succeeded, retrying init-chat
> 04/25 16:01:01 yS2   waiting for line to clear (VTIME), read: [0d][0a]
> 04/25 16:01:01 yS2  send: \dATQ0V1H0[0d]
> 04/25 16:01:02 yS2  waiting for ``OK''
> 04/25 16:01:02 yS2   got: ATQ0V1H0[0d]
> 04/25 16:01:21 yS2    CND: OKATQ0V1H0[0d][0a]OK ** found **
> 04/25 16:01:21 yS2  send: AT[0d]
> 04/25 16:01:21 yS2  waiting for ``OK''
> 04/25 16:01:21 yS2   got: [0d]
> 04/25 16:01:21 yS2    CND: OK[0a]AT[0d]
> 04/25 16:01:41 yS2    CND: AT[0d][0a]OK ** found **

Now modem and computer are back in sync.

> 04/25 16:01:41 yS2  mdm_send: 'ATI'
> 04/25 16:01:41 yS2    got:[0d][0a]
> 04/25 16:01:51 yS2  Warning: got alarm signal!
> 04/25 16:01:51 yS2  mdm_read_byte: read returned -1: Interrupted system call
> 04/25 16:01:51 yS2  mdm_get_line: cannot read byte, return: Interrupted
> system call
> 04/25 16:01:51 yS2   mdm_identify: string '<ERROR>'

There does not seem to be an answer here...

> 04/25 16:01:51 yS2  mdm_identify: can't get modem ID
> 04/25 16:01:51 yS2  mdm_send: 'AT+FCLASS=?'
> 04/25 16:01:51 yS2    got:ATI[0d]
> 04/25 16:02:01 yS2   mdm_gis: string 1: 'ATI'
> 04/25 16:02:01 yS2    got:[0d][0a]282[0d] 
> 04/25 16:02:01 yS2   mdm_gis: string 2: '282'
> 04/25 16:02:01 yS2    got:[0a][0d][0a]OK[0d]

... but it just comes "later".

My guess would be that you have a problem with your serial port...

>   tty00 at 0x03f8 (irq = 4) is a 16450
>   tty01 at 0x02f8 (irq = 3) is a 16450
>   tty02 at 0x03e8 (irq = 4) is a 16450A 
>   tty03 at 0x02e8 (irq = 3) is a 16550A

... and this seconds this.  You MUST NOT put more than one serial port on
the same IRQ line.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de