Contact-DXM

Aww... Guess I'm off to newegg.

Not to sound rude or anything, but is there a progress update?

I suppose I'm eagerly awaiting it aswell. I kind of need the 2.6.x kernel for the added hardware support. (my server hardware isn't supported in 2.4.x :'( )

Welp, I'm back. I don't usually use *nix, I've just played around with it a few times. I opened up my server case and looked around for chip numbers. Near the NIC I found a chip named "VT6103". That chip is a "Fast Ethernet 10 / 100 1-Port PHY / Transceiver". Guess that means it has to be the chip for the network card? I wonder why in the bios it says the onboard NIC is a VIA-3043. Anyway... after doing a little searching (~2 hours), apparently the VIA Rhine drivers have a bug with the VT6103 when using the older kernels - I think.. was fixed in one of the 2.5.x revisions methinks. There was a "patch" released for it... but I seemed to have exited the window before I could get a link. I think what I quoted below is relevant but I might be wrong. (Going out on a limb here, don't know very much about linux and only a little about PCs) From "Pedro A. Gracia Fajardo" <> Subject [PATCH] Added VIA 6103 10/100Mbps Phyceiver in sis900.c Date Tue, 22 Apr 2003 12:11:56 +0100 Digg This The actual driver can't find the VIA 6103 Phyceiver in PC CHIPS M810D MOBOs. I used the mii_chip_table from etherboot project. --- sis900.c 2003-04-22 09:39:29.000000000 +0100 +++ sis900.c-via6103 2003-04-22 11:50:36.000000000 +0100 @@ -125,6 +125,7 @@ { "ICS LAN PHY", 0x0015, 0xF440, LAN }, { "NS 83851 PHY", 0x2000, 0x5C20, MIX }, { "Realtek RTL8201 PHY", 0x0000, 0x8200, LAN }, + { "VIA 6103 PHY", 0x0101, 0x8f20, LAN }, {0,}, }; Regards, Pedro -- Pedro A. Gracia Fajardo Instituto Tecnológico de Energías Renovables (ITER) Anyway... I guess that means it's a little too much work to get the onboard NIC running. In a little while I will start searching for a linux driver for my Linksys NIC. On another note... I suppose a 2.6.x version of unRAID is going to be released soon... That would effectively solve my problem methinks. Hmm, wonder when its going to be released.

Thats for the suggestion Joe, when I get back from school I'll look more into it. The motherboard I am using is a "Chaintech SK8T800". In the bios it said the LAN controller was a VIA-3043 me thinks The NIC I tried to use instead of the onboard was a "Linksys EtherFast 10/100 LAN Card. Model No.: LNE100TX Version 5.1"

Sigh... I couldn't find any other NICs in my house. :'( I guess my only option is to wait for what Tom has to say. (I don't want to spend $20 on a new NIC if I don't need to, I'm a poor kid.)

Thanks for the responses. Yes, the lights on the NICs come on. If I use the onboard LAN (VIA-3043), the orange light will come on indicating a 100mbps link and the green Link/Act light will blink. When I plug in my PCI NIC card (disabled the onbaord LAN in bios), the orange 100mbps light comes on and the green Link/Act will light up and blink. That card is a "Linksys EtherFast 10/100 LAN Card. Model No.: LNE100TX Version 5.1" I guess I'll try and hunt down another NIC to replace this one with. (I think I only have linksys though... )

Hi, Welp, after troubleshooting unRAID for a while I finally got it to boot correctly - I think. Now the problem is that I can't seem to connect to my network. I tried out two separate NICs and neither seems to work. I can't telnet tower nor connect via the webbrowser. When I first boot up unRAID I get the prompt for "Tower login:". If I login using "root" and type in "ifconfig eth0" I get a response saying it the device was not found. Not sure what the problem is. Starting Network Interface Plugging Daemon: eth0. Welcome to Linux 2.4.33 (tty1) Tower login: root Linux 2.4.33 root@Tower:~# ifconfig eth0 eth0: error fetching interface information: Device not found root@Tower:~#