ALSA Sound not Working Anymore
Hello. I had my sound system working fine but lost all sound after rebooting. I have an Audigy 2 ZS, running FC5. I think I was fine until I loaded Xine?? can't be sure. Kmix shows my sound card with PCM and all of the channels set properly, but I can't get alsamixer to run (I did before) Let me show what I have so far:
[root@localhost ~]# lsmod |grep '^snd' snd_intel8x0 32221 0 When i try to run alsamixer I get this: [root@localhost ~]# alsamixer alsamixer: function snd_ctl_open failed for default: No such device [root@localhost ~]# When I look at my modprobe config file I see this.. Not sure if it is ok? [root@localhost etc]# cat modprobe.confPlease help. This is driving me nuts? |
When my ALSA conked out lately I just re-ran alsaconf and got it back.
|
Thanks for the reply. I am a little shy of taking your advice because of the statement in a wiki webesite. Let me know what you think?
I was using the wiki web site shown below to help me out and was worried about the Never part mentioned below. Would this apply to me? I think it would since my sound card is in a PCI slot right? http://wiki.archlinux.org/index.php/Alsa All necessary modules should be detected and loaded automatically by udev. No special configuration has to be done unless you use ISA cards. NEVER use alsaconf if you have a PCI or ISAPNP sound card, the entries alsaconf adds to the modprobe.conf file might break udev's autodetection.Additional information: I get this message when I log in: Sound server informational message:Something interesting that I noticed is that my reciever shows the PCM connection which it never has before if the sound card is not working before? Which says that my stereo thinks it is seeing a pcm connection? :cry: Gray |
I really don't know. I have an onboard sound chip on my notebook, which makes it a device on the PCI-bus. Alsaconf didn't break my hotplugging system or anything. I noticed that the wiki mentions support for OSS and ISA-Soundcards... that makes me wonder how up-to-date it really is.
I would give alsaconf a try. You could backup your modprobe.conf / modules.conf if you're really worried. And maybe your /dev directory. But hey, this is just what I would do. Maybe that isn't the good solution at all. My sound configuration isn't as complex as yours. Code:
lsmod | grep snd Ps: My soundcard doesn't do everything I want either: link |
Actually I could make copies like you said and see what happens. I am just wondering what happened and of course I want my sound back. Somewhere I changed a config file or something? not sure how or when. I was using a FC5 set up guide to set up my system and all was good until I rebooted.. then Nada, nothing, kaput! < check spelling. Aaaghh this is a pain. Anyone else have any suggestions?
|
Everytime my sound screws it turned out to be bad mixer settings. Just a suggestion
|
Re: Alsa not working
I am using the Alsasound built into the kernel ... whenever I rebuild the kernel I need to run alsaconf.
I have never had a problem with this. I have a maestro 3 pci sound card. |
Ok, what am i doing wrong here?
[root@localhost /]# alsaconf -bash: alsaconf: command not found |
Re: Alsa not working
Quote:
|
Quote:
Quote:
Now for the good news. I was doing a yumex update(rpm update) and ran into a dependency problem with bind-9.3.2-33.fc5. In tying to fix it and I accidently removed the bind rpm which apparently removed/disconnected loads of other applications (can't tell which because they all flashed by my screen as being removed). Crap.. Crap.. crap LOL. As a result, none of my repositories worked and infact, I didn't have and internet connection anymore...just great!!! I did a rescue login with my FC5 DVD and got my internet connection again, reinstalled bind, rebooted and checked my rpms again! (sorry I don't mean to be wordy) my update check showed that alsamixergui-0.9.0-0.3.rc1.fc5 was missing (I had it before). So I loaded it up. rebooted and now I have sound. Here it is Now: [root@localhost ~]# rpm -q alsa-utilQuestion: I would like to back up config files, save listing, modprobe or what-ever I can save/backup. Any suggestions? From what I have just posed does anyone know or think they know what happened to fix my sound? |
This is a reply posting for anyone that has followed this thread. I resolved my issue and I think I conclusively, absolutely, resolved my issue this time:)
Let me state that I have read just about every ALSA article regarding possible absolutely problems and help suggestions out there. In reading all of them and performing many different corrective tasks, I got a little wiser and started seeing patterns. Every suggestion worked; however, only temporary which begged the question why would my simple computer configuration with the same distro and hardware be so different from the rest of the world that my sound card is detected, not detected, detected.. and so forth. I finally came to believe/realized that since I was doing everything correctly at the software end so it must be something else.. and it was! For the rest of you :newbie:s like me: CHECK YOUR BIOS sound card detection settings!!!! My Asus card bios setting for sound card detection was set to AUTO<<< NOT GOOD!! Or at least for me. After turning OFF the onboard sound card detection all of my detection toggling went bye bye. Now I am all good, there doesn't seem to be any conflict and my Audigy sound card is detected consistently at log in. I sincerely hope no one else has to go through 6 months of sound card detection toggling. Legolas |
I'd suggest first checking to see if the mixer settings are correct by running alsamixer. Make sure nothing is muted and nothing is turned down, then try. If that is the case, then store your settings so this does not happen again after you reboot. To store the settings, run alsactl store as root.
Good luck |
Quote:
I have exactly the same problem as you have and even the same sound card. I also turned off the onboard sound card detection and my sound worked... for two days. now I have the problem back, the card is not always detected. I really think it's a alsa bug with this hardware. |
All times are GMT -5. The time now is 06:04 AM. |