O.k so I've been a slackware advocate ever since I first installed slackware 8 (I know, not a very long time.) it's given me time to learn to love and appreciate the stability. For a while though I stopped using linux all together, however; I continued to install slackware every time a new release came out just to see what was going on. Just recently I switched to gentoo just to see what all the hype was about, and I was frankly not impressed. To not start a flame war about these flavors I'll get to my question.

I've successfully installed slackware 15+ times on this exact machine, no hardware changes have been made in the past year. Unfortunately for some reason (last night) when I attempted to return to my favorite flavor of linux I am completely unable to get online. Here is my hardware:

ASUS P4P800-E Delux w/ P4 2.8Ghz Presscot (800Mhz FSB)
ATI Radeon 9200 128MB AGP
1GB RAM (2x512)
Marvel Yukon 88E801/8003/8010 PCI Gigabit Ethernet Controller
Linksys LNE100TX Fast Ethernet Adapter

In the past I've had absolutely no problems getting online. Default kernel (bare.i) would always pick up my ethernet card no problem. I'm behind a router (WRT54G) using dhcp, yet I can't communicate with my router? ifconfig returns only loopback, and ifconfig -a just shows me that my router is there. lspci proves that all my hardware is being detected. I'm not sure if I'm making any mistakes as I might be quite rusty. I can't find the information I'm seeking in the 'book' so I come to you guys

I forgot to mention my partition table in case that may be an issue.

/dev/hda1 = /boot ext3
/dev/hda2 = swap
/dev/hda3 = / ext3

In the past I'd simply do this: immediately after fresh install -> netconfig -> set dhcp -> thats it.

I'm going to see if I can get online with a copy of zipslack I have laying around somewhere to see if there is an error elsewhere. Thanks in advance to anyone who takes a look at this thread!

- rony

Forgot to mention I pulled out the Linksys LNE100TX to see if it was a conflict―nothing.

I appologize for my ignorance, turns out I DID have to load a module for my nic.

sk98lin for anyone interested.

First, Welcome back

Second, It's not ignorance. It learning....lol

The differences in the kernels since your last install is probably the culprit. The previous kernel you used may have had the controller compiled in, and this one obviously does not. Check the differences between the older config file and the new one. You maybe surprised. (That's one of the reasons why I always compile the kernel on a new install. Makes the surprises a little less startling)