plz provide the neccessary driver for my modem..
I am using PcteL HSP56 Micromodem
I have used scan Modem.gz
plz help me sir
RAkesh Krishnan
INDIA
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
Welcome to openSUSE 11.0 (i586) - Kernel kernel 2.6.25.5-1.1-default
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 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,
Welcome to openSUSE 11.0 (i586) - Kernel
Linux version 2.6.25.5-1.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-06-07 01:55:22 +0200
scanModem update of: 2008_08_26
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 196d:0100
ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
ID 1d6b:0002 Linux Foundation 2.0 root hub
USB modems not recognized
For candidate card in slot 05:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
05:00.0 134d:2189 134d:1002 Modem: PCTel Inc HSP56 MicroModem
Modem interrupt assignment and sharing:
11: 1952 XT-PIC-XT uhci_hcd:usb4, uhci_hcd:usb5, HDA Intel
--- Bootup diagnostics for card in PCI slot 05:00.0 ----
PCI: Found IRQ 11 for device 0000:05:00.0
0000:05:00.0: ttyS1 at I/O 0x1008 (irq = 11) is a 16450
0000:05:00.0: ttyS2 at I/O 0x1010 (irq = 11) is a 8250
0000:05:00.0: ttyS3 at I/O 0x1018 (irq = 11) is a 16450
Couldn't register serial port 0000:05:00.0: -28
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:2668 8086:e303 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
11: 1952 XT-PIC-XT uhci_hcd:usb4, uhci_hcd:usb5, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Found IRQ 11 for device 0000:00:1b.0
PCI: Setting latency timer of device 0000:00:1b.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-04: ALC880 Analog : ALC880 Analog : capture 2
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x201c0000 irq 11
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.25.5-1.1-default/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.5-1.1-pae/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.5-1.1-xen/kernel/sound/pci/hda/snd-hda-intel.ko
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 05:00.0:
Modem chipset detected on
NAME="Modem: PCTel Inc HSP56 MicroModem "
CLASS=0703
PCIDEV=134d:2189
SUBSYS=134d:1002
IRQ=11
IDENT=slamr
For candidate modem in: 05:00.0
0703 Modem: PCTel Inc HSP56 MicroModem
Primary device ID: 134d:2189
Support type needed or chipset: slamr
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
134d:2189 is a PCTel HSP56 MicroModem 688T modem with the Oasis chipset.
Under 2.6.n kernels, it is only supported through the Smartlink slamr.ko driver.
The modem is supported by the Smartlink slamr
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 2.6.25.5-1.1-default compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
CLASS=0403
PCIDEV=8086:2668
SUBSYS=8086:e303
IRQ=11
HDA=8086:2668
SOFT=8086:2668.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 8086:2668.
If another modem card is present, then most likely 8086:2668 does not host a modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 8086:2668, 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:
wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:2668
Subsystem PCI_id 8086:e303
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.3.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.3.1 and a compiler is not installed
If compiling is necessary packages must be installed, providing:
gcc-4.3 make
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:
-rwxr-xr-x 1 root dialout 304644 2008-06-07 02:51 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
noipdefault
noauth
crtscts
lock
modem
asyncmap 0
nodetach
lcp-echo-interval 30
lcp-echo-failure 4
lcp-max-configure 60
lcp-restart 2
idle 600
noipx
file /etc/ppp/filters
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
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:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/mwave", GROUP="uucp"
/etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", GOTO="skip_ifup"
Within /etc/modprobe.conf files:
/etc/modprobe.conf:# Linux ACP modem (Mwave)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
Smartlink modem setup.
-----------------------------------------------------------
The modem should setup with:
modprobe ungrab-winmodem
modprobe slamr
slmodemd -c YOUR_COUNTRY /dev/slamr0
which should announce creation of ports:
/dev/ttySL0 --> /dev/pts/N , N some number
Specify the symbolic link /dev/ttySL0 as the port to be used by dailer software.
SmartLink (http://www.smlink.com/) chipset modems are sold under a variety
of BrandNames, and have vendor IDs 163c, 2000, 2003, and 2004. Conexant bought
Smartlinks's modem distribution sector in 2005. While Linux updates are not
expected from Conexant, Linux support is still very good thanks to volunteer
Linux maintainer Sasha Khapyorsky. Get his updated software from:
http://linmodems.technion.ac.il/packages/smartlink/
A high level support component is a smart helper: slmodemd
Acting through one of several drivers, it creats ports dynamically and
supports COMM and FAXing functions. During facsimile usage, the AT&F command
is not supported. A means of implmenting the FAX CNG is lacking, because this
function is encoded within the dsplibs.o precompiled at Smartlink, Inc. See
http://marc.theaimsgroup.com/?t=116026350800001&r=1&w=2
http://marc.theaimsgroup.com/?l=hylafax&m=116041369404444&w=2
There is service on AMD x86_64 processor mother boards, see
http://linmodems.technion.ac.il/archive-fourth/msg02594.html
http://linmodems.technion.ac.il/archive-fifth/msg02490.html
However a 64 bit compilation of a proprietary dsplibs.o conponent is not
available. Hence the 32 bit versions of the libasound2 package must be installed
to support slmodemd. But the ALSA modem drivers or USB driver slusb can be assembled
with a 64 bit compiler. The slamr driver is
The slmodemd supports a few different types of modem drivers. Below the suffix
.ko means the modular form of a driver, before loading into the kernel. The
slmodemd does not access the modem hardware directly. Rather access is provided
through lower sophistication drivers. Prior to usage of a slamr driver, there
must be a release of serial driver interference by loading of: ungrab-winmodem.ko
For PCI card modems with Smartlink chips the driver used is: slamr.ko
For USB modems with ID 0483:7554 use Smartlink driver: slusb.ko
For ALSA (Advanced Linux Sound Architecture) modem drivers, see the Table below.
Because of changes during the evolution of the Linux kernel, there are the following
Outstanding PROBLEMS concerning:
slamr - for 2.6.24 and later kernels, function will fail after a single dialout.
See: http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01559.html
To recover, stop slmodemd and then unload slamr, follow 1) or 2)
1) If the sl-modem-daemon or
similar scripts are installed, it will suffice to with root/adm premission:
/etc/init.d/sl-modem-daemon restart
Then proceed with the next dialout.
2) With root/adm permission, to stop slmodemd in the console which it was started:
Ctrl-C
modprobe -r slamr
modprobe slamr
slmodemd -c YOUR_COUNTRY /dev/slamr0
slusb - for 2.6.25 and later kernels, the kernel will no longer accept slusb.
This is because of the Proprietary lincense in its Open Source code.
If principle, those with necessary COMM code skills could rewrite
a non-Proprietary driver. But to our knowledge, this task is not now progressing.
See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01264.html
Sasha's core resources are:
----------------------------
ungrab-winmodem.tar.gz - for compiling a ungrab-winmodem.ko driver
slmodem-2.9.11-MostRecentDate.tar.gz - the core code resource for compiling
and installing slmodemd, slamr.ko and slusb.ko. The slmodemd dynamically
creates ports and provides higher level COMM functions, after driver
loading. Not being a driver, slmodemd serves under alternative boot kernels.
ALSA modem drivers, included with 2.6.n kernel+module releases.
Some derivative resources at http://linmodems.technion.ac.il/packages/smartlink/
SLMODEMD.gcc4.3.tar.gz - containing a compiled slmodemd and usage instructions.
When used with ALSA modem drivers, further compiling is not necessary.
> SLMODEMD.gcc4.3.tar.gz will suffice for getting online, though read on about automation. <<< See Compiling_slmodemd below, for details.
sl-modem-daemon-SomeVersion.deb - an installer for Debian related distros.
It has slmodemd and scripts for starting slmodemd at boot.
This package is also available from repositories of Debian related distros
Ubuntu, Kbuntu, Ebuntu, Xandros, Kanotix and others.
sl-modem-daemon-SomeVersion.tar.gz has the same contents, but is repackaged
in an easily opened format, for access to its automation scripts.
After unpacking, they are resident in the etc/ subfolder
sl-modem-source-SomeVersion.deb - is a Debian installer for the slamr and slusb
source code. It is Not necessary for ALSA driver usage.
slamr-KernelVersion.tar.gz - for several Ubuntu KernelVersions, containing:
ungrab-winmodem.ko, slamr.ko, slusb.ko, slmomdem, setup script and as
a convenience, the sl-modem-daemon-SomeVersion.deb. Look in the folder:
http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
For x86_64 Systems using a USB modem with Smartlink chipset, get from
http://linmodems.technion.ac.il/packages/smartlink/ the slusb64bit.txt and
slusb64bit-2.9.11-20070813.tar.gz. To use it the 32 bit versions of libasound2 (Debian/Ubunutu name)
must be installed, in addition to the 64 bit versions installed by default.
The products will be slmodemd compiled (of necessity) as a 32 bit binary and
slusb.ko compiled as the complementary 64 bit driver.
Slmodemd actions
-----------------------------------------
Start working with slmodemd with commands:
slmodemd --help
slmodemd --countrylist
The long output can be written to a Clist.txt file with:
slmodemd --countrylist &> Clist.txt
Find your COUNTRY_NAME within the 2nd column if the list and record it.
It will be used in capital letters during the modem setup command.
Try USA if your COUNTRY is not in the list.
Before modem setup root/adm capacity must be acquired with:
su - root
or by prefixing commands with "sudo" for Ubuntu Linux and its cousins.
The setup command is:
slmodemd -c COUNTRY_NAME --alsa slmodemd_device
if successful there will be reported dynamic creation of:
/dev/ttySL0 --> /dev/pts/N , with N a number
The /dev/ttySL0 is a symbolic link to the real modem port /dev/pts/N ,
and it is /dev/ttySL0 which should be named to dialup utilities such
as wvdial. The "--alsa" is only needed for usage with ALSA modem drivers.
Throughout a dialout session slmodemd MUST be kept running. Open another
console/termimal to startup dialout software such as wvdial.
The slmodemd device nodes
---------------------------
The slmodemd_device is different for the several modem drivers.
For usage with slamr.ko , the slmodemd_device is /dev/slamr0 , within
the command sequence:
modprobe ungrab-windmodem
modprobe slamr
slmodemd -c COUNTRY_NAME /dev/slamr0
For USB modem usage:
modprobe slusb
slmodemd -c COUNTRY_NAME /dev/slusb0
For a modems using a ALSA driver, details are below.
The /dev/slamr0 and /dev/slusb0 will be made the slmodem installation
processes. However, they usually will NOT survice reboot, because
most current Linux have ports created in volatile RAM space. However
the these devices can be manually created under root/adm persmission with:
mknod -m 600 /dev/slamr0 c 242 0
mknod -m 600 /dev/slusb0 c 243 0
if automation scripts are not yet in place.
For automation of RPM using Linux distros see:
http://www20.brinkster.com/olivares/slmodemd-setup-1.html
For any Distro the following lines will serve in /etc/modprobe.conf or subfolders of
/etc/modprobe.d/:
--------------
alias char-major-243 slusb
alias char-major-242 slamr
# The following install and remove commands are to be written as single lines.
# Preloads ungrab-winmodem and creates a device node upon "modprobe slamr"
install slamr modprobe --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
# rpm using distros should use "uucp" rather than "dialout"
# Removes slamr and ungrab-winmodem successively:
remove slamr /sbin/modprobe -r --ignore-remove slamr ; /sbin/modprobe -r --ignore-remove ungrab-winmodem
# creates /dev/slusb uponn slusb driver loading.
install slusb modprobe --ignore-install slusb ; test -e /dev/slusb0 || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0)
# rpm using distros should use "uucp" rather than "dialout"
Usage with ALSA modem drivers
--------------------------------
See DOCs/SoftModem.txt for a description of the hardware. For a modem using
an ALSA driver, the slmodemd_device only has to be specified within the
slmodemd command line. A preliminary "mknod something" command is not necessary.
The Table shows hardware PCI ID, its card type, driver and slmodemd_device name.
The ALI5451 and HDA (High Definition Audio) cards can host softmodems. For these
cards hw:0,0 is the audio card designation and the modem Subsystem on it
is most commonly hw:0,1 , but there are some hw:0,6 cases. For the older
soft modem controller family, the ALSA software first assigns hw:0 to an audio
card, and the following modem designation is hw:1 or equivalently modem:1
An attempt to use modem:0 may initially appear successful, but modem:0 or hw:0
is actually the companion audio card.
PCI ID controller ALSA driver slmodemd_device
========= =============== =============== ===================
several HDA cards snd-hda-intel hw:0,1 or hw:0,6
10b9:5451 ALI5451 audio snd-ali5451 hw:0,1
------------------ softmodem controllers --------------------------
1002:434d ATI snd-atiixp-modem modem:1
1002:4378 ATI " "
1106:3068 VIA snd-via82xxx-modem "
8086:xxxx many Intel snd-intel8x0m "
10de:00d9 Nvidia Corp " "
SIS 630 " "
Others? " test "
---------------------------------------------------------------------------
* The scanModem script tries to determine ALSA modem driver and slmodemd_device
dynamically from /proc/asound/ information, or the internal Archive as a fallback.
Do a precautionary unloading and reloading of the driver.
su - root (not for Ubuntu)
With driver the proper one of the "ALSA driver" listed above
modprobe -r driver
modprobe driver
This precaution is sometimes necessary, because a driver may functionally die
although loaded. But usually it can be skipped.
For this System, scanModem deduced slmodemd_device is:
For most modems the setup command is:
slmodemd -c COUNTRY_NAME --alsa modem:1
For modems on HDA cards, the command is:
slmodemd -c COUNTRY_NAME --alsa hw:0,1
though there have been cases of hw:0,6
For the ALI5451 hosted modems, a shortbuffer (-s) option is needed:
slmodemd -s -c COUNTRY_NAME --alsa hw:0,1
The slamr diagnostic
---------------------
Sasha has provided slamr.ko with a capability for reporting softmodem codecs,
even for modems not supported fully by slamr. This is useful when other
resources do not report out the modem codec, needed to distinguish between
hsfmodem, slamr and ALSA driver support alternatives.
This slamr test is Not effective for softmodems on HDA audio cards.
The test routine is:
modprobe ungrab-winmodem
modprobe slamr
followed by a readout from the dmesg buffer with:
dmesg | grep slamr
Among the few output lines, there is one like:
slamr: mc97 codec is SIL27
reporting in this example an ALSA driver supported, Agere Systems codec SIL27.
Conexant codecs have format CXTnm, nm a number. These modems are not ALSA driver supported.
Softmodems with all other codecs should be ALSA driver plus slmodemd supported.
Compiling_slmodemd
------------------
slmodemd can be compiled with or without support for ALSA modem drivers.
Within the slmodem code folder, the command sequence:
make clean
make
compiles a slmodemd without ALSA support, and a following
make install
installs slmodemd to /usr/sbin/slmodemd and additionally slusb.ko and slamr.ko drivers.
These two drivers do NOT need the additional ALSA support codes
To compile slmodemd WITH support for ALSA modem drivers, there are two additional requisites.
1) additional ALSA code must be installed. For Debian/Ubuntu related Distros, these
are provided by the package libasound2-dev, in addition to the standardly installed libasound2
For other Linuxes, the needed package may have another name
2) The compile must be done in the modem/ subfolder:
$ cd modem
$ make clean
$ make SUPPORT_ALSA=1
will incorporate the needed libasound2-dev code in the resultant slmodemd.
It should be manually installed:
$ su root
OR for Ubuntu systems "$ sudo COMMAND" to execute Root/adm permission commands.
# cp slmodemd /usr/sbin/
# chmod +x /usr/sbin/slmodemd
# chown root:root /usr/sbin/slmodemd
completes the installation of the ALSA competent slmodemd.
RATIONAL
This scanModem service is sadly necessary because of the pre-compiled format
(binary, Closed Source) of some modem supporting code. Intellectual property
is protected within the binary component. But this prevents compatibility
assessments/debugging against Linux Open Source code. Skipping many details,
the consequence is that some Linux distributions do not deliver Closed Source code,
or tools adequate to fully identify the modem chipset.
This script tries to close this information gap.
This script primarily utilizes the "lspci" utility from the package PCIUTILS.
Various component scriptlets interpret the information captured by lspci.
For many modems, directions to supporting software and/or more detailed information is enabled.
ISA bus modems, 16 bit PCMCIA card modems and USB modems will not be recognized.
See the output files for guidance on these cases.
The script originated as scanPCI written by Chris Hebeisen,
to recognize modems with DSP (digital signal processing) chipsets made by Lucent/AgereSystems.
It now aspires to provide useful information on other modems as well.
For the Lucent/Agere DSP chip modems, System information is used to recommend Installers,
from the Installer list output from the repository: http://ltmodem.heby.de/
For other modem chipsets fully identified, URLs to support sites are given.
Three types of information are acquired from your System:
1) General system information necessary for your guidance;
2) The PCI_ID of the modem card, or for the increasingly prevalent "soft modems",
the PCI_IDs of its AC97/MC97 controller and its modem subsystem.
3) For soft modems, a SIL_ID of the subsystem is either acquired
OR instructions provided for manual agetting it.
The remainder of ./scanModem is a repository of "modem gossip" or URLs thereto.
Only information blocks most relevant to your System will be output into
files written to the Modem/ folder
Should you need assistance after FIRST following all the advice and/or URLs,
1) Browse the general information at: http://linmodems.technion.ac.il/
2) ONLY thereafter send ModemData.txt to: discuss@xxxxxxxxxxxxx
Modem/DOCs/General.txt has common information the List need not be bothered with.
3) Also the archive SEARCH ENGINE at http://linmodems.technion.ac.il/
may be useful once PCI or SIL IDs are acquired.
The scanModem script can be read and word searched with a text browser.
Blocks of Information with little code begin and end with #####.
In case of a failure concerning "lspci", rerun ./scanModem after login to a console with
# su - root
as Root permission may be necessary for access to lspci.
Updated on 2008_08_26 by Marv Stodolsk for access through:
http://linmodems.technion.ac.il/packages/scanModem.gz
Please do NOT use a scanModem.gz from any other site!!
This file should NOT be sent to Discuss@xxxxxxxxxxxxx
It has common guidance for modem usage after setup.
Welcome is not yet providing pre-compiled drivers for WinModems
The Modem/DOCs/DriverCompiling.txt is a MUST READ,
if you are not experienced in configuring kernel-source/
or get "unresolved symbols" upon driver insertion.
Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html
(4) For guidance on automation see http://linmodems.technion.ac.il/archive-fourth/msg03734.html
and the scripts in the slmodem-2.9.n/scripts folder/
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
Welcome to openSUSE 11.0 (i586) - Kernel kernel 2.6.25.5-1.1-default
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 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,
Welcome to openSUSE 11.0 (i586) - Kernel
Linux version 2.6.25.5-1.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-06-07 01:55:22 +0200
scanModem update of: 2008_08_26
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 196d:0100
ID 13fe:1d00 Kingston Technology Company Inc. DataTraveler 2.0 1GB/4GB Flash Drive / Patriot Xporter 4GB Flash Drive
ID 1d6b:0002 Linux Foundation 2.0 root hub
USB modems not recognized
For candidate card in slot 05:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
05:00.0 134d:2189 134d:1002 Modem: PCTel Inc HSP56 MicroModem
Modem interrupt assignment and sharing:
11: 1952 XT-PIC-XT uhci_hcd:usb4, uhci_hcd:usb5, HDA Intel
--- Bootup diagnostics for card in PCI slot 05:00.0 ----
PCI: Found IRQ 11 for device 0000:05:00.0
0000:05:00.0: ttyS1 at I/O 0x1008 (irq = 11) is a 16450
0000:05:00.0: ttyS2 at I/O 0x1010 (irq = 11) is a 8250
0000:05:00.0: ttyS3 at I/O 0x1018 (irq = 11) is a 16450
Couldn't register serial port 0000:05:00.0: -28
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:2668 8086:e303 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
11: 1952 XT-PIC-XT uhci_hcd:usb4, uhci_hcd:usb5, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Sharing IRQ 11 with 0000:00:1b.0
PCI: Found IRQ 11 for device 0000:00:1b.0
PCI: Setting latency timer of device 0000:00:1b.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-04: ALC880 Analog : ALC880 Analog : capture 2
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0x201c0000 irq 11
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.25.5-1.1-default/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.5-1.1-pae/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.25.5-1.1-xen/kernel/sound/pci/hda/snd-hda-intel.ko
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 05:00.0:
Modem chipset detected on
NAME="Modem: PCTel Inc HSP56 MicroModem "
CLASS=0703
PCIDEV=134d:2189
SUBSYS=134d:1002
IRQ=11
IDENT=slamr
For candidate modem in: 05:00.0
0703 Modem: PCTel Inc HSP56 MicroModem
Primary device ID: 134d:2189
Support type needed or chipset: slamr
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
134d:2189 is a PCTel HSP56 MicroModem 688T modem with the Oasis chipset.
Under 2.6.n kernels, it is only supported through the Smartlink slamr.ko driver.
The modem is supported by the Smartlink slamr
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 2.6.25.5-1.1-default compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Predictive diagnostics for card in bus 00:1b.0:
Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW "
CLASS=0403
PCIDEV=8086:2668
SUBSYS=8086:e303
IRQ=11
HDA=8086:2668
SOFT=8086:2668.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 8086:2668.
If another modem card is present, then most likely 8086:2668 does not host a modem.
If another modem card has not been detected, then possibilities are:
1) A Conexant modem chip is present on 8086:2668, 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:
wvdialconf /etc/wvdial.conf
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:2668
Subsystem PCI_id 8086:e303
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.3.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
----------------end Softmodem section --------------
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.3.1 and a compiler is not installed
If compiling is necessary packages must be installed, providing:
gcc-4.3 make
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:
-rwxr-xr-x 1 root dialout 304644 2008-06-07 02:51 /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)
chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
noipdefault
noauth
crtscts
lock
modem
asyncmap 0
nodetach
lcp-echo-interval 30
lcp-echo-failure 4
lcp-max-configure 60
lcp-restart 2
idle 600
noipx
file /etc/ppp/filters
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
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:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave", NAME="modems/mwave", GROUP="uucp"
/etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net", ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*", GOTO="skip_ifup"
Within /etc/modprobe.conf files:
/etc/modprobe.conf:# Linux ACP modem (Mwave)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
