From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000890]: no dialtone with modem & strange log "semaphore is not ready [0x1][0x701300]"
Date: Wed, 2 Mar 2005 15:15:03 +0100 [thread overview]
Message-ID: <a486be8201cc26b7b7a25fb75bdaaaa9@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=890>
======================================================================
Reported By: hothead
Assigned To: sashak
======================================================================
Project: ALSA - driver
Issue ID: 890
Category: PCI - intel8x0m
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution:
Kernel Version: 2.6.9
======================================================================
Date Submitted: 02-08-2005 14:33 CET
Last Modified: 03-02-2005 15:15 CET
======================================================================
Summary: no dialtone with modem & strange log "semaphore is
not ready [0x1][0x701300]"
Description:
Hi,
I want to tell you that snd-intel8x0m works with the
ag&https://bugtrack.alsa-project.org/alsa-bug/view.php?id=232;re modem on
my
thinkpad t41p. The problem is that I can not get the dialtone working.
Do you have any suggestion concerning this problem?
# System Information
# ***********************
System uname: 2.6.9-thinkpad-r1 i686 Intel(R) Pentium(R) M processor
1700MHz
Gentoo Base System version 1.6.9
Python: dev-lang/python-2.3.4 [2.3.4
(https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1, Dec 30 2004,
09:19:20)]
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[enabled]
dev-lang/python: 2.3.4
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.7.9-r1, 1.8.5-r3, 1.6.3, 1.9.4, 1.5
sys-devel/binutils: 2.15.92.0.2-r1
sys-devel/libtool: 1.5.10-r4
virtual/os-headers: 2.6.8.1-r2
# Furthermore I get curious messages from the driver:
# *********************************************************
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:401:
codec_semaphore: semaphore is not ready [0x1][0x701300]
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:415:
codec_write 1: semaphore is not ready for register 0x54
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:401:
codec_semaphore: semaphore is not ready [0x1][0x701300]
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:415:
codec_write 1: semaphore is not ready for register 0x54
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:401:
codec_semaphore: semaphore is not ready [0x1][0x701300]
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:415:
codec_write 1: semaphore is not ready for register 0x54
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:401:
codec_semaphore: semaphore is not ready [0x1][0x701300]
ALSA
/var/tmp/portage/alsa-driver-1.0.8/work/alsa-driver-1.0.8/pci/../alsa-kernel/pci/intel8x0m.c:415:
codec_write 1: semaphore is not ready for register 0x54
It would be great if you could help me!
Regards
Ruben Jenster
======================================================================
----------------------------------------------------------------------
perex - 03-02-05 14:12
----------------------------------------------------------------------
Have you tried to load "snd-intel8x0" and "snd-intel8x0m" modules in
opposite order?
----------------------------------------------------------------------
perex - 03-02-05 15:15
----------------------------------------------------------------------
Alessandro Suardi <alessandro.suardi at gmail.com> wrote at linux-kernel
mailing list (so that it might be also incompatible codec):
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.
Issue History
Date Modified Username Field Change
======================================================================
02-08-05 14:33 hothead New Issue
02-08-05 14:33 hothead Kernel Version => 2.6.9
03-02-05 14:12 perex Note Added: 0003772
03-02-05 15:15 perex Note Added: 0003778
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-02 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 14:15 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 10:39 [ALSA - driver 0000890]: no dialtone with modem & strange log "semaphore is not ready [0x1][0x701300]" bugtrack
2005-03-03 2:13 bugtrack
2005-03-02 14:19 bugtrack
2005-03-02 14:19 bugtrack
2005-03-02 14:17 bugtrack
2005-03-02 13:12 bugtrack
2005-02-08 13:33 bugtrack
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=a486be8201cc26b7b7a25fb75bdaaaa9@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.