Sponsored Content
Full Discussion: No sound
Operating Systems Linux No sound Post 302592666 by Corona688 on Tuesday 24th of January 2012 12:26:05 PM
Old 01-24-2012
64-bit what? sound hardware is hardware-dependent.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

freeBSD 4.4 sound help please

how do i configure sound on a laptop in FreeBSD 4.4 the laptop is a Green753+ i think the sound is a ess ? can any one help please tryed to make a genric kerl but did not work (1 Reply)
Discussion started by: amicrawler
1 Replies

2. UNIX for Advanced & Expert Users

Sound Problems

Hi All I am having difficulty configuring sound on my system an wonder if anyone can help me. xmms refuses to play telling me that oss_open(): Failed to open audio device (/dev/sound/dsp): No such file or directory what I have done to try and fix this is 1. create /dev/sound/dsp ... (7 Replies)
Discussion started by: silvaman
7 Replies

3. UNIX for Dummies Questions & Answers

Sound with Mandrake 9

Howdy all, I have a creative vibra 16 sound card and Mandrake linux 9. I can't seem to get the sound server to run (it comes up with errors). I'm a bit of a linux newb so I'd really appreciate any help on what I have to do to get it working. Thanks! ~ Paul (2 Replies)
Discussion started by: KrazyGuyPaul
2 Replies

4. UNIX for Dummies Questions & Answers

Does this sound right?

A user's default permissions when creating new files or directories is set by the umask of either the system or in the startup script of the user itself. For example, I have 'umask 022' in my .profile which means that my default permissions will be 755. Typically, the system default umask is 022,... (1 Reply)
Discussion started by: wmosley2
1 Replies

5. Linux

sound cards

i installed Red Hat Fedora (successfully this time) and my sound card wasnt automticly found or what ever. so how do i get my sound working and stuff? how do i gonfigure the sound card? how do i get it to detect the sound card? (4 Replies)
Discussion started by: xcaliber
4 Replies

6. Linux

sound driver

i install fedora core 4 but it fail to detect my sound card. my sound card is sigmatel. how can i solve this problem? can i install other sound driver? thx (9 Replies)
Discussion started by: wsc
9 Replies

7. UNIX for Dummies Questions & Answers

turn off sound

how to disable anoying beep sound??? (4 Replies)
Discussion started by: nnn
4 Replies

8. UNIX for Advanced & Expert Users

Sound Device

hi all i have a problem that if i use something like firefox it will grab the sound device and not release it, so i can not use skype is there a command to see what is using the audio device i am using Fedora thaks Adam (3 Replies)
Discussion started by: ab52
3 Replies

9. OS X (Apple)

Sound under OS 10.4.11 and 10.7.2

There is a change with UnIX version concerning these two platforms. I own a Power G4 Mac with OS 10.4.11 and a Mac Book Pro with Lion OS 10.7.2. There are some problems of compatibilities between the two UNIX versions. Under OS 10.4.11, these three UNIX commands work, in order to produce sounds,... (4 Replies)
Discussion started by: shub22
4 Replies

10. Red Hat

No sound in my Linux

I am not able to run any video file. Getting message something like : no audio facility. Is this may be problem of driver. If so please send me link for the same. I am working on Red Hat Fedora (Linux) (16 Replies)
Discussion started by: ravisingh
16 Replies
osstest(1)							 OSS User Commands							osstest(1)

NAME
osstest - Open Sound System audio self test applet. DESCRIPTION
The osstest applet is a simple test application that can be used to test functionality of the sound hardware installed in the system. osstest performs a playback test for each installed audio device. If there are any "machine detectable" problems they will be reported. You will first hear an audio sample played on the left speaker, then the right speaker and finally in stereo on both speakers. It's user's responsibility to listen if the test sound is audible. If no sound output can be heard the possible reason is one of the fol- lowing: 1. An error was reported by osstest. In this case there will usually not be any sound output. The error needs to be fixed before running osstest again. 2. There is no headphones or speakers connected. Or the connection is not made correctly. 3. The mixer volume level is set to a too low value. By default it should be OK. The mixer level can be adjusted using the mixer, ossmix and ossxmix utilities distributed with OSS. 4. Some notebooks have nonstandard volume control and/or speaker selection hardware that is not supported by OSS. It's very likely that OSS doesn't support such vendor specific additions. If no errors were reported and the test sound was audible it means that OSS and your sound hardware is functioning correctly. If you still encounter problems with some sound applications the reason is almost certainly in the application. Check it's configuration or try to use another equivivalent application. If you are having problems with JDS, KDE and/or Gnome system sounds, you need to make sure that OSS gets started before the GUI environ- ment. Refer to your operating system's startup procedures. SAMPLE RATE DRIFT The osstest utility measures a sample rate drift value after playing back the test sound. Ideally it should be 0% but in practice there will be an error of few percents. 0% means that the 48000 Hz test file was played exactly at 48000 Hz sampling rate. The sample rate measurement is based on the system timer which has limited precision. It's likely that less than 1% differenc between the nominal and the measured sampling rates are actually caused by an error in the measurement. For this reason the drift reported by osstest should not be used as any kind of quality measurement. However if the drift is very large it means that there is something wrong in the system. The oscillator chip used with the sound chip is broken or the system clock is running at a wrong speed. USING OSSTEST MANUALLY The osstest utility is located in the /usr/bin directory. It can be run manually to test functionality of OSS and your sound hardware. When invoked without any command line parameters osstest performs the default test on all devices. However it will skip some of the devices base on the following rules. o It is possible to test just one of the available audio devices by giving its number on command line (for example osstest 1). Use the device index numbers reported by "ossinfo -a". o Use the -l command line option to loop the test infinitely. o Virtual mixer devices will not be tested. Use the -V command line option to force test of virtual devices. o The actual (physical) audio devices will be tested directly (bypassing virtual mixer). If you want to test playback through vmix then use the -V option. o Multiple device files related with the same physical device will not be tested. Only the first one gets tested while the remaining ones will be skipped. At this moment there is no way to force osstest to test this kind of devices. o Only stereo devices will be tested. Future versions of osstest will be able to test mono and multi channel devices too. Also osstest requires that the device supports the 16 bit signed format and 48kHz sampling rate. o Send a SIGQUIT (Ctrl- on most terminals) to make osstest skip a device. FILES
/usr/bin/osstest SEE ALSO
savemixer(1) AUTHOR
4Front Technologies 16 December 2012 osstest(1)
All times are GMT -4. The time now is 04:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy