Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

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.

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 192 to 2097152
Period size range from 64 to 699051
Using max buffer size 2097152
Periods = 4
was set period_size = 524288
was set buffer_size = 2097152
0 - Front Left
Time per period = 30.115545
0 - Front Left
Time per period = 30.115036
0 - Front Left
Time per period = 30.129845
0 - Front Left
Time per period = 30.133851
0 - Front Left
Time per period = 30.122867
0 - Front Left
Time per period = 30.117779
0 - Front Left

The speaker-test just continue in the above messages.
In the alsamixer the card and chip is pulseaudio and threre is only two volumes Master and Caputre, here is the alsamixer screenshot:

Thanks for the reply i select the C-media CMI8738 and there was all other controls visible in the alsamixer here is the screenshot:alsamixer2.png
But when i restart the pc then card is again the pulseaudio whith the only one master control in the alsamixer.

For some reason --stop doesn't seem valid, kind of lame imo. I'd recommend using pulseaudio even though I'm not a fan of it. Your openjdk and other things are likely configured for it, and fail to do certain things if you don't use pulseaudio. Like in the game runescape all you get is the musak tracks and none of the sound effects if you don't use pulseaudio. Be sure to add the user to the audio group and the pulse, pulse-access groups.

$ groups
<user> cdrom audio video games pulse pulse-access

That being said pulseaudio does suck, it lacks many things many would consider deal breakers. If you run pulse, even pulse over jack for a software synth you will have a high latency because the sounds will be resampled before actually being outputted. So having the option to opt out of pulseaudio is a good one.

Other tricks are to rename your .asoundrc file if you have one. This should force things to use alsa natively. You can also have different versions of .asoundrc with the renaming trick depending on how you use your soundcard. One for pulse, one for alsa, one for jack, and so on. You might also try purging the .pulse folder and restarting pulse.

Make sure your sound levels are set which you seemed to have done. You can save your levels with alsa-ctl

# alsa-ctl store

And they should be restored at the next boot. It's saved to /var/lib/alsa/asound.state. If you have another mixer application that your prefer that saves settings like aumix, you may want to delete that asound.state file so your settings will be restored. The debian boot sequence will restore mixer settings from asound.state if it exists and bypass aumix settings when both files / settings exist. I'm not a fan of 100% volume settings, a lot of cards distort noticeably when > 90%. Just saying.

In reply of jv2112 there was no sound when i select the C-media in alsamixer but the problem is when i select the opions in alsamixer and gstreamer-properties after reboot the changes is discard, this is a command use to play a file with maplayer and get errors if some one can help:

Quote:

#mplayer -ao alsa:device=CMI8738-MC6 20051210-w50s.flv

MPlayer2 UNKNOWN (C) 2000-2012 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

And don't forget to move .asoundrc back to it's former name. With adjustments if that somehow works for you. Because if it does work, then it is NOT a driver issue. It is a system configuration issue. Note that mplayers syntax is a bit odd as it's not hw:0 like we would use with anything that is alsa. And where 0 is the number of the device you want to use (as listed in /proc/asound/cards) which may not be 0.

For some things you can have a single line in .asoundrc if 0 is not your primary audio device.

~/.asoundrc

Code:

defaults.pcm.card 1

But some things will always use the 0 device no matter what you do. Which is the primary motivation behind aoss, artsdsp, esddsp, padsp, and whatever audio savior of the week we're going with this week. Re-indexing your card numbers is possible with a little customization of /etc/modprobe.d/