Thanks for deleting that Flash. It was so late when I made that post that it didn't occure to me that I could delete it.Johnny Reb wrote:Deleted by Flash. (Duplicate of previous post.)
Incidentally, the originator of a post can edit it at any time.
HSF/HCF softmodem dotpups available for testing
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
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/.
cd /
tar xvfz $PATH-TO-FILE/hcf-extra.tar.gz
you should now have
/bin/hcfpciconfig
/bin/hcfpcistop
/etc/hcfpci/config
/etc/hcfpci/current.cty
/etc/hcfpci/current.inf
/etc/hcfpci/inf/hcfv90_lan_linux.inf
/etc/hcfpci/inf/hcfv90_linux.inf
/etc/hcfpci/inf/hcfv92_linux.inf
/etc/hcfpci/inf/hcfv92_riptide_linux.inf
/etc/hcfpci/inf/hcf_linux.cty
~~~~
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
you should now have
/bin/hcfpciconfig
/bin/hcfpcistop
/etc/hcfpci/config
/etc/hcfpci/current.cty
/etc/hcfpci/current.inf
/etc/hcfpci/inf/hcfv90_lan_linux.inf
/etc/hcfpci/inf/hcfv90_linux.inf
/etc/hcfpci/inf/hcfv92_linux.inf
/etc/hcfpci/inf/hcfv92_riptide_linux.inf
/etc/hcfpci/inf/hcf_linux.cty
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
jcoder,jcoder24 wrote: 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
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.
bash-3.00# tar xvfz /lib/modules/2.4.29/hsfmodem/hcf-extra.tar.gz
tar (child): /lib/modules/2.4.29/hsfmodem/hcf-extra.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error exit delayed from previous errors
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
*** modified ***
Uploaded a new HCF dotpup package. This is the only file you'll need.
Please download from Page 1. http://www.murga.org/~puppy/viewtopic.php?t=1625
Note you will have to run the run the "HSF/HCF modem setup" from the setup menu each time you restart puppy.
Uploaded a new HCF dotpup package. This is the only file you'll need.
Please download from Page 1. http://www.murga.org/~puppy/viewtopic.php?t=1625
Note you will have to run the run the "HSF/HCF modem setup" from the setup menu each time you restart puppy.
Last edited by jcoder24 on Sun 28 Aug 2005, 12:38, edited 5 times in total.
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
jcoder, I hate to have to tell you this, but you put the hsf modem files in this dotpup instead of the hcf modem files, either that or you uploaded the wrong dotpup.jcoder24 wrote:Uploaded a new HCF dotpup package. This is the only file you'll need.
Download link -- http://www.murga.org/~puppy/download.php?id=457
Note you will have to run the run the "HSF/HCF modem setup" from the setup menu each time you restart puppy.
I can't speak for anyone else, but I really appriciate the effort you are putting into this.
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
Download the file hcfmodem.pup package from Page 1. That is the correct file.
http://www.murga.org/~puppy/viewtopic.php?t=1625
Page 1 also contains instructions for installing and using the driver.
http://www.murga.org/~puppy/viewtopic.php?t=1625
Page 1 also contains instructions for installing and using the driver.
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
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).jcoder24 wrote:Download the file hcfmodem.pup package from Page 1. That is the correct file.[/b]
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
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:
See pppd(8) for more options.
# pppd modem
~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~
# pppd crtscts modem
~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~
# pppd crtscts mru n modem
Segmentation fault
# pppd mru n
Segmentation fault
#
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.
See pppd(8) for more options.
# pppd modem
~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~~ÿ}#À!}!}!} }4}"}&} } } } }%}&ºK&}'}"}(}"S~
# pppd crtscts modem
~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~~ÿ}#À!}!}!} }4}"}&} } } } }%}&Z}(A(}'}"}(}"Òë~
# pppd crtscts mru n modem
Segmentation fault
# pppd mru n
Segmentation fault
#
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
~ 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.
Files to be created/edited
1. /etc/resolv.conf
contains the addresses of your nameservers
2. /etc/ppp/pap-secrets or /etc/ppp/chap-secrets
contains username and password information for authentication
3. /etc/ppp/options
"Provides both login information and also certain hardware information about your modem"
4. /usr/sbin/ppp-on, /usr/sbin/ppp-on-dialer and /usr/sbin/ppp-off
scripts to start and stop the connection
1. Edit /etc/resolv.conf and add your isp name servers to the bottom of the file like below
nameserver 1.2.3.4
nameserver 1.2.3.5
2. Typically you only need one of the following files depending on which authentication your isp uses. If you're unsure you can create both of them.
example /etc/ppp/pap-secrets
# Secrets for authentication using PAP
# client server secret acceptable local IP addresses
username * password
example /etc/ppp/chap-secrets
# Secrets for authentication using CHAP
# client server secret acceptable local IP addresses
username * password
* username password
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.
TELEPHONE=555-1212 # The telephone number for the connection
LOCAL_IP=0.0.0.0 # Local IP address if known. Dynamic = 0.0.0.0
REMOTE_IP=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0
export TELEPHONE
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
#--- Initiate the connection
exec /usr/sbin/pppd debug /dev/modem 38400 \
$LOCAL_IP:$REMOTE_IP \
connect $DIALER_SCRIPT
example ppp-on-dialer script (This script was taken from PPP HOWTO and has not been personally tested)
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
exec /usr/sbin/chat -v \
TIMEOUT 3 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
'OK-+++\c-OK' ATH0 \
TIMEOUT 30 \
OK ATDT$TELEPHONE \
CONNECT '' \
example ppp-off script (This script was taken from PPP HOWTO and has not been personally tested)
#!/bin/sh
######################################################################
#
# Determine the device to be terminated.
#
if [ "$1" = "" ]; then
DEVICE=ppp0
else
DEVICE=$1
fi
######################################################################
#
# 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 1
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.
Files to be created/edited
1. /etc/resolv.conf
contains the addresses of your nameservers
2. /etc/ppp/pap-secrets or /etc/ppp/chap-secrets
contains username and password information for authentication
3. /etc/ppp/options
"Provides both login information and also certain hardware information about your modem"
4. /usr/sbin/ppp-on, /usr/sbin/ppp-on-dialer and /usr/sbin/ppp-off
scripts to start and stop the connection
1. Edit /etc/resolv.conf and add your isp name servers to the bottom of the file like below
nameserver 1.2.3.4
nameserver 1.2.3.5
2. Typically you only need one of the following files depending on which authentication your isp uses. If you're unsure you can create both of them.
example /etc/ppp/pap-secrets
# Secrets for authentication using PAP
# client server secret acceptable local IP addresses
username * password
example /etc/ppp/chap-secrets
# Secrets for authentication using CHAP
# client server secret acceptable local IP addresses
username * password
* username password
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.
TELEPHONE=555-1212 # The telephone number for the connection
LOCAL_IP=0.0.0.0 # Local IP address if known. Dynamic = 0.0.0.0
REMOTE_IP=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0
export TELEPHONE
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
#--- Initiate the connection
exec /usr/sbin/pppd debug /dev/modem 38400 \
$LOCAL_IP:$REMOTE_IP \
connect $DIALER_SCRIPT
example ppp-on-dialer script (This script was taken from PPP HOWTO and has not been personally tested)
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
exec /usr/sbin/chat -v \
TIMEOUT 3 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
'OK-+++\c-OK' ATH0 \
TIMEOUT 30 \
OK ATDT$TELEPHONE \
CONNECT '' \
example ppp-off script (This script was taken from PPP HOWTO and has not been personally tested)
#!/bin/sh
######################################################################
#
# Determine the device to be terminated.
#
if [ "$1" = "" ]; then
DEVICE=ppp0
else
DEVICE=$1
fi
######################################################################
#
# 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 1
Last edited by jcoder24 on Sun 23 Oct 2005, 17:51, edited 1 time in total.
-
Guest
Problem with Conexant HCF modem
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?
1) /etc/hcfpci/inf/hcfv90_lan_linux.inf
2) /etc/hcfpci/inf/hcfv90_linux.inf
3) /etc/hcfpci/inf/hcfv92_linux.inf
4) /etc/hcfpci/inf/hcfv92_riptide_linux.inf
5) None of the above
Which INF file would you like to use with your HCF modem? (1-5) 2
I choose number 2 ( My modem was bought in 2000 and I think it is not V92)
Finally the scrip says the modem is correctly instaled.
But when I try to open the Dialer It say that my modem is not present.
My question is : Did I do all things well? What I missed?
Thanks in advance...
Regards from Argentina
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?
1) /etc/hcfpci/inf/hcfv90_lan_linux.inf
2) /etc/hcfpci/inf/hcfv90_linux.inf
3) /etc/hcfpci/inf/hcfv92_linux.inf
4) /etc/hcfpci/inf/hcfv92_riptide_linux.inf
5) None of the above
Which INF file would you like to use with your HCF modem? (1-5) 2
I choose number 2 ( My modem was bought in 2000 and I think it is not V92)
Finally the scrip says the modem is correctly instaled.
But when I try to open the Dialer It say that my modem is not present.
My question is : Did I do all things well? What I missed?
Thanks in advance...
Regards from Argentina
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
Re: Problem with Conexant HCF modem
Heh, well at least I ain't the only one! I hope you have better luck getting it to work than I have.Anonymous wrote:I`m a linux newbie and the happy owner of Conexant HCF 56K Data/Fax/Voice/Spkp modem.
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
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.jcoder24 wrote: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.
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.
Last edited by Johnny Reb on Thu 01 Sep 2005, 05:42, edited 1 time in total.
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
Re: Problem with Conexant HCF modem
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.Anonymous wrote: My question is : Did I do all things well? What I missed?
Thanks in advance...
Regards from Argentina
Note that you will have to restart puppy to try each new inf.
I've gotten hold of an hcf modem. So far I'm not having much luck -- in fact Johnny Reb has had better luck than me. I'm going to try recompiling the drivers with the modem installed in VL. I'll then test it in VL and compare the results.
Stay tuned....
BTW. I've noticed quite a number of downloads for the hsfmodem but I've only had three responses to the poll. It would be nice to know if the drivers are working of if they need more work. So if you download please provide feedback.
Stay tuned....
BTW. I've noticed quite a number of downloads for the hsfmodem but I've only had three responses to the poll. It would be nice to know if the drivers are working of if they need more work. So if you download please provide feedback.
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
Yes it appears that is the problem. I've since downloaded and older version of gcc, which it refuses to install, and the same version that I've got and tried to reinstall it. When I try to reinstall I get a slew of error messages warning of missing dependicies.............libpng.so.3, libtcl8.3.so, /usr/local/bin/perljcoder24 wrote:I'm no where near a 'compilation' pro but from your post it seems like a problem with gcc. Maybe it's broken. You could prob try an older version of GCC.
/bin/csh libc.so.6(GLIBC_2.3) is needed by tcl-8.3.5-96.0.1 libntdll.dll.so
are just a few of them. I've been trying to locate where you can download these files, and it's like looking for a needle in a haystack. If I don't find them before long I think I'm just going to wipe out that partition and reinstall from scratch.
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
-
Johnny Reb
- Posts: 132
- Joined: Fri 05 Aug 2005, 08:02
- Location: The Confederate States of America (occupied)
- Contact:
jcoder, here's something that may be useful. Since I had trouble with Ice crashing I renamed my pup101 to pup101.zip and started over with a new pup101 in order to try and find out what was going on there, but I found out something that may have a bearing on the modem drivers. When I created the new pup101 I installed IceWM before I installed the dodpup for the modem drivers. With Ice installed the HCF/HSF wizard does not appear in the menu, so I attempted to configure the modem via the terminal, and got these results, which you do not get if you use the wizard:jcoder24 wrote:I've gotten hold of an hcf modem. So far I'm not having much luck -- in fact Johnny Reb has had better luck than me. I'm going to try recompiling the drivers with the modem installed in VL. I'll then test it in VL and compare the results.
This package does not contain pre-built modules suitable for your system:
Distribution: unknown-unknown
Kernel arch: i686
Kernel version: linux-2.4.29
Please obtain the appropriate variant of this package for your system
or try the generic RPM or tar version.
#
So, it would appear that the drivers you have may be the problem. If it will be any assistance to you, I do have some of the beta drivers in the source packages, both rpm's and tar.gz. Just let me know, and I can email them. I downloaded quiet a few different versions of them when I first installed Peanut trying to get the modem to work with it, but everytime I'd try to install them I kept getting a message that I needed to recompile the kernel, and then the floppy went out on me. Foutunatly I rarely delete something like that, and still have the drivers on my computer.
He who dares not offend cannot be honest.
~ Thomas Paine
~ Thomas Paine
-
Guest
The emphasis in that message is on pre-built modules which means that you have to recompile the modules from source for your particular distro. (Previously there were only binary versions of the modules for Redhat and I think Debian.)Johnny Reb wrote:
This package does not contain pre-built modules suitable for your system:
Distribution: unknown-unknown
Kernel arch: i686
Kernel version: linux-2.4.29
The modules I've provided were compiled under Vector Linux 5.1 (as recommended) running in VMWare. The problem I'm having is that when I try to insert the modules without the /etc/hcfpci/current.inf I get a number of warnings but all modules load 'successfully' yet the modem fails to work. When I try it with /etc/hcfpci/current.inf in place I get a segmentation fault when inserting the hcfpciserial module.
This could be indicating a 'bad' inf file. My plan it to transfer an image of my VMWare Vector Linux install to a 'real' partition so I can test the modem from Vector.
BTW. Your modem actually appears to have been installed 'completely'. How did you answer the questions about inf, vendor id, pci id, country....?