Network Problems with Slackware 9.1 and VIA Compatible Fast Ethernet Adapter
 

I have to do this from Windows because Slackware decided not to see my network. I can log into the router fine, but I don't know what to do otherwise. I set everything up as well as I could (sorry I'm not good at this, RH9 and FC2 automatically detected the network), like having everything as close to Windows networking as possible. Is there any way to view the network connections and/or modify their values without reinstalling Slackware?



PS: Is there any way to change the display driver in Slackware?

bash-2.05b# netconfig
will get it setup just fine. To view your connection try
bash-2.05b# ifconfig
and alternately add the nic, such as
bash-2.05b# ifconfig eth0
or
bash-2.05b# ifconfig eth1

What is the make and model of your motherboard? Your nic may not be recognized. Can you post the output of
bash-2.05b# lspci

It will return output like thisand from there we can determine your nic, where it's located, and then find out if Slack has a module for it, or if it's built-in the kernel...


What do you mean by "change the display driver?"

To the display driver: Well, in Fedora Core 2 and Redhat 9, there was a screen where I could change the driver that is loaded for my video card. I was just wondering if there was something like that in Slackware.

Hope this works. :D

Not a gui - you actually have to
(1) install the driver if it's not already installed
(2) edit /etc/X11/XF86Config

Cheese what you are doing is trying to make what you have learned in windoze fit into linux. Companies like Redhat are producing products that make some things look the same as windows. Such as a "install new video driver" box. This is NOT the nix way of doing things. If you want to really understand your system make the linux documentation project your friend.

http://www.tldp.org/

What you learned to do in windoze is really only applicable in windoze. Linux is not windows. It has a much better way of doing things Learn how to use linux as linux not as windows. If you do this all the girls will love you, you will make lots more money and live a long and happy life.

:D

I definitely want girls, But I was just taking the network stuff (like the gateway, what IP I'm supposed to be, etc), and didn't think that that would be a problem.

This is what ifconfig printed out:

Well you have an ip
The inet addr:192.168.0.3 shows this. But you say you can't get on the net. What is in, or do you have, an /etc/resolv.conf ? Here is what is in mine:

nameserver 216.148.227.68
nameserver 204.127.202.4
search attbi.com

What does yours say? Can you ping any of the name servers in your resolv.conf file? can you ping 66.94.230.37, this is www.yahoo.com or one of them at least. And just to touch all the bases, what is the output from route? I am looking here to see if you have route to your gateway.

And what kind of router do you have??

This is what /etc/resolv.conf says:
Please explain to me what that means? Do you mean can I access my router (which, BTW, is the Netgear RP614v2 router)

And I didn't understand what nameservers were in the first place so I just left them alone.

Heh. I just had to fill in the nameservers (which I figured out was DNS), and now it works. Thanks for all of the help, I appreciate it.

Dude,

I just gotta ask...what's up with that nick? Whatzit mean?

Just got my router back from the shop - supposedly repaired - it got
toasted when I flashed the bios - we'll see - I got a new ISP and will
have to get the nameservers for them.

The name spawned about 5 years ago on Battle.net. It doesn't mean anything at all. But.......... I don't plan on switching ISPs any time soon (Verizon's package is decent enough, but hey, I'm not paying, my parents are), and I don't do enough to fry anything.

I thought that might be the case. That's why I gave you my resolve.conf.

By the way how did you get the name servers? It's cool to use the ones I have in my resolve.conf but they might change. If they do you will be SOL.

Even though you are up and running now I don't think the problem is solved. Take a look in /etc/dhcpc at the file that matches your ethernet device. Mine is /etc/dhcpc/dhcpcd-eth0.info. Here is what mine looks like:

IPADDR=192.168.1.18
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1
DOMAIN='attbi.com'
DNS=216.148.227.68,204.127.202.4
DHCPSID=192.168.1.1
DHCPGIADDR=0.0.0.0
DHCPSIADDR=192.168.1.1
DHCPCHADDR=xxxxxx # you don't need to see this part
DHCPSHADDR=xxxxxx
DHCPSNAME=''
LEASETIME=7200
RENEWALTIME=3600
REBINDTIME=6300
INTERFACE='eth0'
CLASSID='Linux 2.6.2 i686'
CLIENTID=xxxxx

Notice the DNS part. Does your file have this? If so then there is a problem with your dhcp client. It should have updated your resolv.conf file. If it's not there then there is a problem with your router. It should have given the dhcp client the information.

I don't have the file that you mentioned (I have the same thing, but with an EXE extension), but thanks for ruining my short-lived fun. :p

Don't worry the fun is just beginning.

I think there is some sort of problem with your dhcp client. Here is a list of the files that I have in /etc/dhcpc
-rw------- 1 root root 136 Jun 7 11:49 dhcpcd-eth0.cache
-rwxr-x--- 1 root root 61 Jan 28 2003 dhcpcd-eth0.exe*
-rw-r--r-- 1 root root 410 Jun 7 11:49 dhcpcd-eth0.info
-rw-r--r-- 1 root root 410 Jun 6 23:09 dhcpcd-eth0.info.old
-rw-r--r-- 1 root root 3 Jun 7 11:49 dhcpcd-eth0.pid


Could you post /etc/rc.d/rc.inet1.conf? This will show how your ethernet device is setup.