[wellylug] Smartlink winmodem issue
Bill Christiansen
bill.christiansen at paradise.net.nz
Tue Jun 8 12:59:22 NZST 2004
Hi Lynsay,
sounds like the driver is not 100% stable with your kernel or hardware.
You can get a bit more info on your modem by typing "lspci -v" in a
terminal. On my Toshiba laptop it says I have a Lucent Microelectronics
56k winmodem. My modem uses an Agere Core chipset (which your's may also
if that's what the AC stands for). I downloaded the
ltmodem-8.31alek.tar.gz file from http://ltmodem.heby.de/.
It is compatible with the 2.6.4 kernel but will require your kernels
source directory to compile on your system. Was your driver installed
from source or a binary package?
Bill
Lyndsay Mountfort wrote:
> Hi Luggers
>
> I wonder if anyone has experienced this or a similar problem:
>
> I have an onboard SiS630 AC'97 winmodem in my asus laptop using a
> Smartlink driver. This works fine at or soon after boot up, but after
> the laptop has been running for a while, it fails. It dials ok, but
> fails to negotiate successfuly, and eventually kppp reports "no
> carrier". If I listen to what is coming from the modems (via a phone
> handset) at that stage all there is is a high pitched warbling noise.
> Redialling just ends up with the same result.
>
> All I need to do to get it to go again, is stop and restart the driver
> daemon (slmodemd).
>
> Also I have to do this at the command line - running the same two
> commands via a shell script seems to work, but KPPP fails to find the
> modem device, but I guess that's a separate issue.
>
> But my question is - does anyone have any suggestions as to why the
> whole setup fails after a certain amount of time, and why restarting
> the daemon clears it up. Maybe it is effectively the same as resetting
> the modem??
>
> I'm now running Mepis Linux (Debian unstable) with a 2.6.4 kernel. The
> modem worked "out of the box" with this distro. But I had very similar
> issues with the same laptop running RadHat 9 once I got the modem
> going at all by installing the driver myself, although at that stage I
> hadn't discovered the "cure" by restarting the daemon.
>
> Any helpful comments or even speculation as to what is going on would
> be much appreciated!
>
> Lyndsay
>
>
More information about the wellylug
mailing list