i am a new user to linux ubuntu (ultimate edition ) i want to have a
internet connection through dialup modem(56K) ..once i had mailed to linux
user group but i couldn't get satisfactory result ..group gave me PGP codes
but i dont know how to use them ..when i scanned modem then i got some files
which i have attached with it..please help me to connect to internet by
giving step by step instruction ..
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Linux Users Group.
To post a message, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit our group at
http://groups.google.com/group/linuxusersgroup
-~----------~----~----~----~------~----~------~--~---
Only plain text email is forwarded by the [email protected] List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 2.6.24-16-generic
With this Subject Line cogent experts will be alerted, and useful case names
left in the Archive.
YourCountry will enable Country specific guidance. Linux experts in
YourCountry
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 [email protected] 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.24-16-generic (bui...@palmer) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008
scanModem update of: 2009_01_19
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to [email protected]
For candidate card in slot 04:03.0, firmware information and bootup diagnostics
are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
04:03.0 14f1:2f00 122d:8d86 Communication controller:
Conexant HSF 56k HSFi Modem
Modem interrupt assignment and sharing:
===================================
The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not functional!!
The CPU cannot control the modem until this situation is corrected!!
Possible corrections are:
1) Within the boot up BIOS, change from a Windows to a non-PNP/Other
Operating System type.
Instructions for accessing BIOS are at:
http://linmodems.technion.ac.il/resources.html within: Additional
Resourcces.
2a) Add an option "pci=routeirq" to the kernel boot up line.
Here is an example paragraph from /boot/grub/menu.lst :
title Ubuntu, kernel 2.6.15-26-686
root (hd0,6)
kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro
pci=routeirq
initrd /boot/initrd.img-2.6.15-26-686
savedefault
2b) Same as above, but use "pollirq" instead of "pci=routeirq".
3) Within some BIOS setups, IRQ assignments can be changed.
4) On non-laptop systems, moving the modem card to another slot has helped.
5) Sometimes upgrading the kernel changes IRQ assignment.
=====================================
--- Bootup diagnostics for card in PCI slot 04:03.0 ----
For candidate card in slot 80:01.0, firmware information and bootup diagnostics
are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
80:01.0 1106:3288 1043:81b3 Audio device: VIA Technologies,
Inc. VIA High Definition Audio Controller
Modem interrupt assignment and sharing:
23: 32796 0 IO-APIC-fasteoi HDA Intel
--- Bootup diagnostics for card in PCI slot 80:01.0 ----
[ 49.567930] ACPI: PCI Interrupt 0000:80:01.0[A] -> GSI 17 (level, low) ->
IRQ 23
[ 49.567964] PCI: Setting latency timer of device 0000:80:01.0 to 64
===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.
The ALSA verion is 1.0.16
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-01: AD198x Digital : AD198x Digital : playback 1
00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx
HDA VIA VT82xx at 0xcfffc000 irq 23
PCI slot 80:01.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.24-16-generic/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko
UNEXPECTED HDA diagnostic outcome.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 04:03.0:
Modem chipset detected on
NAME="Communication controller: Conexant HSF 56k HSFi Modem "
CLASS=0780
PCIDEV=14f1:2f00
SUBSYS=122d:8d86
IRQ=255
IDENT=hsfmodem
Driver=hsfmodem-drivers
For candidate modem in: 04:03.0
0780 Communication controller: Conexant HSF 56k HSFi Modem
Primary device ID: 14f1:2f00
Support type needed or chipset: hsfmodem
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
DOCs/Conexant.txt
Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the
hsfmodem package matching your System. For several Linux distros, there are
precompiled drivers matched to specific kernels. These have within the FileName,
your KernelVersion: 2.6.24_16_generic
They can be found through
http://www.linuxant.com/drivers/hsf/full/downloads.php
A more precise location may be given a few paragraphs below.
If an EXACT Match with your your KernelVersion is not found, one of the
"Generic packages with source" near the bottom of the page must be used.
Downloaded packages must be moved into the Linux partition (home folder is OK)
and unzipped with:
unzip hsf*.zip
The installation command for a .deb suffic packages is, with root/adm
permission:
sudo dpkg -i hsf*.deb
while for .rpm suffix it is, with:
rpm -i hsf*.rpm
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.80.02.01full_k2.6.24_16_generic_ubuntu_i386.deb.zip
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 DOCs/Testing.txt for details.
Read DOCs/Conexant.txt
Writing DOCs/Conexant.txt
Predictive diagnostics for card in bus 80:01.0:
Modem chipset not detected on
NAME="Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller
"
CLASS=0403
PCIDEV=1106:3288
SUBSYS=1043:81b3
IRQ=23
HDA=1106:3288
SOFT=1106:3288.HDA
High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
and many are supported by the ALSA audio+modem driver snd-hda-intel
A modem was not detected on HDA card 1106:3288.
If another modem card is present, then most likely 1106:3288 does not host a
modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 1106:3288, as Conexant chips
are frequently not detectable by ALSA diagnostics
2) The modem may be of the older non-PCI Controller Chipset (hardware)
type.
Try detection with Root permission:
sudo wvdialconf /etc/wvdial.conf
For candidate modem in: 80:01.0
0403 Audio device: VIA Technologies, Inc. VIA High Definition Audio
Controller
Primary device ID: 1106:3288
Subsystem PCI_id 1043:81b3
Softmodem codec or chipset from diagnostics:
from Archives:
Support type needed or chipset:
Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.
2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.2.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.2.3
and the compiler used in kernel assembly: 4.2.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.2
linuc_headers base folder /lib/modules/2.6.24-16-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 needed. The also required
headers of package libc6 are commonly installed by default.
Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev packages,
for kernels 2.6.24 and later versions.
In not included on your install CD, search for them at
http://packages.ubuntu.com
or comparable Repository for other Linux distros.
When compiling ALSA drivers, the utility "patch" will also be needed.
Compressed files at: /usr/src/kqemu.tar.bz2 /usr/src/lzma.tar.bz2
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 packages.
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-x 1 root dip 269256 2007-10-05 01:42 /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/DOCs/YourSystem.txt concerning other COMM channels: eth0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be
necessary.
==========================================================
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/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
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
If you want help from the email group [email protected], PLEASE join the
List
at http://www.linmodems.org . Otherwise your messages will be delayed until the
evening,
waiting for someone to verify it is not junk mail, before forwarding through
the List server.
The files in this Modem/ folder have the following roles:
ModemData.txt - Diagnostics and accumulated information cogent to your modem
and host system.
This is the ONLY file which should be sent to the List
[email protected] ,
if further help is needed. Send your email and attachments as plain text
as
other formats are rejected by the List Server, to avoid virus transmission.
Always send the ENTIRE ModemData.txt, as It includes subtle diagnostic
ouputs needed
to best guide you. Please in the covering email mention your Country, to
enable Country
specific advice.
Always use the most recent update of scanModem accessed ONLY at
http://linmodems.technion.ac.il/packages/scanModem.gz
to produce ModemData.txt
URLs to cogent advice are regularly updated, so your problem may be solved
therein.
Please Do NOT send Do NOT send other files in this folder Modem/
Several informative files without diagnostics are in the DOCs subfolder.
A file(s) specific to your modem chipset will be written, such as:
Smartlink.txt, Conexant.txt, Intel.txt , etc
YourModem.txt - Guidance about operating your particular System, for your
benefit
It should NOT be sent to [email protected]
Rational.txt - Motivations of this scanModem package.
DriverCompiling.txt - Explains the roles of additional files which may have to
be installed
to support compiling of modem drivers, and the steps to take.
SoftModem.txt - Information and instructions about "soft modems".
For these modems, additional steps may be necessary for choice of
supporting software.
The primary PCI ID is that of the host audio or modem controller, which
can support diverse Subsystems. It is the chipset of the Subsystem which
determines the software needed.
ModemTesting.txt SHOULD be read, but after drivers have been installed.
InfoGeneral.txt has general information about the status of winmodem support
under Linux,
Do read it if ModemData.txt reports that your current modem is not
supported under Linux.
Unsubscribe.txt - Howto terminate email tranmissions from the List.
If you are Linux newcomer, please do locate your local Linux group through:
http://www.linux.org/groups/index.html . If you are not comfortable with
English,
a local Linux user can often be of substantial assistance in getting you on
to the Internet.
Do NOT send this text with common information to [email protected]
There are instructions to UNSUBSCRIBE from [email protected] at
http://www.linmodems.org
==============
Several sections are included in this file:
The Summary of modem Support under Linux
description of the soft modem identity tests: SIL ids
some output from scanModem specific to your System
an explanation of the GCC 2.95 compiler warning
ethernet Interference with DNS (domain name service)
Please Linux Newbies read carefully, the companion
Modem/DOCs/DriverCompiling.txt and its
Followup Modem/DOCs/DriverTesting.txt section with dialout examples.
It is the CHIPSET, and Not the modem BrandName which is informative for Linux
support
The chipset types that are fully supported under Linux, without proprietary
drivers,
have the more expersive controller chipsets. These include the 3COM,Inc 3CXM556
and
AgereSystems FM560LK chipsets. Do a WWW search to find them.
USB modems will not be detected through the acm.o driver with port /dev/ttyACM0
UNTIL proper USB support is installed.
See http://www.linux-usb.org/USB-guide/x332.html,
Linux_kernel_source/Documentation/usb/acm.txt, and
http://www.usb.org/developers/devclass_docs/usbcdc11.pdf (page 15)
Among the USB modems with proprietary interfaces, there is support for
Conexant HSF modems are supported by the hsfmodem package at
http://www.linuxant.com/drivers
HSF USB with Vendor:Product IDs - 0572:1300 0572:1301 0572:1302
0572:1303 08E3:0111
with updates at http://www.linuxant.com/drivers/hsf/index.php
HCF Vendor ID: 0572 Product ID: 1290 (Cadmus2 HCF, Conexant) is supported,
but NOT the Cadmus I types:
http://www.linuxant.com/drivers/hcf/faq.php#25
HCF USB Vendor ID: 05AC Product ID: 8202 (Cadmus2 HCF, for Apple/Mac and
not PCs)
SmartUSB56 (ST7554) based modems with ID: 0483:7554
The SWEEX USB modem has the ST7554 chipset
Drivers are at http://www.smlink.com/main/index1.php?ln=en&main_id=40
http://linmodems.technion.ac.il/archive-fourth/msg00176.html is an
installation report.
To write out Smartlink information, use the proxy entry
./scanModem test 1131:3400
PCMCIA card modems can serve if your laptops modem is not supported under
Linux.
Look through
http://windows-breaker.devidal.tv:5190/~chris/winmodems/pcmcia_list.html
All modems with a green bar labelled OK on the left will work with Linux serial
drivers. They will immediately be recognized by
# wvdialconf /etc/wvdial.conf
or under kppp as /dev/ttyS0 ...> /dev/ttyS3
Also see http://freewebhosting.hostdepartment.com/g/gromitkc/pcmcia_list.html
The 3COM,Inc 3CXM556 and AgereSystems FM560LK chip modems use Open Source
serial-cs.o drivers.
For modems not recognized by scanModem, chipset information may be obtained
under Microsoft Windows through:
1) Start > Settings > Control Panel > Classical View (for WinXP) > Modem
or alternatively under Linux
# cat /proc/asound/mc97*
Try to identify the modem setup file, with name perhaps MODEM.INF
2) Open a COMM console, and send ATI commands to the modem (ATI, ATI1, ATI2,
etc)
which may elicit chipset and driver information. Here is an example
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
successfully identifying an Agere SoftModem chipset, both by name and through
the:softmodem SIL ID: AC97 ID:SIL REV:0x27
SUPPORT SUMMARY - as of 2009_01_19
-------------------------------------
Controller chipsets are used in the most expensive modems and are supported.
They utilize the same serial drivers included with kernel+module
installations,
and most commonly one of the ports /dev/ttyS0 thru 3.
Such chipsets are produced by 3Com, AgereSystems (the Venus chipset),
Topic Semiconductor Corp., and others. But the same companies may
produce unsupported WinModems. Do not depend on the Brand Name.
Look for an explicit statement of Linux support
AVOID the following modem chipsets:
ESS - no formal support since 2.2.2 kernels, though there are kluges:
http://andywettstein.home.comcast.net/ess/
http://tx.technion.ac.il/~raindel/
3Com/US Robotics winmodems - never supported under Linux
SmartLink - newer chipsets are supported: http://www.smlink.com
ftp://ftp.smlink.com/linux/unsupported/
Moreover, the slmodem-2.9.10 drivers will support Many but not all modem
Ssubsystems
that serve under AC97/MC97 controllers.
Conexant - all modems supported with drivers at: http://www.linuxant.com
Testcode for slow 14,400 mH support is free, BUT
there is a one time charge for the full speed support.
Intel Inc. - http://developer.intel.com/design/modems/support/drivers.htm
For early releases check at: http://linmodems.technion.ac.il/resources.html
The HaM modem is supported, but code is no longer being updated;
there will likely be failures under emerging 2.6 kernels.
The 536EP and five Intel537 modem chipset variants are actively supported.
Lucent /AgereSystems
The Venus chipset modem uses the Linux seraik drivers and is thus supported.
Modems with digital signal processing (DSP) chipsets are supported:
http:/ltmodem.heby.de
For AC97/MC97 soft modems. Initiate software access through code sponsor IBM:
http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-52698
Coding of support for has Not yet begun PCI soft modems with PCI_IDs
11c1:048?
Motorola support is at: http://www.motorola.com/softmodem/sm56_download.htm
through 2.4.22 kernels.
PCTel modem business has been sold to Conexant
Driver compiler resources are at: http://pctelcompdb.sourceforge.net/
However, the pre-compiled binary component is yet to be assembled
with the gcc 3.nn used in newer Linux releases,
so forced (-f) insertions may be necessary:
insmod -f pctel
Some of the HSP soft modems are supported by the SmartLink slmodem-2.9.10
drivers.
Broadcom modems in Dell laptops and PCs - can be made to function under 2.4
kernels, but code has not been updated recently.
--------- end chipset section ----------------------
SUPPORT under the current 2.6.nn kernels.
The more expensive Controller chipset modems are functioning.
SmartLink slmodem-2.9.9 drivers are functioning.
Conexant has 2.6.n support
The Lucent/Agere digital signal processing (DSP) chipsets do have
informal service into 2.6.n kernels and an AgereSystems release is soon
expected.
Intel, Agere Systems and Linuxant are firmly expected to continue support into
2.6.nn,
though the Intel HaM software will not be updated to 2.6.n service
------------------------------------
Preparing winmodem drivers will generally require compiling.
If you are not familar with this process DEFINITELY read carefully
the Modem/DOCs/DriverCompiling.txt
Modem Type Readout and Supporting Software Identification.
-------------------------------------------------------
Most add on cards to motherboards (including modems) adhere to a PCI standard,
for
which there is firmware on the card which can be readout, providing setup
parameters
and specification of the required software. This works under Linux provided that
drivers are resident. Herein is the practical problem. During the evolution of
modems, some of the complementing software components became Proprietary and
Closed Source. A consequence is that for reasons of Legality and/or Principle,
many Linux distributions do not distribute such modem drivers with the regular
releases, even when the modem chipset designer does provide Linux support code.
Without the drivers, additional assistance is needed to identify the modem
chipset and its complementing software.
The scanModem script includes four routines to determine the software required:
1) Readouts with a lspci tool accessing firmware on PCI cards.
2) A test using modem drivers already on your system as part of the ALSA
(Advanced Linux
Sound Architecture) software package. See DOCs/Smartlink.txt for details.
3) Comparison of Primary+Subsystem PCI IDs with others historically gathered,
and
then archived within scanModem.
4) A test requiring the SmartLink slamr.ko driver. See DOCs/Smartlink.txt for
details.
Should these not be adequate, there are directions below for doing diagnostics
during
an alernate Microsoft Windows bootup.
Stop here on a first reading, and just run
./scanModem
Read on later if you are interested in details, OR
need instructions for doing modem diagnostics under Microsoft.
Using MicroSoft(MS) Windows:
-----------------------------
MS installations do generally have adequate diagostic capability. Try the
following
routine 1), beginning with mouse clicks on:
1) Start > Settings > Control Panel > Classical View (for Window XP) >
System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or
vendor
and device information.
Next do the Query Modem and record the ATI specifications displayed such as:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
2) Open a COMM console. Send ATI commands to the modem (ATI, ATI1, ATI2,
etc)
which may elicit chipset and driver information. Here is an example:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
successfully identifying an Agere SoftModem chipset, both by name and through
the softmodem SIL ID: AC97 ID:SIL REV:0x27
The IBM mwave modem:
This has a DSP chip usually seated on the motherboard. Not carried on a PCI
card
it cannot be detected by scanModem. However, the mwave driver is included in
2.6.n kernel releases.
So try:
# modprobe mwave
Either the module will load or the absence of the modem will be indicated by:
FATAL: Error inserting mwave (/lib/modules/2.6.10-1-
686/kernel/drivers/char/mwave/mwave.ko): Input/output error
See http://www.linuxdocs.org/HOWTOs/mini/ACP-Modem/ for details on this modem.
Modem evolution:
----------------
Here is a very abbreviated history on how modem evolutionary development. The
earliest modems (MOdulate and DEModulate signals for phone lines transmission)
managed all signal proceesing on the modem card through actions of expensive
Controllers chipsets with DSP (digital signal processing) capability.
Copyrighted
Vn.nm compression routines were also encoded in the chipset. Under Linux, an
Open
Source serial driver was the minimal complementing software. This generation of
Controller chipset modems placed minimal burden on the early slow central
processing unips (CPU) of personal computers, such as the Intel 386.
As CPUs became faster, it was feasible to transfer some modem functions to
the CPU. A 2nd generation of modems retained a DSP chip, but Controller
functions
were software driven on the CPU. A benefit was that modem hardware became
cheaper.
But sadly the supporting software was Proprietary. Worst, some Intellectual
Property
components were Closed Source to protect large investment in code development.
Such
Controller free modems include the Conexant HCF, Intel-537EP and Mars chipset
modems from Lucent or its later subsidary, Agere Systems Inc.
As CPUs became even faster, even DSP functions could be software code driven on
the CPU. This third generation of modems are commonly called "softmodems". Their
complementing software is comparable in sizeto that of the Linux kernel itself.
The
residual "modem chip" is very cheap, but the development of the complementing
software is a large investment on the part of the chip designer/maker.
Modem chipset determination under Linux:
---------------------------------------
The chipset of a modem determines which complementing software is required.
The Manufacturer and Model of an assembled modem are often inadequate to
identify
the chipset. But sometimes there is an easy chipset identification. There is
a "lspci" utility provided in the Linux pciutils package. It reports the PCI
identifiers (IDs hereafter) or the Primary card, its Subsystem, and some setup
parameters written in firmware. For example, there is a softmodem in the
PCI bus of address 00:11.6 on my laptop. Shown below is firmware information
acquired by two lspci commands:
$ lspci -s 00:11.6
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller
$ lspci -s 00:11.6 -nv
00:11.6 0780: 1106:3068 (rev 80)
Subsystem: 14ff:100b
Flags: medium devsel, IRQ 193
I/O ports at e000 [size=256]
The translation is: The card inserted into PCI bus slot 00:11.6 is named
"Communication controller: VIA Technologies, Inc. AC'97 Modem Controller". The
modem was assembled by a Vendor with ID identification code 1106 . Among 1106's
products, it has a Device ID of 3068 in its 80th revison. This usually
provides
adequate information, to get software from the Vendor designated by 1106 (VIA
Technologies, Inc. in this case) for their device designation 3068. The
parameters
Flags: medium devsel, IRQ 193
I/O ports at e000 [size=256]
are determining by the environment of the host computer as reading modem
firmware.
It may change if other hardware is added/removed from the host computer, or
under a change or Operating System (OS) kernel.
The problem for softmodems is that additional information is needed for the
software
specification. The Subsystem Vendor_ID identifies only the assembler company.
But
the modem chip housed in the Subsystem could be of a variety of types, each
requiring
different support software. In general, a single Subsystem assembler could use a
variety of different softmodem chips. The Subsystem firwmare information on
the chipset
is not accessible to lspci. Rather it requires usage of a modem driver, if one
first had
some competent modem driver for minimal diagnostics.
Fortunately there are the software tools and drivers of the ALSA (Advanced
Linux
Sound Architecture) suite. This includes modem drivers lacking COMM proficiency
by
themselves, but enough capability to readout the Subsystem firmware. For the
VIA
modem above, the encoded modem codec is SIL22, reporting that the softmodem
chip was
made by SmartLink Inc.
It is important to emphasis, that AC'97 Modem Controllers are made by a variety
of companies, and each may house many different Subsystem modem chips. There is
an Archive within scanModem of those with previously identified codecs. For
example,
the table for the 1106:3068 AC'97 Controller is:
codec SubSystems_with_codec ------------>
CXT 104d:8143 104d:80f6 1025:0030
SIL27 1102:0033 1025:0046 1025:0033 1734:1078 1509:2870 1025:0046
SIL22 1743:1032 10cf:118e 1734:1054 1462:309e 1631:e004 1543:4c22
161f:2032 and_more
SIL21 10cf:118e 13bd:1022 1543:4c21 1071:8375 1019:0c04 1458:1543
1019:b320
MOT66 1734:109b
Because of hardware configuration issues, the ALSA tools may initially fail.
Then this
Archive is a fall back reporting the codec, and therefrom the needed software.
For reasons
obscure, a single Subsystem ID may have different codecs under different Primary
controllers. Thus the pair Primary+Subsystem IDs must BOTH be retained to
record
the codec.
In addition to the Modem Controllers adhering to the AC'97 specifications,
softmodem
Subsystems may be hosted by High Definition Audio (HDA) cards such as the:
8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio
Controller
These lack a softmodem codec. Instead the softmodem chip information acquired
with ALSA
tools is within a folder: /proc/asound/card0/codec*#1/
and includes the Vendor ID of the softmodem chip, such as 14f1 corresponding to
Conexant.
The software support:
---------------------
The CXT designation above is an abbreviation of CXT_some_number, for Conexant
HSF softmodem
codecs. These now number some 41 (perhaps more) CXT. Fortunately, all these
codecs are
supported by a single hsfmodem software package provided through
http://www.Linuxant.com
The trial package is free, but locked to speeds of 14,400 K. A software key
must be
purchased to enable full speed support, with future software updates free.
There is NO
freeware alternative for the hsfmodem software. But Linuxant does provide
pre-compiled
drivers for the more common Linux kernels, and their support services are good.
In the Table below, there are currently some 13 other softmodem codecs.
Fortunately
all are supported by a combination of the ALSA modem drivers, the ALSA audio
drivers
the modem drivers depend on, and a very smart helper utility from Smartlink
Inc.,
the slmodemd helper. Sasha Kharposky wrote the Linux slmodemd utility and
remains its
volunteer maintainer. It provides the cleverness to interface between the low
level
ALSA modem driver and the pppd package communications codes. For details do:
$ slmodemd --help
and read associated documentation. The slmodemd is provided with some Linux
distributions,
and can also be downloaded in SLMODEMD packages from:
http://linmodems.technion.ac.il/packages/smartlink/
Subsystems of AC'97 Modem Controllers
---------------------------------------
Subsystems for softmodems are primarily made by Silicon Labs (SIL) under
contract to companies like Intel, Agere Systems, Motorola etc. In the Table
below, ChipMadeBy does NOT imply software support directly from that
manufacturer. The chart of information below is largely harvested from messages
to [email protected].
A codec_indent such as REV:0x27 is reported by diagnostics under Microsoft, as
illustrated above. The matching designations such as SIL27 are translations
under Linux, which are output by a diagnostic of the slamr.ko driver from the
SmartLink slmodem software.
SIL is an abbreviation for Silicon Laboratories Inc., which provides Subsystems
on order to many modem assemblers.
SML is used below as abbreviation for SmartLink Inc. with official driver
resources at http://www.smlink.com/main/index1.php?ln=en&main_id=40 . BUT use
updated resources at http://linmodems.technion.ac.il/packages/smartlink/.
ALSA+SML means use an ALSA modem driver plus the Smartlink slmodemd helper,
with the particular driver depending on the AC'97 or HDA host controller.
ID was originally a hexadecimal readout from 7c and 7e registers of the
SubSystem,
but are translated into "english", as done automatically by the slamr driver.
ID chip_maker driver/helper sources
---------------- ----------------------
CXTnm Conexant hsfmodem package from http://www.linuxant.com with several
hsf* drivers.
nm - a number
SIL25 Intel ALSA+SML or INTEL-537EP supported AA variant
INT65 Intel ALSA+SML or INTEL-537EP supported EA variant
SIL26 SML SML, slamr driver plus slmodemd
SIL27 AgereSystems ALSA+SML
SIL2f " ALSA+SML
MOT66 " ALSA+SML
AGR01 " ALSA+SML
AGR02 " ALSA+SML
SIL21 PCTel ALSA+SML
SIL23 PCTel ALSA+SML
SIL22 SML ALSA+SML
SIL24 Broadcom ALSA+SML
BCM64 Broadcom ALSA+SML, under Intel ICH family, AC'97 controllers.
----------------------------------------------
Subsystems with the above characteristics could reside under any of
the primary softmodem controllers listed below. Ignore the stuff after the > .
It serves during parsing of the Table by scan modem
Primary
PCI_IDs Name Possible support by:
--------------- ----------------------------- -------------------------
8086:2416 82801AA ICHAA AC97 Modem Controller> + A a p c .
8086:2426 82801AB ICHAB AC97 Modem Controller> + A a .
8086:7186 > c .
8086:7196 82440MX Banister AC97 Modem Controller > + A a c .
8086:2446 82801BA/BAM ICH2 AC97 Modem Controller > + A a p c .
8086:2486 82801CA/CAM ICH3 AC97 Modem Controller > + A a p c i .
8086:24c6 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)1DB ICH4 AC97 Modem Controller>
+ A a c i b .
8086:25a7 6300ESB AC97 Modem Controller NEW >
8086:24d6 82801EB/ER ICH5/ICH5SR AC97 Modem Controller> + A
c i .
8086:8280 1EB ICH6 AC97 Modem Controller> + A c .
8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio
Controller> H c .
8086:266d Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC97 Modem Controller
>
8086:2669 631xESB/632xESB AC97 Modem Controller NEW >
8086:27d8 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller HDA > .
8086:27dd (ICH7 Family) AC97 Modem Controller NEW >
8086:xxxx types above are from Intel>
1039:7013 SIS 630 > + a p c i .
1039:7018 SIS 960 > + i .
10de:01c1 Nvidia Corp > + i .
10de:00d9 Nvidia Corp > A c .
1106:3068 VIA > + a p c i .
1022:7446 AMD AC_LINK > + .
10b9:5450 ALI 5450 >
10b9:5451 ALI 5451 > + a c .
10b9:5453 ALI 5453 AC-Link > p c .
1025:5453 ALI 5453 AC-Link > c .
10b9:5457 ALI 5457 AC-Link > + p c i .
1025:5457 ALI 5457 AC-Link > c . .
1002:434d ATI > T a c i .
1002:437b ATI Audio device: ATI Technologies Inc SB450 HDA Audio a .
1002:4378 ATI > c .
1543:3052 SI3052 >
Class 0403, High Definition Audio Controllers (HDA)
-----------------------------------------------------
8086:2668 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) HDA Controller
8086:27d8 Intel Corporation 82801G (ICH7 Family) High Definition Audio
Controller
1002:437b Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
10de:026c nVidia Corporation MCP51 High Definition Audio
----------------------------------------------------
are the members of this family encountered as of September 2006.
From the file /proc/asound/card0/codec*#1/, there are the following Subsystem
chips:
Vendor IDs Chip maker Support type
---------- ---------- -------------
0x14f12bfa Conexant hsfmodem , not slmodemd compatible
0x14f12c06
0x11c13026 AgereSystems snd-hda-intel, slmodemd
0x11c11040 " not supported into 2008
0x163c3055 Smartlink snd-hda-intel, slmodemd
0x163c3155 " " "
0x10573055 Motorola " "
0x10573155 " " "
