KInternet Config in SuSE 8.0
I've tried over a dozen times to configure my modem in YAST2 so that KInternet will load, but there's a red exclamation point over the KInternet icon in the taskbar and each time the log says that there's no provider configured. But I have configured the provider, but the settings I make just won't stick. I'm having to use either wvdial (which I had to set up by manually editing /etc/wvdial.conf, whereas in 7.3 it was set up automatically when configuring the modem) or kppp. I had no such trouble in 7.3, and I know I'm not missing something in the dialogues. I've done it every conceivable way with no effect. Does anyone know where the actual config file for KInternet is, so maybe I can edit it manually like I did for wvdial? Thanks in advance for any help. Bryce Hardy (Santa Rosa, CA) brycehdy@sonic.net
On Wednesday 08 May 2002 12:51 am, I wrote:
I've tried over a dozen times to configure my modem in YAST2 so that KInternet will load, but there's a red exclamation point over the KInternet icon in the taskbar and each time the log says that there's no provider configured. But I have configured the provider, but the settings I make just won't stick. I'm having to use either wvdial (which I had to set up by manually editing /etc/wvdial.conf, whereas in 7.3 it was set up automatically when configuring the modem) or kppp.
I had no such trouble in 7.3, and I know I'm not missing something in the dialogues. I've done it every conceivable way with no effect. Does anyone know where the actual config file for KInternet is, so maybe I can edit it manually like I did for wvdial? Thanks in advance for any help.
Well, I figured out a workaround for this myself, but it still bears some scrutiny because it must have been a bug of some kind. I finally tweaked around until I found the /usr/share/providers/US.conf file. So I manually edited that to include my local ISP at the top of the file. Then when I went in to configure the modem in YAST2 I chose my own new entry in the list of US providers, and it turned out that it finally works! If there aren't a lot of people experiencing this it's really strange, because it happened right after a fresh install. Oh well, I'm glad I figured out a cure. Sorry to bother everyone, but if there are a lot of others with this problem, the above is one solution. Bryce Hardy (Santa Rosa, CA) brycehdy@sonic.net
participants (1)
-
Bryce Hardy