Hello Antonio, thanks for your answer. Since you told me I was doing the correct procedures but maybe the file slamr.ko were not created under the new kernel , I went back to Ubuntu to check it, and uninstalled everything concerning to sl-modem drivers. I went setp by step again installing first the package sl-modem-dkms and this is the output I got in the terminal: Reinstalling sl-modem-dkms Selecting previously unselected package sl-modem-dkms. (Reading database ... 160733 files and directories currently installed.) Unpacking sl-modem-dkms (from .../sl-modem-dkms_2.9.11~20110321-8_i386.deb) ... Setting up sl-modem-dkms (2.9.11~20110321-8) ... Loading new sl-modem-2.9.11~20110321 DKMS files... First Installation: checking all kernels... Building only for 3.8.0-19-generic Building initial module for 3.8.0-19-generic Traceback (most recent call last): File "/usr/share/apport/package-hooks/dkms_packages.py", line 22, in <module> import apport ImportError: No module named apport Error! Build of slusb.ko failed for: 3.8.0-19-generic (i686) Consult the make.log in the build directory /var/lib/dkms/sl-modem/2.9.11~20110321/build/ for more information. The make.log's content is this: DKMS make.log for sl-modem-2.9.11~20110321 for kernel 3.8.0-19-generic (i686) Tue Apr 30 15:12:19 CDT 2013 make: Entering directory `/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' obj-m=slamr.o slusb.o slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o make modules -C /lib/modules/3.8.0-19-generic/build SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic' CC [M] /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/amrmo_init.o /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/amrmo_init.c:250:46: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__devinitdata' /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/amrmo_init.c:728:14: error: 'amrmo_pci_tbl' undeclared here (not in a function) /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/amrmo_init.c:319:1: error: '__mod_pci_device_table' aliased to undefined symbol 'amrmo_pci_tbl' make[2]: *** [/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/amrmo_init.o] Error 1 make[1]: *** [_module_/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic' make: *** [all] Error 2 make: Leaving directory `/var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers' make: Entering directory `/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem' make modules -C /lib/modules/3.8.0-19-generic/build SUBDIRS=/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem make[1]: Entering directory `/usr/src/linux-headers-3.8.0-19-generic' CC [M] /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem .o /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem .c:48:50: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__devinitdata' /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem .c: In function 'softmodem_release_init': /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem .c:84:19: error: 'softmodem_pci_tbl' undeclared (first use in this function) /var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmodem .c:84:19: note: each undeclared identifier is reported only once for each function it appears in make[2]: *** [/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem/ungrab-winmode m.o] Error 1 make[1]: *** [_module_/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-19-generic' make: *** [all] Error 2 make: Leaving directory `/var/lib/dkms/sl-modem/2.9.11~20110321/build/ungrab-winmodem' Installing sl-modem-daemon the terminal output was this: Preconfiguring packages ... Selecting previously unselected package sl-modem-daemon. (Reading database ... 160787 files and directories currently installed.) Unpacking sl-modem-daemon (from .../sl-modem-daemon_2.9.11~20110321-8_i386.deb) ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up sl-modem-daemon (2.9.11~20110321-8) ... Warning: The home dir /var/log/slmodemd you specified can't be accessed: No such file or directory The system user `Slmodemd' already exists. Exiting. usermod: no changes Starting SmartLink Modem driver for: auto. Creating /dev/modem symlink, pointing to: /dev/ttySL0. Processing triggers for ureadahead ... And installing the sl-modem-source did not output any significant messages since that package it's now classified as a "Transitional Dummy Package" and has only a few kb of size (I installed it anyway just in case, and there were no errors). At the beginning I was suspicious about this, but I checked the previous version's repositories of Ubuntu (12.10), and it was the same version, the same size and also classified as "Transitional Dummy Package", but the modem worked fine on that version. What do you think I can do? Best regards. Onay. -----Mensaje original----- De: Antonio Olivares [mailto:olivares14031@xxxxxxxxx] Enviado el: Tuesday, April 30, 2013 1:35 PM Para: AlexO CC: discuss@xxxxxxxxxxxxx; Marvin Stodolsky Asunto: Re: Onay, Cuba, kernel 3.8.0-19-generic Onay, You are doing the correct procedures. As far as I am concerned. What I believe is happening is that sl-modem-* may be conflicting in that it has slmodemd+Alsa instead of building slamr.ko + ungrab-winmodem.ko for your system. In The modem symbolic link is /dev/modem -> ttySL0 Distrib_ID=Ubuntu DistribCodeName=raring The dkms driver upgrade utilities are installed, 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 The modem drivers now loaded are, these conflict with slamr.ko and are conflicting. Marv, How could Onay fix this problem via sl-modem-src.deb ? instead of compiling slmodem-2.9.11-20*.tar.gz sources? He is following correct procedure as far as I know. He has dkms installed, and is following the directions, unless slamr.ko is not created with newer kernels? I have not tested this at this time. 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.8.0-19-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 Best Regards, Antonio On 4/30/13, AlexO <vilmaperez@xxxxxxxxxxxxxx> wrote: > Hi everyone, I need help with a PCI internal Motorola SM-56 Modem. I'm > currently using Ubuntu 13.04 (32 bits) and the modem doesn't work (it > does on other operative systems like Windows). Until Ubuntu 12.10 I > was using the procedure of installing packages sl-modem-source, > sl-modem-daemon (also dkms and dependencies) and after a restart, > applications like gnome-ppp, kppp and wvdial were able to see and use > the modem correctly, so it worked fine. Now with Ubuntu 13.04 I use > the same procedure: I install sl-modem source, sl-modem-daemon, dkms > and all the required dependencies, but gnome-ppp (and also kppp and > wvdial) keeps telling me that "There's no modem on your system", I > also tried running gnome-ppp, kppp and wvdial as root, also did it > from the terminal with sudo and gksu commands (it worked fine on > previous versions of Ubuntu like 12.10, otherwise the modem was not > recognized by gnome-ppp or wvdial) but now in 13.04 it doesn't work > either, scanmodem says the modem is there (Windows OS sees and uses > the modem fine so it's not a hardware problem) but Ubuntu 13.04 > doesn't work with it. Is it about the new kernel? Do I have to do > something else new to this version of Ubuntu? > I've attached the ModemData file produced by scanmodem. > Thank you for your time and help. > Onay. > > > -- > > 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/ > -- 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/
