*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
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.
Distribution: Debian Sid, FreeBSD, Mandrake, Red Hat
Posts: 84
Rep:
Sound hardware "detected" but remains silent
I am now in the process of configuring sound in my FreeBSD installation.
I have it running on a Compaq Armada 100S,
which advertises in Compaq specs that it has a Sound Blaster Pro 16 compatible setup. It has a 550 MHz AMD, 192 MB RAM, 6 GB hd. FreeBSD with KDE is running beautifully otherwise.
I tried the sound blaster driver, but it didn't do anything and there was nothing returned from cat /dev/sndstat
I tried one of the via drivers and it did load and return something. It gave it an IRQ of 5 and so forth (I am at a different computer at work now so I can't copy-paste what it showed). I tried playing a CD in KDE then with the CD player, but it just remained silent. I checked all the sound settings and all the volume controls were cranked up and on.
Now just to find the right configuration. Has anyone had experience with this kind of laptop or chipset? (One user I found by Googling said that it is a Via chipset. I haven't seen any official Compaq information, except that it is SB 16 Pro compatible)
If the unused ones are not commented out, then I get syntax errors when the loader.conf file is loaded.
Right now I have it as above. It loads all the drivers. It is still silent. I tried with snd_82c686 and I do get something when I enter
cat /dev/sndstat , but it is still silent.
Distribution: Debian Sid, FreeBSD, Mandrake, Red Hat
Posts: 84
Original Poster
Rep:
This is what I get when I manually load the module:
smithbsd# kldload snd_via82c686
pcm0: <VIA VT82C686A> port 0x3204-0x3207,0x3200-0x3203,0x3100-0x31ff irq 5 at device 7.5 on pci0
pcm0: [GIANT-LOCKED]
pcm0: <Cirrus Logic CS4299 AC97 Codec>
here is what I get when I type: cat /dev/sndstat
smithbsd# cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: <VIA VT82C686A> at io 0x3100 irq 5 kld snd_via82c686 (1p/1r/0v channels duplex default)
Using emu10k1 and the other Soundblaster drivers didn't work, even though Compaq says in the specs that this has a Soundblaster compatible sound setup. Only the snd_via82c686 module says anything when I load it.
So why does it remain silent?
Ekkume
Quote:
Originally posted by sigsegv What do you get when you cat /dev/sndstat? "something" isn't much to go on ...
I suspect that emu10k1 isn't going to do you much good as it's for the SBLive! and Audigy series cards, which you don't have.
You should probably be using snd_via8233 or snd_via82c686, but the output of sndstat will help say for sure.
Also, please post the output of dmesg | grep -i via and dmesg | grep -i snd (if any)
Distribution: Debian Sid, FreeBSD, Mandrake, Red Hat
Posts: 84
Original Poster
Rep:
Quote:
Originally posted by sigsegv Are you using outlook to edit your posts? Don't top post ...
Run mixer in a shell and see if the volume is just all the way down. man mixer for more info.
Topposting is my style. If I post, I want my post on top, not other peoples' posts. For this thread, for you. I will try to remember not to do it.
Sometimes people post the most dreadful stuff, which I don't
want people to have to wade through.
Mixer has been checked in the console. All the settings are up high. (90-100%)
I am not using Outlook. I haven't configured wine yet in this PC from where I am posting. :- ) Until then, Konqueror has to suffice. ;-)
Originally posted by Ekkume Topposting is my style. If I post, I want my post on top, not other peoples' posts. For this thread, for you. I will try to remember not to do it.
Sometimes people post the most dreadful stuff, which I don't
want people to have to wade through.
Then just reply. You don't have to quote the last message in a forum as it's always there, unless of course if you're replying to a post a couple of posts up, and then you would want to quote the pertinent pieces so everyone will know what you're talking about. Even then though, top posting is as much a "style" in the english language as dyslexia. You read a page top to bottom, not bottom to top.
Example:
Because top posting messes up the flow of reading.
How come?
I prefer to bottom-post.
What do you do instead?
No.
Do you like top-posting?
Quote:
Originally posted by Ekkume Mixer has been checked in the console. All the settings are up high. (90-100%)
Ekkume
You know, now that I think about it, I have a desktop machine with this same sound chip in it and it had exactly the same problem. I remember at the time I thought that it was just dead (I didn't have another OS to try on it at the time), but perhaps it's not after all.
It looks like we're not the only people who have seen this problem though
Distribution: Debian Sid, FreeBSD, Mandrake, Red Hat
Posts: 84
Original Poster
Rep:
Quote:
You know, now that I think about it, I have a desktop machine with this same sound chip in it and it had exactly the same problem. I remember at the time I thought that it was just dead (I didn't have another OS to try on it at the time), but perhaps it's not after all.
It looks like we're not the only people who have seen this problem though
I submitted a bug report to FreeBSD and gave a link to that previous bug report for the same sound chip. Hopefully a solution can easily be found.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.