[alsa-devel] HP pavilion dv5 1110ew - no hdmi sound
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
- Pozdrawiam / Regards bartek
GG:541634; ICQ:33920811;
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
On Wed, Feb 11, 2009 at 8:48 AM, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Takashi, does ALSA even support standalone NV graphics HDMI? I thought only MCPs were supported so far.
At Wed, 11 Feb 2009 09:56:45 +0100, Vedran Miletić wrote:
On Wed, Feb 11, 2009 at 8:48 AM, Takashi Iwai tiwai@suse.de wrote:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Takashi, does ALSA even support standalone NV graphics HDMI? I thought only MCPs were supported so far.
What are difference between them? Just my ignorance.
BTW, interestingly, I've seen HP dv5 alsa-info with the very same PCI SSID (thus supposedly the same model) which has MCP78 HDMI codec chip.
Takashi
On Wed, Feb 11, 2009 at 10:11 AM, Takashi Iwai tiwai@suse.de wrote:
What are difference between them? Just my ignorance.
BTW, interestingly, I've seen HP dv5 alsa-info with the very same PCI SSID (thus supposedly the same model) which has MCP78 HDMI codec chip.
Takashi
MCPxx = single-chip northbridge + southbridge, with or without integrated graphics Gxx = graphics processor
Now, I might be ignorant here, but wouldn't it be realistic to expect them to function at least a bit different? MCPs have integrated audio controller that certainly isn't the same as one used in Gs.
But, well... it might just work. Maybe NVIDIA wanted to make life easier for developers and used the same logic everywhere.
Doesn't ATI have different HDMI for integrated and discrete?
At Wed, 11 Feb 2009 12:20:57 +0100, Vedran Miletić wrote:
On Wed, Feb 11, 2009 at 10:11 AM, Takashi Iwai tiwai@suse.de wrote:
What are difference between them? Just my ignorance.
BTW, interestingly, I've seen HP dv5 alsa-info with the very same PCI SSID (thus supposedly the same model) which has MCP78 HDMI codec chip.
Takashi
MCPxx = single-chip northbridge + southbridge, with or without integrated graphics Gxx = graphics processor
Ah, I see your point now.
Now, I might be ignorant here, but wouldn't it be realistic to expect them to function at least a bit different? MCPs have integrated audio controller that certainly isn't the same as one used in Gs.
Not that much, at least, from the sound-driver perspective. Both provide the own HDMI (transmitter) codec. The sound driver just needs to set up it. Of course, there must be a big difference in the graphic hardware implementation. But it's all about the graphic driver and the sound driver can't do anything.
Note that some devices (mostly some old machines before Nvidia MCP HDMI came out) have special setups. They hook the SPDIF pin of another codec into the graphic side.
But, well... it might just work. Maybe NVIDIA wanted to make life easier for developers and used the same logic everywhere.
Doesn't ATI have different HDMI for integrated and discrete?
The situation is basically same for ATI, Intel and others.
Takashi
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
Still no succes.
aplay -l : **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 0/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
No sound trough HDMI.
Maybe i should add hdmi device manually? - Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
On Wed, Feb 11, 2009 at 8:23 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
Still no succes.
aplay -l : **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 0/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
No sound trough HDMI.
Maybe i should add hdmi device manually?
Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can you provide relevant parts (sound and graphics devices) of "lspci -vnn"?
Dnia 2009-02-11, śro o godzinie 20:35 +0100, Vedran Miletić pisze:
On Wed, Feb 11, 2009 at 8:23 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
Still no succes.
aplay -l : **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 0/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
No sound trough HDMI.
Maybe i should add hdmi device manually?
Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can you provide relevant parts (sound and graphics devices) of "lspci -vnn"?
lspci -vnn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0 Capabilities: <access denied> Kernel modules: intel-agp
00:01.0 PCI bridge [0604]: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port [8086:2a41] (rev 07) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00009000-00009fff Memory behind bridge: 90000000-92ffffff Prefetchable memory behind bridge: 0000000080000000-000000008fffffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at a0e0 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 21 I/O ports at a0c0 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) (prog-if 20) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 19 Memory at 9f305c00 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 214 Memory at 9f300000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 00008000-00008fff Memory behind bridge: 9e200000-9f2fffff Prefetchable memory behind bridge: 0000000093000000-0000000093ffffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: 00006000-00007fff Memory behind bridge: 9d200000-9e1fffff Prefetchable memory behind bridge: 0000000094000000-00000000950fffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: 00005000-00005fff Memory behind bridge: 9c200000-9d1fffff Prefetchable memory behind bridge: 0000000095100000-00000000960fffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 I/O behind bridge: 00004000-00004fff Memory behind bridge: 9b200000-9c1fffff Prefetchable memory behind bridge: 0000000096100000-00000000970fffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 I/O behind bridge: 00003000-00003fff Memory behind bridge: 9a100000-9b1fffff Prefetchable memory behind bridge: 0000000097100000-00000000980fffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 [8086:294a] (rev 03) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=07, subordinate=09, sec-latency=0 I/O behind bridge: 00002000-00002fff Memory behind bridge: 99100000-9a0fffff Prefetchable memory behind bridge: 0000000098100000-00000000990fffff Capabilities: <access denied> Kernel driver in use: pcieport-driver Kernel modules: shpchp
00:1d.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 20 I/O ports at a0a0 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1d.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 19 I/O ports at a080 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1d.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 16 I/O ports at a060 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1d.3 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 18 I/O ports at a040 [size=32] Capabilities: <access denied> Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd
00:1d.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03) (prog-if 20) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0, IRQ 20 Memory at 9f305800 (32-bit, non-prefetchable) [size=1K] Capabilities: <access denied> Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 93) (prog-if 01) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=32 Capabilities: <access denied>
00:1f.0 ISA bridge [0601]: Intel Corporation ICH9M LPC Interface Controller [8086:2919] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, medium devsel, latency 0 Capabilities: <access denied>
00:1f.2 SATA controller [0106]: Intel Corporation ICH9M/M-E SATA AHCI Controller [8086:2929] (rev 03) (prog-if 01) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 215 I/O ports at a108 [size=8] I/O ports at a114 [size=4] I/O ports at a100 [size=8] I/O ports at a110 [size=4] I/O ports at a020 [size=32] Memory at 9f305000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: medium devsel, IRQ 11 Memory at 9f306000 (64-bit, non-prefetchable) [size=256] I/O ports at a000 [size=32] Kernel modules: i2c-i801
00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev 03) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: fast devsel, IRQ 11 Memory at 9f304000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied>
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 9200M GS [10de:06e8] (rev a1) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 92000000 (32-bit, non-prefetchable) [size=16M] Memory at 80000000 (64-bit, prefetchable) [size=256M] Memory at 90000000 (64-bit, non-prefetchable) [size=32M] I/O ports at 9000 [size=128] Capabilities: <access denied> Kernel driver in use: nvidia Kernel modules: nvidia, nvidiafb
02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) Subsystem: Hewlett-Packard Company Device [103c:137d] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 9e200000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: wl Kernel modules: wl
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 216 I/O ports at 6000 [size=256] Memory at 94010000 (64-bit, prefetchable) [size=4K] Memory at 94000000 (64-bit, prefetchable) [size=64K] Expansion ROM at 94020000 [disabled] [size=64K] Capabilities: <access denied> Kernel driver in use: r8169 Kernel modules: r8169
06:00.0 FireWire (IEEE 1394) [0c00]: JMicron Technologies, Inc. IEEE 1394 Host Controller [197b:2380] (prog-if 10) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 9a100000 (32-bit, non-prefetchable) [size=2K] Memory at 9a100d00 (32-bit, non-prefetchable) [size=128] Memory at 9a100c80 (32-bit, non-prefetchable) [size=128] Memory at 9a100c00 (32-bit, non-prefetchable) [size=128] Capabilities: <access denied> Kernel driver in use: ohci1394 Kernel modules: ohci1394
06:00.1 System peripheral [0880]: JMicron Technologies, Inc. SD/MMC Host Controller [197b:2382] Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 9a100b00 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied> Kernel driver in use: sdhci-pci Kernel modules: sdhci-pci
06:00.2 SD Host controller [0805]: JMicron Technologies, Inc. Standard SD Host Controller [197b:2381] (prog-if 01) Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: fast devsel, IRQ 16 Memory at 9a100a00 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied> Kernel modules: sdhci-pci
06:00.3 System peripheral [0880]: JMicron Technologies, Inc. MS Host Controller [197b:2383] Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at 9a100900 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied>
06:00.4 System peripheral [0880]: JMicron Technologies, Inc. xD Host Controller [197b:2384] Subsystem: Hewlett-Packard Company Device [103c:3603] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at 9a100800 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied>
Dnia 2009-02-11, śro o godzinie 21:32 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 20:23:35 +0100, Bartłomiej Holdenmayer wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
What the hack this script does?
Takashi
Description in full is here: http://ubuntuforums.org/showthread.php?p=6589810
The main idea of upgrading ALSA with attached script, is the timeshift of updates through official channels in the range of up to half a year.
This is IMO not acceptable.
There is a great chance that you get your soundcard up and running or problems resolved much earlier, if you use the very lastest ALSA version. The script will get you the latest official stable ALSA release and - if available - the latest release candidate for an upcoming release.
At Thu, 12 Feb 2009 00:41:22 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 21:32 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 20:23:35 +0100, Bartłomiej Holdenmayer wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
What the hack this script does?
Takashi
Description in full is here: http://ubuntuforums.org/showthread.php?p=6589810
The main idea of upgrading ALSA with attached script, is the timeshift of updates through official channels in the range of up to half a year.
This is IMO not acceptable.
There is a great chance that you get your soundcard up and running or problems resolved much earlier, if you use the very lastest ALSA version. The script will get you the latest official stable ALSA release and - if available - the latest release candidate for an upcoming release.
The released or rc tarballs are way too old for debugging. Use the snapshot tarball in the URL below (not from alsa-oroject.org). ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
On Thu, Feb 12, 2009 at 12:54 AM, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Feb 2009 00:41:22 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 21:32 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 20:23:35 +0100, Bartłomiej Holdenmayer wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
What the hack this script does?
Takashi
Description in full is here: http://ubuntuforums.org/showthread.php?p=6589810
The main idea of upgrading ALSA with attached script, is the timeshift of updates through official channels in the range of up to half a year.
This is IMO not acceptable.
There is a great chance that you get your soundcard up and running or problems resolved much earlier, if you use the very lastest ALSA version. The script will get you the latest official stable ALSA release and - if available - the latest release candidate for an upcoming release.
The released or rc tarballs are way too old for debugging. Use the snapshot tarball in the URL below (not from alsa-oroject.org). ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I don' think this will be enough. If you look at lspci, there is not a single mention of HDMI device. I believe (well, at least MCP78S has it that way) that HDMI device should be listed. If it isn't listed for discrete graphics, then there is some other way that it must be implemented.
I believe that ATI also lists separate device for HDMI audio.
To be precise, my 8200 board has this: http://pci-ids.ucw.cz/read/PC/10de/0774, and there is a BIOS option to enable and disable it.
If there isn't a way to get HDMI audio device listed in lspci (BIOS option or whatever), I don't believe upgrading ALSA will do much here.
At Thu, 12 Feb 2009 17:19:14 +0100, Vedran Miletić wrote:
On Thu, Feb 12, 2009 at 12:54 AM, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Feb 2009 00:41:22 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 21:32 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 20:23:35 +0100, Bartłomiej Holdenmayer wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
What the hack this script does?
Takashi
Description in full is here: http://ubuntuforums.org/showthread.php?p=6589810
The main idea of upgrading ALSA with attached script, is the timeshift of updates through official channels in the range of up to half a year.
This is IMO not acceptable.
There is a great chance that you get your soundcard up and running or problems resolved much earlier, if you use the very lastest ALSA version. The script will get you the latest official stable ALSA release and - if available - the latest release candidate for an upcoming release.
The released or rc tarballs are way too old for debugging. Use the snapshot tarball in the URL below (not from alsa-oroject.org). ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I don' think this will be enough. If you look at lspci, there is not a single mention of HDMI device. I believe (well, at least MCP78S has it that way) that HDMI device should be listed.
No, the HDMI part doesn't always appear as an individual PCI device. It can be simply on hooked onto the audio controller together with IDT codec.
Indeed, the HP dv5 model with the same PCI SSID shows that pattern.
Takashi
Dnia 2009-02-12, czw o godzinie 17:19 +0100, Vedran Miletić pisze:
On Thu, Feb 12, 2009 at 12:54 AM, Takashi Iwai tiwai@suse.de wrote:
At Thu, 12 Feb 2009 00:41:22 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 21:32 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 20:23:35 +0100, Bartłomiej Holdenmayer wrote:
I did with: sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap
What the hack this script does?
Takashi
Description in full is here: http://ubuntuforums.org/showthread.php?p=6589810
The main idea of upgrading ALSA with attached script, is the timeshift of updates through official channels in the range of up to half a year.
This is IMO not acceptable.
There is a great chance that you get your soundcard up and running or problems resolved much earlier, if you use the very lastest ALSA version. The script will get you the latest official stable ALSA release and - if available - the latest release candidate for an upcoming release.
The released or rc tarballs are way too old for debugging. Use the snapshot tarball in the URL below (not from alsa-oroject.org). ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I don' think this will be enough. If you look at lspci, there is not a single mention of HDMI device. I believe (well, at least MCP78S has it that way) that HDMI device should be listed. If it isn't listed for discrete graphics, then there is some other way that it must be implemented.
I believe that ATI also lists separate device for HDMI audio.
To be precise, my 8200 board has this: http://pci-ids.ucw.cz/read/PC/10de/0774, and there is a BIOS option to enable and disable it.
If there isn't a way to get HDMI audio device listed in lspci (BIOS option or whatever), I don't believe upgrading ALSA will do much here.
I my bios there is no such a option about hdmi. It is simple bios - boot order, passwords and test for hhd, memory.
What else can i do? Is my problem connected with bios, nvidia driver or alsa? I have the most actual bios, alsa from snap and nvidia 180.11 (most actual from repositories; on nvidia webpage there is 180.22)
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
Sorry, i messed up thread. sudo sh ./AlsaUpgrade-1.0.x-rev-1.16.sh -snap this script is taking actual snapshot from link you gave me.
I did upgrade 5 min ago. What else can i do?
Bartek
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
I found interesting discussion, but nothing from there is helping me. http://www.nvnews.net/vbulletin/showthread.php?t=97993&highlight=hdmi&am...
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
I have to repeat again that I've seen a report regrading HP dv5 with the same PCI SSID with HDMI working using the latest alsa driver.
Takashi
I found interesting discussion, but nothing from there is helping me. http://www.nvnews.net/vbulletin/showthread.php?t=97993&highlight=hdmi&am... -- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote:
Welcome, I have no sound through HDMI. I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And newest bios F13A.
I was googling for a week and only solution i found was to upgrade Alsa and Nvidia to the newest version. I did, but i still do not have sound over HDMI. In Win$ it is working ok.
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote: > > Welcome, > I have no sound through HDMI. > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And > newest bios F13A. > > I was googling for a week and only solution i found was to upgrade Alsa > and Nvidia to the newest version. I did, but i still do not have sound > over HDMI. In Win$ it is working ok. > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I am not sure if do everything properly.
1. I did installation of alsa snap with script AlsaUpgrade-1.0.x-rev-1.16.sh;
2. After that, I changed last line in /etc/modprobe.d/alsa-base from: options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
3. After I restarted alsa with /etc/init.d/alsasound stop and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
Yes. but you should try a snapshot instead.
http://ftp.kernel.org/pub/linux/kernel/people/tiwai/alsa/alsa-driver/alsa-dr...
Vedran Miletić
On Sat, Feb 14, 2009 at 3:53 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Dnia 2009-02-14, sob o godzinie 16:15 +0100, Vedran Miletić pisze:
Yes. but you should try a snapshot instead.
http://ftp.kernel.org/pub/linux/kernel/people/tiwai/alsa/alsa-driver/alsa-dr...
Vedran Miletić
On Sat, Feb 14, 2009 at 3:53 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
I did not noticed before there are 2 of them: alsa-driver-snapshot alsa-driver-unstable-snapshot
At Sat, 14 Feb 2009 16:15:59 +0100, Vedran Miletić wrote:
Yes. but you should try a snapshot instead.
http://ftp.kernel.org/pub/linux/kernel/people/tiwai/alsa/alsa-driver/alsa-dr...
For HD-audio, alsa-driver-snapshot tarball should suffice (except for CA0110). The unstable version is for other things.
Takashi
At Sat, 14 Feb 2009 15:53:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
After you load the latest driver with that probe_mask option, check the "kernel messages" (i.e. run dmesg command). It's not about the message from modprobe.
Takashi
Dnia 2009-02-14, sob o godzinie 18:03 +0100, Takashi Iwai pisze:
At Sat, 14 Feb 2009 15:53:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
After you load the latest driver with that probe_mask option, check the "kernel messages" (i.e. run dmesg command). It's not about the message from modprobe.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
How to load the latest driver with that probe_mask option
Dnia 2009-02-14, sob o godzinie 18:03 +0100, Takashi Iwai pisze:
At Sat, 14 Feb 2009 15:53:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 15:28 +0100, Vedran Miletić pisze:
On Sat, Feb 14, 2009 at 3:22 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
I am not sure if do everything properly.
- I did installation of alsa snap with script
AlsaUpgrade-1.0.x-rev-1.16.sh;
- After that, I changed last line in /etc/modprobe.d/alsa-base from:
options snd-hda-intel enable_msi=1
into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff
- After I restarted alsa with /etc/init.d/alsasound stop
and /etc/init.d/alsasound start
and get message: Starting sound driver: snd-hda-intel done
Am I doing that properly? What should I do (what command) to see hda_intel: codec_mask forced to 0xff
-- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Did you try installing snapshot manually? Script could be bad.
Vedran _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I checked script. It is downloading good snapshot.
There are other options in script: ./configure --with-kernel=/usr/src/linux-headers-$KERNEL --with-cards=all --with-card-options=all --with-sequencer=yes --with-oss=yes --prefix=/usr || die "$DRIVER configure failed"
I guess everything is ok. I attach the script.
After you load the latest driver with that probe_mask option, check the "kernel messages" (i.e. run dmesg command). It's not about the message from modprobe.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I changed last line in /etc/modprobe.d/alsa-base from: options snd-hda-intel enable_msi=1 into: options snd-hda-intel enable_msi=1 probe_mask=0x1ff and restarted system.
Is that the way to load the latest driver with that probe_mask option ????
My dmesg |grep hda is returnig null.
And dmesg |grep HDA: [ 16.863426] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 16.863506] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 16.987913] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input11 [ 17.148503] input: HDA Intel at 0x9f300000 irq 214 Mic at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input12 [ 17.148905] input: HDA Intel at 0x9f300000 irq 214 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 17.149268] input: HDA Intel at 0x9f300000 irq 214 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze:
At Wed, 11 Feb 2009 03:20:44 +0100, Bartłomiej Holdenmayer wrote: > > Welcome, > I have no sound through HDMI. > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And > newest bios F13A. > > I was googling for a week and only solution i found was to upgrade Alsa > and Nvidia to the newest version. I did, but i still do not have sound > over HDMI. In Win$ it is working ok. > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
Try the very latest alsa-driver snapshot below: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
What is that device: STAC92xx Digital? -- Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
On Tue, Feb 17, 2009 at 9:43 PM, Bartłomiej Holdenmayer bh@habah.com wrote:
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
What is that device: STAC92xx Digital?
Pozdrawiam / Regards Bartłomiej Holdenmayer
GG:541634; ICQ:33920811; skypename:bartlomiejholdenmayer
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
This *could* be HDMI device, IF it is internally routed that way. Not sure. Can you give it a shot?
Vedran Miletić
At Tue, 17 Feb 2009 21:43:16 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze: > At Wed, 11 Feb 2009 03:20:44 +0100, > Bartłomiej Holdenmayer wrote: > > > > Welcome, > > I have no sound through HDMI. > > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And > > newest bios F13A. > > > > I was googling for a week and only solution i found was to upgrade Alsa > > and Nvidia to the newest version. I did, but i still do not have sound > > over HDMI. In Win$ it is working ok. > > > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863 > > Try the very latest alsa-driver snapshot below: > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > > Takashi
I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
It's true for dedicated HDMI codec chip. But, right now it's mixed for the HDMI routing from the analog codec chip. This should be fixed in future.
What is that device: STAC92xx Digital?
It's either an SPDIF or an HDMI output.
Turn on "IEC958 Playback Switch", and just try to play something from the default device.
Takashi
At Wed, 18 Feb 2009 07:33:42 +0100, I wrote:
At Tue, 17 Feb 2009 21:43:16 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote:
At Fri, 13 Feb 2009 04:37:54 +0100, Bartłomiej Holdenmayer wrote: > > Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze: > > At Wed, 11 Feb 2009 03:20:44 +0100, > > Bartłomiej Holdenmayer wrote: > > > > > > Welcome, > > > I have no sound through HDMI. > > > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And > > > newest bios F13A. > > > > > > I was googling for a week and only solution i found was to upgrade Alsa > > > and Nvidia to the newest version. I did, but i still do not have sound > > > over HDMI. In Win$ it is working ok. > > > > > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863 > > > > Try the very latest alsa-driver snapshot below: > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > > > > > Takashi > > I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. > Still sound does not work over hdmi.
Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
It's true for dedicated HDMI codec chip. But, right now it's mixed for the HDMI routing from the analog codec chip. This should be fixed in future.
What is that device: STAC92xx Digital?
It's either an SPDIF or an HDMI output.
Turn on "IEC958 Playback Switch", and just try to play something from the default device.
... and post the alsa-info output, too.
Takashi
Quoting Takashi Iwai tiwai@suse.de:
At Wed, 18 Feb 2009 07:33:42 +0100, I wrote:
At Tue, 17 Feb 2009 21:43:16 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote: > > At Fri, 13 Feb 2009 04:37:54 +0100, > Bartłomiej Holdenmayer wrote: > > > > Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze: > > > At Wed, 11 Feb 2009 03:20:44 +0100, > > > Bartłomiej Holdenmayer wrote: > > > > > > > > Welcome, > > > > I have no sound through HDMI. > > > > I have Nvidia Geforce 9200M GS with 180.11 driver.
Alsa 1.0.19. And
> > > > newest bios F13A. > > > > > > > > I was googling for a week and only solution i found
was to upgrade Alsa
> > > > and Nvidia to the newest version. I did, but i
still do not have sound
> > > > over HDMI. In Win$ it is working ok. > > > > > > > >
http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863
> > > > > > Try the very latest alsa-driver snapshot below: > > >
ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
> > > > > > > > > Takashi > > > > I have now the newest nvidia 180.29 from 11.02.09. I
have alsa snapshot.
> > Still sound does not work over hdmi. > > Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try
probe_mask=0x1ff
option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
It's true for dedicated HDMI codec chip. But, right now it's mixed for the HDMI routing from the analog codec chip. This should be fixed in future.
What is that device: STAC92xx Digital?
It's either an SPDIF or an HDMI output.
Turn on "IEC958 Playback Switch", and just try to play something from the default device.
... and post the alsa-info output, too.
Takashi
I will try it at evening. I am out of my hp. I have no spdif port, only hdmi. I have 2 two IEC958 switches in alsa mixer (i do not remember exact names). I use gnome-alsa-mixer. Both switches are on.
I was checking before to play through STAC92xx Digital with aplay. Maybe i did something wrong?
Can You tell exact command to test?
Can "System > Preferences > Sound" settings have impact on aplay?
May there be a difference if I boot with HDMI cable in or hotpluged into working system?
Once again: What is responsible for recognition of hardware - alsa-driver or maybe there is hal involved?
Bartek
Dnia 2009-02-18, śro o godzinie 07:59 +0100, Takashi Iwai pisze:
At Wed, 18 Feb 2009 07:33:42 +0100, I wrote:
At Tue, 17 Feb 2009 21:43:16 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-14, sob o godzinie 11:30 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 22:48:26 +0100, Bartłomiej Holdenmayer wrote:
Dnia 2009-02-13, pią o godzinie 09:03 +0100, Takashi Iwai pisze:
At Fri, 13 Feb 2009 07:58:44 +0100, I wrote: > > At Fri, 13 Feb 2009 04:37:54 +0100, > Bartłomiej Holdenmayer wrote: > > > > Dnia 2009-02-11, śro o godzinie 08:48 +0100, Takashi Iwai pisze: > > > At Wed, 11 Feb 2009 03:20:44 +0100, > > > Bartłomiej Holdenmayer wrote: > > > > > > > > Welcome, > > > > I have no sound through HDMI. > > > > I have Nvidia Geforce 9200M GS with 180.11 driver. Alsa 1.0.19. And > > > > newest bios F13A. > > > > > > > > I was googling for a week and only solution i found was to upgrade Alsa > > > > and Nvidia to the newest version. I did, but i still do not have sound > > > > over HDMI. In Win$ it is working ok. > > > > > > > > http://www.alsa-project.org/db/?f=01be9175263a5021fcfef3a47123afc04d62a863 > > > > > > Try the very latest alsa-driver snapshot below: > > > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz > > > > > > > > > Takashi > > > > I have now the newest nvidia 180.29 from 11.02.09. I have alsa snapshot. > > Still sound does not work over hdmi. > > Well, then the last suspect is BIOS.
BTW, the very latest alsa-driver snapshot includes a new feature to force the codec probing. Grab the latest one and try probe_mask=0x1ff option. You'll have to see some new messages hda_intel: codec_mask forced to 0xff
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Can You please tell me what exactly should I do?
Well, just like what I wrote in the above: grab the latest alsa-driver snapshot tarball, build it, install it, and add probe_mask=0x1ff module option to snd-hda-intel, then load it. If you've done it properly, you see the message like above. And let's see whether the driver can detect more codecs.
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
I did ehat You wrote. Here is my dmesg: [ 14.729023] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 2 2 [ 14.729028] hda_intel: codec_mask forced to 0xff [ 14.729054] HDA Intel 0000:00:1b.0: setting latency timer to 64 [ 15.776021] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:634: hda_intel: azx_get_response timeout, switching to polling mode: last cmd=0x100f0000 [ 16.780019] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #1 probe error; disabling it... [ 17.816508] ALSA /usr/src/Alsa-1.0.19/alsa-driver-1.0.19/pci/hda/../../alsa-k ernel/pci/hda/hda_intel.c:1271: hda_intel: Codec #3 probe error; disabling it... [ 17.921600] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/inp ut/input11 [ 18.052194] input: HDA Intel at 0x9f300000 irq 22 Mic at Ext Front Jack as /d evices/pci0000:00/0000:00:1b.0/input/input12 [ 18.052587] input: HDA Intel at 0x9f300000 irq 22 Mic at Sep UNKNOWN Jack as /devices/pci0000:00/0000:00:1b.0/input/input13 [ 18.052894] input: HDA Intel at 0x9f300000 irq 22 HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:1b.0/input/input14
What next should I do?
I have basic questions: Alsa to work good with my HDMI sound have to know what hardware is onboard and what it can do- features (f.ex.HDMI). What is responsible for recognition of hardware? Is that alsa-driver package? How can I force good recognition?
aplay -l list devices it can use. Now for me it is: artek@hplaptop:~$ aplay -l **** Lista PLAYBACK urządzeń **** karta 0: Intel [HDA Intel], urządzenie 0: STAC92xx Analog [STAC92xx Analog] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0 karta 0: Intel [HDA Intel], urządzenie 1: STAC92xx Digital [STAC92xx Digital] Urządzenia podrzędne: 1/1 Urządzenie podrzędne #0: subdevice #0
Up to my knowledge, as soon as Alsa knows about HDMI feature, i will get 3rd device with aplay -l. Am I right about it?
It's true for dedicated HDMI codec chip. But, right now it's mixed for the HDMI routing from the analog codec chip. This should be fixed in future.
What is that device: STAC92xx Digital?
It's either an SPDIF or an HDMI output.
Turn on "IEC958 Playback Switch", and just try to play something from the default device.
... and post the alsa-info output, too.
Takashi
STILL no succes.
Below is result of my tries: _______________________ bartek@hplaptop:~$ aplay -D plug:iec958 -c 2 -v /nature1.wav Odtwarzanie WAVE '/nature1.wav' : Signed 16 bit Little Endian, Częstotliwość 11025 Hz, Mono Plug PCM: Rate conversion PCM (44100, sformat=S16_LE) Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat : STD channels : 1 rate : 11025 exact rate : 11025 (11025/1) msbits : 16 buffer_size : 4096 period_size : 1024 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min : 1024 period_event : 0 start_threshold : 4096 stop_threshold : 4096 silence_threshold: 0 silence_size : 0 boundary : 268435456 Slave: Route conversion PCM (sformat=S16_LE) Transformation table: 0 <- 0 1 <- 0 Its setup is: stream : PLAYBACK access : MMAP_INTERLEAVED format : S16_LE subformat : STD channels : 1 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 16384 period_size : 4096 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min : 4096 period_event : 0 start_threshold : 16384 stop_threshold : 16384 silence_threshold: 0 silence_size : 0 boundary : 1073741824 Slave: Hooks PCM Its setup is: stream : PLAYBACK access : MMAP_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 16384 period_size : 4096 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min : 4096 period_event : 0 start_threshold : 16384 stop_threshold : 16384 silence_threshold: 0 silence_size : 0 boundary : 1073741824 Slave: Hardware PCM card 0 'HDA Intel' device 1 subdevice 0 Its setup is: stream : PLAYBACK access : MMAP_INTERLEAVED format : S16_LE subformat : STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 16384 period_size : 4096 period_time : 92879 tstamp_mode : NONE period_step : 1 avail_min : 4096 period_event : 0 start_threshold : 16384 stop_threshold : 16384 silence_threshold: 0 silence_size : 0 boundary : 1073741824 _______________________ I was playing with iec958 and iec958 default pcm switches. Still no sound.
Here is my alsa-info: http://www.alsa-project.org/db/?f=adacd4038a2139cfb2a41239df1885af1721f294
There is one thing that makes me puzzled. In "Volume control" i can choose which device to control, and i have: HDA Intel (Alsa mixer) Nvidia ID 3 (OSS Mixer) - like gnome knows about 3rd sound device through Nvidia -hdmi.
participants (4)
-
Bartłomiej Holdenmayer -
bh＠habah.com
-
Takashi Iwai -
Vedran Miletić