From owner-freebsd-current Mon Feb 15 23:03:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13451 for freebsd-current-outgoing; Mon, 15 Feb 1999 23:03:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from h24-64-221-247.gv.wave.shaw.ca (24.64.221.247.bc.wave.home.com [24.64.221.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13418 for ; Mon, 15 Feb 1999 23:03:25 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Received: from h24-64-221-247.gv.wave.shaw.ca (localhost [127.0.0.1]) by h24-64-221-247.gv.wave.shaw.ca (8.9.3/8.9.2) with ESMTP id XAA00471 for ; Mon, 15 Feb 1999 23:03:22 -0800 (PST) (envelope-from jake@h24-64-221-247.gv.wave.shaw.ca) Message-Id: <199902160703.XAA00471@h24-64-221-247.gv.wave.shaw.ca> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: vesa and X wierdness Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Feb 1999 23:03:21 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, if I load the vesa kld module from loader.rc, in order to use a high-res splash screen, when X starts the screen is very dim. Usually I start xdm from ttys, but its the same if I use startx. The cursor looks normal, its really bright against the dim screen. Its fine if I don't load vesa and use a 320x200 splash screen, and if I do load it, the vesa modes work great; I can load a 1024x768 splash image, its just when X starts. I'm running 4.0-current as of about noon on Sunday, Diamond Viper V330 pci video card (riva 128) on a pci motherboard (no agp). I've also got a bt848 TV card, but I doubt that would affect it. Not sure what else would be significant. I imagine its something peculiar to my video card, the console text used to be a gross yellow when I used vesa, but that's been fixed. I didn't want to send huge boot -v or dmesg output to the list until I got some feedback. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message