Takashi Iwai <[email protected]> writes:
> At Tue, 28 Feb 2006 05:51:26 -0300,
> Otavio Salvador wrote:
>>
>> > This kind of problem is likely due to a broken BIOS. The current code
>> > parses the default pin configuration set up via BIOS while the older
>> > version used the fixed pin assignment (depending on the codec chip,
>> > though).
>> > In most cases, it can be recovered by specifying a proper model module
>> > option. See ALSA-Configuration.txt for details.
>>
>> I wasn't able to do it.
>
> Didn't it worked? Which module parameter did you use?
I tried model=hp, model=fujistsu and priority_fix={1,2}. Neither did
it work.
>> I hope it helps.
>
> I need more detail of the hardware -- what model of a laptop or a
> desktop from which vendor.
http://www.ctlnotebooks.com/v2/notebook_spec.aspx?id=21&hdr=Products
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [email protected] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
you the whole house."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
