forcedeth freezes my NIC. How do I compile newer version?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
That is well documented bug with the forcedeth driver: the NIC dies under heavy load.
I have a RTL8211 and am using the 8139 or whatever driver, the one in the kernel, and I haven't had the problem at all. I guess it occurs on one machine but not necessarily another.
EDIT- what NIC device do you have?
I'm sorry I haven't got any specific links for you, however I recommend using Google to see if there's a newer version, or a patch, for the forcedeth driver, which addresses the issue. If you can't find anything, I'll have a look too for you; I'm currently making supper, but after that, I'll definitely have a look for you if you haven't got anywhere.
Last edited by GrapefruiTgirl; 09-19-2007 at 03:52 PM.
Hi again! I have tried google and I can not find any solution to my problem. I am running forcedeth 0.59 and I think the newest is 0.60, is this small version difference that important? Yes I am very desperate for your help. If you want to I can paste my error messages from gcc when trying to compile the 0.60 version of forcedeth.
I am not sure what NIC I have and how to find out. MSI's webpage says "Dual LAN 10/100/1000 Fast Ethernet by Vitesse VSC8601"
Well, a tiny version change *can* be important, depending on what changed. Generally, a changelog will be included or viewable online, which describes any changes made to code when a new version of something is released.
I have never heard of Vitesse VSC8601. My nVidia board (an MSI also) uses the Realtek GBLan device.
Let me go and have a browse around and see if I can relocate some info on that bug I mentioned, and see if there's a patch or repair.
NOTE: Since the driver is one of the linux kernel's drivers, you wouldn't usually compile it all by itself. It would need to be placed into the source directory, added to the kernel config, and then you would recompile the kernel.
Anyway, before I get ahead of myself, lemme go look around. I'll get back to you.
OK, and, what kernel are you using? Since as I mentioned, this IS a kernel driver, the simplest solution will probably be to download a newer kernel and recompile it. That way, you won't have to go through any weird hoops, and the bug fix will already be incorporated.
If you are using a 2.6.xx kernel, why not upgrade, especially if yours is older than 2.6.22 because as I recall, 188.8.131.52 is whereabouts this issue was addressed.
if you look at this link, you'll see that this is a patch-file, which fixes the forcedeth driver code for the Vitesse PHY driver bug. You could save the patch file and patch it manually, OR simply upgrade to a shiny new kernel
Hi again! I was running 2.6.20-15 and since I was not too keen on compiling, I upgraded to gutsy. Now I am running 2.6.22-11
I have not tested with some heavy network load but if it crashes again I will be back whining more :P But I really think it did the trick! I hereby declare my eternal gratefulness! Thank you for your help!