Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?

From: Basil Chupin (blchupin_at_tpg.com.au)
Date: 09/28/03

  • Next message: Ricardo Wagemaker: "Re: [SLE] Wireless" 
    Date: Sun, 28 Sep 2003 19:56:34 +1000
To: suse-linux-e@suse.com

    bernd@covenantmail.net wrote:
    > HELP!!!
    >
    > Please save me from my stupidity!
    >
    > My modem no longer works in linux at all!
    >
    > If your suggestions
    > help me, then I won't have go into the long gory details.
    > Because I'm working from that dark place called windoze,
    > right now, because I'm sick, and also working on a couple
    > hours of sleep, I've had to write this e-mail 3 times
    > already. It keeps getting shorter each time.
    >
    > I was running some tests on the init strings. I do not
    > have a functioning kppp at present, and therefore can't
    > use its' terminal program. I also don't have any other
    > terminal program to directly send commands to the modem
    > from the keyboard. Sooo... To run these tests I have been
    > editing a -new- copy of wvdial.conf and running wvdial
    > from the shell.
    >
    > Long story really short...
    >
    > Here's what I think is going on. I am now getting errors
    > from the output of wvdial (using the tried and true -saved-
    > copy of wvdial.conf). I am told that there are errors with
    > the name servers and www.suse.de can't be found!?! So now
    > I can't use wvdial or kinternet to connect.
    >
    > I swear I didn't program the wrong init string in the
    > modem, because I am able to get it to work in windoze.
    > I went exploring in yast, but I aborted all areas that
    > I was clueless about. Well, apparently not all!!!
    >
    > PLEASE Save Me!!!
    >
    > Bernd

    I can understand the feeling, but PLEASE do NOT panic!

    Let's start from the beginning, and sort things out.

    Let me first say that I remember you using wvdialconf to configure your
    wvdial.conf file, right? Well, from what I have found a few minutes ago
    is that wvdialconf creates the *.conf file in the wrong place- the
    wvdial.conf file should be the one found in /etc and not the one
    wvdialconf creates in /usr/bin.

    Also, it needs stating that kinternet uses the info you supply when you
    first install SuSE and are setting-up your modem and your ISP. We'll
    come back to this in a minute because you are going to check that all
    this info is (still) correct. (You can check what info is being used in
    kinternet by right-clicking on the kinternet icon (the little
    socket/plug in the bottom-right corner of your desktop) and selecting
    Settings/View Configuration.

    I seem to remember that you are using SuSE v8.1 and what I found with
    it, when I was running it, was that the wvdial.conf file was NOT created
    properly during the install of the modem when installing SuSE. You have
    to physically edit /etc/wvdial.conf file; if you don't, it remains
    totally devoid of any info to be used by wvdial.

    The other thing, kppp is configured on its own, but it does "take" some
    of the info it needs from the info you provide when setting up the modem
    when installing SuSE.

    Now, let's "start from the beginning" and set your modem/ISP connection up.

    Left click on the SuSE Work Menu icon (bottom left desktop, looks like a
    green world globe with a lightning bolt thru it), then select
    Administration->Yast2->Modules->Network Devices->Modem. Now you are at
    the stage where you were when first installing SuSE, and you are about
    to install and configure your modem and the connection to your ISP.

    "Pretend" that you are installing SuSE and go thru the screens you see
    and check that the information shown is the correct one to get you
    connected to your ISP and that the modem settings are OK.

    For example, the top box on the first screen you see should read "Other
    (not detected)" and the bottom box should show "Modem configured as ppp0
    with provider <nameofyourISP>.

    If this is correct click on CHANGE to get on to the next screen(s) to
    check the info there.

    For the modem settings you should have -

    Modem Device - /dev/modem; Tone Dialling; Speaker ON; Detect Dial Tone;
      Baud Rate - 115200; Init 1- AT &F &C1 &D2 E1 S0=0; Init 2- ATZ.

    Re your ISP settings, apart from its name and other details re your
    logon name and password, make sure that MODIFY DNS is selected; that
    DIAL ON DEMAND is NOT selected; that STUPID MODE and ACTIVATE FIREWALL
    are both selected; and set IDLE TIMEOUT to 1200 (you will remember that
    I told you to use 1200 in the /etc/ntp.conf file some time ago).

    Complete checking/setting the details and then click on FINISH to exit
    and save (any) changes. This now has your kinternet correctly configured
    and ready for use.

    BUT now, EDIT the file /etc/wvdial.conf and type in the same details you
    just filled in (above) with ONE EXCEPTION: in wvdial.conf instead of
    using 115200 for the BAUD RATE you must type in 57600 because this is
    the baud rate with which you will be connecting to your ISP (the 115200
    is the rate at which the modem and your computer communicate with each
    other; don't mixed these baud rates up).

    Now you can start kppp and see if it now talks to your modem (kppp does
    not work in V8.2 I discovered about 1/2 hour ago :-(, and I don't know
    why); make sure that the device used is /dev/modem. Check that the
    initialising string is as above.

    I'll stop here and let you do all this.

    One comment. Use the HELP (the red/white lifesaver icon) and do a search
    on MODEM. You will find a bit of info including one which states to rem
    out LCP-ECHOINTERVAL and LCP-ECHO-FAILURE in the /etc/ntp.conf file (I
    already told you to do this some time ago).

    Cheers. 

    -- 
Sound that shatters silence is called noise. Sound that enhances silence 
is called music.
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Ricardo Wagemaker: "Re: [SLE] Wireless"

    Relevant Pages

    • RE: [opensuse] 3G Cards And Vodaphone South Africa
      ... Well I checked with the ISP helpdesk last night all the settings seems ... The modem responds. ... 'Compression Control Protocol' received. ...
      (SuSE)
    • Re: opening email
      ... Check your settings in Tools>Accounts>Mail>Properties. ... Make sure your modem is working. ... Contact your ISP. ... If there is a detailed error ...
      (microsoft.public.windows.inetexplorer.ie6_outlookexpress)
    • Re: Dial-up connection
      ... > I had the same problem after installing SuSE 10 as an update over 9.2 ... So I fired up minicom, and within minutes determined both systems got it ... tinkering like I did to see if the modem is still alive somewhere. ... Pardon any bogus email addresses in place for spambots. ...
      (comp.os.linux.misc)
    • Re: Dial-up connection
      ... >>I had the same problem after installing SuSE 10 as an update over 9.2 ... look for are lines like these that show all your serial devices: ... and look for the IRQ of your modem. ... you can line up the modem from its IRQ to the correct serial device. ...
      (comp.os.linux.misc)
    • Re: Routing Question
      ... > Just want to confirm the settings! ... > modem, and all other traffic through the 10.0.0.2 modem. ... Just the return packets from lan host requests? ... ISP or two different ISPs? ...
      (comp.os.linux.networking)