Wvdial, Pon Broke On Sarge-Stable, Only Pon works On Woody-Done Everthing I Know-Need Help

2005-06-26 Thread Debian User Leonard Chatagnier
Discovered wvdial and pon not working after finally getting the 2.4.27-2-386 KI to boot. Ran wvdialconf and pppconfig which didn't change anything. Chmod a+rwx on all wvdial and wvdial.conf files. Some Debians may say that's not the way, but I don't want to use su and don't have to on pon,

Re: Wvdial, Pon Broke On Sarge-Stable, Only Pon works On Woody-Done Everthing I Know-Need Help

2005-06-26 Thread Marty
Debian User Leonard Chatagnier wrote: Discovered wvdial and pon not working after finally getting the 2.4.27-2-386 KI to boot. Ran wvdialconf and pppconfig which didn't change anything. Chmod a+rwx on all wvdial and wvdial.conf files. Some Debians may say that's not the way, but I don't want

[Fwd: Re: Wvdial, Pon Broke On Sarge-Stable, Only Pon works On Woody-Done Everthing I Know-Need Help]

2005-06-26 Thread Debian User Leonard Chatagnier
---BeginMessage--- Marty wrote: Debian User Leonard Chatagnier wrote: Discovered wvdial and pon not working after finally getting the 2.4.27-2-386 KI to boot. Ran wvdialconf and pppconfig which didn't change anything. Chmod a+rwx on all wvdial and wvdial.conf files. Some Debians may say

Re: Wvdial, Pon Broke On Sarge-Stable, Only Pon works On Woody-Done Everthing I Know-Need Help

2005-06-26 Thread Marty
Debian User Leonard Chatagnier wrote: Hi Marty, Took out init3=ATDT, logged out KDE and back in and still getting same wvdial error message, ie., no dialer defaults. This doesn't seem to appear in Bug #276020, so it looks like a different problem. So, shut down and rebooted and runing

Re: Wvdial, Pon Broke On Sarge-Stable, Only Pon works On Woody-Done Everthing I Know-Need Help

2005-06-26 Thread Debian User Leonard Chatagnier
Marty wrote: Debian User Leonard Chatagnier wrote: Hi Marty, Took out init3=ATDT, logged out KDE and back in and still getting same wvdial error message, ie., no dialer defaults. This doesn't seem to appear in Bug #276020, so it looks like a different problem. So, shut down and