The problem seems to be that this is not the original purpose of the
auto_reconnect_delay (see wvdialer.cc).
Auto Reconnect was originally designed to try *redialing*
automatically if your ISP disconnected you or if they gave a busy
signal. In case of problems connecting, wvdial has a backoff timer,
so it'll first wait 5 seconds, then longer and longer each time it
fails. That's why it's not configurable: because the timer is
self-tuning.
However, if wvdial has trouble initializing your modem, that's
considered a critical failure, because it's usually not something you
can fix simply by trying again. Or at least, that's what we thought
when we wrote it :) Apparently in your case, it would have worked
just fine if we had only waited a bit longer.
If you want to try modifying the default timeout, for now you'd have
to modify wvdial itself. Go to around line 548 of wvdialer.cc and
look for the line:
auto_reconnect_delay = 5; // start at 5 seconds
Increase the number 5 to something that sounds right to you. Let us
know if it helps, and if so, we can add an enhancement to wvdial,
basically one or both of:
1) Make the default auto_reconnect_delay configurable
2) Make modem initialization failures not fatal, so the retry backs
off just like it would if there were a dialing problem.
Have fun,
Avery
Great. I wish it were easier, but I don't think this problem has ever
been reported to us before.
Avery