Hi Matthias, just gave it a run (commit 98f46c6a) on a Gigabyte board with onboard graphics and sideport memory Manufacturer: "Gigabyte Technology Co., Ltd." Product: "GA-MA78GPM-DS2H" Vendor: "Award Software International, Inc." Version: "F1" Date: "06/03/2008" not all values seem plausible to me (f.e. voltages 0 or 0.5V or "Valdiated Ranges" (Typo) with a memory clock of 0 kHz. Current Memory Clock: 2075509760 seems out of range. And Maximum Pixel Clock: 400000 seems to be very low (assuming the SI-unit Hz is meant - at other places the the unit (kHz) is explicitly mentioned?) (II) Module "ddc" already built-in (II) RADEONHD(0): Minimum Pixel ClockPLL Frequency Output: 0 (II) RADEONHD(0): Maximum Pixel ClockPLL Frequency Output: 1200000 (II) RADEONHD(0): Maximum Pixel Clock: 400000 (II) RADEONHD(0): Reference Clock: 14320 (II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00000000 (size = 0x00004000) (II) RADEONHD(0): FB: Allocated Cursor Image at offset 0x00004000 (size = 0x00004000) (II) RADEONHD(0): FirmwareInfo Revision 0104 (II) RADEONHD(0): Unused attribute: ul3DAccelerationEngineClock 0 (II) RADEONHD(0): Unused attribute: ulDriverTargetEngineClock 0 (II) RADEONHD(0): Unused attribute: ulDriverTargetMemoryClock 0 (II) RADEONHD(0): Unused attribute: ucASICMaxTemperature 0 (II) RADEONHD(0): Scary bits: Estimated MinEngineClock 250000 kHz (II) RADEONHD(0): Scary bits: Estimated MinMemoryClock 250000 kHz (II) RADEONHD(0): Default Engine Clock: 500000 (II) RADEONHD(0): Default Memory Clock: 400000 (II) RADEONHD(0): Current Engine Clock: 494040 (II) RADEONHD(0): Current Memory Clock: 2075509760 (II) RADEONHD(0): Current Chip Voltage: 0 (II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Power management: used engine clock / memory clock / voltage: (II) RADEONHD(0): Off 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Idle 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Slow2D 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Fast2D 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Slow3D 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Fast3D 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Max3D 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): User 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Connector[0] {RHD_CONNECTOR_VGA, "VGA CRT1", RHD_DDC_0, RHD_HPD_NONE, { RHD_OUTPUT_DACA, RHD_OUTPU T_NONE } } could you move the (II) RADEONHD(0): Power management: used engine clock / memory clock / voltage: a few lines up, so it's easier to get the meanings of the respective columns? Thanks for radeonhd!) Greetings, Frieder PS: latest BIOS for the above board is F5 (I'm at F1) so maybe I should update. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
2009/7/22 Frieder Ferlemann
(II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V
Same for me. weird/null/werid vs. null/werid/null. Will debug that on Sunday. -- Rafał Miłecki -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Jul 23, 09 09:31:31 +0200, Rafał Miłecki wrote:
2009/7/22 Frieder Ferlemann
: (II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V
Same for me. weird/null/werid vs. null/werid/null. Will debug that on Sunday.
Before that, try latest git. I fixed some of the validation routines :-]
Matthias
--
Matthias Hopf
On Jul 22, 09 22:41:34 +0200, Frieder Ferlemann wrote:
just gave it a run (commit 98f46c6a) on a Gigabyte board with onboard graphics and sideport memory
Thanks :)
not all values seem plausible to me (f.e. voltages 0 or 0.5V or "Valdiated Ranges" (Typo) with a memory clock of 0 kHz.
O-key. Apparently there are still issues. Values '0' indicate unknown values, but the validated values should be either valid, or all 0. I think I made a logical mistake there. If the voltage is not known at all, it should never be set.
Current Memory Clock: 2075509760 seems out of range.
Indeed.
And Maximum Pixel Clock: 400000 seems to be very low (assuming the SI-unit Hz is meant - at other places the the unit (kHz) is explicitly mentioned?)
It's always kHz. Some authors didn't bother with units :-]
(II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V
Indeed, this is *very* broken.
could you move the (II) RADEONHD(0): Power management: used engine clock / memory clock / voltage: a few lines up, so it's easier to get the meanings of the respective columns?
Ah, right.
PS: latest BIOS for the above board is F5 (I'm at F1) so maybe I should update.
Before you do that, please dump your current BIOS and send it to me.
It seems sufficiently broken to be interesting :-)
rhd_conntest -d <pci-tag>
Matthias
--
Matthias Hopf
Hi Matthias, previously:
(II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V
a rerun with commit 9c66f5fb looks better: (II) RADEONHD(0): Default Engine Clock: 500000 (II) RADEONHD(0): Default Memory Clock: 400000 (II) RADEONHD(0): Current Engine Clock: 494040 (II) RADEONHD(0): Current Memory Clock: 3005391872 (II) RADEONHD(0): Current Chip Voltage: 0 (II) RADEONHD(0): Power Management: used engine clock / memory clock / core (VDDC) voltage (0: ignore) (II) RADEONHD(0): Power Management: Raw Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power Management: Validated Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power Management: Final Levels (II) RADEONHD(0): Off 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Idle 250000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow2D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast2D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Max3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): User 500000 kHz / 400000 kHz / 0.000 V
Before you do that, please dump your current BIOS and send it to me. It seems sufficiently broken to be interesting :-)
rhd_conntest -d <pci-tag>
That one goes per PM. Different versions of the complete firmware are available at: http://www.gigabyte.com.tw/Support/Motherboard/BIOS_Model.aspx?ProductID=285... They use a dangerous and deprecated compression format ".exe", (MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit) I'm not sure but it seems to extract without side-effects with: wine motherboard_bios_ga-ma78gpm-ds2h_f5.exe Greetings, Frieder -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Jul 23, 09 17:24:47 +0200, Frieder Ferlemann wrote:
a rerun with commit 9c66f5fb looks better:
:-) Current git now includes the readout of known good configurations
from AtomBIOS - that might help significantly in your case.
CU
Matthias
--
Matthias Hopf
FYI: figures for my notebook with HD3470 mobility (Sony VGN-SR21M/S)
commit eabbde4e4cc8
(II) RADEONHD(0): Power Management: Raw Ranges
(II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.950 V
(II) RADEONHD(0): Maximum 0 kHz / 0 kHz / 1.200 V
(II) RADEONHD(0): Default 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): PowerPlayInfo Revision 0401
(II) RADEONHD(0): Power Management: Validated Ranges
(II) RADEONHD(0): Minimum 110000 kHz / 250000 kHz / 0.950 V
(II) RADEONHD(0): Maximum 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Default 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Power Management: Known Good Configurations
(II) RADEONHD(0): 1 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): 2 110000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 3 300000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 4 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): 5 110000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 6 110000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 7 300000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 8 300000 kHz / 405000 kHz / 1.200 V
(II) RADEONHD(0): 9 550000 kHz / 700000 kHz / 1.200 V
(II) RADEONHD(0): 10 550000 kHz / 700000 kHz / 1.200 V
(II) RADEONHD(0): 11 300000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): 12 300000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): 13 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): 14 300000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): 15 300000 kHz / 405000 kHz / 0.950 V
(II) RADEONHD(0): Power Management: Final Levels
(II) RADEONHD(0): Off 110000 kHz / 250000 kHz / 0.950 V
(II) RADEONHD(0): Idle 340000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Slow2D 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Fast2D 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Slow3D 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Fast3D 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): Max3D 680000 kHz / 800000 kHz / 1.200 V
(II) RADEONHD(0): User 680000 kHz / 800000 kHz / 1.200 V
Is there anything else I can provide/test to help you with pm?
txs and LieGrue,
strub
--- On Thu, 7/23/09, Frieder Ferlemann
From: Frieder Ferlemann
Subject: Re: [radeonhd] RE: Powersaving... To: "Matthias Hopf" , radeonhd@opensuse.org Date: Thursday, July 23, 2009, 5:24 PM Hi Matthias, previously:
(II) RADEONHD(0): Power management: Raw Ranges (II) RADEONHD(0): Global Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power management: Valdiated Ranges (II) RADEONHD(0): Global Minimum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Global Maximum 494040 kHz / 0 kHz / 0.500 V (II) RADEONHD(0): Global Default 0 kHz / 0 kHz / 0.000 V
a rerun with commit 9c66f5fb looks better:
(II) RADEONHD(0): Default Engine Clock: 500000 (II) RADEONHD(0): Default Memory Clock: 400000 (II) RADEONHD(0): Current Engine Clock: 494040 (II) RADEONHD(0): Current Memory Clock: 3005391872 (II) RADEONHD(0): Current Chip Voltage: 0 (II) RADEONHD(0): Power Management: used engine clock / memory clock / core (VDDC) voltage (0: ignore) (II) RADEONHD(0): Power Management: Raw Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 0 kHz / 0 kHz / 0.000 V (II) RADEONHD(0): Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power Management: Validated Ranges (II) RADEONHD(0): Minimum 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Maximum 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Default 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Power Management: Final Levels (II) RADEONHD(0): Off 250000 kHz / 250000 kHz / 0.000 V (II) RADEONHD(0): Idle 250000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow2D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast2D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Slow3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Fast3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): Max3D 500000 kHz / 400000 kHz / 0.000 V (II) RADEONHD(0): User 500000 kHz / 400000 kHz / 0.000 V
Before you do that, please dump your current BIOS and send it to me. It seems sufficiently broken to be interesting :-)
rhd_conntest -d <pci-tag>
That one goes per PM.
Different versions of the complete firmware are available at: http://www.gigabyte.com.tw/Support/Motherboard/BIOS_Model.aspx?ProductID=285...
They use a dangerous and deprecated compression format ".exe", (MS-DOS executable PE for MS Windows (GUI) Intel 80386 32-bit) I'm not sure but it seems to extract without side-effects with: wine motherboard_bios_ga-ma78gpm-ds2h_f5.exe
Greetings, Frieder -- 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
On Jul 23, 09 17:41:26 +0000, Mark Struberg wrote:
FYI: figures for my notebook with HD3470 mobility (Sony VGN-SR21M/S)
Looking good.
Is there anything else I can provide/test to help you with pm?
Not ATM.
Next thing will be to select reasonable settings for the default levels
in rhdPmSelectSettings(). That would be a playground for others
(including you if you want to get your hands dirty :-), I will
concentrate on getting the engines idle etc. so we can actually change
the settings on the fly. Only if that works, we can test whether the
power settings are actually any good.
Because rhdPmSelectSettings() does only rudamentary stuff ATM, the
"Power Management: Final Levels" don't contain really reasonable power
levels yet.
I'm just writing something up for you guys and will blog about it.
Thanks
Matthias
--
Matthias Hopf
2009/7/23 Matthias Hopf
Next thing will be to select reasonable settings for the default levels in rhdPmSelectSettings(). That would be a playground for others (including you if you want to get your hands dirty :-), I will concentrate on getting the engines idle etc. so we can actually change the settings on the fly. Only if that works, we can test whether the power settings are actually any good.
We (me and Yang) agree both: setting engine and memory clocks doesn't need manual idle-ing anything. It's done in setting AtomBIOS function. -- Rafał Miłecki -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
2009/7/23 Rafał Miłecki
2009/7/23 Matthias Hopf
: Next thing will be to select reasonable settings for the default levels in rhdPmSelectSettings(). That would be a playground for others (including you if you want to get your hands dirty :-), I will concentrate on getting the engines idle etc. so we can actually change the settings on the fly. Only if that works, we can test whether the power settings are actually any good.
We (me and Yang) agree both: setting engine and memory clocks doesn't need manual idle-ing anything. It's done in setting AtomBIOS function.
It's not done in the atom functions. The atom tables wait for the plls to lock, but not for the engine or MC to be idle. Alex -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Hi, Matthias Hopf schrieb:
Current Memory Clock: 2075509760 seems out of range.
Indeed.
this clock seems to be more or less random. With a sequence of init 3 init 5 I got Memory Clocks of 3331032064 3768198144 2083972096 1651262464 3061892096 (all of them ending with 0x400 if converted to hex)
PS: latest BIOS for the above board is F5 (I'm at F1) so maybe I should update.
Before you do that, please dump your current BIOS and send it to me. It seems sufficiently broken to be interesting :-)
rhd_conntest -d <pci-tag>
Just a note, I updated to F5 (2009/06/01) and the dump of the BIOS is identical. So at least it didn't get less interesting... (Other than that its a nice low power low cost board with dual bios and the things interesting for a HTPC) Greetings, Frieder -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Jul 23, 09 23:12:16 +0200, Frieder Ferlemann wrote:
Current Memory Clock: 2075509760 seems out of range. Indeed.
Matthias Hopf schrieb: this clock seems to be more or less random. With a sequence of init 3 init 5 I got Memory Clocks of 3331032064 3768198144
OMFG. ParseTable returns CD_SUCCESS if the command table does not exist.
And in your AtomBIOS, GetMemoryClock is not implemented. So far we had
no chance to determine this situation. It could well be that other,
completely unrelated bugs have been triggered by this as well.
(Hopefully) fixed in current git now, please retest.
Matthias
--
Matthias Hopf
Hi Matthias, Matthias Hopf schrieb:
On Jul 23, 09 23:12:16 +0200, Frieder Ferlemann wrote:
Current Memory Clock: 2075509760 seems out of range. Indeed.
Matthias Hopf schrieb: this clock seems to be more or less random. With a sequence of init 3 init 5 I got Memory Clocks of 3331032064 3768198144
OMFG. ParseTable returns CD_SUCCESS if the command table does not exist. And in your AtomBIOS, GetMemoryClock is not implemented. So far we had no chance to determine this situation. It could well be that other, completely unrelated bugs have been triggered by this as well.
(Hopefully) fixed in current git now, please retest.
Current git (d19a10b7) seems to work for me. It does not behave completely reproducable though. The Xorg.0.log differs, I'm appending two bz2 compressed of versions of them. I hope they make it to the list. ("bzdiff" might be handy for comparison and "less" handles them without decompression here) Xorg.0.log.d19a10b7.2.bz2 Xorg.0.log.d19a10b7.3.bz2 <- the EDID data is read once more here In line 786 of Xorg.0.log.d19a10b7.3.bz2 there is some strangeness: (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline "(204{" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync line 586 did it better: (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline "1920x1200" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync Greetings, Frieder PS: and a typo (missing 'p' in stoped) (II) RADEONHD(0): RHDHdmiUpdateAudioSettings: stoped with
On Jul 25, 09 18:42:36 +0200, Frieder Ferlemann wrote:
OMFG. ParseTable returns CD_SUCCESS if the command table does not exist. And in your AtomBIOS, GetMemoryClock is not implemented. So far we had no chance to determine this situation. It could well be that other, completely unrelated bugs have been triggered by this as well.
(Hopefully) fixed in current git now, please retest.
Current git (d19a10b7) seems to work for me.
This might have to be retested in the future - the patch might have broken some other stuff... But I'm still hopeful :-)
Xorg.0.log.d19a10b7.2.bz2 Xorg.0.log.d19a10b7.3.bz2 <- the EDID data is read once more here
Ignore that for now - I have no clue what's happening here either, but I think it's not driver related.
In line 786 of Xorg.0.log.d19a10b7.3.bz2 there is some strangeness: (II) RADEONHD(0): On Crtc 0 Setting 60.0 Hz Mode: Modeline "(204{" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync
Standard !@#$% RandR behavior. Apparently as soon as a mode is actually used, the Mode description gets free()d, but the Mode description pointer is not NULLed. Don't know what we can do about that, probably the best would be to fix RandR.
PS: and a typo (missing 'p' in stoped) (II) RADEONHD(0): RHDHdmiUpdateAudioSettings: stoped with
Fixed.
Thanks
Matthias
--
Matthias Hopf
participants (5)
-
Alex Deucher
-
Frieder Ferlemann
-
Mark Struberg
-
Matthias Hopf
-
Rafał Miłecki