Unfortunately my monitor has also suffered a melt down and my power supply decided to follow it so I can't produce the new .pup which hopefully should make things easier for people trying to install the hcf modem.

~~~~

After you install the .pup, change to the root directory and extract the files. hcfpciconfig would be on the PATH and should be found when you try to run it. Also hcfpciconfig would be able to find the config files in /etc/hcfpci/.

After you install the .pup, change to the root directory and extract the files. hcfpciconfig would be on the PATH and should be found when you try to run it. Also hcfpciconfig would be able to find the config files in /etc/hcfpci/.

cd /
tar xvfz $PATH-TO-FILE/hcf-extra.tar.gz

jcoder,

I've not had any luck yet, but I've got an idea what the problem *might* be. When I run the .pup it places the files in the /lib/modules/2.4.29/hsfmodem directory and not the /lib/modules/2.4.29/hcfmodem directory. I copied the output from my last attempt at installing, and will paste it in below so maybe that will be of some assistance in diagnosing what is going on.

Download the file hcfmodem.pup package from Page 1. That is the correct file.[/b]

Thanks jcoder, I got it downloaded, and will be trying it out tomorrow for sure (tonight if I have time). I'll let you know ASAP if it works (ASAP may be a few days if this hurricane takes down the power, even though I'm located a long way inland they are still predicting high winds, and power outages)._________________He who dares not offend cannot be honest.
~ Thomas Paine

jcoder, I got the modem installed! However, I've not got it to actually work yet. None of the dialer programs will work with it. WvDial does recognize that it's there, but returns with an error message which unfortunatly I will be unable to read until my new monitor arrives (working with a monitor that does not dispaly red at all really sucks). After trying the dialer programs, I tried the terminal, and got some results, which may give someone with more knowlege an idea about what's going on. The results are:

Note: the modem never made any sound at all, but as you can see there was some communication with it.

I hope that will be enough for you to diagnose what the problem is, and if it's not please let me know any additional info that you need. Thanks._________________He who dares not offend cannot be honest.
~ Thomas Paine

Glad to see you made it thru the hurricane! I hope you weren't too negatively affected.

According to the pppd howto http://www.tldp.org/HOWTO/PPP-HOWTO/x314.html you can try wvdial from the console
as follows:

run wvdialconf /etc/wvdial.conf
edit /etc/wvdial.conf
uncomment (delete the semicolon at the beginning of the line) the phone, username and password lines and enter your ISP dialup number, your username and your password respectively.
note the time and then run wvdial

this should allow you to see what errors are showing up.

if it still fails to dial your isp check the lines of /var/log/messages for anything after the time you start wvdial and attach it to your next post. There may also be a /etc/ppp/connect-errors, you can attach that as well.

~~~~~~~~

As for using pppd from the command line, that is a bit more involved.

The mru n you specified for the last two commands is incorrect. n is a number between 128 and 1500.
You can omit the mru option.

The crtscts option turns on hardware handshaking. Since the modem is a winmodem I'm not sure how this affects connecting.

In order to use pppd from the console you need to have a couple of other files setup. Below is my summary of the manual configuration adapted from the PPP HOWTO and my four-years-old memories of pppd on unix.

3. Puppy has an /etc/ppp/options file already. If the connection fails with this default file refer to http://www.tldp.org/HOWTO/PPP-HOWTO/options.html#AEN964

4. The following three scripts should be made executable after creating/editing them by issuing the chmod +x command:

example ppp-on script (This script has been adapted from the PPP HOWTO and has not been tested.)

#!/bin/sh
#
#
# Script to initiate a PPP connection. This is the first part of the
# pair of scripts. This is not a secure pair of scripts as the codes
# are visible with the 'ps' command. However, it is simple.
#
# These are the parameters. Change as needed.

######################################################################
#
# If the ppp0 pid file is present then the program is running. Stop it.
if [ -r /var/run/$DEVICE.pid ]; then
kill -INT `cat /var/run/$DEVICE.pid`
#
# If the kill did not work then there is no process running for this
# pid. It may also mean that the lock file will be left. You may wish
# to delete the lock file at the same time.
if [ ! "$?" = "0" ]; then
rm -f /var/run/$DEVICE.pid
echo "ERROR: Removed stale pid file"
exit 1
fi
#
# Success. Let pppd clean up its own junk.
echo "PPP link to $DEVICE terminated."
exit 0
fi
#
# The ppp process is not running for ppp0
echo "ERROR: PPP link is not active on $DEVICE"
exit 1Last edited by jcoder24 on Sun 23 Oct 2005, 13:51; edited 1 time in total

I`m a linux newbie and the happy owner of Conexant HCF 56K Data/Fax/Voice/Spkp modem.
I installed hcfmodem.pup (the one that was posted on 2005/08/26), then rebooted the system and run cnxtcg in Rxvt .
After that the scrip does not recognize my modem any way I followed all the steps..
In This step What should I do?

Glad to see you made it thru the hurricane! I hope you weren't too negatively affected.

According to the pppd howto http://www.tldp.org/HOWTO/PPP-HOWTO/x314.html you can try wvdial from the console
as follows:

run wvdialconf /etc/wvdial.conf
edit /etc/wvdial.conf
uncomment (delete the semicolon at the beginning of the line) the phone, username and password lines and enter your ISP dialup number, your username and your password respectively.
note the time and then run wvdial

this should allow you to see what errors are showing up.

if it still fails to dial your isp check the lines of /var/log/messages for anything after the time you start wvdial and attach it to your next post. There may also be a /etc/ppp/connect-errors, you can attach that as well.

~~~~~~~~

As for using pppd from the command line, that is a bit more involved.

The mru n you specified for the last two commands is incorrect. n is a number between 128 and 1500.
You can omit the mru option.

The crtscts option turns on hardware handshaking. Since the modem is a winmodem I'm not sure how this affects connecting.

In order to use pppd from the console you need to have a couple of other files setup. Below is my summary of the manual configuration adapted from the PPP HOWTO and my four-years-old memories of pppd unix.

Thanks, I wasn't too worried about the hurricane, except for the power going out because I'm up near the Tennessee border. Fortunatly we never lost power at all, which came as a real suprise because the power usualy goes out here whenever a bad cloud comes up...rain or not. The only real negitive effects felt were felt by my tomato plants, which didn't fare too well, but even they made it through it better than I thought they would given the high winds we got.

I'll try the wvdial through the console & pppd suggestions you made and see what happens. It may be a day or two before I get any results for you because I'm working on getting an old install of Peanut Linux to working, as well as Puppy. I had Peanut installed, and was booting via floppy. I don't think I had it up for a full month before the floppy controller on my motherbord died, and it's just been sitting there for I guess a year. Puppy inspired me to download the .iso (when I first installed it I just downloaded the zip file) so that I could boot off the cd. I've now got it booting, but have run into problems with it too. The primary problem is that in order to get some things working on it I'm going to have to recompile the kernel. I've read several howtos on it and was ready to give it a try the other night, and when I entered make menuconfig into the terminal I got the error message unknown command make or something to that effect. There is a gcc compiler installed, but for some reason it's not working. I've since downloaded the compiler from the Peanut 9.5 archives, and installed it again, and tried to install another program that would require compiling, and got this: ~/install-programs/torsmo-0.18# ./configure
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... no
checking for working aclocal-1.4... missing
checking for working autoconf... missing
checking for working automake-1.4... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... gcc
checking whether the C compiler (gcc -Os -mcpu=i386 -fno-strength-reduce ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
CSA3:~/install-programs/torsmo-0.18#

I know that's kind of off topic, but if you have any suggestions I'd sure appriciate them._________________He who dares not offend cannot be honest.
~ Thomas PaineLast edited by Johnny Reb on Thu 01 Sep 2005, 01:42; edited 1 time in total

jcoder, I forgot to mention in my previous post that what I was trying with pppd was just a shot in the dark. I've never attempted to connect through the command line before, and was just entering commands I got after trying pppd --help._________________He who dares not offend cannot be honest.
~ Thomas Paine

Looks like you did everything right. These are beta drivers and may not work for everyone. I would suggest selecting an inf in the order of 2,3,1,4. If all of these fails then you post the contents of /var/log/messages that relates to configuring the modem and setting up the dialer.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum