if it works on guest
logout and back inCode:rm -rf ~/.pulse
if it works on guest
logout and back inCode:rm -rf ~/.pulse
Laptop: ASUS A54C-NB91 (Storage: WD3200BEKT + MKNSSDCR60GB-DX); Desktop: Custom Build - Images included; rPi Server
Putting your Networked Printer's scanner software to shame PHP Scanner Server
I frequently edit my post when I have the last post
Well, I really didn't expect we need to handle so much audio stack details to fix our sound and I'm totally layman. Well from what I learned and practiced, I think if in the similar situation of mine, we just need to find a matched vendor model option for our audio codec chip.
You can get your ACC type from
and go to the corresponding section ofCode:aplay -l
http://www.kernel.org/doc/Documentat...dio-Models.txt
and try each model option and restart. Hope you have that luck.
Just FYR
"What `model` option values are available depends on the codec chip. Check your codec chip from the codec proc file (see "Codec Proc-File" section below). It will show the vendor/product name of your codec chip. Then, see Documentation/sound/alsa/HD-Audio-Models.txt file, the section of HD-audio driver. You can find a list of codecs and `model` options belonging to each codec. For example, for Realtek ALC262 codec chip, pass `model=ultra` for devices that are compatible with Samsung Q1 Ultra. Thus, the first thing you can do for any brand-new, unsupported and non-working HD-audio hardware is to check HD-audio codec and several different `model` option values. If you have any luck, some of them might suit with your device well."from http://www.kernel.org/doc/Documentat...a/HD-Audio.txt
Sweet! I've just received my free Riot Points!
>> FreeRiotPoints.me <<
Bookmarks