From: Albert Cranford <ac9410@bellsouth.net>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: ethernet tulip misdetected starting 2.5.20
Date: Mon, 03 Jun 2002 20:43:01 -0400 [thread overview]
Message-ID: <3CFC0D15.9F03AD36@bellsouth.net> (raw)
2.5.19 works while 2.5.20 has mostly correct lspci output (PME- instead of PME+)
but the wrong driver gets detected and fails loading.
Similar to 3c509 vs 3c590 from Anton.
Anyone have any ideas in troubleshooting this?
Config:
CONFIG_NET_TULIP=y
# CONFIG_DE2104X is not set
CONFIG_TULIP=m
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_DE4X5 is not set
linux-2.5.19
dmesg
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Found IRQ 11 for device 00:0b.0
eth0: ADMtek Comet rev 17 at 0xe800, 00:03:6D:16:4E:39, IRQ 11.
lspci -vv
00:0b.0 Ethernet controller: Bridgecom, Inc: Unknown device 0985 (rev 11)
Subsystem: Bridgecom, Inc: Unknown device 0574
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 255 min, 255 max, 32 set, cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e800 [size=256]
Region 1: Memory at e3001000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME+
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
------------------
linux-2.5.20
dmesg
Linux Tulip driver version 1.1.13 (May 11, 2002)
PCI: Found IRQ 11 for device 00:0b.0
tulip0: MII transceiver #1 config 1000 status 786d advertising 01e1.
eth0: Digital DS21140 Tulip rev 17 at 0xe800, EEPROM not present, 00:4C:69:6E:75:79, IRQ 11.
lspci -vv
00:0b.0 Ethernet controller: Bridgecom, Inc: Unknown device 0985 (rev 11)
Subsystem: Bridgecom, Inc: Unknown device 0574
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 255 min, 255 max, 32 set, cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at e800 [size=256]
Region 1: Memory at e3001000 (32-bit, non-prefetchable) [size=1K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- AuxPwr- DSI- D1+ D2+ PME+
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--
Albert Cranford Deerfield Beach FL USA
ac9410@bellsouth.net
next reply other threads:[~2002-06-04 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 0:43 Albert Cranford [this message]
2002-06-04 2:15 ` Andrew fix it: ethernet tulip misdetected starting 2.5.20 Albert Cranford
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=3CFC0D15.9F03AD36@bellsouth.net \
--to=ac9410@bellsouth.net \
--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 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.