Alex0, The core problem is that the compile of the drivers is failing. Among them, ungrab-winmodem is fairly simply code, so most likely there has been some change in general compiling machinery causing these failures. I am traveling through mid-June and may not be able to help much. But I am copying to the Ubuntu maintainer who is more code proficient than I. In the meantime I suggest you install the prior linux-mage-Version.deb + linux-headers-version.deb, under which the drivers compiled. Such older kernels+modules most often do retain functionality aftre a Distribution upgrade. MarvS On Tue, Apr 30, 2013 at 6:15 PM, AlexO <vilmaperez@xxxxxxxxxxxxxx> wrote: > > Hi Marvin, thanks for the help, this is the results of what you suggested > > I tried > $ sudo dkms Status > the result was this: > sl-modem, 2.9.11~20110321: added > > Then I manually unloaded the conflicting drivers with: > $ sudo modprobe -r snd_atiixp_modem > $ sudo modprobe -r snd_via82xx_modem > $ sudo modprobe -r snd_intel8x0m > There was no error output. > > Then: > $ sudo /etc/init.d/sl-modem-daemon restart > > The output was this: > Shutting down SmartLink Modem driver normally ... no slmodemd daemon > running. > Unloading modem driver from kernel ... none found. > Starting SmartLink Modem driver for: auto. > Creating /dev/modem symlink, pointing to: /dev/ttySL0. > > Then I tried: > $ ls- l /dev/ttySL0 > The result was this: > ls: cannot access /dev/ttySL0: No such file or directory > > Then I tried: > $ sudo wvdialconf > And the result was: > > Editing `/etc/wvdial.conf'. > Scanning your serial ports for a modem. > Modem Port Scan<*1>: S0 S1 S2 S3 S4 S5 S6 S7 > Modem Port Scan<*1>: S8 S9 S10 S11 S12 S13 S14 S15 > Modem Port Scan<*1>: S16 S17 S18 S19 S20 S21 S22 S23 > Modem Port Scan<*1>: S24 S25 S26 S27 S28 S29 S30 S31 > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > The modem still doesn't work :( > > ________________________________ > De: Marvin Stodolsky [mailto:marvin.stodolsky@xxxxxxxxx] > Enviado el: Tuesday, April 30, 2013 5:04 PM > Para: Antonio Olivares > CC: AlexO; discuss@xxxxxxxxxxxxx > Asunto: Re: Onay, Cuba, kernel 3.8.0-19-generic > > Alex0 > > Do continue using the sl-modem source, sl-modem-daemon & dkms Ubuntu > packages as before, as they include our most recent code. But do check > that the ungrab-winmodem and slamr were infact compiled and installed. > $ sudo dkms status > will inform. > > Antonio is correct that drivers snd_atiixp_modem snd_via82xx_modem > snd_intel8x0m may conflict with slamr+ungrab-winodem. You could add them to > the module blacklist file using: > $ sudo gedit /etc/modprobe.d/blacklist.conf > First check that my filename is correct with: > $ less /etc/modprobe.d/blacklist.conf > as I'm not under Linux now: > > But the first thing to try is manually unloading: > $ sudo modprobe -r snd_atiixp_modem > $ sudo modprobe -r snd_via82xx_modem > $ sudo modprobe -r snd_intel8x0m > before testing the modem. > > You should then be able to: > $ sudo /etc/init.d/sl-modem-daemon restart > to load the drivers etc. > Check for port creations with: > $ ls -l /dev/ttySL0 > > Then try: > $ sudo wvdialconf wvtest.txt > which hopefully fine the modem. > If you had just used: > $ sudo wvdialconf > you old /etc/wvdial.conf would be overwritten. > > Report back presently and copy us any errror messages. > > MarvS > > > > On Tue, Apr 30, 2013 at 1:34 PM, Antonio Olivares > <olivares14031@xxxxxxxxx> wrote: > 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/
