Carl, The comments here are in order of importance. 1) for now, simply stay with the 3.13.* kernels under which slam.ko compiles and the modem/fax is functional. There is no compelling reason to switch to the 3.16.* kernels under which compiles are failing. When Ubuntu does an update to 3.16 kernels in the main release, I'm be willing to address the code compilation issues. There is substantial chance that some of the fixes will have then been found, because they will manifest in other modules. 2) Note that slamr does not use the standard serial ports. Port creation under Linux is now a dynamic process, initiated as the a module is loaded. For slamr, the port is named /dev/ttySL0 (for single module installations) Read the SmartLink related documentation output when scanModem is run for more details. 3) When scanModem is run, one of the output files is ModemData.txt , which Antonio requested. It would still be useful for you to send it to the List. MarvS On Sun, Jul 26, 2015 at 3:06 AM, Carl D. Goldin <cdgoldin@xxxxxxxxx> wrote: > Dear Mr. Olivares and Mr. Stodolsky: > > Thank you for your responses to my problem. I will reply in sequence of > their receipt: > >>"Compile was successfull you mention with newer source, but you have no way >> of using the modem? You could use wvdial or kppp or maybe even >> NetworkManager to access the modem and try to use it to connect. " > > Yes, the "compile" appeared to complete successfully with newer source, but > "sudo modprobe slamr" gave the following error messages, indicating that > something is amiss. > > ERROR: ../libkmod/libkmod-module.c:809 kmod_module_insert_module() could not > find module by name='slamr' > modprobe: ERROR: could not insert 'slamr': Function not implemented > > Also, the "off-hook" situation remains, which is of more concern to me at > the moment, as it is impossible to use telephone or modem while the problem > persists. > > $ wvdial says "Cannot open /dev/ttySL0: no such file or directory" > > $ kppp says "kppp(3577)/kdeui (KIconLoader): Error: standard icon theme > "oxygen" not found!" > > $ sudo wvdialconf shows "NO modem detected!" > > $ dmesg | grep tty shows "ttyS0 . . . is a 16550A", which is my modem. > > $ setserial -g /dev/ttyS[0123] shows "/dev/ttyS0, UART: 16550A, Port: > 0x03f8, IRQ: 4" > > sending "AT" commands to the port via "minicom -D /dev/ttyS0 -o console" > accomplishes nothing. > > $ statserial Device: /dev/ttyS0 shows RTS and DTR high (“1”) > > I was concerned that the procedure I found at > https://help.ubuntu.com/community/DialupModemHowto/Smartlink seemed to work > with Ubuntu 14.04, Mint 17.0 and Mint 17.1, but realized over the weekend > that IT NEVER COMPILED THE SOURCE, because "sudo module-assistant > auto-install sl-modem" resulted in "command not found"! I now recall that I > simply continued with the subsequent steps in the procedure steps, and then > discovered the modem had finally hung up the telephone. > > So, tonight I booted from the (downloaded) Mint 17.1 installation CD, and > discovered that the depmod procedure invoked at the very end of the "apt-get > install sl-modem sl-modem-daemon" procedure is what finally placed the > telephone line back on-hook. I tried the same thing with 17.2, and the > apt-get install procedure failed before reaching the depmod procedure. I've > attached the console logs from both. > > I also tried the installation procedure in the > http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20110321.tar.gz > README file > > gzip -dc slmodem-2.9.X.tar.gz | tar xf - > cd slmodem-2.9.11-20110321 > make KERNEL_DIR=/path/to/linux=/lib/modules/3.16.0-38-generic/build > > BUT THIS FAILED WITH SEVERAL WARNINGS AND FINALLY > #include <generated/utsrelease.h> > ^ > compilation terminated. > make[1]: *** [kernel-ver] Error 1 > >>"I believe it would be a good idea if you can send us ModemData.txt to >> confirm that it(modem) needs/requires smarlink modem driver and not >> slmodemd+alsa which does not require slamr.ko?" > > The file "ModemData.txt" does not exist anywhere on my system. > >> marvin.stodolsky@xxxxxxxxx> wrote: A code fix is necessary: > > I don't have a Kmod source file anywhere in my system, and I don't know > enough about Linux or C++ to know what I would do with it after making the > modifications you indicate. Is this "code fix" addressing the "off hook" > problem, or my inability to compile the sl-modem drivers? > >>The problem is more difficult. There is no "kmod-" line in sl-modem-source >> code itself. Thus the change seems to be in general module management, which >> is kmod lines are found. When Ubuntu does an upgrade to 3.16.* from the >> current 3.13* kernels, I would be willing to work on it then. > > So, what should I do meanwhile? Go back to Mint 17.1, or use 17.2 without > updating the kernel, or ??? I still wouldn't have a modem, but at least my > phone would be usable. > >>But note that all my current PCs are 64 bit, while the slamr.ko which you >> do need only compiles on 32 bit PCs, so we would have to interact. > > I have no objection to interacting. But, as I mentioned above, my knowledge > of Linux and C++ are minimal, so you might have to provide more detail than > you would with someone more experienced in these areas. > > I am running the 32-bit version of Mint, because I had hoped to avoid some > on these problems. > >>In the meantime do check whether slamr.ko has infact compiled and >> installed. > > I don't know how to determine this. A file search indicates that slamr.ko > exists in /lib/modules/3.13.0-24-generic/kernel/drivers/misc, > /lib/modules/3.13.0-37-generic/kernel/drivers/misc, > /var/lib/dkms/sl-modem/kernel-3.13.0-24-generic-i686/module and > /var/lib/dkms/sl-modem/kernel-3.13.0-37-generic-i686/module. > > $ find /lib/modules -lname slu*.ko > and > $ find /lib/modules -name sla*.ko > produce no output, which (I assume) means that slusb.ko and slamr.ko have > not been compiled and installed? > > Thank you for your help with this matter. > > ----- Original Message ----- > From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> > To: "Antonio Olivares" <olivares14031@xxxxxxxxx> > Cc: "Carl D. Goldin" <cdgoldin@xxxxxxxxx>; "Linmodems" > <Discuss@xxxxxxxxxxxxx> > Sent: Saturday, July 25, 2015 12:19 > Subject: Re: Problems with Smartlink Modem and Linux > > > Carl > > The problem is more difficult. There is no "kmod-" line in > sl-modem-source code itself. > Thus the change seems to be in general module management, which is > kmod lines are found. > When Ubuntu does an upgrade to 3.16.* from the current 3.13* kernels, > I would be willing to work on it then. > > But note that all my current PCs are 64 bit, while the slamr.ko which > you do need only compiles on 32 bit PCs, so we would have to interact. > In the meantime do check whether slamr.ko has infact compiled and > installed. > > A query like that below should suffice > > MarvS > ------------------ > $ find /lib/modules -lname slu*.ko > /lib/modules/3.13.0-52-generic/updates/dkms/slusb.ko > found slusb.ko, but not slamr.ko reported as expected. on my 64 bit > system with query: > $ find /lib/modules -name sla*.ko > > > > On Fri, Jul 24, 2015 at 8:25 PM, Marvin Stodolsky > <marvin.stodolsky@xxxxxxxxx> wrote: >> A code fix is necessary: >> >> https://kernel.googlesource.com/pub/scm/utils/kernel/kmod/kmod/+/3a721bbcf02217e11b214a479f15529669d05339%5E!/ >> >> with one instance therein: >> >> -int c(struct kmod_module *mod, unsigned int flags); >> +int kmod_module_insert_module(struct kmod_module *mod, unsigned int >> flags, const char *options); >> >> >> Over the weekend I'll try to work it through >> >> >> Google search with >> >> for more info >> >> >> MarvS >> >> >> >> >> On Fri, Jul 24, 2015 at 11:17 AM, Antonio Olivares >> <olivares14031@xxxxxxxxx> wrote: >>> Dear Carl, >>> >>> Compile was successfull you mention with newer source, but you have no >>> way of using the modem? You could use wvdial or kppp or maybe even >>> NetworkManager to access the modem and try to use it to connect. `` I >>> have no idea if >>> it actually made the modem usable, as I don't yet have a fax program or >>> dialer >>> that works with Linux.'' For a fax, you may look for hylafax, or >>> other fax software available. For the off the hook problems I cannot >>> recall issues, but Marv may remember instances or search the archives >>> for how this matter was taken care of. Also slamr.ko would be for a >>> true smartlink modem or a motorola one that is supported via smartlink >>> driver. I believe it would be a good idea if you can send us >>> ModemData.txt to confirm that it(modem) needs/requires smarlink modem >>> driver and not slmodemd+alsa which does not require slamr.ko? >>> >>> Best Regards, >>> >>> >>> Antonio >>> >>> >>> On Fri, Jul 24, 2015 at 1:51 AM, Carl D. Goldin <cdgoldin@xxxxxxxxx> >>> wrote: >>>> I have a (Windoze 7 and Linux Mint 17.1) dual-boot system with a >>>> Smartlink >>>> v92 >>>> modem. >>>> >>>> When I installed and/or upgraded to Ubuntu 14.04, Mint 17.0, Mint 17.1 >>>> and >>>> Mint >>>> 17.2, booting into Linux resulted in my modem being taken "off-hook" >>>> (and >>>> thus >>>> tying up the telephone line until I shut down Linux or unplugged the >>>> line). >>>> This >>>> didn't occur with Ubuntu 12.04, so it appears to be something introduced >>>> in >>>> 14.04, which is the current Mint base. >>>> >>>> I have also verified that it occurs when "live booting" from the >>>> installation >>>> CD, and thus is not the result of something amiss in my installation. I >>>> have >>>> also verified that this does NOT occur with a Motorola SM56 modem, or a >>>> (generic) PCI-SoftV92 modem. >>>> >>>> The "solution" (to the "off-hook" problem) was finally discovered to be >>>> installing the driver according to the procedure found at >>>> https://help.ubuntu.com/community/DialupModemHowto/Smartlink. I have no >>>> idea > >>>> if >>>> it actually made the modem usable, as I don't yet have a fax program or >>>> dialer >>>> that works with Linux. >>>> >>>> However, this "solution" only worked with Ubuntu 14.04, Mint 17.0 and >>>> Mint >>>> 17.1, >>>> but NOT Mint 17.2! (Actually, the "off-hook" problem didn't return when >>>> I >>>> upgraded from 17.1 to 17.2, until I subsequently updated the kernel from >>>> 3.13.0-37 to 3.16.0-38). For some reason that I don't understand, >>>> following >>>> the >>>> identical procedure for installing the driver resulted in a multitude of >>>> errors! >>>> >>>> Here is what I tried (with Mint 17.2), and the unhappy results: >>>> >>>> -sudo apt-get install sl-modem-source sl-modem-daemon >>>> -sudo module-assistant auto-install sl-modem >>>> >>>> This step FAILED with “module-assistant not found”, so I did >>>> >>>> -sudo apt-get install module-assistant >>>> -sudo module-assistant auto-install sl-modem >>>> >>>> This FAILED with a meaningless message saying the compilation (?) had >>>> failed, >>>> nothing more. >>>> >>>> So I followed the "Fiesty 7.04" procedure specified in the article: >>>> >>>> -mkdir slmodemtmp >>>> -cd slmodemtmp/ >>>> -wget >>>> >>>> http://linmodems.technion.ac.il/packages/martlink/slmodem-2.9.11-20070505.tar.gz >>>> -tar -xvf slmodem-2.9.11-20070505.tar.gz >>>> -sudo cp slmodem-2.9.11-20070505/* /usr/src/modules/sl-modem/ -r # Now >>>> the >>>> sources are updated >>>> >>>> BUT this resulted in ERROR: “/usr/src/modules/sl-modem/ NOT A >>>> DIRECTORY"! so >>>> I >>>> did: >>>> >>>> -sudo mkdir /usr/src/modules >>>> -sudo mkdir /usr/src/modules/sl-modem >>>> -sudo cp slmodem-2.9.11-20070505/* /usr/src/modules/sl-modem/ -r # Now >>>> the >>>> sources are updated >>>> -sudo touch /usr/src/linux-headers-`uname -r`/include/linux/config.h # >>>> Compile-fix >>>> >>>> And then I continued with: >>>> >>>> -sudo module-assistant auto-install sl-modem >>>> >>>> Which STILL FAILED with the same meaningless message saying the >>>> compilation >>>> had >>>> failed, nothing more. >>>> >>>> So I followed the alternate "Fiesty 7.04" procedure specified in the >>>> article: >>>> >>>> -check http://linmodems.technion.ac.il/packages/smartlink/ for a newer >>>> source >>>> package and use that one instead. >>>> >>>> There were about ten more recent packages. I selected the latest one: >>>> >>>> -wget >>>> >>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20110321.tar.gz >>>> -tar -xvf slmodem-2.9.11-20110321.tar.gz >>>> -sudo mkdir /usr/src/modules >>>> -sudo mkdir /usr/src/modules/sl-modem >>>> -sudo cp slmodem-2.9.11-20110321/* /usr/src/modules/sl-modem/ -r # Now >>>> the >>>> sources are updated >>>> -sudo touch /usr/src/linux-headers-`uname -r`/include/linux/config.h # >>>> Compile-fix* >>>> -sudo module-assistant auto-install sl-modem >>>> >>>> This time the "compile" appeared to complete successfully! So I >>>> continued: >>>> >>>> -sudo depmod -a (this updates the list of available modules) >>>> -sudo gedit /etc/default/sl-modem-daemon >>>> Insuring that SLMODEMD_COUNTRY=USA >>>> -sudo modprobe slamr >>>> >>>> This resulted in: >>>> ERROR: ../libkmod/libkmod-module.c:809 kmod_module_insert_module() could >>>> not >>>> find >>>> module by name='slamr' >>>> modprobe: ERROR: could not insert 'slamr': Function not implemented >>>> >>>> At this stage I am stuck. Any suggestions will be appreciated. Meanwhile >>>> I've >>>> gone back to 17.1 >>>>
