usr sportster pro not always properly detected

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

On Sat, Oct 23, 1999 at 08:20:45PM +0200, Marc SCHAEFER wrote:
> Erik Hovland <ehovland@thorin.instanet.com> wrote:
> > v2.2.13pre17. Current debug level in mgetty.config and voice.conf is 5.
> 
> Please augment it (I think it's 8).

You asked for it. I cranked voice.conf to 6 and mgetty.config to 8.

> > Very rarely I see this beautiful message in the vg_ttyS1.log:
> > 10/23 09:10:36 yS1  detecting voice modem type
> > 10/23 09:10:36 yS1   voice command: 'ATI9' -> ''
> > 10/23 09:10:37 yS1   voice command: 'ATI' -> ''
> > 10/23 09:10:37 yS1  US Robotics detected
> 
> so we can see what is happening.

I can't get it to properly detect reliably so all I can give you is the
case where it fails:
10/23 11:44:44 yS1  detecting voice modem type
10/23 11:44:44 yS1    vgetty: ATE0
10/23 11:44:44 yS1    serial port: OK
10/23 11:44:45 yS1   voice command: 'ATI9' -> ''
10/23 11:44:45 yS1    vgetty: ATI9
10/23 11:44:45 yS1    serial port: ATI9
10/23 11:44:45 yS1    serial port: (1.0USR3020\\Modem\PNPC107\U.S. Robotics 56K Voice Pro EXT)FF
10/23 11:44:45 yS1    serial port: OK
10/23 11:44:46 yS1   voice command: 'ATI' -> ''
10/23 11:44:46 yS1    vgetty: ATI
10/23 11:44:46 yS1    serial port: ATI
10/23 11:44:46 yS1    serial port: 5601
10/23 11:44:46 yS1    serial port: OK
10/23 11:44:46 yS1  no voice modem detected

Hope it helps some.

> NB: once this happens, does it recover if you kill vgetty ?

I only see proper detection at boot, maybe. After that no matter what I do
to stop and start vgetty it doesn't seem to detect properly. I was lucky to
catch the previous good detection at all. And it has properly detected maybe
4 times since I started working on this issue (over 3 weeks ago).

E