From owner-freebsd-questions@freebsd.org  Sat Apr 30 20:46:15 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88FD8B22C78
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Sat, 30 Apr 2016 20:46:15 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "wonkity.com", Issuer "wonkity.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 461BC1188
 for <freebsd-questions@freebsd.org>; Sat, 30 Apr 2016 20:46:15 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.15.2/8.15.2) with ESMTPS id u3UKkAG7053189
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 30 Apr 2016 14:46:10 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id u3UKk9QG053184;
 Sat, 30 Apr 2016 14:46:09 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Sat, 30 Apr 2016 14:46:09 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Manish Jain <bourne.identity@hotmail.com>
cc: Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org
Subject: Re: Is 10.3 i386 jinxed ?
In-Reply-To: <BLU436-SMTP10004EAA9AA9F6D830DF24CF6670@phx.gbl>
Message-ID: <alpine.BSF.2.20.1604301436210.47377@wonkity.com>
References: <BLU436-SMTP151A41CC0BE118F82C0C189F6660@phx.gbl>
 <20160430084415.03be443d.freebsd@edvax.de> <5724604D.3020804@hotmail.com>
 <BLU436-SMTP10004EAA9AA9F6D830DF24CF6670@phx.gbl>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Sat, 30 Apr 2016 14:46:10 -0600 (MDT)
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Apr 2016 20:46:15 -0000

On Sat, 30 Apr 2016, Manish Jain wrote:

> I reinstalled the whole system using xfce as the desktop. While things have 
> improved, the system is still not workable.
>
> 1) The installer 'forgot' to place the boot code on the MBR. I had to use 
> live CD + boot0cfg to fix that.

boot0cfg is (mostly) for writing the dual-boot boot0 code.  Use gpart 
for ordinary booting.

> 2) The first time X started, xfce4-panel crashed
> 3) The second time, xfce-terminal crashed
> 4) The third time, trying to launch firefox rebooted the system.

This sounds unlike my experience with xfce.

Some of the Gateway NE56R models included Nvidia GPUs.  Some special 
thing might be needed to properly support that GPU.

I have an i386 image with xfce that is bootable on most systems, but I 
have not tested it with Nvidia due to a mysterious lack of them among my 
computers.  It works fine on Intel and AMD video, though.

The RAM or power supply could be a problem with the Gateway.