Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a gigabyte GA-M57SLI-S4 motherboard, AMD 4200+ X2 CPU so i downloaded the SuSE 10.1 64 bit edition DVD because i liked SuSE 10 on my old 32 bit system (currently kaput)
For the life of me i cannot get my onboard NIC to work. I understand people have been having this problem, but i havent found a solution that works for me.
I CAN, however, pick up the card when i fresh install and when i do an ifconf i can tell its not contacting my DHCP b/c of the 169 address. i can set all the settings manually, but it has no effect on the connectivity - still none.
I know the card works b/c i dual boot and Windows is fine so i'm blameing the drivers at this stage... only i can't get any non forcedeth drivers, and previous releases of forcedeth from nvidia.com don't work.
Please help, its the only thing stopping me permenantly removing Windows - now thats desperation.
I think you might be experiencing the problem with forcedeth drivers described here. This problem is caused by MS leaving the NIC in a state that older forcedeth drivers couldn't handle. Note that a simple power down won't work. You have to actually remove power, or in the case of a laptop remove the battery.
Quote:
Originally Posted by boombastic_007
I had the same issue with Suse... This is an issue with the forcedeth driver. To get it to work correctly you need to shutdown the pc and unplug the power cord, wait for a few seconds plug it back in and boot straight into linux...
I installed an additional nic card to resolve this.
The issue seems to have now been fixed in kernel 2.6.16.21-0.21-default. Try updating the kernel.
phew, thanks for responding, i thought noone was gonna reply there for a second. i'll give it a whirl. -ps i havent come across this solution before, awesome
:: UPDATE, it works, that was EXACTLY the problem. now i just gotta update the kernel, thx again
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.