begin Ian Romanick quotation of Mon, Jul 25, 2005 at 07:28:17PM -0700:
Hi again,
So, that's like taking the Diesel fuel only sticker off your gas tank
to make it work with regular gas. :) The name changed because the
interface changed. Use *all* DRI drivers *and* libGL.so from Mesa CVS.
Oh
On Monday 25 July 2005 21:53, Jerome Glisse wrote:
On 7/25/05, Bellido Nicolas [EMAIL PROTECTED] wrote:
On Monday 25 July 2005 10:18, Jerome Glisse wrote:
radeon 9800 card still lockup with r300 driver. If you first run
an X server with fglrx, then leave and launch xorg with r300
In fact, i use xfree86 (from debian testing) for fglrx,
You mean xfree86 4.3.0 + ati.patch from r300 cvs ?
No the original xfree86 from debian with fglrx, and i
have installed elsewhere Xorg with r300 (in fact
my rep /usr/X11R6 is link to xfree86 or to xorg and
i point it to which one i want
On Monday 25 July 2005 16:22, Aapo Tahkola wrote:
On Mon, 25 Jul 2005 08:59:53 +0200
[drm:drm_ioctl] pid=9733, cmd=0x40106450, nr=0x50, dev 0xe200, auth=1
[drm:radeon_cp_cmdbuf] RADEON_CMD_SCALARS2
[drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at e08fa024
r300_do_cp_cmdbuf doesnt get
Sebastien Cevey wrote:
The problem is that Xorg is unusable because the fonts are scrambled
in the xterm (and other such terms). All fonts are not, for
instance fonts appear correctly in Firefox, but not in the titlebar
(fluxbox) of the same program. I guess it depends who handles the
font
On Tue, 26 Jul 2005, Mark Ferry wrote:
Section Device
Identifier Card0_r300
Driver ati
BusID PCI:0:16:0
Option UseFBDev true # [bool]
Option DMAForXV off # [bool]
On 7/26/05, Sebastien Cevey [EMAIL PROTECTED] wrote:
begin Ian Romanick quotation of Mon, Jul 25, 2005 at 07:28:17PM -0700:
Hi again,
So, that's like taking the Diesel fuel only sticker off your gas tank
to make it work with regular gas. :) The name changed because the
interface
On 7/26/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005, Mark Ferry wrote:
Section Device
Identifier Card0_r300
Driver ati
BusID PCI:0:16:0
Option UseFBDev true # [bool]
Option DMAForXV
On Tue, 26 Jul 2005, Alex Deucher wrote:
On 7/26/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005, Mark Ferry wrote:
Section Device
Identifier Card0_r300
Driver ati
BusID PCI:0:16:0
Option UseFBDev true # [bool]
On 7/26/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005, Alex Deucher wrote:
On 7/26/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005, Mark Ferry wrote:
Section Device
Identifier Card0_r300
Driver ati
BusID
On 7/12/05, Brian Paul [EMAIL PROTECTED] wrote:
So GLX_BUILT_IN_XMESA is old? I just did a 'make World' and it didn't
appear in the logs.
GLX_BUILT_IN_XMESA is old stuff and should probably be removed. The
idea was for libGL to fall back to stand-alone Mesa Xlib rendering if
the X server
begin Mark Ferry quotation of Tue, Jul 26, 2005 at 01:03:05PM +0100:
Keith Conger suggested the following xorg.conf device options which
solved the screwy font rendering for me:
Option XaaNoScanlineImageWriteRect
Option XaaNoScanlineCPUToScreenColorExpandFill .
This fixes it for me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Smirl wrote:
On 7/12/05, Brian Paul [EMAIL PROTECTED] wrote:
So GLX_BUILT_IN_XMESA is old? I just did a 'make World' and it didn't
appear in the logs.
GLX_BUILT_IN_XMESA is old stuff and should probably be removed. The
idea was for libGL to
On 7/26/05, Sebastien Cevey [EMAIL PROTECTED] wrote:
begin Mark Ferry quotation of Tue, Jul 26, 2005 at 01:03:05PM +0100:
Keith Conger suggested the following xorg.conf device options which
solved the screwy font rendering for me:
Option XaaNoScanlineImageWriteRect
Option
I have tried to enable DRI on my IBM Thinkpad T23 running FC4. selinux
used to be enabled by default. However, this leads to segmentation faults
when calling applications which depend on OpenGL, e.g. in the case of
glxinfo. The corresponding dmesg entry reads:
Unable to handle kernel paging
Hi,
I saw this reported on the acpi list too [1], so I thought I would post
it here hoping it's the right place to send it.
Using the radeon driver from recent X.org CVS (on Linux 2.6.11.10), my
CPU never enters C3 while under X. This causes me to lose about 30
minutes of battery life.
Hi all,
I'm able to do software suspend with the binary-only ATI driver.
This is in no means disrespect to the open source DRI driver but is just an
info for someone who doesnot know. I myself came across this by accident.
You need a program called vbetool. This allows one to save and
Hello, I need my ATI R9250 based board to work because I need it for RD
work. -- possibly even remunitive RD work =\
I managed to get the Mesa CVS sources to work but it caused my critical
application ( www.croquetproject.org ) to hang... (run it with unix
Squeak VM 3.7-7 from www.squeak.org
On Tue, 26 Jul 2005 13:37:02 -0700
Nguyen The Toan [EMAIL PROTECTED] wrote:
You need a program called vbetool. This allows one to save and restore the
graphic card state before suspending and after resuming.
I wonder if this could be used to hunt down the r300 problem.
--
Aapo Tahkola
On Tue, 26 Jul 2005, Alan Grimes wrote:
Hello, I need my ATI R9250 based board to work because I need it for RD
work. -- possibly even remunitive RD work =\
I managed to get the Mesa CVS sources to work but it caused my critical
application ( www.croquetproject.org ) to hang... (run it
On Tue, 2005-07-26 at 11:07 -0700, Lorenzo Colitti wrote:
Using the radeon driver from recent X.org CVS (on Linux 2.6.11.10),
Are you implying that the issue didn't occur with older versions of X
and/or the kernel?
my CPU never enters C3 while under X. This causes me to lose about 30
Is there something that can be done to fix this?
Not sure; bus mastering is used for sending commands to the GPU when the
DRI is enabled (I wouldn't exactly call that 'pointless'...), but that
shouldn't be going on all the time, unless e.g. a client that rarely
(but regularly) redraws parts of
22 matches
Mail list logo
