Linuxant Linux drivers for Conexant chipsets - RIPTIDE driver installation      
company drivers
ALSA (audio) driver
ALSA (ppch) driver
HSF (softmodem) driver
DGC (modem) driver
HCF (modem) driver
RIPTIDE (audio) driver

RIPTIDE driver installation

Not logged in.
[Log in]
Please see the README file for general information.


Remove any old RIPTIDE drivers, either manually or by running "rpm -e riptide" or "make uninstall" if using the RPM or tar versions of this package respectively.


If your Linux distribution supports the RPM Package Manager, and has a recent libc, it is easiest to install the binary RPM package with METHOD A. METHOD B is for distributions without RPM support, or those who prefer not to use RPM.


If you have obtained the driver package in RPM format:

1. install the rpm with "rpm -i riptide-{version}.{arch}.rpm"

2. optionally re-run "ripconfig" to complete the installation (if necessary).

If you need to rebuild the binary RPM from source, you can get the TAR package and run: "rpmbuild -tb riptide-{version}.tar.gz" (if rpmbuild is not found, you might have to install the rpm-build package or if you have an older RPM version, try "rpm --rebuild ...")


If you have obtained the driver package in tar format:

1. extract the package with "tar -xzf riptide-{version}.tar.gz"

2. change to the package directory with "cd riptide-{version}"

3. run "make install" from the top of the package directory.

4. run "ripconfig" to complete the installation and configure your board.

(Alternatively to this whole procedure you may generate RPMS from the tar package using rpm -ta riptide-{version}.tar.gz")


If an error occurred during installation, please see the sections 'BUGS' and 'REPORTING PROBLEMS' below.

Once the drivers are installed and configured, you should check the entries in /etc/modules.conf to ensure that no other conflicting "sound" alias or audio/dsp/midi configuration exists.

The "ripconfig" command can be used to recompile (generic packages only) the kernel modules after installation. Run "ripconfig --help" for usage information.


The RIPTIDE drivers can be manually unloaded using the "ripstop" command.


If for any reason you wish to un-install the RIPTIDE drivers from your system, the proper way to proceed depends on how they were initially installed.

If you used an RPM installation method, execute "rpm -e riptide" to remove the package. If you used the tar method, change your current directory to where you extracted the archive, and execute "make uninstall"


If you require assistance or need more information, go to:

Conexant Systems neither distributes nor maintains this package. PLEASE DO NOT CONTACT CONEXANT REGARDING THIS SOFTWARE!!!


A list of currently known problems is included in the file "BUGS".


Additional problem reports or patches may be sent to:

Enclosing the output of "ripconfig --dumpdiag" in your report can greatly facilitate problem resolution.



User comment:

Hi! I am a Linux Beginner and installed the SuSE-Linux 8.2 version on my system a couple of days ago. At first my HCFPCI-modem (bought the computer system from Gateway 3 years ago...) did not work - of course there were no drivers installed as Linux could not identify the modem during installation. I did not expect at all that it would be possible to get the modem working, especially as SuSE does not support so called "winmodems". Anyway thanks to the devicemanager in win98 I knew that Conexant was the manufacturer. To make a long story short: I found your website , downloaded "hcfpcimodem-0.99lnxtbeta03042700k2.4.20_4GB-1suse.i586.rpm" and installed it successfully !!!! Juhu ! The modem works brilliantly and I am really happy that you also support the Linux operating system. so once again: thank you very much and have a nice day greetings from Germany

Hans-Peter Muller

Copyright © 2003-2008 Linuxant inc. All rights reserved.
Linuxant™ and DriverLoader™ are trademarks of Linuxant inc.
Linux is a trademark of Linus Torvalds in the US and some other countries.
Conexant™ and some product names are trademarks of Conexant Systems Inc.
Other trademarks belong to their respective owners.