From owner-freebsd-questions Thu Aug 10 3:13:28 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id AF87F37BB48 for ; Thu, 10 Aug 2000 03:13:17 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-213-168-64-79.netcologne.de [213.168.64.79]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id MAA28945; Thu, 10 Aug 2000 12:13:11 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e7AA48362681; Thu, 10 Aug 2000 12:04:08 +0200 (CEST) Date: Thu, 10 Aug 2000 12:04:08 +0200 (CEST) From: Paul Herman To: George Sollish Cc: questions@FreeBSD.ORG Subject: Re: Upgrade woes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi George, On Wed, 9 Aug 2000, George Sollish wrote: > I've been running 3.2R on a compaq i586-84 for a year and felt it was time > to move on to 4.0R, so I followed the instructions for a binary upgrade > which worked reasonably well EXCEPT: > > (1) 'startx' (for root or user) fails with a series of messages: > Xwrapper: no modules loader for 'xserver' service > Authentication failed -- cannot start X server Perhaps with your upgrade you didn't update /etc/pam.conf? You might want to check if you have this in /etc/pam.conf: xserver auth required pam_permit.so If that doesn't do the trick, in /etc/fbtab try uncommenting the line: /dev/ttyv0 0600 /dev/console > (2) This is a dual boot box (Win95) using the FreeBSD bootloader. The > bootloader works fine on a cold boot, but locks solid on a warm boot. > Initiating a boot from the install floppy displays the same behavior: fine > on a cold boot, 'disc read error, no /kernel present' on a warm boot. Sounds like a problem with either BIOS/hardware. I'd be really grasping at straws if I were to guess that your drives needed to reset from some reason or something... ? -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message