From: "Pere Castañer Sardà" <XaRz69-pCzzcW6XgXY@public.gmane.org>
To: acpidevel <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: new DRI resume binary snapshots and patches available
Date: 04 Dec 2002 20:41:27 +0100 [thread overview]
Message-ID: <1039030887.15651.11.camel@debian.Debian-beast> (raw)
In-Reply-To: <1039011070.4773.36.camel-1Jw6Eky0yc0@public.gmane.org>
El mié, 04-12-2002 a las 15:11, Charl P. Botha escribió:
> There should be no problem... it's exactly the same as the dri.sf.net
> binaries, except that it has my patch integrated and installs its own
> copy of the XFree86, libxaa.a and libpcidata.a binaries as well. These
> have all been built from a 20021203 checkout of the DRI tree.
mmm it won't install. This is the output:
Begin-----------------------------------------------------
DIRECT RENDERING OPEN SOURCE PROJECT - DRIVER INSTALLATION SCRIPT
[ http://dri.sourceforge.net ]
==========================================================================
The script will now compile the DRM kernel modules for your machine.
Press ENTER to continue or CTRL-C to exit.
Compiling...
ERROR: Kernel modules did not compile
The DRI drivers can not be installed without the latest kernel modules.
Installation will be aborted. See the dri.log file for information on
what went wrong.
-------------------------------------------------------end
> ps. You know about the SSE problems in current DRI? If some of your
> applications quit with a FPE, start them with env var MESA_NO_SSE=1 ...
> this bug manifested after the latest Mesa merge.
Uh! I don't knew nothing about it. But I 've not see nothing strange in
my 3D apps (quake3 mostly).But thanks for the comment.
PD: I haven't be able to install swsusp(beta16)-vainilla
+acpi20021126-2.4.20-rc3.diff with linux-2.4.20 final release of the
kernel, and because of this, your resume-patch doesn't have any sense
for my hardware (at this moment).
--
Pere Castañer Sardà
Computer Management Technical Engineering Student on UOC
Member of AEIGi (http://www.aeigi.org)
Linux Registered User #232073
Debian/GNU User (http://www.debian.org)
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET
comprehensive development tool, built to increase your
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
next prev parent reply other threads:[~2002-12-04 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 23:25 new DRI resume binary snapshots and patches available Charl P. Botha
[not found] ` <20021203232507.GA1723-V1rPnKwUOrA59+mn7qD7y50iERQUc4G+@public.gmane.org>
2002-12-04 14:00 ` Pere Castañer Sardà
[not found] ` <1039010406.31730.53.camel-XpXrOaFReG1A+pMbq6XI4y5m1MAxIYdN@public.gmane.org>
2002-12-04 14:11 ` Charl P. Botha
[not found] ` <1039011070.4773.36.camel-1Jw6Eky0yc0@public.gmane.org>
2002-12-04 19:41 ` Pere Castañer Sardà [this message]
[not found] ` <1039030887.15651.11.camel-XpXrOaFReG1A+pMbq6XI4y5m1MAxIYdN@public.gmane.org>
2002-12-04 20:49 ` Charl P. Botha
2002-12-11 9:38 ` Juan Quintela
[not found] ` <m2el8oopys.fsf-I+/jYW0I6Y1pcJYJbGLfGQ@public.gmane.org>
2002-12-11 10:22 ` [Swsusp] " Charl P. Botha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1039030887.15651.11.camel@debian.Debian-beast \
--to=xarz69-pczzcw6xgxy@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox