NetBSD Problem Report #10437

Received: (qmail 11225 invoked from network); 25 Jun 2000 07:54:18 -0000
Message-Id: <200006250754.AAA28810@nbwww.isc.org>
Date: Sun, 25 Jun 2000 00:54:18 -0700 (PDT)
From: shaneyroo@yahoo.com
Reply-To: shaneyroo@yahoo.com
To: gnats-bugs@gnats.netbsd.org
Subject: Mitsumi cr-4804TE atapi cdrw drive is not detected by 1.4.2's kernel
X-Send-Pr-Version: www-1.0

>Number:         10437
>Category:       kern
>Synopsis:       Mitsumi cr-4804TE atapi cdrw drive is not detected by 1.4.2's kernel
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 25 07:55:00 +0000 2000
>Closed-Date:    Sun Jul 30 16:25:29 +0000 2000
>Last-Modified:  Sun Jul 30 16:25:29 +0000 2000
>Originator:     Shane Sanders
>Release:        1.4.2
>Organization:
>Environment:
NetBSD daemon 1.4.2 (GENERIC) #3: Wed Mar 15 23:41:54 PST 2000
toddpw@vader.toddpw.net:/usr/src/sys/arch/i386/compile/GENERIC i386

>Description:
I own a Mitsumi CR-4804TE IDE CDRW.  Netbsd fails to find the device.
Although it detects perfectlly my Sony CD Reader, also an IDE device.
It may be that I need to use some specific option with-in my kernel.
Any ideas are appreciated as I will attempt to implement them.
>How-To-Repeat:
Just buy a drive and hook it up.

>Fix:
ATAPI/IDE device.  Should be detected automatically.

>Release-Note:
>Audit-Trail:

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: shaneyroo@yahoo.com
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: kern/10437: Mitsumi cr-4804TE atapi cdrw drive is not detected by 1.4.2's kernel
Date: Mon, 26 Jun 2000 21:18:22 +0200

 On Sun, Jun 25, 2000 at 12:54:18AM -0700, shaneyroo@yahoo.com wrote:
 > 
 > >Number:         10437
 > >Category:       kern
 > >Synopsis:       Mitsumi cr-4804TE atapi cdrw drive is not detected by 1.4.2's kernel

 I suspect what's happening here, and it should be fixed in -current.
 Could you grab the kernel from the last snapshot (
 ftp://ftp.netbsd.org/pub/NetBSD/arch/i386/snapshot/...) and tell me if
 it detects the drive ?

 --
 Manuel Bouyer <bouyer@antioche.eu.org>
 --
State-Changed-From-To: open->feedback 
State-Changed-By: bouyer 
State-Changed-When: Wed Jun 28 07:49:38 PDT 2000 
State-Changed-Why:  
Patch sent to author. 

From: Manuel Bouyer <bouyer@antioche.lip6.fr>
To: Jeremy Sanders <shaneyroo@yahoo.com>
Cc: gnats-bug@gnats.netbsd.org
Subject: Re: kern/10437: Mitsumi cr-4804TE atapi
Date: Wed, 28 Jun 2000 16:49:34 +0200

 --M9NhX3UHpAaciwkO
 Content-Type: text/plain; charset=us-ascii

 On Mon, Jun 26, 2000 at 07:11:40PM -0700, Jeremy Sanders wrote:
 > Worked like majik! :)

 Ok.

 > 
 > Care to enlighten me as to your suspisions?

 After a bus reset, an atapi device is supposed to put magic numbers in its
 registers, so that it can easily be detected. But some devices (mostly CD-R,
 but I've also seen this with CD) combined with some controllers fails to do
 this for 2 of the 4 registers. Because of this the kernel ignore it.

 Now that my machine with 1.4 sources is up again I've been able to do a
 diff. The attached patch should solve the problem in the same way for the
 1.4 branch. Can you try it and tell me if it's enouth ?

 > I am thinking mainly towards a funky bios.  Seeing as
 > how it boots off the Burner, yet cannot seem to see
 > the device.

 No, that's not the problem. NetBSD doesn't use the bios for this.

 --
 Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
 --

 --M9NhX3UHpAaciwkO
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename=diff

 Index: wdc.c
 ===================================================================
 RCS file: /cvsroot/syssrc/sys/dev/ic/wdc.c,v
 retrieving revision 1.66.2.8
 diff -u -r1.66.2.8 wdc.c
 --- wdc.c	2000/02/01 23:30:28	1.66.2.8
 +++ wdc.c	2000/06/28 14:48:41
 @@ -252,11 +252,10 @@
  		    chp->wdc ? chp->wdc->sc_dev.dv_xname : "wdcprobe",
  	    	    chp->channel, drive, sc, sn, cl, ch), DEBUG_PROBE);
  		/*
 -		 * sc is supposted to be 0x1 for ATAPI but at last one drive
 -		 * set it to 0x0 - or maybe it's the controller.
 +		 * sc & sn are supposted to be 0x1 for ATAPI but in some cases
 +		 * we get wrong values here, so ignore it.
  		 */
 -		if ((sc == 0x00 || sc == 0x01) && sn == 0x01 &&
 -		    cl == 0x14 && ch == 0xeb) {
 +		if (cl == 0x14 && ch == 0xeb) {
  			chp->ch_drive[drive].drive_flags |= DRIVE_ATAPI;
  		} else {
  			chp->ch_drive[drive].drive_flags |= DRIVE_ATA;

 --M9NhX3UHpAaciwkO--
State-Changed-From-To: feedback->closed 
State-Changed-By: bouyer 
State-Changed-When: Sun Jul 30 09:24:13 PDT 2000 
State-Changed-Why:  
This is now fixed in the 1.4 branch too 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.