For the Debian related distributions including Ubuntu derivatives,
there is a package sl-modem-daemon
Thank you for the advice. The "$ sudo /etc/init.d/sl-modem-daemon restart"
command does the trick. Fantastic. I also upgraded to the newest package
from http://phep2.technion.ac.il/linmodems/packages/smartlink/ , but have
not noticed any functional difference. Would there be some compelling reason
to make that switch on every install I do?
Also, how would I automatically call the restart command upon resuming from
an ACPI sleep state? I don't mind the console, but my non-technical wife
will also be using this laptop, and the more I automated I can it get the
better.
Thanks, Matt
From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx>
To: DISCUSS@xxxxxxxxxxxxx
Subject: Re: No Carrier error after suspend, USA Ubuntu 6.10 kernel
2.6.17-10-generic
Date: Thu, 8 Feb 2007 08:25:09 -0500
RE: In your case (ALSA driver) just do as root "/etc/init.d/slmodemd
restart"
For the Debian related distributions including Ubuntu derivatives,
there is a package sl-modem-daemon providing such start/stop/restart
functions, with corresponding command
$ sudo /etc/init.d/sl-modem-daemon restart
These scripts provide for setup upon boot of the modem through the command:
slmodemd -c USA --alsa modem:1
or equivalent for your System. The configuration settings are in
/etc/default/sl-modem-daemon , with maintenance by "Eduard Bloch"
<blade@xxxxxxxxxx>
Note that it provides the slmodemd provided is NOT as recent as that
in the SLMODEMD.gccN.tar.gz at
http://phep2.technion.ac.il/linmodems/packages/smartlink/
So if you search out with sl-modem-daemon the package at
http://packages.ubuntu.com/ and install it with
$ sudo dpkg -i sl-modem*.deb
you may wish to replace its older slmodemd with that from
http://phep2.technion.ac.il/linmodems/packages/smartlink/
Just copy the newer slmodemd to /usr/sbin/slmodemd
$ sudo cp slmodemd /usr/sbin/slmodemd
MarvS
On 2/8/07, Joern Wuestenfeld <j.wuestenfeld@xxxxxx> wrote:
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
_________________________________________________________________
Check out all that glitters with the MSN Entertainment Guide to the Academy
Awards® http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline2
