From owner-freebsd-stable Thu Nov 30 3:33: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from area51.v-wave.com (area51.v-wave.com [24.108.173.252]) by hub.freebsd.org (Postfix) with SMTP id C51A837B400 for ; Thu, 30 Nov 2000 03:33:05 -0800 (PST) Received: (qmail 83914 invoked by uid 1001); 30 Nov 2000 11:33:05 -0000 Date: Thu, 30 Nov 2000 04:33:05 -0700 From: Chris Wasser To: freebsd-stable@FreeBSD.ORG Subject: options VESA Message-ID: <20001130043304.A83838@skunkworks.area51-arpa.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suppose I could have done this in one message... Is VESA for Nvidia cards slightly broken? I've got a 32MB TNT2 Ultra in one particular box (dual boot) and kernel reports: CPU: Pentium II/Pentium II Xeon/Celeron (400.91-MHz 686-class CPU) VESA: v3.0, 16320k memory, flags:0x1, mode table:0xc02bea62 (1000022) VESA: NVidia pci1: at 0.0 irq 10 agp0: mem 0xd0000000-0xd7ffffff at device 0.0 on pci0 Memory count is wrong, yet on a ATI 32MB R128 I get: CPU: AMD Athlon(tm) Processor (750.03-MHz 686-class CPU) VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc025c4c2 (1000022) VESA: ATI RAGE128 pci1: at 0.0 irq 10 agp0: mem 0xd0000000-0xd7ffffff at device 0.0 on pci0 Anyone got a theory/reason/suggestion? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message