From owner-freebsd-stable Thu Jun 15 7:15:24 2000 Delivered-To: freebsd-stable@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 9DB5237B7BA for ; Thu, 15 Jun 2000 07:15:12 -0700 (PDT) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id QAA19223; Thu, 15 Jun 2000 16:15:02 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 19138; Thu Jun 15 16:14:18 2000 Message-ID: Date: Thu, 15 Jun 2000 16:16:12 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" Cc: freebsd-stable@freebsd.org Subject: Re: Sound support broken in FreeBSD 4.0-S? References: <200006141708.KAA26673@mass.cdrom.com> <0dce9503d987a0677241f7982294693f@cequrux.com> <20000615091719.A8955@stat.Duke.EDU> <20000615095956.B8955@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean O'Connell wrote: > > Graham Wheeler stated: > > > PS. Forgot to ask about the video card on your machine ... does > > > it requrire 4.0 or are you after the TrueType fonts? > > > > Trident Cyberblade/i1. > > > > It requires 4.0; although 3.3.6 lists the Cyberblade(generic) as > > supported, I suspect that the i1 isn't (there are several Cyberblade > > variants, it seems). Whenever 3.3.6 started up it would log `unknown > > chipset'. VGA16 in 640x480x8 was the best I could ever get to work. > > I wonder if it is just missing a pci identifier in the Trient code > in XF86_SVGA... along the lines of making the Neomagic 256ZX work That is very possible. When I tried to use depths of 16, 24 or 32, the server barfed saying that the colour mode was not supported for the chipset. For a depth of 8 it may just be that I didn't have an appropriate modeline. If that is the case, can you suggest what I need to do to fix it? > > Re: mouse problem: > > > > I've applied the patches Kazu sent out a week or so ago to the psm > > driver, and so far it seems to be behaving. But I thought the same about > > my patches, until two days ago when the mouse went beserk. So I'll > > reserve judgement for now on these. I did have to fix the one bug I > > found as well, which isn't included in the patch, namely adjusting the > > #define of the GENERIC_MOUSE_ENTRY driver offset in the mouse type table > > to be 10 and not 7. > > Are you using moused? Or is the raw psm device under X? Doesn't seem to make a difference. If I use moused, then the mouse still goes beserk. In a text-mode console, it obbviously doesn't pop up windows all over, but it does make the screen flash and highlight arbitrary pieces of text, so the bug is the same. Can't blame X for this one! regards gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message