linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [tg3] failing to detect NIC when built statically...
Date: Thu, 22 Sep 2005 09:59:56 +0100	[thread overview]
Message-ID: <6278d222050922015937890366@mail.gmail.com> (raw)

I have a PCI express BCM5751 NIC using the tg3 driver. If I build the
driver statically, it fails to identify the network card - no kernel
log messages or anything. It works as expected when built modular.
Platform is x86_64 running native 64bit code.

# lspci -vvxs 2:0.0
0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme
BCM5751 Gigabit Ethernet PCI Express (rev 01)
        Subsystem: Broadcom Corporation NetXtreme BCM5751 Gigabit
Ethernet PCI Express
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 0x08 (32 bytes)
        Interrupt: pin A routed to IRQ 201
        Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=64K]
        Expansion ROM at 40100000 [disabled] [size=64K]
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-
                Address: d258788c36d7592c  Data: f7f6
        Capabilities: [d0] #10 [0001]
00: e4 14 77 16 06 00 10 00 01 00 00 02 08 00 00 00
10: 04 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 00 00 00 e4 14 77 16
30: 00 00 00 00 48 00 00 00 00 00 00 00 0c 01 00 00

Any ideas? Please CC.
___
Daniel J Blueman

                 reply	other threads:[~2005-09-22  8:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=6278d222050922015937890366@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).