[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 Thom changed: What|Removed |Added CC||madeforspam at telfort.nl --- Comment #38 from Thom --- I landed here via: https://bugs.freedesktop.org/show_bug.cgi?id=87682 With the same issue mentioned by user Lockheed and the exact same chip (RS780M). Last comment in that post (from Alex Deucher) referred to this bugreport. On my RS780M I have exactly the same artefacts on my LVDS on any kernel version higher than 3.13 ( https://www.youtube.com/watch?v=nx2-Fvihzxg ) strangely enough the VGA out is not affected. Kernels tested up to 4.4.0 Would you like me to add some more info or would you like me to file a separate bug ? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #37 from Alex Deucher --- (In reply to Joerg Esser from comment #35) > I had similar problems until I used 3.18.7. > I couldn´t even boot beyond radeon load. The whole kernel crashed and my > Monitor showed no usable signal. I had to blacklist and load it manually > with option radeon.dpm=0, after turning on my Monitor . With kernel 3.18.6 I > could use the radeon option radeon.aspm=0, but still had to turn on my > Monitor before radeon module load. > > Now with this kernel I only need radeon.aspm=0 and no blacklist option, > either the Monitor is turned on before or after radeon module load. Also GPU > speedup with Video output works fine. Please file a different bug. This bug and the patch only affect old asics like the RS880. Something else must have fixed the issue for you. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #36 from Joerg Esser --- Oh I forgot, In the kernel changelog it also hits bug 91861. And it isn´t in 3.19 because there I still have those problem. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 Joerg Esser changed: What|Removed |Added CC||jackfritt at boh.de --- Comment #35 from Joerg Esser --- I had similar problems until I used 3.18.7. I couldn´t even boot beyond radeon load. The whole kernel crashed and my Monitor showed no usable signal. I had to blacklist and load it manually with option radeon.dpm=0, after turning on my Monitor . With kernel 3.18.6 I could use the radeon option radeon.aspm=0, but still had to turn on my Monitor before radeon module load. Now with this kernel I only need radeon.aspm=0 and no blacklist option, either the Monitor is turned on before or after radeon module load. Also GPU speedup with Video output works fine. Thx alot!! Here´s my card info lspci -s 01:00.0 -vv 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device e157 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [150 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Kernel driver in use: radeon -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #34 from Alex Deucher --- Already upstream: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=72edd83cc9e5819ed1ee771519143d7594e059f0 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 tuxoholic at hotmail.de changed: What|Removed |Added CC||tuxoholic at hotmail.de --- Comment #33 from tuxoholic at hotmail.de --- Hello Christian It took me a while to regather my bugzilla login info, so I'm not sure whether you pushed this fix into kernel-git already or still are awaiting feedback, anyway ... I'm quoting my testing results I wrote in the debian bugtracker (#770790): That small patch in attachment #163891 does indeed fix the screen flickering for me. I built three versions of radeon.ko against 3.16.7-ckt2 from debian/testing: 1) vanilla version: reproducible flickering, it's even easier to reproduce by quickly dragging a medium sized window around in circles 2) superseded version: (attachment #159331): no flickering, might contain a typo on line 1002, but I did not fix that one and it ran flawless for days 3) current version: (#attachment 163891): no flickering So to sum up: this small fix in #163891 is a blessing, I vote for pushing this if it hasn't happened already. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 Christian König changed: What|Removed |Added Attachment #156211|0 |1 is obsolete|| Attachment #159331|0 |1 is obsolete|| --- Comment #32 from Christian König --- Created attachment 163891 --> https://bugzilla.kernel.org/attachment.cgi?id=163891&action=edit Possible fix Unfortunately I don't have any more ideas either. There must be some undocumented limitation on RS880 and maybe older chips that don't seem to exists any more on newer ones. Unfortunately my last RS880 based system blow up about a month ago, so I can't test this any more. Please test the attached patch, it just artificial limits the reference divider to 7 on RS880 and older chips. If that works I'm going to submit the patch upstream. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #31 from kb at spatium.org --- Christian, do you have any further ideas? Can perhaps the ref_div_max be settable via sysfs so that I can cap it on boot? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #30 from Markus Gaugusch --- Additional info: With the (unmodified) patch applied, I get a message "Nonpreset Mode" displayed on my monitor when I turn it on. So I think the patch is not 100% correct ... -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #29 from Markus Gaugusch --- Hi, I've also verified that commit 32167016076f714f0e35e287fbead7de0f1fb179 breaks my system: 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] (prog-if 00 [VGA controller]) The attached patch works fine for me. Without the patch, I can no longer use the DVI connector of my (onboard) graphics card, only VGA works. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #28 from kb at spatium.org --- I think your patch has a typo on line 1002 should be ref_div_max not fb_div_max. Anyway I played with the numbers and I found a config that works for me. See below for all the different combos. Right now I'm running with ref_div_max capped to 2 and going to test it in prolonged use. Any further ideas about this? fb/ref => outcome 4000/13 => mode not supported (message on TV screen) 2000/13 => MNS 1000/13 => MNS 500/13 => MNS 4000/1023 => MNS 2000/1023 => MNS 1000/1023 => MNS 20470/1023 => (nominal value without any capping) flicker 1/1023 => flicker 8000/1023 => different type of flicker, then blank screen 6000/1023 => MNS 20470/13 => flicker 20470/11 => flicker 20470/10 => flicker 20470/9 => very seldom flicker 20470/7 => stable! 20470/2 => stable! -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #27 from Christian König --- Created attachment 159331 --> https://bugzilla.kernel.org/attachment.cgi?id=159331&action=edit Testing patch. (In reply to kb from comment #26) > (In reply to Christian König from comment #25) > > You could try to artificially limit ref_div_max or fb_div_max until you get > > a stable signal once more. Maybe this will yield some more light on the root > > cause of the issue. > > Can you give me some details - how to do this? Attached is a testing patch which adds an artificially upper limit to 400.0 for the feedback divider (normal range 17.0-2048.0) and an upper limit of 13 for the reference divider (normal range 2-15). I suggest you start playing with the feedback divider values until you can figure out the limits for your hardware. E.g. try 400 as in my patch first, if that works raise it to 800 if that doesn't work go down to 600 again etc.. > > > > Do you think change of graphics card would resolve the issue? > > > > Well, most likely yes. > > > > But the new kernel seems to work better for some people, but has regressed > > for you. So I would really like to create a solution that works for > > everybody. > > Right now I switched to catalyst which seems to work and allows me to use > new kernel. But since apparently my card is "legacy" I had to downgrade to > xorg server 1.12 :-| Yeah, that's the problem I've got as well. The hardware isn't supported any more so the whole documentation is not available. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #26 from kb at spatium.org --- (In reply to Christian König from comment #25) > You could try to artificially limit ref_div_max or fb_div_max until you get > a stable signal once more. Maybe this will yield some more light on the root > cause of the issue. Can you give me some details - how to do this? > > Do you think change of graphics card would resolve the issue? > > Well, most likely yes. > > But the new kernel seems to work better for some people, but has regressed > for you. So I would really like to create a solution that works for > everybody. Right now I switched to catalyst which seems to work and allows me to use new kernel. But since apparently my card is "legacy" I had to downgrade to xorg server 1.12 :-| -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #25 from Christian König --- (In reply to kb from comment #24) > Any ideas on this? It's really annoying as I need to keep away from > upgrading kernel past 3.14. :( Unfortunately not, cause I don't have any idea what's causing this. You could try to artificially limit ref_div_max or fb_div_max until you get a stable signal once more. Maybe this will yield some more light on the root cause of the issue. > Do you think change of graphics card would resolve the issue? Well, most likely yes. But the new kernel seems to work better for some people, but has regressed for you. So I would really like to create a solution that works for everybody. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #24 from kb at spatium.org --- Any ideas on this? It's really annoying as I need to keep away from upgrading kernel past 3.14. :( Do you think change of graphics card would resolve the issue? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #23 from kb at spatium.org --- Created attachment 158001 --> https://bugzilla.kernel.org/attachment.cgi?id=158001&action=edit dmesg #3 -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461
--- Comment #22 from kb at spatium.org ---
I've also added this line
DRM_DEBUG_KMS("in patched branch: %u\n", ref_div_max);
add the end of your patch, i.e. after
ref_div_max = min(ref_div_max, pll->reference_freq / in_min);
just to make sure the new code gets hit.
I see this in dmesg
[ 23.002707] [drm:radeon_compute_pll_avivo] in patched branch: 13
and I'm attaching the full output as well. Hope it gives you some more ideas.
--
You are receiving this mail because:
You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #21 from Christian König --- (In reply to kb from comment #20) > Hi, unfortunately supplied patch does not fix the issue. Do you need some > more debug output? dmesg output generated with drm.debug=0xE on the kernel command line would be nice. But I'm running out of idea what else this could be. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #20 from kb at spatium.org --- Hi, unfortunately supplied patch does not fix the issue. Do you need some more debug output? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 Christian König changed: What|Removed |Added Attachment #155721|0 |1 is obsolete|| --- Comment #19 from Christian König --- Created attachment 156211 --> https://bugzilla.kernel.org/attachment.cgi?id=156211&action=edit Possible fix Please try the attached patch. It's based on top of Alex drm-fixes-3.18 branch, but should apply to older ones as well. The problem seems to be that with a reference frequency of 14.32Mhz and a reference divider of 14 we get 1.0228Mhz which is very close to the minimum input frequency of 1Mhz. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #18 from kb at spatium.org --- OK, false alarm. I had a wrong kernel. Correct output attached. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #17 from kb at spatium.org --- Created attachment 156071 --> https://bugzilla.kernel.org/attachment.cgi?id=156071&action=edit dmesg round 2 with correct kernel -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #16 from kb at spatium.org --- I applied the patch but don't see any of the extra msgs in the dmesg. Maybe it's because i'm running it on the BAD kernel? Can you make a patch against 3.14 (this one doesn't apply cleanly on 3.14)? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #15 from kb at spatium.org --- Created attachment 156061 --> https://bugzilla.kernel.org/attachment.cgi?id=156061&action=edit dmesg 2nd run -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #14 from Christian König --- Created attachment 155721 --> https://bugzilla.kernel.org/attachment.cgi?id=155721&action=edit Add more debugging output. Please apply the attached patch and provide new dmesg created with drm.debug=0xE It should now show a bit more debugging output about your hardware. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #13 from Christian K?nig --- (In reply to kb from comment #12) > note xrandr is on good kernel, dmesg in on bad Those outputs should work fine. Going to make a patch for this, but this might take a while. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #12 from kb at spatium.org --- note xrandr is on good kernel, dmesg in on bad -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #11 from kb at spatium.org --- Created attachment 154681 --> https://bugzilla.kernel.org/attachment.cgi?id=154681&action=edit dmesg with drm.debug=0xe on BAD kernel -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #10 from kb at spatium.org --- Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x51 Timestamp: 20519 Subpixel: no subpixels Clones: CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: load detection: 1 range: (0, 1) HDMI-0 connected 1920x1080+0+0 (0x54) normal (normal left inverted right x axis y axis) 160mm x 90mm Identifier: 0x52 Timestamp: 20519 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004c2d09050100 30120103801009780aee91a3544c9926 0f5054bdef80714f8100814081809500 950fb3000101023a801871382d40582c 4500a05a001e662150b051001b30 40703600a05a001e00fd0018 4b1a5117000a20202020202000fc 0053414d53554e470a2020202020016f 020327f14b901f041305140312202122 230907078301e2000fe305030167 030c003000b82d011d007251d01e206e 285500a05a001e011d00bc52d01e 20b8285540a05a001e011d801871 1c1620582c2500a05a009e011d80 d0721c1620102c2580a05a009e00 00fd dither: off supported: off, on audio: auto supported: off, on, auto underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, on, auto coherent: 1 range: (0, 1) 1920x1080 (0x54) 148.500MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x55) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x56) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125 clock 59.94Hz 1920x1080i (0x57) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1094 total 1125 clock 60.00Hz 1920x1080i (0x58) 74.250MHz +HSync +VSync Interlace h: width 1920 start 2448 end 2492 total 2640 skew0 clock 28.12KHz v: height 1080 start 1084 end 1094 total 1125 clock 50.00Hz 1920x1080 (0x59) 74.250MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.75KHz v: height 1080 start 1084 end 1089 total 1125 clock 30.00Hz 1920x1080 (0x5a) 74.250MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 28.12KHz v: height 1080 start 1084 end 1089 total 1125 clock 25.00Hz 1920x1080 (0x5b) 74.250MHz +HSync +VSync h: width 1920 start 2558 end 2602 total 2750 skew0 clock 27.00KHz v: height 1080 start 1084 end 1089 total 1125 clock 24.00Hz 1920x1080i (0x5c) 74.176MHz +HSync +VSync Interlace h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.72KHz v: height 1080 start 1084 end 1094 total 1125 clock 59.94Hz 1920x1080 (0x5d) 74.176MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 33.72KHz v: height 1080 start 1084 end 1089 total 1125 clock 29.97Hz 1920x1080 (0x5e) 74.176MHz +HSync +VSync h: width 1920 start 2558 end 2602 total 2750 skew0 clock 26.97KHz v: height 1080 start 1084 end 1089 total 1125 clock 23.98Hz 1680x1050 (0x5f) 119.000MHz +HSync -VSync h: width 1680 start 1728 end 1760 total 1840 skew0 clock 64.67KHz v: height 1050 start 1053 end 1059 total 1080 clock 59.88Hz 1280x1024 (0x60) 135.000MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew0 clock 79.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.02Hz 1280x1024 (0x61) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1440x900 (0x62) 136.750MHz -HSync +VSync h: width 1440 start 1536 end 1688 total 1936 skew0 clock 70.64KHz v: height 900 start 903 end 909 total 942 clock 74.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #9 from Christian K?nig --- Please provide the output of "xrandr --verbose" and of dmesg when booted with "drm.debug=0xe" on the kernel command line. Thanks, Christian. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #8 from kb at spatium.org --- Also, I've noticed that when X boots, the "good" kernels give this sequence: 1) TV blanks with "No signal" message briefly 2) Desktop shows normally And the "bad" kernels give: 1) TV blanks with "Mode not supported" message for a longer time 2) Desktop shows, blinking and/or flickering -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #7 from kb at spatium.org --- 32167016076f714f0e35e287fbead7de0f1fb179 is the first bad commit commit 32167016076f714f0e35e287fbead7de0f1fb179 Author: Christian K?nig Date: Fri Mar 28 18:55:10 2014 +0100 drm/radeon: rework finding display PLL numbers v2 This completely reworks how the PLL parameters are generated and should result in better matching dot clock frequencies. Probably needs quite a bit of testing. bugs: https://bugs.freedesktop.org/show_bug.cgi?id=76564 v2: more cleanup and comments. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher :04 04 1a91914271fc3761ec6961fa0cc4bded879bd05c c0ab21500dcb8d2876f4744e4465c9aa7203a113 Mdrivers -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #6 from kb at spatium.org --- I'll have to setup the enviro, it'll take some time. But yeah, I'll do it. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #5 from Alex Deucher --- (In reply to kb from comment #0) > > Downgrading to 3.14 seems to remove the issue. Can you bisect to find out what change caused this regression? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #4 from kb at spatium.org --- ok i tried it and surprisingly it does not help. I have flicker, but i don't get the ELD messages. Note I also use video=HDMI-A-1:640x480 for the kernel to get a usable resolution in the text console. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 --- Comment #3 from Alex Deucher --- Can you try it to be sure to at least narrow down what the problem might be? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 kb at spatium.org changed: What|Removed |Added Regression|No |Yes --- Comment #2 from kb at spatium.org --- I haven't tried myself, but according to publicly available forums it would help. However, I need hdmi audio working, so I can't use this as a workaround. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 83461] hdmi screen flicker/unusable
https://bugzilla.kernel.org/show_bug.cgi?id=83461 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1 from Alex Deucher --- Does booting with radeon.audio=0 on the kernel command line in grub fix the issue? You can also disable audio on the fly xrandr. E.g., xrandr --output HDMI-0 --set audio off -- You are receiving this mail because: You are watching the assignee of the bug.
