Sponsored Content
Full Discussion: Speakers not working....
Operating Systems Linux Red Hat Speakers not working.... Post 302437599 by mark54g on Thursday 15th of July 2010 01:21:02 PM
Old 07-15-2010
I think the problem here is that the original poster doesn't understand the role of the card in this. His speakers are more than likely working fine. His audio card is the part that is not working.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Using gzip and my speakers have gone mad!

Hello, I wanted to compress a directory which I did with: tar -czvf backup15062007.tar.gz backup15062007/ I knew that you could specify the compression level with gzip so I then did: gzip -cvf9 backup15062007.tar.gz backup15062007compress.tar.gz Now I know this probably won't... (5 Replies)
Discussion started by: patwa
5 Replies

2. Ubuntu

I can't make my pc speakers beep

I don't know why, but when I issue echo -e '\a' or beep. I get only some sound, set in my OS (Ubuntu Karmic). I tried to run these on Lenovo Y510KA and Lenovo S10-2. Is there another way to make my laptops beep?.. (3 Replies)
Discussion started by: Sapfeer
3 Replies

3. Red Hat

Nslookup working but ping not working at windows client

Hi Team we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network. Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and... (5 Replies)
Discussion started by: boby.kumar
5 Replies

4. Shell Programming and Scripting

Automating pbrun /bin/su not working, whenever manually it is working using putty

I am trying to automate a script where I need to use pbrun /bin/su but for some reason it is not passing thru the pbrun as my code below. . ~/.bash_profile pbrun /bin/su - content c h 1 hpsvn up file path I am executing this from an external .sh file that is pointing to this scripts file... (14 Replies)
Discussion started by: jorgejac
14 Replies

5. Shell Programming and Scripting

Working web service call not working with curl

Hello, Newbie here, I have a perfectly well working web service call I can issue from chrome (PC Windows 10) and get the results I want (a dimmer being turned on in Fibaro Home Center 2 at level 40) I am not allowed to post urls but the below works with http and :// and... (3 Replies)
Discussion started by: abigbear
3 Replies

6. Shell Programming and Scripting

Disk Space Utilization in HTML format working in one environment and not working on the other

Hi Team, I have written the shell script which returns the result of the disk space filesystems which has crossed the threshold limit in HTML Format. Below mentioned is the script which worked perfectly on QA system. df -h | awk -v host=`hostname` ' BEGIN { print "<table border="4"... (13 Replies)
Discussion started by: Harihsun
13 Replies
7(16 December 2012)													       7(16 December 2012)

NAME
dsp - Open Sound System audio devices DESCRIPTION
/dev/dsp is the default audio device in the system. It's connected to the main speakers and the primary recording source (such as micro- phone). The system administrator can set /dev/dsp to be a symbolic link to the desired default device. The ossinfo utility can be used to list the available audio devices in the system. /dev/dsp_mmap, /dev/dsp_ac3, /dev/dsp_multich and /dev/dsp_spdifout are default audio devices for specific applications such as games or media (DVD) players. DIRECT ACCESS AUDIO DEVICE FILES
OSS 4.0 (and later) will create audio devices under /dev/oss/<device> directory. For example /dev/oss/sblive0/pcm0 is the first audio device that belongs to the first Sound Blaster Live! or Audigy card in the system. These direct devices are used when an application needs to access specific audio device (instead of the default one). You can use the ossinfo(1) utility with the -a option to get a list of the available audio devices in the system. LEGACY AUDIO DEVICE FILES
Traditionally OSS has created device files like /dev/dsp0 to /dev/dspN for each audio device in the system. OSS 4.0 still supports this legacy naming. These files are symbolic links to the actual device files located under /dev/oss. The ossdevlinks(8) utility is used to manage these links and it will be automatically invoked when OSS is started. COMPATIBILITY
o The /dev/dsp (default() audio device file will be supported by all OSS implementations and versions. o The special purpose audio default devices (such as /dev/dsp_mmap) are only supported by OSS 4.0 and later. o The legacy audio device files (such as /dev/dsp1) are supported by all OSS versions and implementations. o New style audio device files (under /dev/oss) are only supported by OSS 4.0 and later. However some independent OSS implementations may only support the legacy naming even they are otherwise OSS 4.0 compatible. o /dev/dsp0 doesn't exist in all Linux systems which use /dev/dsp for the same purpose. In such systems /dev/dsp points to the first audio device and /dev/dsp1 to the second. PROGRAMMING INFORMATION
See the Audio Programming section of the OSS Programmer's Guide (DSP(2)) for more info. OPTIONS
None FILES
o /dev/dsp Default audio device o /dev/dsp_mmap Default audio device for applications using mmap(2) o /dev/dsp_ac3 Default audio device for applications sending Dolby Digital (AC3) audio to an external receiver. o /dev/dsp_multich Default multichannel (4.0-7.1) audio output device o /dev/dsp_spdifout Default digital audio (S/PDIF) output device o /dev/oss/<driver>/pcmN Direct access device files for individual audio devices. o /dev/dsp0 to /dev/dspN Legacy style direct access audio device files. AUTHOR
4Front Technologies OSS Devices 7(16 December 2012)
All times are GMT -4. The time now is 05:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy