Joey,
It's your decision.
If you remove the Conexant modem and replace it by any slmodemd
compatible modem, sl-modem-daemon will work.
You would not try to use a Ford engine on a Mercedes, right? Nor in the
reversed order use a Mercedes engine on a Ford?
Sure enough, one is free, the other not.
But the swap won't work.
A driver is made for a given hardware, not for any hardware.
The slmodemd driver could work if Conexant would make one of their
proprietary software (named Codec) available for free. But they do not
want to.
Sorry ...
Jacques
Joey Carter wrote:
Hello,
I'm getting no dialtone error after installing sl-modem-daemon. Tried
with both wvdial and kppp.
I think my modem is conexant so the driver from linuxant.com does
work, but very slow (free version, 14.4kbps). I would like to know
whether it is possible to make sl-modem-daemon work.
uname -a:
Linux x-presario 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007
i686 GNU/Linux
Using freshly installed Ubuntu 7.10 (gutsy) on Compaq Presario V2000 notebook.
I just downloaded the latest version of scanModem and here's the
output of ModemData.txt:
-------------------------------------------------------
Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.22-14-generic
With this Subject Line cogent experts will be alerted, and useful case
names left in the Archive.
YourCountry will enable Country specific guidance. Your contry's local
Linux experts
can be found through: http://www.linux.org/groups/index.html.
They will know your Country's modem code, which may be essential for
dialup service.
Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an
Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org
-------------------------- System information ----------------------------
CPU=i686,
Linux version 2.6.22-14-generic (buildd@palmer) (gcc version 4.1.3
20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14
23:05:12 GMT 2007
scanModem update of: 2008_02_25
The modem symbolic link is /dev/modem -> ttySHSF0
There are no blacklisted modem drivers in /etc/modprobe* files
The Advanced Linux Sound Architecture (ALSA) packages providing audio support,
also includes drivers for some modems. The ALSA diagnostics are written during
bootup to /proc/asound/ folders.
The /proc/asound/ audio+modem diagostics are being copied.
Finished copy to Modem/ALSAroot.tgz
The ALSA verion is 1.0.14
The modem cards detected by "aplay -l" are:
The /proc/asound/pcm file reports:
-----------------------
00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : playback 1
00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC : capture 1
00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : capture 1
00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4
Intel 82801DB-ICH4 with unknown codec at irq 17
USB modem not detected by lsusb
For candidate card in slot 00:1f.6, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1f.6 8086:24c6 103c:3080 Modem: Intel Corporation 82801DB/DBL/DBM
Modem interrupt assignment and sharing:
17: 195778 IO-APIC-fasteoi hsfmc97ich, Intel 82801DB-ICH4
--- Bootup diagnostics for card in PCI slot 00:1f.6 ----
[ 12.329541] ACPI: PCI Interrupt 0000:00:1f.6[B] -> GSI 17 (level,
low) -> IRQ 17
[ 12.329550] ACPI: PCI interrupt for device 0000:00:1f.6 disabled
[ 15.604000] ACPI: PCI Interrupt 0000:00:1f.6[B] -> GSI 17 (level,
low) -> IRQ 17
[ 16.604000] PCI: Setting latency timer of device 0000:00:1f.6 to 64
The PCI slot 00:1f.6 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
Predictive diagnostics for card in bus 00:1f.6:
Modem chipset detected on
CLASS="Class 0703: 8086:24c6"
NAME="Modem: Intel Corporation 82801DB/DBL/DBM "
PCIDEV=8086:24c6
SUBSYS=103c:3080
SUBven=103c
IRQ=17
IDENT=hsfmodem
CODECp=CXT
COD=CXT
SOFT=8086:24c6.MC97
For candidate modem in: 00:1f.6
Class 0703: 8086:24c6 Modem: Intel Corporation 82801DB/DBL/DBM
Primary PCI_id 8086:24c6
Subsystem PCI_id 103c:3080
Softmodem codec or chipset from diagnostics:
from Archives: CXT, a Conexant type using hsfmodem software.
CXT is a generic for all CXTnumbers, with Linuxant hsfmodem software support.
Lacking a dsp (digital signal processing) chip, the modem is a software
intensive or "softmodem" type. Its primary controller manages the traffic
with the CPU. But the software needed is specified in the Subsystem.
-----------------------------------------
Support type needed or chipset: hsfmodem
Writing Intel.txt
For owners of a Dell PCs with Conexant HSF modems, a driver source
package with full speed enabled is available, but requires driver
compiling. Read Conexant.txt
The hsfmodem package serves a great variety of Conexant chipset modems.
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem_hsfmodem_7.68.00.07full_k.deb.zip
with 2.6.22_14_generic equivalent to 2.6.22-14-generic, your kernel version.
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See Testing.txt for details.
Read Conexant.txt
Writing Conexant.txt
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.3
and the compiler used in kernel assembly: 4.1.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.1
linuc_headers base folder /lib/modules/2.6.22-14-generic/build
However some compilations and executable functions may need additional files,
in the FileNames.h (so called kernel "h"eaders) collection installed
in /usr/include/ .
For martian_modem, additional required packages are libc6-dev (and for
Debian/Ubuntu, linux-libc-dev). The also required headers of package
libc6 are commonly installed by default.
If a driver compilation fails, with message including some lack of
some FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include.
The minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev
If an alternate ethernet connection is available,
$ apt-get update
$ apt-get -s install linux-kernel-devel
will install needed package
For Debian/Ubuntu related distributions, run the following command to
display the needed package list:
Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb
Checking pppd properties:
-rwsr-xr-- 1 root dip 269256 2007-10-05 00:57 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html
To enable dialout without Root permission do:
$ su - root (not for Ubuntu)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
In case of a message like:
Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth1 ppp0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for the experts
should trouble shooting be necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link: lrwxrwxrwx 1 root root 8 2008-02-29 17:59
/dev/modem -> ttySHSF0
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"
Within /etc/modprobe.conf files:
/etc/modprobe.d/hsf:alias /dev/modem /dev/ttySHSF
/etc/modprobe.d/hsf.conflicts:install snd-via82xx-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97via
/etc/modprobe.d/hsf.conflicts:install snd-atiixp-modem /bin/true #
temporarily disabled by hsf - conflicts with hsfmc97ati
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to
blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
/etc/devfs/conf.d/hsf.conf:LOOKUP ^(ttySHSF[0-9]|modem$) EXECUTE nice
/sbin/modprobe /dev/ttySHSF
/etc/devfs/conf.d/hsf.conf:REGISTER ^ttySHSF0$ CFUNCTION GLOBAL
symlink $devname modem
/etc/devfs/conf.d/hsf.conf:UNREGISTER ^ttySHSF0$ CFUNCTION GLOBAL unlink modem
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
