Skip to contentSkip to conversation

r8169 native module problems on 2.6.11

DISCUSSION TommyDrum 2 participants 3 messages Apr 10, 2005 – Apr 11, 2005 2 messages not in the archive

Subsystems (2)
lore
Share & tools
lore

TommyDrum

author
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello, I've got a problem with usrobotics r8169 based gigabit ethernet; kernel module doesn't properly startup, with modprobe r8169; module gets correctly loaded, but ifconfig doesn't see it, and startup scripts deny existence of an eth0 dev; meanwhile the r8169 module taken from the cdrom compiles installs and functions correctly; here's the modinfo for both:

kernel native module:

author:         Realtek and the Linux r8169 crew <[email protected]>
description:    RealTek RTL-8169 Gigabit Ethernet driver
parmtype:       media:array of int
parmtype:       rx_copybreak:int
parmtype:       use_dac:int
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot.
license:        GPL
version:        2.2LK
vermagic:       2.6.11-gentoo-r5 preempt PENTIUMIII gcc-3.3
depends:
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
srcversion:     017DC70C1E25F3AB2CA0324

USrobotics cdrom module:

author:         Realtek
description:    U.S. Robotics 10/100/1000 PCI NIC driver
license:        GPL
vermagic:       2.6.11-gentoo-r5 preempt PENTIUMIII gcc-3.3
depends:
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*

and dmesg for both:

kernel native:

ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: U.S. Robotics 10/100/1000 PCI NIC driver version 2.0 at 0xe08ee000, 00:c0:49:f2:86:1e, IRQ 11
eth0: Auto-negotiation Enabled.

USR module:

ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: U.S. Robotics 10/100/1000 PCI NIC driver version 2.0 at 0xe08e6000, 00:c0:49:f2:86:1e, IRQ 11
eth0: Auto-negotiation Enabled.

I don't understand exactly the difference between the two, thought I could help by posting this fact. Please if you find it irrelevant don't flame me, since it's my first post to the kernel mailing list, I'd welcome any suggestions and I will try to post any other information you request.

Keep on the good work,
Ciao!

Tommy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCWRkRgpUvhTIUBAERApE1AJ9aju0Np0VWGD8ItP30fchnXSwSfQCeLbS4 1EimT1GM7TfC2yWrurNFg24=
=j5ge
-----END PGP SIGNATURE-----

#1 lore raw

TommyDrum <[email protected]> :
[new brand of r8169 adapter coming into town]

Quoted 7 lines

and dmesg for both:

kernel native:

ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: U.S. Robotics 10/100/1000 PCI NIC driver version 2.0 at

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Quoted 2 lines

0xe08ee000, 00:c0:49:f2:86:1e, IRQ 11
eth0: Auto-negotiation Enabled.

Can you check that the message above is _really_ the output of your native kernel ? I have not checked gentoo's sources but the real vanilla kernel can not issue this string.

Quoted 8 lines

USR module:

ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 11 (level, low) -> IRQ 11
eth0: Identified chip type is 'RTL8169s/8110s'.
eth0: U.S. Robotics 10/100/1000 PCI NIC driver version 2.0 at 0xe08e6000, 00:c0:49:f2:86:1e, IRQ 11
eth0: Auto-negotiation Enabled.

Quoted 5 lines

I don't understand exactly the difference between the two, thought I could help by posting this fact. Please if you find it irrelevant don't flame me, since it's my first post to the kernel mailing list, I'd welcome any suggestions and I will try to post any other information you request.

You can send for both working/non-working after module insertion (wait for a few seconds):
- complete dmesg (the beginning of it could be in /var/log/dmesg or such)
- lspci -vx
- lsmod
- ifconfig -a
- ethtool eth0
- cat /proc/interrupts
- source code

Also:
- brand name of the motherboard
- the name given by USR to the adapter (check the box)

I do not mind if the info is mailed, available on some web site or stuffed at bugzilla.kernel.org. Please Cc: [email protected] on further messages.

--
Ueimor

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#4 lore raw

Re: r8169 native module problems on 2.6.11 [SOLVED]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

O/H Francois Romieu έγραψε:

| Ok, new pci id, no wonder it does not work. Can you give the attached patch
| a quick but carefull test on your vanilla kernel ?

Wasn't too quick, sorry, had to supper (very long, I admit it!). It's modprobed very quick (much faster than the USR provided module) and works pretty good up 'til now; dmesg is clean, lspci also, and cat /proc/interrupts doesn't show any conflicts. ifconfig also seems to be in line, and the interface is up and running smoothly.
IMO all is quiet on this front ;)

I forwarded last message to netdev, also do it with this one.

Keep up the good work Francois, and thanks really a lot!

A presto!
Tommy

P.S. Any other info needed, I'll be glad to provide.

| ------------------------------------------------------------------------
|
| --- a/drivers/net/r8169.c	2005-04-10 18:45:05.200274476 +0200
| +++ b/drivers/net/r8169.c	2005-04-10 18:52:41.197933777 +0200
| @@ -176,6 +176,7 @@ const static struct {
|  static struct pci_device_id rtl8169_pci_tbl[] = {
|  	{0x10ec, 0x8169, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
|  	{0x1186, 0x4300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
| +	{0x16ec, 0x0116, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0},
|  	{0,},
|  };
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCWcRCgpUvhTIUBAERArnEAJ9A8/LbF2Mra0pVJS9Lcp+hg0pZ4wCeKAsu N4L1zAsNmRg15EQOuqcPmEE=
=S2E/
-----END PGP SIGNATURE-----