Lazaro, 1057:3052 chipsets do indeed need slamr+ungrab-winmodem drivers + slmodemd support. This is a happy support accident reflecting how little many winmodems differ, and not a planned feature of slmodem code. There are 2 forward routes. 1) The best is to provide if possible the deb packages for dkms, sl-modem-deamon & sl-modem-source (as the latter now has dkms support for auto upgrades). Thus once installed upgrades with future kernels will be automatic. 2) If this cannot be done, the compilation and installation with ungrab-winmodem and slmodem resources can be done. Once online: $ sudo apt-get update $ sudo apt-get install dkms sl-modem-deamon sl-modem-source to then achieve the same result of 1) Note that the driver loading under 2) is not automated. So there must manually be done after ever bootup $ sudo modprobe ungrab-winmodem The $ sudo make install step in the slmodem source package $ sudo slmodemd -c USA /dev/slamr0 to activate the modem. Also beyond our control, between each dialout under a single boot, one must $ Ctrl-C to stop wvdial In the console used to activate the modem $ Ctrl-C to stop slmodemd $ sudo modprobe -r slamr Restart With: $ modprobe slamr $ slmodemd -c USA /dev/slarm0 Once the sl-modem-daemon package is installed, the above steps are automated by: $ sudo /etc/init.d/sl-modem-daemon restart MarvS 2010/7/16 "Dr. Lázaro J. Rojas Sopo" <lazaro.rojas@xxxxxxxxxxxxxx>: > Hi Marv, hope you and your family are doing all right. This request of > assistance is for a friend, Alex, not Alex Ochoa, but another one, (a very > common name here), he has an SM56 Motorola modem (same as Cary as I recall), > but under kernel 2.6.32-24-generic. > According to my interpretation of your scanModem ModemData.txt, which I > attach, he needs: > slamr-2.6.32-24-generic driver (which I don't know whether or not exists), > the slamr-2.6.X in the CD you sent me reaches .31-14-generic, and > slmodem-2.9.X-Y.tar.gz + ungrab-winmodem-Z.tar.gz I'm not sure which one to > use. > You've got to teach me how to correctly interprete ModemData.txt issues, so > I'd be less bothersome. > I'd like you to chech his ModemData.txt and assist me with him if posssible. > Regards. > Lázaro. > > > > -- > > 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 2.6.32-24-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=i686, Ubuntu , ALSA_version=1.0.23 > Linux version 2.6.32-24-generic (buildd@vernadsky) (gcc version 4.4.3 > (Ubuntu 4.4.3-4ubuntu5) ) #38-Ubuntu SMP Mon Jul 5 09:22:14 UTC 2010 > scanModem update of: 2010_04_29 > > Distrib_ID=Ubuntu > DistribCodeName=lucid > > > 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: > > > Attached USB devices are: > ID 03f0:0901 Hewlett-Packard ScanJet 2300c > ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard > 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: > 02:01.0 Modem: Motorola SM56 Data Fax Modem (rev 04) > High Definition Audio cards can host modem chips. > > For candidate card in slot 02:01.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 02:01.0 1057:3052 1057:3020 Modem: Motorola SM56 Data > Fax Modem > > Modem interrupt assignment and sharing: > --- Bootup diagnostics for card in PCI slot 02:01.0 ---- > [ 0.222345] pci 0000:02:01.0: reg 10 32bit mmio: [0xfa000000-0xfa000fff] > [ 0.222357] pci 0000:02:01.0: reg 14 io port: [0xa000-0xa0ff] > [ 0.222413] pci 0000:02:01.0: PME# supported from D0 D3hot D3cold > [ 0.222420] pci 0000:02:01.0: PME# disabled > [ 0.320237] serial 0000:02:01.0: PCI INT A -> GSI 21 (level, low) -> IRQ > 21 > [ 0.320499] 0000:02:01.0: ttyS2 at I/O 0xa008 (irq = 21) is a 16450 > [ 0.320647] 0000:02:01.0: ttyS3 at I/O 0xa010 (irq = 21) is a 8250 > [ 0.320699] Couldn't register serial port 0000:02:01.0: -28 > > The PCI slot 02: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. > > > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > Predictive diagnostics for card in bus 02:01.0: > Modem chipset detected on > NAME="Modem: Motorola SM56 Data Fax Modem " > CLASS=0703 > PCIDEV=1057:3052 > SUBSYS=1057:3020 > IRQ=21 > IDENT=slamr > > For candidate modem in: 02: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 > > 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 2.6.32-24-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 ===================== > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.4.3 > and the compiler used in kernel assembly: 4.4.3 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.4 > linuc_headers base folder /lib/modules/2.6.32-24-generic/build > > However some compilations and executable functions may need additional > files, > in the FileNames.h (so called kernel "h"eaders) collection installed in > /usr/include/ . > For martian_modem, additional required packages are needed. The also > required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev > packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at > http://packages.ubuntu.com > or comparable Repository for other Linux distros. > When compiling ALSA drivers, the utility "patch" will also be needed. > > > > > 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 273312 2010-03-06 22:59 /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 > proxyarp > 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 -------- > > > >
