From owner-freebsd-stable@FreeBSD.ORG Thu Jul 8 22:10:52 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D41E41065673 for ; Thu, 8 Jul 2010 22:10:52 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id 95B7A8FC15 for ; Thu, 8 Jul 2010 22:10:52 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o68MAnxC026399 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Jul 2010 18:10:49 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o68MAmkG022124; Thu, 8 Jul 2010 18:10:48 -0400 Message-ID: <4C364CE8.6050104@aldan.algebra.com> Date: Thu, 08 Jul 2010 18:10:48 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: Peter Jeremy References: <4C34C5DE.7040007@aldan.algebra.com> <20100708210611.GA34250@server.vk2pj.dyndns.org> In-Reply-To: <20100708210611.GA34250@server.vk2pj.dyndns.org> X-Mailman-Approved-At: Mon, 12 Jul 2010 11:34:51 +0000 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: 8.x grudges X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 22:10:52 -0000 08.07.2010 17:06, Peter Jeremy ΞΑΠΙΣΑΧ(ΜΑ): > On 2010-Jul-07 14:22:22 -0400, "Mikhail T." wrote: > >> In no particular order: >> >> 1. A picture, that one of the systems was displaying at boot (and >> then used as a screen-saver), stopped showing properly. The >> colors are right, but the picture is distorted beyond recognition. >> The relevant part of loader.conf is: >> >> splash_pcx_load="YES" >> vesa_load="YES" >> bitmap_load="YES" >> bitmap_name="/boot/187426-9-quokka-dreaming.pcx" >> > It's a bit difficult to provide any useful input without some idea > of what the picture should and does look like. Can you please post > the actual bitmap as well as a picture of your screen showing the > problem. > I don't want to post it publicly for copyright reasons. I can e-mail it to you (or anyone else) directly, though. >> 3. Likewise, having "device ugen" breaks config(8) -- another >> undocumented incompatibility. >> > Can you please advise where it is documented that "device ugen" > is valid in a FreeBSD-8 config file? > It was a valid device for FreeBSD-7. The UPDATING-file enumerates a number of things, that need to be changed, when updating to 8, but the removal of "ugen" is not mentioned there. >> 5. One of the upgraded systems would repeatedly hang at boot, until I >> disabled the on-board firewire-device through the BIOS... It was >> not a problem under 7.x, although I don't know, whether the device >> actually worked. >> > I haven't seen this on any of my systems. Can you please provide > details of your motherboard, BIOS and the output from a verbose boot > up to the hang. Is there a BIOS update available and have you tried > installing it? > No BIOS updates :-( I can e-mail boot's output to you directly (please, confirm interest). It would be with the device disabled though, because the boot never completes, if it is enabled. >> 6. Despite the reported improvements in the USB area, my USB keyboard >> /still/ does not work during boot. It during POST and then after >> the booting is complete. But in single-user mode -- no... Had to >> fish-out the PS2 keyboard... >> > I have had similar problems on one of my USB-only desktops. In my > case, moving the keyboard to a different USB port solved the problem. > All I can suggest is to work your way through all the USB ports you > have available and see if they all behavee the same. > I'll try that next time I reboot this system. Thanks, -mi