hardware modem won't connect - PPP

This is a discussion on hardware modem won't connect - PPP ; I have never gotten this modem to work with Linux before. It is a USRobotics Sportster Vi external modem. It will dial, even authenticate. But when the music stops it just sits there, waiting for God to touch it or ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: hardware modem won't connect

  1. hardware modem won't connect

    I have never gotten this modem to work with Linux before.
    It is a USRobotics Sportster Vi external modem. It will dial, even authenticate. But when the music stops it just sits there, waiting for God to touch it or something.

    This is the output of tail -s 3 -f /var/log/messages

    Jan 24 18:17:20 localhost ifup-ppp: pppd started for ppp0 on /dev/ttyS0 at 115200
    Jan 24 18:17:20 localhost pppd[4505]: pppd 2.4.1 started by root, uid 0
    Jan 24 18:17:21 localhost wvdial[4520]: WvDial: Internet dialer version 1.53 Jan 24 18:17:21 localhost wvdial[4520]: Initializing modem. Jan 24 18:17:21 localhost wvdial[4520]: Sending: ATZ Jan 24 18:17:22 localhost wvdial[4520]: ATZ Jan 24 18:17:22 localhost kernel: spurious 8259A interrupt: IRQ7. <----What the weiner is this!?
    Jan 24 18:17:22 localhost wvdial[4520]: OK Jan 24 18:17:22 localhost wvdial[4520]: Modem initialized. Jan 24 18:17:22 localhost wvdial[4520]: Sending: ATDT722-0447 Jan 24 18:17:22 localhost wvdial[4520]: Waiting for carrier. Jan 24 18:17:22 localhost wvdial[4520]: ATDT722-0447 Jan 24 18:17:40 localhost wvdial[4520]: CONNECT 26400/ARQ Jan 24 18:17:40 localhost wvdial[4520]: Carrier detected. Chatmode finished. Jan 24 18:17:40 localhost pppd[4505]: Serial connection established.
    Jan 24 18:17:40 localhost pppd[4505]: Using interface ppp0
    Jan 24 18:17:40 localhost pppd[4505]: Connect: ppp0 <--> /dev/ttyS0
    Jan 24 18:17:40 localhost /etc/hotplug/net.agent: assuming ppp0 is already up
    Jan 24 18:18:11 localhost pppd[4505]: LCP: timeout sending Config-Requests
    Jan 24 18:18:11 localhost pppd[4505]: Connection terminated.
    Jan 24 18:18:11 localhost /etc/hotplug/net.agent: NET unregister event not supported
    Jan 24 18:18:12 localhost pppd[4505]: Hangup (SIGHUP)
    Jan 24 18:18:12 localhost pppd[4505]: Exit.

    So what does it all mean? Why does it die mysteriously?

    I hope you can understand my modem, because I sure as hell don't.

    Thanks!
    Alex Pressť

    --

    You gotta get rid of the sp4mm3d and r3m0ve in my email address.
    GP0503.sp4mm3d@trytel.r3m0ve.com

  2. Re: hardware modem won't connect

    Lord_Alex wrote:
    > I have never gotten this modem to work with Linux before.
    > It is a USRobotics Sportster Vi external modem. It will dial, even authenticate. But when the music stops it just sits there, waiting for God to touch it or something.


    Modems don't authenticate.

    > This is the output of tail -s 3 -f /var/log/messages


    > Jan 24 18:17:20 localhost ifup-ppp: pppd started for ppp0 on /dev/ttyS0 at 115200
    > Jan 24 18:17:20 localhost pppd[4505]: pppd 2.4.1 started by root, uid 0
    > Jan 24 18:17:21 localhost wvdial[4520]: WvDial: Internet dialer version 1.53 Jan 24 18:17:21 localhost wvdial[4520]: Initializing modem. Jan 24 18:17:21 localhost wvdial[4520]: Sending: ATZ Jan 24 18:17:22 localhost wvdial[4520]: ATZ Jan 24 18:17:22 localhost kernel: spurious 8259A interrupt: IRQ7. <----What the weiner is this!?


    Using ATZ alone is a poor way to initialize a modem unless you know what
    profile it sets. Some Sportsters need AT&F1.

    I haven't a clue about the kernel message.

    > Jan 24 18:17:22 localhost wvdial[4520]: OK Jan 24 18:17:22 localhost wvdial[4520]: Modem initialized. Jan 24 18:17:22 localhost wvdial[4520]: Sending: ATDT722-0447 Jan 24 18:17:22 localhost wvdial[4520]: Waiting for carrier. Jan 24 18:17:22 localhost wvdial[4520]: ATDT722-0447 Jan 24 18:17:40 localhost wvdial[4520]: CONNECT 26400/ARQ Jan 24 18:17:40 localhost wvdial[4520]: Carrier detected. Chatmode finished. Jan 24 18:17:40 localhost pppd[4505]: Serial connection established.
    > Jan 24 18:17:40 localhost pppd[4505]: Using interface ppp0
    > Jan 24 18:17:40 localhost pppd[4505]: Connect: ppp0 <--> /dev/ttyS0
    > Jan 24 18:17:40 localhost /etc/hotplug/net.agent: assuming ppp0 is already up
    > Jan 24 18:18:11 localhost pppd[4505]: LCP: timeout sending Config-Requests
    > Jan 24 18:18:11 localhost pppd[4505]: Connection terminated.
    > Jan 24 18:18:11 localhost /etc/hotplug/net.agent: NET unregister event not supported
    > Jan 24 18:18:12 localhost pppd[4505]: Hangup (SIGHUP)
    > Jan 24 18:18:12 localhost pppd[4505]: Exit.


    > So what does it all mean? Why does it die mysteriously?


    The most likely reason is that the remote host hasn't been coaxed
    into starting PPP. If you haven't tried it then configure wvdial with
    Stupid mode = 1, and then add the pppd option "user ",
    and configure /etc/ppp/{pap,chap}-secrets (man pppd) - unless wvdial
    does that for you when Stupid mode = 1.

    Also check out

    http://www.theory.physics.ubc.ca/ppp-linux.html

    Finally, when you post log messages to a newsgroup please don't wrap
    several message lines into one.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* They that can give up essential liberty to obtain a little temporary
    safety deserve neither liberty nor safety." Benjamin Franklin */


+ Reply to Thread