Hello,
I am using SmartLink Soft Modem: version 2.9.11 Feb 25 2008 18:25:57, with the snd_intel8x0m driver (see attached ModemData file), on Kubuntu 8.04.
Whenever I try to send a multi-page fax, using efax v 0.9a, the first page seems to be correctly sent:
[...]
efax: 31:53 sent 20+2292 lines, 51553+0 bytes, 29 s 14221 bps
efax: 31:53 command "+FTH=3"
efax: 31:53 waiting 3,1 s
efax: 31:53 .695 [CONNECT<CR><LF>]
efax: 31:53 response "CONNECT"
efax: 31:53 sent 3 bytes: ff c8 f2
efax: 31:53 sent MPS - not done
efax: 31:53 waiting 13,6 s
efax: 31:55 .015 [OK<CR><LF>]
efax: 31:55 response "OK"
efax: 31:55 command "+FRH=3"
efax: 31:55 waiting 3,0 s
efax: 31:55 .375 [CONNECT<CR><LF>]
efax: 31:55 response "CONNECT"
efax: 31:56 waiting 2,0 s
efax: 31:56 .375 [OK<CR><LF>]
efax: 31:56 response "OK"
efax: 31:56 received 5 bytes: ff c8 32 75 ec
efax: 31:56 received RTN - page not OK, check channel
efax: 31:56 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 31:56 remote 196lpi 14.4kbps 8.5"/215mm any 2D ECM-64 - 0ms
efax: 31:56 session 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 31:56 command "+FTH=3"
efax: 31:56 waiting 3,1 s
efax: 31:56 .455 [CONNECT<CR><LF>]
efax: 31:56 response "CONNECT"
efax: 31:56 sent 23 bytes:
efax: 31:56 ff c0 c2 cc 6c 0c 9c 0c ac 0c 0c ec 04 4c 0c 04
efax: 31:56 9c cc d4 04 04 04 04
efax: 31:56 sent TSI - caller ID
efax: 31:56 waiting 13,6 s
efax: 31:58 .295 [CONNECT<CR><LF>]
efax: 31:58 response "CONNECT"
efax: 31:58 sent 6 bytes: ff c8 c1 00 46 1e
efax: 31:58 sent DCS - session format
efax: 31:58 waiting 13,6 s
efax: 31:58 .675 [OK<CR><LF>]
efax: 31:58 response "OK"
efax: 31:58 command "+FTM=145"
efax: 31:58 waiting 3,1 s
efax: 31:58 .815 [CONNECT<CR><LF>]
efax: 31:58 response "CONNECT"
efax: 31:58 waiting 30,0 s
efax: 32:01 .975 [OK<CR><LF>]
efax: 32:01 response "OK"
efax: 32:01 sent TCF - channel check of 2700 bytes
efax: 32:01 command "+FRS=1"
efax: 32:01 waiting 3,0 s
efax: 32:02 .075 [OK<CR><LF>]
efax: 32:02 response "OK"
efax: 32:02 command "+FRH=3"
efax: 32:02 waiting 3,0 s
efax: 32:02 .355 [CONNECT<CR><LF>]
efax: 32:02 response "CONNECT"
efax: 32:03 waiting 2,0 s
efax: 32:03 .335 [OK<CR><LF>]
efax: 32:03 response "OK"
efax: 32:03 received 5 bytes: ff c8 21 57 be
efax: 32:03 received CFR - channel OK
efax: 32:03 command "+FTM=146"
efax: 32:03 waiting 3,1 s
efax: 32:03 .435 [CONNECT<CR><LF>]
efax: 32:03 response "CONNECT"
efax: 32:04 padding to 0 bytes/scan line.
the problem comes by the transmission of the second page:
efax: 32:04 header:[2008/06/28 17:26 +XXXXXXXXXXXXXXXXXXXXX. p. 2/4]
efax: 32:28 waiting 30,0 s
efax: 32:33 .076 [OK<CR><LF>]
efax: 32:33 response "OK"
efax: 32:33 sent 20+2292 lines, 51553+0 bytes, 29 s 14221 bps
efax: 32:33 command "+FTH=3"
efax: 32:33 waiting 3,1 s
efax: 32:33 .196 [CONNECT<CR><LF>]
efax: 32:33 response "CONNECT"
efax: 32:33 sent 3 bytes: ff c8 f2
efax: 32:33 sent MPS - not done
efax: 32:33 waiting 13,6 s
efax: 32:34 .516 [OK<CR><LF>]
efax: 32:34 response "OK"
efax: 32:34 command "+FRH=3"
efax: 32:34 waiting 3,0 s
efax: 32:34 .976 [CONNECT<CR><LF>]
efax: 32:34 response "CONNECT"
efax: 32:35 waiting 2,0 s
efax: 32:35 .956 [OK<CR><LF>]
efax: 32:35 response "OK"
efax: 32:35 received 5 bytes: ff c8 32 75 ec
efax: 32:35 received RTN - page not OK, check channel
efax: 32:35 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 32:35 remote 196lpi 14.4kbps 8.5"/215mm any 2D ECM-64 - 0ms
efax: 32:35 session 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 32:35 command "+FTH=3"
efax: 32:35 waiting 3,1 s
efax: 32:36 .036 [CONNECT<CR><LF>]
efax: 32:36 response "CONNECT"
efax: 32:36 sent 23 bytes:
efax: 32:36 ff c0 c2 cc 6c 0c 9c 0c ac 0c 0c ec 04 4c 0c 04
efax: 32:36 9c cc d4 04 04 04 04
efax: 32:36 sent TSI - caller ID
efax: 32:36 waiting 13,6 s
efax: 32:37 .876 [CONNECT<CR><LF>]
efax: 32:37 response "CONNECT"
efax: 32:37 sent 6 bytes: ff c8 c1 00 46 1e
efax: 32:37 sent DCS - session format
efax: 32:37 waiting 13,6 s
efax: 32:38 .256 [OK<CR><LF>]
efax: 32:38 response "OK"
efax: 32:38 command "+FTM=145"
efax: 32:38 waiting 3,1 s
efax: 32:38 .396 [CONNECT<CR><LF>]
efax: 32:38 response "CONNECT"
efax: 32:38 waiting 30,0 s
efax: 32:41 .556 [OK<CR><LF>]
efax: 32:41 response "OK"
efax: 32:41 sent TCF - channel check of 2700 bytes
efax: 32:41 command "+FRS=1"
efax: 32:41 waiting 3,0 s
efax: 32:41 .656 [OK<CR><LF>]
efax: 32:41 response "OK"
efax: 32:41 command "+FRH=3"
efax: 32:41 waiting 3,0 s
efax: 32:41 .936 [CONNECT<CR><LF>]
efax: 32:41 response "CONNECT"
efax: 32:42 waiting 2,0 s
efax: 32:42 .916 [OK<CR><LF>]
efax: 32:42 response "OK"
efax: 32:42 received 5 bytes: ff c8 21 57 be
efax: 32:42 received CFR - channel OK
efax: 32:42 command "+FTM=146"
efax: 32:42 waiting 3,1 s
efax: 32:43 .016 [CONNECT<CR><LF>]
efax: 32:43 response "CONNECT"
efax: 32:44 padding to 0 bytes/scan line.
efax: 32:44 header:[2008/06/28 17:26 +XXXXXXXXXXXXXXXXXXXXX. p. 2/4]
efax: 33:07 waiting 30,0 s
efax: 33:12 .657 [OK<CR><LF>]
efax: 33:12 response "OK"
efax: 33:12 sent 20+2292 lines, 51553+0 bytes, 28 s 14729 bps
efax: 33:12 command "+FTH=3"
efax: 33:12 waiting 3,1 s
efax: 33:12 .777 [CONNECT<CR><LF>]
efax: 33:12 response "CONNECT"
efax: 33:12 sent 3 bytes: ff c8 f2
efax: 33:12 sent MPS - not done
efax: 33:12 waiting 13,6 s
efax: 33:14 .097 [OK<CR><LF>]
efax: 33:14 response "OK"
efax: 33:14 command "+FRH=3"
efax: 33:14 waiting 3,0 s
efax: 33:14 .557 [CONNECT<CR><LF>]
efax: 33:14 response "CONNECT"
efax: 33:15 waiting 2,0 s
efax: 33:15 .537 [OK<CR><LF>]
efax: 33:15 response "OK"
efax: 33:15 received 5 bytes: ff c8 32 75 ec
efax: 33:15 received RTN - page not OK, check channel
efax: 33:15 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 33:15 remote 196lpi 14.4kbps 8.5"/215mm any 2D ECM-64 - 0ms
efax: 33:15 session 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 33:15 command "+FTH=3"
efax: 33:15 waiting 3,1 s
efax: 33:15 .617 [CONNECT<CR><LF>]
efax: 33:15 response "CONNECT"
efax: 33:15 sent 23 bytes:
efax: 33:15 ff c0 c2 cc 6c 0c 9c 0c ac 0c 0c ec 04 4c 0c 04
efax: 33:15 9c cc d4 04 04 04 04
efax: 33:15 sent TSI - caller ID
efax: 33:15 waiting 13,6 s
efax: 33:17 .457 [CONNECT<CR><LF>]
efax: 33:17 response "CONNECT"
efax: 33:17 sent 6 bytes: ff c8 c1 00 46 1e
efax: 33:17 sent DCS - session format
efax: 33:17 waiting 13,6 s
efax: 33:17 .837 [OK<CR><LF>]
efax: 33:17 response "OK"
efax: 33:17 command "+FTM=145"
efax: 33:17 waiting 3,1 s
efax: 33:17 .977 [CONNECT<CR><LF>]
efax: 33:17 response "CONNECT"
efax: 33:17 waiting 30,0 s
efax: 33:21 .137 [OK<CR><LF>]
efax: 33:21 response "OK"
efax: 33:21 sent TCF - channel check of 2700 bytes
efax: 33:21 command "+FRS=1"
efax: 33:21 waiting 3,0 s
efax: 33:21 .237 [OK<CR><LF>]
efax: 33:21 response "OK"
efax: 33:21 command "+FRH=3"
efax: 33:21 waiting 3,0 s
efax: 33:21 .517 [CONNECT<CR><LF>]
efax: 33:21 response "CONNECT"
efax: 33:22 waiting 2,0 s
efax: 33:22 .497 [OK<CR><LF>]
efax: 33:22 response "OK"
efax: 33:22 received 5 bytes: ff c8 21 57 be
efax: 33:22 received CFR - channel OK
efax: 33:22 command "+FTM=146"
efax: 33:22 waiting 3,1 s
efax: 33:22 .597 [CONNECT<CR><LF>]
efax: 33:22 response "CONNECT"
efax: 33:23 padding to 0 bytes/scan line.
efax: 33:23 header:[2008/06/28 17:26 +XXXXXXXXXXXXXXXXXXXXX. p. 2/4]
efax: 33:46 waiting 30,0 s
efax: 33:52 .238 [OK<CR><LF>]
efax: 33:52 response "OK"
efax: 33:52 sent 20+2292 lines, 51553+0 bytes, 29 s 14221 bps
efax: 33:52 command "+FTH=3"
efax: 33:52 waiting 3,1 s
efax: 33:52 .358 [CONNECT<CR><LF>]
efax: 33:52 response "CONNECT"
efax: 33:52 sent 3 bytes: ff c8 f2
efax: 33:52 sent MPS - not done
efax: 33:52 waiting 13,6 s
efax: 33:53 .678 [OK<CR><LF>]
efax: 33:53 response "OK"
efax: 33:53 command "+FRH=3"
efax: 33:53 waiting 3,0 s
efax: 33:54 .138 [CONNECT<CR><LF>]
efax: 33:54 response "CONNECT"
efax: 33:55 waiting 2,0 s
efax: 33:55 .118 [OK<CR><LF>]
efax: 33:55 response "OK"
efax: 33:55 received 5 bytes: ff c8 32 75 ec
efax: 33:55 received RTN - page not OK, check channel
efax: 33:55 local 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 33:55 remote 196lpi 14.4kbps 8.5"/215mm any 2D ECM-64 - 0ms
efax: 33:55 session 196lpi 14.4kbps 8.5"/215mm any 1D - - 0ms
efax: 33:55 command "+FTH=3"
efax: 33:55 waiting 3,1 s
efax: 33:55 .198 [CONNECT<CR><LF>]
efax: 33:55 response "CONNECT"
efax: 33:55 sent 23 bytes:
efax: 33:55 ff c0 c2 cc 6c 0c 9c 0c ac 0c 0c ec 04 4c 0c 04
efax: 33:55 9c cc d4 04 04 04 04
efax: 33:55 sent TSI - caller ID
efax: 33:55 waiting 13,6 s
efax: 33:57 .038 [CONNECT<CR><LF>]
efax: 33:57 response "CONNECT"
efax: 33:57 sent 6 bytes: ff c8 c1 00 46 1e
efax: 33:57 sent DCS - session format
efax: 33:57 waiting 13,6 s
efax: 33:57 .418 [OK<CR><LF>]
efax: 33:57 response "OK"
efax: 33:57 command "+FTM=145"
efax: 33:57 waiting 3,1 s
efax: 33:57 .558 [CONNECT<CR><LF>]
efax: 33:57 response "CONNECT"
efax: 33:57 waiting 30,0 s
efax: 34:00 .718 [OK<CR><LF>]
efax: 34:00 response "OK"
efax: 34:00 sent TCF - channel check of 2700 bytes
efax: 34:00 command "+FRS=1"
efax: 34:00 waiting 3,0 s
efax: 34:00 .818 [OK<CR><LF>]
efax: 34:00 response "OK"
efax: 34:00 command "+FRH=3"
efax: 34:00 waiting 3,0 s
efax: 34:01 .098 [CONNECT<CR><LF>]
efax: 34:01 response "CONNECT"
efax: 34:02 waiting 2,0 s
efax: 34:02 .058 [OK<CR><LF>]
efax: 34:02 response "OK"
efax: 34:02 received 5 bytes: ff c8 21 57 be
efax: 34:02 received CFR - channel OK
efax: 34:02 command "+FTM=146"
efax: 34:02 waiting 3,1 s
efax: 34:02 .158 [CONNECT<CR><LF>]
efax: 34:02 response "CONNECT"
efax: 34:03 padding to 0 bytes/scan line.
efax: 34:03 header:[2008/06/28 17:26 +XXXXXXXXXXXXXXXXXXXXX. p. 2/4]
efax: 34:05 Error: terminating on signal 2
then I have to manually interrupt the process, in order to avoid an endless loop...
Any help will be highly appreciated!
Federico
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.24-17-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.24-17-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu May 1 14:31:33 UTC 2008
scanModem update of: 2008_05_30
There are no blacklisted modem drivers in /etc/modprobe* files
USB modems not recognized
For candidate card in slot 00:1e.3, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1e.3 8086:266d 14c0:0012 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
Modem interrupt assignment and sharing:
17: 2 IO-APIC-fasteoi ohci1394
--- Bootup diagnostics for card in PCI slot 00:1e.3 ----
[ 13.266684] ACPI: PCI Interrupt 0000:00:1e.3[B] -> GSI 20 (level, low) -> IRQ 17
[ 13.266693] ACPI: PCI interrupt for device 0000:00:1e.3 disabled
The PCI slot 00:1e.3 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.15
The modem cards detected by "aplay -l" are: None
The /proc/asound/pcm file reports:
-----------------------
00-04: Intel ICH - IEC958 : Intel ICH6 - IEC958 : playback 1
00-03: Intel ICH - ADC2 : Intel ICH6 - ADC2 : capture 1
00-02: Intel ICH - MIC2 ADC : Intel ICH6 - MIC2 ADC : capture 1
00-01: Intel ICH - MIC ADC : Intel ICH6 - MIC ADC : capture 1
00-00: Intel ICH : Intel ICH6 : playback 1 : capture 1
about /proc/asound/cards:
------------------------
0 [ICH6 ]: ICH4 - Intel ICH6
Intel ICH6 with ALC250 at irq 22
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 00:1e.3:
Modem chipset detected on
CLASS="Class 0703: 8086:266d"
NAME="Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW "
SUBSYS=14c0:0012
PCIDEV=8086:266d
IRQ=17
SOFT=8086:266d.MC97
CodecArchived=SIL27
IDENT=slmodemd
SLMODEMD_DEVICE=modem:1
Driver=snd-intel8x0m
For candidate modem in: 00:1e.3
Class 0703: 8086:266d Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW
Primary device ID: 8086:266d
Subsystem PCI_id 14c0:0012
Softmodem codec or chipset from diagnostics:
from Archives: SIL27, an LSI/AgereSystems type
Support type needed or chipset: slmodemd
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-intel8x0m
provides Low Level support enabling contact with the modem hardware.
For all BUT Conexant chip soft modems (using hsfmodem software)
complementary High Level support is through a Smartlink utility: slmodemd
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.2.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.2.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
----------------end Softmodem section --------------
Writing DOCs/Intel.txt
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-17-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 libc6-dev (and for Debian/Ubuntu,
linux-libc-dev). 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/linux-source-2.6.24.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-- 1 root dip 269256 2007-10-04 21:57 /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 ra0
Which can interfere with Browser naviagation.
Don't worry about the following, it is for experts should trouble shooting be necessary.
==========================================================
# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Checking for modem support lines:
--------------------------------------
/device/modem symbolic link:
slmodemd created symbolic link /dev/ttySL0:
Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
Within /etc/modprobe.conf files:
/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
/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:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base: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 --------
