Integrated ethernet on SiS chipset doesn't work

Integrated ethernet on SiS chipset doesn't work

[Jean Francois Martinez]

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

I have a friend who owns a computer manufactured by Medion and who
sports an MSI motherboard who has a SiS chipset.  The MSI motherboard 
seems to have ben made specially for Medion since it isn't 
referenced on MSI's site.  The problems is that the integrated ethernet
doesn't work at all under Linux be it with 2.4 or 2.6 kernel.  He can't 
ping or connect to other boxes.  His ethernet works when he boots
Windows.

I include the output of lspci



[-- Attachment #2: lspcin.txt --]
[-- Type: text/plain, Size: 462 bytes --]

00:00.0 Class 0600: 1039:0648 (rev 50)
00:01.0 Class 0604: 1039:0003
00:02.0 Class 0601: 1039:0008 (rev 14)
00:02.3 Class 0c00: 1039:7007
00:02.5 Class 0101: 1039:5513
00:02.7 Class 0401: 1039:7012 (rev a0)
00:03.0 Class 0c03: 1039:7001 (rev 0f)
00:03.1 Class 0c03: 1039:7001 (rev 0f)
00:03.2 Class 0c03: 1039:7001 (rev 0f)
00:03.3 Class 0c03: 1039:7002
00:04.0 Class 0200: 1039:0900 (rev 91)
00:07.0 Class 0780: 8086:1040
01:00.0 Class 0300: 10de:0314 (rev a1)

[-- Attachment #3: lspciv.txt --]
[-- Type: text/plain, Size: 6727 bytes --]

00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS 645xx (rev 50)
	Subsystem: Silicon Integrated Systems [SiS] SiS 645xx
	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
	Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=128M]
	Capabilities: <available only to root>

00:01.0 PCI bridge: Silicon Integrated Systems [SiS]: Unknown device 0003 (prog-if 00 [Normal decode])
	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: 64
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	Memory behind bridge: e8000000-e9ffffff
	Prefetchable memory behind bridge: d0000000-dfffffff
	BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-

00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 (rev 14)
	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: 0

00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller (prog-if 10 [OHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 785d
	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 (1000ns min, 3000ns max)
	Interrupt: pin B routed to IRQ 9
	Region 0: Memory at eb405000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: <available only to root>

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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: 128
	Interrupt: pin ? routed to IRQ 5
	Region 4: I/O ports at 4000 [size=16]
	Capabilities: <available only to root>

00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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 (13000ns min, 2750ns max)
	Interrupt: pin C routed to IRQ 3
	Region 0: I/O ports at e000 [size=256]
	Region 1: I/O ports at e400 [size=128]
	Capabilities: <available only to root>

00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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 (20000ns max), cache line size 08
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at eb400000 (32-bit, non-prefetchable) [size=4K]

00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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 (20000ns max), cache line size 08
	Interrupt: pin B routed to IRQ 3
	Region 0: Memory at eb401000 (32-bit, non-prefetchable) [size=4K]

00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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 (20000ns max), cache line size 08
	Interrupt: pin C routed to IRQ 5
	Region 0: Memory at eb402000 (32-bit, non-prefetchable) [size=4K]

00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 7850
	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 (20000ns max)
	Interrupt: pin D routed to IRQ 11
	Region 0: Memory at eb403000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: <available only to root>

00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 91)
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 785c
	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 (13000ns min, 2750ns max)
	Interrupt: pin A routed to IRQ 11
	Region 0: I/O ports at e800 [size=256]
	Region 1: Memory at eb404000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: <available only to root>

00:07.0 Communication controller: Intel Corp. 536EP Data Fax Modem
	Subsystem: Creatix Polymedia GmbH V.9X DSP Data Fax Modem
	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, cache line size 08
	Interrupt: pin A routed to IRQ 3
	Region 0: Memory at eb000000 (32-bit, non-prefetchable) [size=4M]
	Capabilities: <available only to root>

01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0314 (rev a1) (prog-if 00 [VGA])
	Subsystem: Micro-Star International Co., Ltd.: Unknown device 9306
	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 (1250ns min, 250ns max)
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at e8000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: <available only to root>

Re: Integrated ethernet on SiS chipset doesn't work

[Dominik Karall]

On Saturday 10 July 2004 19:35, Jean Francois Martinez wrote:
> I have a friend who owns a computer manufactured by Medion and who
> sports an MSI motherboard who has a SiS chipset.  The MSI motherboard 
> seems to have ben made specially for Medion since it isn't 
> referenced on MSI's site.  The problems is that the integrated ethernet
> doesn't work at all under Linux be it with 2.4 or 2.6 kernel.  He can't 
> ping or connect to other boxes.  His ethernet works when he boots
> Windows.
> 
> I include the output of lspci

I have an Medion computer either and nearly the same components. Did you
enabled SiS900 support in kernel? Can you attach the dmesg output?
The only curios thing with the onboard sis900 chip is, that it does not work
in 100Mb full-duplex mode with the stable kernel tree, but there is a patch
included in -mm patchset, which makes sis900 working in 100Mb full-duplex
mode too.

greets dominik

Re: Integrated ethernet on SiS chipset doesn't work

[Richard B. Johnson]

On Sat, 10 Jul 2004, Jean Francois Martinez wrote:

> I have a friend who owns a computer manufactured by Medion and who
> sports an MSI motherboard who has a SiS chipset.  The MSI motherboard
> seems to have ben made specially for Medion since it isn't
> referenced on MSI's site.  The problems is that the integrated ethernet
> doesn't work at all under Linux be it with 2.4 or 2.6 kernel.  He can't
> ping or connect to other boxes.  His ethernet works when he boots
> Windows.
>
> I include the output of lspci

Tell him to plug a supported ethernet board into a PCI slot
and forget trying to get the embeded one working. It probably
isn't "turned on" by some secret incantations to some secret
registers. If you were to actually find out what was necessary
to make the board work, then that software won't work with a
regular SiS setup so nobody will put it into the kernel. The
usual problem with these imbeded boards is that the vendor
saved 18 US cents (actually) by not putting in the serial
EEPROM that enables I/O and sets the IEEE station address
(the MAC address). If you poke the correct registers, you
can get it turned ON, then what MAC address would you use?

Buried in some BAR somewhere is the MAC address. Forget it.
Get a real ethernet board. Been there, done that.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.

Re: Integrated ethernet on SiS chipset doesn't work

[Jean Francois Martinez]

Le dim 11/07/2004 à 03:48, Richard B. Johnson a écrit :
> On Sat, 10 Jul 2004, Jean Francois Martinez wrote:
> 
> > I have a friend who owns a computer manufactured by Medion and who
> > sports an MSI motherboard who has a SiS chipset.  The MSI motherboard
> > seems to have ben made specially for Medion since it isn't
> > referenced on MSI's site.  The problems is that the integrated ethernet
> > doesn't work at all under Linux be it with 2.4 or 2.6 kernel.  He can't
> > ping or connect to other boxes.  His ethernet works when he boots
> > Windows.
> >
> > I include the output of lspci
> 
> Tell him to plug a supported ethernet board into a PCI slot
> and forget trying to get the embeded one working. It probably
> isn't "turned on" by some secret incantations to some secret
> registers. If you were to actually find out what was necessary
> to make the board work, then that software won't work with a
> regular SiS setup so nobody will put it into the kernel. The
> usual problem with these imbeded boards is that the vendor
> saved 18 US cents (actually) by not putting in the serial
> EEPROM that enables I/O and sets the IEEE station address
> (the MAC address). If you poke the correct registers, you
> can get it turned ON, then what MAC address would you use?
> 
> Buried in some BAR somewhere is the MAC address. Forget it.
> Get a real ethernet board. Been there, done that.
> 
> 

1) I have been using several integrated ethernets in both Nvidia aand
Intel chipsets with good results

2) The Sis 900 driver is supposed to be _supported_ ie someone is being
paid for fixing problems.  It has the highest maintenance status so
its problems are made to be fixed.

3) The guy is not a hard core Linuxer but someone who is just feeling
water temperature.  He has made from Linux being able to make his
ethernet work THE test for deciding if Linux is usable.

4) If I am bothering to submit to the kernel list it is because I want
the problem fixed for _everyone_ and the road for this doesn't go
through using another board or performing a trick of black magic
(putting the thing in half duplex mode).  It goes through having the
driver fixed and in the interim, since searching for black magic things
is not acceptable in a professional context, getting the driver to use
the black magic thing _by default_.  Now I am very willing to help the
maintainer to find what is wrong with this particular
submodel/motherboard.

> Cheers,
> Dick Johnson
> Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
>             Note 96.31% of all statistics are fiction.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: Integrated ethernet on SiS chipset doesn't work

[Daniele Venzano]

On Sun, Jul 11, 2004 at 11:26:54AM +0200, Jean Francois Martinez wrote:
> 2) The Sis 900 driver is supposed to be _supported_ ie someone is being
> paid for fixing problems.  It has the highest maintenance status so
> its problems are made to be fixed.
The email listed in the MAINTAINERS file bounces, so the driver is not
supported so well, I'm acting as maintainer, but no one is paying me.

The sis900 driver driver works in most cases, I am aware of some issues,
mostly caused by new hardware not known by the driver. These problems,
however, cause slowdowns, but the card is always detected.

So before saying anything let's wait for the poster's dmesg.

Cheers.

-- 
-----------------------------
Daniele Venzano
Web: http://teg.homeunix.org

Re: Integrated ethernet on SiS chipset doesn't work

[Richard B. Johnson]

On Sun, 11 Jul 2004, Jean Francois Martinez wrote:

> Le dim 11/07/2004 à 03:48, Richard B. Johnson a écrit :
> > On Sat, 10 Jul 2004, Jean Francois Martinez wrote:
> >
> > > I have a friend who owns a computer manufactured by Medion and who
> > > sports an MSI motherboard who has a SiS chipset.  The MSI motherboard
> > > seems to have ben made specially for Medion since it isn't
> > > referenced on MSI's site.  The problems is that the integrated ethernet
> > > doesn't work at all under Linux be it with 2.4 or 2.6 kernel.  He can't
> > > ping or connect to other boxes.  His ethernet works when he boots
> > > Windows.
> > >
> > > I include the output of lspci
> >
> > Tell him to plug a supported ethernet board into a PCI slot
> > and forget trying to get the embeded one working. It probably
> > isn't "turned on" by some secret incantations to some secret
> > registers. If you were to actually find out what was necessary
> > to make the board work, then that software won't work with a
> > regular SiS setup so nobody will put it into the kernel. The
> > usual problem with these imbeded boards is that the vendor
> > saved 18 US cents (actually) by not putting in the serial
> > EEPROM that enables I/O and sets the IEEE station address
> > (the MAC address). If you poke the correct registers, you
> > can get it turned ON, then what MAC address would you use?
> >
> > Buried in some BAR somewhere is the MAC address. Forget it.
> > Get a real ethernet board. Been there, done that.
> >
> >
>
> 1) I have been using several integrated ethernets in both Nvidia aand
> Intel chipsets with good results
>

Did you bother to READ what I took the time to explain?

> 2) The Sis 900 driver is supposed to be _supported_ ie someone is being
> paid for fixing problems.  It has the highest maintenance status so
> its problems are made to be fixed.
>

WTF?    Who is getting paid?  Find them and bitch to them. All the
stuff you see on the linux-kernel list was/is contributed for free.
It's possible that a vendor like Suse or RedHat may have people
working for them that get paid. You find out what company provided
your distribution and contact them.

> 3) The guy is not a hard core Linuxer but someone who is just feeling
> water temperature.  He has made from Linux being able to make his
> ethernet work THE test for deciding if Linux is usable.

So what?  I'm going to decide that THE test to find out about my
electric connection is, "Can a cat walk the wire?"

>
> 4) If I am bothering to submit to the kernel list it is because I want
> the problem fixed for _everyone_ and the road for this doesn't go
> through using another board or performing a trick of black magic
> (putting the thing in half duplex mode).  It goes through having the
> driver fixed and in the interim, since searching for black magic things
> is not acceptable in a professional context, getting the driver to use
> the black magic thing _by default_.  Now I am very willing to help the
> maintainer to find what is wrong with this particular
> submodel/motherboard.

Contact the "maintainer". Using black magic will break it for
real boards that plug into PCI slots. If you had bothered to
read what I wrote, you would know that.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
            Note 96.31% of all statistics are fiction.

Re: Integrated ethernet on SiS chipset doesn't work

[Jean Francois Martinez]

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

A few weeks ago I reported a problem with the Sis driver but the
poerson who owns the machine was out of town 


Le dim 11/07/2004 à 12:16, Daniele Venzano a écrit :
> On Sun, Jul 11, 2004 at 11:26:54AM +0200, Jean Francois Martinez wrote:
> > 2) The Sis 900 driver is supposed to be _supported_ ie someone is being
> > paid for fixing problems.  It has the highest maintenance status so
> > its problems are made to be fixed.
> The email listed in the MAINTAINERS file bounces, so the driver is not
> supported so well, I'm acting as maintainer, but no one is paying me.
> 
> The sis900 driver driver works in most cases, I am aware of some issues,
> mostly caused by new hardware not known by the driver. These problems,
> however, cause slowdowns, but the card is always detected.
> 
> So before saying anything let's wait for the poster's dmesg.
> 

Here is the interesting part of his dmesg, after reloading the
sis900 driver.  We can see that the card
indentifies a VIA transceiver at address 1 but instead uses the 
(inexistent) one at address 31.

When we look at the sis_default_phy function we notice that there is
a loop on the transceivers and that the first one to answer and have
a link will be selected.  If none answers then we end with the one
at address 31 (despite the varibale being named first_mii) and that
is what is probably happened.

The code looks quite absurd because it continues to loop after finding
an eligible transceiver despite the fact that transceivers with
higher addresses are uneligible to be selected as default.

Now the question is why the VIA transceiver is not answering the probe
or is reporting it has no link  despite having one.
 
---

		Jean Francois Martinez

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 2083 bytes --]

NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 00000005 00000000 
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 00000005 00000000 
sis900.c: v1.08.06 9/24/2002
eth0: Unknown PHY transceiver found at address 0.
eth0: VIA 6103 PHY transceiver found at address 1.
eth0: Unknown PHY transceiver found at address 2.
eth0: Unknown PHY transceiver found at address 3.
eth0: Unknown PHY transceiver found at address 4.
eth0: Unknown PHY transceiver found at address 5.
eth0: Unknown PHY transceiver found at address 6.
eth0: Unknown PHY transceiver found at address 7.
eth0: Unknown PHY transceiver found at address 8.
eth0: Unknown PHY transceiver found at address 9.
eth0: Unknown PHY transceiver found at address 10.
eth0: Unknown PHY transceiver found at address 11.
eth0: Unknown PHY transceiver found at address 12.
eth0: Unknown PHY transceiver found at address 13.
eth0: Unknown PHY transceiver found at address 14.
eth0: Unknown PHY transceiver found at address 15.
eth0: Unknown PHY transceiver found at address 16.
eth0: Unknown PHY transceiver found at address 17.
eth0: Unknown PHY transceiver found at address 18.
eth0: Unknown PHY transceiver found at address 19.
eth0: Unknown PHY transceiver found at address 20.
eth0: Unknown PHY transceiver found at address 21.
eth0: Unknown PHY transceiver found at address 22.
eth0: Unknown PHY transceiver found at address 23.
eth0: Unknown PHY transceiver found at address 24.
eth0: Unknown PHY transceiver found at address 25.
eth0: Unknown PHY transceiver found at address 26.
eth0: Unknown PHY transceiver found at address 27.
eth0: Unknown PHY transceiver found at address 28.
eth0: Unknown PHY transceiver found at address 29.
eth0: Unknown PHY transceiver found at address 30.
eth0: Unknown PHY transceiver found at address 31.
eth0: Using transceiver found at address 31 as default
eth0: SiS 900 PCI Fast Ethernet at 0xe800, IRQ 11, 00:0c:76:68:a9:89.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timeout, status 00000005 00000000 

Re: Integrated ethernet on SiS chipset doesn't work

[Daniele Venzano]

On Thu, Jul 29, 2004 at 09:42:36PM +0200, Jean Francois Martinez wrote:
> Here is the interesting part of his dmesg, after reloading the
> sis900 driver.  We can see that the card
> indentifies a VIA transceiver at address 1 but instead uses the 
> (inexistent) one at address 31.

> eth0: VIA 6103 PHY transceiver found at address 1.
...
> eth0: Unknown PHY transceiver found at address 31.
> eth0: Using transceiver found at address 31 as default
> eth0: SiS 900 PCI Fast Ethernet at 0xe800, IRQ 11, 00:0c:76:68:a9:89.

This behaviuor should be corrected in tha latest kernels (mm or bk) by
the patches available here:
http://teg.homeunix.org/sis900.html

If all fails this patch should work just fine:
http://teg.homeunix.org/download/kpatches/sis900-list-phy-ids.diff
But is just for that particular case.


-- 
-----------------------------
Daniele Venzano
Web: http://teg.homeunix.org

Integrated ethernet on SiS chipset NOW does work

[Jean Francois Martinez]

A month ago you wrote:

Le mer 04/08/2004 à 10:32, Daniele Venzano a écrit :
> On Thu, Jul 29, 2004 at 09:42:36PM +0200, Jean Francois Martinez wrote:
> > Here is the interesting part of his dmesg, after reloading the
> > sis900 driver.  We can see that the card
> > indentifies a VIA transceiver at address 1 but instead uses the 
> > (inexistent) one at address 31.
> 
> > eth0: VIA 6103 PHY transceiver found at address 1.
> ...
> > eth0: Unknown PHY transceiver found at address 31.
> > eth0: Using transceiver found at address 31 as default
> > eth0: SiS 900 PCI Fast Ethernet at 0xe800, IRQ 11, 00:0c:76:68:a9:89.
> 
> This behaviuor should be corrected in tha latest kernels (mm or bk) by
> the patches available here:
> http://teg.homeunix.org/sis900.html
> 
> If all fails this patch should work just fine:
> http://teg.homeunix.org/download/kpatches/sis900-list-phy-ids.diff
> But is just for that particular case.
> 

I applied the patch to the sis900 driver in 2.4.21 (Suse).  This fixed
the problem and the integrated ethernet now works.  Thank you.

Sorry for the delay.

				JFM