From owner-freebsd-current Wed Feb 26 2:41:48 2003 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 C837A37B401 for ; Wed, 26 Feb 2003 02:41:46 -0800 (PST) Received: from horkos.telenet-ops.be (horkos.telenet-ops.be [195.130.132.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id C07C643F93 for ; Wed, 26 Feb 2003 02:41:45 -0800 (PST) (envelope-from philip@paeps.cx) Received: from localhost (localhost.localdomain [127.0.0.1]) by horkos.telenet-ops.be (Postfix) with SMTP id 4E79C83C7A for ; Wed, 26 Feb 2003 11:41:42 +0100 (CET) Received: from fortuna.home.paeps.cx (D5768746.kabel.telenet.be [213.118.135.70]) by horkos.telenet-ops.be (Postfix) with ESMTP id 41AEB83C51 for ; Wed, 26 Feb 2003 11:41:42 +0100 (CET) Received: from juno.home.paeps.cx (juno.home.paeps.cx [10.0.0.2]) by fortuna.home.paeps.cx (Postfix) with ESMTP id CD1DA20D1 for ; Wed, 26 Feb 2003 11:41:46 +0100 (CET) Received: by juno.home.paeps.cx (Postfix, from userid 1001) id D35FF10AC; Wed, 26 Feb 2003 11:41:41 +0100 (CET) Date: Wed, 26 Feb 2003 11:41:41 +0100 From: Philip Paeps To: current@freebsd.org Subject: VESA modes with i815? Message-ID: <20030226104141.GE579@juno.home.paeps.cx> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline X-Date-in-Rome: ante diem IV Kalendas Martias MMDCCLVI ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Mutt: User-Agent: Mutt/1.5.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi guys! I've recently had my Matrox VGA board die on me (don't know why, it just died), and since then I've been doomed to use the on-board i815 chip to get the phosphors in my monitor to light up. This works fine with 'small consoles', and even with VESA_800x600, but when I type 'vidcontrol VESA_132x60` or any other VESA mode, for that matter, the screen just goes blank. When I then type 'vidcontrol -g 100x37 VESA_800x600', or 'vidcontrol 80x25' my screen comes back. First I thought perhaps the prompt was hidden way off the visible area of my monitor, but fiddling with the knobs doesn't bring an answer. Is this a known problem with this chipset, or am I doing something silly? I'm running -CURRENT from a few days ago. Thanks! - Philip -- Philip Paeps Please don't CC me, I am philip@paeps.cx subscribed to the list. The one thing that money can not buy is poverty. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message