From owner-freebsd-ppc@FreeBSD.ORG Mon Jan 13 05:11:29 2014 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EDB25766; Mon, 13 Jan 2014 05:11:29 +0000 (UTC) Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 45B0112E1; Mon, 13 Jan 2014 05:11:29 +0000 (UTC) Received: by mail-lb0-f175.google.com with SMTP id w6so4931874lbh.20 for ; Sun, 12 Jan 2014 21:11:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tgytr1cMsD5vPxIB8QLGZ6qaRYrmGR56Xhmbz7U8hhE=; b=vDcYka8XupuCAdHDefb0KOktJ8uEtJ0YIzeXuDtBQtHD5xZLbt5qiNYK8nkRC0cxJ4 7Fbt3dze9JW6NFQ1Rv5FwRWYBVQjsTxq6lXeI6a4+eSeHH2N860DsyYC8avHyN6JS6FH 6dWSfE7uNhEbHO9QA8uTQB2eOewya/rbGwl7JGv3YtR8diTVppzB3CWnn+B4Q9ZDxPlc cxxKu15Z/1a178sjQp7LWqaT9zqCTtogLMYoterIluLb+BTG2hiK7L+c+zPZikHB7PfN FUxw5EpYFReTMIBh6zKgtS+xitap/DkFU8ZUHiSvaM1bJIA00tJCxWOH+xszlZ1rQ8Vj 7SAA== X-Received: by 10.152.26.72 with SMTP id j8mr60173lag.85.1389589887174; Sun, 12 Jan 2014 21:11:27 -0800 (PST) Received: from selene.local (h-42-134.a357.priv.bahnhof.se. [79.136.42.134]) by mx.google.com with ESMTPSA id h11sm8832116lbg.8.2014.01.12.21.11.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 Jan 2014 21:11:26 -0800 (PST) Message-ID: <52D3757C.1020600@gmail.com> Date: Mon, 13 Jan 2014 06:11:24 +0100 From: Erik Larsson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Nathan Whitehorn , freebsd-ppc@freebsd.org Subject: Re: Failed install attempt for FreeBSD 10 RC1 powerpc64 References: <52AC0CA3.2010301@gmail.com> <52C967C7.3050101@freebsd.org> In-Reply-To: <52C967C7.3050101@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jan 2014 05:11:30 -0000 Hi, Nathan Whitehorn wrote 2014-01-05 15.10: > On 12/14/13 02:45, Erik Larsson wrote: >> Hi all, >> >> I just tried installing FreeBSD 10 RC1 powerpc64 on my PowerMac11,2 >> (2x2.3 GHz). The disc created from the ISO booted fine, and I was able >> to install FreeBSD onto a UFS filesystem on my second hard drive (I >> couldn't find an option to install to ZFS), but after a reboot the >> system boot setting 'boot-device' in nvram had not changed (it booted >> the previous default OS instead). >> >> I fixed the nvram value myself to point at the instealled .elf file >> and made another attempt at booting. It loads the .elf file, the >> screen flashes into black and then it exits back to openfirmware. >> Seems to crash somehow. >> >> Does anybody have an idea what to try next to make the install succeed >> and boot? >> >> Best regards, >> >> - Erik >> >> _______________________________________________ >> freebsd-ppc@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > In case this never got answered, you probably want to boot bootinfo.txt > instead of boot1.elf. Holding option should also let OF figure out the > right thing to do. Thanks, I actually did figure this out. Currently running RC4 on this machine and it's working quite well (without X at least...). A .txt file seemed like an unlikely boot file and AFAICR it wasn't blessed properly with 'tbxi', but when installing RC4 it got properly blessed. Just curious... why isn't the installer setting the nvram 'boot-device' value (or at least offering to set it, like it probably asks whether to install boot code to MBR on x86 BIOS hardware)? Best regards, - Erik