Re: Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?
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
On Saturday 27 September 2003 10:11, wrote:
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.
This may have nothing to do with the modem working or not, but simply your setting for using dhcp on this interface may be wrong. In any event kinternet (and probably wvdial) simply try to look up www.suse.de (or what ever you set it to look up) as a simple means of knowing if dns is working. Check your setting for dhcp and see if they are being set properly when you conntect. (But first watch the log to see if you are connecting at all). -- _____________________________________ John Andersen
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.
On 09/28/2003 05:56 PM, Basil Chupin wrote:
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.
Actually, kppp works great (my favorite). I did need to add: /usr/sbin/pppd root.dialout 4755 to my /etc/permissions.local file, as kppp required pppd to be suid root. Using 8.2, kde 3.1.4. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Joe Morris (NTM) wrote:
On 09/28/2003 05:56 PM, Basil Chupin wrote:
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.
Actually, kppp works great (my favorite). I did need to add: /usr/sbin/pppd root.dialout 4755 to my /etc/permissions.local file, as kppp required pppd to be suid root. Using 8.2, kde 3.1.4.
Aah, thanks for this. I will try it out and see if it has the same intended effect here - normally such things seem not to work here for some peculiar reasons :-). (A few minutes pass.....) <LOL> OK, my turn to get helped :-). (What did I just say above?) I've done what you said in permissions.local (and I am in the dialout group) but whenever I try to Query the Modem or even enter the Terminal mode kppp just freezes! And I have to use kill -9 xxxx (not just ordinary kill xxxx) to dead it :-). What is missing and that has to be done to get kppp to work? Give me a clue :-). BTW, I am also using kde 3.1.4. Cheers. -- Sound that shatters silence is called noise. Sound that enhances silence is called music.
On 09/28/2003 08:51 PM, Basil Chupin wrote:
I've done what you said in permissions.local (and I am in the dialout group) but whenever I try to Query the Modem or even enter the Terminal mode kppp just freezes! And I have to use kill -9 xxxx (not just ordinary kill xxxx) to dead it :-).
Did you run SuSEconfig? That will set the correct permissions for pppd.
What is missing and that has to be done to get kppp to work? Give me a clue :-).
The only thing I can guess is a messed up config file. Try renaming or moving to Trash ~/.kde/share/config/kpprc. I have used it for several years with only minor packaging glitches, i.e. once /etc/ppp/peers/kppp file was left out, now the pppd permissions.
BTW, I am also using kde 3.1.4.
I have used it since upgrading, so I know it still works. Same config file on mine since quite a while. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Joe Morris (NTM) wrote:
On 09/28/2003 08:51 PM, Basil Chupin wrote:
I've done what you said in permissions.local (and I am in the dialout group) but whenever I try to Query the Modem or even enter the Terminal mode kppp just freezes! And I have to use kill -9 xxxx (not just ordinary kill xxxx) to dead it :-).
Did you run SuSEconfig? That will set the correct permissions for pppd.
No I didn't.
What is missing and that has to be done to get kppp to work? Give me a clue :-).
The only thing I can guess is a messed up config file. Try renaming or moving to Trash ~/.kde/share/config/kpprc. I have used it for several years with only minor packaging glitches, i.e. once /etc/ppp/peers/kppp file was left out, now the pppd permissions.
Well, something was messed up because I 'lost' the whole system for the first time in some 5 years of using Linux :-(. I couldn't login into SuSE- when trying to boot into SuSE kept getting the message modprobe: modprob; Can't locate module char-najor-180 and when the login prompt came up and I tried to login as root I got the message FATAL: cannot change permissions of TTY: Read-only file system. So I had to re-install the whole sheebang. And this also made me stop worrying about getting kppp to work :-). kinternet is working just fine so kppp can stay in its cage :-). Cheers. -- Hire teenagers while they still know everything.
The 03.09.30 at 23:04, Basil Chupin wrote:
modprob; Can't locate module char-najor-180 and when the login prompt came up and I tried to login as root I got the message FATAL: cannot change permissions of TTY: Read-only file system. So I had to re-install the whole sheebang.
I heard of that problem on this list time ago, but I don't remember the solution. Did you try to log on text mode console, o reboot into runlevel 1? -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The 03.09.30 at 23:04, Basil Chupin wrote:
modprob; Can't locate module char-najor-180 and when the login prompt came up and I tried to login as root I got the message FATAL: cannot change permissions of TTY: Read-only file system. So I had to re-install the whole sheebang.
I heard of that problem on this list time ago, but I don't remember the solution. Did you try to log on text mode console, o reboot into runlevel 1?
No and No. With the error message I was getting and not being able to get into the system from the CD or the rescue disk, the only thing a young lad could do was to re-install, which is what I did. And I didn't have the other computers setup to access the Net so I wasn't able to ask for help in this forum. Cheers. -- If logic ruled the World, men would ride side-saddle.
The 03.10.06 at 22:05, Basil Chupin wrote:
change permissions of TTY: Read-only file system. So I had to re-install the whole sheebang.
I heard of that problem on this list time ago, but I don't remember the solution. Did you try to log on text mode console, o reboot into runlevel 1?
No and No. With the error message I was getting and not being able to get into the system from the CD or the rescue disk, the only thing a young lad could do was to re-install, which is what I did. And I didn't have the other computers setup to access the Net so I wasn't able to ask for help in this forum.
Mmm. I friend of mine just phoned me because he could not boot into linux - I'm his free support hotline, by the way ;-) - and it appears he has a corrupt HD. One of the error messages he is getting is that; I think it is because resmgr failed to start, and I don't like it. Told him to reseat cables first, and check the HD. I hope to be sleep before he finishes ;-) -- Cheers, Carlos Robinson
*** Reply to message from "Carlos E. R."
Mmm. I friend of mine just phoned me because he could not boot into linux - I'm his free support hotline, by the way ;-) <snippage> I hope to be sleep before he finishes ;-)
boy, been there.. got kid in Oklahoma , pissed at the latest round of worms etc. I sent her a brand new pkgs of Suse ( chumbo had a nice price including "free" fedex shipping ) She got it Mondya, and we spent a few days and long hours trying to fugure out why her modem ( USR ext.) wouldn't connect... and after we'd poked at and changed nearly every file possible she said she was going to go to bed.. called back the next ayem and said it was working just fine, set her kids up w/ their own desktops and everyone is happy , including her hubby who now has his own desktop <G> Now it's just to update everything and there's a lot... but so far Earthlink has treated her and her linux connect questions very well. She is half a continent away and email is a much cheaper way to go than voice lines, unless you have one of those wireless phones like the ones from Pacbell or some of the others that offer some sort of family setup I don't... SOme days one really has to get away from ringin g phones and demands for one's time.. totally connected and always available can be a real drag at times! <sigh> oh yeah, for those who wonder, I sent her the 8.2 because I know it's solid and it will be around long enough for her to get used to it... eventually she will want the latest and newest , like her mum.. But for that , she will need at least one more computer <G> (9.0 should be out soon and I'll be back to the testbed and playing w/ it again yay!!) At least I've installed enough copies of 8.2 on enough computers that barring a weird ISP ( and there are still a lot of those !) I can actually set it up on the phone. Next project, to figure out what tunneling software can let her connect to my lan here w/o driving up both crazy . Her modem and isp gives her a different ip each connect so I'm not really certain how to handle that .. This'll be my first tunnel that isn't on a static ip setup. time to hit the books again I guess. ;-) -- j nemo me impune lacesset
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 08 October 2003 14:16, jfweber@bellsouth.net wrote:
*** Reply to message from "Carlos E. R."
on Thu, 9 Oct 2003 00:47:14 +0200 (CEST)*** Mmm. I friend of mine just phoned me because he could not boot into linux - I'm his free support hotline, by the way ;-)
<snippage>
<snip> . Her modem and
isp gives her a different ip each connect so I'm not really certain how to handle that .. This'll be my first tunnel that isn't on a static ip setup.
time to hit the books again I guess. ;-)
I would set up ez-update on her box and write a script to collect her new ip to enable to change the ip. If possible it would be better with the dns name as that does not change. Just my thoughts Ian - -- A child of five would understand this. Send someone to fetch a child of five. Groucho Marx - ---------------------------------------------------- This mail has been scanned for virus by AntiVir for UNIX Copyright (C) 1994-2003 by H+BEDV Datentechnik GmbH. PGP ID: 589F8449 Fingerprint: EB1C FACF 6BEB 540E 8AC0 F04E 2A25 A2F1 589F 8449 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/hdqUKiWi8VifhEkRApOaAJ0YKYUwvA2mPKKSemmmEvcKul+7qQCfTxIc QQqlU2uWyKgfXNIAMT9jzKs= =k68f -----END PGP SIGNATURE-----
The 03.10.08 at 18:16, jfweber@bellsouth.net wrote:
*** Reply to message from "Carlos E. R."
on Thu, 9 Oct 2003 00:47:14 +0200 (CEST)*** Mmm. I friend of mine just phoned me because he could not boot into linux - I'm his free support hotline, by the way ;-) <snippage> I hope to be sleep before he finishes ;-)
boy, been there.. got kid in Oklahoma , pissed at the latest round of
She is half a continent away and email is a much cheaper way to go than voice lines,
You should try things like gnomemeeting: voice over IP. A bit tricky with firewalls, but possible, and very cheap, compared to long distance. On the other hand, if she doesn't have a fixed IP (like me) then you need an intermediary server with fixed IP to meet.
oh yeah, for those who wonder, I sent her the 8.2 because I know it's solid and it will be around long enough for her to get used to it...
Good choice. Don't touch the 9.0 for a remote installation ;-)
Her modem and isp gives her a different ip each connect so
You can have her side send an email with the new IP each time: this can be done from inside /etc/ppp/ip-up.local. Then you need a way to confirm the machine... perhaps ssh. Some kind of keepalive ping would be nice... -- Cheers, Carlos Robinson
participants (7)
-
Basil Chupin
-
bernd@covenantmail.net
-
Carlos E. R.
-
Ian David Laws
-
jfweber@bellsouth.net
-
Joe Morris (NTM)
-
John Andersen