Re: Motorola SM56 - Ubuntu 11.04 ( Reply )

[Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>]

Elven,

When you reboot, first check that the modem has been activated with:
$ lsmod | grep slamr
which should list slamr
$ ls -l /dev/pts/*  /dev/ttySL0
which should show a symbolic link like:
 /dev/ttySL0 --> /dev/pts/n   , n some number

If these are OK, again try the
$ sudo wvdialconf

Report back to the List
Please attach a fresh ModemData.txt output

MarvS


On Fri, Sep 2, 2011 at 12:17 AM, Elven <magusubrazil@xxxxxxxxx> wrote:
> I followed eveyr single instruction line-by-line and everything was
> going smoothly.
>
> But when I did $sudo wvdialconf the following messages were displayed:
>
> root@ubuntu:/home/elven# $sudo wvdialconf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S1   S2   S3   S4   S5   S6   S7   S8
> Modem Port Scan<*1>: S9   S10  S11  S12  S13  S14  S15  S16
> Modem Port Scan<*1>: S17  S18  S19  S20  S21  S22  S23  S24
> Modem Port Scan<*1>: S25  S26  S27  S28  S29  S30  S31
> WvModem<*1>: Cannot get information for serial port.
> ttySL0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttySL0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttySL0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
>
>
> Sorry, no modem was detected!  Is it in use by another program?
> Did you configure it properly with setserial?
>
> Please read the FAQ at http://alumnit.ca/wiki/?WvDial
>
>
> When trying to dialout:
>
> root@ubuntu:/home/elven# $sudo wvdial
> --> WvDial: Internet dialer version 1.61
> --> Cannot get information for serial port.
> --> Initializing modem.
> --> Sending: ATZ
> --> Sending: ATQ0
> --> Re-Sending: ATZ
> --> Modem not responding.
> root@ubuntu:/home/elven#
>
> I wonder what could be causing the serial port problem, is there the
> possibility there is another driver messing it? I did a few attempts
> to make things work previously.
>