RE:>> Should I ignore the other "martian" files and proceed with the tar in Yes indeed! Following typical Debian/Ubuntu cussom package martian-modem installs the /usr/src/martian_modem (non-driver ) helper containing all the closed source code, and also the scripts written to the /etc/ files. The martian-modem-source contains the code for compiling the martian_dev driver. If will unpack into /usr/src/modules/martian-modem/source/ Within the /usr/src/modules/martian-modem/source/ do $ less Makefile for understanding. Then $ sudo make clean $ sudo make modules $ sudo make install Then you can proceed with modem testing. Antonio, I was not aware that these two packages were now being provided under Ubuntu. Shortly I will update scanModem MarvS On Sun, Apr 24, 2011 at 4:36 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Joe, > > On Sat, Apr 23, 2011 at 10:20 PM, Joe Herko <joe.herko@xxxxxxxxx> wrote: >> Antonio and MarvS >> >> Thank you for your responses and I have a couple of follow-up questions. >> >> I used the Ubuntu Software Center to uninstall martian-modem-source, but I >> did not think to check for other files that might remain before I did the >> tar download. >> >> I downloaded the martian-full-20100123.tar.gz file, and the file is now in >> my Download subdirectory. >> >> I now have the following files on my system with "martian" as part of the >> filename. >> >> /home/systemadmin/Downloads/martian-full-20100123.tar.gz, 21 Apr 2011, tar >> archive >> >> Some of these files in this group may be from the tar download and some >> might be left over from the martian-modem-source install and removal. >> /etc/init.d/martian-modem, 5 Feb 2010, shell script >> /etc/default/martian-modem, 5 Feb 2010, plain text document >> /var/lib/update-rc.d/martian-modem, 22 Mar 2011, plain text document >> /var/lib/dpkg/info/martian-modem.postrm, 5 Feb 2010, shell script >> /var/lib/dpkg/info/martian-modem.list,21 Apr 2010, plain text document >> /proc/sys/net/ipv4/conf/all/log_martians, 23 Apr 2011, plain text document >> /proc/sys/net/ipv4/conf/default/log_martians, 23 Apr 2011, plain text >> document >> /proc/sys/net/ipv4/conf/lo/log_martians, 23 Apr 2011, plain text document >> /proc/sys/net/ipv4/conf/eth0/log_martians, 23 Apr 2011, plain text document >> >> I think this group of files is left over from the martian-modem-source >> Ubuntu Software Center install. >> /etc/rc0.d/K20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc1.d/K20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc2.d/S20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc6.d/K20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc4.d/S20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc5.d/S20martian-modem, 5 Feb 2010, link to shell script >> /etc/rc3.d/S20martian-modem, 5 Feb 2010, link to shell script >> >> My follow-up questions: >> >> Should I ignore the other "martian" files and proceed with the tar >> decompression and compile? (see other questions below) > It is up to you, if you don't have a working connection? ÂThe src file > that you installed should have made the connection work. > >> >> Should I remove all of the "martian" files including the tar file and start >> again by downloading the tar file? > No. ÂKeep in case you need them again? >> >> Should I delete any of the files in the first group above? (e.g. >> /etc/init.d/martian-modem, 5 Feb 2010, shell script) > No. >> >> Should I delete the K20martian-modem and S20martian-modem files in the >> /etc/rc... subdirectories that remain from the martian-modem-source install? > No, these files will help in the automation process. >> >> Do I run the tar decompression from the Download subdirectory or another >> location? > Wherever the file is, just decompress it from there. Âunless you feel > it is better to move it? >> >> I looked for a lib6 package on the Ubuntu Software Center, and did not find >> a package. >> >> Â Â Â ÂIs the reference to the lib6 package the same as libc6-dev? > Yes, It was a typo on my part :( >> >> The Ubuntu Software Center indicates that libc6-dev and linux-libc-dev are >> both on my laptop. >> >> Â Â Â ÂIs there a terminal command that I can use to determine if libc6-dev >> and linux-libc-dev are correctly installed? >> Â Â Â Âor >> Â Â Â ÂDo I still need to use the dpkg command to install libc6-dev >> (libc6*)? >> Â Â Â ÂShould I also use the dpkg command to install linux-libc-dev? > No proceed to decompress and build the package. >> >> Again, thank you in advance for your advice. >> > > Try to follow the instructions provided. ÂThen report back to us if > you encounter problems/difficulties. > > Regards, > > Antonio > >> At 02:55 PM 4/21/2011, you wrote: >>> >>> Joe, >>> >>> Download >>> >>> http://linmodems.technion.ac.il/packages/ltmodem/kernel-2.6/martian/martian-full-20100123.tar.gz >>> and look for lib6 package as line output by scanModem recommends >>> >>> >>> Â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. >>> >>> After successful installation of the libc6 package with >>> $ sudo dpkg -i libc6* >>> run >>> $ tar -zxvf martian-full-20100123.tar.gz >>> and >>> $ cd martian-full-20100123 >>> $ make all >>> $ sudo make install >>> $ sudo modprobe martian_dev >>> $ sudo martian_modem >>> >>> leave it running and open another shell/tab and type >>> $ sudo wvdialconf /etc/wvdial.conf >>> >>> and hopefully it will find /dev/ttySM0 as the modem port, if it does, >>> then edit (with sudo priviledges) the file /etc/wvdial.conf and add >>> the line >>> "Carrier Check = no" >>> and then run >>> $ sudo wvdial >>> >>> to see if you can connect. ÂIf you can connect/not connect send us >>> what messages you get so that we may try to help you. >>> >>> Regards, >>> >>> Antonio >>> >>> >>> > -------------------- >>> > Joe Herko >>> > >> >> -------------------- >> Joe Herko >> >
