radeonhd on my x1400 mobility with swsuspend - Radeon HD - openSUSE Mailing Lists

newer
Re: [radeonhd] radeonhd on my...

radeonhd on my x1400 mobility with swsuspend

older
ati mobility x2300 on asus f3jr -...

Maarten Lankhorst

22 Oct 2007 22 Oct '07

01:38

Hi all, After testing it again I got sick of the error that my fixed mode was invalid. So I looked at the fglrx X.org log and found out the same mode is used there. I created the attach hack. It may destroy your panel if you are not 100% sure your mode is valid. After that it worked for 100% proper, nice work. Only thing that gave me some trouble was suspend-to-ram. "echo mem > /sys/power/state" doesn't work, screen stays disabled (vesafb) or gets garbled (radeonhd) so I created a tiny script to use instead. I'm hoping that hopefully sometime soon I won't need to switch to console and restore vbemode there manually then switching back to x.org Cheers, Maarten. PS: This script will only work if there are no other potential bugs that would prevent swsuspend from working 100% succesfully.

Attachments:

disable-validating-fixed-modes-hack.patch (text/x-diff — 616 bytes)
sleep.sh (application/x-sh — 164 bytes)

Reply

Sign in to reply online Use email software

Show replies by date

Luc Verhaegen

22 Oct 22 Oct

14:50

On Mon, Oct 22, 2007 at 01:38:28AM +0200, Maarten Lankhorst wrote:

Hi all,

After testing it again I got sick of the error that my fixed mode was invalid. So I looked at the fglrx X.org log and found out the same mode is used there. I created the attach hack. It may destroy your panel if you are not 100% sure your mode is valid. After that it worked for 100% proper, nice work.

Only thing that gave me some trouble was suspend-to-ram. "echo mem > /sys/power/state" doesn't work, screen stays disabled (vesafb) or gets garbled (radeonhd) so I created a tiny script to use instead. I'm hoping that hopefully sometime soon I won't need to switch to console and restore vbemode there manually then switching back to x.org

Cheers, Maarten.

PS: This script will only work if there are no other potential bugs that would prevent swsuspend from working 100% succesfully.

commit 303e8c4d7c9eedfe01fa9e9650ca02aff51e920a Author: maarten Date: Sun Oct 21 13:42:31 2007 +0200

radeonhd: Dont validate fixed modes

diff --git a/src/rhd_modes.c b/src/rhd_modes.c index 700f643..7166549 100644 --- a/src/rhd_modes.c +++ b/src/rhd_modes.c @@ -1214,7 +1214,6 @@ rhdCreateModesListAndValidate(ScrnInfoPtr pScrn, Bool Silent) " \"%s\"\n", Output->Connector->Monitor->Name, Output->Connector->Name);

- Modes = rhdModesListValidateAndCopy(pScrn, Modes, Silent); Keepers = RHDModesAdd(Keepers, Modes); return Keepers; }

What caused you to create this patch has been altered, and i doubt that you will still need such a workaround. Please test a more recent version of the driver and report back. 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

Reply

Sign in to reply online Use email software

Maarten Lankhorst

15:15

Luc Verhaegen schreef:

What caused you to create this patch has been altered, and i doubt that you will still need such a workaround.

Please test a more recent version of the driver and report back.

I tried, it seems as of commit 5d003ae54dc23d286df31ea327913bfc1fddcf26 it is still needed unfortunately. Regards, Maarten. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

Luc Verhaegen

15:42

On Mon, Oct 22, 2007 at 03:15:43PM +0200, Maarten Lankhorst wrote:

Luc Verhaegen schreef:

...
What caused you to create this patch has been altered, and i doubt that you will still need such a workaround.

Please test a more recent version of the driver and report back.

I tried, it seems as of commit 5d003ae54dc23d286df31ea327913bfc1fddcf26 it is still needed unfortunately.

Regards, Maarten.

Can you get me a log of this? 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

Reply

Sign in to reply online Use email software

Maarten Lankhorst

16:13

Hi Luc, Luc Verhaegen schreef:

Can you get me a log of this?

Here you go. On a totally unrelated note: When will xrandr 1.2 support be added? Regards, Maarten.

Reply

Sign in to reply online Use email software

Luc Verhaegen

16:44

On Mon, Oct 22, 2007 at 04:13:34PM +0200, Maarten Lankhorst wrote:

Hi Luc,

Luc Verhaegen schreef:

...
Can you get me a log of this?

Here you go. On a totally unrelated note: When will xrandr 1.2 support be added?

Regards, Maarten.

Hi, Please comment out the monitor directive from your screen section in your xorg.conf. 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

Reply

Sign in to reply online Use email software

Maarten Lankhorst

17:43

Hi Luc, Luc Verhaegen schreef:

Please comment out the monitor directive from your screen section in your xorg.conf.

That seems to do the trick, hack is not needed if I use that. Would it be possible to fix, or at least emit a warning when screen is overridden? Cheers, Maarten. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

Luc Verhaegen

17:55

On Mon, Oct 22, 2007 at 05:43:37PM +0200, Maarten Lankhorst wrote:

Hi Luc,

Luc Verhaegen schreef:

...
Please comment out the monitor directive from your screen section in your xorg.conf.

That seems to do the trick, hack is not needed if I use that. Would it be possible to fix, or at least emit a warning when screen is overridden?

Cheers, Maarten.

Yeah, warning will happen soon, also, since X configurators like sax insist on creating a monitor section, there will be an option to tell the driver to ignore it. This monitor section is a deeply engrained paradigm that we should banish from our minds and configurators. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

Maarten Lankhorst

18:11

Hi Luc, Luc Verhaegen schreef:

Yeah, warning will happen soon, also, since X configurators like sax insist on creating a monitor section, there will be an option to tell the driver to ignore it.

This monitor section is a deeply engrained paradigm that we should banish from our minds and configurators.

Worse, Xorg :1 -configure created a monitor section too. It also seems that radeonhd fails to initialise by attaching a monitor to the vga output. The error I then get is: 'Horizontal blanking window too narrow'. I can send the xorg log again if needed. Cheers, Maarten. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

Luc Verhaegen

18:31

On Mon, Oct 22, 2007 at 06:11:58PM +0200, Maarten Lankhorst wrote:

Hi Luc,

Luc Verhaegen schreef:

...
Yeah, warning will happen soon, also, since X configurators like sax insist on creating a monitor section, there will be an option to tell the driver to ignore it.

This monitor section is a deeply engrained paradigm that we should banish from our minds and configurators.

Worse, Xorg :1 -configure created a monitor section too.

This things all still operate under the 1 driver, 1 device, 1 crtc, 1 monitor paradigm, which is hopelessly outdated.

It also seems that radeonhd fails to initialise by attaching a monitor to the vga output. The error I then get is: 'Horizontal blanking window too narrow'. I can send the xorg log again if needed.

This is to be expected. The timing of your panel and the timing of the monitor attached to the vga connector are not immediately compatible. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

Hans Ulrich Niedermann

23 Oct 23 Oct

02:01

Luc Verhaegen wrote:

This monitor section is a deeply engrained paradigm that we should banish from our minds and configurators.

How do I tell X and the driver what frequencies my non-DDC CRT can handle without a monitor section? -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

Reply

Sign in to reply online Use email software

6094

Age (days ago)

6096

Last active (days ago)

Download

10 comments

3 participants

tags

participants (3)

Hans Ulrich Niedermann
Luc Verhaegen
Maarten Lankhorst