~ 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.
now I see the picture, but it doesn't look like my case. (since I am very
sure that my modem sits on ttyS0, otherwise pppd wouldn't work with the same
setup).
~ 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.
manual connection, is it what you mean? well, yes, it works fine with it. I
am not quite sure whether echoing should be off or on with dip.. also I
specify speed to 38400 while modem could handle 14400 as maximum, maybe this
also creates a mess? I wouldn't think so, since serial port goes faster
anyway, but maybe diald is catchy about this thing?
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
