[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: M4A88TD-V EVO/USB3 Realtek ALC892 - No sound(mostly)



On Fri, 03 Jun 2011 21:42:30 +1000, David Kinyua wrote:

> On 17/05/11 03:35, Camaleón wrote:

(...)

>> Anyway, you can try with "alsa reload", instead.
>>
>>
> Sorry to have hijacked this thread days later, but I basically have the
> same issue and I can't work where I messed my sound up. I tried
> reinstalling alsa-base but no sound.

Does your sound card have the same chipset we were talking about (ALC892)?
 
> I've got one of the SB EMU10K1X driver which just stopped working when I
> upgraded my system to wheezy. I'm not sure what more information I need
> to provide but when I do alsa reload I get this warning ;

> Unloading ALSA sound driver modules: snd-seq-oss snd-seq-midi
> snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device
> (failed: modules still loaded: snd-seq-midi snd-rawmidi
> snd-seq-midi-event snd-seq snd-timer snd-seq-device). 

> Loading ALSA sound driver modules: snd-seq-oss snd-seq-midi snd-rawmidi
> snd-seq-midi-event snd-seq snd-timer snd-seq-device

I thinks those messages are normal, just warnings but nothing serious.

> WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be 
> ignored in a future release. 
> WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it
> will be ignored in a future release.

(...)

And these are just warnings, too.

> I changed the sound file in /etc/modprobe.d to sound.conf. That file has
> got this;
> alias snd-card-0 snd-emu10k1
> alias sound-slot-0 snd-emu10k1

Just in case, check this page:

http://wiki.debian.org/snd-emu10k1

> I'm on kernel 2.6.38. Would this be an issue? I'm not too sure what I
> might have messed with but I desperately tried fixing this but I'm not
> sure if I didn't cause the damage myself as I am on a tight time
> constraint and just need my sound back.
> 
> I've also tried the Real-linux-audiopack-5.16 option suggested at
> http://wiki.debian.org/ALSA but to no luck.
> 
> Any ideas? Thanks in advance.

Look at the "/var/log/syslog" file, maybe there is something there :-?

Greetings,

-- 
Camaleón


Reply to: