From owner-freebsd-current Mon Dec 28 17:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26633 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:32:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26627 for ; Mon, 28 Dec 1998 17:32:31 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id UAA17538 for ; Mon, 28 Dec 1998 20:32:14 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma017536; Mon, 28 Dec 98 20:31:22 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id UAA15812 for ; Mon, 28 Dec 1998 20:31:21 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id UAA16173; Mon, 28 Dec 1998 20:31:21 -0500 (EST) Date: Mon, 28 Dec 1998 20:31:21 -0500 (EST) Message-Id: <199812290131.UAA16173@jabberwock.rstcorp.com> MIME-Version: 1.0 From: "Viren R. Shah" To: freebsd-current@FreeBSD.ORG Subject: VESA kld question X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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