From stacy@millions.ca  Sat May 30 19:38:26 1998
Received: from inet-gw-0.ey.ca (inet-gw-0.iti.qc.ca [204.19.117.4])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA16040
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 30 May 1998 19:38:15 -0700 (PDT)
          (envelope-from stacy@millions.ca)
Received: from oak.millions.ca (slip-00.EY.CA [132.220.28.1]) by inet-gw-0.ey.ca (8.6.12/8.6.12) with ESMTP id WAA13338 for <FreeBSD-gnats-submit@freebsd.org>; Sat, 30 May 1998 22:27:52 -0400
Received: (from stacy@localhost)
	by oak.millions.ca (8.8.8/8.8.5) id WAA00323;
	Sat, 30 May 1998 22:27:48 -0400 (EDT)
Message-Id: <199805310227.WAA00323@oak.millions.ca>
Date: Sat, 30 May 1998 22:27:48 -0400 (EDT)
From: stacy@millions.ca
Reply-To: stacy@millions.ca
To: FreeBSD-gnats-submit@freebsd.org
Subject: Cyclom 8yo problem
X-Send-Pr-Version: 3.2

>Number:         6800
>Category:       kern
>Synopsis:       Cyclom 8yo problem
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 30 19:40:01 PDT 1998
>Closed-Date:    Tue Jun 2 05:53:17 PDT 1998
>Last-Modified:  Tue Jun  2 05:54:12 PDT 1998
>Originator:     Stacy Millions
>Release:        FreeBSD 2.2.6-RELEASE i386
>Organization:
Millions Consulting Limited
>Environment:

	FreeBSD 2.2.6-R
	PC clone (running FreeBSD for several years)
	486/66
	Adaptec 1542 SCSI
	Cyclom 8yo v6.02 ISA card
		firware ID  222
		firware Rev 2

>Description:

	The cyclom board test out fine with the cyctest.exe

	The board is recognised by FreeBSD
		cy0 irq 15 maddr 0xd4000 msize 8192 on isa
	
	For testing I started a getty running on ttyc01. Then
	I connected the com1 port to that port with a null modem.
	I ran 'cu -l /dev/cuaa0'. I get garbage on the screen in
	response to what I type.

	The strange thing is, when I install the Cyclade provide
	loop back cable on the cyclom port, every thing echos back
	fine. I have verified that it is not a baud rate or framing
	problem.

		# stty < /dev/cuaa0
		speed 9600 baud;
		lflags: -icanon -isig -iexten -echo
		iflags: -icrnl -ixany -imaxbel -brkint
		oflags: -opost -onlcr -oxtabs
		cflags: cs8 -parenb crtscts
		time    
		1       

		# stty < /dev/cuac01
		speed 9600 baud;
		lflags: -icanon -isig -iexten -echo
		iflags: -icrnl -ixany -imaxbel -brkint
		oflags: -opost -onlcr -oxtabs
		cflags: cs8 -parenb crtscts
		time    
		1       
	
	I know my com1 functions OK, because I can talk to my modem
	over it. The same can not be said for the cyclom.

>How-To-Repeat:


>Fix:
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: phk 
State-Changed-When: Tue Jun 2 04:15:05 PDT 1998 
State-Changed-Why:  
Can you talk with the same cable to another device/port/something ? 
It is important that you be systematic in isolating the troubled  
part.  Cabeling is suspect #1.  Look out for ground-loops which can 
induce serious amounts of noise. 

From: Stacy Millions <stacy@Millions.CA>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/6800
Date: Tue, 02 Jun 1998 08:45:50 -0400

 Poul-Henning Kamp wrote:
 > 
 > Synopsis: Cyclom 8yo problem
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: phk
 > State-Changed-When: Tue Jun 2 04:15:05 PDT 1998
 > State-Changed-Why:
 > Can you talk with the same cable to another device/port/something ?
 > It is important that you be systematic in isolating the troubled
 > part.
 
 I did that. I used my NT box for the standard. From the NT, I was able to
 communicate with the com1 port of the FreeBSD, but not any of the cyclom
 ports.
 
 >       Cabeling is suspect #1.
 
 Nope. I have a good breakout box and a set of trusted cables that I use for
 testing.
 
 >                               Look out for ground-loops which can
 > induce serious amounts of noise.
 
 My multimeter shows a potential of 1.1 mV between the signal grounds of the
 two boxes.
 
 I looked on the Cyclades support web page and found a driver for FreeBSD
 2.2.6 that was different from the one in my source directory. I installed
 it and every thing is fine now.
 
 cy.c:
      $Id: cy.c,v 1.41.3.1 1998/05/01 18:23:46 ivan Exp $
 
 cy.c.orig:
      $Id: cy.c,v 1.41.2.3 1998/03/18 21:05:19 dg Exp $
 
 Thanks for the help.
 
 -stacy
State-Changed-From-To: feedback->closed 
State-Changed-By: phk 
State-Changed-When: Tue Jun 2 05:53:17 PDT 1998 
State-Changed-Why:  
I guess this could be said to be an instance of PR4338 :-/ 

Committer with cyclades board WANTED!  apply at PR #4338 
>Unformatted:
