From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000432]: Impossible de se connecter : NODIALTONE
Date: Fri, 27 Aug 2004 15:41:28 +0200 (CEST) [thread overview]
Message-ID: <20040827134128.67F282C008@server.perex-int.cz> (raw)
A BUGNOTE has been added to this bug.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000432
======================================================================
Reported By: Cyrille
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Bug ID: 432
Category: PCI - atiixp-modem
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: Slackware 10
Kernel Version: 2.4.24
======================================================================
Date Submitted: 08-08-2004 19:02 CEST
Last Modified: 08-27-2004 15:41 CEST
======================================================================
Summary: Impossible de se connecter : NODIALTONE
Description:
I've got a TOSHIBA SATELITTE A30 222 laptop
Sound card and modem are based upon ATI IXP
But I'm not able to run modem in spite of the differents bug-report on
ALSA web site
(https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000422
-
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000418
-
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000417
) and on Unixtrix.com (http://www.unixtrix.com/)
Even if I do like Ronis or Netstar say -bugtrack.alsa-project :
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000418
-, I'm always in the same situation : compilation is OK, modem driver OK
but I'm not able to connect : NODIALTONE
======================================================================
----------------------------------------------------------------------
sashak - 08-25-2004 19:11 CEST
----------------------------------------------------------------------
There is similar problem - some BIOSes doesn't report valid MODEM_PRESENT
bit in ATI_REG_CMD register (reg 003, bit 27 - look in
'/proc/asound/card1/atiixp'). Device behaviuor in this case is identical
to reported here - DMA works ok, line still be disconnected.
Uploaded patch solves the problem.
----------------------------------------------------------------------
netstar - 08-26-2004 01:18 CEST
----------------------------------------------------------------------
Additional problems with patch when applied to alsa CVS. All conditions
necessary are met.
----------------------------------------------------------------------
netstar - 08-26-2004 18:54 CEST
----------------------------------------------------------------------
Forget that, now working fine, congratulations.
----------------------------------------------------------------------
Cyrille - 08-26-2004 21:46 CEST
----------------------------------------------------------------------
Concretrely, does it mean the current version of alsa driver will not run
with this hardware ?
Thanx
----------------------------------------------------------------------
Cyrille - 08-26-2004 21:47 CEST
----------------------------------------------------------------------
Oups, I've got not see the last Netstar message...
I try to test it...
----------------------------------------------------------------------
Cyrille - 08-27-2004 15:41 CEST
----------------------------------------------------------------------
Hello
I have try Sashak's tip but the upload patch don't solve the problem.
Always the same error message : NODIALTONE.
(with alsa-driver/lib/... 1.0.6 ; test with slmodem-2.9.9 unless patch and
with Ronis's patch).
At your mind, is there really no hope to run it ?
Bug History
Date Modified Username Field Change
======================================================================
08-08-04 19:02 Cyrille New Bug
08-08-04 19:02 Cyrille Distribution => Slackware 10
08-08-04 19:02 Cyrille Kernel Version => 2.4.24
08-08-04 19:02 Cyrille Bug Monitored: Cyrille
08-25-04 19:04 sashak File Added: atiixp_modem.patch
08-25-04 19:11 sashak Bugnote Added: 0001624
08-26-04 01:16 netstar File Added: debugging.tar.gz
08-26-04 01:18 netstar Bugnote Added: 0001630
08-26-04 18:54 netstar Bugnote Added: 0001634
08-26-04 21:46 Cyrille Bugnote Added: 0001636
08-26-04 21:47 Cyrille Bugnote Added: 0001637
08-27-04 15:41 Cyrille Bugnote Added: 0001644
======================================================================
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next reply other threads:[~2004-08-27 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 13:41 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 18:40 [ALSA - driver 0000432]: Impossible de se connecter : NODIALTONE bugtrack
2005-01-14 21:17 bugtrack
2005-01-14 21:12 bugtrack
2004-08-28 20:37 bugtrack
2004-08-28 17:49 bugtrack
2004-08-28 11:49 bugtrack
2004-08-28 2:24 bugtrack
2004-08-27 17:33 bugtrack
2004-08-26 19:47 bugtrack
2004-08-26 19:46 bugtrack
2004-08-26 16:54 bugtrack
2004-08-25 23:18 bugtrack
2004-08-25 17:11 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=20040827134128.67F282C008@server.perex-int.cz \
--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.