can't establish a dial-up conn with kinternet
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated. jozien
Take a look at the log files kinternet shows. It might give you a clue on what is happening. You wil need to right click on the kinternet icon and select log files. Joe Zien wrote:
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated.
jozien
-- Joseph Loo jloo@acm.org
El Jue 02 Jun 2005 18:23, Joseph Loo escribió:
Take a look at the log files kinternet shows. It might give you a clue on what is happening. You wil need to right click on the kinternet icon and select log files.
Yes, but those logs are not very verbose by default. What you can do is to uncomment in /etc/ppp/options the line with the 'debug' parameter, and put 'debug = yes' in /etc/smpppd.conf. Now you may get some meaningful log information. Regards, -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia http://www.noemasol.com
On 02/06/05, Joe Zien <jozien@cybercomm.net> wrote:
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated.
jozien
Check in the /etc folder(directory) that you have a file called resolve.conf There does not have to be anything in it just that it is there. Do not confuse it with the resolvconf file (note the absence of the full stop). If the file is not there just create it as a text file. This has worked for me in the past both with SuSE and with Kubuntu both using KDE (kinternet, kppp). -- Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
Fri, 03 Jun 2005, by kevanf1@gmail.com:
On 02/06/05, Joe Zien <jozien@cybercomm.net> wrote:
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated.
jozien
Check in the /etc folder(directory) that you have a file called resolve.conf There does not have to be anything in it just that it is there. Do not confuse it with the resolvconf file (note the absence of the full stop). If the file is not there just create it as a text file. This has worked for me in the past both with SuSE and with Kubuntu both using KDE (kinternet, kppp).
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s). It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more powerful magic than mine (you did get an official licence for that did you?) Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
On 05/06/05, Theo v. Werkhoven <twe-suse.e@ferrets4me.xs4all.nl> wrote:
Fri, 03 Jun 2005, by kevanf1@gmail.com:
On 02/06/05, Joe Zien <jozien@cybercomm.net> wrote:
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated.
jozien
Check in the /etc folder(directory) that you have a file called resolve.conf There does not have to be anything in it just that it is there. Do not confuse it with the resolvconf file (note the absence of the full stop). If the file is not there just create it as a text file. This has worked for me in the past both with SuSE and with Kubuntu both using KDE (kinternet, kppp).
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s). It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more powerful magic than mine (you did get an official licence for that did you?)
Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Well, all I have done is posted up what helped me. I do not have a clue how it worked but it did. All I was getting was an error message saying something about not being able to find (or possibly access) the etc/resolve.conf (I may have added the 'e' in error). So I went into the etc folder and simply added it. My dial up connection then worked. I'm pretty sure I have seen exactly the same happen in Mandrake. Perhaps I am just very lucky? -- Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
Do you have stupid mode enabled? Play with the baudrate. On Sun, 5 Jun 2005 18:21:56 +0100 Kevanf1 <kevanf1@gmail.com> wrote:
Fri, 03 Jun 2005, by kevanf1@gmail.com:
On 02/06/05, Joe Zien <jozien@cybercomm.net> wrote:
I finally got 9.3 Pro installed and am very impressed. Only problem is I can't establish a dial-up connection with kinternet When I first installed, yast did not setup my modem. After installation, I tried to setup connection with yast. The kinternet icon is in the bottom tray and when I click, the modem starts dialing and I hear the modem working, all the proper led's are lit and the modem dies. I have an external modem on port tty0, com port 1. This modem works great on my libranet 2.8.1 system. Any help would be appreciated.
jozien
Check in the /etc folder(directory) that you have a file called resolve.conf There does not have to be anything in it just that it is there. Do not confuse it with the resolvconf file (note the absence of the full stop). If the file is not there just create it as a text file. This has worked for me in the past both with SuSE and with Kubuntu both using KDE (kinternet, kppp).
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s). It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more
On 05/06/05, Theo v. Werkhoven <twe-suse.e@ferrets4me.xs4all.nl> wrote: powerful magic
than mine (you did get an official licence for that did you?)
Theo -- Theo v. Werkhoven Registered Linux user# 99872 http://counter.li.org ICBM 52 13 26N , 4 29 47E. + ICQ: 277217131 SUSE 9.2 + Jabber: muadib@jabber.xs4all.nl Kernel 2.6.8 + See headers for PGP/GPG info. Claimer: any email I receive will become my property. Disclaimers do not apply.
Well, all I have done is posted up what helped me. I do not have a clue how it worked but it did. All I was getting was an error message saying something about not being able to find (or possibly access) the etc/resolve.conf (I may have added the 'e' in error). So I went into the etc folder and simply added it. My dial up connection then worked. I'm pretty sure I have seen exactly the same happen in Mandrake.
Perhaps I am just very lucky?
-- Take care. Kevan Farmer
34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
-- 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
_____________________________________________________________________ For super low premiums, click here http://www.dialdirect.co.za/quote
Theo v. Werkhoven wrote:
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s).
They are always empty from a fresh install.
It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more powerful magic than mine (you did get an official licence for that did you?)
I have seen this as well. ppp moves resolv.conf to /etc/ppp/resolv.conf.ppp (or something like that), and creates a new resolv.conf with the info from the connection. If something happens to resolv.conf, ppp gets stuck not being able to move the original file and doesn't create the new resolv.conf. It could be the pppd crashed while moving the file and deleted it without replacing it, which could cause the problem. Creating an empty file via touch gives it a file to move, and it works again. As you said, without it, even though the modem connects, no traffic moves, so the modem appears non-responsive. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On 05/06/05, Joe Morris (NTM) <Joe_Morris@ntm.org> wrote:
Theo v. Werkhoven wrote:
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s).
They are always empty from a fresh install.
It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more powerful magic than mine (you did get an official licence for that did you?)
I have seen this as well. ppp moves resolv.conf to /etc/ppp/resolv.conf.ppp (or something like that), and creates a new resolv.conf with the info from the connection. If something happens to resolv.conf, ppp gets stuck not being able to move the original file and doesn't create the new resolv.conf. It could be the pppd crashed while moving the file and deleted it without replacing it, which could cause the problem. Creating an empty file via touch gives it a file to move, and it works again. As you said, without it, even though the modem connects, no traffic moves, so the modem appears non-responsive. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Thank you Joe. It's entirely possible that it was exactly that which happened to me. All I did in the first place was to post a solution that had worked in real time for me. I never professed to know 'how' it had worked I was just trying to be helpful. -- Take care. Kevan Farmer 34 Hill Street Cheslyn Hay Staffordshire WS6 7HR
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-06-05 at 16:35 +0200, Theo v. Werkhoven wrote:
In the 10 years I've been workong with Linux i've never come across a distro that wants an empty file named /etc/resolve.conf. /etc/resolv.conf otoh (notice the absence of the 2nd 'e') is mandatory of you want to use nameserver(s).
That's a typo.
It is useless to leave it empty though, read up on 'man 5 resolver' if you want to know what is expected in that file. How this would have anything to do with a non-responsive modem is beyond me btw., but maybe your xtal ball has more powerful magic than mine (you did get an official licence for that did you?)
That's a documented and known bug: I knew first about it around November 2003. I thought it would have been corrected since then. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCo6A3tTMYHG2NR9URAixqAJ9AAk3xay9ltVS8LNjg9Kpr3Rx7mACfRm34 0s/23CSrmRhE8qKXZkZFETY= =MpwQ -----END PGP SIGNATURE-----
participants (8)
-
Andreas Philipp -
Carlos E. R. -
it clown -
Joe Morris (NTM) -
Joe Zien -
Joseph Loo -
Kevanf1 -
Theo v. Werkhoven