NetBSD Problem Report #44212

From www@NetBSD.org  Thu Dec  9 18:55:26 2010
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 047E863B886
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  9 Dec 2010 18:55:26 +0000 (UTC)
Message-Id: <20101209185525.D74E263B87A@www.NetBSD.org>
Date: Thu,  9 Dec 2010 18:55:25 +0000 (UTC)
From: mike@dewberryfields.co.uk
Reply-To: mike@dewberryfields.co.uk
To: gnats-bugs@NetBSD.org
Subject: Iyonix will not boot a kernel from IDE
X-Send-Pr-Version: www-1.0

>Number:         44212
>Category:       port-iyonix
>Synopsis:       Iyonix will not boot a kernel from IDE
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-iyonix-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 09 19:00:00 +0000 2010
>Last-Modified:  Sun Dec 12 09:14:47 +0000 2010
>Originator:     Mike Howard
>Release:        NetBSD-current
>Organization:
>Environment:
NetBSD 5.99.41 (IYONIX51CC) #0: Mon Dec  6 22:40:22 GMT 2010 root@snoddy.dewberryfields.co.uk:/usr/obj/sys/arch/iyonix/compile/IYONIX51CC iyonix
>Description:
NetBSD has insttalled to a Maxtor 80GB drive. With the drive installed in the Iyonix and using boot32 to boot with the following commanf line 'boot32 netbsd root=/dev/wd0a' results in a failure of the machine to boot.

Everything works as expected upto and including leaving RiscOS. No  messages are displayed either on theconsole or serial port.

Attaching the drive to another (x86) NetBSD system reveals the logs have not been written to.

The iyonix is currently running RiscOS 5.16 and NetBSD was not tried with any earlier OS versions on this machine.

>How-To-Repeat:
Refit drive to the machine, on either IDE interface, in any Master/Slave order results in no boot.
>Fix:
Not really a fix but, attach the drive to an IDE->USR coverter ('Easy IDE') and the system will boot using 'boot32 netbsd root=/dev/sd0a'.

Maybe the _fairly_ recent RiscOS 5.16 rom update has caused the issue?

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->port-iyonix-maintainer
Responsible-Changed-By: dholland@NetBSD.org
Responsible-Changed-When: Sun, 12 Dec 2010 09:14:47 +0000
Responsible-Changed-Why:
boot issues are (almost always) machine-dependent, so use the corresponding
category.


>Unformatted:

Home	PR Database Search