Sorry to see you're still battling this. My post is long here as I give you some extra info, sorry just trying to really explain is all, if anything much of it should confirm some things for you. I know trouble shooting can be a pain.
I went over to tigerdirect to look at your motherboard a little more, so you have (2) physical nic's according to this page here (it's a shopping site, but they've always been good to me :X) and they have really good picture's, better than dfi's site for your board. A pic is worth a thousand words right...:
Now I have not had a chance to do a 2.4.33 install of slack11 yet, and try the internet out. However, I too have (2) network cards built into my motherboard.
Now, from slackware's site:
As an alternate choice, Slackware 11.0 includes Linux 188.8.131.52
and 2.6.18 kernel source, kernel modules, and binary packages,
along with the mkinitrd tool and instructions on using it to
install the new kernel (see /boot/README.initrd). When running a
2.6 kernel, Slackware supports udev. This is a system for
creating devices in /dev dynamically, greatly reducing device
clutter and making it easy to see what devices are actually
present in the system. Udev probes for and enables hardware on
the system, much like the hotplug system does for a 2.4 kernel.
Now I'm not sure of this, but I think the part of Alien Bob's post there that you look for the udev rule, does NOT apply? As you're using a 2.4 kernel, so if 2.4 then no UDEV? Can someone confirm this. I do know that what Alien Bob said is exactly what I had to do to get my motherboard to work w/huge 2.6. Ironically I had no problem for about 10 reboots, then all of the sudden my network just dropped out and I had to do that.
However, I did not see if you tried the other part of Alien Bob's post there which is are you sure you plugged into eth0 or eth1. In case you missed that
I think what he's saying, is to plug it into one port boot up, run 'ifconfig' to see which ethX is running, and then try the internet out. If that doesn't work trying the other port and seeing how that goes following same manner.
Basically, your /etc/rc.d/rc.inet1.conf file store's all of your settings that you input into netconfig. There is also /etc/resolv.conf and that store's the 'nameserver' which is your router's IP address. Then there is 'hostname'which is the pc's name.
You were fine to use 'no modem' if you do not choose to use a modem for your internet BTW.
I can tell you that I too think that if you're using a router, you probably are better off to use a static IP address, slightly faster boot process and if you have a lan, everything works a little cleaner, well that's an opinion I know but you get my drift.
If you're not sure of your router's IP address, in windows xp you just type at the run command in start menu, 'cmd' that brings up a terminal window in Windows, then type 'ipconfig' that will list all of your network cards info. The "Default Gateway ....192.168.x.x" is your router's IP address. That is the number you put into 'netconfig' of linux as your 'gateway' and your 'nameserver (a.k.a. DNS server)'. Many router's let you manually key in an IP address into a PC, even tho the router is setup for DHCP (that is assigns IP addresses to the computer). Just be sure to pick an IP address out when you run 'netconfig' in linux that you do NOT pick a number of a pc that is currently in use. You actually might like to use this forced IP so you can forward incoming network traffic to the pc easily, set it up once and forget it. It helps for bittorrent to seed slack 11 to others
, gaming, instant messaging, etc. DHCP is crude IMO and leads to chaos. It's nice for when you have a friend run over and plug-in, but for the usual pc's plugged in go with manual.
Now that motherboard is an nforce 4 motherboard. I suspect that maybe you would be better off to install slackware with a 2.6 kernel.
See,..nvidia has released a lot of info out to the kernel team for that motherboard, it's a recent chipset, so coding for it would be in the 2.6.X series kernels and not 2.4X
Now that may not be needed for this issue of your lan, but you're agp, all the other feature's for sure, I think you really need that 2.6 kernel to be honest.
Now before you just run out and install 2.6 kernel (which is Ultimately what I think you need to do here) what file system type did you use to install slack 11? Ext3? Reiser? Please advise as you may or may not need to make an initrd to use 2.6 kernel.
if you want you can mail me that board and let me run it or a few weeks and I'll test it
I'm jealous that's a nice board.
To clarify, when you run 'ifconfig' that just shows you what adapter's are up at the time.
Also, if you run 'lspci' and 'lsmod' that tells you alot of information about what devices are seen, and what modules are running at the time. Or if you still have kubuntu installed you can boot up there and run those commands using sudo and see what you get.
lastly, I think every slacker should have a slax cd in their arsenal. it really helps out alot, you can run that cd and use those commands there too, slax runs a 2.6x kernel and is based on a snapshot of slack 10.2's current now known as 11 if i'm not mistaken.