Hi Matthew, Marvin, just to give some technical insight: The power management of most drivers is still focused on APM, while most systems nowadays have ACPI. Thus all drivers need to be changed to get informed about a suspend / resume of the system. For most modem drivers (ltmodem, slamr) I know off, this has not been done. So you need to unload and reload your modem driver to initialize the hardware again. In your case (ALSA driver) just do as root "/etc/init.d/slmodemd restart". This should unload and reload the modemdriver and initialize the hardware again. Joern Matthew Brinkerhff wrote: > Thanks Marvin -- I had actually already figured that one out before > sending the original message, and accidentaly send an old version of > my wvdial.conf file. Unfortunately, I still have the original problem. > > As I said before, my modem works quite well on a newly booted system. > In fact, I'm sending this email with it. The problem is that it stops > working after resuming from a hibernate or suspend. The system detects > it just fine, but for some reason it won't dial--just gives an > automatic "No Carrier" error. Rebooting fixes it -- until the next > time I suspend, anyway. > > I'm sure I just need to reload some module or something, but don't > know what it could be. > > Thank you, > Matt > > >> From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> >> To: "Matthew Brinkerhff" <mbbrinker@xxxxxxxxxxx> >> CC: DISCUSS@xxxxxxxxxxxxx >> Subject: Re: No Carrier error after suspend, USA Ubuntu 6.10 kernel >> 2.6.17-10-generic >> Date: Wed, 7 Feb 2007 12:44:56 -0500 >> >> Matt >> >> RE: Phone = 494-4075 >> Try instead: >> Phone = 4944075 >> >> On 2/7/07, Matthew Brinkerhff <mbbrinker@xxxxxxxxxxx> wrote: >> >>> I have Ubuntu 6.10 on a Dell Inspiron 5100 laptop. After some >>> configuration, >>> the internal modem mostly works using ALSA drivers and the smartlink >>> daemon >>> from the Ubuntu repositories. >>> >>> While the modem works well upon startup, it fails to connect to the >>> Internet >>> after I suspend or hibernate the system. Wvdialconf still detects >>> the modem >>> fine. "$ sudo wvdial" begins the connection process, but brings back >>> a "No >>> Carrier" error and goes into an endless "Trying again" loop until I >>> kill it >>> with ctl-c. >>> >>> I assume something just needs to be re-loaded, but don't know what. >>> Rebooting fixes the problem, but is not ideal. >>> >>> I have looked all over for a solution but have as yet been >>> unsuccessful. >>> >>> I have attached three files: >>> 1) my ModemData.txt >>> 2) my wvdial.conf >>> 3) the log from wvdial when I attempt to connect after suspending or >>> hibernating the system. >>> >>> Any help or guidance about where to look for answers would be >>> appreciated. >>> >>> Thanks: >>> Matt >>> >>> _________________________________________________________________ >>> FREE online classifieds from Windows Live Expo – buy >>> and sell with people >>> you know >>> http://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://expo.live.com?s_cid=Hotmail_tagline_12/06 >>> >>> >>> > > _________________________________________________________________ > FREE online classifieds from Windows Live Expo – buy and sell with > people you know > http://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://expo.live.com?s_cid=Hotmail_tagline_12/06 > > -- Dr. Joern Wuestenfeld Forschungszentrum Dresden - Rossendorf Abt. FWKH Tel: +49 351 260 3263 Postfach 510119 FAX: +49 351 260 3700 01314 Dresden eMail: j.wuestenfeld@xxxxxxxxxxxxxxxx
