nForce4 - no network - please help

[strmtrupr2]

Hi,

I have a Shuttle SN25P with an nForce4 chipset, and an AMD Athlon 64 Proc.
I am attempting to get Fedora Core 4 working. However, the network doesn't work

I tried using the 2.6.15-1.1830_FC4 kernel with the FORCEDETH enabled but that didn't work. I got the idea from here: http://gentoo-wiki.com/HARDWARE_Shuttle_SN25P#Ethernet

I tried using the nVidia drivers with no luck:
http://www.nvidia.com/object/linux_n..._1.0-0310.html

I then tried the above two things with the 2.6.14 kernel. No luck.
Every time the card comes up OK but it can't get an IP address. If I use static assignments, I can't ping the gateway even. There is a link light, and I have changed the cable.

The 2.6.15-1.1831_FC4 kernel doesn't boot at all, so don't try that one.

I don't know what else to try. Could anyone point me in the right direction?

Thanks!!!

Scott

Here is my lspci:
00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 TurboCache] (rev a1)
02:00.0 Ethernet controller: D-Link System Inc: Unknown device 4b00 (rev 10)
05:06.0 Multimedia audio controller: VIA Technologies Inc. VT1720/24 [Envy24PT/HT] PCI Multi-Channel Audio Controller (rev 01)
05:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)

[bweekes]

I noticed many have looked at your post but none have replied. So, I'll give it a try...

The Shuttle sn25p (sweet machine) is supported by FC 32&64bit 4/5 with Athlon 64 X2 CPUs. I had it running with FC4 32bit for 1 month and then replaced it with 64bit for 5 months. The only problems I initially had were sound and cool-n-quite support. These were resolved with BIOS (ran Shuttle driver CD under windows for this), kernel and alsa updates as they came out. The only feature I wish I could have used with FC4 is the Nvidia hardware RAID. I recently upgraded to FC5 64bit (wife loves it btw) and the installer recognized the hardware RAID1 of my SATA2 drives and everything works w/o issue. For both FC4/5, I never had to use the FORCEDETH you referenced.

I assume you are trying to use DHCP. If you are not having any luck getting a dynamic IP address, try assigning a static IP if you haven't already. You may want to try this and see if it works to rule out any DHCP issues with your switch or router. Some things that would be of help to help others analyze the problem are the output of the following commands run as root:
ifconfig -a
netstat -nr
ethtool eth0
cat /etc/sysconfig/network-scripts/ifcfg-eth0

[strmtrupr2]

Hi,

With my time running out, I tried other distros until I found one that worked out of the box and ended up with Suse. It works... My heart is still with Fedora. I am running it under VMware on that box

Thanks for your reply.

Scott

[namenlos]

I found this post after troubleshooting my own machine. It ultimately led to success, so I thought I'd post my findings.

I took one of bweekes' suggestions and ran 'ethtool eth0' to find out that the driver thought it could negotiate at 1G/s, but I've never managed to get that high even on windows (I'm almost certain the board won't even do it).

I forced 100M/full duplex negotiation in my ifcfg-eth0, brought the network back up, and viola! I am now on the internet.

If anybody's curious, here's the line I dropped into the config:

ETHTOOL_OPTS="speed 100 duplex full autoneg off"