Results 1 to 10 of 160

Thread: Howto Conexant and Smartlink modem

Threaded View

  1. #1
    Join Date
    Apr 2005
    South Africa
    Kubuntu 7.04 Feisty Fawn

    Howto Conexant and Smartlink modem

    I have had to revise the Howto's for installing a Conexant winmodem and a Smartlink winmodem due to some changes after installing Dapper kubuntu.
    As some of you wanted this urgently here goes: ( also note that some of this information (and drivers) may be out of date as I have not used the Smartlink modem since updating to Feisty)

    Howto get Conexant HSF modem to work in Dapper Kubuntu
    Please note that this open driver used below does not work in Edgy or Feisty, the only free driver that does work is by Linuxant and is restricted to 14400 and needs registration at a fee to open up.

    Conexant modems can mostly be made to work in linux by using older drivers that were open source and thus free. Do not laugh, but presently Conexant drivers are free for Windows, but have to be purchased seperately at about $15 for free linux! These purchased drivers are said to be free, but the free version only supports speeds up to14400 and if you want maximum 56k you have to pay. Below you will find two different methods for installing the open source drivers that run at the full 56k and this should work in Ubuntu Dapper and other versions, but I have only tested in Dapper Kubuntu. This came about when Rafael Espíndola ported the latest Conexant open source version to 2.6.x kernels. AlexandreOttoStrube packaged it for Ubuntu Breezy using kernel 2.6.12-9 The.deb file thus will not work on any newer kernel unless you compile it yourself as below. The files can be downloaded from or courtesy AndyRabagliati
    Firstly to ensure you have a modem that may work with these drivers, look at the make and model of your modem, by looking at the chipset. If it shows HSF and the number CX11252 (maybe other numbers here) on the chip then you have a softmodem/winmodem/linmodem and this driver should work. You can also install it on a Windows pc and do a modem query and if it shows PCI/VEN_14F1&DEV2F00 then you know it should work.
    The best way is to use your terminal to check your Vendorevice pci id with "lspci" :
    0000:01:0b.0 Communication controller: Conexant HSF 56k Data/Fax Modem (rev 01)
    Then, type "lspci -n" and look at the same identifying numbers to get the vendor:device id
    lspci -n
    0000:01:0b.0 0780: 14f1:2f00 (rev 01)
    In this example, it's 14f1:2f00. Vendor ID is first part (14f1), then a ":" separates the Device ID (2f00).

    Vendor ID's that are suported are listed here:
    Vendor id 14fi = Conexant
    8086 = Intel or Ambient
    125D = ESS Technologies/Creative
    2003 = Smartlink/Netodragon
    10B9 = ALI/Netodragon Acer Labs Incorporated

    VendorID=14F1 : DeviceID=2F00 Tested and works on Dapper
    VendorID=14F1 : DeviceID=2F01
    VendorID=14F1 : DeviceID=2013 Tested and works
    VendorID=14F1 : DeviceID=2014
    VendorID=14F1 : DeviceID=2015
    VendorID=14F1 : DeviceID=2016
    VendorID=14F1 : DeviceID=2F10
    VendorID=14F1 : DeviceID=2F11
    VendorID=14F1 : DeviceID=2F12
    VendorID=14F1 : DeviceID=2F13
    VendorID=14F1 : DeviceID=2F14
    VendorID=14F1 : DeviceID=2F20
    VendorID=14F1 : DeviceID=4311
    VendorID=127A : DeviceID=1025
    VendorID=127A : DeviceID=2004
    VendorID=127A : DeviceID=2005
    VendorID=127A : DeviceID=2013
    VendorID=127A : DeviceID=2014
    VendorID=127A : DeviceID=2015
    VendorID=127A : DeviceID=2016
    VendorID=127A : DeviceID=4311
    VendorID=127A : DeviceID=2114
    VendorID=8086 : DeviceID=2416
    VendorID=8086 : DeviceID=2446
    VendorID=8086 : DeviceID=2486
    VendorID=1106 : DeviceID=3068
    VendorID=10B9 : DeviceID=5453
    VendorID=10B9 : DeviceID=5457
    VendorID=14F1 : DeviceID=2043
    VendorID=14F1 : DeviceID=2044
    VendorID=14F1 : DeviceID=2045
    VendorID=14F1 : DeviceID=2046
    VendorID=14F1 : DeviceID=2443
    VendorID=14F1 : DeviceID=1631
    VendorID=14F1 : DeviceID=1636
    VendorID=14F1 : DeviceID=1637

    Download the following files:
    modem-hsfpci.tar.bz2 from
    conexant_192-1ubuntu-1.tar.gz from

    This software supports the Conexant HSF 56k HSFi Modem, and was not tested with all models, anyone varifying a model to please update this with “tested and works” next to the ID list for help to others.
    As you are going to compile your own drivers it is necessary that the required files are installed, check and/or install with Synaptic that the following are there:
    build-essential, linux-headers-ARCH, debhelper and fakeroot is installed, ARCH is the result you get if typing uname -r in a terminal – version of kernel.

    Method A:
    This comprises of creating a .deb file and then using that to install and configure the driver.
    1.Create a folder called HSFmodem on your Desktop and put both downloaded files in it, modem-hsfpci.tar.bz2 and conexant_192-1ubuntu-1.tar.gz
    2.Now right click on modem-hsfpci.tar.bz2 and Extract Here (in same folder) a folder and a folder modem-hsfpci-0.1 and a file HOWTO.txt will be created.
    3.No go to the konsole and enter:
    cd Desktop/HSFmodem
    and a file modem-hsfpci_0.1-0ubuntu1_386.deb will be created in folder /HSFmodem
    4.You can install it with
    sudo dpkg -i modem-hsfpci_0.1-0ubuntu1_i386.deb
    5.Go to file /etc/modem-hsfpci/modem-hsfpci.conf Right click, click Actions then Edit as Root and Kwrite should open file modem-hsfpci.conf
    Remove the comment # from your country and also from the Vendorevice ID number determined above. If your ID are not shown you can try to create it in a new line, but there is no guarentee that it will work. If you do not do this the country will default to USA and the script will try to determine the Vendor ID with lspci.
    6.Now you have to do the following to compile and install the configuration files and modules for your kernel version.
    sudo /usr/sbin/modem-hsf --install
    You should see the last line refering to modem installed and available on /dev/modem A symlink has also been created to the /dev/ttySHSF0 device.
    7.You may have to reboot. The modem can be tested in Kppp by using Modem Query on /dev/modem. If it sees it you are OK and ATI 5 should show your country code.
    8.You can uninstall by using Synaptic to completely uninstall modem-hsfpci_0.1-0ubuntu1

    Note: Everytime you install a new kernel, especially after an update you will have to use the sudo /usr/sbin/modem-hsf --install command to build kernel modules for it.

    It has been suggested that you also try ATW2DT instead of ATDT when setting up your dialler (Kppp).

    Method B:

    1.Put the downloaded file conexant_192-1ubuntu-1.tar.gz on your Desktop and right click “Extract Here” and a folder “conexant” will be created on your Desktop.
    2.Read the txt files in the folder for more info.
    3.Open the folder “conexant/modules/makefile”, right click on makefile, click Actions, then Edit as Root and Kwrite should open the file /conexant/makefile. Now find the 2 lines that start with # KERNELDIR? = /lib/modules..... etc. and KERNELDIR?= /usr/src... etc Remove the comment # in the first line and insert comment # on second line and save changes.
    4.Now open the /conexant/makefile in the same way and find the commented line # rm -rf $$DESTDIR/dev/ttySHFS0. Remove the comments from the mentioned line and the following 3 lines up to “update modules” and save changes Desktop/conexant
    7.sudo make install
    8.sudo modprobe hsfserial (you should get no result report if OK)
    9.dmesg | grep hsfserial ( you should get no result report if OK)
    10.The /dev/ttySHFS0 is created for the modem
    11.To test, use the query modem on Kppp

    To remove the installation:
    rm /dev/ttySHFS0
    rm -r /etc/hsf
    rm /lib/modules/ARCH/misc/hsf*

    Howto get Smartlink winmodem working in edgy

    Smartlink soft modems work quite well in ubuntu, but some problems have been found and the process below works in Edgy. It also seems as if the Smartlink modems with Netodragon chip MDV92XP do not work, but the ND92XPA chip works with the process below. Also read the ubuntu wiki dialupmodemhowto for details and other methods.
    Use Synaptic or Adept to ensure that you have all the necessary packages installed for compiling your drivers. This includes build-essential, linux-headers-ARCH (where ARCH is your kernel version and can be found with uname -r in the terminal), fakeroot, module-assistant and debhelper.
    Basically the sl-modem-source has to be installed first and then the sl-modem-daemon. It seems as if the latest daemon also looks for ungrab-winmodem so download and install this from the linmodem website.
    Please note that you will have to do this after everytime you update your kernel.

    Method A:

    This method uses the latest packages from linmodems and the latest daemon on the Edgy repository or from the Debian repositories and works well.
    1.Download slmodem-2.9.11-20061021.tar.gz from
    This package seems to work better in breezy and dapper and does not give the dialing problem that causes the modem to fail on ATDT and not dial out.
    2.Also download and install the ungrab-winmodem from the
    linmodem website by using extract, make and sudo make install. (same as step 3)
    3.Copy the sl-modem-2.9.11-20061021.tar.gz file to your Desktop and right click on it and select “Extract here” and a folder wth the same name will be created with the extracted files on your Desktop.
    4.Now rename the folder to an easier name such as “slmodem”.
    5.Open a terminal and cd in to the slmodem folder or drag and drop in the terminal and select cd when asked.
    6.Type make
    7.Type sudo make install
    8.Type sudo modprobe slamr
    9.Type dmesg | grep slamr
    10.Now enable your repositories and install sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5build1_i386.deb with Synaptic or Adept or download sl-modem-daemon_2.9.9d+e-pre2-7.deb from the debian website if you want the latest daemon.
    11.Use Kppp to query the modem on /dev/modem, if this works you are there! If you are not using Kubuntu then just see if it works from Gnome-ppp (wvdial must first be set up)
    12.Edit /etc/default/sl-modem-daemon to change the line SLMODEMD_COUNTRY= USA to i.e SOUTHAFRICA or your country
    13.Type sudo /etc/init.d/sl-modem-daemon restart to restart the daemon or just reboot.
    14.If you again do a “Query modem” in Kppp and you will see that your country has changed.

    Method B:
    This is the ideal way. Synaptic or adept to install sl-modem daemon and sl-modem-source as well as ungrab-winmodem as a dependancy from the repositories
    This also means that the files need to be updated for the newer versions of the kernel everytime. Unfortunately the sl-modem files on bothe the dapper and edgy repositories are long out dated and do not work. Someone needs to compile new drives from the files as in method A
    ( At the moment this fails and the sl-modem-module is not created when installing with Synaptic, the install is successful if the install is done with sudo module-assistant auto-install sl-modem, sudo depmod -a The modem is then detected but fails on ATDT and does not dial out) This problem was already noted in Breezy. We need a .deb file made from slmodem-2.9.11-20061021.tar.gz that has already been proven to work in Breezy and Dapper)
    • Also download and install the ungrab-winmodem from the linmodem website. Install with, extract, make, sudo make install.
    • Enable the universe/multiverse repositories
    • Use Synaptic or Adept to search for sl-modem
      You will find 2 files called sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5build1_i386.deb and sl-modem-source_xxxxxx.deb (this file with xxxxxx is not ready yet)
    • Install the sl-modem-source and then the sl-modem-daemon
    • Now go to /etc/default/sl-modem-daemon, right click, Action, Edit as Root, find the line SLMODEMD_COUNTRY=USA and change the USA to SOUTHAFRICA or your country name.
    • Go to the konsole:
    • sudo modprobe slamr
    • sudo /etc/init.d/sl-modem-daemon restart
    • Now go to Kppp and select /dev/modem and use the Query Modem to test you modem. Now setup Kppp and go on line!
    Note: If you are going to use Kppp it is advisable that you first activate the line #noauth by removing the # comment in /etc/ppp/peers/kppp-options.

    To release a locked up Smartlink modem use sudo modprobe ungrab-winmodem, then sudo modprobe slamr, then restart the daemon with sudo /etc/init.d/sl-modem-daemon restart. This may help you from rebooting.

    The daemon package shown above, whether from the debian repo or ubuntu repos works with any of the driver packages, but only the linmodem driver package slmodem-2.9.11-20061021.tar.gz seems to be the latest for the edgy and dapper kernel version. We thus need this package to be put on the ubuntu repos. The ungrab-winmodem package should also be a 'dependancy” for the daemon package and also be installed together by Synaptic.

    To remove any installation go to Synaptic, search for sl-modem and uninstall completely. Then use Krusader in root mode to search for sl-modem. Double click on any found (except those in your repository or download folder) and right click for delete. This clears all left over dreggs and leftovers of a previous installation that may be causing a problem with a new sl-modem install. Be very careful before you delete anything in this way.
    Last edited by Matchless; June 18th, 2007 at 07:18 PM. Reason: note on HSF conexant drivers for Edgy or Feisty

    Proudly kubuntu!


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts