I have an Abit I90HD motherboard (ATI 1250 video, HDMI etc.).
The onboard network adapter shows in Windows as RTL8169/8110 (PCI-Express) but the 8169 driver under OpenSuse 10.3 doesn't work so I assume it is a 8110 device.
Does anyone know of a suitable driver? I haven't worked on Linux drivers before so I would prefere to get a ready made one.
Thanks.

how do you that it is not working?

1 the kernel may have 8169 built in or as module then once it is loaded, you have to configure the software....the network install stuff.

so step one

open a shell and get root powers for me

open the file lsmod in your home directory and look for something like this
r8169 25768 0

this proves I am using a module for my kernel and its loaded.

step 2
Pls report if you can not find it. and if so try still in su mode

and see if you can now see it?

step 3

only if the module is now loaded, while in root mode run
ifconfig > ifconfig1.txt

and post the output pls. Note I am being rude but I do not want to see the output until we know r8169 loads

This is not my post but having same issue: Abit Fatal1ty F190 HD, Realtek 8111 NIC onboard. YAST shows "Unable to configure network card because kernel device is not present"

results of: "lsmod | grep r8169"

r8169 32904 0

The driver is listed as 8168 not 8169, there is a linux driver at
http://www.realtek.com.tw/downloads/...L8168/RTL8111C

I put the R8168.ko in /lib/modules/2.6.....-default/kernel/drivers/net and the YaST Hardware Information now reports an ABIT Ethernet controller with the Subvendor Identifier 70779.
There is another stage missing but it's progress.

Trollslayer

look by all means try and solve your own problems, but if you think your equipment is 8169 and you do want to show me the output of your lsmod, I am none the wiser as to why you have decided to download a driver for a 8168?

if you are still having issues lets use su
rmmod r8168
lsmod

also lets

lspci > pci.txt to see what your pci cards are detected as please.

thanks in advance

Thank you both for replying! I was trying to insert r8169 I guess because I thought it was the same driver for 8168, 8169, and 8111. I formatted/reinstalled, then installed the driver that you pointed to in your post for the r8168. I used these commands after untarring the driver:

make clean modules
make install
depmod -a
insmod ./src/r8168.ko


Here is some output afterward:

"lspci | grep Ethernet"
02:00.0 Ethernet controller: Unknown device 0001:8168 (rev 01)

"lsmod | grep r8168"
r8168 47504 0

"ifconfig -a"
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2056 (2.0 Kb) TX bytes:2056 (2.0 Kb)

YAST still says that the kernel device is not present.

OK, progress.
I ran 'lspci' as suggested by Aus9 and it returns "02:00.0 Ethernet controller: Unknown device 001:8168 9rev 01)".
One thing cleared up - Windows uses the same driver for 8169/8110 and 8168/8111, Linux uses different ones, hence the driver I linked to earlier.
The other thing is that Abit treat it as an expansion card so don't use Realtek's PCI vendor ID (0x10EC) but their own (0x147b).
I have changed the PCI_VENDOR_ID to 0x147b but the 8111 still doesn't work.

ok I doubted you so I thought I better have a look myself at your specs abits so called specs page is crap
http://www.uabit.com/index.php?optio...ge=2&model=339

but on the driver page we have Realtek 8111B Gigabit Lan Driver and that appears to be your link above so yep....its a r8168 sorry.

2) now we may be getting somewhere....but it is not clear to me...from looking at the readme that realtek have supplied....that you have understood they have left out some assumptions....

3) they are

your module compile assumes you have a proper full kernel installed or the minimum kernel installed....in /usr/src

normally its a link from /usr/src/linux to some fuller name including the kernel version that will be found in /boot/vmlinuz-version.....

can you tell me both that vmlinuz name and that you really have /usr/src/linux symbolic linked to linux version X pls

AND
some distros use various security apps called selinux / apparmour and a form of prelinking that can make some things difficult


4) but now I know its r8168 and because you say you re-formatted....there was no need just rmmod to get rid of wrong drivers.....lets start again.

take a copy of that r8168 driver and
in bios settings....make sure if you such a setting...its set to non-windows....and another setting is for plugnplay....set it to no
then do a clean install

do not copy r8168 bz2 file yet back pls

5) in root mode (su)

lsmod
lspci

and post results to a file sharing service rather that make it a big post here.

I use www.divshare.com and also www.ripway.com they give you links you can post here.

6) I know this is frustrating....but we want to be on the same page

then
modprobe r8168 (looking for an already compiled module)
lsmod to see if its there....if it is just say so.

7) if its not, the realtek readme has left out some assumptions, but I can only guide you cos mine is r8169...truly

only if its not there....you need proper links in /usr/src/linux to /usr/src/linux-version and you will see a match in /boot/vmlinuz-version

but I do not know your distro well enough to say if we need to disable prelinking and or if you are using selinux or apparmour which can interfere with the stuff you MAY have to do.

ok I found a good guide here cos I do not use suse

http://forums.suselinuxsupport.de/in...e+build+kernel

pls pay attention to this section

BUILDING ADDITIONAL (EXTERNAL) MODULES

A single binary kernel module generally only works for a specific
version of the kernel source tree, for a specific architecture and
configuration. This means that for each binary kernel that SUSE ships, a
custom module must be built. This requirement is to some extent relaxed
by the modversion mechanism: modversions attach a checksum to each
symbol (function or variable) exported to modules by the kernel. This
allows to use kernel modules that have been built for a kernel with a
different version or release number in many cases, as long as none of
the symbols the module uses have changed between the two kernel
versions.
_____________________________

Naturally when you do the install your package manager should be able to find a
kernel-source to install but it may be called something else.

I am not willing to install suse to help....so if the link is not useful to you, please consider starting a new post in the suse forum either lq or the one linked on help to build and use the r8168 driver (module)

Which distro do you use? I am not comitted to Suse, it was just a convenient choice at the time and is not widely supported by MythTV which is my eventual aim so it's probably easier for me to sync. with you.
Thanks.

Mandriva 2008.0 but as you appear open to trying distros can I suggest
http://www.mythtv.org/wiki/index.php/Linux_Distros

www.distrowatch.com is of course the biggie...but it does not appear to think mythtv is worthy of a search pulldown.

you can use google like this
http://www.google.com.au/linux?hl=en...G=Search&meta=

having done some more google....it looks like 8111 is playing up so it may not be the fault of the distro.

try this

http://wiki.sabayonlinux.org/index.p...3.0stable_mini

and sign of success

http://www.murga-linux.com/puppy/vie...php?=&p=128301

if that fails here is another success post 7

http://www.linuxquestions.org/questi...98#post3029998

I saw Ubuntu 7.10 on the cover of a magazzine the other day and tried it - it successfully installed the R8169 driver which works!
Someone at work mentioned aliases for driver which I assume allows a driver to be used with different vendor and device IDs.

Thanks for the help, now I've got the rmeote control, audio, dvd playback etc. to sort