On Thu, Dec 13, 2007 at 09:24:24PM +0100, Lo?c Greni? wrote:
1) I don't known its id. It's an OEM card, I've a "Sapphire Inside" label on my case and one of the stickers on the back reads "X1550 512MB DDR2 PCI-E VGA/TVO/DVI-I". It looks nearly exactly like the Sapphire X1550 512MB that is on Newegg, except that it has a RoHS mention on one sticker (I'm in Europe) and the SKU# is 11093-19 (I cannot decipher it on Newegg's photo, but it does not seem to be the same).
Don't worry too much about this atm :)
2) The BIOS maps only 256MB of ram; it is related to: 3) The card and driver do not seem to know whether the card has 256 or 512MB of RAM (it prints 0xE00000000/28 as main memory, but the driver claims 512MB somewhere else). The bios message starts with "512mb".
This is no big deal right now... In the future it'd be nice if it were possible to remap the 512MB somewhere else (above the 4GB mark, because I've 4GB of DRAM).
Both are the exact same issue. The memory available on the card does not equal the memory we can access from the cpu directly. Whatever is in the non-directly-addressable part can be used by the card itself, but we currently are not doing anything that could make use of that memory anyway.
4) There is a secondary chip with id 0x71a7. It could be another X1550 without output registers (lspci -x below).
This exists only to fool some windows version. Ignore it.
5) Both outputs are changed together by xrandr. I've compiled a fairly recent version of the X server and xrandr (git of beginning of September) and, when I act on one output with xrandr, both change together. For instance, if I type
xrandr --output VGA_1 --right-of DVI-I_1/digital
both output go to (1024,0). I always get same resolution and same position for both outputs. The outputs are not in parallel because the EDID are different for both screens.
That's what I've found after some tries. With a single screen it works ok. With two it's a problem (and that's unfortunate because I'd like to make a two-seat computer).
I have no idea whether this is an RandR FAQ, a known RandR issue, or an issue that still has to be dug out. I hope that Matthias can shed some light on this one. Thanks, Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org