SuSE Linux 9.1 personal, kernel 2.6.xx, KDE 3.2.1... I have Intel 82801DB-ICH4 sound card. It works, I can hear the sound. I have 3 users: root, first_user, second_user. Now here's the problem. CASE 1: for example, if I start first session as first_user I can hear the sound, there's KAMix in systray and everything is fine. Then if I start new (second) session as second_user the sound is gone. If I try to open KAMix it gives me error: "direct access to sound device not possible" no soundcard available or sound not configured yet. In control center - sound system, the sound is enabled ... but... then if I start another (third) session as root everything is ok. KAMix loads, sound works, I can change configuration, mute sound.... CASE 2: if i start first session as root everything is ok. then if i start second session eather as first or second user... sound does not work. both users are members of audio group. what's the catch??? what am I missing here??? thanx for your answers
Hi Bojan! That's because this audio chip cannot handle multiple opens. So only one alsa application can connect to the card at one time, and that's the arts daemon from your first session. There should be a possibility to configure alsa to use the so called dmix plugin, so alsa handles the multiple opens in software and mixes the streams. I was able to get this to work on an older SuSE with updated alsa, but with the alsa from SuSE 9.1 I wasn't able to get this working. Can anybody help here? One starting point: http://alsa.opensrc.org/index.php?page=DmixPlugin Greets, Daniel Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
SuSE Linux 9.1 personal, kernel 2.6.xx, KDE 3.2.1... I have Intel 82801DB-ICH4 sound card. It works, I can hear the sound. I have 3 users: root, first_user, second_user. Now here's the problem.
CASE 1: for example, if I start first session as first_user I can hear the sound, there's KAMix in systray and everything is fine. Then if I start new (second) session as second_user the sound is gone. If I try to open KAMix it gives me error: "direct access to sound device not possible" no soundcard available or sound not configured yet. In control center - sound system, the sound is enabled ... but... then if I start another (third) session as root everything is ok. KAMix loads, sound works, I can change configuration, mute sound....
CASE 2: if i start first session as root everything is ok. then if i start second session eather as first or second user... sound does not work.
both users are members of audio group. what's the catch??? what am I missing here???
thanx for your answers
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
On Monday 28 of June 2004 09:41, Daniel Eckl wrote:
Hi Bojan!
That's because this audio chip cannot handle multiple opens. So only one alsa application can connect to the card at one time, and that's the arts daemon from your first session.
There should be a possibility to configure alsa to use the so called dmix plugin, so alsa handles the multiple opens in software and mixes the streams. I was able to get this to work on an older SuSE with updated alsa, but with the alsa from SuSE 9.1 I wasn't able to get this working.
Can anybody help here?
One starting point: http://alsa.opensrc.org/index.php?page=DmixPlugin
Greets, Daniel
Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
SuSE Linux 9.1 personal, kernel 2.6.xx, KDE 3.2.1... I have Intel 82801DB-ICH4 sound card. It works, I can hear the sound. I have 3 users: root, first_user, second_user. Now here's the problem.
CASE 1: for example, if I start first session as first_user I can hear the sound, there's KAMix in systray and everything is fine. Then if I start new (second) session as second_user the sound is gone. If I try to open KAMix it gives me error: "direct access to sound device not possible" no soundcard available or sound not configured yet. In control center - sound system, the sound is enabled ... but... then if I start another (third) session as root everything is ok. KAMix loads, sound works, I can change configuration, mute sound....
CASE 2: if i start first session as root everything is ok. then if i start second session eather as first or second user... sound does not work.
both users are members of audio group. what's the catch??? what am I missing here???
thanx for your answers
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
How come if I start first session as normal user and for example start playing mp3s, then start second session as super user, I can still access my soundcard, but as a normal user I cannot. If normal user is logged in at session1, super user can still access the sound card, but the normal user cannot. I don't get it... with SuSE 9.0 everything was fine. After fresh 9.1 install it's not.
On Monday 28 of June 2004 09:41, Daniel Eckl wrote:
Hi Bojan!
That's because this audio chip cannot handle multiple opens. So only one alsa application can connect to the card at one time, and that's the arts daemon from your first session.
There should be a possibility to configure alsa to use the so called dmix plugin, so alsa handles the multiple opens in software and mixes the streams. I was able to get this to work on an older SuSE with updated alsa, but with the alsa from SuSE 9.1 I wasn't able to get this working.
Can anybody help here?
One starting point: http://alsa.opensrc.org/index.php?page=DmixPlugin
Greets, Daniel
Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
SuSE Linux 9.1 personal, kernel 2.6.xx, KDE 3.2.1... I have Intel 82801DB-ICH4 sound card. It works, I can hear the sound. I have 3 users: root, first_user, second_user. Now here's the problem.
CASE 1: for example, if I start first session as first_user I can hear the sound, there's KAMix in systray and everything is fine. Then if I start new (second) session as second_user the sound is gone. If I try to open KAMix it gives me error: "direct access to sound device not possible" no soundcard available or sound not configured yet. In control center - sound system, the sound is enabled ... but... then if I start another (third) session as root everything is ok. KAMix loads, sound works, I can change configuration, mute sound....
CASE 2: if i start first session as root everything is ok. then if i start second session eather as first or second user... sound does not work.
both users are members of audio group. what's the catch??? what am I missing here???
thanx for your answers
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
How come if I start first session as normal user and for example start playing mp3s, then start second session as super user, I can still access my soundcard, but as a normal user I cannot.
If normal user is logged in at session1, super user can still access the sound card, but the normal user cannot.
I don't get it... with SuSE 9.0 everything was fine. After fresh 9.1 install it's not.
I´ve successfully configured dmix plugin on SuSE 9.1. Here are my steps: 1)su root 2)cp /etc/asoundrc.dmix /etc/asound.conf 2.1) My asound.conf looks like pcm.ossmix { type dmix ipc_key 1027 # must be unique! slave { pcm "hw:0,0" # you cannot use a "plug" device here, darn. period_time 0 period_size 1024 buffer_size 4096 #format "S32_LE" #periods 128 # dito. rate 44100 # with rate 8000 you *will* hear, # if ossmix is used :) } bindings { 0 0 # from 0 => to 0 1 1 # from 1 => to 1 } } pcm.!default { type plug slave.pcm "ossmix" } # mixer0 like above ctl.mixer0 { type hw card 0 } 2.2) My asound.conf differs from asoundrc.dmix, but original asoundrc.dmix should be OK. 3)/etc/init.d/alsasound restart That´s all. Some strange things: play(console) doesn´t work when xmms plays via ALSA so i´setted up xmms to play via aRts and switched from play to aplay WBR, Victor Galkin.
Wait a minute! I was too fast! I found this page: http://www.pseudorandom.co.uk/2004/debian/alsa/ And it worked on my SuSE 9.1 out of the box. You only need to create the /etc/asound.conf with the shown content and that's all. Forget the modules, they are alright on SuSE 9.1. Just use the asound.conf. Greets, Daniel Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
SuSE Linux 9.1 personal, kernel 2.6.xx, KDE 3.2.1... I have Intel 82801DB-ICH4 sound card. It works, I can hear the sound. I have 3 users: root, first_user, second_user. Now here's the problem.
CASE 1: for example, if I start first session as first_user I can hear the sound, there's KAMix in systray and everything is fine. Then if I start new (second) session as second_user the sound is gone. If I try to open KAMix it gives me error: "direct access to sound device not possible" no soundcard available or sound not configured yet. In control center - sound system, the sound is enabled ... but... then if I start another (third) session as root everything is ok. KAMix loads, sound works, I can change configuration, mute sound....
CASE 2: if i start first session as root everything is ok. then if i start second session eather as first or second user... sound does not work.
both users are members of audio group. what's the catch??? what am I missing here???
thanx for your answers
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
On Monday 28 June 2004 09:11, Daniel Eckl wrote:
I found this page: http://www.pseudorandom.co.uk/2004/debian/alsa/
And it worked on my SuSE 9.1 out of the box. You only need to create the /etc/asound.conf with the shown content and that's all. Forget the modules, they are alright on SuSE 9.1. Just use the asound.conf.
I have just the same situation as Bojan regarding availability of sound to root and to two ordinary users. I am running SuSE 9.0 and it was the same when I ran SuSE 7.3, so I have come to believe that this is just how it has to be. I am running KDE 3.2.3.But again, it has been like this for KDE2, KDE 3.1, etc. I tried adding /etc/asound.conf but it makes no difference. This is true for the version suggested by Daniel and for the version suggested by Victor. I am assuming (but only assuming) that my system is taking no notice of /etc/asound.conf at all. Does anyone have a solution that works for SuSE 9.0? I'd like to fix this if possible because my daughters keep leaving themselves logged on and I hardly ever get to hear my MP3s! Steve Dundee, UK
Well, just make an strace -ff aplay somesound.wav | grep -i "alsa\|asound" and look what config files it is trying to open. What I don't understand is, why on this sound chip the root should has access if an user has the sound device open. I assume that happens by fluke, because artsd opens the sound device, but if it's not needed for some seconds, it releases the device... But that's only a wild guess and depends if you are using xmms over arts or alsa directly or oss or something else... But judging from the type of audio device which is on the intel 845 boards, then it's for sure that the device can only handle one open at a time. I use such a board at work, too. Greets, Daniel Zitat von Steve King <stevenking66@yahoo.co.uk>:
On Monday 28 June 2004 09:11, Daniel Eckl wrote:
I found this page: http://www.pseudorandom.co.uk/2004/debian/alsa/
And it worked on my SuSE 9.1 out of the box. You only need to create the /etc/asound.conf with the shown content and that's all. Forget the modules, they are alright on SuSE 9.1. Just use the asound.conf.
I have just the same situation as Bojan regarding availability of sound to root and to two ordinary users. I am running SuSE 9.0 and it was the same when I ran SuSE 7.3, so I have come to believe that this is just how it has to be.
I am running KDE 3.2.3.But again, it has been like this for KDE2, KDE 3.1, etc.
I tried adding /etc/asound.conf but it makes no difference. This is true for the version suggested by Daniel and for the version suggested by Victor. I am assuming (but only assuming) that my system is taking no notice of /etc/asound.conf at all.
Does anyone have a solution that works for SuSE 9.0?
I'd like to fix this if possible because my daughters keep leaving themselves logged on and I hardly ever get to hear my MP3s!
Steve Dundee, UK
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
On Monday 28 of June 2004 19:45, Daniel Eckl wrote:
Well, just make an
strace -ff aplay somesound.wav | grep -i "alsa\|asound"
and look what config files it is trying to open.
What I don't understand is, why on this sound chip the root should has access if an user has the sound device open.
I assume that happens by fluke, because artsd opens the sound device, but if it's not needed for some seconds, it releases the device...
But that's only a wild guess and depends if you are using xmms over arts or alsa directly or oss or something else...
But judging from the type of audio device which is on the intel 845 boards, then it's for sure that the device can only handle one open at a time. I use such a board at work, too.
Greets, Daniel
Ahh... I'll just have to live with one-user-sound for now. It's not such a big problem, since I only have two users. In the future however I'll try to fix it. I need to do some school work now and then I'll see what I can do :)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon June 28 2004 2:03 pm, Bojan Hribernik wrote: - -------snip------------
Ahh... I'll just have to live with one-user-sound for now. It's not such a big problem, since I only have two users. In the future however I'll try to fix it. I need to do some school work now and then I'll see what I can do :)
I haven't really been following this thread but since there hasn't been a solution heres my 2 cents. I've got a soundblaster live running on suse 9.1 with multiple users logged in. Some or all of the following may or may not apply. All users are part of the audio group What really did the trick (I believe) was changing permissions in the /dev/snd directory. All of the devices in this directory are now rw-rw-rw- and owned by the first user to login and the root group. I know when I made this change I had to change some boot script to do the change automatically on reboot (the changes to permissions, not owner or group) but I don't remember which script I changed. There may be security issues w/ my method but if there are I'm sure someone will pipe up. Hope this is useful Good luck - -- dh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFA4PUkBwgxlylUsJARAmYlAJ4xYjNp1xQXmmmWqiCkZfBReRUwBgCeNetf WAL4npCz3vSRR9QDX5e72Fs= =vmSi -----END PGP SIGNATURE-----
I concur with you mail. I run 8.2 with kde 3.2.3 and have not tweaked my sound installation since installation. I also have the devices in /dev/snd/ set as 666 permission and sound works for all users that are logged in and that includes those logged in through xdmcp remotely although this can be annoying since the sound comes out at the PC where I am working. In suse 8.2 I did not need to change any permissions!! Andrew On Tuesday 29 June 2004 05:50, dh wrote:
On Mon June 28 2004 2:03 pm, Bojan Hribernik wrote: -------snip------------
Ahh... I'll just have to live with one-user-sound for now. It's not such a big problem, since I only have two users. In the future however I'll try to fix it. I need to do some school work now and then I'll see what I can do :)
I haven't really been following this thread but since there hasn't been a solution heres my 2 cents.
I've got a soundblaster live running on suse 9.1 with multiple users logged in.
Some or all of the following may or may not apply. All users are part of the audio group
What really did the trick (I believe) was changing permissions in the /dev/snd directory. All of the devices in this directory are now rw-rw-rw- and owned by the first user to login and the root group. I know when I made this change I had to change some boot script to do the change automatically on reboot (the changes to permissions, not owner or group) but I don't remember which script I changed.
There may be security issues w/ my method but if there are I'm sure someone will pipe up.
Hope this is useful Good luck --
dh
-- Andrew Colvin apc@abcj.demon.co.uk ICQ: 44775817 Yahoo Messenger: apcolvin Jabber: acolvin@jabber.com -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) mQGiBD8FKdkRBADo7ANPdaMNYIlihjYh5oBld3ShWLTVqfQVjz5+twZgo7T5FlCy OSscQaC12NiYixanlZqZrXJs7/fQGAKAZ/CFZvZCTufHLuO5IXVOyRZAWNu7QbcN kWc8m0UilZDSKSb+AxXCnMpW/iEyQ0l8Zv6PKKRrC9Ok/zX9dszCSYakdwCgpKHY MI10jbBAD8cGMWIHGGj4egUD/0f2AWy8Ko02nW3zYLjV6qFkYGLc524qX/XhLhBo m4mhba5SWZl3P7CWs91ZkBTjgdz/XHUA5nCoFCQWTxuTL1UUx9dSHnCkPn4JQRTe /jWO1aOD+HBJYWV1w1r2EfDJE/Fmnukb+tgc3D2ZBROFvQSN9fCYt29aINkVyz0A BXj3A/4xwIAT+PfyiSkn6wheSUdhvXusQ4pZuETu+dbCNpvKWvR7p45KdJQ6DsRV mgWnVQZSxxPBBJIpXl/2JGI9F37VLnA4ATx8qauntHfDL11wjLCAIVab6x+0+ZeM s69xywtWOTiaTU0Rjh8IeNDDvb3hv/3EWCmfyQXvbDlLgRcS8LQkQW5kcmV3IENv bHZpbiA8YXBjQGFiY2ouZGVtb24uY28udWs+iFkEExECABkFAj8FKdkECwcDAgMV AgMDFgIBAh4BAheAAAoJEP9j3GM12XCdoWMAn1byxQyJH+Rxtcjd6ZEyS1gCAHWC AJ9GI9ZtwL/m703mg9T4hh+CajwZirkCDQQ/BSnsEAgAuBM0PxJdK1vKrHg1inEJ 83+e0oQPWLhTnvV3wT34OGkj/Krzexo9cOUHM5BteidQY6ovhH3AKjmkF0aNXaay xpsVrtXYpqEWgqeZagRvuLw5+mj/X9+S0LS458bFmwpkkqZ+5QOhoLjNGeYutHqJ orINQsU/74NLfgKbGd94uP82t1kPTgF+oAuVUCidqVN0eubQ4OdxZ+ySxxCRU4GU vbUVxo/CfnG0PazXeWOIqBrq+WkuHF/C6OoBGyi67UXq5FjhR8hrmr4OuDBXuU0Z mb08CuLi0nTxXrbwrmH0G9SzXBMxMBRep9qnGdILVWeACeIz9sVBj+dwJHyTpgM2 7wAEDQf/QXSyLsrX9pufdGSJqKS6+sMouMeJo+fnkX2VXUFLLDX7KdwmHO4liISb BleT3m69w/WwVwN286kW7wlMVXD7cLFCLC3SVXLHaVVkArGt/9uY6g3gZ53FaqNv NvumuYLpqH6iAicP9rIVrA69ztTwtmbqcHA+P6juoO3tJohJEiQhlrmH0Tmp+BSq XMyBUb5SJJOeRArPb1FNF9Q96iOk45EIRPp4riiaBptOFe95jJBiWBBfLIuQDMQ8 PA6gVw+u9kMUbKjA30yj4vL43lFyQPUwSiT0okgq0/TXMzyO568UFhYTeT/DV8Lq 5evvNwRmRpjfJHwekUyD4MHVkEr5BohGBBgRAgAGBQI/BSnsAAoJEP9j3GM12XCd KWAAoJIN9wx51sDaCHdY49MnNNFxZ7imAJsEi4G5d9LOIBne++TrHCFMjWzcwA== =AFMd -----END PGP PUBLIC KEY BLOCK-----
On Tuesday 29 of June 2004 08:54, Andrew Colvin wrote:
I concur with you mail. I run 8.2 with kde 3.2.3 and have not tweaked my sound installation since installation. I also have the devices in /dev/snd/ set as 666 permission and sound works for all users that are logged in and that includes those logged in through xdmcp remotely although this can be annoying since the sound comes out at the PC where I am working.
In suse 8.2 I did not need to change any permissions!!
Andrew
On Tuesday 29 June 2004 05:50, dh wrote:
On Mon June 28 2004 2:03 pm, Bojan Hribernik wrote: -------snip------------
Ahh... I'll just have to live with one-user-sound for now. It's not such a big problem, since I only have two users. In the future however I'll try to fix it. I need to do some school work now and then I'll see what I can do :)
I haven't really been following this thread but since there hasn't been a solution heres my 2 cents.
I've got a soundblaster live running on suse 9.1 with multiple users logged in.
Some or all of the following may or may not apply. All users are part of the audio group
What really did the trick (I believe) was changing permissions in the /dev/snd directory. All of the devices in this directory are now rw-rw-rw- and owned by the first user to login and the root group. I know when I made this change I had to change some boot script to do the change automatically on reboot (the changes to permissions, not owner or group) but I don't remember which script I changed.
There may be security issues w/ my method but if there are I'm sure someone will pipe up.
Hope this is useful Good luck --
dh
IT WORKS! I changed permissions in directory /dev/snd to rw-rw---- and multiple non-root users have access to the sound card. I knew it had something to do with permissions and file access, since root was able to use soundcard anytime. Thanx a lot guys!!!
Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
IT WORKS! I changed permissions in directory /dev/snd to rw-rw---- and multiple non-root users have access to the sound card. I knew it had something to do with permissions and file access, since root was able to use soundcard anytime.
Thanx a lot guys!!!
Hi Bojan! Now just do not forget to edit /etc/logindevperm as stated in my mail, because without this at your next login the permissions are reverted again. :) Greets, Daniel
On Tuesday 29 of June 2004 16:19, Daniel Eckl wrote:
Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
IT WORKS! I changed permissions in directory /dev/snd to rw-rw---- and multiple non-root users have access to the sound card. I knew it had something to do with permissions and file access, since root was able to use soundcard anytime.
Thanx a lot guys!!!
Hi Bojan!
Now just do not forget to edit /etc/logindevperm as stated in my mail, because without this at your next login the permissions are reverted again. :)
Greets, Daniel
Done! It works :D Thanks Daniel. I really appreciate your help. Switching from win to linux was quite difficult, but thanks to people like you, my life is now better. lol :D Bojan
Zitat von Bojan Hribernik <bojan.hribernik@siol.net>:
Ahh... I'll just have to live with one-user-sound for now. It's not such a big problem, since I only have two users. In the future however I'll try to fix it. I need to do some school work now and then I'll see what I can do :)
I think I found it. :D SuSE makes the permissions for all alsa sevices for logged in users only. So if user1 logges in, the devices /dev/snd/* are all changed to ownership user1:audio and mode 600 like this: ls -l /dev/snd/pcmC0D0p crw------- 1 user1 audio 116, 16 2004-04-06 15:27 /dev/snd/pcmC0D0p So another user has no permissions on that device anymore (regardless of multi-opens), but root can access, because he has all permissions. So my hint is to edit /etc/logindevperm and change the line: :0 0600 /dev/snd/* to: :0 0660 /dev/snd/* After that all users which are in additional group "audio" can access the device. And after that, you have "only" the problem of multi opens on that sound chip. :) Daniel
On Tuesday 29 June 2004 15:16, Daniel Eckl wrote:
So my hint is to edit /etc/logindevperm and change the line: :0 0600 /dev/snd/*
to: :0 0660 /dev/snd/*
After that all users which are in additional group "audio" can access the device.
That works for me. Brilliant! Thanks! Steve
participants (6)
-
Andrew Colvin -
Bojan Hribernik -
Daniel Eckl -
dh -
Steve King -
Victor Galkin