Oye, muchísimas gracias por la ayuda, la verdad es que entre tanta gente que proponía cambiar de modem para solucionar el problema estaba empezando a perder las esperanzas. Lo del problema de recursos era solo un intento desesperado por probar algo que pudiera solucionar el problema, no obstante sería bueno saberlo para futuras situaciones en que realmente lo necesite. Muchas gracias nuevamente por la ayuda y el dato sobre scanModem en español ....
... Salu2 Homer
Seguí las instrucciones que me das paso a paso y aquí posteo el resultado de ModemData.txt:
Only plain text email is forwarded by the
Discuss@Linmodems.org List Server,
as HTML can contain viruses. Use as the email Subject Line:
YourName, YourCountry kernel 3.8.0-19-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@Linmodems.org 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, Ubuntu , ALSA_version=k3.8.0
Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013
scanModem update of: 2011_08_08
Distrib_ID=Ubuntu
DistribCodeName=raring
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 059b:047a Iomega Corp. Select Portable Hard Drive
ID 046d:c52e Logitech, Inc.
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 ... 00578.html
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to
discuss@linmodems.org
Candidate PCI devices with modem chips are:
03:00.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)
High Definition Audio cards can host modem chips.
For candidate card in slot 03:00.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
03:00.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 03:00.0 ----
[ 0.096065] pci 0000:03:00.0: [1057:3052] type 00 class 0x070300
[ 0.096084] pci 0000:03:00.0: reg 10: [mem 0xe1200000-0xe1200fff]
[ 0.096095] pci 0000:03:00.0: reg 14: [io 0xd000-0xd0ff]
[ 0.096167] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
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 NM10/ICH7 Family High Definition Audio Controller
Modem interrupt assignment and sharing:
43: 903 901 PCI-MSI-edge snd_hda_intel
--- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[ 0.085026] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
[ 0.085038] pci 0000:00:1b.0: reg 10: [mem 0xe1380000-0xe1383fff 64bit]
[ 0.085095] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 16.346581] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
[ 16.375901] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
[ 16.376061] input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[ 16.376195] input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 16.376325] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 16.376456] input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 03:00.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=20
HDA2=00:1b.0
IDENT=slamr
For candidate modem in: 03:00.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 ... 00846.html
http://linmodems.technion.ac.il/bigarch ... 00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch ... 00990.html
For general guidance on ungrab-winmodem + slamr usage, read the DOCs/Smartlink.txt
There is a package sl-modem-source providing a source code the modem driver ,
If can be searched for at
http://pacakge.ubuntu.com. After downloading install under Linux with:
$ sudo dpkg -i sl*.deb
It is preferable to install the dkms package first.
With DKMS support installed, driver updates with kernel updates will be automatically done.
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 3.8.0-19-generic compiling drivers is necessary. As of October 2007 the current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz
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 NM10/ICH7 Family High Definition Audio Controller "
CLASS=0403
PCIDEV=8086:27d8
SUBSYS=1458:a002
IRQ=43
For candidate modem in: 00:1b.0
0403 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller
Primary device ID: 8086:27d8
Support type needed or chipset:
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.7.3
and the compiler used in kernel assembly: 4.7
linux-headers-3.8.0-19-generic resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
linux-headers-3.8.0-19-generic
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 322968 Jan 22 2013 /usr/sbin/pppd
In case of an "error 17" "serial loopback" problem, see:
http://linmodems.technion.ac.il/linmode ... 02637.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
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 ... 04656.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.
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
/etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0)
/etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0)
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
. Llevo días tratando de instalar mi modem (Motorola SM56 Data Fax Modem) pero no he conseguido ningún resultado, leí el paper de Javier y en la parte del wvdialconfig me sale que no encuentra el modem. En windows hubo un tiempo en que no me reconocía el modem porque había problemas con los recursos entre este y otro dispositivo ethernet, al parecer la tarjeta de red integrada al board pero se soluciono sin problemas. Por favor si alguien sabe como resolver este problema en linux me haría un gran favor. Gracias por adelantado!!!
