cracking winmodem issues in FC2

[Matthew Saltzman]

On Fri, 27 Aug 2004, Gabriel Mititica wrote:

> Regarding ALSA suggestion:
>
> I don't think it works for me although I enabled it in
> the kernel and rebuilt the slmodemd with ALSA support
>
> slmodemd -a
>
> error: alsa setup: cannot open playback device 'hw:1':
> No such device error: cannot setup device `hw:1'
>
> my sound dev is ALI not INTEL Modem is Toshiba as I
> mentioned not INTEL/AMD as shown in make *config

I have the Intel modem, so this is outside my experience.

>
> I tried different slmodemd /dev/tty* without success
>
> Just slmodemd
> error: mdm setup: cannot open dev `/dev/slamr0': No
> such device error: cannot setup device `/dev/slamr0'

OK If you can't use the ALSA driver then you must insmod the slamr driver.

>
> minicom: trying to dial in without result (no other
> complaints)
>
> modem_test: (w/o slamr inserted)
>
> <072.503789> SmartLink Soft Modem: version 2.9.9 Aug
> 27 2004 11:34:06
> <072.504004> modemA: startup modem...
> <072.504086> modemA: update termios...
> main: created modemA: /dev/pts/3
> SmartLink Soft Modem: version 2.9.9 Aug 27 2004
> 11:34:06
> <072.504531> SmartLink Soft Modem: version 2.9.9 Aug
> 27 2004 11:34:06
> <072.504640> modemB: startup modem...
> <072.526984> modemB: update termios...
> main: created modemB: /dev/pts/4
>
> modem_test: (w/ slamr inserted)
>
> SmartLink Soft Modem: version 2.9.9 Aug 27 2004
> 11:34:06
> <132.944302> SmartLink Soft Modem: version 2.9.9 Aug
> 27 2004 11:34:06
> <132.944477> modemA: startup modem...
> <132.944530> modemA: update termios...
> main: created modemA: /dev/pts/3
> SmartLink Soft Modem: version 2.9.9 Aug 27 2004
> 11:34:06
> <132.944780> SmartLink Soft Modem: version 2.9.9 Aug
> 27 2004 11:34:06
> <132.944844> modemB: startup modem...
> <132.944875> modemB: update termios...
> main: created modemB: /dev/pts/4
>
> after that is not doing anything else and I have to
> Ctrl+C (both cases)

I'm not sure what modem_test does.  I've not been able to get it to do
anything other than what you report.

>
> log output kppp:
>
> ATZ
> OK
> ATM1L1
> OK
> ATDT96048224477
> NO CARRIER
> ERROR

OK This looks promising.  If you get "OK" when you enter "AT" commands,
then the driver is installed and the daemon is talking to the device.  It
looks like it dialed the number but didn't contact a modem on the other
end.

Can you dial with Minicom?  Make sure to configure Minicom to point to the
/dev/ttySL0 device (or whatever slmodemd tells you it is).  I use the 115K
interface speed and N-8-1 format.  At least you can enter AT commands from
the keyboard and watch the progress in real time that way.  You may even
be able to make the modem audible and listen to the call's progress.

>
> Any input? Thanks, Gabriel
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
>
>
>
>

-- 
		Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs