NIC won't work

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

Ok, im rather new to linux i started out with redhat and mandrake, but i was told that if I could get Gentoo to work i would like it alot better. I have the os installed and it boots and i can login to root. My problem is i can't emerge kde or any other gui. I have been told its because my NIC is not being recognized by the kernel or thats what i think is wrong. When i login and try ifconfig it never shows eth0. I run a D-Link DFE-530TX+ in my linux box. I have tried numorous things that a friend told me to try. He told me to try modprobe tulip and it let me emerge rsync it won't let me emerge kde. If anyone could help me get this NIC working and get eth0 to load i would greatly appreciate some help with it.

thanks

delta407 · Posted: Tue Jul 16, 2002 12:54 am Post subject: Re: NIC won't work

delta407 · Posted: Tue Jul 16, 2002 12:55 am Post subject:

Oh yeah, moving to Networking forum.
_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

thanks, is there a way to do that without redoing my whole system. Im a linux newbie and i just don't know if i need to start over and enable the realtek or if i can do it right now logged in as root.

delta407 · Posted: Tue Jul 16, 2002 1:00 am Post subject:

To use a new kernel, do this:

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok it booted without errors this time. But now my problem is its not booting eth0, i think that i might of removed it from some file that its supposed to be in, im not sure what all i've edited, just a friend had me edited a bunch of files

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok now when it boots i get an error that it can't load tulip...any help??

rac · Posted: Tue Jul 16, 2002 2:09 am Post subject:

It shouldn't want tulip any more, assuming the Gentoo Forums' resident AI aka delta407 is operating correctly. Might you have a stale reference to tulip in /etc/modules.autoload as a result of your earlier efforts? If that is not the case, please post a more detailed error message.
_________________
For every higher wall, there is a taller ladder

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok i did what delta said, i added the realtek support. I reboot my machine and when its finished and wants me to login it has an error that says "Failed to load tulip"

delta407 · Posted: Tue Jul 16, 2002 2:28 am Post subject:

You probably still have tulip enabled in /etc/modules.autoload. Remove it and everything should be happy.
_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok well i took it out. It boots fine without any errors except when i do ifconfig i get no eth0........and i can't emerge any guis or anything because of it.

delta407 · Posted: Tue Jul 16, 2002 2:33 am Post subject:

Did you build rtl8139 as a module <M> or compiled in [*]? If it's <M>, you have to add rtl8139 to modules.autoload.
_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ohh ok, that will probably help because yea it is M not * let me try it

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok well that didn't work, now its saying "Failed to load rtl8139"

delta407 · Posted: Tue Jul 16, 2002 2:37 am Post subject:

Wait, did you compile "RealTek RTL-8139 PCI Fast Ethernet Adapter support" or "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"? If you did the first one, you need to add "8139too"; if it's the second one, you need to add "8139cp".

...and remove the earlier one I told you, I wasn't thinking.

_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

i chose the non expiremental one..

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok i took out rtl8139 (/etc/modules.autoload) and added 8139cp, it says failed to load 8139cp...

delta407 · Posted: Tue Jul 16, 2002 2:42 am Post subject:

No, see, 8139cp is if you chose the experimental one.

Anyway, I tend to compile drivers into the kernel [*], since we don't have these problems then. Oh well, this ought to work.
_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok well when im in the kernel configuration how do i make it compile that instead of making it a module. I hit M on it and it makes it a module. sorry wasn't paying attention up there :wink:

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok, its loading that module now but still no eth0....i just don't understand it

delta407 · Posted: Tue Jul 16, 2002 2:47 am Post subject:

You don't have to reconfigure, but if you want [*] you can hit Y.
_________________
I don't believe in witty sigs.

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok, but what about this eth0 thing, i can't get it to find eth0 and without it i can't emerge any gui...

delta407 · Posted: Tue Jul 16, 2002 2:52 am Post subject:

Okay, here's what happens. The kernel needs to have a driver for your network card, and you can do this in two ways. One is to build the driver into the kernel [*], the other is to build it as a module <M> and put the module name into /etc/modules.autoload. Then, /etc/init.d/net.eth0 reads your configuration settings in (/etc/conf.d/net) and tries to bring up eth0, which corresponds to the previously loaded driver.

Thus, you can either hit Y and recompile/reinstall your kernel, or add 8139too to /etc/modules.autoload. Everything should work after doing either.
_________________
I don't believe in witty sigs.

delta407 · Posted: Tue Jul 16, 2002 2:53 am Post subject:

Green Letters · n00b Joined: 16 Jul 2002 Posts: 17

ok this is what i get when i reboot