From owner-freebsd-qa Mon Jan 28 11:29:36 2002 Delivered-To: freebsd-qa@freebsd.org Received: from mail.dobox.com (mail.dobox.com [65.88.244.102]) by hub.freebsd.org (Postfix) with SMTP id 6813F37B400 for ; Mon, 28 Jan 2002 11:29:34 -0800 (PST) Received: (qmail 18427 invoked from network); 28 Jan 2002 19:51:03 -0000 Received: from salty.dobox.com (HELO dobox.com) (10.0.1.33) by spinoff.dobox.com with SMTP; 28 Jan 2002 19:51:03 -0000 Message-ID: <3C55A692.F89548B4@dobox.com> Date: Mon, 28 Jan 2002 12:29:22 -0700 From: Wes Peters Organization: DoBox Inc. X-Mailer: Mozilla 4.75 [en] (X11; U; OpenBSD 2.7 i386) X-Accept-Language: en MIME-Version: 1.0 To: Murray Stokely Cc: qa@freebsd.org Subject: Re: FreeBSD 4.5 RC2 problem with XF86 4.1.0_12 References: <3C4DEE64.185F29CE@dobox.com> <20020128124142.GH9395@freebsdmall.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Murray Stokely wrote: > > On Tue, Jan 22, 2002 at 03:57:40PM -0700, Wes Peters wrote: > > I (finally!) installed 4.5RC2 yesterday. I installed XF86 3.3.6 during > > sysinstall, only to find it did not have drivers for the VGA chipset > > in my test machine, a "PC Wave" brand "book pc". The video card is > > identfied in dmesg as "Trident model 8400" by the PCI bus probe. > > > > So I erased the /usr/X11R6 directory and installed XF86 4.1.0 from the > > packages on the CD-ROM. Attempting to run xf86cfg failed, /usr/X11R6/bin/X > > You mean XFree86 -configure? I've never used 'xf86cfg' with > X4.1.0. XFree86 4.1.0 seems to work fine for me on RC3. /usr/X11R6/bin/xf86cfg is the 4.x graphical configuration tool. It runs /usr/X11R6/bin/X -configure, yes. > > messages I can re-install the 4.1.0 package later today, but it would > > certainly bear testing. It would be a shame to ship 4.5 with a broken > > 4.1.0 package, no 4.2.0 package, and only creaky old 3.3.6 that actually > > works. > > These unresolved symbol problems are caused by some conflict on your > local machine. Apparently they're caused by X not recognizing or providing a correct driver for the graphics chip. Weird, but not a show stopper, except for someone trying to install and configure X on a Trident Cyberblade 7i, which is quite common in low-end laptops and integrated motherboards. Sigh. You can't win them all, right? -- Boats love me Sails fear me Wes Peters System Architect http://www.dobox.com/ DoBox Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message