Cary & Lazaro Please help with and translation issues. Juan, You and Ivan have the same Motorola modem hardwasre Currently it cannot be supported after 2.6.28 kernels. However 2.6.28 kernels are supported on your Ubuntu Karmic installation. Download under Microsoft from http://mirror.ucf.edu.cu the packages: http://mirror.ucf.edu.cu/ubuntu/pool/main/g/grub2/grub-pc_1.96+20080724-12ubuntu2_i386.deb http://mirror.ucf.edu.cu/ubuntu/pool/main/g/grub2/grub-common_1.96+20080724-12ubuntu2_i386.deb http://mirror.ucf.edu.cu/ubuntu/pool/main/l/linux/linux-headers-2.6.24-16-generic_2.6.24-16.30_i386.deb http://mirror.ucf.edu.cu/ubuntu/pool/restricted/s/sl-modem/sl-modem-daemon_2.9.11~20080817-3ubuntu3_i386.deb http://mirror.ucf.edu.cu/ubuntu/pool/multiverse/u/unrar-nonfree/unrar_3.9.3-1_i386.deb Under Ubuntu all these package can be co-installed, by commanding in the folder where they are located: $ sudo dpkg -i *.deb Do not yet use the slamrIv.rar package. First reboot, using the new 2.6.24-16-generic kernel choice (which hopefully will be visible because of the grub upgrade). Next unpack: $ unrar slamrIv.rar In the new folder unpacked, browse, then run: $ sudo ./setup Folow the output instructions and included documentation. MarvS You and Ivan have the same modem. He can give you a slamrIv.rar package already provided to him, but I'll try to send it to your too. After unpacking it Your > Your modem is not supported for kernels >= 2.6.31 kernels like you have :( > > For kernels 2.6.31 the slamr driver is not (yet) functional, failing > within at the > Carrier Check > function. Thus for service, retain a 2.6.30 or earlier kernel. For this > can be done by downloading the kernel from > http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic > and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ the > slamr-2.6.28-16-generic.tar.gz On Fri, Jan 29, 2010 at 3:08 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Juan, > > Your modem is not supported for kernels >= 2.6.31 kernels like you have :( > > For kernels 2.6.31 the slamr driver is not (yet) functional, failing > within at the > Carrier Check > function. Thus for service, retain a 2.6.30 or earlier kernel. For > Ubuntu users this > can be done by downloading the kernel from > http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic > and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ the > slamr-2.6.28-16-generic.tar.gz > > Tu modem no funciona con el kernel que corre tu computadora. Para > poder hacer que funcione necesitaras instalar un kernel previo. > Your modem does not work with the kernel that you machine is running. > To make it functional you need to install an earlier kernel like > previous paragraph states. > > Tambien no tienes el archivo wvdial. You don't have wvdial installed: > > The dialer utility package WVDIAL does not appear to be installed on > your System. > For Ubuntu users, there are at the bottom of > http://linmodems.technion.ac.il/packages/ > packages with the files necessary to install wvdial, with names like: > wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems. > wvdial_jaunty_i386.zip for 32 bit systems. > wvdial_karmic_i386.zip for 32 bit systems. > These are about 1 MB in size. After downloaded and copied into your > Linux partition: > $ unzip wv*.zip > Within the new folder: > $ sudo dpkg -i *.deb > will complete the wvdial installation > Please read Modem/DOCs/wvdial.txt for usage information. > > Regards, > > Antonio > > > > On Fri, Jan 29, 2010 at 10:27 AM, Juan Alejandro Martinez Linares > <islanis@xxxxxxxxxxxxxx> wrote: >> >> >> ayudenemeeeee que no tengo idea y la mayoria de los paquetes los he bajado pero soy nuevo >> en linux >> >> >> este es el contenido de modemdata.txt >> >> >> 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.31-14-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, >> Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1 (Ubuntu >> 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 >> scanModem update of: 2010_01_22 >> >> The dialer utility package WVDIAL does not appear to be installed on your System. >> For Ubuntu users, there are at the bottom of http://linmodems.technion.ac.il/packages/ >> packages with the files necessary to install wvdial, with names like: >> wvdial_jaunty_amd64.zip for x86_64, 64 bit bus systems. >> wvdial_jaunty_i386.zip for 32 bit systems. >> wvdial_karmic_i386.zip for 32 bit systems. >> These are about 1 MB in size. After downloaded and copied into your Linux partition: >> $ unzip wv*.zip >> Within the new folder: >> $ sudo dpkg -i *.deb >> will complete the wvdial installation >> Please read Modem/DOCs/wvdial.txt for usage information. >> >> 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_atiixp_modem snd_via82xx_modem snd_intel8x0m snd_hda_intel >> >> Attached USB devices are: >> ID 04f3:0103 Elan Microelectronics Corp. >> ID 13fe:1f00 Kingston Technology Company Inc. DataTraveler 2.0 4GB Flash Drive >> 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 >> >> For candidate card in slot 01:0a.0, firmware information and bootup diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 01:0a.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem >> >> Modem interrupt assignment and sharing: >> --- Bootup diagnostics for card in PCI slot 01:0a.0 ---- >> [ 0.097168] pci 0000:01:0a.0: reg 10 32bit mmio: [0xcbeff000-0xcbefffff] >> [ 0.097177] pci 0000:01:0a.0: reg 14 io port: [0xb800-0xb8ff] >> [ 0.097227] pci 0000:01:0a.0: PME# supported from D0 D3hot D3cold >> [ 0.097232] pci 0000:01:0a.0: PME# disabled >> [ 0.758699] serial 0000:01:0a.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 >> [ 0.758808] 0000:01:0a.0: ttyS1 at I/O 0xb808 (irq = 22) is a 16450 >> [ 0.758881] 0000:01:0a.0: ttyS2 at I/O 0xb810 (irq = 22) is a 8250 >> [ 0.758951] 0000:01:0a.0: ttyS3 at I/O 0xb818 (irq = 22) is a 16450 >> [ 0.758975] Couldn't register serial port 0000:01:0a.0: -28 >> >> The PCI slot 01:0a.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:27d8 1043:8249 Audio device: Intel Corporation 82801G >> >> Modem interrupt assignment and sharing: >> 19: 1891 IO-APIC-fasteoi uhci_hcd:usb5, HDA Intel >> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> [ 0.095710] pci 0000:00:1b.0: reg 10 64bit mmio: [0xcbdf8000-0xcbdfbfff] >> [ 0.095756] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> [ 0.095761] pci 0000:00:1b.0: PME# disabled >> [ 20.033066] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 >> [ 20.033102] HDA Intel 0000:00:1b.0: setting latency timer to 64 >> [ 20.170814] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input6 >> >> 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. >> >> >> >> ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >> The ALSA packages provide audio support and also drivers for some modems. >> ALSA diagnostics are written during bootup to /proc/asound/ folders. >> >> The ALSA verion is 1.0.20 >> The modem cards detected by "aplay -l" are: None >> >> >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 1 >> 00-01: ALC883 Digital : ALC883 Digital : playback 1 : capture 1 >> 00-02: ALC883 Analog : ALC883 Analog : capture 1 >> >> about /proc/asound/cards: >> ------------------------ >> 0 [Intel ]: HDA-Intel - HDA Intel >> HDA Intel at 0xcbdf8000 irq 19 >> >> PCI slot 00:1b.0 has a High Definition Audio Card >> The drivers are in the kernel modules tree at: >> /lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> UNEXPECTED HDA diagnostic outcome. >> === Finished firmware and bootup diagnostics, next deducing cogent software. === >> >> Predictive diagnostics for card in bus 01:0a.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: 01:0a.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 >> >> 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 kernels 2.8.31 the slamr driver is not (yet) functional, failing within at the >> Carrier Check >> function. Thus for service, retain a 2.8.30 or earlier kernel. For Ubuntu users this >> can be done by downloading the kernel from >> http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic >> and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ the >> slamr-2.6.28-16-generic.tar.gz >> >> >> From http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ , >> download the package slamr-2.6.31-14-generic.tar.gz >> Under Linux, open a terminal and unpack with: >> $ tar zxvf slamr*.tar.gz >> Move into the unpacked folder >> $ cd slamr-2.6.31-14-generic >> Look around >> $ ls >> Run the >> $ sudo ./setup >> >> Afterwards do: >> $ slmodemd --help >> $ slmodemd --countrylist &> Clist.txt >> If not in the USA, look for your COUNTRY_NAME therein. >> Do and edit with: >> $ sudo gedit /etc/default/sl-modem-daemon >> and therein replace the USA in the line: >> SLMODEMD_COUNTRY=USA >> This will provide for the correct Country setting in the automated: >> slmodemd -c COUNTRY /dev/slamr0 >> >> Read the DOCs/Smartlink.txt and DOCs/YourSystem.txt >> 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 82801G " >> CLASS=0403 >> PCIDEV=8086:27d8 >> SUBSYS=1043:8249 >> IRQ=19 >> HDA=8086:27d8 >> SOFT=8086:27d8.HDA >> >> >> High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, >> and many are supported by the ALSA audio+modem driver snd-hda-intel >> A modem was not detected on HDA card 8086:27d8. >> If another modem card is present, then most likely 8086:27d8 does not host a modem. >> If another modem card has not been detected, then possibilities are: >> 1) A Conexant modem chip is present on 8086:27d8, as Conexant chips >> are frequently not detectable by ALSA diagnostics >> 2) The modem may be of the older non-PCI Controller Chipset (hardware) type. >> Try detection with Root permission: >> sudo wvdialconf /etc/wvdial.conf >> >> For candidate modem in: 00:1b.0 >> 0403 Audio device: Intel Corporation 82801G >> Primary device ID: 8086:27d8 >> Subsystem PCI_id 1043:8249 >> Softmodem codec or chipset from diagnostics: >> from Archives: >> >> >> >> Support type needed or chipset: >> >> Support can likely be achieved through two mutually exclusive alternatives: >> 1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt >> The following ALSA alternative CANNOT work with Conexant modems. >> >> 2) An ALSA modem driver plus slmodemd. Read DOCs/Smartlink.txt for details, and >> to test get the package SLMODEMD.gcc4.4.tar.gz from: >> http://linmodems.technion.ac.il/packages/smartlink/ >> >> >> Completed candidate modem analyses. >> >> The base of the UDEV device file system is: /dev/.udev >> >> Versions adequately match for the compiler installed: 4.4.1 >> and the compiler used in kernel assembly: 4.4.1 >> >> The patch utility is needed for compiling ALSA drivers, and possibly others. >> >> >> Minimal compiling resources appear complete: >> make utility - /usr/bin/make >> Compiler version 4.4 >> linuc_headers base folder /lib/modules/2.6.31-14-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 277352 2009-02-20 18:25 /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/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 >> Within any ancient /etc/devfs files: >> >> Within ancient kernel 2.4.n /etc/module.conf files: >> >> --------- end modem support lines -------- >> >> >> >> ------------------------------ >> Infomed - Red de Salud de Cuba >> http://www.sld.cu/ >> >> >> -- >> >> 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/ >> >
