All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: manfreds@colorfullife.com
Subject: forcedeth as a module only?
Date: Fri, 17 Jun 2005 19:41:39 +0200	[thread overview]
Message-ID: <42B30B53.2060204@g-house.de> (raw)

hi,

are there any known issues with the forcedeth driver when statically
compiled in? i have an onboard GbE ethernet controller (see below) and
forcedeth seems to work pretty fine for this controller. it's 100Mbps
only, but i don't care because my switch is 100Mbps too.

i've noticed that the driver just does not work, when it's compiled with
CONFIG_FORCEDETH=y

eth0: forcedeth.c: subsystem: 01462:0250 bound to 0000:00:05.0
eth0: no link during initialization

recompiling the same kernel (2.6.12-rc6-mm1, x86_64) with
CONFIG_FORCEDETH=m and loading the module without any parameters get the
NIC up. mii-tool does not work in both cases, CONFIG_MII is set to "y".


any hints?

thank you,
Christian.

% lspci -v | grep -A6 0000:00:05.0
0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
        Subsystem: Micro-Star International Co., Ltd.: Unknown device 0250
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 217
        Memory at f8000000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at d800 [size=8]
        Capabilities: [44] Power Management version 2

(the manual says it's a Marvell 88E111 10/100/1000 onboard NIC)

% mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not supported
SIOCGMIIPHY on 'eth1' failed: Operation not supported
no MII interfaces found

% ethtool eth0
Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: externel
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Link detected: yes

-- 
BOFH excuse #334:

50% of the manual is in .pdf readme files

             reply	other threads:[~2005-06-17 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17 17:41 Christian Kujau [this message]
     [not found] <200506171804.j5HI4qoh027680@dbl.q-ag.de>
     [not found] ` <42B31749.90208@g-house.de>
2005-06-17 20:47   ` forcedeth as a module only? Manfred Spraul
2005-06-17 22:22     ` Christian Kujau
2005-06-17 22:36       ` Christian Kujau
2005-06-18 10:44     ` marvin24
2005-06-18 12:53       ` Manfred Spraul

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=42B30B53.2060204@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfreds@colorfullife.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.