This controller probably needs the 8139too module. A few of these cards actually nave the C+ chipset, which has its own driver in the kernel.
If you load the wrong driver, it won't work at all, so its easy to sort them out.

Okay, this is a little weird, not sure what really happened, but I can tell you what I did to get it to work, just not sure what I need to do to make it automatically come up. First of all, I was backward with my controllers. the r8169 does not work at all (not even in Windows), the 8139 is the card controller that I use instead. So, I entered:

Code:

modprobe 8139too

then eth1 showed up in the list of ifconfig -a, so I entered /etc/init.d/net.eth1 start, and it started just fine. I'm actually using it to enter this reply. I did this of course after looking at my kernel config and finding that I indeed have the 8139too module compiled and installed in it. For some reason, it failed to load this module upon booting, but I can't begin to tell you why. So I am kind of stuck with that for now, I guess.