Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Schuster <marco@harddisk.is-a-geek.org>
To: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org,
	Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Subject: Re: ALC268 (no sound)
Date: Tue, 05 Feb 2008 18:29:12 +0100	[thread overview]
Message-ID: <47A89CE8.3010902@harddisk.is-a-geek.org> (raw)
In-Reply-To: <s5hbq703lv4.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 1547 bytes --]

Takashi Iwai schrieb:
> At Fri, 1 Feb 2008 18:12:32 +1030 (CST),
> Jonathan Woithe wrote:
>> Hi Marco
>>
>>> maybe this topic is a bit outdated, but still, when using the current
>>> hg code of the kernel module together with 2.6.24 (stable), I can't
>>> get any sound :(
>> Interesting.  I've had another user report getting sound out of the latest
>> hg tree with an ALC268 both with test mode and the "auto" mode.  Our
>> continued failure to get anything out of your laptop over the last few
>> months makes me suspect that there's some other non-standard thing (external
>> to the ALC268 codec) linked to the sound system in your laptop which
>> prevents audio unless activated.  Takashi, what's your take on this?
> 
> Hard to say...  I still think it's either GPIO or EAPD except for very
> stupid things like the hardware-volume control via laptop keys
> (e.g. Thinkpad has independent volume controls and you have to unmute
> it via a button properly).  Marco, did you test all combinations of
> GPIO and EAPD?
Well, there are softkeys on the machine, but they don't have any
effect (for example the LED for mute doesn't change when pressing the
button). What's that stuff with GPIO/EAPD?
> 
> On other earlier ALC codecs, some device require COEF setups.  This
> might be worth to try for ALC268 if the above is all checked.
Another thing I don't understand :(

Marco

PS: If you want, I can upload the Windoze drivers somewhere so that
you can take a look at them and find out what is going on here...


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-02-05 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 21:05 ALC268 (no sound) Marco Schuster
2008-02-01  7:42 ` Jonathan Woithe
2008-02-01 12:24   ` Takashi Iwai
2008-02-05 17:29     ` Marco Schuster [this message]
2008-02-05 22:25       ` Jonathan Woithe
2008-02-05 22:42         ` Marco Schuster
2008-02-06  6:17           ` Jonathan Woithe
2008-02-06 11:06             ` Marco Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47A89CE8.3010902@harddisk.is-a-geek.org \
    --to=marco@harddisk.is-a-geek.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox