Bug 63666

Summary: [acpi] Network card 3c575B do not work after the 5.1 release
Product: Base System Reporter: damien <damien.chaumette>
Component: kernAssignee: freebsd-acpi (Nobody) <acpi>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description damien 2004-03-02 23:00:33 UTC
Did a cvsup / make buildkernel installkernel and strangely my network card didn't work anymore.
Thinking I was just a newbie; I started a 5.2.1 network installation untill I realized that my network card didn't work there neither...
The situation is the same with 5.2 installation.

The error message is "xl0: PHY not found!", and then no more /dev/xl0 and no network.

How-To-Repeat: * use 5.1 and cvsup kernel
* try a 5.2/5.2.1 network installation
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2005-04-07 23:10:11 UTC
State Changed
From-To: open->feedback

Is this still a problem with recent versions of FreeBSD?
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2005-04-07 23:21:29 UTC
Responsible Changed
From-To: freebsd-bugs->linimon

track.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2005-04-08 19:33:35 UTC
Responsible Changed
From-To: linimon->freebsd-acpi

Submitter notes that this is only a problem with ACPI, so assign it 
to that mailing list.
Comment 4 John Baldwin freebsd_committer freebsd_triage 2005-04-08 20:44:56 UTC
Can you please verify if the 5.4 release candidates still have this issue?  
Also, can you please provide a dmesg from a non-ACPI boot as well as one from 
an ACPI boot if possible?  Thanks.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
Comment 5 Kris Kennaway freebsd_committer freebsd_triage 2005-07-30 01:51:18 UTC
State Changed
From-To: feedback->closed

Feedback timeout
Comment 6 damien.chaumette 2005-08-11 10:22:59 UTC
Sorry for the delay,

I just tried the latest 6.0-Beta2 and the acpi problem is still there.
Will send dmesg later on as the system is now higly unstable and prone
to unexpected crashes.

--
Damien