public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "\"Alejandro A. Valdés\"" <av2406@gmail.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: "Jon Arne Jørgensen" <jonarne@jonarne.no>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: Audio: no sound
Date: Wed, 05 Jun 2013 22:37:32 -0300	[thread overview]
Message-ID: <51AFE7DC.9040801@gmail.com> (raw)
In-Reply-To: <CALF0-+XS0urZ=G=jCLgKifs6NeC=rNqZB_ft2PXpcEVezuG=rw@mail.gmail.com>

On 05/30/2013 05:13 AM, Ezequiel Garcia wrote:
> Hi Alejandro,
>
> See below.
>
> On Sat, May 25, 2013 at 4:00 AM, Jon Arne Jørgensen <jonarne@jonarne.no> wrote:
>> On Thu, May 23, 2013 at 09:48:38PM -0300, "Alejandro A. Valdés" wrote:
> [...]
>>> [  187.472216] easycap::0adjust_contrast: adjusting contrast to  0x3F
>>> [  187.496207] easycap::0adjust_saturation: adjusting saturation to  0x2F
>>> [  187.520220] easycap::0adjust_hue: adjusting hue to  0x00
> Kernel dmesg should say stk1160.
>
>> [...]
>>
>>> Module                  Size  Used by
> [...]
>>> easycap              1213860  1
> As Jon says lsmod and dmesg should say stk1160, and not easycap.
> It's my bad: the first kernel version that includes stk1160 instead of the
> old driver is v3.7.x.
>
> You'll have to re-try with a newer kernel.
>
> Notice that you probably own a device with no AC97-compliant
> audio output. For those devices, the sound does not work.
> It's on my TODO list, but I'm not sure when I will be able to do it.
>
> AFAIK, some devices have AC97 sound (and thus work), and some doesn't.
>
> Sorry for the confusion,
Well, upgraded to kernel 3.7, but with the same results: no audio. Now 
the lsmod output shows the stk1160 driver loaded instead of the former 
EasyCAP, so that one got solved. Not quite sure about ac97 compliance, 
but I already tested with 5 or 6 different machines, all of them running 
the kernel 3.7 or up, and all of them also showing the ac97 bus being 
used by the ac97 codec (from lsmod output too), and none did work so far.

Little bit frustrating. May be time now to toss the damn dongle away and 
start looking for linux certified hardware.

Thanks anyway. Alex.

  reply	other threads:[~2013-06-06  1:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23  1:12 Audio: no sound "Alejandro A. Valdés"
2013-05-23 10:48 ` Ezequiel Garcia
2013-05-23 16:19   ` "Alejandro A. Valdés"
2013-05-23 16:22     ` Ezequiel Garcia
     [not found]       ` <519E6046.8050509@gmail.com>
2013-05-23 19:12         ` Ezequiel Garcia
2013-05-23 20:07           ` "Alejandro A. Valdés"
2013-05-24  0:48             ` "Alejandro A. Valdés"
2013-05-25  7:00               ` Jon Arne Jørgensen
2013-05-30  8:13                 ` Ezequiel Garcia
2013-06-06  1:37                   ` "Alejandro A. Valdés" [this message]
     [not found]                     ` <CALF0-+Use=xFe5XmoDMCTCw-CM11FZXTGoOnYwRSS9OL7Dk7Aw@mail.gmail.com>
     [not found]                       ` <51B076A2.9000903@gmail.com>
2013-06-07 12:14                         ` Ezequiel Garcia
2013-06-10 23:27                           ` "Alejandro A. Valdés"
2013-06-11 23:04                             ` Ezequiel Garcia

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=51AFE7DC.9040801@gmail.com \
    --to=av2406@gmail.com \
    --cc=elezegarcia@gmail.com \
    --cc=jonarne@jonarne.no \
    --cc=linux-media@vger.kernel.org \
    /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