MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Taking the problem back to the root, i discovered a problem.
Alsa ask to chmod /dev/dsp /dev/mixer ... etc
I discovered that those were only links to /dev/sound/dsp ... /dev/sound/mixer and so on !!!
So i tried to chmod the above to 777 to be sure, the thing works but if i log in and out... things get back to the previous information!!!
Can i store chmod information and how ?? ( i use Mdk 9.2 and i used mdk control panel to change things but i discovered this was not changing much ). I have used command line to chmod with the above result.
Also do you know if i should change group ( from users to audio maybe ?? )
I know about permissions, the only think is not clear enough is :
If i use" ls" command for /dev/sound/dsp i have the following information ( more or less )
crw------- 1 myself audio ...
The thing is ... should i change audio to users, or keep it as it is?
Any idea where that script can be ( i have had a look but cannot find it )
Also, even when chmoding the sound was not there anyway ( the idea is should i have permissions right away after chmoding, or after a log in/ log out ? in that case as permissions are back to rw only for owner i cannot have sound anyway ? )
You may be able to keep your settings by doing the chmod in etc/rcd/rclocal .this may run the chmod script after everything else initialises . Ihave not tried this with chmod but it works for my joystick . best of luck
I'm a complete newbie (Linux installed a week ago), and had exactly the same problem with my system which is VIA8233. I had CD playing, and the line input worked. All inputs were set to max and un-muted.
As the CD, line, and speakers worked, I figured that this meant the sound card and its driver were sort of OK, but it wouldn't play anything from xmms, and although I had enabled all sounds, they didn't work either.
I tried playing a wav file in xmms (I used startup.wav) and set it to 'repeat'. At first it wouldn't even play the file until I fiddled about with the device it used which was 'PCM'. Then it was playing but still no output. I then realised that in my troubleshooting I now had 3 mixers installed - alsamix, aumix, and KMix. As I am using KDE I decided to keep KMix and get rid of the other 2. After a restart (sorry - old Windoze habits die hard), it all came up and worked OK. Arts still seems to be starting and is also OK.
I didn't need to fiddle with any permissions etc, and don't understand what went on yet, but I'm still learning!
Something I came across while researching a totally unrelated topic:
Apparently, support for the VIA8233 was working in kernel 2.4.16, then "disappeared" until 2.4.20, when it came back.
Check your kernel versions with:
I'd suggest upgrading to the latest 2.4 kernel, or the 2.6 series if you feel ambitious.