Debian Wheezy 2.6n install on GX620

Drivers? How do I install the drivers?

The drivers for the GX620, I can't seem to find anything for installing drivers on Debian other than video cards.

You shouldn't need any. (Your not in Windoze any more)

Is there something that isn't working? If something isn't working on your Dell, try Googling some more generic Linux websites.

I have a GX620 on the desk beside me. I have not tried Wheezy on it, but it didn't have any trouble installing the older Linuxcnc live CDs. I never got good latency numbers off it, but I didn't really try either. (I only used it for testing and setting up new configurations for other machines, so I didn't care if it had bad latency.)

Ubuntu 12.04 everything work. With debian it seems my NIC is not working.

This is a bit like pulling teeth

What NIC is it?

Debian does not install non-free packages by default, for copyright reasons they are not part of a distro

so

firmware-linux-nonfree
firmware-realtek
firmware-ralink

and many others are not there unless you installed them

With some later realtek chips you may even need to fetch the package from Jessie to get the extra firmware files
(however I think these have made their way into the backports, if not the main Wheezy files, so don't try that unless you know you have files missing)

regards

The Net work Interface card is built onto the motherboard. How do I tell what NIC it actually is? According to Dell's web site it should be a Broadcom 57XX series card. I dont know how to tell what Debian thinks is installed in the PC.

How do I tell what NIC it actually is?

sudo lspci -vv > lspci.txt
in a terminal and attach the resultant lspci.txt file.

dmesg | grep eth should give some info about what happened at boot too

Here is this, the grep command didnt show anything.

Well either I am going blind or there is no Ethernet controller showing up

I am expecting to see something like

Ethernet controller [0200]: Intel Corporation NM10/ICH7 Family LAN Controller [8086:27dc] (rev 01)

Do dmesg > dmesg.txt and attach the whole file, maybe the reason the dmesg | grep eth did not produce anything is that either the kernel does not detect it, it is broken or not present.