Bug 123191 – SIS900 driver in Asus motherboard series X fails

Bug 123191 - SIS900 driver in Asus motherboard series X fails

Summary:	SIS900 driver in Asus motherboard series X fails

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	kernel (Show other bugs)
Sub Component:
Version:	1
Hardware:	i586 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Jeff Garzik
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-05-13 14:23 EDT by Edgard Matamala
Modified:	2013-07-02 22:19 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-09-29 16:25:55 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Edgard Matamala 2004-05-13 14:23:01 EDT

Description of problem:
Sis900 network driver seems to load without problems but when fedora
try to give up, it fails (shows "SIOSIFFLAGS: DEVICE OR RESOURCE BUSY")
in other motherboard with chipset SIS no show this problem, but in the
ASUS motherboar Series X (P4S533-MX) the integrated network card fails.


Version-Release number of selected component (if applicable):


How reproducible:
installing and running Fedora Core 1

Steps to Reproduce:
1.install the O.S. Fedora Core1
2.restarting the OS
3.
  
Actual results:


Expected results:


Additional info:
the bug not are tested in another ASUS type of motherboards

Comment 1 Harald Hoyer 2004-05-17 04:36:38 EDT

reassigning to component kernel

Comment 2 David Lawrence 2004-09-29 16:25:55 EDT

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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