Sushil,
scanModem recommends the slamr module for your PCTEL modem:
Predictive diagnostics for card in bus 01:02.0:
Modem chipset detected on
NAME="Modem: PCTel Inc HSP56 MicroModem "
CLASS=0703
PCIDEV=134d:2189
SUBSYS=134d:1002
IRQ=18
IDENT=slamr
For candidate modem in: 01:02.0
0703 Modem: PCTel Inc HSP56 MicroModem
Primary device ID: 134d:2189
Support type needed or chipset: slamr
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 kernels 2.6.31 the slamr driver is not (yet) functional, failing
within at the
Carrier Check
function. Thus for service, retain a 2.6.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.28-11-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.28-11-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
It also reports that you don't have wvdial installed and how to install it:
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.
If you install your modem drivers and the modem does not respond, it
might be because of:
For candidate card in slot 01:02.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:02.0 134d:2189 134d:1002 Modem: PCTel Inc HSP56 MicroModem
Modem interrupt assignment and sharing:
18: 0 IO-APIC-fasteoi uhci_hcd:usb4
--- Bootup diagnostics for card in PCI slot 01:02.0 ----
[ 0.845728] pci 0000:01:02.0: reg 10 32bit mmio: [0xe8000000-0xe8000fff]
[ 0.845739] pci 0000:01:02.0: reg 14 io port: [0xd000-0xd0ff]
[ 0.845782] pci 0000:01:02.0: PME# supported from D0 D3hot D3cold
[ 0.845788] pci 0000:01:02.0: PME# disabled
[ 2.443164] serial 0000:01:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 2.443342] 0000:01:02.0: ttyS2 at I/O 0xd008 (irq = 18) is a 16450
[ 2.443450] 0000:01:02.0: ttyS3 at I/O 0xd010 (irq = 18) is a 8250
[ 2.443492] Couldn't register serial port 0000:01:02.0: -28
The PCI slot 01:02.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.
Try the above advice and report back.
Regards,
Antonio
On Thu, Jan 28, 2010 at 2:01 PM, Sushil Dahal <sushilthe@xxxxxxxxx> wrote:
> Please help me wvdial didn't detect my modem...
>
>
>
> Regards,
>
> Sushil Dahal
> Nepal
>
