From owner-freebsd-alpha@FreeBSD.ORG  Sun Mar  6 16:21:16 2005
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 B724516A4CE
	for <freebsd-alpha@freebsd.org>; Sun,  6 Mar 2005 16:21:16 +0000 (GMT)
Received: from hooters.chaossolutions.net (a.ns.chaossolutions.org
	[209.216.77.5])	by mx1.FreeBSD.org (Postfix) with SMTP id 0BBB543D6A
	for <freebsd-alpha@freebsd.org>;
	Sun,  6 Mar 2005 16:21:16 +0000 (GMT)
	(envelope-from marrandy@chaossolutions.org)
Received: (qmail 8119 invoked from network); 6 Mar 2005 16:15:17 -0000
Received: from unknown (HELO ?192.168.1.1?) (209.216.76.1)
  by a.ns.chaossolutions.org with SMTP; 6 Mar 2005 16:15:17 -0000
From: marrandy <marrandy@chaossolutions.org>
To: ticso@cicely.de
Date: Sun, 6 Mar 2005 11:21:36 -0500
User-Agent: KMail/1.7.2
References: <200503042131.34556.marrandy@chaossolutions.org>
	<422B1EE4.4DB1B3A8@performancedesign.no>
	<20050306152449.GE22167@cicely12.cicely.de>
In-Reply-To: <20050306152449.GE22167@cicely12.cicely.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503061121.36216.marrandy@chaossolutions.org>
cc: freebsd-alpha@freebsd.org
Subject: Re: alphaserver 4100 stops om boot
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: Sun, 06 Mar 2005 16:21:16 -0000

On Sunday 06 March 2005 10:24, Bernd Walter wrote:

> Possible, but that would mean it doesn't boot at all and not that it
> stops during boot.
> Even if that's the case there are several reasons why this could happen.
> With an exact description one could easily give an exact answer.

OK - please explain to me how I can retrieve the information with the exact 
description when it hasn't fully booted yet