I realise this isn't amd64 related but it's definitely suse. (Sorry it's slightly off topic, but it might be an issue with amd64 suse (probably is) so isn't entirely) Recently we updated our gateway... We had been using 7.2, using the wvdial.dod/diald method... But the hardware it was installed on was a bit crap, constant lockups, and when a new error involving ide timeouts started, we decided to switch to a new machine, thinking, let's install the latest suse on this one. So far, dial on demand has been a nightmare. No longer is the wvdial.dod script available, now we seem to be forced to rely on the smpppd daemon and q/k/cinternet. At first, it wouldn't even start at bootup. It took a while to locate the option to replace in the ifcfg-modem0 script. It was set to manual. not ideal... Now I know it's onboot, that issue's cleared, but, and this is a big but... With the old setup, the modem would dialup even after being turned off all night... Now? It seems the process dealing with the modem just terminates if it can't find it when it tries to connect... Is there anything? Any option, any setting, any program that I can use to setup this thing to work as before? Just dial, ON DEMAND, whether the modem's been on for a few minutes or off all weekend? If all else fails I'll just setup a cron job to prod the modem with a cinternet -A command every 10 minutes or so, but that should not be necessary. Again, sorry about the mild off-topicness of this, but I'm subscribed to this one, and having poked my head around the door of the spam infested suse-e list, I decided this was the best place.