From owner-freebsd-questions@FreeBSD.ORG Thu Oct 28 15:25:59 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EB3D16A4CE for ; Thu, 28 Oct 2004 15:25:59 +0000 (GMT) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0EA643D2D for ; Thu, 28 Oct 2004 15:25:58 +0000 (GMT) (envelope-from m.hauber@mchsi.com) Received: from [10.51.10.3] (12-219-204-133.client.mchsi.com[12.219.204.133]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20041028152557m9200k1r3ce>; Thu, 28 Oct 2004 15:25:57 +0000 From: Mike Hauber To: freebsd-questions@freebsd.org Date: Thu, 28 Oct 2004 11:27:30 -0400 User-Agent: KMail/1.7 X-Copyright: 2004, Michael C. Hauber. All rights reserved. X-Notice: Duplication, modification, and/or redistribution are prohibited without proper consent from the author. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200410281127.30511.m.hauber@mchsi.com> Subject: shared memory X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.hauber@mchsi.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 15:25:59 -0000 Greetings, I have acquired a mo/bo with a built-in video adapter. =20 Being that I have 768 megs of ram, I _know_ I have plenty=20 of memory to allot to video. BIOS doesn't pass this on to=20 =46reeBSD. I have two choices for x. I can use the VESA standard or I=20 can use the S3 video driver (both come up fine, but theres=20 quit a bit of chop when it comes to video processing=20 regardless of which I use).=20 I'm bringing up VESA from the kernal and it's giving it 16=20 megs of ram. Where can I read up on, or how can I increase=20 this allotment? As for the S3 video driver, do I allot the memory from the=20 kernal or is this somehow set up from the x configuration=20 file? (I'm running x.org, although that probably shouldn't=20 matter being that they pretty much seem the same at this=20 point). Applicable nfo as follows: (from dmesg -a) Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (1202.73-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x644 Stepping =3D 4 Features=3D0x183f9ff AMD Features=3D0xc0440000 real memory =3D 788463616 (769984K bytes) avail memory =3D 760496128 (742672K bytes) Preloaded elf module "vesa.ko" at 0xc066d140. =2E..snip... VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc00c0e2a=20 (c0000e2a) VESA: S3 Incorporated. Savage4 =2E..snip... agp0: mem=20 0xd8000000-0xdbffffff at device 0.0 on pci0 pcib1: at=20 device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 =2E..snip... sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem=20 0xa0000-0xbffff on isa0 =2E..snip... (from /sys/i386/conf/WIZARD, comments removed for cleaner=20 reading) cpu I686_CPU ident WIZARD maxusers 132 options CPU_ATHLON_SSE_HACK options CPU_ENABLE_SSE =2E..snip... options USER_LDT options SHMALL=3D32768 options SHMMAX=3D67108864 options VESA =2E..snip... device sc0 at isa? flags 0x100 device vga0 at isa? device agp =2E..snip... =46rom what I've read on it, I can tell you that I'm=20 completely lost when it comes to shared memory (and reading=20 more seems to confuse me more). I simply don't understand=20 how it works. =20 Of course, I know that built in video is recommended against=20 (regardless of what OS is running), but I'm sure there's a=20 way to up the memory... And I hope that theres a place=20 that explains how it works in laymens terms? :) So far, I've re-read the manual on setting up x, for setting=20 up video applications, various video app manuals, LINT, and=20 many googles on shared memory. Mayhaps there's a man page I'm missing that puts all this=20 stuff in perspective? If not, someone explain it so I can=20 write one. :) Thanks. Mike