From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001733]: Intel HDA Modem ?
Date: Thu, 16 Mar 2006 19:44:55 +0100 [thread overview]
Message-ID: <9ccaa1519c438f9a203495bcb714fa3f@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1733>
======================================================================
Reported By: chrmue
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1733
Category: PCI - hda-intel
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: SuSE Linux 10.0
Kernel Version: 2.6.13-15
======================================================================
Date Submitted: 01-11-2006 07:23 CET
Last Modified: 03-16-2006 19:44 CET
======================================================================
Summary: Intel HDA Modem ?
Description:
I want to use my HDA Softmodem in Linux, is there any development on a HDA
Modem Module ?
cat /proc/asound/card0/codec#1 gives me:
Codec: Generic 11c1 ID 3026
Address: 1
Vendor Id: 0x11c13026
Subsystem Id: 0x11c13026
Revision Id: 0x70500
In Windows it is called "Agere Systems HDA Modem" (Conexant ?)
If there is development on this i would like to participate to get it
going, because i dont't want to have a windows-installation on my Notebook
(Acer TravelMate 8104) just for getting my mails at my parents house,
where there is only analog telephone.
======================================================================
----------------------------------------------------------------------
sashak - 03-16-06 02:17
----------------------------------------------------------------------
slmodem-2.9.10 is old, it does not do off-hook. Use slmodem-2.9.11-20051101
from http://linmodmes.technion.ac.il/packages/smartlink .
About wvdial. I know that such problem was reported and reason was that
this fails after unsuccessful serial port specific ioctl()s.
What is the difference between wvdial-1.54.0 and wvdial-1.54.0 - I don't
know (configure parameters?) and actually never seen such problem
personally (my wvdial-1.54.0 was ok when I've used it last time). Try to
debug with gdb, this should not be too complicated problem.
----------------------------------------------------------------------
kratz00 - 03-16-06 19:44
----------------------------------------------------------------------
i tried slmodem-2.9.11-20051101 but still the same if i have a little more
time i will have a close look at this but maybe somebody has an idea what
could be wrong in the mean time
Issue History
Date Modified Username Field Change
======================================================================
01-11-06 07:23 chrmue New Issue
01-11-06 07:23 chrmue Distribution => SuSE Linux 10.0
01-11-06 07:23 chrmue Kernel Version => 2.6.13-15
01-11-06 07:42 rlrevell Note Added: 0007559
01-11-06 23:32 sashak File Added: hda-modem-si3054-11c13026.patch
01-11-06 23:35 sashak Note Added: 0007571
01-12-06 00:00 sashak Note Added: 0007574
01-12-06 00:02 sashak Issue Monitored: sashak
01-12-06 05:35 chrmue Note Added: 0007581
01-13-06 00:16 sashak Note Added: 0007598
01-16-06 20:19 chrmue Note Added: 0007692
01-16-06 20:22 chrmue Issue Monitored: chrmue
03-03-06 15:43 lrupn Note Added: 0008341
03-03-06 15:44 lrupn Issue Monitored: lrupn
03-10-06 23:44 kratz00 Note Added: 0008413
03-11-06 15:19 kratz00 Note Added: 0008416
03-11-06 19:03 rlrevell Note Added: 0008421
03-11-06 19:23 kratz00 Note Added: 0008423
03-11-06 19:33 rlrevell Note Added: 0008424
03-11-06 23:08 sashak Note Added: 0008427
03-12-06 11:22 kratz00 Note Added: 0008431
03-15-06 00:42 chrmue Note Added: 0008525
03-15-06 11:35 tiwai Note Added: 0008530
03-15-06 21:42 kratz00 Note Added: 0008573
03-15-06 21:42 kratz00 Issue Monitored: kratz00
03-16-06 02:17 sashak Note Added: 0008581
03-16-06 19:44 kratz00 Note Added: 0008619
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-16 18:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 18:44 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-22 23:12 [ALSA - driver 0001733]: Intel HDA Modem ? bugtrack
2006-04-22 23:06 bugtrack
2006-04-22 23:04 bugtrack
2006-03-16 1:17 bugtrack
2006-03-15 20:42 bugtrack
2006-03-15 10:35 bugtrack
2006-03-14 23:42 bugtrack
2006-03-12 10:22 bugtrack
2006-03-11 22:08 bugtrack
2006-03-11 18:33 bugtrack
2006-03-11 18:23 bugtrack
2006-03-11 18:03 bugtrack
2006-03-11 14:20 bugtrack
2006-03-10 22:44 bugtrack
2006-03-03 14:43 bugtrack
2006-01-16 19:19 bugtrack
2006-01-12 23:16 bugtrack
2006-01-12 4:35 bugtrack
2006-01-11 23:00 bugtrack
2006-01-11 22:35 bugtrack
2006-01-11 6:42 bugtrack
2006-01-11 6:23 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=9ccaa1519c438f9a203495bcb714fa3f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox