From owner-freebsd-alpha@FreeBSD.ORG  Mon Mar 29 13:21:38 2004
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AEE4D16A4D2
	for <alpha@freebsd.org>; Mon, 29 Mar 2004 13:21:38 -0800 (PST)
Received: from mailsv01.comindico.com.au (mailsv01.comindico.com.au
	[203.194.27.4])	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E7CE43D1D
	for <alpha@freebsd.org>; Mon, 29 Mar 2004 13:21:38 -0800 (PST)
	(envelope-from robbyrnes@fastmail.com.au)
Received: from fastmail.com.au
	(dialup-158.88.221.203.acc50-kent-syd.comindico.com.au [203.221.88.158])
	by mailsv01.comindico.com.au (Mirapoint)	with ESMTP id AFC23507;
	Mon, 29 Mar 2004 19:45:40 +1000 (EST)
Message-ID: <4067F087.1000208@fastmail.com.au>
Date: Mon, 29 Mar 2004 19:46:47 +1000
From: Rob B <robbyrnes@fastmail.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.6b) Gecko/20031205 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: alpha@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: cdrom not detected in 5.2.1-RELEASE
X-BeenThere: freebsd-alpha@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Alpha <freebsd-alpha.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-alpha>
List-Post: <mailto:freebsd-alpha@freebsd.org>
List-Help: <mailto:freebsd-alpha-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Mar 2004 21:21:38 -0000

Finally got my PC64 up to 5.2.1-RELEASE, but the ATA cdrom doesn't want 
to work.  The chipset and ata ports are recognised by the kernel at boot 
time:

ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0
ata0: interrupting at ISA irq 14
ata0: [MPSAFE]
ata1 at port 0x376,0x170-0x177 irq 15 on isa0
ata1: interrupting at ISA irq 15
ata1: [MPSAFE]

but there is nothing in /dev, and the drive is known good.

Any thoughts?

cheers,
Rob

-- 
"If one studies too zealously, one easily loses his pants."
- Albert Einstein

This is random quote 57 of 1254.

Distance from the centre of the brewing universe
[15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian

Public Key fingerprint = 6219 33BD A37B 368D 29F5  19FB 945D C4D7 1F66 D9C5