Bug 21623

Summary: Chipset SiS630E / NIC SiS 900
Product: Base System Reporter: roland <roland>
Component: kernAssignee: Martin Blapp <mbr>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description roland 2000-09-28 17:30:01 UTC
The SiS 900 Driver cant read the ethernet-address
from the all-in-one-chipset SiS630E.
Ethernet-Address will always be 0:0:0:0:0:0.

Fix: 

No fix, only a ugly workaround.

Hardwire the Ethernet-Address in sys/pci/if_sis.c:

static u_char sis_macaddr[ETHER_ADDR_LEN] = { 0x00,0xe0,0x18,0x01,0x02,0x03 };

And assign that in function sis_attach below:

bcopy((char *)sis_macaddr, eaddr, ETHER_ADDR_LEN);
How-To-Repeat: Install FreeBSD on a ASUS CUSI-FX with integrated NIC.
Comment 1 Johan Karlsson freebsd_committer freebsd_triage 2000-10-03 20:15:38 UTC
Responsible Changed
From-To: freebsd-bugs->wpaul

Over to if_sis maintainer.
Comment 2 scs 2001-07-09 18:41:19 UTC
This problem may have been fixed in 4.3-RELEASE; my first
load using an ASUS CUSI-FX (SIS-630E chip set) correctly set
the enet address.
-- 
   "The optimist proclaims that we live in the best of all possible worlds;
and the pessimist fears this is true."
	      -- James Branch Cabell, from 'The Silver Stallion', 1926.
Comment 3 Sheldon Hearn freebsd_committer freebsd_triage 2001-12-30 13:31:54 UTC
State Changed
From-To: open->feedback

Can you confirm that the problem is fixed in 4.3-RELEASE, as suggested 
in the audit trail for this PR?
Comment 4 Martin Blapp freebsd_committer freebsd_triage 2003-01-30 23:18:22 UTC
Responsible Changed
From-To: wpaul->mbr

Taking this PR from wpaul. It seems that this has been fixed 
since a long time. Can you confirm that you don't encounter 
any problems with this card anymore ? 

If you still have problems, you can try this patch against 
FreeBSD 4.7 stable: 

http://people.freebsd.org/~mbr/patches/if_sis_stable.diff
Comment 5 Martin Blapp freebsd_committer freebsd_triage 2003-02-12 23:10:46 UTC
State Changed
From-To: feedback->closed

Feedback timeout. The problem has been fixed since a while.