--
Este mensaje le ha llegado mediante el servicio de correo electronico que ofrece Infomed para respaldar el cumplimiento de las misiones del Sistema Nacional de Salud. La persona que envia este correo asume el compromiso de usar el servicio a tales fines y cumplir con las regulaciones establecidas
Infomed: http://www.sld.cu/
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 3.2.0-23-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=x86_64, Ubuntu , ALSA_version=1.0.24
Linux version 3.2.0-23-generic (buildd@crested) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
scanModem update of: 2011_08_08
Distrib_ID=Ubuntu
DistribCodeName=precise
AptRepositoryStem=http://archive.ubuntu.com/ubuntu/
The dkms driver upgrade utilities are installed,
Some modem drivers can only be used in 32 bit modem on x86_64 systems,
while some others are competent on x86_64 Systems. Cases are:
1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem controllers.
In both cases, 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component.
2) For USB modems using the slusb.ko driver. 32 bit libraries must be installed to support the slmodemd helper having a precompiled 32 bit component
3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are x86_64 competent.
4) agrsm packages for LSI/AgereSystems softmodems are not competent on x86_64 systems.
There are no blacklisted modem drivers in /etc/modprobe* files
Potentially useful modem drivers now loaded are:
snd_atiixp_modem snd_via82xx_modem snd_intel8x0m snd_hda_intel
Attached USB devices are:
ID 08ec:0008 M-Systems Flash Disk Pioneers TravelDrive 2C
ID 046d:c018 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:
00:03.0 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller (rev 02)
07:01.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV620 HDMI Audio [Radeon HD 3400 Series]
High Definition Audio cards can host modem chips.
For candidate card in slot 00:03.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:03.0 8086:29c4 8086:5044 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Modem interrupt assignment and sharing:
49: 4 4 PCI-MSI-edge mei
--- Bootup diagnostics for card in PCI slot 00:03.0 ----
[ 1.164347] pci 0000:00:03.0: [8086:29c4] type 0 class 0x000780
[ 1.164359] pci 0000:00:03.0: reg 10: [mem 0xe0722100-0xe072210f 64bit]
[ 1.164398] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
[ 1.164401] pci 0000:00:03.0: PME# disabled
[ 1.166629] pci 0000:03:00.0: [11ab:6101] type 0 class 0x000101
[ 1.166644] pci 0000:03:00.0: reg 10: [io 0x2018-0x201f]
[ 1.166656] pci 0000:03:00.0: reg 14: [io 0x2024-0x2027]
[ 1.166667] pci 0000:03:00.0: reg 18: [io 0x2010-0x2017]
[ 1.166679] pci 0000:03:00.0: reg 1c: [io 0x2020-0x2023]
[ 1.166691] pci 0000:03:00.0: reg 20: [io 0x2000-0x200f]
[ 1.166702] pci 0000:03:00.0: reg 24: [mem 0xe0500000-0xe05001ff]
[ 1.166765] pci 0000:03:00.0: supports D1
[ 1.166767] pci 0000:03:00.0: PME# supported from D0 D1 D3hot
[ 1.166771] pci 0000:03:00.0: PME# disabled
[ 1.166787] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 3.277616] pata_acpi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3.277680] pata_acpi 0000:03:00.0: setting latency timer to 64
[ 3.277694] pata_acpi 0000:03:00.0: PCI INT A disabled
[ 3.876335] pata_marvell 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 3.876424] pata_marvell 0000:03:00.0: setting latency timer to 64
[ 22.977335] mei 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 22.977341] mei 0000:00:03.0: setting latency timer to 64
[ 22.977391] mei 0000:00:03.0: irq 49 for MSI/MSI-X
The PCI slot 00:03.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.
For candidate card in slot 07:01.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
07:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 07:01.0 ----
[ 1.167240] pci 0000:07:01.0: [1057:3052] type 0 class 0x000703
[ 1.167257] pci 0000:07:01.0: reg 10: [mem 0xe0400000-0xe0400fff]
[ 1.167267] pci 0000:07:01.0: reg 14: [io 0x1000-0x10ff]
[ 1.167336] pci 0000:07:01.0: PME# supported from D0 D3hot D3cold
[ 1.167340] pci 0000:07:01.0: PME# disabled
[ 3.236127] serial 0000:07:01.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 3.236198] serial 0000:07:01.0: PCI INT A disabled
The PCI slot 07:01.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.
For candidate card in slot 01:00.1, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:00.1 1002:aa28 174b:aa28 Audio device: Advanced Micro Devices [AMD] nee ATI RV620 HDMI Audio [Radeon HD 3400 Series]
Modem interrupt assignment and sharing:
50: 94 94 PCI-MSI-edge snd_hda_intel
--- Bootup diagnostics for card in PCI slot 01:00.1 ----
[ 1.166363] pci 0000:01:00.1: [1002:aa28] type 0 class 0x000403
[ 1.166375] pci 0000:01:00.1: reg 10: [mem 0xe0610000-0xe0613fff 64bit]
[ 1.166432] pci 0000:01:00.1: supports D1 D2
[ 24.995626] snd_hda_intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 24.995693] snd_hda_intel 0000:01:00.1: irq 50 for MSI/MSI-X
[ 24.995717] snd_hda_intel 0000:01:00.1: setting latency timer to 64
[ 25.122399] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input4
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 07:01.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=22
IDENT=slamr
For candidate modem in: 07:01.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
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/archive-seventh/msg00846.html
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
and Alvaro Aguirre about the ungrab-winmodem fix:
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.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.2.0-23-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:03.0:
Modem chipset not detected on
NAME="Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller "
CLASS=0780
PCIDEV=8086:29c4
SUBSYS=8086:5044
IRQ=49
HDA2=01:00.1
For candidate modem in: 00:03.0
0780 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller
Primary device ID: 8086:29c4
Support type needed or chipset:
Predictive diagnostics for card in bus 01:00.1:
Modem chipset not detected on
NAME="Audio device: Advanced Micro Devices [AMD] nee ATI RV620 HDMI Audio [Radeon HD 3400 Series]"
CLASS=0403
PCIDEV=1002:aa28
SUBSYS=174b:aa28
IRQ=50
For candidate modem in: 01:00.1
0403 Audio device: Advanced Micro Devices [AMD] nee ATI RV620 HDMI Audio [Radeon HD 3400 Series]
Primary device ID: 1002:aa28
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.6.3
and the compiler used in kernel assembly: 4.6
linux-headers-3.2.0-23-generic resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
linux-headers-3.2.0-23-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 325744 Feb 4 2011 /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
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.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/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/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 --------
