US Robotics 56K Voice Faxmodem

[Jeff LaCoursiere]

Is it a 16550A UART?  Perhaps you are driving it too fast if not.  Try a
lower baud rate.

j

On Mon, 5 Nov 2001, Jon Mercer wrote:

> Jeff & James,
> 
> Thanks, I've retried all permutations (including changing the COM and IRQ on
> the card), there has to be something else as well.
> 
> I've checked 'dmesg | grep irq' for conflicts, even changed the jumpers on
> the card; and tried both hardware and software flow control. Oh, and I
> recompiled the kernel with support for only sio0 and sio1, just to be on the
> safe side. It's still screwey. It should be a relief really - at least it is
> consistent! I think I'm still looking for that one little piece of config
> that isn't right - somewhere...
> 
> I've had a 'watch' session snooping on /dev/cuaa01, interestingly,
> everything that goes to the modem from the ppp - term session gets echoed,
> but nothing at all comes back. Correct me if I am wrong, but is this default
> behaviour? I would have thought that if watch were doing a two way thing
> then everything would come back as it was - instead of looking at a one way
> flow. Still - if you know different...
> 
> I'll re-read the sio(4) page tomorrow, in case there is something I've
> missed in the kernel config - which looks like this - just in case anyone
> spots something they think is obvious:
> 
>     # Serial (COM) ports
>     device          sio0    at isa? port IO_COM1 flags 0x10 irq 4
>     device          sio1    at isa? port IO_COM2 irq 3
>     #device         sio2    at isa? disable port IO_COM3 irq 5
>     #device         sio3    at isa? disable port IO_COM4 irq 9
> 
>     # To make an SMP kernel, the next two are needed
>     options         SMP                     # Symmetric MultiProcessor
> Kernel
>     options         APIC_IO                 # Symmetric (APIC) I/O
> 
>     device          isa
>     device          eisa
>     device          pci
> 
> Anyone think of somthing I'm missing?
> 
> Cheers,
> 
> Jon
> 
> 
> ----- Original Message -----
> From: "Jeff LaCoursiere" <jeff at jeff.net>
> To: "Jon Mercer" <jon at trojan-heroes.co.uk>
> Cc: <freebsd-users at uk.freebsd.org>
> Sent: Monday, November 05, 2001 9:11 PM
> Subject: Re: US Robotics 56K Voice Faxmodem
> 
> 
> >
> > I'm using a Sportster 56K FLash (not voice), but a few of my settings seem
> > to be different, for what its worth:
> >
> > U.S. Robotics Sportster Flash 56000 Settings...
> >    B0  E1  F1  M1  Q0  V1  X4  Y0
> >    SPEED=115200  PARITY=N  WORDLEN=8
> >    DIAL=TONE   OFF LINE
> >    &A3  &B1  &C1  &D2  &H1  &I0  &K1
> >    &M4  &N0  &R2  &S0  &T5  &U0  &Y1
> >    S00=000  S01=000  S02=043  S03=013  S04=010  S05=008  S06=004
> >    S07=060  S08=002  S09=006  S10=014  S11=072  S12=050  S13=000
> >    S15=000  S16=000  S18=000  S19=000  S21=010  S22=017  S23=019
> >    S25=005  S27=001  S28=008  S29=020  S30=000  S31=128  S32=002
> >    S33=000  S34=000  S35=000  S36=014  S38=000  S39=011  S40=000
> >    S41=006
> >
> > If you are getting truncated data back, however, I would suspect a flow
> > control or maybe an IRQ sharing problem?
> >
> > j
> >
> > On Mon, 5 Nov 2001, Jon Mercer wrote:
> >
> > > Folks,
> > >
> > > Is anyone successfully using a US Robotics 56K Voice Faxmodem with
> FreeBSD?
> > > If so how??? I seem to have a problem with the control codes coming back
> > > from it, which obviously is a bit of a showstopper for any chat scripts
> I
> > > can write. This is the output from the userland ppp terminal option, and
> all
> > > the settings look fine. But, the final OK gets truncated, and, no
> characters
> > > are output to screen unless they get a keystroke to prompt them out,
> which I
> > > can't believe is a feature.
> > >
> > >     ati40
> > >     U.S. Robotics 56K Voice INT Settings...
> > >
> > >        B0  E1  F1  L2  M1  Q0  V1  X4  Y3
> > >        SPEED=115200  PARITY=N  WORDLEN=8
> > >        DIAL=TONE    OFF LINE
> > >
> > >        &A3  &B1  &C1  &D2  &H1  &I0  &K1
> > >        &M4  &N0  &R2  &S0  &T5  &U0  &Y1
> > >
> > >        S00=000  S01=003  S02=043  S03=013  S04=010  S05=008  S06=004
> > >        S07=060  S08=002  S09=006  S10=014  S11=070  S12=050  S13=000
> > >        S15=000  S16=000  S18=000  S19=000  S21=010  S22=017  S23=019
> > >        S25=005  S27=001  S28=008  S29=020  S30=000  S31=128  S32=002
> > >        S33=000  S34=000  S35=000  S36=014  S38=000  S39=011  S40=000
> > >        S41=004  S42=000
> > >
> > >        LAST DIALLED #:
> > >
> > >     O
> > >
> > > Any ATDT commands get dialled correctly, and I can change settings in
> the
> > > modem fine with any of the AT commands, but nothing seems to be coming
> back
> > > from the modem correctly, so I don't think it is a hardware/hardware
> jumper
> > > config problem.
> > >
> > > All I can think of now that this is a problem with /dev/cuaa1
> major/minor
> > > numbers. Can anyone confirm this, or point out the error of my
> reasoning???
> > >
> > > Any helpful suggestions/workarounds gratefully received,
> > >
> > > Jon Mercer
> > >
> > >
> > > ------ FreeBSD UK Users' Group  -  Mailing List ------
> > > http://listserver.uk.freebsd.org/mailman/listinfo/freebsd-users
> > >
> >
> 
>