Mailinglist Archive: radeonhd (145 mails)

< Previous Next >
Re: [radeonhd] 0x7249:0x1043:0x0168: ASUS EAX1900 CROSSFIRE
  • From: "Alex Deucher" <alexdeucher@xxxxxxxxx>
  • Date: Fri, 26 Dec 2008 11:28:06 -0500
  • Message-id: <a728f9f90812260828v787d18feibcc1b3740507a6ab@xxxxxxxxxxxxxx>
On Wed, Dec 24, 2008 at 5:02 PM, Tom Merriam <tmerriam87@xxxxxxxxx> wrote:
I'm running Slackware 12.2 and using version 1.2.3 of the radeonhd
driver. It prints a message to the Xorg log saying it doesn't identify
my chipset. My video card is an ASUS EAX1900 CROSSFIRE which is just a
rebranded X1900 CF with a bigger fan. It has 512MB of
RAM. The outputs are a DVI out, an S-Video out, and the crossfire cable
connector.


The driver is able to detect the card specific information from the
data tables in the bios. that message is a bit misleading.

ASUS's page for the EAX1900 CROSSFIRE:
http://www.asus.com/products.aspx?l1=2&l2=8&l3=264&l4=0&model=1027&modelmenu=2


I'm attaching the output from Xord.0.log, my xorg.conf file, and the output
of lspci -vv

There
are also some other issue's I've had, though it could also be that I
don't have up-to-date-enough versions of some software. When I enable,
DRI in xorg.conf, X doesn't seem to detect the correct resolution for
my monitor, and 2D seems to be off as well. The full 512MB of memory
isn't recognized either. Driver limitation? I can provide more
information on Mesa/X versions if you think it's necessary.

It's a driver limitation. The maximum PCI BAR size is 256 MB,
anything larger than that cannot be mapped directly by the CPU. The
full amount of memory can be addressed by the GPU. In order to use
the full amount of vram the driver needs a proper memory manager since
the CPU cannot access buffers in the part of vram beyond the PCI BAR
window. Work to support this in the drm is in progress.

Alex
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx

< Previous Next >
References