Luc,
This is copy of scanModem that you have sent me, inline:
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.32-5-686
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, debian , ALSA_version=1.0.21
Linux version 2.6.32-5-686 (Debian 2.6.32-31) (ben@xxxxxxxxxxxxxxx)
(gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC
2011
scanModem update of: 2011_02_04
/etc/lsb-release not found
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:
cdc_acm
Attached USB devices are:
ID 04c1:3021 U.S. Robotics (3Com) 56k Voice FaxModem Pro
ID 046d:c00c Logitech, Inc. Optical Wheel Mouse
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
Candidate PCI devices with modem chips are:
High Definition Audio cards can host modem chips.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
A candidate modem is not transparent among the PCI devices:
------------------------------------------------
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
65x/M650/740 PCI/AGP VGA Display Adapter
------------------------------------------------
with USB, bridge, and RAM devices not displayed.
If a High Definition Audio card is present, if might be hosted on the Subsystem.
If your modem is an
external USB type,
connected by an external serial cable,
or mounted internally on an ISA card,
then scanModem would not access it.
Try with Root permission
$ wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
gedit /etc/wvdial.conf
will be able to dial out with Root permission:
wvdial
Many modems for which scanModem fails have Conexant chips.
From http://www.linuxant.com/drivers/modemident.php
get the ListModem tool, which will report on Conexant chipset modems
If the above tests fail, please provide any independent information
available on your modem.
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. From the Driver Details TAB, copy out the
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.
The base of the UDEV device file system is: /dev/.udev
The kernel was compiled with gcc version 4.3.5 and a compiler is not installed
linux-headers-2.6.32-5-686 resources needed for compiling are not
manifestly ready!
If compiling is necessary packages must be installed, providing:
gcc-4.3 linux-headers-2.6.32-5-686
For Debian and some related distributions, a package
kernel-kbuild-2.6-32 may be needed to support driver compiling.
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 273568 Aug 8 2010 /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
asyncmap 0
auth
crtscts
lock
hide-password
modem
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
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/alsa-base-blacklist.conf:# Uncomment these entries in
order to blacklist unwanted modem drivers
/etc/modprobe.d/alsa-base-blacklist.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist.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 --------
For Debian users, the linux-headers-2.6.32-5-686.deb can be used
instead of kernel-source/
===================================================================
The driver for your modem is apparently loaded:
Potentially useful modem drivers now loaded are:
cdc_acm
Have you run:
If your modem is an
external USB type,
connected by an external serial cable,
or mounted internally on an ISA card,
then scanModem would not access it.
Try with Root permission
$ wvdialconf /etc/wvdial.conf
to detect these modem types and some USB modems.
If the detection is successful, read the DOCs/wvdial.txt .
Edit the /etc/wvdial.conf with Root permission:
gedit /etc/wvdial.conf
will be able to dial out with Root permission:
wvdial
Run the above comands and send to list not directly to me. I get the
mail too, you can CC me. This way other people can help you too.
Regards,
Antonio
On Fri, May 6, 2011 at 12:52 PM, Luc Filiatrault <luc@xxxxxxxxx> wrote:
> Hi,
> Here is the complete file you requested attached to this message.
> Cheers,
>
> On Fri, 2011-05-06 at 08:48 -0500, Antonio Olivares wrote:
>> Luc,
>>
>> Please download scanModem and copy it to your linux partition. Then
>> $ gunzip scanModem.gz
>> $ chmod +x scanModem
>> $ sudo ./scanModem
>> or
>> $ su -
>> passwd
>> # cd to-where-scanModem-is
>> # ./scanModem
>>
>> send us ModemData.txt only. Alternatively, you could run
>> $ sudo lsusb
>> and see if there's a way to find out something about your modem, if it
>> is a usb modem it could be supported natively try to see if wvdial
>> finds it
>> $ sudo wvdialconf /etc/wvdial.conf
>> it may find your modem?, in the case that it does you could see that
>> your port is /dev/ttyACM0 or /dev/ttyUSB0 or similar.
>> This hopefully could determine if your modem is supported or not.
>> Then for faxing, there are other issues to deal with.
>>
>> Regards,
>>
>> Antonio
>>
>> On Fri, May 6, 2011 at 8:39 AM, Luc Filiatrault <luc@xxxxxxxxx> wrote:
>> > Attached USB devices are:
>> > ID 04c1:3021 U.S. Robotics (3Com) 56k Voice FaxModem Pro
>> >
>> > I only need this modem to send faxes.
>> >
>> > Thanks,
>> >
>> >
>> >
>> >
>
>
