2.6.26-rc5-git2: snd-emu10k1 does not work
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
Thanks,
Rafael
Signature · 1 line
"Premature optimization is the root of all evil." - Donald Knuth
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 11 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check /proc/asound/cards whether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position. If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
Takashi
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.
This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
Thanks,
Rafael
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from /proc/asound/cards:
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17
1 [UART ]: MPU-401 UART - MPU-401 UART
MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Thanks,
Rafael
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:
Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether /dev/snd/* files exist and have proper permissions and ACL (see "getfacl /dev/snd/*")
- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove /etc/asound-pulse.conf if present.
Takashi
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.
I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Rafael
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 58 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.
Quoted 6 lines
I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking /proc/asound/cards and/or kernel config would save the time of bisect. At least, check the following:
1. you have emu10k1 in the first entry (#0) of /proc/asound/cards
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
3. run "aplay -Dhw:0 /usr/share/sounds/alsa/test.wav" for testing
thanks,
Takashi
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cards
Yes. The contents of /proc/asound/cards are exactly as shown above.
Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testing
As root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission denied
Thanks,
Rafael
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 84 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
Quoted 8 lines
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testingAs root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission denied
Weird. Could you try to remove ~/.asoundrc and /etc/asound*.conf if they exist?
Takashi
Quoted 90 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 88 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testing
Quoted 7 lines
Quoted 4 lines
As root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission deniedWeird. Could you try to remove ~/.asoundrc and
/etc/asound*.confif they exist?
I only had /etc/asound-pulse.conf . Removed that, but it didn't change anything.
Thanks,
Rafael
At Mon, 30 Jun 2008 11:58:47 +0200,
Quoted 94 lines · Rafael J. Wysocki
Quoted 92 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 90 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testingAs root it works just fine. As a normal user I get:
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission deniedWeird. Could you try to remove ~/.asoundrc and
/etc/asound*.confif they exist?I only had
/etc/asound-pulse.conf. Removed that, but it didn't change anything.
Then I have no idea... Could you bisect? At least, I'd like to know whether manually built vanilla 2.6.25.x works on your system...
thanks,
Takashi
Quoted 99 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:58:47 +0200,
Quoted 97 lines · Rafael J. Wysocki
Quoted 95 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 92 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testingAs root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission denied
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Weird. Could you try to remove ~/.asoundrc and
/etc/asound*.confif they exist?I only had
/etc/asound-pulse.conf. Removed that, but it didn't change anything.Then I have no idea... Could you bisect? At least, I'd like to know whether manually built vanilla 2.6.25.x works on your system...
I tried vanilla 2.6.25 and it behaved exactly like the current -git, so this is not a recent regression.
Still, it's interesting why the openSUSE kernels work with the card without any problems while the kernel.org ones apparently don't.
Thanks,
Rafael
Quoted 2 lines · Rafael J. Wysocki
Still, it's interesting why the openSUSE kernels work with the card without any problems while the kernel.org ones apparently don't.
Same config? Particularly, same config for CONFIG_SYSFS_DEPRECATED_V2 and other such small details?
Signature · 4 lines
"One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
Quoted 5 lines · Henrique de Moraes Holschuh
Quoted 2 lines · Rafael J. Wysocki
Still, it's interesting why the openSUSE kernels work with the card without any problems while the kernel.org ones apparently don't.
Same config?
Certainly not.
Quoted 2 lines
Particularly, same config for
CONFIG_SYSFS_DEPRECATED_V2and other such small details?
Well, in fact I'd like to find the small detail that makes the difference. :-)
Thanks,
Rafael
Quoted 6 lines · On Monday 30 June 2008 22:36:45 Rafael J. Wysocki wrote:
I tried vanilla 2.6.25 and it behaved exactly like the current -git, so this is not a recent regression.
Still, it's interesting why the openSUSE kernels work with the card without any problems while the kernel.org ones apparently don't.
I had the same problem with Mandriva, try the following:
la -l /dev/snd/
you should have something like this:
total 0
0 crw-rw---- 1 root audio 116, 0 2008-07-03 08:44 controlC0 0 crw-rw---- 1 root audio 116, 4 2008-07-03 08:44 hwC0D0 0 crw-rw---- 1 root audio 116, 8 2008-07-03 08:44 midiC0D0 0 crw-rw---- 1 root audio 116, 9 2008-07-03 08:44 midiC0D1
0 crw-rw---- 1 root audio 116, 24 2008-07-03 08:45 pcmC0D0c 0 crw-rw---- 1 root audio 116, 16 2008-07-03 08:45 pcmC0D0p 0 crw-rw---- 1 root audio 116, 25 2008-07-03 08:44 pcmC0D1c 0 crw-rw---- 1 root audio 116, 26 2008-07-03 08:44 pcmC0D2c 0 crw-rw---- 1 root audio 116, 18 2008-07-03 08:44 pcmC0D2p 0 crw-rw---- 1 root audio 116, 19 2008-07-03 08:44 pcmC0D3p 0 crw-rw---- 1 root audio 116, 28 2008-07-03 08:44 pcmC0D4c 0 crw-rw---- 1 root audio 116, 20 2008-07-03 08:44 pcmC0D4p 0 crw-rw---- 1 root audio 116, 1 2008-07-03 08:44 seq 0 crw-rw---- 1 root audio 116, 33 2008-07-03 08:44 timer
create the audio group and add you self to it, it required a reboot for the changes to apply, but if you are too lazy to reboot: chmod 666 /dev/snd/* will work ;)
Quoted 99 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:58:47 +0200,
Quoted 97 lines · Rafael J. Wysocki
Quoted 95 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 92 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testingAs root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission denied
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
Weird. Could you try to remove ~/.asoundrc and
/etc/asound*.confif they exist?I only had
/etc/asound-pulse.conf. Removed that, but it didn't change anything.Then I have no idea... Could you bisect? At least, I'd like to know whether manually built vanilla 2.6.25.x works on your system...
I made it work and the trick was to set CONFIG_TMPFS_POSIX_ACL=y.
Thanks to Andrew Clayton for the hint.
Rafael
At Thu, 3 Jul 2008 13:39:59 +0200,
Quoted 104 lines · Rafael J. Wysocki
Quoted 102 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:58:47 +0200,
Quoted 100 lines · Rafael J. Wysocki
Quoted 97 lines · Takashi Iwai
At Mon, 30 Jun 2008 11:44:39 +0200,
Quoted 84 lines · Rafael J. Wysocki
Quoted 65 lines · Takashi Iwai
At Sun, 29 Jun 2008 19:46:49 +0200,
Quoted 63 lines · Rafael J. Wysocki
Quoted 47 lines · Takashi Iwai
At Mon, 9 Jun 2008 22:45:01 +0200,
Quoted 37 lines · Rafael J. Wysocki
Quoted 22 lines · Rafael J. Wysocki
Quoted 11 lines · Takashi Iwai
At Sun, 8 Jun 2008 23:03:58 +0200,
Quoted 9 lines · Rafael J. Wysocki
Hi,
snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads, but the card is not visible, for example, to any mixer apps (including the ALSA mixer). However, YaST correctly detects and reports the card (the system is openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does correctly work on the same hardware.
Quoted 6 lines
Quoted 2 lines
Is there anything I should pay attention to, like any options related to /proc or sysfs that could have an effect on the audio adapter?
First off, check
/proc/asound/cardswhether snd-emu10k1 driver is really loaded on the first slot. I guess something else occupies the position.This is quite possible, as there is an on-board audio in this box too and I'm not sure if the setup switch really turns it off.
Quoted 8 lines
Quoted 6 lines
If yes, a simple solution is to add the following option for snd module:
options snd slots=snd-emu10k1
then the first slot is reserved for emu10k1. Note that this option is available for 2.6.25 or later kernel.
I'll try later today and let you know.
No, it didn't work.
Here's what I got from
/proc/asound/cards:Quoted 7 lines
0 [Audigy ]: Audigy - Audigy 1 [SB0090]
Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17 1 [UART ]: MPU-401 UART - MPU-401 UART MPU-401 UART at 0x330, irq 10so I think this is correct, and the "options snd slots=snd-emu10k1" thing had no visible effect.
Quoted 8 lines
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether/dev/snd/*files exist and have proper permissions and ACL (see "getfacl/dev/snd/*")- The default ALSA configuration is hijacked, e.g. via pulse plugin. Try to remove
/etc/asound-pulse.confif present.I've just installed openSUSE 11.0 on this box and the distro kernel 2.6.25.5-something works, but 2.6.26-rc8 doesn't. The symptoms are exactly the same as described in this thread and the kernel is the only system component replaced.
Quoted 8 lines
Quoted 1 line
So this is a regression from 2.6.25, actually. Do you want me to bisect?
Hmm... there is really no visible problematic changes for emu10k1 between 2.6.25 and 2.6.26. I guess checking
/proc/asound/cardsand/or kernel config would save the time of bisect. At least, check the following:1. you have emu10k1 in the first entry (#0) of
/proc/asound/cardsYes. The contents of
/proc/asound/cardsare exactly as shown above.Quoted 2 lines
2. the mixer states are OK (e.g. "Audigy Analog/Digital Output Jack" switch is off, "Master" and "PCM" are muted/adjusted, etc)
I can only run alsamixer as root and then it works correctly. As a normal user it doesn't start due to insufficient access rights.
Quoted 8 lines
While kmix can be started as a normal user, it only shows empty window.
Quoted 1 line
3. run "aplay -Dhw:0
/usr/share/sounds/alsa/test.wav" for testingAs root it works just fine. As a normal user I get:
ALSA lib pcm_hw.c:1240:(_snd_pcm_hw_open) Invalid value for card
aplay: main:583: audio open error: Permission deniedWeird. Could you try to remove ~/.asoundrc and
/etc/asound*.confif they exist?
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
I only had
/etc/asound-pulse.conf. Removed that, but it didn't change anything.Then I have no idea... Could you bisect? At least, I'd like to know whether manually built vanilla 2.6.25.x works on your system...
I made it work and the trick was to set
CONFIG_TMPFS_POSIX_ACL=y.
Ah that explains. On SUSE systems, the device files are created on tmpfs, and the permission to the desktop user is added/removed dynamically at login/logout via hal-resmgr.
thanks,
Takashi