On 23 Jul, Cheshire wrote: >> > Jul 20 00:51:29 cheshire chat[304]: send (ATZ^M) >> > Jul 20 00:51:29 cheshire chat[304]: expect (OK) >> > Jul 20 00:51:38 cheshire chat[304]: >> > Jul 20 00:51:48 cheshire chat[304]: OK >> > Jul 20 00:51:48 cheshire chat[304]: -- got it >> > Jul 20 00:51:48 cheshire chat[304]: send (ATDT7770591^M) >> > Jul 20 00:51:48 cheshire chat[304]: expect (CONNECT) >> > Jul 20 00:51:48 cheshire chat[304]: ^M >> > Jul 20 00:51:58 cheshire chat[304]: ATZ^M^M >> > Jul 20 00:51:58 cheshire chat[304]: OK^M >> > Jul 20 00:52:33 cheshire chat[304]: alarm >> > Jul 20 00:52:33 cheshire chat[304]: Failed >> > Jul 20 00:52:33 cheshire pppd[300]: Connect script failed >> > Jul 20 00:52:34 cheshire pppd[300]: Exit. >> >> This log shows the system neither dialing nor connecting. >> Can you really hear it dial? > > Actually, ya :) > > I could hear a dial and subsequent connection, but everything kinda > terminated after that. > > But I did nail down the problem and tried to let everyone know with a > message that you might have missed--I hadn't run setserial to resolve my > non-default irq. > > But with that I've run into another small thing. I run 'setserial > /dev/ttyS2 irq 5' and voila, problems solved, except if I reboot, that > setting is lost and I must run setserial again. Can anyone tell me how > to permanently set it, or at least run setserial on boot up? > > thanx > > |cheshire| > > ps--sorry to those that I sent this message to personally via 'reply'. I > hate how it doesn't set debian-user for the reply to field :| > >
try uncommenting the /dev/ttyS2 line in the manual part of the /etc/rc.boot/0setserial file and altering it to match your configuration. I`m no expert but it worked for me. Paul
