I have HDMI working perfectly for video but no sound occurs. I installed pavucontrol and started a DVD in VLC and opened pavucontrol and set it to use the HDMI audio. The blue bar underneath shopws the sound is working and received (the blue bar moves quickly back and forth) but no sound comes out the speakers. I also tried booting with “radeon.audio=1” but again, no sound. I’m wondering if the catalyst proprietary drivers could solve the issue. I am afraid it could screw up the video though, so is there a way to install those drivers but then be able to uninstall them and go back to the default generic ones if there’s an issue?
My setup:
CPU: AMD A4-3400 APU with Radeon™ HD Graphics, 2,700.00 MHz
RAM: 3.6 GiB
Kernel: Linux 3.1.0-1.2-desktop x86_64
OS: openSUSE 12.1 (x86_64)
Desktop: KDE 4.7.2 (4.7.2) “release 5”
GPU: Integrated AMD Radeon HD 6410D
2D driver: fbdev
3D driver: swrast (No 3D Acceleration) (7.11)
2D driver = fbdev ? That suggests (if correct, and it may not be as I have discovered it not a reliable indication) that your PC is not even using the ‘radeon’ graphic driver. Clearly the fbdev graphic driver does NOT support HDMI.
So while the radeon.audio=1 boot code is ESSENTIAL for the radeon graphic driver (because the HDMI audio module is disabled by default in kernel >=3.0 for the radeon driver) , 1st you need to be using the radeon graphic driver.
Please do the following to provide us more information.
(1) As a regular user with a text editor (say kwrite) open the file /var/log/Xorg.0.log and copy its contents and paste its contents to the site SUSE Paste, and press ‘create’ and post here the website URL it gives. That will allow us to inspect your graphic configuration.
(2) Second, as a regular user run the following diagnostic audio script with your PC connected to the Internet:
/usr/sbin/alsa-info.sh
and select the UPLOAD/SHARE option and then complete the script. When the script has finished running it will provide you a website URL where the script output with your PC audio configuration is located. Please post that website URL here. Its possible the settings we get from this will be no good if indeed your PC is not running the ‘radeon’ graphic driver.
Your /var/log/Xorg.0.log output confrims what oldcpu suspected - the fbdev driver is being loaded, and the radeonhd/radeon drivers are not used. This needs to be solved first.
32.496] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
32.496] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
32.497] (**) FBDEV(0): claimed PCI slot 0@0:1:0
32.497] (II) FBDEV(0): using default device
32.497] (WW) Falling back to old probe method for vesa
32.497] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
32.497] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
32.497] (==) FBDEV(0): RGB weight 888
32.497] (==) FBDEV(0): Default visual is TrueColor
32.497] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
32.497] (II) FBDEV(0): hardware: radeondrmfb (video memory: 8100kB)
32.497] (II) FBDEV(0): checking modes against framebuffer device...
32.497] (II) FBDEV(0): checking modes against monitor...
32.497] (--) FBDEV(0): Virtual size is 1920x1080 (pitch 1920)
32.497] (**) FBDEV(0): Built-in mode "current"
32.497] (==) FBDEV(0): DPI set to (96, 96)
32.497] (II) Loading sub module "fb"
32.497] (II) LoadModule: "fb"
32.498] (II) Loading /usr/lib64/xorg/modules/libfb.so
32.506] (II) Module fb: vendor="X.Org Foundation"
32.506] compiled for 1.10.4, module version = 1.0.0
32.506] ABI class: X.Org ANSI C Emulation, version 0.4
32.506] (**) FBDEV(0): using shadow framebuffer
32.507] (II) Loading sub module "shadow"
32.507] (II) LoadModule: "shadow"
32.507] (II) Loading /usr/lib64/xorg/modules/libshadow.so
32.508] (II) Module shadow: vendor="X.Org Foundation"
32.508] compiled for 1.10.4, module version = 1.1.0
32.508] ABI class: X.Org ANSI C Emulation, version 0.4
32.508] (II) UnloadModule: "radeonhd"
32.508] (II) Unloading radeonhd
32.508] (II) UnloadModule: "radeon"
32.508] (II) Unloading radeon
32.508] (II) UnloadModule: "vesa"
32.508] (II) Unloading vesa
32.508] (==) Depth 24 pixmap format is 32 bpp
According to the AMD fusion wiki the Radeon HD 6410D (codename WinterPark, Sumo2) was released in Jun 20, 2011.
Given both the radeon open source driver release cycle and the openSUSE-12.1 release cycle, that is too soon to see support for that driver in the open source radeon driver implementation in openSUSE-12.1 IMHO.
IMHO your only options are:
fbdev driver which you are using now, which has VERY slow performance but is highly compatible (but no HDMI audio)
vesa driver which should be faster than the FBDEV, but still relatively slow (but no HDMI audio)
fglrx (proprietary AMD Catalyst) driver which will provide good performance and HDMI audio
That Catalyst driver should solve this (providing HDMI audio) … although my experience is the 11.12 Catalyst driver is a bit buggy for 12.1. AMD release a new Catalyst driver version every month, and I’m hoping their 'late January" (or possibly instead in ‘early February’ ) release of this driver will be better.
Yes it is possible to roll back after installing this Catalyst driver. I recommend you learn how to roll back BEFORE installing. And since there are a few ways to install the driver, you need to know how to roll back for the way in which you plan to install the driver. I only use the manual method (also called the 'hardway (which is not hard) ’ to install the driver so I can’t help much wrt the other ways.
My recommendation is you (1) start a NEW THREAD asking for help in the installation of the proprietary driver. (2) Then AFTER you have that sorted, come back to this thread for help with the HDMI Audio.
I have machines with kernel-desktop-3.1.6 and kernel-desktop-3.1.4 from …/repositories/Kernel:/stable/standard/
They both have:
SUPPORTED HARDWARE
...
RV710/RV730 Radeon HD 4330/4350/4550/4650/4670/5145/5165/530v/545v/560v/565v
...
SUMO/SUMO2 Radeon HD 6370/6380/6410/6480/6520/6530/6550/6620
in man radeon.
My laptop has an integrated HD4330 using the radeon driver. Unfortunately I do not have anything with an HDMI input here to test whether it works.
6tr6tr’s openSUSE-12.1 has the Kernel: Linux 3.1.0-1.2-desktop x86_64 kernel. So it appears between the Kernel: Linux 3.1.0-1.2 kernel and the 3.1.4 kernel, there will be support added for the radeon open source driver.
For those who are not comfortable in updating the kernel from a 3rd party repository, given its a change from 3.1.0 to 3.1.4 that provides the additional radeon driver support, then IMHO there is hope that we will see that update sometime in the openSUSE-12.1 update repository.
http://download.opensuse.org/update/12.1/
… my experience is an openSUSE kernel update from y.y.x to y.y.x+z is fairly common.
Some of us do consider it as that, as it is not an officially pushed kernel for 12.1 by the packagers for openSUSE-12.1 (intended for regular users). I guess it depends on one’s definition of ‘3rd party’.
Hmmm …
I can’t find in the kernel change log any reference, thou, to this increase in radeon driver support to support the output of ‘man radeon’ that you noted. I do note:
Is it possible you also updated the package xorg-x11-driver-video from version 7.6-80.1.2 to some newer version and it was NOT the kernel update providing the addition open source radeon driver support ?
This is more a mute point, than anything else (helping teach me how to follow change history). … I’m struggling a bit to understand where open source radeon driver support for the AMD 6410D was implemented (as its not in the default openSUSE 12.1.).
I note from checking the change log for the xorg-x11-driver-video version in openSUSE-12.1, that the version of xf86-video-ati is 6.14.2 (last updated 4-Oct-11).
I also note in factory an update to that xorg-x11-driver-video which I downloaded (and did NOT install) and checked the change log:
rpm -qip xorg-x11-driver-video-7.6-258.3.x86_64.rpm --changelog | less
...
* **Thu Nov 03 2011** sndirsch@suse.com
**- xf86-video-ati 6.14.3**
* **Support for more cards**, in particular Llano APUs.
* KMS page flipping fixes.
* vdpau/XvMC support (currently only available for >= R3xx via
Gallium3D).
* Tiling fixes, enable it on more cards by default.
… so its vague, but it could be where the update to the radeon driver for 6410D is located (if not the kernel ? )
When I look at the change log for xf86-video-ati 6.14.3 I struggle … the radeon site has the 6.14.2 as the latest stable version: X.Org Wiki - radeon … But I also note the 6.14.3 when I dig further: xorg/driver/xf86-video-ati - ATI video driver … but I did not see the change history. But when I download xf86-video-ati-6.14.3.tar.gz and not install it, but rather look inside the man file that comes with it, and I see the 6410D is supported.
That suggests to me that it is not just the kernel update that brought the 6410D driver functionality, but rather it was the the 6.14.3 radeon driver update, which may or may not also require the kernel update. …
. < and I don’t know wrt whether this updated xf86-video-ati-6.14.3 needs an updated kernel … but it might … >
When I look at the change log for xf86-video-ati 6.14.3 I struggle … the radeon site has the 6.14.2 as the latest stable version: X.Org Wiki - radeon … But I also note the 6.14.3 when I dig further: xorg/driver/xf86-video-ati - ATI video driver … but I did not see the change history. But when I download xf86-video-ati-6.14.3.tar.gz and not install it, but rather look inside the man file that comes with it, and I see the 6410D is supported.
That suggests to me that it is not just the kernel update that brought the 6410D driver functionality, but rather it was the the 6.14.3 radeon driver update, which may or may not also require the kernel update. …
Excellent catch!
I just updated the kernel on a client’s machine and 3.1.6 does NOT support SUMO/SUMO2.
My laptop has xorg-x11-driver-video-7.6.99.git20111206.1722-1.1.x86_64 which appears to provide SUMO/SUMO2 support.
That xorg-x11-driver-video I would class as third party. It came from: http://download.opensuse.org/repositories/home:/jobermayr/openSUSE_11.4/
Now that you have the proriatary amd graphic driver installed have you tested your HDMI audio?
If HDMI audio still does not work then please run again diagnostic alsa-info.sh script and post here website URL it provides. It should give different information with the fglrx driver installed.