Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 had the best luck with the Livna repo for getting nividia cards going.
Using the nvidia sites download causes you more problems in Fedora as it overwrites your xorg.conf and then you are chasing your tail trying to get it sorted.
Nah, what I'm trying to figure out is what happened to the card. Maybe udev has two devices with the same name. That's happened to me once. The "grep" command just searches for a file that has what's being grepped for. We're just trying to figure out what udev has discovered for the ethernet ("eth") devices.
Added:
"lsmod" does have r8169 listed now, right? A quick way to check is "lsmod |grep r8169"
Last edited by Quakeboy02; 01-23-2007 at 10:11 PM.
Did you ever run "dmesg |grep eth"? I've found some other threads on this device but they at least report the thing to dmesg when the module is loaded.
Good grief, I've just read that you have to smash this driver with a large hammer after you load it. From the README file for the Realtek driver and I assume this applies to the r8169:
Quote:
<Force Link Status>
1. Force the link status when insert the driver.
If the user is in the path ~/r1000, the link status can be forced to one of the 5 modes as following command.
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = 0 for half-duplex
= 1 for full-duplex
NWAY_OPTION = 0 for auto-negotiation off
= 1 for auto-negotiation on
For example:
#insmod ./src/r1000.ko speed=100 duplex=0 autoneg=0
will force PHY to operate in 100Mpbs Half-duplex.
2. Force the link status by using ethtool.
a. Insert the driver first.
b. Make sure that ethtool exists in /sbin.
c. Force the link status as the following command.
,where
SPEED_MODE = 1000 for 1000Mbps
= 100 for 100Mbps
= 10 for 10Mbps
DUPLEX_MODE = half for half-duplex
= full for full-duplex
NWAY_OPTION = off for auto-negotiation off
= on for auto-negotiation on
So, it might just easiest for you to install the "ethtool" program and run the following command as root:
Code:
ethtool -s eth0 speed 100 duplex full autoneg on
But I'd still like to see the output from "dmesg |grep eth". That SHOULD tell us where Fedora thinks the card is.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.