It is NOT ADVISABLE to activate winmodems on bootup, in my opinion. While OK say 98% of the time, there are rare Systems whereon loading the modem driver will cause a System CRASH. There have been cases where merely upgrading to a new kernel thus makes a previously sound system vulnerable. There have been not uncommon reports of loading winmodem drivers causing System problems. Fortunately, at least those reported to us have been subsequent to bootup, upon manual loading. If the crash occurs through usage of a bootup script such as those in /etc/init.d/ , then usage of a Rescue disk may be necessary to achieve restoration of the System. This is non-trivial for a Linux Newbie (and I remember the pains of such a rescue). Also remember that many Linuxes are now installing by default, DKMS driver update services. So new drivers will be compiled and installed by DKMS upon booting up a new kernel, thus putting the System at risk through the yet untested (under that kernel) winmodem driver. Fortunately, retention of the former kernel is usually retained, so there is not a bad rescue problem here. MarvS scanModem maintainer Mon, Jul 12, 2010 at 3:36 AM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Barbara, > > Might work or not? But > > Here: > >> Then adding to /etc/rc.d/rc.local the line >> /sbin/modprobe martian_dev >> ------------------------------ > > You would need to run something like > $ sudo gedit /etc/rc.d/rc.local > and add at the end > the line > /sbin/modprobe martian_dev > >> someone@someone-desktop:~/Downloads/martian-full-20100123/scripts$ >> /etc/rc.d/rc.local >> bash: /etc/rc.d/rc.local: No such file or directory > > The file /etc/rc.d/rc.local gets executed at startup, you don't need to run it. > > Have you tried shutting down and restarting the system and see that > the modem works without typing the commands ? > > Thanks, > > Antonio > > On 7/12/10, Barbara Denny and Associates <dennyandassociates@xxxxxxxxxxx> wrote: >> Got this far >> Then adding to /etc/rc.d/rc.local the line >> /sbin/modprobe martian_dev >> ------------------------------ >> result >> someone@someone-desktop:~/Downloads/martian-full-20100123/scripts$ sudo >> update-rc.d martian defaults 45 60 >> update-rc.d: warning: /etc/init.d/martian missing LSB keyword >> 'required-start' >> >> update-rc.d: warning: /etc/init.d/martian missing LSB keyword >> 'required-stop' >> >> update-rc.d: warning: /etc/init.d/martian missing LSB keyword 'default-stop' >> >> update-rc.d: warning: martian stop runlevel arguments (0 1 6) do not match >> LSB Default-Stop values (none) >> Adding system startup for /etc/init.d/martian ... >> /etc/rc0.d/K60martian -> ../init.d/martian >> /etc/rc1.d/K60martian -> ../init.d/martian >> /etc/rc6.d/K60martian -> ../init.d/martian >> /etc/rc2.d/S45martian -> ../init.d/martian >> /etc/rc3.d/S45martian -> ../init.d/martian >> /etc/rc4.d/S45martian -> ../init.d/martian >> /etc/rc5.d/S45martian -> ../init.d/martian >> someone@someone-desktop:~/Downloads/martian-full-20100123/scripts$ >> /etc/rc.d/rc.local >> bash: /etc/rc.d/rc.local: No such file or directory >> someone@someone-desktop:~/Downloads/martian-full-20100123/scripts$ >> >> >> >> >> Barbara Denny >> (626)966-9969 >> fax 966-6621 >> >> ---------- Original Message ---------- >> From: Antonio Olivares <olivares14031@xxxxxxxxx> >> To: Barbara Denny and Associates <dennyandassociates@xxxxxxxxxxx> >> Cc: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> >> Subject: Re: automation of martian_modem on Ubuntu Lucid, ie, $ sudo >> modprobe martian_dev, $ sudo martian_modem, ... just $ sudo wvdial >> Date: Mon, 12 Jul 2010 02:47:54 +0000 >> >> Marv, >> >> Will the following make this automation work? >> >> $ cd martian-full-20100123/scripts/ >> $ sudo cp martian /etc/init.d/ >> $ sudo chmod +x /etc/init.d/martian >> >> Since chkconfig line has >> # chkconfig: 2345 45 60 >> >> $ sudo update-rc.d martian defaults 45 60 >> >> Then adding to /etc/rc.d/rc.local the line >> /sbin/modprobe martian_dev >> >> Would make it work? Right? >> Should I ask Barbara kindly to test it. Do the above steps, then >> shutdown/reboot and see if by opening a terminal and typing >> $ sudo wvdial >> >> would work. >> >> Thanks, >> >> Antonio >> >> On 7/12/10, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: >>> Barbara, >>> >>> I am cc:'ing this to Marv for suggestions regarding: >>> >>>> While I am typing is there a short cut or just push the firefox icon to >>>> get >>>> on line now that the system had info or will the client need to >>>> go to the terminal and type all the commands? >>>> >>> >>> Marv, >>> >>> Barbara has a modem supported by martian-full-20100123 code which she >>> has installed successfully. However, to the best of my knowledge, I >>> told her that automate script in martian-full-20100123/scripts/ folder >>> installs successfully for RPM based distros, ie, Fedora, OpenSuse, >>> CentOS, Mandriva, ..., etc. But for Ubuntu, it might not work? >>> >>> How can she automate martian for Ubuntu, if there is an easy way to do it? >>> >>> Thanks and sorry to bother, >>> >>> Antonio >>> >> >> >> ____________________________________________________________ >> Penny Stock Jumping 2000% >> Sign up to the #1 voted penny stock newsletter for free today! >> http://thirdpartyoffers.netzero.net/TGL3241/4c3a8aeb6bf8a2194d1st05vuc >> >
