Bug 145538 - D-Link DGE-530T not detected (sk98lin)
Summary: D-Link DGE-530T not detected (sk98lin)
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: hwdata (Show other bugs)
(Show other bugs)
Version: 4.0
Hardware: i686 Linux
Target Milestone: ---
: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
Depends On:
Blocks: 137160
TreeView+ depends on / blocked
Reported: 2005-01-19 15:08 UTC by Pascal de Bruijn
Modified: 2014-03-17 02:51 UTC (History)
3 users (show)

Fixed In Version: RHBA-2005-120
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-09 13:01:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:120 normal SHIPPED_LIVE hwdata bug fix update 2005-06-09 04:00:00 UTC

Description Pascal de Bruijn 2005-01-19 15:08:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
I've recently purchased a D-Link DGE-530T Gigabit Copper Ethernet
adapter. The card is based on the newer Marvell Yukon chip:

It used the sk98lin driver:
When I modprobe sk98lin I get this"

eth0: DGE-530T Gigabit Ethernet Adapter
      PrefPort:A  RlmtMode:Check Link State
Then I can ifconfig eth0, and everything works fine...

MY PROBLEM: kudzu won't autodetect the card.

lspci -vv for the DGE-530T:
00:0a.0 Ethernet controller: D-Link System Inc Gigabit Ethernet
Adapter (rev 11)
	Subsystem: D-Link System Inc DGE-530T Gigabit Ethernet Adapter
	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: 32 (5750ns min, 7750ns max), Cache Line Size 08
	Interrupt: pin A routed to IRQ 185
	Region 0: Memory at e3800000 (32-bit, non-prefetchable) [size=16K]
	Region 1: I/O ports at b800 [size=256]
	Capabilities: [48] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [50] Vital Product Data

I also noticed that the driver is quite outdated, a newer 7.09 is
available here:
It has some nice new features like NAPI.

Version-Release number of selected component (if applicable):
kernel 2.6.9-1.675 SMP

How reproducible:

Steps to Reproduce:
1. Install the card.
2. Boot the machine

Actual Results:  The card isn't autodetected.

Expected Results:  The card should be autodetected by kudzu.

Additional info:

Comment 3 Bill Nottingham 2005-01-19 21:07:43 UTC
Added in CVS. 

Comment 4 Bill Nottingham 2005-03-01 17:57:22 UTC
In 0.146.2.EL-1.

Comment 5 Pascal de Bruijn 2005-03-07 19:02:39 UTC
I'm running 2.6.9-5.0.3.EL now, the card still isn't detected.

Also any chance, of seeing the sk98lin card officially supported? with
newer driver versions?

If you need any more information please lett me know...

Comment 6 Bill Nottingham 2005-03-07 19:44:30 UTC
If you manually load the driver does it work? The fix is in
hwdata-0.146.2.EL-1 to manually set a mapping for it, since the driver
doesn't export tables of what cards it supports.

Comment 7 Pascal de Bruijn 2005-03-07 21:00:41 UTC
When I manually load it, it works...

Also, If I'm not mistaken, a while back, I patched my kernel with the
newer sk98lin driver, and I think kudzu detected it back then...

Anyway, like I said before, I can really recommend the newer driver...

Thanks for the assistance,
Pascal de Bruijn

Comment 8 Tim Powers 2005-06-09 13:01:12 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.