pppd connection failed

Home Forums Conduit: mLinux Model pppd connection failed

Tagged: , , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #22560
    Nicola Mondello
    Participant

    Hi all,
    I’m having problems with the pppd connection of a Conduit (MTCDTIP-H5-220L-868-OP).
    It worked when suddenly it stopped. If I use the command

    
    pppd call gsm
    

    nothing happen.
    The dmesg log is:

    
    root@mtcdt:~# dmesg
    sam9x5: ap1 eeprom read failed: -110
    at24_get_setup: found a match for eeprom at 52
    at24 1-0052: 512 byte 24c04 EEPROM, writable, 16 bytes/write
    sam9x5: read 512 bytes from ap2 eeprom
    atmel_nand 40000000.nand: Using dma0chan0 for DMA transfers.
    ONFI param page 0 valid
    ONFI flash detected
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xaa (Micron MT29F2G08ABBEAHC), 256MiB, page size: 2048, OOB size: 64
    atmel_nand 40000000.nand: ONFI params, minimum required ECC: 4 bits in 512 bytes
    atmel_nand 40000000.nand: Initialize PMECC params, cap: 4, sector: 512
    Scanning device for bad blocks
    9 ofpart partitions found on MTD device atmel_nand
    Creating 9 MTD partitions on "atmel_nand":
    0x000000000000-0x000010000000 : "NANDFlash"
    0x000000000000-0x000000040000 : "at91bootstrap"
    0x000000040000-0x0000000c0000 : "u-Boot"
    0x0000000c0000-0x000000160000 : "u-Boot Config"
    0x000000160000-0x000000200000 : "u-Boot Redundant Config"
    0x000000200000-0x000000800000 : "uImage"
    0x000000800000-0x000001000000 : "Config"
    0x000001000000-0x000001800000 : "OEM Config"
    0x000001800000-0x000010000000 : "Rootfs"
    libphy: MACB_mii_bus: probed
    macb f802c000.ethernet eth0: Cadence MACB at 0xf802c000 irq 23 (00:08:00:4a:12:0d)
    macb f802c000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=f802c000.etherne:00, irq=-1)
    PPP generic driver version 2.4.2
    PPP BSD Compression module registered
    PPP Deflate Compression module registered
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci-atmel: EHCI Atmel driver
    atmel-ehci 700000.ehci: EHCI Host Controller
    atmel-ehci 700000.ehci: new USB bus registered, assigned bus number 1
    atmel-ehci 700000.ehci: irq 31, io mem 0x00700000
    atmel-ehci 700000.ehci: USB 2.0 started, EHCI 1.00
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: EHCI Host Controller
    usb usb1: Manufacturer: Linux 3.12.27 ehci_hcd
    usb usb1: SerialNumber: 700000.ehci
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    at91_ohci 600000.ohci: AT91 OHCI
    at91_ohci 600000.ohci: new USB bus registered, assigned bus number 2
    at91_ohci 600000.ohci: irq 31, io mem 0x00600000
    usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb2: Product: AT91 OHCI
    usb usb2: Manufacturer: Linux 3.12.27 ohci_hcd
    usb usb2: SerialNumber: at91
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 3 ports detected
    rtc (null): invalid alarm value: 1900-1-1 0:0:0
    at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0
    at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver.
    i2c /dev entries driver
    at91sam9_wdt: enabled (heartbeat=15 sec, nowayout=0)
    Netfilter messages via NETLINK v0.30.
    nf_conntrack version 0.5.0 (3968 buckets, 15872 max)
    ipip: IPv4 over IPv4 tunneling driver
    gre: GRE over IPv4 demultiplexor driver
    ip_gre: GRE over IPv4 tunneling driver
    IPv4 over IPSec tunneling driver
    ip_tables: (C) 2000-2006 Netfilter Core Team
    TCP: cubic registered
    Initializing XFRM netlink socket
    NET: Registered protocol family 10
    mip6: Mobile IPv6
    sit: IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    NET: Registered protocol family 15
    l2tp_core: L2TP core driver, V2.0
    Key type dns_resolver registered
    at91_rtc fffffeb0.rtc: setting system clock to 2018-02-12 14:59:13 UTC (1518447553)
    usb 1-2: new high-speed USB device number 2 using atmel-ehci
    usb 1-2: New USB device found, idVendor=0424, idProduct=2534
    usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    hub 1-2:1.0: USB hub found
    hub 1-2:1.0: 4 ports detected
    usb 2-3: new full-speed USB device number 2 using at91_ohci
    usb 2-3: New USB device found, idVendor=04e2, idProduct=1412
    usb 2-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    usb 1-2.2: new high-speed USB device number 3 using atmel-ehci
    usb 1-2.2: New USB device found, idVendor=0403, idProduct=6014
    usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    usb 1-2.2: Product: Single RS232-HS
    usb 1-2.2: Manufacturer: FTDI
    usb 1-2.3: new high-speed USB device number 4 using atmel-ehci
    usb 1-2.3: New USB device found, idVendor=1bc7, idProduct=0021
    usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 1-2.3: Product: 6 CDC-ACM
    usb 1-2.3: Manufacturer: Telit
    usb 1-2.3: SerialNumber: 356136072959598
    jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
    VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
    devtmpfs: mounted
    Freeing unused kernel memory: 168K (c053d000 - c0567000)
    jffs2: notice: (73) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
    jffs2: notice: (73) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
    udevd[84]: starting version 182
    tmp102 0-0048: initialized
    atmel_spi f0000000.spi: version: 0x212
    atmel_spi f0000000.spi: Using dma0chan1 (tx) and dma0chan2 (rx) for DMA transfers
    atmel_spi f0000000.spi: Atmel SPI Controller at 0xf0000000 (irq 28)
    atmel_spi f0000000.spi: master is unqueued, this is deprecated
    cdc_acm 1-2.3:1.0: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.0: ttyACM0: USB ACM device
    pps_core: LinuxPPS API ver. 1 registered
    pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    atmel_spi f0004000.spi: version: 0x212
    atmel_spi f0004000.spi: Using dma1chan0 (tx) and dma1chan1 (rx) for DMA transfers
    atmel_spi f0004000.spi: Atmel SPI Controller at 0xf0004000 (irq 29)
    atmel_spi f0004000.spi: master is unqueued, this is deprecated
    cdc_acm 1-2.3:1.2: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.2: ttyACM1: USB ACM device
    cdc_acm 1-2.3:1.4: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.4: ttyACM2: USB ACM device
    pps pps0: new PPS source pps.7.-1
    pps pps0: Registered IRQ 32 as PPS source
    cdc_acm 1-2.3:1.6: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.6: ttyACM3: USB ACM device
    cdc_acm 1-2.3:1.8: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.8: ttyACM4: USB ACM device
    cdc_acm 1-2.3:1.10: This device cannot do calls on its own. It is not a modem.
    cdc_acm 1-2.3:1.10: ttyACM5: USB ACM device
    usbcore: registered new interface driver usbserial
    usbcore: registered new interface driver usbserial_generic
    usbserial: USB Serial support registered for generic
    usbcore: registered new interface driver cdc_acm
    cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
    atmel_usba_udc 500000.gadget: MMIO registers at 0xf803c000 mapped at d0dfa000
    atmel_usba_udc 500000.gadget: FIFO at 0x00500000 mapped at e1100000
    atmel_mci f0008000.mmc: version: 0x504
    atmel_mci f0008000.mmc: using dma0chan3 for DMA transfers
    usbcore: registered new interface driver ftdi_sio
    usbserial: USB Serial support registered for FTDI USB Serial Device
    ftdi_sio 1-2.2:1.0: FTDI USB Serial Device converter detected
    usb 1-2.2: Detected FT232H
    usb 1-2.2: Number of endpoints 2
    usb 1-2.2: Endpoint 1 MaxPacketSize 512
    usb 1-2.2: Endpoint 2 MaxPacketSize 512
    usb 1-2.2: Setting MaxPacketSize 512
    atmel_mci f0008000.mmc: Atmel MCI controller at 0xf0008000 irq 22, 1 slots
    vizzini 2-3:1.0: This device cannot do calls on its own. It is not a modem.
    vizzini 2-3:1.0: ttyXRUSB0: XR21v14x usb uart device
    usb 1-2.2: FTDI USB Serial Device converter now attached to ttyUSB0
    vizzini 2-3:1.2: This device cannot do calls on its own. It is not a modem.
    vizzini 2-3:1.2: ttyXRUSB1: XR21v14x usb uart device
    usbcore: registered new interface driver vizzini
    vizzini: Exar USB UART Driver for XR21V141x
    [INFO] mts-io:mts_io_init:829: init: v1.1.1
    [INFO] mts-io:mts_id_eeprom_load:754: detected board MTCDT-0.0
    [INFO] mts-io:mts_id_eeprom_load:757: sizeof: 512
    [INFO] mts-io:mts_id_eeprom_load:758: vendor-id: Multi-Tech Systems
    [INFO] mts-io:mts_id_eeprom_load:759: product-id: MTCDT-H5-210L
    [INFO] mts-io:mts_id_eeprom_load:760: device-id: 18922171
    [INFO] mts-io:mts_id_eeprom_load:761: hw-version: MTCDT-0.0
    [INFO] mts-io:mts_id_eeprom_load:768: mac-addr: 00:08:00:4A:12:0D
    [INFO] mts-io:mts_id_eeprom_load:770: imei: 356136072959598
    [INFO] mts-io:mts_id_eeprom_load:771: capa-gps: no
    [INFO] mts-io:mts_id_eeprom_load:772: capa-din: no
    [INFO] mts-io:mts_id_eeprom_load:773: capa-dout: no
    [INFO] mts-io:mts_id_eeprom_load:774: capa-adc: no
    [INFO] mts-io:mts_id_eeprom_load:775: capa-wifi: no
    [INFO] mts-io:mts_id_eeprom_load:776: capa-bluetooth: no
    [INFO] mts-io:mts_id_eeprom_load:800: uuid: 00000000000000000000000000000000
    [INFO] mts-io:load_port:653: no accessory card inserted in port 1
    [INFO] mts-io:load_port:688: accessory card 2 vendor-id: Multi-Tech Systems
    [INFO] mts-io:load_port:689: accessory card 2 product-id: MTAC-LORA-868
    [INFO] mts-io:load_port:690: accessory card 2 device-id: 18829190
    [INFO] mts-io:load_port:691: accessory card 2 hw-version: MTAC-LORA-1.0
    [INFO] mts-io:load_port:712: accessory card 2 eui: 00:80:00:00:00:00:C2:D9
    [INFO] mts-io:lora_setup:42: loading LORA accessory card in port 2
    IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    macb f802c000.ethernet eth0: link up (100/Full)
    IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    jffs2: warning: (414) jffs2_sum_write_data: Not enough space for summary, padsize = -1152
    jffs2: warning: (414) jffs2_sum_write_data: Not enough space for summary, padsize = -1412
    

    as you can see there is

    sam9x5: ap1 eeprom read failed: -110
    
    jffs2: warning: (414) jffs2_sum_write_data: Not enough space for summary, padsize = -1412
    
    

    What does it mean?
    Could it be an hardware error? Look also at these commands:

    root@mtcdt:~# mts-io-sysfs show ap1/product-id
    cat: can't open '/sys/devices/platform/mts-io/ap1/product-id': No such file or directory
    root@mtcdt:~# mts-io-sysfs show ap2/product-id
    MTAC-LORA-868

    #22563
    Jeff Hatch
    Keymaster

    Nicola,

    The two errors you have identified should be “innocuous”. The “ap1 eeprom” one is correct to the effect that there is no card plugged into accessory port #1. If there is actually a card plugged in, then there must be a contact issue or a problem with the card. The “jffs2” warning is innocuous.

    To figure out what is going wrong with the “ppp call gsm” command, you need to look in the /var/log/messages and any other pertinent log files to determine what is going wrong with the chat script. That will be the best place to start to debug the connection problem.

    Jeff

    #22565
    Nicola Mondello
    Participant

    Thank you Jeff, I fear there is a problem with the HSPA+ card .
    When I execute the pppd call gsm command no /var/log/messages file is generated.
    All this happens suddenly, before it was working properly.
    Is there any other test I could try?

    Thanks in advance.
    Nicola

    #22576
    Bruce Anderson
    Participant

    Nicola,
    At this point we recommend that you create a case in our portal.
    Please submit your requests at the Multi-Tech Online Support Portal.
    Support cases have 1st priority over forums, email and phone messages.
    https://support.multitech.com/
    The Online Support Portal provides the following features:
    1. The ability to easily submit support requests.
    2. Track and view the status of all your support cases.
    3. Receive email notifications when there are updates to your cases.
    To Create an account:
    Go to https://support.multitech.com/
    Follow the instructions for creating an account and you will receive an invitation via email.
    After you have created an account:
    Return to https://support.multitech.com/ to create your ticket.
    If you have any questions about the portal you can email us at support@multitech.com
    Support cases are monitored from 8:00 am to 5:00 pm CT, Monday through Friday.
    Thank you!
    Product Support

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.