John, You may use kppp as your dialer, there is no problem there, but you may have to change your martian_modem script (autostart script) to point to /dev/modem since /dev/ttySM0 is not in the dialers section. You can safely do a $ cd martian-full-20080625/scripts/ and run the setup script that is there to automate the process at startup. You can add there to that file or to /etc/rc.local the line that brings eth0 interface down $ sudo ifconfig eth0 down but I believe that it might not be needed, unless you have an internet connection with the ethernet port, but then again why would you need dialup if you have that in place. As far as the automate script, I don't know how it works with Debian/Ubuntu variants since it calls on chkconfig martian on, and if chkconfig is available for them? Maybe Marv can advice you on this part? Regards, Antonio On Wed, Dec 2, 2009 at 1:11 PM, John Wright <john@xxxxxxxxxxxxx> wrote: > Antonio, > > It looks like I'm good to go but I have not tested a dial-out connection yet > using wvdial. I'm using wvdial-karmic, I figured that was okay since my Linux > version is Kubuntu-Karmic. > > I need to do some reading to understand how everything needs to be setup for > easy modem and faxing operations. I guess I will be using Kppp as interface to > the ppp dialer. I use to use uucp years ago so I will need to brush up on > everything. > > What about martin_modem? Is it always needed to spawn a process that drives > the LT Modem? I noticed that my terminal does not return to the command > prompt. > > I guess the next step is what I mention above, what commands need to be added > to startup scripts to make everything seamless. This would include bringing > 'eth0' down, then back up after a modem session. I'm sure that all of these > things are done through Kppp configuration files etc... but please elaborate on > what I should do next. I plan to use Kfax or some other free faxing software > program. I think Xsane will probably call Kfax or some other faxing program. > You can scan to fax in Xsane so the hooks are there. > > Thanks for you help and guidence on this. Please reply when you have time. I > might need some more once I start testing. I will probably do some of this > tonight. > > Thanks. > > > On Wednesday 02 December 2009 07:10:32 am you wrote: >> John, >> >> sometimes this happens, if you have already run >> $ sudo modprobe martian_dev >> and >> $ sudo martian_modem >> >> and you should see a messaging telling you that martian modem is >> running and your port is /dev/ttySM0, if you don't see this, then that >> is why you see that no modem was detected. >> >> If you do see (modem is running /dev/ttySM0 is your device port), then >> before you run >> $ sudo wvdialconf /etc/wvdial.conf >> run >> $ sudo ls -l /dev/ttySM0 >> >> Regards, >> >> Antonio >> >> On 12/2/09, John Wright <john@xxxxxxxxxxxxx> wrote: >> > Antonio, >> > >> > This is where I'm at now. I noticed a reference to /etcc/wvial.conf, but >> > that >> > can't be right. Anyway, the following is what happened. If you can help >> > me with the "setserial" command syntax that would be great to take me to >> > the next >> > point. >> > >> > johnw@Harm:/tmp/martian-full-20080625$ sudo wvdialconf /etc/wvdial.conf >> > Editing `/etc/wvdial.conf'. >> > >> > Scanning your serial ports for a modem. >> > >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >> > ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >> > ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >> > Modem Port Scan<*1>: S1 S2 S3 >> > >> > >> > Sorry, no modem was detected! Is it in use by another program? >> > Did you configure it properly with setserial? >> > >> > Please read the FAQ at http://open.nit.ca/wiki/?WvDial >> >
