Paul,
OK, I don't know that much about Mac internals but it strikes me there are a
couple of possibilities:
- my 9600 and 6100 do not have the same internal wiring as your 7600.
Possible because they each have different motherboards - but a bit unlikely
- my serial cable (also a commercial component bought from a Mac dealer)
does not connect DCD.
If it is the latter then there must be many other Mac users like myself who
will spend months mystified by the failure of diald to work. This can only
give them a poor opinion of linux - which is a bad idea. I nearly gave up
myself.
However, if diald passed through the pppd 'local' option (assuming this
works) then a note could be included in the diald documentation notifying
users of the problem and a solution worth trying. Since modifying pppd to
ignore DCD on my installation I have had no trouble at all.
There is also the question of why pppd always worked manually for me with a
standard PAP configuration and without using the 'local' option. There is
clearly some interaction between the diald and pppd programs that causes a
problem.
Iain
on 2/8/00 11:00 PM, Paul Mackerras at [EMAIL PROTECTED] wrote:
> Iain,
>
>> Pin Signal Name Description
> [snip]
>> 7 GPi General Purpose Input (modem port only: can be set
>> by software to act as a second clock)
>
> Normally GPi is connected to the DCD pin of the serial chip internally and
> to the DCD line of the modem externally. At least that's the way it is on
> my 7600, and I'm using a standard mac serial cable, not one I cobbled up
> myself.
>
> --
> Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
> +61 2 6262 8990 tel, +61 2 6262 8991 fax
> [EMAIL PROTECTED], http://www.linuxcare.com.au/
> Linuxcare. Support for the revolution.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
