Hi LinModemers,
The Problem: The modem works, but it's not reporting Caller ID on Linux
(using /dev/slusb0).
Some Background: It reports Caller ID using HyperTerm under Windows XP with
the exact same configuration.
Therefore the modem h/w must support it and the telco line is working
correctly.
I tried switching to alsa, and I can communicate with the modem, but it
doesn't even report RING,
so I figured on staying with slusb
ati7 reports back the following on both Linux and Windows:
Country: USA
I added more detailed info below.
Hope somebody can help...
Chaim
========== Windows HyperTerm Log ====================
at
OK
at#cid=1
OK
RING
DATE = 0831
TIME = 1223
NMBR = 7325551212
NAME = HOWELL NJ
RING
RING
========= Here's info on my Linux installed packages
==========================
$ dpkg -l | grep modem
ii sl-modem-daemon 2.9.9d+e-pre2-10
SmartLink software modem daemon
ii sl-modem-modules-2.6.18-5-486 2.9.9d+e-pre2-10+2.6.18.dfsg.1-13etch1
Smart Link modem modules for Linux (kernel 2
ii sl-modem-source 2.9.9d+e-pre2-10
SmartLink software modem driver - module bui
========= Here's the results of starting it up with slmodemd -d5 -c USA
/dev/slusb0 ==============================
SmartLink Soft Modem: version 2.9.11 Sep 3 2007 03:40:16
picocom /dev/ttySL0
picocom v1.4
port is : /dev/ttySL0
flowcontrol : none
baudrate is : 9600
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : no
nolock is : no
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
Terminal ready
<153.505740> main: termios changed.
<153.505775> slusb0: update termios...
at
<157.225516> slusb0: run cmd: at
<157.225553> slusb0: modem report result: 0 (OK)
OK
at#cid=1
<163.222422> slusb0: run cmd: at#cid=1
<163.222461> slusb0: modem report result: 0 (OK)
OK
<177.541382> slusb0: modem_ring...
<177.541455> slusb0: modem_cid_start: timeout = 400...
<177.541470> cid: create...
<177.541488> FSK CID Creating
<177.541500> FSK CID Reset !
<177.541516> FSK CID Setting Fs = 8000 Threshold = 2 !
<177.541531> slusb0: modem set hook: 0 --> 2...
<177.541545> main: modemap_ioctl: cmd 2, arg 2...
<177.541561> main: modemap_ioctl: cmd 4, arg 2580...
<177.541575> main: modemap_ioctl: cmd 7, arg 30...
<177.541589> main: modemap_start...
<180.056416> slusb0: modem_event: 1...
<180.056465> slusb0: ring valid.
<180.056484> slusb0: modem report result: 2 (RING)
RING
<181.060570> Tone 1200 Detected
<181.560455> slusb0: modem_cid_stop...
<181.560502> slusb0: modem_stop..
<181.560514> main: modemap_stop...
<181.564380> slusb0: modem set hook: 0 --> 0...
<181.564456> main: modemap_ioctl: cmd 8, arg 0...
<181.564481> cid: delete...
<181.564505> slusb0: modem set state: 1 --> 1...
<183.539900> slusb0: modem_ring...
<186.052373> slusb0: modem_event: 1...
<186.052425> slusb0: ring valid.
<186.052437> slusb0: modem report result: 2 (RING)
RING
<189.539541> slusb0: modem_ring...
<192.052355> slusb0: modem_event: 1...
<192.052406> slusb0: ring valid.
<192.052417> slusb0: modem report result: 2 (RING)
RING
<198.564348> slusb0: modem_event: 1...
<198.564395> slusb0: ring cancel...
Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Debian GNU/Linux 4.0 kernel 2.6.18-5-486
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through: http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Debian GNU/Linux 4.0
Linux version 2.6.18-5-486 (Debian 2.6.18.dfsg.1-13etch1) (dannf@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Sun Aug 12 21:23:09 UTC 2007
scanModem update of: 2007_August_28
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2
There are no blacklisted modem drivers in /etc/modprobe* files
Bus 003 Device 007: ID 0483:7554 SGS Thomson Microelectronics 56k SoftModem
idVendor 0x0483 SGS Thomson Microelectronics
idProduct 0x7554 56k SoftModem
Several modems are supported by drivers with ALSA, the Advanced Linux Sound Architecture software.
Copying ALSA diagnostics to Modem/ALSAroot.tgz
ALSAversion = 1.0.13
Modem or candidate host audio card have firmware information and diagnostics:
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
A modem was not detected among the PCI devices:
------------------------------------------------
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics (rev 03)
------------------------------------------------
with USB and bridge devices not displayed.
Please provide any independent information available on your modem.
If your modem is mounted on an ISA card, scanModem could not access it.
If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
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.
If may contain chipset Vendor informaton.
Checking for audio+modem support in /proc/asound/pcm
00-01: VIA 8235 : VIA 8235 : playback 1 : capture 1
00-00: VIA 8235 : VIA 8235 : playback 4 : capture 1
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.1.2
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.18-5-486/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.
Compressed files at: /usr/src/alsa-driver.tar.bz2 /usr/src/sl-modem.tar.bz2
For Debian and some related distributions, a package kernel-kbuild-2.6-18 may be needed to support driver compiling
If a driver compilation files with message including some lack of some FileName.h (stdio.h for example.
Some additional kernel-header files need installation to /usr/include.
For Debian/Ubuntu related distributions, run the following command to display the needed package list:
$ sudo apt-get -s install linux-kernel-devel
While some of the files may be on the install CD, others may have to be found through http://packages.ubuntu.com
For Ubuntu Feisty, additional packages required were:
libc6-dev linux-libc-dev
available through http://packages.ubuntu.com/ , if not on the install CD.
Such packages may have different names for other Linux distributions.
Try installing just the libc6-dev, then test the compile again.
Checking settings of: /etc/ppp/options
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
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:
slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 2007-09-06 00:48 /dev/ttySL0 -> /dev/pts/2
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/sl-modem-daemon.modutils: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)
/etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
