From nobody@FreeBSD.ORG  Fri Aug 25 12:13:00 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 1ACCE37B422; Fri, 25 Aug 2000 12:13:00 -0700 (PDT)
Message-Id: <20000825191300.1ACCE37B422@hub.freebsd.org>
Date: Fri, 25 Aug 2000 12:13:00 -0700 (PDT)
From: topping@grassroots.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Cyclades cy driver incompatible with Cyclom-Ye PCI and Intel PR440GX motherboard
X-Send-Pr-Version: www-1.0

>Number:         20845
>Category:       i386
>Synopsis:       Cyclades cy driver incompatible with Cyclom-Ye PCI and Intel PR440GX motherboard
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    ceri
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 25 12:20:01 PDT 2000
>Closed-Date:    Sun Jun 08 11:00:59 PDT 2003
>Last-Modified:  Sun Jun 08 11:00:59 PDT 2003
>Originator:     Brian Topping
>Release:        Tested with both 3.3-RELEASE and 4.1-RELEASE
>Organization:
Grassroots.com
>Environment:
Intel PR440GX motherboard in both one and two processor configurations
>Description:
I tried many different combinations of relevant BIOS setup changes, number of processors (1 or 2), and OS version (3.3 and 4.1) trying to get the Cyclades card working in my system.  The "cyctest" disk (a L*@ux mfsrooted filesystem with embedded test utility) and it worked fine on all occasions.  In the best case, the driver reported "no ports found" on boot messages, although 'boot -v' provided no additional information about the problem.  In desparation, I built a new PC using an ABIT VL-6 motherboard (1/5th the cost of the Intel...) and the same serial hardware came up the first time after kernel reconfiguration.
>How-To-Repeat:
Install parts, compile in driver, boot system, try to use a serial port.  Session hang is the typical result.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: bde 
State-Changed-When: Sat Mar 16 20:24:48 PST 2002 
State-Changed-Why:  


http://www.freebsd.org/cgi/query-pr.cgi?pr=20845 
State-Changed-From-To: feedback->open 
State-Changed-By: bde 
State-Changed-When: Sat Mar 16 20:26:21 PST 2002 
State-Changed-Why:  
Gnats accepted a null feedback request; try again. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20845 
State-Changed-From-To: open->feedback 
State-Changed-By: bde 
State-Changed-When: Sat Mar 16 20:28:25 PST 2002 
State-Changed-Why:  
Is this the same problem as in PR 30965?  There was a problem with 
certain newer (?) YeP boards on certain motherboards.  This was fixed 
recently. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20845 
State-Changed-From-To: feedback->closed 
State-Changed-By: ceri 
State-Changed-When: Sun Jun 8 11:00:58 PDT 2003 
State-Changed-Why:  
Feedback timeout (6 months or more). 
I will handle any feedback that this closure generates. 


Responsible-Changed-From-To: freebsd-bugs->ceri 
Responsible-Changed-By: ceri 
Responsible-Changed-When: Sun Jun 8 11:00:58 PDT 2003 
Responsible-Changed-Why:  
Feedback timeout (6 months or more). 
I will handle any feedback that this closure generates. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20845 
>Unformatted:
