Your message dated Wed, 13 Oct 2004 16:36:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing old installation-reports
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Mar 2004 10:56:56 +0000
>From [EMAIL PROTECTED] Wed Mar 17 02:56:56 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-217-155-153-11.zen.co.uk (trigger.kantaka.co.uk) [217.155.153.11] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1B3YjH-0005vW-00; Wed, 17 Mar 2004 02:56:56 -0800
Received: from phil by trigger.kantaka.co.uk with local (Exim 3.36 #1 (Debian))
        id 1B3YjG-0002M2-00
        for <[EMAIL PROTECTED]>; Wed, 17 Mar 2004 10:56:54 +0000
Date: Wed, 17 Mar 2004 10:56:54 +0000
From: Philip Armstrong <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Sparc installation fails on Ultra 5
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

Package: installation-reports

Debian-installer-version: beta3 sarge-sparc-businesscard.iso from gluck.debian.org
uname -a: SunOS turing 5.8 Generic_108528-15 sun4u sparc SUNW,Ultra-5_10
Date: 2004-03-17
Method: boot from CD, with the "boot cdrom" command at the OpenBoot prompt
Machine: Sun Ultra5 
Processor: UltraSPARC-IIi 360MHz
Memory: 256Mb
Root Device: IDE
Root Size/partition table: 
Output of lspci:

Base System Installation Checklist:

Initial boot worked:    [E]

Comments/Problems:

First time I booted from the CD, I got an "illegal instruction" report
after the loading of the initrd. It appears on further
experimentation, that the boot works fine after a cold boot, or a hard
reset, but if the solaris kernel has run first, then the illegal
instruction occurs during the boot from the Debian install CD.

ie.

Hard reset / power on -> boot cdrom -> kernel boots
Hard reset / power on -> boot solaris -> halt solaris -> boot cdrom ->
illegal instruction after initrd loading.

However, after booting the kernel, it is then unable to find a root
filesystem, so the install halts at this point.

This is one of the evil Ultra 5 IDE based Sun boxes. Is the installer
assuming that the CD is going to be on the scsi bus & trying to mount
that instead of /dev/hdc? Or it maybe failing to find the initrd in
memory? I've no idea how to tell unfortunately.

I did try booting with linux root=/dev/hdc, but that didn't appear to
make any difference.

cheers,

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt

---------------------------------------
Received: (at 238495-done) by bugs.debian.org; 13 Oct 2004 21:47:39 +0000
>From [EMAIL PROTECTED] Wed Oct 13 14:47:38 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CHqyA-00078W-00; Wed, 13 Oct 2004 14:47:38 -0700
Received: from dragon.kitenet.net (unknown [66.168.94.144])
        (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
        (Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
        by kitenet.net (Postfix) with ESMTP id 2575B1810F;
        Wed, 13 Oct 2004 20:35:33 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
        id C6B796E111; Wed, 13 Oct 2004 16:36:59 -0400 (EDT)
Date: Wed, 13 Oct 2004 16:36:59 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED]
Subject: closing old installation-reports
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.5 required=4.0 tests=BAYES_00,SUSPICIOUS_RECIPS 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 16


--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm closing this old installation report, since it looks to me like all the
problems reported in it are old and fixed. There are much newer versions of
the debian installer available, that fix lots of bugs. If you're able to
try one and verify that the problems you reported are fixed (or file a new
report if not), that would be great.

Thanks for your installation report.

--=20
see shy jo

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBbZHrd8HHehbQuO8RAh+GAKDRX7bxhNlBf7bBpmM3BwnErCpeFQCfTvrK
q0ckVhnUPx+u+Pf9VD48lDs=
=Pdl/
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to