Contact-DXM Posted February 21, 2007 Share Posted February 21, 2007 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:~# Link to comment
BillK Posted February 21, 2007 Share Posted February 21, 2007 Do any LED lights on your NICS come on and/or flash? I clipped the following screenshot from my motherboard manual to help clarify: Link to comment
Joe L. Posted February 21, 2007 Share Posted February 21, 2007 The response to his ifconfig command seems to indicate the chipset on his NIC is not one Tom has included a driver for in the current distribution. Tom has on occasion offered to add drivers for NIC cards, perhaps he will chime in here and offer again. Otherwise, the answer is to use a supported card. Link to comment
Contact-DXM Posted February 21, 2007 Author Share Posted February 21, 2007 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... ) Link to comment
Contact-DXM Posted February 21, 2007 Author Share Posted February 21, 2007 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.) Link to comment
Joe L. Posted February 21, 2007 Share Posted February 21, 2007 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.) Since you seem pretty familiar with UNIX, you might see if you can find a loadable device driver for your network card somewhere on the web. Then, add it to your flash drive, and add a line to the end of the 'go' script to insmod it. No matter what... post your motherboard and NIC card "model numbers" here, so Tom might see what he can do to help. Joe L. Link to comment
Contact-DXM Posted February 21, 2007 Author Share Posted February 21, 2007 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" Link to comment
Contact-DXM Posted February 21, 2007 Author Share Posted February 21, 2007 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. Link to comment
rasputinreborn Posted February 28, 2007 Share Posted February 28, 2007 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:~# I get the same results; am using an Asus K8VSE Deluxe - the onboard LAN is Marvell 88E8001. I also tried a D-Link DGE 530T which has the Marvell 88E8003 I believe. Thanks for any help in advance... Link to comment
limetech Posted February 28, 2007 Share Posted February 28, 2007 Contact-DXM - sorry to say driver for that chip isn't built into unRAID. rasputinreborn - that chip should be supported. Try typing this: modprobe sk98lin ifconfig eth0 Link to comment
rasputinreborn Posted February 28, 2007 Share Posted February 28, 2007 Okay, I got the driver installed with modprobe, but still need to install it permanently. Also I've done ifconfig eth0 up and so on.. but I can't get dhcp to work via dhcpd. Argh, linux. Link to comment
Contact-DXM Posted February 28, 2007 Author Share Posted February 28, 2007 Contact-DXM - sorry to say driver for that chip isn't built into unRAID. Aww... Guess I'm off to newegg. Link to comment
rasputinreborn Posted March 1, 2007 Share Posted March 1, 2007 So... I know I'm showing off my linux noobness but is there a concise walkthrough on configuring the NIC so it and DHCP just work on bootup? Link to comment
rasputinreborn Posted March 6, 2007 Share Posted March 6, 2007 Well Tom, you can see from my travails here: http://lime-technology.com/forum/index.php?topic=506.0 that I am not having an easy time getting this NIC (that you say is supported) working right automatically on boot... Any insight you can provide is appreciated! I'd rather not have to buy a new NIC when what I have can work, but I am almost to that point. I now realize that my problem is that my flash key isn't being fully mounted. See above link for more info. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.