Don't rerun $ wvdailconf or it will overwrite your functional /etc/wvdial.conf. Try unloading and reloading the drivers: modprobe -r agrserial modprobe -r agrmodem modprobe agrmodem modprobe agrserial Then wvdial MarvS On Wed, Oct 8, 2008 at 9:19 PM, cgomez.cu <cgomez.cu@xxxxxxxxx> wrote: > > Hi, > > I followed the steps described in > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg02512.html and my > modem work fine. > > When I recover from Hibernate don't work. Woh i can solve it? > > cgomez@grtau:~$ wvdialconf > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 S1 S2 S3 > ttySAGR<Info>: Device or resource busy > Modem Port Scan<*1>: SAGR > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > > > > Regards > -- > View this message in context: http://www.nabble.com/Modem-problem-after-Hibernate-tp19890620p19890620.html > Sent from the Linux Winmodem Support - Discussion mailing list archive at Nabble.com. > >
