What I meant by "didn't point to a modem" was that the device I specified
in diald as my modem was really another serial port with nothing attached,
or even a port which did not exist on the machine. I had this happen a few
times as I was bringing up a diald server and had changed modems and ports
but forgot to update the scripts. It also happened when I tried invoking
a chat script after diald shut down to make sure that the modem was
on-hook. I found that I needed to use DIP instead (in hindsight this was a
dumb mistake) but nonetheless I got a the "can't get terminal parameters"
error when chat couldn't see the modem port.
If you are sure that the port you give diald is really where the modem
lives then the error could come from a dead or non-responsive mode. Test
the modem using DIP or minicom to see if it working as it should.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
