The time now is Fri 24 May 2013, 23:04
All times are UTC - 4 |
| Author |
Message |
md_jamil
Joined: 10 Sep 2006 Posts: 46 Location: Saudi Arabia
|
Posted: Wed 11 Oct 2006, 16:26 Post subject:
hsf modem driver |
|
I am using Gnome at the moment I think I tried gkdial as well didnt work.I will give it another try anyway, when you try to do pppsetup it says first run modem wizard, question, how to tell modem wizard that modem is ttySHSF0 it does not show in wizard. Gnome is readily available without pppsetup thats why I am always trying. Let my try gkdial
|
|
Back to top
|
|
 |
jcoder24

Joined: 06 May 2005 Posts: 601 Location: Barbados
|
Posted: Wed 11 Oct 2006, 18:17 Post subject:
|
|
For the HCF/HSF modems you don't have to run the "Modem Wizard". You shouldn't need to run pppsetup either (I'm not sure if it is still being used).
|
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 6866 Location: Perth, Western Australia
|
Posted: Wed 11 Oct 2006, 18:36 Post subject:
|
|
If you're using Gnome-ppp, don't. It makes the connection, but fails to
negotiate properly with the isp. Myself and many others had this problem.
A shame, as it looks good otherwise.
Gkdial is usually the best choice.
|
|
Back to top
|
|
 |
md_jamil
Joined: 10 Sep 2006 Posts: 46 Location: Saudi Arabia
|
Posted: Thu 12 Oct 2006, 06:33 Post subject:
hsf modem driver |
|
ok tried gkdial dials, starts pppd, negotiates ppp and stops after a few seconds exactly the way gnome did, when I look at /var/log/messages it has same errors as gnome (pap-secrets and chap-secrets file has world and/or group access) modem hangsup line (sighup). Well it turns out one must put some lines in those files to resolve this, at the moments they have just one line which says ( username*password ), any suggestions?
|
|
Back to top
|
|
 |
md_jamil
Joined: 10 Sep 2006 Posts: 46 Location: Saudi Arabia
|
Posted: Thu 12 Oct 2006, 06:35 Post subject:
hsf modem driver |
|
ok tried gkdial dials, starts pppd, negotiates ppp and stops after a few seconds exactly the way gnome did, when I look at /var/log/messages it has same errors as gnome (pap-secrets and chap-secrets file has world and/or group access) modem hangsup line (sighup). Well it turns out one must put some lines in those files to resolve this, at the moments they have just one line which says ( username*password ), any suggestions?
|
|
Back to top
|
|
 |
md_jamil
Joined: 10 Sep 2006 Posts: 46 Location: Saudi Arabia
|
Posted: Mon 16 Oct 2006, 16:38 Post subject:
hsf modem driver |
|
I downloaded generic type modem drive because puppy core type is not listed on linuxant.com, is that right or I have to try another one. it could be that modem driver is crashing? it connecets fine though but does not fetch any server or client adresses. One more thing,( about PAP and CHAP secrets) its warning not an error, these files may be fine may be its the wrong modem driver, what core type you guys have selected when downloading modem driver?
|
|
Back to top
|
|
 |
EdFromHouston
Joined: 07 Apr 2006 Posts: 176
|
Posted: Tue 28 Nov 2006, 23:32 Post subject:
Still Must Run hsfconfig, cnxtcfg After Reboot |
|
Hi, I have Puppy 1.09CE installed to hda5 with hda6 being used as a 900mb swap partition.
Hda5 and 6 are located on hda2 and hda 1 is Windows ME. I use GRUB v1.5 installed
to MBR to boot.
I have the Rockwell HSF/Data/Fax/Voice/Speakerphone modem 127A / 2015
This modem works but I must run "hsfconfig" and "cnxtcfg" after every reboot to
reinstall the driver.
I am using Jcoder24s' "hsfmodem1105.pup".
I think I added "hsfconfig --serial" correctly to /etc/rc.d/rc.local below.
I think I also added to /etc/rc.d/rc.local Jcoder24s' script listed here:
http://www.murga-linux.com/puppy/viewtopic.php?t=2258&postdays=0&postorder=asc&start=16&sid=4d0adca27132c7df450523a62a366028
-----------------------------Beginning of rc.local in blue-------------
Is the paragraph spacing a worry in writing script and if so is it right?
#this file called from rc.local0
#you can edit this file
#When firewall is installed, will append lines to this file
if [ -x /etc/rc.d/rc.firewall ]; then
/etc/rc.d/rc.firewall start (Is this space before /etc... right?)
fi (Is this right? What is fi?)
HSF="1"
modem="hsf"
mdev="HSF"
hsfconfig --serial
# Due to segmentation errors when inserting hcfpciserial we (Should this be hsfpciserial?}
# have to temporarily move the current.cty file until after
# the modules are inserted
if [ -f /etc/$modem/current.cty ]; then
mv /etc/$modem/current.cty /etc/$modem/current.cty.o
fi
#-----------------------------------------------------------
# Load modules for detected modem
#-----------------------------------------------------------
echo >> /etc/modules.conf
echo alias /dev/ttyS"$mdev"* "$modem"serial >> /etc/modules.conf
echo alias char-major-241 "$modem"serial >> /etc/modules.conf
echo alias /dev/ttyCUA* "$modem"serial >> /etc/modules.conf
echo alias char-major-242 "$modem"serial >> /etc/modules.conf
echo alias /dev/modem "$modem"serial >> /etc/modules.conf
#echo options "$modem"serial serialmajor=240 calloutmajor=241 >> /etc/modules.conf
if [ `lsmod | grep -ic $modem` -eq 0 ] #check if modules loaded already
then
insmod "$modem"osspec
if [ "$HSF" -gt 0 ] ; then insmod hsfbasic2 ; fi
insmod "$modem"engine
insmod "$modem"serial
fi
if [ -f /etc/$modem/current.cty.o ]; then
mv /etc/$modem/current.cty.o /etc/$modem/current.cty
fi
#-----------------------------------------------------------
# Setup required devices
#-----------------------------------------------------------
rm -f /dev/modem /dev/cua"$mdev"0 /dev/ttyS"$mdev"0 2>/dev/null
"$modem"config -serial
dialog --no-shadow --msgbox "$mdev modem successfully installed." 6 37
#Load modem drivers on boot. This adds 10 or more seconds to the boot time.
rm -f /dev/modem /dev/cuaHSF0 s>/dev/null
hsfconfig --serial (This paragraph appears over and
over again after each reboot and the running of "hsfconfig" and then
"cnxtcfg' in order to reinstall the modem driver so it will connect after rebooting.)
--------------------------------End of rc.local------------------------------------------
I don't know a thing about linux. All I've learned I've learned here. My system is getting
better as time goes by but this is stumping me, no big deal really as the driver does work.
Does the above file look right? I'm new at this so I'd like to know if it is right before I go deeper.
I'm also thinking the firewall or GRUB may be causing problems but I'm just guessing.
Thanks for your time. I only have a few hours ISP time till the end of the month so please excuse
me if I can't respond sooner.
Ed
|
|
Back to top
|
|
 |
muggins
Joined: 20 Jan 2006 Posts: 6660 Location: lisbon
|
Posted: Wed 29 Nov 2006, 01:02 Post subject:
|
|
hi ed,
my sister has a hsf winmodem and i followed jcoder's advice & did the hsfconfig --serial thing in rc.local, and it worked fine. then, perhaps following an upgrade, it stopped working for her for some unknown reason, so instead i modified the script for defaultconnect, in /usr/local/bin, to run hsfconfig --serial before gkdial.
at least i think that's what i did? she's at work at the moment, but i'll email her later & ask.
if you just do hsfconfig --serial in a console window does that activate your modem? (there is a bit of a delay i recall)
|
|
Back to top
|
|
 |
EdFromHouston
Joined: 07 Apr 2006 Posts: 176
|
Posted: Wed 29 Nov 2006, 01:54 Post subject:
|
|
Hi muggins,
When I run "hsfconfig --serial" the modem works.
My modem did originally connect after rebooting come to think of it but after only two or three reboots and not changing anything like adding software it quit working after rebooting so I think I'm having the same problem your sister is having.
(Edit: This occurred after first installing hsfmodem-1105.pup. I didn't change rc.local until after it quit working after rebooting.)
I noticed this at startup just now after running hsfconfig --serial:
Module hsf2 loaded with warnings.
Using lib/modules/2.4.29/hsfmodem/hsfengine/o.gz.
At this point Puppy stalled for about 15 seconds looking for it.
I also noticed this at startup and shutdown:
/etc/rc.d/rc.local not found 55
/etc/rc.d/rc.local not found 56
/etc/rc.d/rc.local not found 64
/etc/rc.d/rc.local not found 68
I have no idea what all this means but it did seem relevant.
I'm smoking my ISP this month so I wont be able to stay much longer. Maybe your sister can help.
Thanks again.
Edit: How did you modify the other file?
Last edited by EdFromHouston on Wed 29 Nov 2006, 13:51; edited 1 time in total
|
|
Back to top
|
|
 |
muggins
Joined: 20 Jan 2006 Posts: 6660 Location: lisbon
|
Posted: Wed 29 Nov 2006, 06:37 Post subject:
|
|
where you've got those errors, rclocal not found ,is that a typo? as the file should be called rc.local
i'll have a look at my sister's computer tomorrow & see where i put that "hsfconfig --serial" command. why it doesn't work in rc.local i can't understand.
|
|
Back to top
|
|
 |
EdFromHouston
Joined: 07 Apr 2006 Posts: 176
|
Posted: Wed 29 Nov 2006, 13:58 Post subject:
|
|
| muggins wrote: | where you've got those errors, rclocal not found ,is that a typo? as the file should be called rc.local
i'll have a look at my sister's computer tomorrow & see where i put that "hsfconfig --serial" command. why it doesn't work in rc.local i can't understand. |
Five typos: Sorry about that.
|
|
Back to top
|
|
 |
muggins
Joined: 20 Jan 2006 Posts: 6660 Location: lisbon
|
Posted: Thu 30 Nov 2006, 01:41 Post subject:
|
|
ed,
OK, i'm on the net using my sister's hsf winmodem. in her /etc/rc.d/rc.local file it has this, pertaining to the modem, via jcoder:
| Code: |
#Load modem drivers on boot. This adds 10 or more seconds to the boot time.
rm -f /dev/modem /dev/cuaHSF0 /dev/ttySHSF0 2>/dev/null
hsfconfig --serial |
as i mentioned previously, this used to work fine, but for some reason doesn't load the modem any more. Instead i put the code in /root/.xinitrc , towards the end of the file, like this:
| Code: |
exec hsfconfig -s &
exec $CURRENTWM
###END###
|
and this now works. (N.B. there is a 10 second delay after the window comes up before the modem is active) .the important thing to remember is to place the "hsfconfig -s &" command before
exec $CURRENTWM
|
|
Back to top
|
|
 |
EdFromHouston
Joined: 07 Apr 2006 Posts: 176
|
Posted: Thu 30 Nov 2006, 16:35 Post subject:
|
|
| muggins wrote: | ed,
OK, i'm on the net using my sister's hsf winmodem. in her /etc/rc.d/rc.local file it has this, pertaining to the modem, via jcoder:
| Code: |
#Load modem drivers on boot. This adds 10 or more seconds to the boot time.
rm -f /dev/modem /dev/cuaHSF0 /dev/ttySHSF0 2>/dev/null
hsfconfig --serial |
as i mentioned previously, this used to work fine, but for some reason doesn't load the modem any more. Instead i put the code in /root/.xinitrc , towards the end of the file, like this:
| Code: |
exec hsfconfig -s &
exec $CURRENTWM
###END###
|
and this now works. (N.B. there is a 10 second delay after the window comes up before the modem is active) .the important thing to remember is to place the "hsfconfig -s &" command before
exec $CURRENTWM |
OK, this is what I did.
I left everything in rc.local.
I opened /root/.xinitrc as text and added the first code followed by a space then the second you have written above.
I rebooted Puppy.
I ran hsfconfig --serial in the console.
I rebooted.
It is working fine now and connecting at 45.2 which is the same as my other Windows XP system.
I still have funny things showing up at startup and shutdown like rc.local not found and then numbers like I talked about before but everything works now so I'm not going to worry about those things.
I'm sure there are at least several hundred other people with the problem your sister and I were having, the problem you solved at least for us.
You should let Jcoder24 know about how you solved this.
Ed
|
|
Back to top
|
|
 |
muggins
Joined: 20 Jan 2006 Posts: 6660 Location: lisbon
|
Posted: Thu 30 Nov 2006, 19:31 Post subject:
|
|
ed,
at least it works for the moment. maybe try removing the "hsfconfig" stuff from rc.local, or comment the relevant lines out, (which you do by inserting an # at the beginning of the line), and see if you're still getting those rc.local not found messages.
because you shouldn't be getting any, AFAIK. to me it's a mystery why you're receiving these messages at bootup, & also why hsfconfig doesn't work in rc.local.
|
|
Back to top
|
|
 |
EdFromHouston
Joined: 07 Apr 2006 Posts: 176
|
Posted: Fri 01 Dec 2006, 16:01 Post subject:
|
|
| muggins wrote: | ed,
at least it works for the moment. maybe try removing the "hsfconfig" stuff from rc.local, or comment the relevant lines out, (which you do by inserting an # at the beginning of the line), and see if you're still getting those rc.local not found messages.
because you shouldn't be getting any, AFAIK. to me it's a mystery why you're receiving these messages at bootup, & also why hsfconfig doesn't work in rc.local. |
OK I took everything out of rc.local except:
HSF="1"
modem="hsf"
mdev="HSF"
hsfconfig --serial
if [ -f /etc/$modem/current.cty ]; then
mv /etc/$modem.current.cty /etc/$modem/current.cty.o
(And the firewall stuff.)
Everything works. It also boots faster by about 5 seconds.
I used GRUB on MBR to boot between Windows and Puppy back and forth several times. I cold started it several times.
Ed
New Edit: I did notice on startup and shutdown it said "rc.local not found 14: hsfconfig not found". I did have 4 lines saying there were problems with rc.local and now there is just the one. I may put that in another thread but I doubt it, it works good now. I wanted to let you know. Thanks again.
Last edited by EdFromHouston on Sat 02 Dec 2006, 02:18; edited 1 time in total
|
|
Back to top
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|