View Full Version : system-config-network
owakroeger
2004-08-15, 04:24 PM CDT
FC2(2.6.7) I just compiled a new 2.6.7 kernel. The dialup will dial, and connect momentarily, and then disconnect. If I boot to the 2.6.5-1.358 kernel, using the same dialup connection, everything works normally. I tried deleting everything, including the modem, from the system-config-network, and rebooted to the 2.6.7 kernel. I then ran system-config-network, configured the modem, and the dialup connection. In 2.6.7 it would connect momentarily, then disconnect. I rebooted to the 2.6.5-1.358 kernel, and the dialup I had just configured was there. I tried it, and it works.
Do you suppose the password is not being passed on to the ISP provider?
Any suggestions? I really need to get this guy's system up and running, and he wants it on 2.6.7.
Thanks for any ideas.
owa :o :o :o
ghaefb
2004-08-16, 01:30 AM CDT
Try updating your system-config-network.
There has beed an update released -> http://www.fedoranews.org/updates/FEDORA-2004-209.shtml
owakroeger
2004-08-16, 05:14 AM CDT
Thanks, gaefb.
I had planned on setting up apt-get and synaptic, and showing this fellow how to update his system after I had 2.6.7 up and running. We'll do the updates first, and see if that fixes the problem. Thanks, again, for your reply.
owa
owakroeger
2004-08-17, 12:52 PM CDT
Sorry it took a while to get back to this.....I did a complete update ( I prefer apt-get with synaptic...same thing) and tried again, with the same results. The dialer works with the 2.6.5-1.358 kernel but not with the 2.6.7 kernel. So....while it was doing the update in the background, my gut was telling me that there was some minute, obscure problem with the 2.6.7 kernel. Whether the problem developed during the 'config' part of build or just where, is a mystery. While the update was completing, I built another new 2.6.7 kernel, and had it ready to go. When the update didn't fix the problem, I installed the freshly built 2.6.7 kernel, and it works flawlessly.
36 years as a service technician for Xerox makes me want to find out exactly what was broken in the faulty kernel, but, as yet, I can't see any difference between the bad one and the good one.
Long story short, the problem is fixed, I have a happy neighbor (I was helping him get going on Linux), I have a somewhat happy wife ( she refers to my computer as "The Slut!!") , and I had some more practice troubleshooting Linux, specifically FC2.
Have fun every chance you get.
Thanks again for your advice, even though that didn't fix it. I appreciate your response.
owa :) :) :) :) :) :) :) :rolleyes:
vBulletin® v3.7.3, Copyright ©2000-2009, Jelsoft Enterprises Ltd.