Slackware 13 Network Settings
I just installed Slackware 13 and I cannot see my network settings with KDE
I get an error "could not parse XML file()" My networks connect fine and I can see them with iwlist or ifconfig from the command line....just cant see the setting with KDE. I have the same problem on both my Laptop and Desktop computers. Any ideas?? Thanks |
so do I
|
Hello ibwew,
welcome to LQ, If everything works fine in your network, why do you want to see the settings in KDE? I don't know what to do to make KDE show the networksettings. But it is not the prefered method in Slackware, to configure the system via a gui-tool. Markus |
It's easier to switch networks.....especially on my Laptop. I used the GUI
with Slackware 12.2 and it was easier to change the wireless settings...just "point and click". Now I have to edit my /etc/rc.d/rc.wireless.conf file to switch wireless networks...PITA!! Thanks |
You could try using wicd. Slackware has a package for it.
|
Already installed and tried it......no joy!!
|
Hi,
Quote:
|
OK........I got wicd working!! Had to add myself to the netdev group.
Thanks everyone for your help!! |
I still would like to be able to see my network setting with KDE though...if anyone has a solution I would love to hear it.
Thanks |
Contact the KDE people who added "Slackware network configuration support" but didn't check with the Slackware developers to make it actually work...
Eric |
Forever newbie...
1 Attachment(s)
Ok, I had just installed Slackware 13.0 and got no network working.
I also got the same error in KDE (prnt screen attached). How to get out of here and have eth0 up and running? Thanks! |
Hello eraosso,
please let us know which network card you're using. Wired or wireless? what is the output of ifconfig? please post the related part of your /etc/rc.d/rc.inet1.conf. Markus |
3 Attachment(s)
Quote:
I was trying the wired card. Wireless will come next. :D Attached are dmesg, ifconfig and rc.inet1.conf. Since I did not know what is the important part of rc.inet1.conf, I attached the whole file. On dmesg I found the following about eth0:
Thanks again for the help! |
Hello eraosso,
your networkinterface is set up correct with the appropriate drivers. But it did not get an IP-configuration via DHCP. If you use DHCP you shoud try: Code:
dhcpcd eth0 The IP-adress which ifconfig shows for eth0 is a so called APIPA-adress (automatic private ip adressing) which the computer generates if there is noch configuration available via DHCP. Have you used Slackware before installing Slack13? Have you made any changes? As far as I know the network-configuration while the installation has not changed since earlier versions of Slackware. Markus |
Hi Markus,
this is a plain vanilla installation I did yesterday. I have played with Slackware since version 8, then installed Slack 11 and even played with wireless. But I never had such problems... Usually network was up and running without issues. I will give it another try and will revert back in case I do not succeed. Thanks again! Osmar. |
Hi,
First, do you have the 'users' in the proper groups; Code:
users floppy audio video cdrom plugdev power netdev |
Well, I did rerun the installation DVD and this time I configured the network through the setup program...
But what I really believed solved the problem was that I set the MAC address of the network card as allowed into my router... :newbie: This is posted using my good old Dell Inspiron with Slack 13 on it!! Again, many thanks for helping and sorry for the clumsy "newbiness"... |
Quote:
anyway happy that the problem is sloved. |
Quote:
thanks in advance.... |
Quote:
|
Quote:
|
finally I did it with command line. Although not through gui still..
thread really helped. I would like to thank Nylex also.:) |
Quote:
|
Quote:
P.S. By using wicd,I can configure my network in graph mode,but I do want to make kdenetwork work. |
i have this problem as well in slack13, but im using the GNOME based desktop, "cholesterol free desktop" and it also cannot parse the XML file.
|
Quote:
As for command line, that is very simple for ethernet, and should be for wireless also as long as your wireless drivers are installed. I generally
Though if you're going to run wicd it's easier to remove all specific settings and let wicd auto-detect which network you're connected to. I don't think I had to change anything, though, because eth0 was already configured to use DHCP, which is all it actually needs. Even if I reboot and don't go to the desktop, I find my ethernet gets its settings automatically. I'm not good at remembering details and can't remember the path to the config file...I'm not at home right now...the path is different on Slackware than other distros. You really shouldn't have to do anything except bring eth0 up. F.Y.I., I downloaded the latest wicd, I did not install from the Slack DVD because the older wicd has a bug (read that on SourceForge http://wicd.sourceforge.net/ ) |
All times are GMT -5. The time now is 04:51 PM. |