Date: Mon, 28 Dec 1998 20:31:21 -0500 (EST) From: "Viren R. Shah" <viren@rstcorp.com> To: freebsd-current@FreeBSD.ORG Subject: VESA kld question Message-ID: <199812290131.UAA16173@jabberwock.rstcorp.com>
next in thread | raw e-mail | index | archive | help
So far, I've been using[1] the VESA kld (with VM86 compiled into the
kernel) by loading it thru the /boot/boot.conf file. I tried using the
new logo kld screensaver, and it wouldn't work saying that the
particular VESA mode wasn't supported. This seemed ridiculous to me
since the screensaver was only looking for 800x600. So, I compiled a
new kernel with "options VESA", rebooted, and voila! the screensaver
worked.
Is there a known problem with using the VESA kld, as oppossed to
compiling it statically into the kernel? I discovered that when I was
using the VESA kld, I wasn't getting the following lines upon bootup,
which I do get with VESA compiled into the kernel:
VESA: v3.0, 4096k memory, flags:0x1, mode table:0xf021652a (1000022)
VESA: STB Velocity 128 (RIVA 128)
My boot.conf file looks like (or looked like):
load kernel
load atapi
load cd9660
load vesa
load linux
load if_tun
load kernfs
load procfs
load portal
autoboot 5
Any ideas as to why the kld module wouldn't work?
[1]: When I say "using" here, I mean loading it without really trying
to use it for anything. :-)
Thanks
Viren
--
Viren R. Shah | "For oft, when on my couch I lie
viren@rstcorp.com | In vacant or in pensive mood,
Research Associate | They flash upon that inward eye
RST Inc. | Which is the bliss of solitude;" --WW
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?199812290131.UAA16173>