mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* r8169 native module problems on 2.6.11
@ 2005-04-10 12:16 TommyDrum
  2005-04-10 13:26 ` Francois Romieu
  0 siblings, 1 reply; 2+ messages in thread
From: TommyDrum @ 2005-04-10 12:16 UTC (permalink / raw)
  To: linux-kernel

-----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 <netdev@oss.sgi.com>
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-----


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: r8169 native module problems on 2.6.11
  2005-04-10 12:16 r8169 native module problems on 2.6.11 TommyDrum
@ 2005-04-10 13:26 ` Francois Romieu
  0 siblings, 0 replies; 2+ messages in thread
From: Francois Romieu @ 2005-04-10 13:26 UTC (permalink / raw)
  To: TommyDrum; +Cc: linux-kernel

TommyDrum <mycooc@yahoo.it> :
[new brand of r8169 adapter coming into town]
> 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.

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.

> 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.

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: netdev@oss.sgi.com on further messages.

--
Ueimor

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-04-10 13:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-04-10 12:16 r8169 native module problems on 2.6.11 TommyDrum
2005-04-10 13:26 ` Francois Romieu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®