Network Trouble

[blinkin]

Ok, here is my story.

I had the 2.4.26-gentoo-r9 kernel working fine with internet access and everything else except my mouse. I got lots of help on the Desktop Environment forums, but none of it helped. So I asked a friend here and he suggested upgrading to the 2.6.9-gentoo-r1 kernel.

I did and now my mouse works fine, but I cannot access the internet.

I have searched the forums and tried many different things.

The module for my NIC is loaded on boot, no internet.
I built the driver into my kernel, no internet.
Checked my /etc/conf.d/net, looks like it should according to many posts here, no internet.
Looked at the FAQ about kernel compilation and networking not working. I tried getting rid of ACPI as suggested, no internet.

I am on a network with dhcp, and I have done "rc-update add net.eth0 default" , but still no internet.

Is there something that I am missing here that was posted in these forums? I think that I found just about all the tips that were suggested for this problem, and none of them helped.

I would really appreciate it if someone had another suggestion for me to try.

I'll just keep browsing and searching the forums so that I'll stumble upon something.

Thank you very much for any help that you may provide.

Scott

[ewtrowbr]

please post...

dmesg | grep eth0
lsmod
ifconfig
netstat -r

and make sure in /etc/conf.d/net you have
iface_eth0="dhcp"

erich

[blinkin]

[marsbt]

Hi,
My problem is also similar. I upgraded from kernel 2.6.8-gentoo-r3 to 2.6.9-gentoo-r1. Earlier everything was working fine. But now, I'm not able to access anything outside the network. I cannot ping anything except other PCs in my network.

Any suggestions?

/KS

[ewtrowbr]

correct me if I'm wrong, but I think IEEE-1394 means firewire... This doesn't look like and ethernet card to me. can you send an "lspci"? You probably can't as this requires "emerge pcitools". This must be comething wacky configured in your kernel.

here is what I would do. Boot up with knoppix, which is a tool everybody needs. Use the dmesg, lsmod, and lspci commands to identify your hardware, and what kernel modules work nicely with them. then configure a kernel with support for those modules you need.

gl,
erich

[blinkin]

I did what you are talking about with the Gentoo LiveCD. So I know what the modules are for my nics.

lspci does work, and it tells me that

I have a D-Link RTL8139 which uses the 8139too module,

and

a Davicom Semiconductor 21x4x DEC-Tulip which I had to use the dmfe module with because tulip was not working.

I currently have the two aforementioned modules built into the kernel. I can use them as modules and add them to /etc/modules.autoload.d/kernel-26 if you think that that will make a difference.

I will just go back over my kernel config and check out the help files for now. Hopefully my finger just slipped hen I was on something important. I would hate to have to re-install from the very beginning.

Thank you very much.

Scott

[Peracles]

Having the modules built into the kernel is fine.

You can issue a dmesg and look at the output. Look for ethX where X=0,1,2. The module for the 8139 is 8139too.

# dmesg | less

You should see something like the following:
eth1: RealTek RTL8139 at 0xd400, 00:90:47:02:b6:1e, IRQ 10
eth1: Identified 8139 chip type 'RTL-8100B/8139D'

I saw earlier where you looked for eth0. With the firewire taking eth0, the others will show up as eth1, eth2, etc. Be sure to do an 'ifconfig -a' This shows all interfaces (even ones not configured).

Once you identify the right ethX. Change the lines in /etc/conf.d/net to correspond to your setup.

Now you need to create an /etc/init.d/net.ethX file to correspond to your ethernet nic. Just copy the /etc/init.d/net.eth0 to /etc/init.d/net.ethX

Now issue:
/etc/init.d/net.ethX restart

[blinkin]

I'll try that as soon as I can. I just got back and I was away from computers all weekend. Thank you.

I'll just have to take a closer look at dmesg. I looked over it before, but I probably missed my nic.

Thank you

Scott