Hello all, I've been recording radio shows (using sox) all this time without any single problem. Suddenly I'm now unable to to record them. The only different thing I'm doing now is that I log out from KDE before leaving my house in the morning. When I arrive from work at night I now notice that nothing is being recorded. (I have a cron job scheduled at 4pm to record show). Before this, I always left my KDE session open. Today I did a test...I sshed to my home around the time the show was going to be recorded ...and I typed: aumix -q and I got "error opening mixer ". I even tried playing an mp3 file from command line (using mpg123) and I got the following error: ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0' Is there like a timeout for the sound module? If it's not being used for a certain time...will it be unloaded? How come this never happend while I had my KDE session going? What does KDE do in order to make the sound-module loaded all the time? I'll appreciate your comments. Thanks, Jorge
Jorge Fábregas wrote:
I've been recording radio shows (using sox) all this time without any single problem. Suddenly I'm now unable to to record them.
The only different thing I'm doing now is that I log out from KDE before leaving my house in the morning. When I arrive from work at night I now notice that nothing is being recorded. (I have a cron job scheduled at 4pm to record show).
Do you start in runlevel 3 or 5 (i.e. console or graphical). My guess is 5, and logging out of kde logs you out, which changes the permissions on the devices per resmgr. For this to work, IIANM, you would need to be logged in.
Before this, I always left my KDE session open. Today I did a test...I sshed to my home around the time the show was going to be recorded ...and I typed:
Unless you change it from the default, an ssh session does log into the resmgr. Therefore, perms are as if you are not logged in.
aumix -q and I got "error opening mixer ". I even tried playing an mp3 file from command line (using mpg123) and I got the following error: ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0'
For it to work for ssh sessions, check /etc/pam.d/sshd
Is there like a timeout for the sound module? No If it's not being used for a certain time...will it be unloaded? No. How come this never happend while I had my KDE session going? You were logged in, and registered with resource manager (resmgr), which allowed you access permissions. What does KDE do in order to make the sound-module loaded all the time? I don't believe kde is doing anything, and the problem is not the sound module, but device permissions. HTH
-- Joe Morris Registered Linux user 231871
On Friday 16 December 2005 8:36 pm, Joe Morris (NTM) wrote:
I don't believe kde is doing anything, and the problem is not the sound module, but device permissions. HTH
Many thanks Joe! Yes, that totally makes sense. I found this on syslog : linux resmgr[4260]: set_facl() - ACL error on /dev/amidi, acl_set_file: No such file or directory ...about the time I was trying to have access to the sound device. About the runlevel question...Yes, my default is 5. I always left the KDE session open...but now I have many visits (from my brothers) when I'm not home..so now I log out...and this started happening. I guess I'll need to investigate this issue more (trying to make it work..). I'll try logging out of KDE (and then I'll switch to a virtual console, F4 for example, and I'll log there and leave it there) and then I'll switch back to GUI (F7) and leave it there with KDM. There's got to be an elegant way to do this but I'll try that in the meantime. If you know of any please let me know. Thanks! Jorge
On Friday 16 December 2005 8:36 pm, Joe Morris (NTM) wrote:
I don't believe kde is doing anything, and the problem is not the sound module, but device permissions. HTH
Hey Joe! Again, many thanks! That was it! I did a couple of tests...and yes...it never worked while nobody was logged in. I knew it didn't work because I ran sox thru crontab (while no one was logged in) I then added my regular user to the audio group and now it works! Even if no one's logged in..it works! I never thought about being on the audio group ...because I had no problems with sound while using KDE...but now I know, thanks to you, that I was having access to the sound device by means of the "Resource Manager" daemon..and not necessarily because I had proper permissions on it. Now my user belongs to the audio group and can access the audio device even if the user isn't logged on. I can now happily run sox thru crontab and it will work. Many thanks! Jorge
participants (2)
-
Joe Morris (NTM)
-
Jorge Fábregas