Re: [radeonhd] AMD 690G - dual head mode at high res. - Radeon HD

newer
0x9442:0x174B:0xE104: Sapphire ati...

Re: [radeonhd] AMD 690G - dual head mode at high res.

older
xf86-video-radeonhd:master: 1...

Egbert Eich

9 Jan 2009 9 Jan '09

11:50

scott.radeonhd@scottrix.co.uk writes:

...

All

I have a gigabyte GA-MA690G-S3H motherboard with the AMD 690G chipset. Until recently I was using the VGA output connected to a 1280x1024 CRT and the DVI_D output connected to a 1920x1200 LCD, this worked fine. I now have two 1920x1200 LCDs one connected to the VGA and one to the DVI_D, however, I have been unable to get the VGA to display at 1920x1200. Instead everything in software on the box thinks the VGA is at 1920x1200 (xrandr, but X start up logs), however, the screen is actually at 1600x1200. The radeon (NOT HD) driver seemed to work a little better in that both screens were put in the same mode, however, the bottom screen in the setup would always get corruption. I am now using the ati driver which seems to work fine for this setup.

I am not sure how much testing I can do since this PC is used daily by myself and my wife and taking down X and restarting it would be a real pain. I might be able to do some testing with a second X server running on a different VT if people think that won't destroy my current setup.

I thought that maybe I am doing something wrong and if not then maybe someone on the list can test this setup and confirm it and then raise a bug if they can.

Please provide a a verbose log file. To obtain this start X from the console with: 'X -logverbose 7' and terminate it with ctrl-alt-backspace. Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Show replies by date

scott.radeonhd＠scottrix.co.uk

17 Mar 17 Mar

22:24

New subject: AMD 690G - dual head mode at high res.

Hi, Sorry it's been so long, I have read some of the posts on this list and tried the "UseAtomBios" setting and this then fixes the problem. I can if you want still produce the "X -logverbose 7" log file, but thought I should let you know that I have a solution. Thanks Scott. On Fri, Jan 09, 2009 at 12:50:06PM +0100, Egbert Eich wrote:

...

scott.radeonhd@scottrix.co.uk writes:

...
All

I have a gigabyte GA-MA690G-S3H motherboard with the AMD 690G chipset. Until recently I was using the VGA output connected to a 1280x1024 CRT and the DVI_D output connected to a 1920x1200 LCD, this worked fine. I now have two 1920x1200 LCDs one connected to the VGA and one to the DVI_D, however, I have been unable to get the VGA to display at 1920x1200. Instead everything in software on the box thinks the VGA is at 1920x1200 (xrandr, but X start up logs), however, the screen is actually at 1600x1200. The radeon (NOT HD) driver seemed to work a little better in that both screens were put in the same mode, however, the bottom screen in the setup would always get corruption. I am now using the ati driver which seems to work fine for this setup.

I am not sure how much testing I can do since this PC is used daily by myself and my wife and taking down X and restarting it would be a real pain. I might be able to do some testing with a second X server running on a different VT if people think that won't destroy my current setup.

I thought that maybe I am doing something wrong and if not then maybe someone on the list can test this setup and confirm it and then raise a bug if they can.

Please provide a a verbose log file. To obtain this start X from the console with: 'X -logverbose 7' and terminate it with ctrl-alt-backspace.

Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf

25 Mar 25 Mar

13:57

New subject: AMD 690G - dual head mode at high res.

On Mar 17, 09 22:24:16 +0000, scott.radeonhd@scottrix.co.uk wrote:

...

Sorry it's been so long, I have read some of the posts on this list and tried the "UseAtomBios" setting and this then fixes the problem. I can if you want still produce the "X -logverbose 7" log file, but thought I should let you know that I have a solution.

Can you try to use the undocumented Option "AtomBios" "pll=on" *instead* of the "UseAtomBios" option? This would help to narrow down the issue. CU Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

scott.radeonhd＠scottrix.co.uk

22 Mar 22 Mar

13:00

New subject: I'd like to help.....

All, I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ? Thanks Scott. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Alex Deucher

13:02

New subject: I'd like to help.....

On Mon, Mar 22, 2010 at 9:00 AM, wrote:

...

All,

I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ?

The asic documentation is linked from this page: http://wiki.x.org/wiki/DataSheets Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

scott.radeonhd＠scottrix.co.uk

25 Mar 25 Mar

10:00

New subject: I'd like to help.....

Thanks for the link, another question, should I be concentrating on the case when the driver is using AtomBIOS (Option "AtomBIOS" "True" in xorg) or without it ? Thanks, Scott. On Mon, Mar 22, 2010 at 09:02:47AM -0400, Alex Deucher wrote:

...

On Mon, Mar 22, 2010 at 9:00 AM, wrote:

...
All,

I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ?

The asic documentation is linked from this page: http://wiki.x.org/wiki/DataSheets

Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Alex Deucher

14:19

New subject: I'd like to help.....

On Thu, Mar 25, 2010 at 6:00 AM, wrote:

...

Thanks for the link, another question, should I be concentrating on the case when the driver is using AtomBIOS (Option "AtomBIOS" "True" in xorg) or without it ?

It depends what you are interested in working on. Using atom or not relates to mode setting, but is irrelevant for things like acceleration. Alex

...

Thanks,

Scott.

On Mon, Mar 22, 2010 at 09:02:47AM -0400, Alex Deucher wrote:

...
On Mon, Mar 22, 2010 at 9:00 AM, wrote:

...
All,

I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ?

The asic documentation is linked from this page: http://wiki.x.org/wiki/DataSheets

Alex

-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

scott.radeonhd＠scottrix.co.uk

14:34

New subject: I'd like to help.....

Alex, First I'd like to look into the problem I am having, without AtomBIOS VGA monitor is at 1600x1050 instead of 1920x1200 (xrandr + logs say it is at 1920x1200, but it isn't). With AtomBIOS DVI monitor is very flickerly, goes black for a second then back to X then black etc. etc. I have raised a bug, but I do understand that there are lots of bugs to fix and lots of features to add and far too little time to do either. Since I have done some lowlevel programming in the past I thought I might try and help. I guess this is mode setting and from what I understand I can't fix the AtomBIOS case since the mode settings are from the BIOS. Secondly, I'd like to look into UVD, however, it might be that Gallium3D provides this kind of acceleration, not 100% sure. Regards, Scott. On Thu, Mar 25, 2010 at 10:19:36AM -0400, Alex Deucher wrote:

...

On Thu, Mar 25, 2010 at 6:00 AM, wrote:

...
Thanks for the link, another question, should I be concentrating on the case when the driver is using AtomBIOS (Option "AtomBIOS" "True" in xorg) or without it ?

It depends what you are interested in working on. Using atom or not relates to mode setting, but is irrelevant for things like acceleration.

Alex

...
Thanks,

Scott.

On Mon, Mar 22, 2010 at 09:02:47AM -0400, Alex Deucher wrote:

...
On Mon, Mar 22, 2010 at 9:00 AM, wrote:

...
All,

I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ?

The asic documentation is linked from this page: http://wiki.x.org/wiki/DataSheets

Alex

-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Alex Deucher

15:10

New subject: I'd like to help.....

On Thu, Mar 25, 2010 at 10:34 AM, wrote:

...

Alex,

First I'd like to look into the problem I am having, without AtomBIOS VGA monitor is at 1600x1050 instead of 1920x1200 (xrandr + logs say it is at 1920x1200, but it isn't). With AtomBIOS DVI monitor is very flickerly, goes black for a second then back to X then black etc. etc. I have raised a bug, but I do understand that there are lots of bugs to fix and lots of features to add and far too little time to do either. Since I have done some lowlevel programming in the past I thought I might try and help. I guess this is mode setting and from what I understand I can't fix the AtomBIOS case since the mode settings are from the BIOS.

In both the atom and non-atom cases, the bugs are likely in the driver. The atombios problems are most likely an ordering issue or a problem with the parameters passed to the command tables rather than a problem with the tables themselves.

...

Secondly, I'd like to look into UVD, however, it might be that Gallium3D provides this kind of acceleration, not 100% sure.

Acceleration related things like video decoding would be handled in mesa or a separate backend lib for the API you want to accelerate. We have not released any documentation yet for the UVD block, however, video decode can be accelerated using the 3D engine. Alex

...

Regards,

Scott.

On Thu, Mar 25, 2010 at 10:19:36AM -0400, Alex Deucher wrote:

...
On Thu, Mar 25, 2010 at 6:00 AM, wrote:

...
Thanks for the link, another question, should I be concentrating on the case when the driver is using AtomBIOS (Option "AtomBIOS" "True" in xorg) or without it ?

It depends what you are interested in working on. Using atom or not relates to mode setting, but is irrelevant for things like acceleration.

Alex

...
Thanks,

Scott.

On Mon, Mar 22, 2010 at 09:02:47AM -0400, Alex Deucher wrote:

...
On Mon, Mar 22, 2010 at 9:00 AM, wrote:

...
All,

I'd like to help in the development of this driver how do I get involved ? Are there docs from AMD/ATI about the different cards and how to program them ? how do I get hold of them ?

The asic documentation is linked from this page: http://wiki.x.org/wiki/DataSheets

Alex

-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Matthias Hopf

16:45

New subject: I'd like to help.....

On Mar 25, 10 14:34:32 +0000, scott.radeonhd@scottrix.co.uk wrote:

...

First I'd like to look into the problem I am having, without AtomBIOS VGA monitor is at 1600x1050 instead of 1920x1200 (xrandr + logs say it is at 1920x1200, but it isn't). With AtomBIOS DVI monitor is very flickerly, goes black for a second then back to X then black etc. etc. I have raised

You typically want to concentrate first on the case that is used by default. Probably the best you can do is to trace the according calls, add some debug output of what is actually programmed, etc. Matthias -- Matthias Hopf __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

5150

Age (days ago)

5590

Last active (days ago)

List overview

Download

9 comments

4 participants

participants (4)

Alex Deucher
Egbert Eich
Matthias Hopf
scott.radeonhd＠scottrix.co.uk