John, Near the bottom of http://www.linuxant.com/drivers/hcf/full/downloads.php use the hcfpcimodem_1.21full_i386.deb.zip which includes tbe resources for compiling the drivers. MarvS On Fri, Oct 29, 2010 at 5:38 PM, Sacman Agency Staff <staff.asacman@xxxxxxxxxxxxxxxxx> wrote: > ÂTwo Issues: > > 1) ÂAs far as the HCF driver is concerned, there is not one listed for the > installed kernel 2.6.24-28. ÂThe ModemData.txt file mentions to download > 7.80.02.06full_k2.6.24_28_generic_ubuntu_i386.deb.zip. Âcould not find it > listed. Âthe closest is 2.6.24-26-generic > hcfpcimodem_1.21full_k2.6.24_26_generic_ubuntu_i386.deb.zip, which does not > work. Âis it possible to get this functioning with my kernel? > > 2) Âthe apt-get update and install linux-kernel-devel were run. ÂThe RIPTIDE > driver install and the ripconfig were run with the following results: > > sacserve@sacserve:~$sudo make install > > make[1]: Entering directory > `/home/sacserve/linuxant/riptide-0.6lnxtbeta03122800/scripts' > install -m 755 ripconfig ripstop /usr/sbin > make[1]: Leaving directory > `/home/sacserve/linuxant/riptide-0.6lnxtbeta03122800/scripts' > cc1: error: /lib/modules/2.6.24-28-generic/build/include/linux/config.h: No > such file or directory > make[1]: Entering directory > `/home/sacserve/linuxant/riptide-0.6lnxtbeta03122800/modules' > rm -rf "/usr/lib/riptide/config.mak" "/usr/lib/riptide/modules" > mkdir -m 755 -p /usr/lib/riptide/modules > prevsum=""; md5sum `find binaries -type f -print`</dev/null | sort | while > read sum file ; do \ >        Âif [ "$sum" = "$prevsum" ]&& Âcmp -s "$file" "$prevfile"; > then \ >            Ârm -f "$file"; \ >            Âln "$prevfile" "$file"; \ >        Âelse \ >            Âprevsum="$sum"; \ >            Âprevfile="$file"; \ >        Âfi; \ >    Âdone > (cd ..&& Âfind config.mak -depth -print | cpio -pdm /usr/lib/riptide) > 2 blocks > find . \( -name '*.sh' -o -name '*.[ch]' -o -name '*.mak' -o -name > '[Mm]akefile' \) -print | cpio -pdm /usr/lib/riptide/modules > 580 blocks > find binaries -depth -print | cpio -pdm /usr/lib/riptide/modules > 0 blocks > make[1]: Leaving directory > `/home/sacserve/linuxant/riptide-0.6lnxtbeta03122800/modules' > install -m 444 LICENSE riptide.hex /usr/lib/riptide > > To complete the installation and configuration of your RIPTIDE board, > please run "ripconfig" (or "/usr/sbin/ripconfig") > > sacserve@sacserve:~$ sudo ripconfig > Linux RIPTIDE audio/communication drivers, version 0.6lnxtbeta03122800 > > WARNING: this is an EXPERIMENTAL BETA VERSION of the RIPTIDE drivers for > Linux. > USE AT YOUR OWN RISK! See the file /usr/lib/riptide/LICENSE for details. > > Conexant Systems neither distributes nor maintains this package. > PLEASE DO NOT CONTACT CONEXANT REGARDING THIS SOFTWARE!!! > > If you require assistance or need more information, go to: >       Âhttp://www.linuxant.com/drivers > > When reporting a problem for the first time, please send > us the file generated by "ripconfig --dumpdiag". > grep: /proc/ksyms: No such file or directory > [: 809: 100: unexpected operator > > RIPTIDE drivers have not been fully tested on SMP kernels. > Please report results to<riptide-bugs@xxxxxxxxxxxx> > > This package does not contain pre-built modules suitable for your system: > ÂDistribution: Debian-lenny/sid > ÂKernel arch: i686-SMP > ÂKernel version: linux-2.6.24-28-generic > > Trying to automatically re-compile the modules.. > (this requires a C compiler and proper kernel sources to be installed) > > Where is the linux source build directory that matches your running kernel? > [/lib/modules/2.6.24-28-generic/build] > > WARNING: missing file > /lib/modules/2.6.24-28-generic/build/include/linux/modversions.h > The cause of this problem is usually a missing or misconfigured > kernel source tree (and sometimes an incorrect directory or symbolic link). > > First, ensure that the proper kernel source and compiler packages > from your distribution vendor and/or the community are installed. > > The Linux kernel can then be reconfigured by running "make menuconfig" > under the kernel source directory (usually /usr/src/linux). > > Verify that the proper options for your system are selected, > and that CONFIG_SMP ("Symmetric multi-processing support" under > "Processor type and features") is disabled, as this driver is > presently designed to work on single-processor machines. > > Then compile and install your new kernel (for more information about > this procedure, see the README file under the kernel source directory), > reboot the system using the new kernel, and re-run "ripconfig". > > > > Not sure where to go from here. > Thanks > > > > On 10/28/2010 8:05 PM, Marvin Stodolsky wrote: >> >> John, >> >> I need to do a correction in scanModem concerning Riptide, concerning your >>  0780 Communication controller: Rockwell International Riptide HCF >> 56k PCI Modem >>   ÂPrimary device ID: Â127a:4321 >> ÂSupport type needed or chipset:  ÂHCF.Riptide >> >> On http://www.linuxant.com/drivers/riptide/index.php it is instructed: >> If you have a RipTide HCF modem (127A:4321 or 127A:4331), you need to >> install *both* the RIPTIDE and HCF drivers, otherwise the modem will >> *not* work. >> So get to work on that process, after first establishing compiling >> support as Tony instructs. >> >> MarvS >> scanModem maintainer >> >> On Thu, Oct 28, 2010 at 10:22 PM, Antonio Olivares >> <olivares14031@xxxxxxxxx> Âwrote: >>> >>> John, >>> >>> Before you attempt to do anything, you need to get compiler& Âkernel >>> source/kernel headers: >>> >>> ÂThe kernel was compiled with gcc version 4.2.4 and a compiler is not >>> installed >>> >>> Âlinux-headers-2.6.24-28-generic resources needed for compiling are >>> not manifestly ready! >>> >>> But it also tells you how you may fix this: >>> >>> If an alternate ethernet connection is available, >>> $ Âapt-get update >>> $ Âapt-get -s install linux-kernel-devel >>> will install needed packages. >>> For Debian/Ubuntu related distributions, run the following command to >>> display the needed package list: >>> >>> Otherwise packages have to be found through http://packages.ubuntu.com >>> Once downloaded and transferred into a Linux partition, >>> they can be installed alltogether with: >>> $ sudo dpkg -i *.deb >>> >>> try get those packages, and then follow the directions provided here: >>> >>> Predictive Âdiagnostics for card in bus 00:0b.1: >>>  Modem chipset Âdetected on >>> NAME="Communication controller: Rockwell International Riptide HCF 56k >>> PCI Modem" >>> CLASS=0780 >>> PCIDEV=127a:4321 >>> SUBSYS=1235:4321 >>> IRQ=9 >>> IDENT=HCF.Riptide >>> >>> ÂFor candidate modem in: Â00:0b.1 >>> Â0780 Communication controller: Rockwell International Riptide HCF >>> 56k PCI Modem >>>   Primary device ID: Â127a:4321 >>> ÂSupport type needed or chipset:  ÂHCF.Riptide >>> ÂUnder Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read >>> DOCs/InfoGeneral.txt about alternatives. >>> >>> >>> For owners of a Dell PCs with Conexant HSF modems, a driver source >>> package with full speed enabled is available, but requires driver >>> compiling. Read DOCs/Conexant.txt >>> >>> >>> Under 2.4.n kernels install both the RIPTIDE and HCF or HSF drivers, >>> otherwise the modem will *not* work. >>> http://www.linuxant.com/drivers/riptide/index.php explains why >>> this modem which REQUIRES the additional installation of a Riptide >>> driver. >>> Under 2.6.n kernels, the hsfmodem package may provide modem support. >>> But there will be no audio functions. See >>> >>> http://www.linuxant.com/drivers/riptide/index.php?PHPSESSID=19b31933499f87b5b150db2315f714bd >>> >>> >>> For all code packages from Linuxant.com, either a driver set matching >>> the boot kernel will be installed, >>> or the drivers will first be compiled and then installed. The expert >>> on modem software for Linux is >>> "Support (Jonathan)"<modem.support@xxxxxxxxxxxx> >>> >>> ÂFrom Âhttp://www.linuxant.com/drivers//downloads-ubuntu-x86.php >>> Âdownload -7.80.02.06full_k2.6.24_28_generic_ubuntu_i386.deb.zip >>> ÂUnder Linux unpack with: >>> Â$ unzip *.zip >>> ÂThen install with: >>> Â$ sudo dpkg -i *.deb >>> ÂSubsequently, the modem should be found with >>> Â$ sudo wvdialconf /etc/wvdial.conf >>> ÂEdit in your personal information with: >>> Â$ sudo gedit /etc/wvdial.conf >>> Âand try dialing out with: >>> Â$ sudo wvdial. >>> ÂSee DOCs/Testing.txt Âfor details. >>> >>> >>> *** I just hope that this part does not apply: >>> >>>   Primary device ID: Â127a:4321 >>> ÂSupport type needed or chipset:  ÂHCF.Riptide >>> ÂUnder Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read >>> DOCs/InfoGeneral.txt about alternatives. >>> >>> Regards, >>> >>> Antonio >>> >>> On Thu, Oct 28, 2010 at 8:16 PM, Sacman Agency Staff >>> <staff.asacman@xxxxxxxxxxxxxxxxx> Âwrote: >>>> >>>> ÂThe modem data file shows that the Conexant HCF Riptide modem is >>>> installed. >>>> ÂAttempts to download/install the driver from LinuxAnt did not work. ÂA >>>> binary for kernel 2.6.24-28 was not found. ÂThe run install files did >>>> not >>>> install the driver. ÂCould you please help getting my Conexant HCF >>>> Riptide >>>> driver to install so I could use it as a Fax? ÂI am not too familiar >>>> with >>>> compiling source, but am willing to learn to get this fax modem >>>> functioning. >>>> >>>> Thanks in advance, >>>> >>>> John >>>> >>>> -------------------------- ÂSystem information >>>> ---------------------------- >>>> CPU=i686, ÂUbuntu , ÂALSA_version=1.0.16 >>>> Linux version 2.6.24-28-generic (buildd@vernadsky) (gcc version 4.2.4 >>>> (Ubuntu 4.2.4-1ubuntu3)) #1 SMP Wed Aug 25 15:25:41 UTC 2010 >>>> ÂscanModem update of: Â2010_05_29 >>>> >>>> Distrib_ID=Ubuntu >>>> DistribCodeName=hardy >>>> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >>>> >>>> >>>> Presently install your Linux Distributions dkms package. It provides for >>>> automated driver updates, >>>> following upgrade of your kernel. ÂFor details see >>>> http://linux.dell.com/projects.shtml#dkms >>>> >>>> ÂThere are no blacklisted modem drivers in /etc/modprobe* Âfiles >>>> >>>> ÂPotentially useful modem drivers now loaded are: >>>> >>>> >>>> If a USB modem or cellphone is attached and was not detected, please >>>> provide available information in your request to discuss@xxxxxxxxxxxxx >>>> >>>> Candidate PCI devices with modem chips are: >>>> 00:0b.1 Communication controller: Rockwell International Riptide HCF 56k >>>> PCI >>>> Modem >>>> High Definition Audio cards can host modem chips. >>>> >>>> For candidate card in slot 00:0b.1, firmware information and bootup >>>> diagnostics are: >>>> ÂPCI slot  ÂPCI ID    ÂSubsystemID  ÂName >>>> Â----------  Â---------  Â---------  Â-------------- >>>> Â00:0b.1  Â127a:4321  Â1235:4321  ÂCommunication controller: Rockwell >>>> International Riptide HCF 56k PCI Modem >>>> >>>> ÂModem interrupt assignment and sharing: >>>> Â9:     Â0  ÂXT-PIC-XT    Âacpi, RIPTIDE >>>> Â--- Bootup diagnostics for card in PCI slot 00:0b.1 ---- >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>> software. >>>> === >>>> >>>> Predictive Âdiagnostics for card in bus 00:0b.1: >>>>  ÂModem chipset Âdetected on >>>> NAME="Communication controller: Rockwell International Riptide HCF 56k >>>> PCI >>>> Modem" >>>> CLASS=0780 >>>> PCIDEV=127a:4321 >>>> SUBSYS=1235:4321 >>>> IRQ=9 >>>> IDENT=HCF.Riptide >>>> >>>> ÂFor candidate modem in: Â00:0b.1 >>>>  0780 Communication controller: Rockwell International Riptide HCF 56k >>>> PCI >>>> Modem >>>>   ÂPrimary device ID: Â127a:4321 >>>> ÂSupport type needed or chipset:  ÂHCF.Riptide >>>> ÂUnder Linux 2.6.n kernels, the chipset is NOT SUPPORTED . Read >>>> DOCs/InfoGeneral.txt about alternatives. >>>> >>>> >>>> For owners of a Dell PCs with Conexant HSF modems, a driver source >>>> package >>>> with full speed enabled is available, but requires driver compiling. >>>> Read >>>> DOCs/Conexant.txt >>>> >>>> >>>> Under 2.4.n kernels install both the RIPTIDE and HCF or HSF drivers, >>>> otherwise the modem will *not* work. >>>> http://www.linuxant.com/drivers/riptide/index.php explains why >>>> this modem which REQUIRES the additional installation of a Riptide >>>> driver. >>>> Under 2.6.n kernels, the hsfmodem package may provide modem support. >>>> But there will be no audio functions. See >>>> >>>> http://www.linuxant.com/drivers/riptide/index.php?PHPSESSID=19b31933499f87b5b150db2315f714bd >>>> >>>> >>>> For all code packages from Linuxant.com, either a driver set matching >>>> the >>>> boot kernel will be installed, >>>> or the drivers will first be compiled and then installed. The expert on >>>> modem software for Linux is >>>> "Support (Jonathan)"<modem.support@xxxxxxxxxxxx> >>>> >>>> ÂFrom Âhttp://www.linuxant.com/drivers//downloads-ubuntu-x86.php >>>> Âdownload -7.80.02.06full_k2.6.24_28_generic_ubuntu_i386.deb.zip >>>> ÂUnder Linux unpack with: >>>> Â$ unzip *.zip >>>> ÂThen install with: >>>> Â$ sudo dpkg -i *.deb >>>> ÂSubsequently, the modem should be found with >>>> Â$ sudo wvdialconf /etc/wvdial.conf >>>> ÂEdit in your personal information with: >>>> Â$ sudo gedit /etc/wvdial.conf >>>> Âand try dialing out with: >>>> Â$ sudo wvdial. >>>> ÂSee DOCs/Testing.txt Âfor details. >>>> >>>> ÂThe directions following below need only be pursued, if the above >>>> procedures are not adequate. >>>> 00:0b.1 >>>> ÂRead DOCs/Conexant.txt >>>> >>>> Writing DOCs/Conexant.txt >>>> >>>> >>>> ÂCompleted candidate modem analyses. >>>> >>>> ÂThe base of the UDEV device file system is: /dev/.udev >>>> >>>> ÂThe kernel was compiled with gcc version 4.2.4 and a compiler is not >>>> installed >>>> >>>> Âlinux-headers-2.6.24-28-generic resources needed for compiling are not >>>> manifestly ready! >>>> ÂThe code linking utility, ld, may be needed and is provided in the >>>> binutils >>>> package >>>> ÂThe patch utility is needed for compiling ALSA drivers, and possibly >>>> others. >>>> >>>> ÂIf compiling is necessary packages must be installed, providing: >>>>  Âgcc-4.2 make linux-headers-2.6.24-28-generic >>>> >>>> >>>> If a driver compilation fails, with message including some lack of some >>>> FileName.h (stdio.h for example), then >>>> Some additional kernel-header files need installation to /usr/include. >>>> The >>>> minimal additional packages are libc6-dev >>>> and any of its dependents, under Ubuntu linux-libc-dev >>>> >>>> If an alternate ethernet connection is available, >>>> $ Âapt-get update >>>> $ Âapt-get -s install linux-kernel-devel >>>> will install needed packages. >>>> For Debian/Ubuntu related distributions, run the following command to >>>> display the needed package list: >>>> >>>> Otherwise packages have to be found through http://packages.ubuntu.com >>>> Once downloaded and transferred into a Linux partition, >>>> they can be installed alltogether with: >>>> $ sudo dpkg -i *.deb >>>> >>>> >>>> Checking pppd properties: >>>>  Â-rwsr-xr-- 1 root dip 269256 2007-10-04 12:57 /usr/sbin/pppd >>>> >>>> In case of an "error 17" "serial loopback" problem, see: >>>>  Âhttp://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html >>>> >>>> To enable dialout without Root permission do: >>>>  Â$ su - root Â(not for Ubuntu) >>>>    Âsudo chmod a+x /usr/sbin/pppd >>>> or under Ubuntu related Linuxes >>>>  Âsudo chmod a+x /usr/sbin/pppd >>>> >>>> Checking settings of:  Â/etc/ppp/options >>>> asyncmap 0 >>>> noauth >>>> crtscts >>>> lock >>>> hide-password >>>> modem >>>> proxyarp >>>> lcp-echo-interval 30 >>>> lcp-echo-failure 4 >>>> noipx >>>> >>>> In case of a message like: >>>>  Warning: Could not modify /etc/ppp/pap-secrets: Permission denied >>>> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html >>>> >>>> For guidance on FAX usage, get from >>>> http://linmodems.technion.ac.il/packages/ Âget faxing.tar.gz >>>> It has samples for a modem using port /dev/ttySL0, which must be changed >>>> to >>>> match your modem's port. >>>> >>>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 >>>> Which can interfere with Browser naviagation. >>>> >>>> ÂDon't worry about the following, it is for experts should trouble >>>> shooting >>>> be necessary. >>>> ========================================================== >>>> >>>> ÂChecking for modem support lines: >>>> Â-------------------------------------- >>>>   /device/modem symbolic link: >>>> slmodemd created symbolic link /dev/ttySL0: >>>>   Within /etc/udev/ files: >>>> >>>>   Within /etc/modprobe.conf files: >>>> >>>>   Within any ancient /etc/devfs files: >>>> >>>>   Within ancient kernel 2.4.n /etc/module.conf files: >>>> >>>> --------- end modem support lines -------- >>>> >>>> >
