[netdrivers] Sundance driver doesn't recognize an OEM Sundance device.

Thu Nov 10 13:00:24 PST 2005

I think your chip is actually an icplus ip100a.

You'll find the datasheet at :

	http://www.icplus.com.tw/Data/Datasheet/IP100A-DS-R14-07052005.pdf

there is a driver for 2.6 floating around called sundance-icplus.c.
Ask google.

I think it is currently slowly merged into sundance.c

Hope this helps

Philippe

TJ wrote :
> Hi,
>     I have an i386 system using an MSI NF7-S2 motherboard which includes 
> an onboard ethernet device which I've been unable to get working. The 
> board is an NForce 2 based board. The ethernet may or may not be the 
> nVidia ethernet included in some NForce 2 chipsets. I don't believe it 
> is, though.
>     I'm currently running Slackware 10.0, 2.6.11.7 kernel. I've tried 
> compiling several different drivers as modules and loading them to see 
> if they recognized the device with no success. I've tried both realtek 
> drivers, the sundance driver, and the forcedeth driver.
>     The output of lspci claims that the device is a sundance, but the 
> device type is unknown. The driver does not recognize it, and the 
> diagnostic program from scyld.com doesn't recognize it 
> <ftp://ftp.scyld.com/pub/diag/starfire-diag.c>.
>     I attempted to upgrade the version of my sundance driver, but the 
> documentation for doing so <http://www.scyld.com/driver_updates.html> 
> has no information for updating a 2.6 kernel. Simply throwing the new 
> sundance.c file, as well as the necessary headers did not work, nor did 
> downloading the <ftp://ftp.scyld.com/pub/network/> directory and running 
> 'make'. If the new driver version does detect this card, could someone 
> point out how to integrate it into a 2.6 kernel, please?
>     I am including as much useful possible output below.
>     Please CC me. I am not on the mailing list.
> 
> Thanks for any input,
> TJ Harrell
> systemloc <nospam>  earthlink.net
> 
> 
> 
> lspci:
> 
> 00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) 
> (rev c1)
> 00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
> 00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
> 00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
> 00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
> 00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
> 00:01.0 ISA bridge: nVidia Corporation: Unknown device 0080 (rev a3)
> 00:01.1 SMBus: nVidia Corporation: Unknown device 0084 (rev a1)
> 00:02.0 USB Controller: nVidia Corporation: Unknown device 0087 (rev a1)
> 00:02.1 USB Controller: nVidia Corporation: Unknown device 0087 (rev a1)
> 00:02.2 USB Controller: nVidia Corporation: Unknown device 0088 (rev a2)
> 00:06.0 Multimedia audio controller: nVidia Corporation: Unknown device 
> 008a (rev a1)
> 00:08.0 PCI bridge: nVidia Corporation: Unknown device 008b (rev a3)
> 00:09.0 IDE interface: nVidia Corporation: Unknown device 0085 (rev a3)
> 00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
> 02:06.0 Unknown mass storage controller: CMD Technology Inc PCI0680 (rev 01)
> 02:07.0 Unknown mass storage controller: Promise Technology, Inc. 20269 
> (rev 02)02:08.0 Ethernet controller: Linksys Network Everywhere Fast 
> Ethernet 10/100 model NC100 (rev 11)
> 02:09.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet 
> Controller (rev 02)
> 02:0a.0 VGA compatible controller: ATI Technologies Inc Rage XL AGP 2X 
> (rev 65)
> 02:0b.0 Ethernet controller: Sundance Technology Inc: Unknown device 
> 0200 (rev 31)
> 
> lspci -nvv (Only the sundance device is shown for brevity):
> 
> 02:0b.0 Class 0200: 13f0:0200 (rev 31)
>         Subsystem: 147b:1c08
>         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 (2500ns min, 2500ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 11
>         Region 0: I/O ports at c400 [size=128]
>         Region 1: Memory at e90c6000 (32-bit, non-prefetchable) [size=512]
>         Expansion ROM at <unassigned> [disabled] [size=64K]
>         Capabilities: [50] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA 
> PME(D0-,D1+,D2+,D3hot+,D3cold+)
>                 Status: D0 PME-Enable- DSel=0 DScale=2 PME-
> 
> pci-config <ftp://ftp.scyld.com/pub/diag/pci-config.c>:
> 
> pci-config.c:v2.05 2/23/2005 Donald Becker (becker at scyld.com)
>  http://www.scyld.com/diag/index.html
> Device #1 at bus 0 device/function 0/0, 01e010de.
> Device #2 at bus 0 device/function 0/1, 01eb10de.
> Device #3 at bus 0 device/function 0/2, 01ee10de.
> Device #4 at bus 0 device/function 0/3, 01ed10de.
> Device #5 at bus 0 device/function 0/4, 01ec10de.
> Device #6 at bus 0 device/function 0/5, 01ef10de.
> Device #7 at bus 0 device/function 1/0, 008010de.
> Device #8 at bus 0 device/function 1/1, 008410de.
> Device #9 at bus 0 device/function 2/0, 008710de.
> Device #10 at bus 0 device/function 2/1, 008710de.
> Device #11 at bus 0 device/function 2/2, 008810de.
> Device #12 at bus 0 device/function 6/0, 008a10de.
> Device #13 at bus 0 device/function 8/0, 008b10de.
> Device #14 at bus 0 device/function 9/0, 008510de.
> Device #15 at bus 0 device/function 30/0, 01e810de.
> 
> _______________________________________________
> netdrivers mailing list
> netdrivers at scyld.com
> http://www.scyld.com/mailman/listinfo/netdrivers
> 