SlackwareThis Forum is for the discussion of Slackware 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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When you say no sound... there is no /dev/dsp device, or what? play a mp3 file, and if it does *not* give you an error.. chances are your main output is muted. Run alsamixer and check if there is a MM overtop the audio levels . Far to many times have i looked to deep and noticed it was just muted 0_o.
Originally posted by SomeGuy7898 When you say no sound... there is no /dev/dsp device, or what? play a mp3 file, and if it does *not* give you an error.. chances are your main output is muted. Run alsamixer and check if there is a MM overtop the audio levels . Far to many times have i looked to deep and noticed it was just muted 0_o.
There is no sound with XMMS via ShoutCast when I use the bare.i kernel. XMMS sound works fine with the Win4Lin kernel. The alsamixer is the same for both, obviously as I only have one alsa installed.
It's got to be a kernel thing with the bare.i that I didn't do or need to do. But what?
I see no errors anywhere.... dmesg or when I try to run
root@xxxx:/home/al# aplay /usr/share/sounds/phone.wav
Playing WAVE '/usr/share/sounds/phone.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
root@xxxx:/home/al#
nothing happens. (I should get a phone ring.... and I do when booted to the other kernel.
It can't be an alsa problem as its the same for each kernel. I must be missing some module in the bare.i ... but which one?
No error at all eh? So it can play the audio through some known device..
Check alsamixer, and MAKE SURE ITS NOT MUTED. I'm not kiddin' yah, I have found it muted after spending like 2 - 3 hours trying to figure out why it wasn't working, lol.
If alsamixer has a MM above the audiolevel on master and PCM... then one of hte channels is muted (Master is master.. and PCM is the normal wave output to your spk out). Double check that m8
Both Master and PCM are fine. No MM and setting is 100<>100
If this was an alsa problme it would show up on BOTH kernels. So it is not alsa's config. But maybe some module is being loaded (or is compiled) in the Win4Lin kernel that works and not in the bare.i one. What should I look for?
Al
(Going to bed. Will be back in the AM on this!)
Humm... does the device at the top of alsamixer show the same on both kernels? If both devices are the same, both show up in alsamixer as full volume, and only 1 plays.. check the premissions on /dev/dsp.. Also, just for future refrence, what is your sound card, and what does alsamixer show as the device? also, give me a 'lsmod' as well please
alsamixer shows ICH5 as the sound card when running both kernels. Makes sense. There is only ONE alsamixer installed TTBOMK.
permissions for both are:
al@xxx:~$ ls -l /dev/dsp
lrwxrwxrwx 1 root root 4 Oct 10 2003 /dev/dsp -> dsp0
al@xxx:~$ ls -l /dev/dsp0
crw-rw-rw- 1 root sys 14, 3 Aug 29 2003 /dev/dsp0
The lsmod for each are below... first the BAD, then the GOOD. Note that on the BAD the 'used by' is different on the following. And why are the sizes different? Why is oss there to begin with? I'm really baffled by this.
Hold on. I noticed something else when looking at alsamixer for each kernel. The no-sound kernel has a "headphone' vertical bar in alsamixer while the "good" kernel does not show that when I execute alsamixer.
Are there two different alsa systems here and the bare.i kernel is pulling in the wrong one. How can I check to see what versions each is using?
By the sounds of this... Your kernels (both bare.i and the W4L) are both fully supporting your sound card. Alsamixer detects the device under both kernels.. both kernels have the module loaded and being used. If all the volume is turned up, speakers are plugged in and turned on (Doh!), it *should* be working. When an app goes to play music, and returns no error (just you don't hear anything), usually its your output being blocked, not device / kernel problems.
Originally posted by gbonvehi Well if ALSA isn't built-in on the the kernel, you should be able to update it by running the "bad" kernel and updating alsa-driver package.
I don't know what is built into what because like an idiot I deleted the "good" kernel source folder and config etc. Like I said, I'm an idiot.
It's not that big a deal. I was was mainly curious as to why it would work in one kernel and not in the other. I DO remember downloading the alsa stuff and compiling it and then building the kernel of the Win4Lin. So that is how I have two sets of alsa.
If I update the drive via pkgtools, I wonder what that will do the the "good" kernel as I don't know if I have it compiled in or if it is a module. Why? Because I'm an IDIOT !!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. Far to many times have i looked to deep and noticed it was just muted 0_o.
