Tony,
scanModem reports that you have a modem that would be supported under
32 bit linux by slamr + ungrab-winmodem,
or candidate card in slot 04:01.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
04:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 04:01.0 ----
[ 0.440719] pci 0000:04:01.0: [1057:3052] type 0 class 0x000703
[ 0.440754] pci 0000:04:01.0: reg 10: [mem 0xf7c00000-0xf7c00fff]
[ 0.440773] pci 0000:04:01.0: reg 14: [io 0xd000-0xd0ff]
[ 0.440923] pci 0000:04:01.0: PME# supported from D0 D3hot
[ 0.440929] pci 0000:04:01.0: PME# disabled
[ 0.680599] serial 0000:04:01.0: enabling device (0080 -> 0083)
[ 0.680612] serial 0000:04:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 0.680671] serial 0000:04:01.0: PCI INT A disabled
The PCI slot 04: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.
If you install 32 bit linux, you could follow the directions provided
by scanModem to get your modem functioning.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 04:01.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=18
IDENT=slamr
For candidate modem in: 04:01.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/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-52-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 =====================
If you install 32 bit Ubuntu, you can hunt down the slamr +
ungrab-winmodem package. if you do please install dkms package, for
automated installations after kernel upgrades:
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.
Best Regards,
Antonio
On Thu, Oct 24, 2013 at 4:07 AM, Tanapon Luangaroonlerd
<tanaponl@xxxxxxxxx> wrote:
> -------------------------- System information ----------------------------
> CPU=x86_64, Ubuntu , ALSA_version=1.0.24
> Linux version 3.2.0-52-generic (buildd@roseapple) (gcc version 4.6.3
> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #78-Ubuntu SMP Fri Jul 26 16:21:44
> UTC 2013
> scanModem update of: 2011_08_08
>
> Distrib_ID=Ubuntu
> DistribCodeName=precise
> AptRepositoryStem=http://th.archive.ubuntu.com/ubuntu/
>
>
> 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
>
>
> 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_hda_intel
>
> Attached USB devices are:
> ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> ID 04f9:0187 Brother Industries, Ltd FAX-2820 Printer
> ID 04f3:0210 Elan Microelectronics Corp. AM-400 Hama Optical 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:16.0 Communication controller: Intel Corporation 6 Series/C200
> Series Chipset Family MEI Controller #1 (rev 04)
> 04:01.0 Modem: Motorola SM56 Data Fax Modem (rev 04)
> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
> Family High Definition Audio Controller (rev 05)
> High Definition Audio cards can host modem chips.
>
> For candidate card in slot 00:16.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:16.0 8086:1c3a 1458:1c3a Communication controller: Intel
> Corporation 6 Series/C200 Series Chipset Family MEI Controller #1
>
> Modem interrupt assignment and sharing:
> 41: 13 0 PCI-MSI-edge mei
> --- Bootup diagnostics for card in PCI slot 00:16.0 ----
> [ 0.433958] pci 0000:00:16.0: [8086:1c3a] type 0 class 0x000780
> [ 0.433979] pci 0000:00:16.0: reg 10: [mem 0xf7d09000-0xf7d0900f 64bit]
> [ 0.434050] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
> [ 0.434054] pci 0000:00:16.0: PME# disabled
> [ 11.666454] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 11.666458] mei 0000:00:16.0: setting latency timer to 64
> [ 11.666505] mei 0000:00:16.0: irq 41 for MSI/MSI-X
>
> The PCI slot 00:16.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 04:01.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 04:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
>
> Modem interrupt assignment and sharing:
> --- Bootup diagnostics for card in PCI slot 04:01.0 ----
> [ 0.440719] pci 0000:04:01.0: [1057:3052] type 0 class 0x000703
> [ 0.440754] pci 0000:04:01.0: reg 10: [mem 0xf7c00000-0xf7c00fff]
> [ 0.440773] pci 0000:04:01.0: reg 14: [io 0xd000-0xd0ff]
> [ 0.440923] pci 0000:04:01.0: PME# supported from D0 D3hot
> [ 0.440929] pci 0000:04:01.0: PME# disabled
> [ 0.680599] serial 0000:04:01.0: enabling device (0080 -> 0083)
> [ 0.680612] serial 0000:04:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [ 0.680671] serial 0000:04:01.0: PCI INT A disabled
>
> The PCI slot 04: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 00:1b.0, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:1b.0 8086:1c20 1458:a002 Audio device: Intel Corporation 6
> Series/C200 Series Chipset Family High Definition Audio Controller
>
> Modem interrupt assignment and sharing:
> 43: 3329 272 PCI-MSI-edge snd_hda_intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [ 0.434211] pci 0000:00:1b.0: [8086:1c20] type 0 class 0x000403
> [ 0.434224] pci 0000:00:1b.0: reg 10: [mem 0xf7d00000-0xf7d03fff 64bit]
> [ 0.434287] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [ 0.434290] pci 0000:00:1b.0: PME# disabled
> [ 12.123503] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002)
> [ 12.123518] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
> low) -> IRQ 22
> [ 12.123565] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
> [ 12.123587] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
> [ 12.169552] input: HDA Intel PCH Line as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
> [ 12.169623] input: HDA Intel PCH Front Mic as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
> [ 12.169726] input: HDA Intel PCH Rear Mic as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
> [ 12.169808] input: HDA Intel PCH Front Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
> [ 12.169927] input: HDA Intel PCH Line-Out as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
>
> The PCI slot 00:1b.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.
>
>
> === Finished firmware and bootup diagnostics, next deducing cogent software. ===
>
> Predictive diagnostics for card in bus 04:01.0:
> Modem chipset detected on
> NAME="Modem: Motorola SM56 Data Fax Modem "
> CLASS=0703
> PCIDEV=1057:3052
> SUBSYS=1057:3020
> IRQ=18
> IDENT=slamr
>
> For candidate modem in: 04:01.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/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-52-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:16.0:
> Modem chipset not detected on
> NAME="Communication controller: Intel Corporation 6 Series/C200 Series
> Chipset Family MEI Controller #1 "
> CLASS=0780
> PCIDEV=8086:1c3a
> SUBSYS=1458:1c3a
> IRQ=41
> HDA2=00:1b.0
>
> For candidate modem in: 00:16.0
> 0780 Communication controller: Intel Corporation 6 Series/C200
> Series Chipset Family MEI Controller #1
> Primary device ID: 8086:1c3a
> Support type needed or chipset:
>
>
>
> Predictive diagnostics for card in bus 00:1b.0:
> Modem chipset not detected on
> NAME="Audio device: Intel Corporation 6 Series/C200 Series Chipset
> Family High Definition Audio Controller "
> CLASS=0403
> PCIDEV=8086:1c20
> SUBSYS=1458:a002
> IRQ=43
>
> For candidate modem in: 00:1b.0
> 0403 Audio device: Intel Corporation 6 Series/C200 Series Chipset
> Family High Definition Audio Controller
> Primary device ID: 8086:1c20
> 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-52-generic resources needed for compiling are not
> manifestly ready!
>
> If compiling is necessary packages must be installed, providing:
> linux-headers-3.2.0-52-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 ก.พ. 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/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
> Within any ancient /etc/devfs files:
>
> Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
