Slackware 12.1 ethernet was working perfectly, until one day the motherboard dies and was replaced with another (both old and new ASUS A8V Deluxe). Now, eth0 isn't anywhere to be seen. My on-board ethernet is the "Marvell Yukon 88E8001/8003/8010 Gigabit Ethernet Controller".

Windows XP x64 can use the on-board ethernet just fine.

Can changing a motherboard, even if it's the same model, cause eth0 to not be found by ifconfig in Linux?

When I run "ifconfig -a", all I see is "lo" (loopback) and "eth1". My "eth0" disappeared.

I haven't even been using Slackware after the motherboard died, until today.

When I do "modprobe" and "lsmod", "sk98lin" is not shown in the output - however I don't know 100% if it was even there before the motherboard died. And as far as I know, "sk98lin" is needed for the ethernet controller I want to use.

I have checked some other threads, I'll continue to do so, but I'd like to do some poking around in Linux some more. (I have to get on Windows to browse internet at the moment.)

Thank you for any help you can give me.

Can you post output of lspci

I honestly don't see any point but ok...

I could probably paste the whole output, but I would need to save to file and copy to Windows.

It might because your net has different mac address now.

If it shows eth1, I think it might be naming problem only
I would try to modify /etc/udev/rules.d/70-persistent-net.rules
if there are two lines there (eth0 and eth1) just comment out the one that says eth0, and change the name of second from eth1 to eth0

Ok, I was thinking something similar myself too.
It seems very likely to me. I'll go try it.

Ok, I changed "eth1" to "eth0" and commented out the eth0 one, rebooted and still doesn't work; it says now it can't start the device.
Mind you, eth0 was the FireWire and eth1 was my Marvell Yukon...

"eth1" is using "skge", at least I think that's what it was.

(Windows XP also detects the FireWire (IEEE 1394) and the Gigabit LAN (Marvell Yukon 88E8001).)

Original error outputs would be helpful
What ifconfig -a shows now
Did you rerun netconfig

I didn't run netconfig at all, can't seem to find where it's located. (Saw it mentioned on forum already too.)

ifconfig -a shows "lo" and "eth0" with the changes you instructed me to make. Without changes, it shows "lo" and "eth1".

I'll see if I can get the exact error messages for you too. (Having one computer to do this on requires me to do alot of rebooting Windows and Linux.)

make a copy of /etc/udev/rules.d/70-persistent-net.rules
delete file 70-persistent-net.rules
reboot your system

Deleted the file, rebooted, ran "netconfig" and typed in all the settings, rebooted -- did "ifconfig eth0 192.168.2.20" -- I now can access the other LAN machines, just not get on the internet.

There is no need for
Everything suppose to be done by netconfig ip address, gateway, dhcp.
What kind of network connection do you have?

I used that line because the README file for the sk98lin told me to do so, "Manual Load of Module", although I didn't install the module, as it already existed.

I have a DSL broadband connection.

I also found out why I couldn't get on the internet; for whatever crazy reason, files on my hard drive change their attributes by themselves - they lose their "Executable" flag. In this case, "resolv.conf" wasn't executable... Why does that happen? o_O

Anyway, I'm on the internet again, I really appreicate your help, you did point me in the right direction, thanks!

resolv.conf doesn't have to be executable

If it's sorted not much point to this, but I have a new asus mboard and you just use eth1 instead of eth0, have no idea why.

If I remove the executable flag from "resolv.conf", I lose my internet, since my "Default Gateway" gets set to "" (nothing).

I won't question it, I just know it's working now.