Attached is the output from Scanmodem.
I tried to install wvdial and here is the result:
trevorj@trevorj-Linux:~$ sudo apt-get install wvdial
[sudo] password for trevorj:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package wvdial is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package wvdial has no installation candidate
trevorj@trevorj-Linux:~$
Help (again!)
Trevor
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.31-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. 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,
Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
scanModem update of: 2010_01_22
The dialer utility package WVDIAL does not appear to be installed on your System.
For Ubuntu users, there are at the bottom of http://linmodems.technion.ac.il/packages/
packages with the files necessary to install wvdial, with names like:
wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems.
wvdial_jaunty_i386.zip for 32 bit systems.
wvdial_karmic_i386.zip for 32 bit systems.
These are about 1 MB in size. After downloaded and copied into your Linux partition:
$ unzip wv*.zip
Within the new folder:
$ sudo dpkg -i *.deb
will complete the wvdial installation
Please read Modem/DOCs/wvdial.txt for usage information.
Presently install your Linux Distributions dkms package. It provides for automated driver updates,
following upgrade of your kernel. For details see http://linux.dell.com/projects.shtml#dkms
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_hda_intel
Attached USB devices are:
ID 03f0:7904 Hewlett-Packard
ID 16d8:6280 CMOTECH Co., Ltd. CMOTECH CDMA Technologies modem
If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html
A sample report is: http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx
For candidate card in slot 03:01.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
03:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
--- Bootup diagnostics for card in PCI slot 03:01.0 ----
[ 0.174825] pci 0000:03:01.0: reg 10 32bit mmio: [0xe1200000-0xe1200fff]
[ 0.174833] pci 0000:03:01.0: reg 14 io port: [0xd000-0xd0ff]
[ 0.174881] pci 0000:03:01.0: PME# supported from D0 D3hot D3cold
[ 0.174886] pci 0000:03:01.0: PME# disabled
[ 0.810422] serial 0000:03:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[ 0.810530] 0000:03:01.0: ttyS1 at I/O 0xd008 (irq = 19) is a 16450
[ 0.810599] 0000:03:01.0: ttyS2 at I/O 0xd010 (irq = 19) is a 8250
[ 0.810668] 0000:03:01.0: ttyS3 at I/O 0xd018 (irq = 19) is a 16450
[ 0.810687] Couldn't register serial port 0000:03:01.0: -28
The PCI slot 03:01.0 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 DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1b.0 8086:27d8 1458:a002 Audio device: Intel Corporation 82801G
Modem interrupt assignment and sharing:
16: 1462 1494 IO-APIC-fasteoi uhci_hcd:usb5, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.173735] pci 0000:00:1b.0: reg 10 64bit mmio: [0xe1380000-0xe1383fff]
[ 0.173779] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.173783] pci 0000:00:1b.0: PME# disabled
[ 8.748396] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 8.748424] HDA Intel 0000:00:1b.0: setting latency timer to 64
[ 9.008449] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input5
The PCI slot 00:1b.0 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 DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
===== 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.20
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-00: ALC662 rev1 Analog : ALC662 rev1 Analog : playback 1 : capture 1
00-01: ALC662 rev1 Digital : ALC662 rev1 Digital : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xe1380000 irq 16
PCI slot 00:1b.0 has a High Definition Audio Card
The drivers are in the kernel modules tree at:
/lib/modules/2.6.31-14-generic/kernel/sound/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 03:01.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=19
IDENT=slamr
For candidate modem in: 03:01.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
Writing DOCs/Intel.txt
1057:3052 has a Motorola chipset, poorly supported by Motorola itself
However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!
It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.
There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052
similarly added. See messages from Zello:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
The modem is supported by the Smartlink
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For kernels 2.8.31 the slamr driver is not (yet) functional, failing within at the
Carrier Check
function. Thus for service, retain a 2.8.30 or earlier kernel. For Ubuntu users this
can be done by downloading the kernel from http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic
and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ the slamr-2.6.28-16-generic.tar.gz
From http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ ,
download the package slamr-2.6.31-14-generic.tar.gz
Under Linux, open a terminal and unpack with:
$ tar zxvf slamr*.tar.gz
Move into the unpacked folder
$ cd slamr-2.6.31-14-generic
Look around
$ ls
Run the
$ sudo ./setup
Afterwards do:
$ slmodemd --help
$ slmodemd --countrylist &> Clist.txt
If not in the USA, look for your COUNTRY_NAME therein.
Do and edit with:
$ sudo gedit /etc/default/sl-modem-daemon
and therein replace the USA in the line:
SLMODEMD_COUNTRY=USA
This will provide for the correct Country setting in the automated:
slmodemd -c COUNTRY /dev/slamr0
Read the DOCs/Smartlink.txt and DOCs/YourSystem.txt
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 82801G "
CLASS=0403
PCIDEV=8086:27d8
SUBSYS=1458:a002
IRQ=16
HDA=8086:27d8
SOFT=8086:27d8.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:27d8.
If another modem card is present, then most likely 8086:27d8 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:27d8, 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: 00:1b.0
0403 Audio device: Intel Corporation 82801G
Primary device ID: 8086:27d8
Subsystem PCI_id 1458:a002
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.4.tar.gz from:
http://linmodems.technion.ac.il/packages/smartlink/
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.1
and the compiler used in kernel assembly: 4.4.1
The patch utility is needed for compiling ALSA drivers, and possibly others.
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.31-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 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.
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 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
For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ get faxing.tar.gz
It has samples for a modem using port /dev/ttySL0, which must be changed to match your modem's port.
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0
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/blacklist-modem.conf:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
