| View previous topic :: View next topic |
| Author |
Message |
Kvetch
Guru
Joined: 29 Apr 2004
Posts: 318
Location: /dev/null, VA
|
 Posted: Mon Oct 22, 2007 9:09 pm Post subject: Network Issue [SOLVED] |
 |
|
I installed gentoo-sources on a new box yesterday and everything went as normal but upon reboot I noticed that my NIC couldn't talk out. It couldn't ping the gateway nor other machines on that subnet, I had set the IP statically so I thought maybe when the livecd pulled a dhcp address the switch it was on held the dhcp IP in the arp table but that wasn't it and I tried to use dhcp but no go. The NIC is an old Linksys 10/100 that uses the tulip driver which I have built into the kernel. When I boot into the livecd I don't have any network issues. I am using 2.6.23-gentoo-sources on an x86 box. I haven't had a chance to physically get to that box today but would anyone have any ideas what I might be missing that would cause the NIC to be recognized just not route properly, maybe a kernel setting I am somehow overlooking? It has to be something stupid I am overlooking but I just don't see it. My /etc/conf.d/net settings are correct, no typos.
Thanks and sorry for the vague question,
Nick
Last edited by Kvetch on Thu Oct 25, 2007 5:10 pm; edited 1 time in total |
|
| Back to top |
|
 |
CrankyPenguin
Apprentice
Joined: 19 Jun 2003
Posts: 283
|
| Posted: Mon Oct 22, 2007 9:13 pm Post subject: Basic starting points. |
|
|
1) Dmesg, check for anything with "tulip" and "eth0" to ensure that the driver is finding the card and vice-versa.
2) Check ifconfig -a to ensure that the card is properly configured.
3) Assuming that you specified the tulip driver in the kernel there isn't much that should "block" it.
4) As a final point did you install any firewall? If so check to ensure that is properly configured.
_________________
Linux, the OS for the obsessive-compulsive speed freak in all of us. |
|
| Back to top |
|
|
nixnut
Bodhisattva
Joined: 09 Apr 2004
Posts: 10974
Location: the dutch mountains
|
| Posted: Tue Oct 23, 2007 3:56 pm Post subject: |
|
|
Moved from Installing Gentoo to Networking & Security.
postinstallation networking problem, so moved here.
_________________
Please add [solved] to the initial post's subject line if you feel your problem is resolved. Help answer the unanswered
talk is cheap. supply exceeds demand |
|
| Back to top |
|
|
Kvetch
Guru
Joined: 29 Apr 2004
Posts: 318
Location: /dev/null, VA
|
| Posted: Wed Oct 24, 2007 3:46 am Post subject: |
|
|
Hmm, I am not sure what is going on here. My motherboard has an onboard NIC which is set to disabled. I have 3 other Linksys PCI NIC cards in my machine. 1 Linksys 10/100 ver.5.1, and 2 Linksys 10/100 ver.4.1. The two 4.1 cards are going to be bonded once I can get everything working smoothly.
Upon bootup I am getting an error saying eth0 doesn't exist please verify the module is loaded. If I symlink net.lo to make a net.eth1 and start eth1 the top most NIC (v5.1) works. I am not sure what is failing on bootup but the MAC is not the onboard NIC, so it must be the 2nd or 3rd NIC. I am just not sure why it would fail since it too is a Linksys that uses the tulip module and why would it make eth0 instead of the top most card that the LiveCD also sees as eth0. I know these cards use to work fine in older 2.6 kernels.
| Code: | # dmesg|grep eth0
eth0: ADMtek Comet rev 17 at Port 0xd000, 00:04:5A:66:A8:B7, IRQ 16.
net eth0_rename: device_rename: sysfs_create_symlink failed (-17) |
Kernel config does have tulip loaded.
| Code: | CONFIG_NET_TULIP=y
CONFIG_TULIP=y |
dmesg output
| Code: | eth0: forcedeth.c: subsystem: 01565:2301 bound to 0000:00:04.0
Linux Tulip driver version 1.1.15 (Feb 27, 2007)
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC3] -> GSI 18 (level, high) -> IRQ 17
tulip0: MII transceiver #1 config 3100 status 7849 advertising 05e1.
tulip0: MII transceiver #2 config 1000 status 7849 advertising 05e1.
tulip0: MII transceiver #3 config 1000 status 7849 advertising 05e1.
tulip0: MII transceiver #4 config 1000 status 7849 advertising 05e1.
eth1: ADMtek Comet rev 17 at Port 0xd000, 00:04:5A:66:A8:B7, IRQ 17.
ACPI: PCI Interrupt Link [APC4] enabled at IRQ 19
ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 18
tulip1: MII transceiver #1 config 1000 status 7849 advertising 01e1.
eth2: ADMtek Comet rev 17 at Port 0xd400, 00:04:5A:55:E5:65, IRQ 18.
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 19
tulip2: MII transceiver #1 config 1000 status 7849 advertising 01e1.
eth3: ADMtek Comet rev 17 at Port 0xd800, 00:04:5A:58:5F:45, IRQ 19.
|
For right now I took the easy way out and enabled the onboard NIC and then put a 3Com card in and took the two Linksys 4.1 cards out. When I can I will messed around with it some more. Everything I read seems to point to some APIC issues. |
|
| Back to top |
|
|
Kvetch
Guru
Joined: 29 Apr 2004
Posts: 318
Location: /dev/null, VA
|
| Posted: Wed Oct 24, 2007 4:01 am Post subject: |
|
|
Ok now I am confused. I took out the two NIC cards and I am still seeing
| Code: | forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
eth0: forcedeth.c: subsystem: 01565:2301 bound to 0000:00:04.0
eth1: ADMtek Comet rev 17 at Port 0xd000, 00:04:5A:42:6E:77, IRQ 17.
eth2: ADMtek Comet rev 17 at Port 0xd400, 00:04:5A:66:A8:B7, IRQ 18.
net eth2_rename: device_rename: sysfs_create_symlink failed (-17)
net eth4: device_rename: sysfs_create_symlink failed (-17)
net eth1: device_rename: sysfs_create_symlink failed (-17)
|
I created a eth2,3 & 4. eth2 & eth3 wouldn't come up when I did an ifconfig ethX up.
| Code: | eth0 Link encap:Ethernet HWaddr 00:04:4B:80:70:23
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:75 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7971 (7.7 Kb) TX bytes:8081 (7.8 Kb)
Interrupt:16 Base address:0x2000
eth1 Link encap:Ethernet HWaddr 00:04:5A:66:A8:B7
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18 Base address:0xd400
eth4 Link encap:Ethernet HWaddr 00:04:5A:42:6E:77
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:2
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xd000 |
So confused on what the fudge is going on here. Why does it show 2 ADMtek cards. I believe admtek was the Linksys 4.1 cards and now it is the 5.1 Linksys card and the 3Com card? |
|
| Back to top |
|
|
Kvetch
Guru
Joined: 29 Apr 2004
Posts: 318
Location: /dev/null, VA
|
| Posted: Wed Oct 24, 2007 4:20 am Post subject: |
|
|
| Could the udev 70-persistent-net rules be wrong? And somehow not cleared out? |
|
| Back to top |
|
|
Kvetch
Guru
Joined: 29 Apr 2004
Posts: 318
Location: /dev/null, VA
|
| Posted: Thu Oct 25, 2007 5:11 pm Post subject: |
|
|
| I removed 70-persistent-net rebooted and everything came back. Swapping NIC's just seemed to mess things up. |
|
| Back to top |
|
|
|
Networking & Security
