cdeever wrote:
> To the Linux diald community,
>
> I've run into a show-stopper getting diald to work properly on my Linux
> box and I would appreciate any insights anyone might have.
>
> I have a simple ISP dialup account with a static IP - the ISP assigns the
> IP as if it were dynamic (I get the same IP upon connection everytime)
>
> Upon needing a connection, diald launches a chat script which connects OK
> to my ISP. Then when diald attempts to start pppd. Pppd exits saying
> (in syslog) Failed to open /dev/cua2: Device or resource busy."
>
> I'm running Slackware 3.5, linux kernel 2.0.34
> pppd 2.2.0 patch level 0
> diald .16 with patch applied
>
> I've checked each of the potential causes as presented in the diald FAQ.
>
> My /etc/ppp/options has almost all options turned off - however at one
> point, I tried with options file zeroed out with the same result. Root
> (who is starting diald) does not have a .pppdrc script.
>
> I'm at a loss - any ideas?
>
> Thanks,
>
> Chris Deever
Sometimes people _can_ overlook the obvious...
Maybe you meant to put /dev/cua1...
/dev/cua2? Are you sure? That's equivalent to COM3 in DOS. It would be
appropriate for an internal modem maybe, if you happen to have both the external
serial ports enabled as well; though that would be a fairly unusual situation.
Why? Because all the internal modems I've seen, even the cheap ones, can be set
up to operate as any COM port (1-4); and since there are only two serial port
IRQs, setting your modem to COM3 or COM4 means it is going to share an interrupt
with one of the serial ports on your motherboard. It's safer and more
straightforward to disable the second COM port in the motherboard's BIOS setup,
and set the internal modem serial port to COM2.
Of course if it's an external modem then it should probably be /dev/cua0 or
/dev/cua1 since all the motherboards I've seen have only two serial ports which
can only be set up as COM1 and COM2 under DOS.
Make sure you don't choose the same one your mouse is attached to!
If memory serves:
linux DOS IRQ
===================
/dev/cua0 COM1 4
/dev/cua1 COM2 3
/dev/cua2 COM3 4
/dev/cua3 COM4 3
When you are sure you have identified the right cu device the next thing to do
is to see if you can get a terminal emulator package (minicom or seyon usually)
to connect to the modem and dial out manually via AT commands from the keyboard.
You can even do:
$ echo 'ATDT0123456789' > /dev/cua0
or something like that just to see if the lights change on the modem or if you
hear the dial tones. If you can't connect this way then obviously there's a
hardware or driver problem somewhere.
Can anybody remember for sure if we are supposed to be using the cu drivers or
the ttyS drivers these days?
I find that the very best way to get diald and ppp set up is to use the terminal
emulator to go through the entire login and PPP protocol request by hand,
writing down all the prompts and responses and typical response times. This
makes it easy to write an accurate chat script that works the very first time.
Are you sure you have all the relevant support compiled into the kernel or as
properly configured modules? I seem to remember there is a 'gotcha' for diald in
that you need to include SLIP support even if you are using PPP as diald routes
through the SLIP interface first.
I beg your pardon if this is too elementary for you!
Ralph
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
