Re: gammu-detect on ARM

João M. S. Silva <[email protected]>
Newsgroups gmane.linux.drivers.gammu
Message-ID <[email protected]>
Hi Gilberto,

dmesg shows nothing relevant, except maybe:

[    3.695865] 1c29c00.serial: ttyS4 at MMIO 0x1c29c00 (irq = 43, 
base_baud = 1500000) is a U6_16550A

There are no messages when I turn on the module, since it's just a 
serial connection.

$ wvdialconf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

WvModem<*1>: Cannot set information for serial port.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 115200 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
WvModem<*1>: Cannot set information for serial port.
ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S5


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

João M. S. Silva

On 11/06/2015 03:28 AM, gilberto dos santos alves wrote:
> Hi. Please post your dmesg contents and what log wvdialconf says!
>
> 2015-11-05 22:42 GMT-02:00 João M. S. Silva
> <[email protected] <mailto:[email protected]>>:
>
>     Hi again,
>
>     Anyone using gammu on an ARM platform?
>
>     I'm now experimenting with the SIM800 module in Ubuntu 14.04.3 on an ARM
>     platform with a serial connection (no USB adapter). gammu-detect does
>     not detect the modem:
>
>     $ gammu-detect
>     ; Configuration file generated by gammu-detect.
>     ; Please check The Gammu Manual for more information.
>
>     [gammu]
>     device = /dev/ttyS5
>     name = Phone on serial port 5
>     connection = at
>
>     opening socket: No such device
>
>     The result /dev/ttyS5 is wrong. The modem is in /dev/ttyS4. If I use the
>     following configuration file, gammu works:
>
>     $ cat gammu.conf
>     [gammu]
>     device = /dev/ttyS4
>     name = Phone on serial port 4
>     connection = at
>
>     So, why can't gammu auto-detect the modem, but it works if I manually
>     configure the correct serial port?
>
>     Also, wvdial does not detect any modem and it does not work with a
>     correct configuration file that I copied from the Intel platform.
>
>     Any difference for an ARM platform?
>
>     --
>     João M. S. Silva
>
>     ------------------------------------------------------------------------------
>     _______________________________________________
>     Gammu-users mailing list -
>     https://lists.sourceforge.net/lists/listinfo/gammu-users
>
>
>
>
> --
> gilberto dos santos alves
> +55(11)9-8646-5049
> sao paulo - sp - brasil
>
>
>
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Gammu-users mailing list - https://lists.sourceforge.net/lists/listinfo/gammu-users
>

------------------------------------------------------------------------------
_______________________________________________
Gammu-users mailing list - https://lists.sourceforge.net/lists/listinfo/gammu-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.