From owner-freebsd-hackers Fri Jul 18 07:39:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA23445 for hackers-outgoing; Fri, 18 Jul 1997 07:39:11 -0700 (PDT) Received: from ns.newreach.net (root@ns.newreach.net [206.25.170.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23432 for ; Fri, 18 Jul 1997 07:39:08 -0700 (PDT) Received: from inetgw.aristar.com (inetgw.aristar.com [206.25.171.180]) by ns.newreach.net (8.8.4/8.6.9) with ESMTP id KAA20593 for ; Fri, 18 Jul 1997 10:38:52 -0400 (EDT) Message-Id: <199707181438.KAA20593@ns.newreach.net> From: "Matthew A. Gessner" To: Subject: Installation - SYSVSHM required for X??? Date: Fri, 18 Jul 1997 10:49:29 -0400 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, all, Why would the X servers (XF86_SVGA) give me a lot of grief about not being able to do SYSVSHM? It's not in GENERIC, but it is in LINT. Do I need to rebuild the kernel to support X??? I have a TSENG ET4000/W32 chipset, which SuperProbe gives as Super-VGA. I had X under 2.1.5-RELEASE running just fine under this chipset, although that old XF86Config file doesn't seem to work now either. I did go to XFree86.org and try to find out what was going on, and I followed their suggestions, but that didn't solve the SYSVSHM error message problem. TIA, Matt -- Matthew A. Gessner, Computer Scientist Aristar, Inc. Akron, OH 330.668.2267 FAX 330.668.2961