LinuxQuestions.org HCL

amos · 12-04-2003, 01:05 PM

If you are using a computer with an onboard SiS 7012 soundcard then you need to download the slmdm 2.7.10.tar.gz/bz2 tar ball, as the others I've tried seem to have some incompatability with the sound card.

Cheers
Amos

tmorton · 12-04-2003, 02:52 PM

Yes, also if you've got a Sager laptop with this modem, you'll need to enable ACPI support (e.g, rebuild your kernel).
--Taj

JeanBrownHarrel · 02-04-2005, 01:46 AM

I have tried to install the software for this winmodem but it will not work under Linux; only under Windoze. I have tried everything and nothing works. The documentation from Smartlink is worthless as is this so-called "modem" and the software. All is NO GOOD!!! Save your money and buy an external serial-port controller-based modem or buy US Robotics internal PCI 56K V.92 Performance Pro modem that works great!!! I highly recommend you to avoid the Smartlink "modems" and get the one I mentioned as Smartlink products are worthless and useless. I have a Smartlink 56K PCI winmodem that is supposed to work under Linux but it does NOT; it ONLY works under Windoze. The Performance Pro modem [a REAL modem!!!] is recognized by Linux as /dev/ttyS4 but you have to make a symbolic link of /dev/ttyS4 with /dev/modem and it works flawlessly!!!

yarek · 02-04-2005, 03:40 AM

Having installed drivers from net-dialup/slmodem ebuild ( http://linmodems.technion.ac.il/packages/smartlink/ ) and kernel drivers for AC'97 codec intel8x0m (-m stands for modem, obviously) I had no problems to make modem on my Notestar notebook work.

jsilve1 · 03-30-2005, 11:11 AM

I bought this Smartlink chipset modem as a CompUSA-branded modem. (But naturally CompUSA doesn't *make* the modem -- it is just OEM rebranded).

In any case, with the stock RHEL kernel, the smartlink drivers would simply not work. They actually compiled and installed, but the softmodem utility (slmodemd) would not create a softmodem device (/dev/slamr0) and the modules would not load with modprobe.

I tried serveal kernels before finally downgrading to the vanilla kernel 2.6.8.1 from kernel.org.

More of my story can be found here:
http://www.newtnotes.com/index.php?itemid=117&catid=3

later...

-Jeff

thandermax · 07-03-2005, 10:50 AM

WARNING : The driver provided is only for 2.4 version kernel !!! May not run in 2.6 version kernel ! Use it at your own risk .

It dosen't run in my 2.6 ver kernel , and i had to BUY ANOTHER MODEM !!!

I don't know if any driver will be written ever for 2.6 ver Kernel !!!!!

: WARNING :: WARNING :: WARNING :: WARNING :: WARNING :
: WARNING :: WARNING :: WARNING :: WARNING :: WARNING :

xukosky · 07-20-2005, 08:03 AM

I have been able to get this modem work with three different distributions: Red Hat 9, Fedora Core 2 and Debian Sarge 3.1, the first with a 2.4 series kernel and the two others with a 2.6 series kernel. I haven't tried with any other distributions so 100% success except for the 2.6.10 kernel in Sarge (downgraded to 2.6.8 and now working).

This modem is a bit hard but yes, it works with Linux, if you already have it you should be able to get it working but if you don't have it maybe you should consider buying another modem because you'll find a lot of people having problems with it anywhere. Of course, serial modems are the best choice with Linux.

That's why I can' recomend it and also because I wasn't able to enable the alsa compatibility.

The good points is that the driver continues being developed (at least until a few months ago) and it works better with every version, and yes, it works with the 2.6 series kernel (i promise you).

peter_89 · 02-08-2006, 07:48 AM

I bought this modem under the fact that the box claimed it came with support for Linux, or at least a driver. I bought it and installed it to my last PCI port, and booted to SUSE 9.3. Tried to load the driver that came on the CD, but soon realized that it was written about three years ago and only supported 2.4 kernels. I download the newer driver on SmartLink's web site and attempt to load it in, but as illustrated above there are many issues that come along with the driver, so many that I decided not to bother with it in Linux at all.
Just to give it a fair shot, however, I tried it in my Windows XP Professional installation. It recognized it and installed the stock driver automatically, but apparantly their driver was of a very low quality. I kept getting this problem where I'd keep getting disconnected about every 10 minutes, and it just got worse, to the point that I was getting disconnected every 30 seconds (I wish I were kidding). Having paid for this and feeling ripped-off, I went back and returned it.
Guys, even if you are in Windows, buy a real controller-based modem. I've had mine for years and it hasn't skipped a beat.

burntfuse · 03-13-2006, 08:03 PM

I bought this as a CompUSA-brand modem, thinking that it probably wasn't a winmodem since it wasn't labeled as one. In short: don't make my mistake, and stay far away from this one. There is an "official" driver, but it's very annoying. Unlike normal drivers, which are built as loadable modules, this "driver" comes in the form of a program that has to be running continuously in the background. That wouldn't be so bad by itself if I didn't keep on getting disconnected every 5-10 minutes like the last reviewer. I've already taken it out of my computer, and plan to return it as soon as possible. If you have to get a winmodem, get a PCTel, but it's much better to just get a real "hard modem".