02-12-2013
Quote:
Originally Posted by
Corona688
We cannot possibly help you with hardware problems without knowing what your hardware is.
What he said.
Need to know what architecture your computer is, version of RHEL, what sound hardware you're using (make and model) and how it's attached (ISA, PCI, USB, Firewire, etc.) also what modules are loaded (lspci), what your alsa.conf file looks like, and any relevant lines from dmesg or /var/log/messages.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
sapp guys
i've got this little problem, i have no idea what kind of sound card i got
i check dmesg|more and its not there
is there any other way to find out ?
THX (4 Replies)
Discussion started by: challenger
4 Replies
2. UNIX for Dummies Questions & Answers
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
3. UNIX for Dummies Questions & Answers
Dear all,
I have been using suse linux for as long as I can remember. However, for every installation I get the same problem.
Once the installation is completed, and all of my devices (brand new hardware, from reknown brands) are detected, I decide to start doing some work, and play some... (2 Replies)
Discussion started by: bionicfysh
2 Replies
4. UNIX for Dummies Questions & Answers
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. Windows & DOS: Issues & Discussions
Hello all.
Can anyone tell me if there is any alternative to Window$ Media Player for LINUX(Linux Mint).
What am searching for is a player with sound processing capabilities.(Bass,Equaliser,SRS,Dolby,etc..)
Thanks. (1 Reply)
Discussion started by: coolatt
1 Replies
6. Linux
Hi All,
Recently I installed Linux RHEL5 on my machine. It seems that I can not play sound on RHEL5. I have real player installed along with RHEL5 but, when I try to play any song, the error message comes up saying "Can not open the audio device.Another application may be using it."
Does any... (2 Replies)
Discussion started by: gydave
2 Replies
7. OS X (Apple)
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
8. Linux
I reformatted my hard drive and installed Mandriva 2011.
It works fine. I can go to the Internet
The problem is no sound.
I want to listen to songs from YouTube. Sound doesn't come.
I see a man is singing on the screen. No sound.
I had no problem with my old Mandriva. Sound and everything... (11 Replies)
Discussion started by: Toxic
11 Replies
LEARN ABOUT DEBIAN
discover-modprobe.conf
discover-modprobe.conf(5) File Formats Manual discover-modprobe.conf(5)
NAME
discover-modprobe.conf -- configuration file for discover-modprobe(5)
Description
discover-modprobe.conf is the configuration file for discover-modprobe, which is responsible for retrieving and loading kernel modules.
Warning:
This file is a shell script, and as such is subject to a string variable assignment syntax. No space is allowed between the variable
name, the equal (=) sign, and the value(s) assigned. If multiple values are to be assigned, the list must be space-delimited with
surrounding quotes.
Two directives can be used in this file: types and skip. Both can be defined multiple times.
types This describes the classes of hardware that should be scanned and queried.
skip These modules should never be loaded. See the ``Files'' section for details on the mechanism for generating these entries auto-
matically.
Files
/var/lib/discover/crash
A crash file written and erased each time discover-modprobe attempts to load a module. If the file lingers, the computer is
assumed to have crashed while loading that module, and the module name is added to discover-modprobe.conf as a module to skip in
the future.
See Also
discover-modprobe(8), modprobe(8), discover(1)
discover-modprobe.conf(5)