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 tried the Wake on Lan setup. The wakeup-0n-Lan after poweroff was already enabled. Tried to diasable and shutdown, wait 10 seconds, startup. Still the same problem. Changed it back to "Enable". But the same error.
I also tried BIOS setup, which had ROM on lan card enabled. Tried disabling this. Reboot and the same error.
Though it may not have anything to do with the network card issue, let me make my setup clear. I have comcast HS internet and I am connecting it to a netgear router. The router then connects my PC. I even tried connecting directly to the cable-modem and it still doesn't work. Am I missing anything?
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
Slax works with this card. But I can't get my Slackware 2.6.17.13 to work with it yet. I have the same problem, eth0 does not exist when you do ifconfig -a but you can see it in lspci, etc.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
This is a known problem with winbloze putting the NIC to sleep. It was reported in dual boot situations. There is some patch in higher level kernel to wake up the NIC.
The slax works and finds eth0, with the forcedeth driver. The size was a little different. It had the kernel 2.6.27 or something, which is higher than the one that i have 2.6.18. I also compiled lshw on my box. Even that shows the ethernet device. But card doesn't work.
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
It seems to be. I just installed Slackware's 2.6.27.7 kernel on a Slackware 11.0 system and the RTL8201 I have is now recognized. From what I could tell from all the web searches I did, the drivers supplied by the manufacturer are buggy. The later kernel seems to work better.
But I am still getting mostly terrible download performance and I don't know why.
It says "..I have installed 2.6.18-6 and seems it's forcedeth module doesn't support this chipset...I have downloaded kernel sources starting from 2.6.21 up to 2.6.25 and found that this chipset is supported in 2.6.23 and above.."
Does anybody know of forcedeth for kernel 2.6.18 or worked out any solution for mcp73 on 2.6.18?
This is a known problem with winbloze putting the NIC to sleep. It was reported in dual boot situations. There is some patch in higher level kernel to wake up the NIC.
Okay, it is a distro problem i do believe. It works on ubuntu but doesn't work on CentOS 5.3 and/or Fedora Based O/S. I do believe it only has the problem with CentOS. I am trying to fix this problem and I am having trouble and there isn't any good info on how to fix it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.