mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: TommyDrum <mycooc@yahoo.it>
To: linux-kernel@vger.kernel.org
Subject: r8169 native module problems on 2.6.11
Date: Sun, 10 Apr 2005 14:16:20 +0200	[thread overview]
Message-ID: <42591914.2000800@yahoo.it> (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 <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-----


             reply	other threads:[~2005-04-10 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 12:16 TommyDrum [this message]
2005-04-10 13:26 ` Francois Romieu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42591914.2000800@yahoo.it \
    --to=mycooc@yahoo.it \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®