From owner-freebsd-bugs@FreeBSD.ORG Fri Mar 23 23:30:15 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA0DB1065670 for ; Fri, 23 Mar 2012 23:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 956F78FC15 for ; Fri, 23 Mar 2012 23:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2NNUFCN073775 for ; Fri, 23 Mar 2012 23:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2NNUFMc073772; Fri, 23 Mar 2012 23:30:15 GMT (envelope-from gnats) Date: Fri, 23 Mar 2012 23:30:15 GMT Message-Id: <201203232330.q2NNUFMc073772@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Frank Reppin Cc: Subject: Re: kern/166262: [syscons] syscons issue on DN2800MT X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frank Reppin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 23:30:15 -0000 The following reply was made to PR kern/166262; it has been noted by GNATS. From: Frank Reppin To: bug-followup@freebsd.org Cc: Subject: Re: kern/166262: [syscons] syscons issue on DN2800MT Date: Sat, 24 Mar 2012 00:21:54 +0100 Hi, On Fri, Mar 23, 2012 at 7:55 PM, Jung-uk Kim wrote: [...] > I am not so sure about that. FYI, BTX uses BIOS int 10h calls and > kernel directly accesses VGA hardware and memory. I see - thank's for enlighten me ;) > Maybe you do not have the BIOS that I saw from YouTube > presentation. :-( No idea - I flashed the most 'recent' one (0151) quite soon after receiving the board. The previous BIOS didn't had any other settings from what I remember. > Sorry, there is something strange going on with writing to video > memory. That's all I can say ATM. :-/ Well - nevermind then ;) The 'workaround' (as described in the initial PR) to get things working at the beginning is OK (for me at least...). Again - thanks for having a quick look into this. cheers, frank\