Bug 68244 - screen flickering and no sound with radeon.audio=1 when using hdmi on HD5450
Summary: screen flickering and no sound with radeon.audio=1 when using hdmi on HD5450
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-18 18:15 UTC by dagg
Modified: 2013-09-26 17:00 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
output of avivotool regs hdmi (661 bytes, text/plain)
2013-08-18 18:15 UTC, dagg
no flags Details

Description dagg 2013-08-18 18:15:37 UTC
Created attachment 84210 [details]
output of  avivotool regs hdmi

Hello,

I'm running gentoo with kernel 3.10.7 in a multiseat (hd5450, hd3650 and intel hd3000) config in which I use the hd5450 gpu for xbmc with uvd and hdmi enabled.

for some reason I don't have sound and the screen flickers from time to time.
dmesg and Xorg logs doesn't signal anything special.

I've tried to patch the kernel with Rafal Milecki's "[FIX][PATCH] drm/radeon: fix WREG32_OR macro setting bits in a register" fix but it still didn't worked.
Comment 1 dagg 2013-09-07 15:20:15 UTC
any updates on this matter? the issue is still unresolved in kernel 3.11

I'd be happy to provide any needed outputs.
Comment 2 dagg 2013-09-26 17:00:58 UTC
ok, the sound issue is resolved, here is the explenation.

with Mr. Konig's help, I was able to make the sound work when rerouting the feed to the following card: card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]

strangly when I was using the intel card, I streamed it directly to the intel card.

it seems to tno be an issue with the alsa drivers so I've posted a question on the alsa mailing list on the matter.

so the sound it not dri issue.

the flickering is still an issue, I'll try to gather more info and open a new bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.