Maurizio,
scanModem detects that your modem is supported through slusb
slmodem-2.9.11-20* code. Follow instructions provided *** as per
ModemData.txt
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 002:
Modem chipset detected on
SLOT="Bus 002 Device 008:"
NAME="SGS Thomson Microelectronics 56k SoftModem"
bus=002
USBmodemID=0483:7554
IDENT=slusb
Driver=slusb
For a detailed USB cellphone usage report, see
http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html
For candidate modem in: 002
SGS Thomson Microelectronics 56k SoftModem
Primary device ID: 0483:7554
*** Support type needed or chipset: slusb
Writing DOCs/Intel.txt
*** There is a package sl-modem-source providing a source code the
modem driver slusb ,
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 slusb
plus the slmodemd helper utility. Read the
DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance.
For 3.8.0-30-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.g
z and slmodem-2.9.11-20080126.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
*** Look Here
*** There is a package sl-modem-source providing a source code the
modem driver slusb ,
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 Fri, Oct 11, 2013 at 11:15 AM, Maurizio Mastria
<mastria9howto@xxxxxxxxx> wrote:
> 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.8.0-30-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=k3.8.0
> Linux version 3.8.0-30-generic (buildd@allspice) (gcc version 4.6.3
> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41
> UTC 2013
> scanModem update of: 2011_08_08
>
> Distrib_ID=Ubuntu
> DistribCodeName=precise
> AptRepositoryStem=http://it.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_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 05ca:18c0 Ricoh Co., Ltd
> ID 0483:7554 SGS Thomson Microelectronics 56k SoftModem
> ID 046d:c52f Logitech, Inc. Wireless Mouse M305
> ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
> ID 0763:2024 Midiman M-Audio Fast Track MKII
> ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
> 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)
> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family
> High Definition Audio Controller (rev 04)
> 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 104d:9081 Communication controller: Intel
> Corporation 6 Series/C200 Series Chipset Family MEI Controller #1
>
> Modem interrupt assignment and sharing:
> 48: 12 0 0 0 PCI-MSI-edge mei
> --- Bootup diagnostics for card in PCI slot 00:16.0 ----
> [ 0.376749] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
> [ 0.376771] pci 0000:00:16.0: reg 10: [mem 0xf7d0a000-0xf7d0a00f 64bit]
> [ 0.376843] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
> [ 12.356759] mei 0000:00:16.0: setting latency timer to 64
> [ 12.356808] mei 0000:00:16.0: irq 48 for MSI/MSI-X
> [ 3730.648082] mei 0000:00:16.0: irq 48 for MSI/MSI-X
>
> 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 104d:9081 Audio device: Intel Corporation 6
> Series/C200 Series Chipset Family High Definition Audio Controller
>
> Modem interrupt assignment and sharing:
> 49: 665 0 0 0 PCI-MSI-edge
> snd_hda_intel
> --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> [ 0.377004] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
> [ 0.377018] pci 0000:00:1b.0: reg 10: [mem 0xf7d00000-0xf7d03fff 64bit]
> [ 0.377083] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
> [ 13.290623] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
> [ 13.388765] input: HDA Intel PCH HDMI/DP,pcm=3 as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
> [ 13.388847] input: HDA Intel PCH Mic as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
> [ 13.388912] input: HDA Intel PCH Headphone as
> /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
> [ 2045.469227] hda-intel 0000:00:1b.0: Unstable LPIB (65424 >= 32768);
> disabling LPIB delay counting
> [ 3730.648104] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
>
> 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 002:
> Modem chipset detected on
> SLOT="Bus 002 Device 008:"
> NAME="SGS Thomson Microelectronics 56k SoftModem"
> bus=002
> USBmodemID=0483:7554
> IDENT=slusb
> Driver=slusb
>
> For a detailed USB cellphone usage report, see
> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html
> For candidate modem in: 002
> SGS Thomson Microelectronics 56k SoftModem
> Primary device ID: 0483:7554
> Support type needed or chipset: slusb
>
>
>
> Writing DOCs/Intel.txt
>
> There is a package sl-modem-source providing a source code the modem driver
> slusb ,
> 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 slusb
> plus the slmodemd helper utility. Read the
> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through
> guidance.
>
>
> For 3.8.0-30-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=104d:9081
> IRQ=48
> 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=104d:9081
> IRQ=49
>
> 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:
>
>
>
> 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.8.0-30-generic resources needed for compiling are not
> manifestly ready!
>
> If compiling is necessary packages must be installed, providing:
> linux-headers-3.8.0-30-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 wlan0
> 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/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)
> /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 --------
