From owner-freebsd-current@FreeBSD.ORG Wed Apr 6 15:05:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A82A16A4CE for ; Wed, 6 Apr 2005 15:05:44 +0000 (GMT) Received: from postino-2.etat.lu (postino-2.etat.lu [194.154.205.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8727F43D49 for ; Wed, 6 Apr 2005 15:05:43 +0000 (GMT) (envelope-from didier.wiroth@mcesr.etat.lu) Received: from avirus-1.cie.etat.lu (dispatch-1.cie.etat.lu [148.110.137.6]) by postino-2.etat.lu (Postfix) with ESMTP id 648CA1112DCE for ; Wed, 6 Apr 2005 17:05:11 +0200 (CEST) Received: from avirus-1.cie.etat.lu (dispatch-1.cie.etat.lu [148.110.137.6]) by localhost (CIE ESMTP Dispatch 1) with ESMTP id 674542151E for ; Wed, 6 Apr 2005 17:05:11 +0200 (CEST) Received: from hermes-1.cie.etat.lu (hermes-1.cie.etat.lu [148.110.136.56]) 4DEF02103C for ; Wed, 6 Apr 2005 17:05:11 +0200 (CEST) Received: from hermes-1.cie.etat.lu (hermes-1.cie.etat.lu [148.110.136.56]) by store.etat.lu (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IEJ003FY5WN06A0@store.etat.lu> for freebsd-current@freebsd.org; Wed, 06 Apr 2005 17:05:11 +0200 (MEST) Received: from LUCY ([148.110.43.189]) by store.etat.lu (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTP id <0IEJ00F9M5WK1A80@store.etat.lu>; Wed, 06 Apr 2005 17:05:11 +0200 (MEST) Date: Wed, 06 Apr 2005 17:05:09 +0200 From: Didier Wiroth In-reply-to: <4096.212.12.51.89.1112798211.squirrel@212.12.51.89> To: 'Marian Hettwer' , 'Robert Backhaus' Message-id: <0IEJ00F9O5WN1A80@store.etat.lu> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Content-transfer-encoding: 7BIT Thread-index: AcU6tiBIhEBST4jYQMiqRuAsdil6TQAARI7g cc: freebsd-current@freebsd.org Subject: RE: vesa 1024x768 mode in future version? to the freebsd community X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2005 15:05:44 -0000 Yes, I agree. Stability and robustness is priority number 1. Having an option like "Boot FreeBSD with HighD Console" in the boot menu, like "Boot FreeBSD ACPI disabled" would not hurt anybody. May be it would also be possible to have something in loader.conf: vesa_load="YES" vesa_resolution="MODE_322" Or/and an additional kernel option to enable it in a custom kernel, would be ok to. If the kernel would crash, you could still always boot the default kernel. Well to RELENG_5 or 6 is not really important to me, the important part is that the freebsd core team think about a possible integration in the "near" future :-)) >On one hand it would be pretty useful to have a high resolution console, on the other hand, I wouldn't like to see the FreeBSD Kernel crashing while booting, because of some faulty graphics >card. >I recently had the problem on Gentoo Linux (2.6.8), that it just didn't recognized my graphics card and therefor the kernel crashed due to some framebuffer problems. >That's annoying! >If FreeBSD would implement a high resolution console (by use of either FrameBuffer or VESA), than it never ever should be the default for your installation. >And even if you enabled it, the kernel should never crash. Instead it should give an error message, telling me "Hej buddy, your graphics card won't work with VESA" and then scaling down to old >fashioned low res console ... > it occours. >Doesn't matter to me wether I'll have this feature in 6-stable or MFC'ed to RELENG_5. It has to be stable.