From owner-freebsd-bugs Mon May 13 13: 2: 1 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from inet1.ywave.com (inet1.yelmtel.com [65.161.32.36]) by hub.freebsd.org (Postfix) with ESMTP id 53B5737B408 for ; Mon, 13 May 2002 13:01:42 -0700 (PDT) Received: from yelmtel.com (p115.yelmtel.com [65.161.32.211]) by inet1.ywave.com (Postfix) with ESMTP id 3CA7E2CC1B; Mon, 13 May 2002 12:59:42 -0700 (PDT) Message-ID: <3CE01B2C.AFBED74B@yelmtel.com> Date: Mon, 13 May 2002 12:59:40 -0700 From: billn Organization: Writer & CP/PM Consultant X-Mailer: Mozilla 4.61 [en] (OS/2; U) X-Accept-Language: en MIME-Version: 1.0 To: xfree86@XFree86.Org, freebsd-bugs@FreeBSD.ORG Subject: Re: S3 Trio3D/2X Has Artifacts References: <200205131527.g4DFR7j60531@public.xfree86.org> <3CE00E92.CD45F8F1@yelmtel.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org For reasons which are not clear (I have no clue), after an unplanned reboot, the S3 Trio3D/2X no longer shows the artifact of leaving parts of the picture around on the screen. It still is too slow, so I still want to install XFree86-4-Server, which fails to port as per previous message. BillN billn wrote: > > I read your autoresponse and started to install XFree86-4-Server from > the updated (may 13) ports collection. It failed on an imake, the make > install log is below. > > I am copying this to FreeBSD as well. > > BillN > ====== > inst.log > ====== > ===> Building for XFree86-Server-4.2.0_2 > > Building Release 6.6 of the X Window System: - > > Mon May 13 10:06:24 PDT 2002 > > cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc" > clean > rm -f ccimake imake.o imake > rm -f *.CKP *.ln *.BAK *.bak *.o core errs ,* *~ *.a tags TAGS make.log > \#* > rm -f -r Makefile.proto Makefile Makefile.dep bootstrap > make Makefile.boot > cd ./config/imake && make -f Makefile.ini BOOTSTRAPCFLAGS="" CC="cc" > making imake with BOOTSTRAPCFLAGS= in config/imake > cc -o ccimake -O -I../../include -I../../imports/x11/include/X11 > ccimake.c > cc -c -O -I../../include -I../../imports/x11/include/X11 `./ccimake` > imake.c > cc -o imake -O -I../../include -I../../imports/x11/include/X11 imake.o > rm -f ./config/makedepend/Makefile.proto > ./config/imake/imake -I./config/cf -s > ./config/makedepend/Makefile.proto > -f ./config/makedepend/Imakefile -DTOPDIR=../.. > -DCURDIR=./config/makedepend > *** Error code 1 > > Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc. > *** Error code 1 > > Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc. > *** Error code 1 > > Stop in /usr/ports/x11-servers/XFree86-4-Server. > > ======= > Original message to XFree86.org: > It works (S3 Trio3D/2X) under FreeBSD 4.5, but the images are not > correctly replaced when the image moves. (This leaves partial copies of > the images all over the window). (under XFree86 3.6 w/base install) > > Are there any driver updates since the Jan 2002 4.5 release? > > Thanks, > Bill Nicholls > ======= > > owner-xfree86@XFree86.Org wrote: > > > > --- This is an automatically generated reply --- > > > > Your message has been received and a copy is being distributed > > to all the members of the XFree86 support team. > > > > You might receive a response as soon as someone who knows how to > > respond to your question has time to do so. This may take anywhere > > from 5 minutes to several weeks. On the other hand, you might not > > receive an answer at all. See below. > > > > If you are writing to join the XFree86 developer team, please resend > > your message to signup@xfree86.org > > > > If you are submitting a patch for a bug-fix or enhancement to XFree86, > > please resend your message to fixes@xfree86.org. > > > > Please write your question or bug report in *English* (occasional typos and > > language misuse by non-native speakers are of course no problem). We cannot > > answer mails in other languages (including but not restricted to French, > > Spanish, Russian, Japanese) here. > > > > If your request for help doesn't contain enough information to be able > > to help you, you will probably not get a reply as well. Such a reply would > > just contain a request for more information anyway, so you can remedy that > > right now by sending a properly documented request for help. The bug report > > form is a good start. You can find it at > > http://www.xfree86.org/cgi-bin/bugform.cgi > > > > If you are not using the latest version of XFree86, please try it > > first. Due to lack of manpower, we can't provide service for older > > versions. If the problem persists in the latest version, return > > back to here; also if you find out that something worked in an earlier > > version, but now in the recent version does no longer work, inform us. > > > > Many people report problems with versions which are older than > > their video card. Also, many bugs in older versions are fixed in > > the current version. You can find out what the latest version is, > > and where to get it by referring to the XFree86 home page. When > > we receive a report about a version of XFree86 older than the > > current version, our first response (if any) will usually be to > > ask you to try the latest version to see if the same problem is > > present there. You can short-circuit that by trying it now. > > > > We receive a lot of messages about problems with X servers. Many > > of these messages do not include sufficient information for us to > > be able to determine the nature of the problem. Often there is no > > description of the problem at all. We cannot answer such messages. > > Please include full details of the problem, the video card, the OS > > (and its version) you are using, and the version of XFree86 you > > are using. Also include the full server startup messages (please > > do not reformat them, or trim them -- people often trim out parts > > that seem unimportant to them, but which we need to see). > > > > All messages sent to the XFree86 support address are read by our > > volunteer support group. Unfortunately we cannot guarantee that > > all messages are answered. > > > > We receive a lot of messages that are not directly related to > > XFree86. Some examples include: > > > > Questions about Windows 95 video drivers. XFree86 has nothing > > whatsoever to do with Windows 95 video drivers, and such questions > > cannot be answered by us. > > > > Questions about Linux (or some other Unix-like OS), like questions > > about installing Linux, connecting to the Internet, accessing a > > CDROM, etc. XFree86 is an implementation of the X Window System, > > not an Operating System (Linux or otherwise). It has no connection > > with these other things, and we cannot answer such questions. > > > > Questions about X11 applications which are not part of XFree86. > > Other than things like other X11 clients demonstrating bugs in > > the libraries or X servers distributed with XFree86, we cannot > > answer questions about X11 client applications or libraries which > > are not part of XFree86. Some examples of things which are not part > > of XFree86 are the Xpm library and fvwm (and any other window > > manager other than twm). > > > > Questions about X11 programming. > > > > Questions requesting programming documentation for video cards. > > > > Questions relating to X11 products from third-party enterprises. > > This includes the XBF servers from RedHat as well as the XFCOM > > servers from SuSE, even if they are almost completely based on > > XFree86 code. > > > > Similarly, questions to provide XFree86 binaries in a vendor specific > > format, such as RPM. Contact your vendor about things like that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message