Re: smartlink alsa modem problem in 2.6.11

From: Alessandro Suardi (alessandro.suardi_at_gmail.com)
Date: 03/02/05

  • Next message: Kristian Sørensen: "Re: UserMode bug in 2.6.11-rc5? autolearn=disabled version=3.0.2"
    Date:	Wed, 2 Mar 2005 15:02:01 +0100
    To: Jaroslav Kysela <perex@suse.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")
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Kristian Sørensen: "Re: UserMode bug in 2.6.11-rc5? autolearn=disabled version=3.0.2"

    Relevant Pages

    • Re: AGP problem SiS 746FX Linux 2.6.5-rc3
      ... the Empire squashes the Federation like a bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.9bk6 msdos fs OOPS
      ... >This bug is triggered by race condition. ... Apparently my lashup doesn't trigger it. ... Copyright 2004 by Maurice Eugene Heskett, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [patch 0/3] j_state_lock, j_list_lock, remove-bitlocks
      ... BUG: Unable to handle kernel NULL pointer dereference at virtual address ... TAS_BUFFER_FNS(RevokeValid, revokevalid) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: BUG at mm/memory.c:1501 in 2.6.0-test5
      ... >Any module running inside the kernel can destroy anything. ... A simple bug in any ... You should send your report to the vendor. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: kernel BUG at page_alloc.c
      ... Marcelo Tosatti wrote: ... > Its the third or fourth report like this I see, ... CONFIG_GRKERNSEC_PAX_MPROTECT) and i don't remember seeing such BUG... ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)