pppd-2.4.2 + kernel-2.6.7 problem

Discussion in 'Linux Networking' started by Dimitris Mandalidis, Jul 15, 2004.

  1. Hello,
    I 'm trying to migrate from 2.4 kernel to 2.6 series, and after a successful
    compile I ran into this problem; I run pppd to initiate a connection with my ISP
    but when I tried to do this with 2.6.7 kernel, the modem (external USRobotics
    33.600) didn't make the usual <click> after ATDT, which seems to me that it
    actually chat(8) cannot speak to the modem. Then it keeps waiting for CONNECT
    until timeout. I use the *very same* ppp options and chatscript as I did with
    2.4.26 kernel (and pppd-2.4.2), so I think that it 'd be unnecessary to send you
    my configuration files. Does anyone has a clue on this? I suspect that I have
    misconfigured the kernel.

    Thanks in advance
    D.

    pppd-2.4.2
    kernel-2.6.7
    Slackware-10.0
    ..config :

    CONFIG_PPP=y
    CONFIG_PPP_ASYNC=y
    CONFIG_PPP_DEFLATE=y
    CONFIG_PPP_BSDCOMP=y
     
    Dimitris Mandalidis, Jul 15, 2004
    #1
    1. Advertisements

  2. make menuconfig
    Linux Kernel Configuration
    Device Drivers --->
    Character devices --->
    Serial drivers --->
    <*> 8250/16550 and compatible serial support

    ?
     
    Clifford Kite, Jul 15, 2004
    #2
    1. Advertisements

  3. On Thu, 15 Jul 2004 17:25:21 -0500, Clifford Kite wrote
    It is also included, with minicom-2.0.0 everything goes just fine.

    D.
     
    Dimitris Mandalidis, Jul 16, 2004
    #3
  4. Okay.

    Configure chat with the -v option and pppd with the debug option, add

    daemon.*;local2.* /var/log/ppp.log

    to /etc/syslog.conf, and do "killall -HUP syslogd" to cause syslogd to
    reread syslog.conf.

    Then try to connect and afterwards post an exact copy of the ppp.log,
    including timestamps, so that, hopefully, we will have a better idea
    of just what is going on.
     
    Clifford Kite, Jul 16, 2004
    #4
  5. On Fri, 16 Jul 2004 17:46:54 -0500, Clifford Kite wrote
    I 've already done this but logs show absolutely nothing, the problem seems to
    be in chat because when sending ATZ I get OK as expected but when sending
    ATDTxxxxxxxx, the line doesn't open, chat waits for CONNECT till the time-out
    expires.

    D.
     
    Dimitris Mandalidis, Jul 17, 2004
    #5
  6. If you succeed with minicom on the same computer then there's something
    wrong with the chat configuration. I don't know what "the line doesn't
    open" means. If you won't post the log messages then I can't help you.

    Maybe a psychic reads this group and will help.

    -- Clifford Kite Email: "echo |rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* In his wisdom RMS decided that people need no man pages when they can
    use GNU's beautiful info system.
    Unfortunately, everybody I know greatly prefers man pages.
    - From the man-pages-1.55/man1/README */
     
    Clifford Kite, Jul 17, 2004
    #6
  7. On Sat, 17 Jul 2004 12:09:39 -0500, Clifford Kite wrote
    I told that the logs are of no importance but if you insist :

    Jul 16 19:51:25 lizard chat[1388]: timeout set to 60 seconds
    Jul 16 19:51:25 lizard chat[1388]: abort on (BUSY)
    Jul 16 19:51:25 lizard chat[1388]: abort on (NO CARRIER)
    Jul 16 19:51:25 lizard chat[1388]: abort on (NO DIALTONE)
    Jul 16 19:51:25 lizard chat[1388]: abort on (ERROR)
    Jul 16 19:51:25 lizard chat[1388]: send (ATZ^M)
    Jul 16 19:51:25 lizard chat[1388]: expect (OK)
    Jul 16 19:51:25 lizard chat[1388]: ATZ^M^M
    Jul 16 19:51:25 lizard chat[1388]: OK
    Jul 16 19:51:25 lizard chat[1388]: -- got it
    Jul 16 19:51:25 lizard chat[1388]: send (ATDT8962588888^M)
    Jul 16 19:51:25 lizard chat[1388]: timeout set to 75 seconds
    Jul 16 19:51:25 lizard chat[1388]: expect (CONNECT)
    Jul 16 19:51:25 lizard chat[1388]: ^M
    Jul 16 19:52:40 lizard chat[1388]: alarm
    Jul 16 19:52:40 lizard chat[1388]: Failed

    Debug is turned both in chat and pppd. 'The line doesn't open' means that I
    don't hear the <click> from my modem after ATDT. I still believe that the
    problem lurks within chat and pppd but I don't know where and most of all I
    don't know how to fix it.

    D.
     
    Dimitris Mandalidis, Jul 18, 2004
    #7
  8. I found something that might help. I 've programmed my modem to have its speaker
    turned off. My original chatscript was :

    TIMEOUT 60
    ABORT BUSY
    ABORT 'NO CARRIER'
    ABORT 'NO DIALTONE'
    ABORT ERROR
    '' ATZ
    OK ATDT8962588888
    TIMEOUT 75
    CONNECT

    And I changed in order to hear something to solve this problem :

    TIMEOUT 60
    ABORT BUSY
    ABORT 'NO CARRIER'
    ABORT 'NO DIALTONE'
    ABORT ERROR
    '' ATZ
    OK ATM2
    OK ATL3
    OK ATDT8962588888
    TIMEOUT 75
    CONNECT

    And I saw this to my logs :

    Jul 18 03:28:45 lizard chat[1412]: timeout set to 60 seconds
    Jul 18 03:28:45 lizard chat[1412]: abort on (BUSY)
    Jul 18 03:28:45 lizard chat[1412]: abort on (NO CARRIER)
    Jul 18 03:28:45 lizard chat[1412]: abort on (NO DIALTONE)
    Jul 18 03:28:45 lizard chat[1412]: abort on (ERROR)
    Jul 18 03:28:45 lizard chat[1412]: send (ATZ^M)
    Jul 18 03:28:45 lizard chat[1412]: expect (OK)
    Jul 18 03:28:45 lizard chat[1412]: ATZ^M^M
    Jul 18 03:28:45 lizard chat[1412]: OK
    Jul 18 03:28:45 lizard chat[1412]: -- got it
    Jul 18 03:28:45 lizard chat[1412]: send (ATM2^M)
    Jul 18 03:28:45 lizard chat[1412]: expect (OK)
    Jul 18 03:28:45 lizard chat[1412]: ^M

    Then the script was waiting and I did as (root) # echo "OK" > /dev/modem
    (/dev/tts/0) and it worked just fine! It's easy to modify connect pppd
    command to add this, but I still don't know where's the problem and why it
    worked like this.

    D.
     
    Dimitris Mandalidis, Jul 18, 2004
    #8
  9. Okay. The reference to /dev/tts/0 triggered my memory but it was
    still not easy to find kernel configuration change(s) that *might*
    fix the problem. After the change(s), you should change the sym-link
    /dev/modem to point to /dev/ttyS0 (or ttyS?), if it doesn't already -
    I never used the devfs device filesystem.

    Kernel 2.6.4
    ------------
    make menuconfig
    Linux Kernel Configuration
    File systems --->
    Pseudo filesystems --->
    [*] /proc file system support
    [ ] /dev file system support (OBSOLETE)
    .... more stuff not configured here ...

    Note that the obsolete devfs is NOT configured. I *think* this
    also causes UNIX98 (ttypX is replaced by pts/X) to be automatically
    configured - anyway I couldn't find an explicit configuration option
    for UNIX98. So you'll likely also need to add

    none /dev/pts devpts gid=5,mode=0660 0 0

    to /etc/fstab and mount it (or reboot), after adding the /dev/pts
    directory:

    drwxr-xr-x 2 root root 0 Jul 1 09:15 /dev/pts/

    Check for UNIX98 PTY configuration with "less .config" in the top
    source directory and search for UNIX98. You should see

    #
    # Non-8250 serial port support
    #
    CONFIG_SERIAL_CORE=y
    CONFIG_UNIX98_PTYS=y

    You *might* also need sysctl (always configured here) support too:

    Linux Kernel Configuration
    General setup --->
    [*] Sysctl support

    Now, something else in the kernel that you may need (since it hung when
    attempting AT configuration of audio from the modem):

    Linux Kernel Configuration
    Device Drivers --->
    Input device support --->
    [*] Misc
    <*> PC Speaker support

    Note that there are a lot of "might"s, "should"s, ect., above. YMMV with
    the 2.6.7 kernel, or perhaps I'm just plain guessing wrong about what's
    causing the problem(s).
     
    Clifford Kite, Jul 18, 2004
    #9
  10. On Sun, 18 Jul 2004 06:50:56 -0500, Clifford Kite wrote
    Here is my .config file. Do you see anything weird? (I removed devfs support)

    CONFIG_X86=y
    CONFIG_MMU=y
    CONFIG_UID16=y
    CONFIG_GENERIC_ISA_DMA=y
    CONFIG_CLEAN_COMPILE=y
    CONFIG_STANDALONE=y
    CONFIG_BROKEN_ON_SMP=y
    CONFIG_SWAP=y
    CONFIG_SYSVIPC=y
    CONFIG_BSD_PROCESS_ACCT=y
    CONFIG_SYSCTL=y
    CONFIG_AUDIT=y
    CONFIG_AUDITSYSCALL=y
    CONFIG_LOG_BUF_SHIFT=14
    CONFIG_IKCONFIG=y
    CONFIG_IKCONFIG_PROC=y
    CONFIG_KALLSYMS=y
    CONFIG_FUTEX=y
    CONFIG_EPOLL=y
    CONFIG_IOSCHED_NOOP=y
    CONFIG_IOSCHED_AS=y
    CONFIG_IOSCHED_DEADLINE=y
    CONFIG_IOSCHED_CFQ=y
    CONFIG_MODULES=y
    CONFIG_MODULE_UNLOAD=y
    CONFIG_OBSOLETE_MODPARM=y
    CONFIG_KMOD=y
    CONFIG_X86_PC=y
    CONFIG_MK7=y
    CONFIG_X86_GENERIC=y
    CONFIG_X86_CMPXCHG=y
    CONFIG_X86_XADD=y
    CONFIG_X86_L1_CACHE_SHIFT=7
    CONFIG_RWSEM_XCHGADD_ALGORITHM=y
    CONFIG_X86_WP_WORKS_OK=y
    CONFIG_X86_INVLPG=y
    CONFIG_X86_BSWAP=y
    CONFIG_X86_POPAD_OK=y
    CONFIG_X86_GOOD_APIC=y
    CONFIG_X86_INTEL_USERCOPY=y
    CONFIG_X86_USE_PPRO_CHECKSUM=y
    CONFIG_X86_USE_3DNOW=y
    CONFIG_PREEMPT=y
    CONFIG_X86_UP_APIC=y
    CONFIG_X86_UP_IOAPIC=y
    CONFIG_X86_LOCAL_APIC=y
    CONFIG_X86_IO_APIC=y
    CONFIG_X86_TSC=y
    CONFIG_X86_MCE=y
    CONFIG_NOHIGHMEM=y
    CONFIG_MTRR=y
    CONFIG_HAVE_DEC_LOCK=y
    CONFIG_PM=y
    CONFIG_ACPI_BOOT=y
    CONFIG_APM=y
    CONFIG_PCI=y
    CONFIG_PCI_GOANY=y
    CONFIG_PCI_BIOS=y
    CONFIG_PCI_DIRECT=y
    CONFIG_PCI_MMCONFIG=y
    CONFIG_PCI_NAMES=y
    CONFIG_ISA=y
    CONFIG_BINFMT_ELF=y
    CONFIG_BINFMT_AOUT=y
    CONFIG_BINFMT_MISC=y
    CONFIG_PARPORT=m
    CONFIG_PARPORT_PC=m
    CONFIG_PARPORT_PC_CML1=m
    CONFIG_PARPORT_1284=y
    CONFIG_PNP=y
    CONFIG_ISAPNP=y
    CONFIG_BLK_DEV_FD=m
    CONFIG_BLK_DEV_LOOP=m
    CONFIG_IDE=y
    CONFIG_BLK_DEV_IDE=y
    CONFIG_BLK_DEV_IDEDISK=y
    CONFIG_BLK_DEV_IDECD=m
    CONFIG_BLK_DEV_IDESCSI=y
    CONFIG_IDE_GENERIC=y
    CONFIG_BLK_DEV_IDEPCI=y
    CONFIG_IDEPCI_SHARE_IRQ=y
    CONFIG_BLK_DEV_GENERIC=y
    CONFIG_BLK_DEV_IDEDMA_PCI=y
    CONFIG_IDEDMA_PCI_AUTO=y
    CONFIG_BLK_DEV_ADMA=y
    CONFIG_BLK_DEV_VIA82CXXX=y
    CONFIG_BLK_DEV_IDEDMA=y
    CONFIG_IDEDMA_AUTO=y
    CONFIG_SCSI=y
    CONFIG_BLK_DEV_SR=y
    CONFIG_BLK_DEV_SR_VENDOR=y
    CONFIG_CHR_DEV_SG=y
    CONFIG_SCSI_QLA2XXX=y
    CONFIG_NET=y
    CONFIG_PACKET=m
    CONFIG_PACKET_MMAP=y
    CONFIG_UNIX=y
    CONFIG_NET_KEY=m
    CONFIG_INET=y
    CONFIG_NETFILTER=y
    CONFIG_IP_NF_CONNTRACK=m
    CONFIG_IP_NF_FTP=m
    CONFIG_IP_NF_IRC=m
    CONFIG_IP_NF_TFTP=m
    CONFIG_IP_NF_AMANDA=m
    CONFIG_IP_NF_QUEUE=m
    CONFIG_IP_NF_IPTABLES=m
    CONFIG_IP_NF_MATCH_LIMIT=m
    CONFIG_IP_NF_MATCH_IPRANGE=m
    CONFIG_IP_NF_MATCH_MAC=m
    CONFIG_IP_NF_MATCH_PKTTYPE=m
    CONFIG_IP_NF_MATCH_MARK=m
    CONFIG_IP_NF_MATCH_MULTIPORT=m
    CONFIG_IP_NF_MATCH_TOS=m
    CONFIG_IP_NF_MATCH_RECENT=m
    CONFIG_IP_NF_MATCH_ECN=m
    CONFIG_IP_NF_MATCH_DSCP=m
    CONFIG_IP_NF_MATCH_AH_ESP=m
    CONFIG_IP_NF_MATCH_LENGTH=m
    CONFIG_IP_NF_MATCH_TTL=m
    CONFIG_IP_NF_MATCH_TCPMSS=m
    CONFIG_IP_NF_MATCH_HELPER=m
    CONFIG_IP_NF_MATCH_STATE=m
    CONFIG_IP_NF_MATCH_CONNTRACK=m
    CONFIG_IP_NF_MATCH_OWNER=m
    CONFIG_IP_NF_FILTER=m
    CONFIG_IP_NF_TARGET_REJECT=m
    CONFIG_IP_NF_NAT=m
    CONFIG_IP_NF_NAT_NEEDED=y
    CONFIG_IP_NF_TARGET_MASQUERADE=m
    CONFIG_IP_NF_TARGET_REDIRECT=m
    CONFIG_IP_NF_TARGET_NETMAP=m
    CONFIG_IP_NF_TARGET_SAME=m
    CONFIG_IP_NF_NAT_IRC=m
    CONFIG_IP_NF_NAT_FTP=m
    CONFIG_IP_NF_NAT_TFTP=m
    CONFIG_IP_NF_NAT_AMANDA=m
    CONFIG_IP_NF_MANGLE=m
    CONFIG_IP_NF_TARGET_TOS=m
    CONFIG_IP_NF_TARGET_ECN=m
    CONFIG_IP_NF_TARGET_DSCP=m
    CONFIG_IP_NF_TARGET_MARK=m
    CONFIG_IP_NF_TARGET_CLASSIFY=m
    CONFIG_IP_NF_TARGET_LOG=m
    CONFIG_IP_NF_TARGET_ULOG=m
    CONFIG_IP_NF_TARGET_TCPMSS=m
    CONFIG_IP_NF_ARPTABLES=m
    CONFIG_IP_NF_ARPFILTER=m
    CONFIG_IP_NF_ARP_MANGLE=m
    CONFIG_IP_NF_TARGET_NOTRACK=m
    CONFIG_IP_NF_RAW=m
    CONFIG_XFRM=y
    CONFIG_NETDEVICES=y
    CONFIG_DUMMY=m
    CONFIG_PPP=m
    CONFIG_PPP_ASYNC=m
    CONFIG_PPP_DEFLATE=m
    CONFIG_PPP_BSDCOMP=m
    CONFIG_INPUT=y
    CONFIG_INPUT_MOUSEDEV=y
    CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
    CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
    CONFIG_INPUT_EVDEV=y
    CONFIG_SOUND_GAMEPORT=y
    CONFIG_SERIO=y
    CONFIG_SERIO_I8042=y
    CONFIG_INPUT_KEYBOARD=y
    CONFIG_KEYBOARD_ATKBD=y
    CONFIG_INPUT_MOUSE=y
    CONFIG_MOUSE_PS2=y
    CONFIG_INPUT_MISC=y
    CONFIG_INPUT_PCSPKR=y
    CONFIG_INPUT_UINPUT=y
    CONFIG_VT=y
    CONFIG_VT_CONSOLE=y
    CONFIG_HW_CONSOLE=y
    CONFIG_SERIAL_8250=m
    CONFIG_SERIAL_8250_NR_UARTS=2
    CONFIG_SERIAL_8250_EXTENDED=y
    CONFIG_SERIAL_8250_SHARE_IRQ=y
    CONFIG_SERIAL_CORE=m
    CONFIG_UNIX98_PTYS=y
    CONFIG_LEGACY_PTYS=y
    CONFIG_LEGACY_PTY_COUNT=256
    CONFIG_PRINTER=m
    CONFIG_PPDEV=m
    CONFIG_HW_RANDOM=m
    CONFIG_NVRAM=m
    CONFIG_RTC=m
    CONFIG_GEN_RTC=m
    CONFIG_GEN_RTC_X=y
    CONFIG_AGP=m
    CONFIG_AGP_ATI=m
    CONFIG_DRM=y
    CONFIG_DRM_RADEON=m
    CONFIG_VGA_CONSOLE=y
    CONFIG_DUMMY_CONSOLE=y
    CONFIG_SOUND=m
    CONFIG_SND=m
    CONFIG_SND_TIMER=m
    CONFIG_SND_PCM=m
    CONFIG_SND_RAWMIDI=m
    CONFIG_SND_SEQUENCER=m
    CONFIG_SND_SEQ_DUMMY=m
    CONFIG_SND_OSSEMUL=y
    CONFIG_SND_MIXER_OSS=m
    CONFIG_SND_PCM_OSS=m
    CONFIG_SND_SEQUENCER_OSS=y
    CONFIG_SND_RTCTIMER=m
    CONFIG_SND_DUMMY=m
    CONFIG_SND_VIRMIDI=m
    CONFIG_SND_AC97_CODEC=m
    CONFIG_SND_ENS1371=m
    CONFIG_USB=y
    CONFIG_USB_EHCI_HCD=y
    CONFIG_USB_UHCI_HCD=y
    CONFIG_USB_AUDIO=m
    CONFIG_USB_HID=y
    CONFIG_USB_HIDINPUT=y
    CONFIG_USB_HIDDEV=y
    CONFIG_EXT2_FS=y
    CONFIG_EXT3_FS=y
    CONFIG_EXT3_FS_XATTR=y
    CONFIG_EXT3_FS_POSIX_ACL=y
    CONFIG_EXT3_FS_SECURITY=y
    CONFIG_JBD=y
    CONFIG_FS_MBCACHE=y
    CONFIG_FS_POSIX_ACL=y
    CONFIG_ISO9660_FS=m
    CONFIG_JOLIET=y
    CONFIG_FAT_FS=m
    CONFIG_VFAT_FS=m
    CONFIG_PROC_FS=y
    CONFIG_PROC_KCORE=y
    CONFIG_SYSFS=y
    CONFIG_DEVPTS_FS_XATTR=y
    CONFIG_DEVPTS_FS_SECURITY=y
    CONFIG_RAMFS=y
    CONFIG_MSDOS_PARTITION=y
    CONFIG_NLS=m
    CONFIG_NLS_DEFAULT="iso8859-1"
    CONFIG_NLS_CODEPAGE_737=m
    CONFIG_NLS_ISO8859_1=m
    CONFIG_NLS_ISO8859_7=m
    CONFIG_NLS_UTF8=m
    CONFIG_EARLY_PRINTK=y
    CONFIG_X86_FIND_SMP_CONFIG=y
    CONFIG_X86_MPPARSE=y
    CONFIG_CRC32=y
    CONFIG_ZLIB_INFLATE=m
    CONFIG_ZLIB_DEFLATE=m
    CONFIG_X86_BIOS_REBOOT=y
    CONFIG_X86_STD_RESOURCES=y
    CONFIG_PC=y

    D.
     
    Dimitris Mandalidis, Jul 18, 2004
    #10
  11. Dimitris Mandalidis

    Moe Trin Guest

    And I think this is the problem. What all does "Reset to Stored Profile 0"
    do? I think that one of the stored commands you have is "Q1" which turns
    OFF the reply/results codes. I'd suggest reading the modem manual, and
    finding the recommended init string, which is _usually_ AT&F AT&F0 or
    maybe AT&F1, and use that in place of ATZ.
    That would help ;-)
    So you sent ATZ, and it was echoed back to you - the command was
    accepted, giving the OK result code. Now, what ever was the stored profile
    takes over from here.
    Was the "ATM2^M" echoed back to you? (That's controlled by the ATE[01]
    commnd.>
    I suspect that your problem is the stored profile that you get with the
    modem reset command. If you check the modem manual, you may find a
    command to report what the "stored profile" is. Unfortunetly, this
    varies WIDELY between manufacturers. For one example, US Robotics uses

    In n=0 Product Code
    n=1 Checksum
    n=2 RAM Test
    n=3 Product ID string
    n=4 Current Settings
    n=5 NVRAM Settings
    n=6 Link Diagnostics
    n=7 Product Configuration
    n=9 PnP Enumeration Screen
    n=11 Link Diagnostics

    and if (in minicom) I give the command

    ati5
    U.S. Robotics Sportster 56000 Fax NVRAM Settings...

    Template Y0

    DIAL=TONE B0 E1 F1 L2 M1 Q0 V1 X4
    BAUD=38400 PARITY=N WORDLEN=8

    &A3 &B1 &C1 &D2 &G0 &H1 &I0 &K1 &M4 &N0
    &P0 &R2 &S0 &T5 &U0 &Y1

    S00=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07=060
    S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=000
    S19=000 S21=010 S22=017 S23=019 S25=005 S27=000 S28=008
    S29=020 S30=000 S31=128 S32=002 S33=000 S34=000 S35=000
    S36=014 S38=000 S39=000 S41=000 S42=000

    Template Y1

    and so on


    Old Guy
     
    Moe Trin, Jul 18, 2004
    #11
  12. support)

    I can only point out things that are different *and* which seem to me
    to have at least a slim chance of being part of the problem.
    I don't have SERIAL_8250_EXTENDED configured. Doing so displays extra
    options. One is

    [ ] Support for sharing serial interrupts (NEW)

    which if answered "y" then configures:
    I don't want an interrupt used by my modem's serial device to be shared
    with anything else.
    I don't have LEGACY_PTYS configured. The reason it's not is that I don't
    know it might affect the UNIX98_PTYS. Minor thing, SERIAL_CORE=y is the
    way I chose to configure that here.
    So far it seems that the modem accepts ATZ and promptly replies with OK,
    but not so for the next AT command.

    At least you seem to have a workaround with

    echo "OK" > /dev/modem

    which is good since I can't think of anything else to suggest.

    [ I will add that I tried going to 2.6.6 a few weeks ago and found that
    pppd filtering with the active-filter option was broken in that kernel,
    so I'm staying put for awhile. ]

    Good Luck!
     
    Clifford Kite, Jul 18, 2004
    #12
  13. On Sun, 18 Jul 2004 14:14:29 -0500, Moe Trin wrote
    Profile 0 includes all the manufactory default commands + M0. Q0 is stored
    instead of Q1.
    USRobotics Sportster Voice 33600 Fax NVRAM Settings...

    Template Y0

    DIAL=PULSE B0 E1 F1 M0 Q0 V1 X3
    BAUD=38400 PARITY=N WORDLEN=8

    &A3 &B1 &C1 &D2 &H1 &I0 &K1
    &M4 &N0 &P0 &R2 &S0 &T5 &U0 &Y1

    S00=000 S02=043 S03=013 S04=010 S05=008 S06=005 S07=060
    S08=002 S09=006 S10=014 S11=070 S12=050 S13=000 S15=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 S36=014
    S38=000 S39=010 S40=000 S41=000 S42=000

    But I think that modem settings are not a problem, they work just fine like this
    for about 10 years :)

    D.
     
    Dimitris Mandalidis, Jul 18, 2004
    #13
  14. Finally it got fixed! It seems that there was a problem at profile0
    configuration, I don't know why because as I already said I use this profile for
    about 10 years. However now I use AT&F2X3M0 for initialisation and everything
    goes fine.

    Thank you all for answering,
    D.
     
    Dimitris Mandalidis, Jul 18, 2004
    #14
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.