ALSA not detect HDMI audio output of nVidia GT240M (GT216)

[RussianNeuroMancer]

Binary package hint: xserver-xorg-video-nouveau

I have a Lenovo Y550-4CWI laptop with nVidia GT240 and HDMI port. nouveau not detect HDMI audio output.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Fri Apr 9 21:29:42 2010
DkmsStatus: Error: [Errno 2] Нет такого файла или каталога
InstallationMedia: Error: [Errno 13] Отказано в доступе: '/var/log/installer/media-info'
MachineType: LENOVO 20017
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic root=UUID=3312396f-d048-4888-ad00-71ab21db6e27 ro quiet splash
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-nouveau
dmi.bios.date: 10/11/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 15CN32WW(V2.05)
dmi.board.name: KIWB1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr15CN32WW(V2.05):bd10/11/2009:svnLENOVO:pn20017:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 20017
dmi.product.version: Lenovo IdeaPad Y550
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: lucid
 architecture: x86_64
 kernel: 2.6.32-19-generic

[RussianNeuroMancer (russianneuromancer)]

In 2.6.34rc5 already fixed.

[Chris Halse Rogers (raof)]

Updated description, moved to the appropriate package.

[Jeremy Foshee (jeremyfoshee)]

RussianNeuroMancer,
     Are you able to confirm for me that this is fixed in Maverick?

Declining the Maverick specific nomination for now and leaving this open against the actively developed Ubuntu kernel (which happens to be Maverick at this time). Will re-open the nomination should a fix be narrowed down which we can confirm specifically resolves this issue in Maverick.

~JFo

[RussianNeuroMancer (russianneuromancer)]

In Maverick this bug is fixed.