[Alsa-user] Force-enabling a video mode breaks HDMI audio on Intel DG45FC

2010-05-30 Thread David Härdeman
Hi Wu, I'm back to breaking stuff again :)

First of all, the good news, HDMI (and SPDIF) audio works really well 
with 2.6.34...none of the previous problems with silence etc, seem to 
remain and the driver now seems to automagically map the channels to 
what ALSA userspace expects.

However, I've found a new issue.

My receiver likes to report a hardcoded list of supported video modes 
(1080i being the main one) via EDID which are not really useful. So I 
usually don't see the boot messages (X.org has 1080p hardcoded so once 
it starts I get a reasonable mode).

I recently tried played with the video= kernel parameter, and booting 
with:
video=HDMI Type A-1:1920x1...@60d

gives me a proper video mode from the beginning. However, it also seems 
to break HDMI audio. Booting with that parameter - no audio, receiver 
doesn't light up, etc. Booting without that parameter - audio works as 
expected.

Any ideas?

-- 
David Härdeman

--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] ftp.alsa-project.org down?

2010-05-30 Thread Jaroslav Kysela
On Sat, 29 May 2010, James Shatto wrote:

 My debian distro comes with a 2.6.26-2-686 kernel.  Which has version
 1.0.17 of alsa.  I was hoping to just install the 1.0.23 version from
 alsa-project.org.  But the links to download the sources don't appear
 to work.  Is the ftp site down?  Is there some other way to get these
 sources without extracting them from another more recent kernel?

 wget -c ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2

 --2010-05-29 16:09:25--
 ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
   = `alsa-driver-1.0.23.tar.bz2'
 Resolving ftp.alsa-project.org... 212.20.107.51
 Connecting to ftp.alsa-project.org|212.20.107.51|:21... connected.
 Logging in as anonymous ...
 Error in server response, closing control connection.
 Retrying.

The command works for me. It seems like a local issue in your network 
(perhaps a broken NAT gateway)?

Jaroslav

-
Jaroslav Kysela pe...@perex.cz
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.


--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


[Alsa-user] Problem(?) when reloading modules.

2010-05-30 Thread VDR User
Whenever I reload my audio driver, I get the following:

FATAL: Error running install command for snd_seq
WARNING: Error running install command for snd

I'm reloading by unloading all the associated modules and `sudo
modprobe snd_hda_intel`.  What do these lines mean and how do I fix
it?  I don't see them on a fresh boot, only when reloading the driver.

Many thanks.

For reference, here's my /etc/modprobe.d/alsa-base.conf

# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd  { /sbin/modprobe
--quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi  {
/sbin/modprobe --quiet snd-seq-midi ; : ; }
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1  {
/sbin/modprobe --quiet snd-emu10k1-synth ; : ; }

# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2

options snd-hda-intel enable_msi=0 probe_mask=0x,0xfff2

--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] Problem(?) when reloading modules.

2010-05-30 Thread Paul Menzel
Am Sonntag, den 30.05.2010, 12:49 -0700 schrieb VDR User:
 Whenever I reload my audio driver, I get the following:
 
 FATAL: Error running install command for snd_seq
 WARNING: Error running install command for snd
 
 I'm reloading by unloading all the associated modules

How? `sudo modprobe -r snd_hda_intel`?

 and `sudo
 modprobe snd_hda_intel`.  What do these lines mean and how do I fix
 it?  I don't see them on a fresh boot, only when reloading the driver.

Do you only see those messages or do you also experience some
disfunctionalities?

Did you find something on the Web?

Maybe you could pass `--verbose` to `modprobe`? (See `man modprobe`.)

 Many thanks.
 
 For reference, here's my /etc/modprobe.d/alsa-base.conf

[…]

What distribution do you use. I guess you should check with them and
report back here.


Thanks,

Paul


signature.asc
Description: This is a digitally signed message part
--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] Problem(?) when reloading modules.

2010-05-30 Thread VDR User
On Sun, May 30, 2010 at 1:08 PM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
 Am Sonntag, den 30.05.2010, 12:49 -0700 schrieb VDR User:
 Whenever I reload my audio driver, I get the following:

 FATAL: Error running install command for snd_seq
 WARNING: Error running install command for snd

 I'm reloading by unloading all the associated modules

 How? `sudo modprobe -r snd_hda_intel`?

Using rmmod to unload them.

 and `sudo
 modprobe snd_hda_intel`.  What do these lines mean and how do I fix
 it?  I don't see them on a fresh boot, only when reloading the driver.

 Do you only see those messages or do you also experience some
 disfunctionalities?

I haven't noticed any actual problems so I'll say only see them so far.

 Did you find something on the Web?

I did try google'ing first but didn't find anything useful.

 Maybe you could pass `--verbose` to `modprobe`? (See `man modprobe`.)

 Many thanks.

 For reference, here's my /etc/modprobe.d/alsa-base.conf

 […]

 What distribution do you use. I guess you should check with them and
 report back here.

I'm using Debian.  Somebody suggested to just comment out the
following line from /etc/modprobe.d/alsa-base.conf:

install snd /sbin/modprobe --ignore-install snd  { /sbin/modprobe
--quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; }

I did that and now the messages are gone.  Rebooted the box to make
sure it still works from there and yup, still working.  I don't know
if there's anything bad about removing that however.

--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] Force-enabling a video mode breaks HDMI audio on Intel DG45FC

2010-05-30 Thread Wu Fengguang
Add CC to Zhenyu.

Thanks,
Fengguang

On Sun, May 30, 2010 at 07:49:13PM +0800, David Härdeman wrote:
 Hi Wu, I'm back to breaking stuff again :)
 
 First of all, the good news, HDMI (and SPDIF) audio works really well 
 with 2.6.34...none of the previous problems with silence etc, seem to 
 remain and the driver now seems to automagically map the channels to 
 what ALSA userspace expects.
 
 However, I've found a new issue.
 
 My receiver likes to report a hardcoded list of supported video modes 
 (1080i being the main one) via EDID which are not really useful. So I 
 usually don't see the boot messages (X.org has 1080p hardcoded so once 
 it starts I get a reasonable mode).
 
 I recently tried played with the video= kernel parameter, and booting 
 with:
 video=HDMI Type A-1:1920x1...@60d
 
 gives me a proper video mode from the beginning. However, it also seems 
 to break HDMI audio. Booting with that parameter - no audio, receiver 
 doesn't light up, etc. Booting without that parameter - audio works as 
 expected.
 
 Any ideas?
 
 -- 
 David Härdeman

--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user


Re: [Alsa-user] ftp.alsa-project.org down?

2010-05-30 Thread James Shatto
It doesn't appear to be NAT.  At least not anything that I have
control over.  Same error(s) on the router box with or without
firewall.  FTP to my other ISP's base web space works fine.

$ curl ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
curl: (56) FTP response reading failed

$ wget ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
Error in server response, closing control connection.

$ ftp
open ftp.alsa-project.org
421 Service not available, remote server has closed connection

and so on and so on.

traceroute to alsa0.alsa-project.org (212.20.107.51), 30 hops max, 40
byte packets
 1  192.168.2.1 (192.168.2.1)  1.566 ms  1.975 ms  2.980 ms
...
 5  user45.embarqnow.net (64.45.249.45)  21.211 ms  22.044 ms  22.377 ms
 6  ge-6-14.car2.Houston1.Level3.net (4.78.10.17)  30.828 ms  18.662
ms  17.253 ms
 7  ae-2-5.bar2.Houston1.Level3.net (4.69.132.238)  19.686 ms  24.716
ms  25.090 ms
 8  ae-7-7.ebr1.Atlanta2.Level3.net (4.69.137.142)  49.183 ms  49.600
ms  48.246 ms
 9  ae-63-60.ebr3.Atlanta2.Level3.net (4.69.138.4)  47.535 ms  47.883
ms  47.829 ms
10  ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86)  57.109 ms
55.129 ms  57.400 ms
11  ae-61-61.csw1.Washington1.Level3.net (4.69.134.130)  54.671 ms
ae-91-91.csw4.Washington1.Level3.net (4.69.134.142)  45.316 ms  44.817
ms
12  ae-82-82.ebr2.Washington1.Level3.net (4.69.134.153)  50.233 ms
49.554 ms ae-72-72.ebr2.Washington1.Level3.net (4.69.134.149)  50.113
ms
13  ae-44-44.ebr2.Frankfurt1.Level3.net (4.69.137.61)  139.208 ms
ae-43-43.ebr2.Frankfurt1.Level3.net (4.69.137.57)  134.281 ms
ae-44-44.ebr2.Frankfurt1.Level3.net (4.69.137.61)  166.472 ms
14  ae-5-5.car2.Prague1.Level3.net (4.69.135.50)  179.133 ms  179.015
ms  179.089 ms
15  ae-11-11.car1.Prague1.Level3.net (4.69.135.41)  175.002 ms
175.047 ms  175.025 ms
16  212.162.8.14 (212.162.8.14)  156.870 ms  181.953 ms  182.332 ms
17  perexsoft.customer.vol.cz (212.20.107.218)  164.298 ms  184.698 ms
 159.328 ms
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

- James


On 5/30/10, Jaroslav Kysela pe...@perex.cz wrote:
 On Sat, 29 May 2010, James Shatto wrote:

 My debian distro comes with a 2.6.26-2-686 kernel.  Which has version
 1.0.17 of alsa.  I was hoping to just install the 1.0.23 version from
 alsa-project.org.  But the links to download the sources don't appear
 to work.  Is the ftp site down?  Is there some other way to get these
 sources without extracting them from another more recent kernel?

 wget -c ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2

 --2010-05-29 16:09:25--
 ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.23.tar.bz2
   = `alsa-driver-1.0.23.tar.bz2'
 Resolving ftp.alsa-project.org... 212.20.107.51
 Connecting to ftp.alsa-project.org|212.20.107.51|:21... connected.
 Logging in as anonymous ...
 Error in server response, closing control connection.
 Retrying.

 The command works for me. It seems like a local issue in your network
 (perhaps a broken NAT gateway)?

   Jaroslav

 -
 Jaroslav Kysela pe...@perex.cz
 Linux Kernel Sound Maintainer
 ALSA Project, Red Hat, Inc.



--

___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user