Date: Fri, 30 Oct 1998 15:47:41 -0600 From: Dan Nelson <dnelson@emsphone.com> To: Alfred Perlstein <bright@hotjobs.com>, current@FreeBSD.ORG, Mike Smith <mike@smith.net.au> Subject: Re: if anyone is interested VESA seems broken. Message-ID: <19981030154741.A18571@emsphone.com> In-Reply-To: <Pine.BSF.4.05.9810301442320.389-100000@porkfriedrice.ny.genx.net>; from "Alfred Perlstein" on Fri Oct 30 14:51:22 GMT 1998 References: <Pine.BSF.4.05.9810301442320.389-100000@porkfriedrice.ny.genx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Oct 30), Alfred Perlstein said: > I recently enabled "options USER_LDT" in my kernel to test some > things out. I also enabled VESA and VM86 (figured if i was gonna > reboot...) > > Well vidcontrol seems only able to set a very small subset of modes > that seem available to my machine (from boot -v and vidcontrol -i > mode) > > Modes that I could get to work: 80x25, 132x25, VESA_800x600 no more > :( vidcontrol should only let you set the text modes and 800x600, I think. If you can't get 132x50, make sure you have an 8x8 font loaded. I know I have gotten 132x43 on my system (cheap s3 chipset won't do 132x50) > Another odd thing with VESA, if you notice how it seems the top of my > dmesg it gone? Well right about there at bootup my screen goes blank for > a split second and again either a second before or after the cut part. > (This happens twice while probing VESA it seems) That's because the default dmesg buffer in the kernel is 8k by default. Add "options MSGBUF_SIZE=16384" to your kernel config file to double it. > VESA: mode:0x109, flags:0x000b, T 132x25, font:8x16 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k > VESA: mode:0x10b, flags:0x000b, T 132x50, font:8x8 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k > VESA: mode:0x10c, flags:0x000b, T 132x60, font:8x8 > VESA: window A:0xb800 (7), window B:0x0 (0), size:32k, gran:32k Your card definitely should be able to do 132x50, since it claims to support it here. Maybe check to see that vidcontrol and syscons.c handle them correctly (I don't have access to 3.0 at the moment) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981030154741.A18571>