public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Michal Semler <cijoml@volny.cz>, linux-kernel@vger.kernel.org
Subject: Re: smartlink alsa modem problem in 2.6.11
Date: Wed, 2 Mar 2005 15:02:01 +0100	[thread overview]
Message-ID: <5a4c581d0503020602130fc630@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0503021358290.1745@pnote.perex-int.cz>

On Wed, 2 Mar 2005 14:01:41 +0100 (CET), Jaroslav Kysela <perex@suse.cz> wrote:
> On Wed, 2 Mar 2005, Michal Semler wrote:
> 
> > Hi,
> >
> > I tried use snd_intel8x0m  with smartlink modem, but without success:
> 
> > Mar  2 13:49:37 notas kernel: codec_semaphore: semaphore is not ready [0x1][0x701300]
> > Mar  2 13:49:37 notas kernel: codec_write 1: semaphore is not ready for
> 
> It's known bug:
> 
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=890
> 
> Have you tried to load "snd-intel8x0m and snd-intel8x0" modules in
> opposite order? Anyway, further discussion should go to this bug
> report...

slmodemd over snd-intel8x0m worked for me last week on 2.6.11-rc4-bk10:

Feb 24 23:19:07 incident chat[2554]: send (ATX3M0^M)
Feb 24 23:19:07 incident chat[2554]: timeout set to 120 seconds
Feb 24 23:19:07 incident chat[2554]: expect (OK)
Feb 24 23:19:07 incident chat[2554]: ^M
Feb 24 23:19:07 incident chat[2554]: ATX3M0^M^M
Feb 24 23:19:07 incident chat[2554]: OK
Feb 24 23:19:07 incident chat[2554]:  -- got it
Feb 24 23:19:07 incident chat[2554]: send (ATDT0,,xxxxxx^M)
Feb 24 23:19:07 incident chat[2554]: expect (CONNECT)
Feb 24 23:19:07 incident chat[2554]: ^M
Feb 24 23:19:07 incident chat[2554]: ATDT0,,xxxxxx^M^M
Feb 24 23:19:07 incident kernel: ALSA sound/pci/intel8x0m.c:401:
codec_semaphore: semaphore is not ready [0x1][0x301300]
Feb 24 23:19:07 incident kernel: ALSA sound/pci/intel8x0m.c:415: codec_write 1:
semaphore is not ready for register 0x54
Feb 24 23:19:52 incident chat[2554]: CONNECT
Feb 24 23:19:52 incident chat[2554]:  -- got it
Feb 24 23:19:52 incident chat[2554]: send (^M)
Feb 24 23:19:52 incident chat[2554]: expect (ogin:)
Feb 24 23:19:52 incident chat[2554]:  28800^M
Feb 24 23:19:58 incident chat[2554]: ^M

[snipped rest of log]

That is - I do get the codec_semaphore messages (though the error code
 is slightly different), but the modem connection works fine.

I have snd-intel8x0m modular while snd-intel8x0 is in-kernel.

--alessandro

  "There is no distance that I don't see
  I do have a will - No limit to my reach"
  
    (Wallflowers, "Empire In My Mind")

      reply	other threads:[~2005-03-02 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 12:54 smartlink alsa modem problem in 2.6.11 Michal Semler
2005-03-02 13:01 ` Jaroslav Kysela
2005-03-02 14:02   ` Alessandro Suardi [this message]

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=5a4c581d0503020602130fc630@mail.gmail.com \
    --to=alessandro.suardi@gmail.com \
    --cc=cijoml@volny.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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