Bug 11146

can you attach an Xorg.0.log? and one from a working master driver as well?

Created attachment 10193 [details]
server log with a working version using mergedfb and with the external screen plugged on

Created attachment 10194 [details]
server log with a driver compiled from gir branch randr-1.2

Created attachment 10195 [details]
In case it is usefull, server log with the same setup than the working one with mergedfb and only the internal screen

Please attach (not pasting) your xorg.conf to this bug.

Created attachment 10294 [details]
a log with the last git master version

Created attachment 10295 [details]
my xorg.conf

....i'm on x86, and my video card is:

01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 SE] (rev 01) (prog-if 00 [VGA])

i'm using randr-1.2 aranch of ati driver (up to and include ec1fd2c388ec2c4033644776ee8588405a3d25f1)

i have strange screen corruption after server startup. But only if i have also ColorTiling enabled (default, as i can see from logs). If I disable it - i get normal picture (but slower 3d). 


And should i fill another bug about non-working VT switch?  (again, but here is more serious problem - i can't see anything on text consoles, only blank screen. but Xserver itself working, i can return to graphics mode.)

....issue with not restored text mode resolved!

in radeon_driver.c , in function RADEONRestore i enable again call to RADEONUnblank(pScrn); [around line 5103] and all working again! But i have only one monitor (VGA connector, CRT monitor) - may be this 'fix' broke things for another people?

I got a correct display on the LVDS if I disable ColorTiling AND the hardware cursor, otherwise, with commit 3bb46c03fddd3bd79bdab887366aeeced0290a3a, I got the messed display.

Should be fixed now:
52cc1dc1491559a9055f3ba6dd54064bb382ad86

Default size is 1600x1200; use a virtual line in your config to make it bigger.

cursor and depth 16 palette set up still need fixes for big endian.

these should be resolved now.

Hi,
I have tested the driver today with git commits up to bdcae62...
The problem is still there.
You can ask for informations or testing or anything else that does not require too much time.

Thanks in advance
Best regards

(In reply to comment #13)
> Hi,
> I have tested the driver today with git commits up to bdcae62...
> The problem is still there.

Which problem?  The stride issues or the HW cursor issues?  Depth 16 is still broken and HW cursors are still broken on ppc.  The stride issues should be fixed however.  What size desktop are you using?

(In reply to comment #14)
> (In reply to comment #13)
> > Hi,
> > I have tested the driver today with git commits up to bdcae62...
> > The problem is still there.
> 
> Which problem?  The stride issues or the HW cursor issues?  Depth 16 is still
> broken and HW cursors are still broken on ppc.  The stride issues should be
> fixed however.  What size desktop are you using?
> 
I have checked and I am using depth 24 with a desktop of 1024x768 according to the xorg log. It is the native display of my iBook.
I am still experiencing the stride issue.

PS : sorry for the delay since you closed the bug, but I had no time to test before today.

(In reply to comment #15)
> I have checked and I am using depth 24 with a desktop of 1024x768 according to
> the xorg log. It is the native display of my iBook.
> I am still experiencing the stride issue.
> 

1024x768 is the size of the mode, but the max desktop size is different.  the default is 1600x1200 unless you add a virtual line to your config.  Does changing the virtual size help?  try 1024 or 1664 for the virtual width:
e.g.,

Virtual 1024 768
Virtual 1664 1200

See bug 11796 for the HW cursor issue.

The software Tiling bug is now closed (see https://bugs.freedesktop.org/show_bug.cgi?id=11357 for reference) and since bug 11796 is taking care of the hardware cursor, I am closing the bug.