Subject: IDE CDROM problem
To: None <port-i386@NetBSD.ORG>
From: Tim Janes <janes@signal.dra.hmg.gb>
List: port-i386
Date: 05/20/1997 16:37:26
For 6 months or so I have been using Manuel Bouyer's ATAPI CD support
on NetBSD1.2Beta without any problems. 

I have just reinstalled 1.2.1 and can't get it working again.

I downloaded Manuel's files on May12th and followed the README without
any problems.

The CDROM is seen at bootup but any attempt to access it just gets the
response "device not configured".

uname -a

NetBSD titan0.dra.hmg.gb 1.2.1 NetBSD 1.2.1 (NETBSD) #0: Thu May 15 14:46:02 BST 1997     root@titan0.dra.hmg.gb:/usr/src/sys/arch/i386/compile/NETBSD i386

Here are the boot up messages

May 15 14:47:21 titan0 /netbsd: wdc0 at isa0 port 0x1f0-0x1f7 irq 14
May 15 14:47:21 titan0 /netbsd: atapibus0 at wdc0
May 15 14:47:21 titan0 /netbsd: acd0 at atapibus0 drive 1: <TOSHIBA CD-ROM XM-56
02B, 2900006642, 1156> type 5/cdrom removable
May 15 14:47:21 titan0 /netbsd: acd0: 120mm data disc
May 15 14:47:21 titan0 /netbsd: wd0 at wdc0 drive 0: <QUANTUM FIREBALL_TM2110A>
May 15 14:47:21 titan0 /netbsd: wd0: 2014MB, 4092 cyl, 16 head, 63 sec, 512 byte
s/sec
May 15 14:47:21 titan0 /netbsd: wd0: using 16-sector 16-bit pio transfers, lba a
ddressing

Here is an extract from the kernel config file

fdc0    at isa? port 0x3f0 irq 6 drq 2  # standard PC floppy controllers
#fdc1   at isa? port 0x370 irq ? drq ?
fd*     at fdc? drive ?

#mcd0   at isa? port 0x300 irq 10       # Mitsumi CD-ROM drives

wdc0    at isa? port 0x1f0 irq 14       # ST506, ESDI, and IDE controllers
#wdc1   at isa? port 0x170 irq ?
wd*     at wdc? drive ?
atapibus* at wdc?
acd* at atapibus? drive?

And the device files

titan0:##ls -l /dev/*acd*
brw-r--r--  1 root  wheel   17,   0 May 15 14:20 /dev/acd0a
brw-r--r--  1 root  wheel   17,   3 May 15 14:20 /dev/acd0d
crw-r--r--  1 root  wheel   21,   0 May 15 14:20 /dev/racd0a
crw-r--r--  1 root  wheel   21,   3 May 15 14:20 /dev/racd0d

The CDROM is slaved onto the hard disk on the primary IDE controller.

I don't think this is a hardware problem as we have a number of
machines and I can't now get any working but they all worked before
the O/S reinstall.

My guess is I have done something stupid but I just can't see what.

Many Thanks

Tim.