[alsa-devel] model needed for Clevo P150HM (Realtek ALC892)

Julian Sikorski belegdol at gmail.com
Mon Jul 4 22:47:03 CEST 2011

W dniu 02.07.2011 00:37, Julian Sikorski pisze:
> W dniu 2011-07-02 00:09, Julian Sikorski pisze:
>> W dniu 01.07.2011 09:14, Takashi Iwai pisze:
>>> At Fri, 01 Jul 2011 09:07:47 +0200,
>>> Julian Sikorski wrote:
>>>>>>>>> So it seems that the only things remaining are the SPDIF/rear
>>>>>>>>> channel
>>>>>>>>> jack and the coupled muting issue.
>>>>>>>> It's a BIOS bug.  It doesn't tell SPDIF is available.
>>>>>>>> Ditto for the 4th stereo out.  No pin is exposed by BIOS.
>>>>>>> I see. I can try updating the BIOS and see if it changes
>>>>>>> anything. If it
>>>>>>> doesn't, is there a way to work the problem around in the driver?
>>>>>> You need to figure out pins manually by yourself, then change the
>>>>>> driver code.  I leave it as a homework :)
>>>>> :) I cannot write code, so I would not count on myself doing that. I
>>>>> will have a look into updating the BIOS though.
>>>>>> thanks,
>>>>>> Takashi
>>>>> Once again thanks for all the work you have done,
>>>>> Julian
>>>> Hmm, I googled a bit and it seems the way to find the pins is to write
>>>> values to user_pin_configs. So no coding knowledge seems needed, could
>>>> you give me some pointers on where to start?
>>> First off, read the HD-audio specification to understand what the values
>>> represent.  Then, use hda-analyzer or manually via hda-verb, figure out
>>> which widget corresponds to which I/O jack.  Compose the corresponding
>>> pin-config value, and put it to the sysfs file.  A brief description
>>> is found in Documentation/sound/alsa/HD-Audio.txt.
>>> Takashi
>> I have been scratching my head for almost 2 h now without much progress.
>> Can I steal this values from Windows driver somehow? It seems to be
>> possible:
>> http://www.insanelymac.com/forum/index.php?s=3298551705d0d48ba8faa28b9a7d3283&showtopic=137188&st=20
>> Julian
> I managed to get the data out of Windows install, does it look useful?
> Julian
I managed to figure out which ini file is used for my device, I am
attaching both the 32- and 64-bit versions. Hopefully there is some
useful info inside.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: thx2.tar.xz
Type: application/x-xz
Size: 19968 bytes
Desc: not available
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20110704/f41a642c/attachment-0001.bin 

More information about the Alsa-devel mailing list