Created attachment 88136 [details] dmesg on 3.11.6 HDMI audio was working at some point in the past. Some upgrades or changes I did while on Ubuntu 13.04 caused it to stop working, so I tried to upgrade to 13.10. I also tried upgrading to a newer 3.11 generic kernel (which didn't help). $ uname -a Linux fserv 3.11.6-031106-generic #201310181453 SMP Fri Oct 18 18:54:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I have the radeon.audio=1 parameter in my kernel command line, and I've got the 1,3 device in my aplay -l. When I try playing a sound through the speakers, using mplayer, aplay, or speaker-test, it looks like it's working, but I get no sound. The TV's sound works fine with other machines, and used to work with this machine. I've attached my dmesg, the output of avivotools regs hdmi, some output from aplay, and my asound.conf.
Created attachment 88137 [details] asound.conf file from the machine
Created attachment 88138 [details] lspci output
Created attachment 88139 [details] output of 'sudo avivotool regs hdmi'
Created attachment 88140 [details] output of aplay -L and aplay -l
https://bugs.freedesktop.org/show_bug.cgi?id=70660 Mind changing defaults.pcm.dmix.rate to 44100 to see if we share the same problem?
>Mind changing defaults.pcm.dmix.rate to 44100 to see if we share the same problem? Unfortunately, no such luck. I changed that setting in asound.conf and tried a speaker-test forced to that rate, still no sound. $ speaker-test -c 2 -r 44100 -D hw:1,3 speaker-test 1.0.27.1 Playback device is hw:1,3 Stream parameters are 44100Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 44100Hz (requested 44100Hz) Buffer size range from 64 to 16384 Period size range from 32 to 8192 Using max buffer size 16384 Periods = 4 was set period_size = 4096 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5.577833
By the way, soon after I replied you I found that the audio could be affected by the resolution you are using. See the following bug: https://bugs.freedesktop.org/show_bug.cgi?id=69675 From what I understand, it means that I can hear sound with the resolution I am using with rate 44100Hz could be considered some sort of luck. Therefore maybe you can try different rate with different resolution and refresh rate to see if your problem is of the same nature. Or you can try with a newer kernel, the fixes are applied in 3.12-rc5. Yet I might not be right about anything. I am having no luck with the new kernel myself (since it seems to bring other problems).
I don't think this bug is a duplicate. It occurred with 3.8.0-29 (http://packages.ubuntu.com/raring/any/linux-image-3.8.0-29-generic) in Ubuntu 13.04. Also, I don't see two sets of modes, and I'm using 1280x720.
Maybe you are right. But you don't have to see two sets of mode to have this issue. It seems to be occur because of some slight variation between different monitor models. And I don't think this problem is a new one. Possibly ever since the RE HDMI Audio is in the driver. At least I first notice it in Feb with Arch Linux when I have my first HDMI monitor (a TV actually).
(In reply to comment #0) > Created attachment 88136 [details] > dmesg on 3.11.6 > > HDMI audio was working at some point in the past. Some upgrades or changes I > did while on Ubuntu 13.04 caused it to stop working, so I tried to upgrade > to 13.10. I also tried upgrading to a newer 3.11 generic kernel (which > didn't help). Can you indentify when it was last working and use git to bisect to indentify what commit broke it?
It stopped working when I restarted X after a system upgrade, but _before_ a reboot. I was on Ubuntu's 3.8.0-29, and had installed 3.8.0-31. Thinking that something was funky with the loaded modules, I did a reboot but to no avail. This doesn't seem like the symptom of a nice neat kernel bug. I can try to build a version of 3.8.0-29 for Ubuntu 13.10, but I'm dubious.
Eric Swanson, Ubuntu 13.10 reached EOL on July 17, 2014. For more on this, please see https://wiki.ubuntu.com/Releases. If this is reproducible with a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.
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.