Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 25 Oct 2014, 15:21
All times are UTC - 4
 Forum index » House Training » HOWTO ( Solutions )
Howto compile HSF/HCF drivers for Puppy2
Moderators: Flash, Ian, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 2 of 2 Posts_count   Goto page: Previous 1, 2
Author Message
telemetric_au

Joined: 28 Feb 2007
Posts: 54

PostPosted: Wed 28 Feb 2007, 09:18    Post_subject: looking for file, plz help  

as listed above, the dotpups.de site is down, plz someone share...

linux-2.6.18.1-scripts.tar.bz2


http://dotpups.de/dotpups/Wifi/compiling-kernel-scripts/linux-2.6.18.1-scripts.tar.bz2
Back to top
View user's profile Send_private_message 
telemetric_au

Joined: 28 Feb 2007
Posts: 54

PostPosted: Wed 28 Feb 2007, 20:38    Post_subject:  

http://puppyfiles.org/dotpupsde/dotpups/Wifi/compiling-kernel-scripts/
Back to top
View user's profile Send_private_message 
telemetric_au

Joined: 28 Feb 2007
Posts: 54

PostPosted: Thu 01 Mar 2007, 08:37    Post_subject:  missing files
Sub_title: more
 

libacl.so.1.1.0 (libacl.so.1)
libattr.so.1.1.0 (libattr.so.1)
libproc.so.3.1.8 (libproc.so.3.1.9) (`_3_1_5' )
libselinux.so.1
libsepol.so.1
ls
sysctl


well i got it install, and dialing but it drops almost straight after a few screeches....
there's also apparently a speed limit of 14kbps in freeware version...

so would interested to hear if anyone can use them all the way...
missing_files.rar
Description  missing files from while trying to install HCF drivers
rar

 Download 
Filename  missing_files.rar 
Filesize  222.56 KB 
Downloaded  785 Time(s) 
Back to top
View user's profile Send_private_message 
telemetric_au

Joined: 28 Feb 2007
Posts: 54

PostPosted: Fri 02 Mar 2007, 00:54    Post_subject: solved: "The line is busy"  

well im making this post from puppy with wvdial working after several days non-stop...

i just overcame my largest problem which was getting a "The line is busy" error and it dropping after dialing.

this was solved by editing the /etc/wvdial.conf so that the first init line read: (this stops it from detecting a busy tone)

Init1 = AT &F X1

i also read other possibilities on linmodems mailing list such as: AT &F X3, AT FX 1, X1 inserted... and also booting with kernel option: pci=usepirqmask, and or pci=noacpi

then it would drop in the negotiation part with some ppp error:

this was solved by adding the file:

/etc/ppp/peers/wvdial

and making the first line read: noauth

some handy tips:

run: wvdial >/var/log/wvdial.log 2>&1 &

(this will create a log of the conection attempt in /var/log )

also /var/log has a messages file where i found:
"Can't open options file /etc/ppp/peers/wvdial: No such file or directory" -which put me onto the final solve. Laughing

i am dialing from 10km rural area from city, and may need these extra options due to isp, line quality, electric fence interference, though i used the noauth option for my zaurus while travelling with success Smile !
Back to top
View user's profile Send_private_message 
jcoder24


Joined: 06 May 2005
Posts: 601
Location: Barbados

PostPosted: Sun 24 Jun 2007, 11:52    Post_subject:  

Good news for hsfmodem owners --your days of hex-editing drivers or applying hsfpatch to get full speed from your free conexant drivers may soon be over.

NathanF has compiled hsf drivers into the latest version of grafpup. When booting grafpup they actually initialise my modem. I manually setup the devices and it was detected by wvdialconf and the modem actuall dialed the number but then gave an error which I can't remember (that was over a month ago).

I'm to do more research when I find the time, but if we can get this working it would be a welcomed addition.

What little research I did back then indicated that someone had ported the older free hsf drivers over to the 2.6 kernel. I assume that this work should make it easy for someone with the know-how to port over the hcf drivers as well.
Back to top
View user's profile Send_private_message 
panzerpuppy

Joined: 02 Oct 2007
Posts: 632

PostPosted: Fri 02 Nov 2007, 15:41    Post_subject:  

Any progress with this free driver port to k2.16?
I'm especially interested in the HCF driver progress.

By the way,is there a .pup/.pet package available of this free HSF driver port?
I'd also like to know if they work now with the newest Puppy 3.01
Back to top
View user's profile Send_private_message 
benign

Joined: 29 Nov 2007
Posts: 23

PostPosted: Thu 29 Nov 2007, 03:19    Post_subject: What now? Help needed!  

I'm new to Puppy, I've only had it for a few days because I was using it to recover data from a hard drive that was submerged. Anyway, it seems like a nice little distro, so I'm trying to get everything working properly to get more familiarized with linux.

I'm using 2.16seamonkey_fulldrivers.iso or whatever it's called.

I've downloaded the HSF drivers for my modem (14F1:2f30) and was able to compile them after downloading and extracting linux-2.6.18.1-scripts.tar.bz2 and devx_216.sfs

I try to run HSFCONFIG, but it won't let me enter a region, it says FOLD command not available; however, I can still dial the modem, and the handshake seems normal, but no connection is made.

So I downloaded the missing_files.rar that contain:

libacl.so.1.1.0 (libacl.so.1)
libattr.so.1.1.0 (libattr.so.1)
libproc.so.3.1.8 (libproc.so.3.1.9)
libselinux.so.1
libsepol.so.1
ls
sysctl

I renamed the files to what is in parenthesis, and put all the lib* files in the /lib directory. I put a copy of sysctl in /bin and /sbin (wasn't sure), and renamed the original ls in /bin to lsorig before replacing it with the above ls. Then I rebooted.

Now, if I run the new ls, I get an error about shared libs or something. If I replace the new ls with the original ls, there are no errors when I run ls.

The problem still remains: I can't get HSFCONFIG to recognize the region, nor get linux to use the FOLD command.

I've read about symbolically linking, but I have no idea what that means other then I think it has something to do with the ln -s command.

Any help would be appreciated!
Back to top
View user's profile Send_private_message 
muggins

Joined: 20 Jan 2006
Posts: 6689
Location: lisbon

PostPosted: Wed 20 Feb 2008, 03:57    Post_subject:  

I just thought I'd post here that I'm sending this with a HSF modem, (14f1:2f00), using pup2.16 & a ubuntu/dell driver, and it's not speed restricted.

I never came up against any issues with a fold command. I've posted in this other thread:

http://www.murga-linux.com/puppy/viewtopic.php?p=175841#175841
Back to top
View user's profile Send_private_message 
craftybytes


Joined: 17 Nov 2006
Posts: 298
Location: QLD AUSTRALIA

PostPosted: Tue 26 Feb 2008, 01:42    Post_subject:  

.
I don't think a .pet package is doable for the hcf/hsf modem drivers from Conexant..

The reason being that when one does a 'compile' of the drivers - how the driver compiles depends specifically on what "model/type" of winmodem you have in your computer..

The Conexant drivers package available as .deb package ( @muggins ubuntu/dell driver would be one of these ) are actually the base driver package that then is used to "compile" the relevant modem drivers WITHIN the Linux kernel being used AND against the physical winmodem 'model/type' in the computer ( e.g.. @muggins HSF modem 14f1:2f00 )..

I believe therefore it would be very difficult to put together a 'generic' .pet package that would be capable of covering ALL the various 'models/types' of hcf/hsf based ( Conexant ) winmodems that may be used by Puppy users..

As this particular thread explains - you need to do a 'compile' for YOUR particular modem's drivers..

Even NathanF had to 'compile' as @jcoder24 stated earlier in one of his posts -
Code:

NathanF has compiled hsf drivers into the latest version of grafpup.


The only other possibility is that if all of us Puppy users who have been successful in 'compiling' and using the Conexant based winmodem drivers for their particular modems were to submit their working 'modem drivers' to a common pool (yet to be determined) - then maybe other Puppy users looking for these "drivers" could benefit from our efforts - this might be worth further discussion..

Just my 2 c'ss of ranting..

crafty.
.
.

_________________
3 x boot:- ASROCK VIA 'all-in-one' m/b; AMD Duron 1.8Ghz+; 1.0GB RAM; 20GB hdd (WinXP Pro); 80GB hdd (MEPIS 3.4-3/Puppy v2.15CE Frugal); 1GB USB pendrive (Puppy 2.15CE Frugal); CD/DVDRW; 17" LCD monitor; HSF 56k modem... MEPIS is great.. Puppy ROCKS..
Back to top
View user's profile Send_private_message 
jcoder24


Joined: 06 May 2005
Posts: 601
Location: Barbados

PostPosted: Tue 26 Feb 2008, 15:11    Post_subject:  

The hcf/hsf drivers typically have the facility to handle the different model/types of modems.

The problem with creating a generic package of the hsf driver is that one would have to be created for each kernel version used by puppy.

These dell drivers from the license file appears to be Linuxant based, so it would be interesting to find out how dell managed this one.
Back to top
View user's profile Send_private_message 
craftybytes


Joined: 17 Nov 2006
Posts: 298
Location: QLD AUSTRALIA

PostPosted: Tue 26 Feb 2008, 22:15    Post_subject:  

.
Yep - that is surely the crux of the matter -

Code:

The problem with creating a generic package of the hsf driver is that one would have to be created for each kernel version used by puppy.


How many kernel versions has Puppy used say since Puppy v2.10..??

I'm sure there may be some 'backward-compatibility' of use of earlier versions of the modem drivers able to be installed in later versions of Puppy - but can say a driver compiled for kernel version 2.6.15 work properly in a Puppy with kernel version 2.6.18.x - or even 2.6.20.x - or even in Puppy 3.x series with kernel 2.6.21.x ..?

It does seem from user experience that ANY Linuxant/Conexant HSF/HCF modem drivers to work correctly really MUST be 'compiled' against the version of kernel for the particular Puppy being used AND against the actual physical 'model/type' of modem card installed in the users computer - otherwise we be getting into the realms of "maybe/maybe not"..!!

Anyway - those of us who still use these modem cards will just have to be more aware of the limitations that Linuxant have forced on us as Linux & Puppy users..

crafty.
.
.

_________________
3 x boot:- ASROCK VIA 'all-in-one' m/b; AMD Duron 1.8Ghz+; 1.0GB RAM; 20GB hdd (WinXP Pro); 80GB hdd (MEPIS 3.4-3/Puppy v2.15CE Frugal); 1GB USB pendrive (Puppy 2.15CE Frugal); CD/DVDRW; 17" LCD monitor; HSF 56k modem... MEPIS is great.. Puppy ROCKS..
Back to top
View user's profile Send_private_message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Wed 27 Feb 2008, 10:03    Post_subject:  

jcoder24 wrote:
one would have to be created for each kernel version used by puppy.

With the current situation of 3 different streams of Puppy (2.x,3.x,4.x), plus a few official "retro" versions, plus the bizarre plethora of derivatives, it certainly seems complex. But actually there are only a few different kernels in use:

Puppy 2.0/2.01 = k2.6.16.7
Puppy 2.02/2.10/2.11 = k2.6.16.7-variant
Puppy 2.12-2.16 = k2.6.18.1
Puppy 2.17 = k2.6.21.5
Puppy 3.x = k2.6.21.7
Puppy 4.x unconfirmed, but possibly 2.6.25

Puppy 2.17 was really an intermediate version leading up to Puppy 3.0, and anything earlier than Puppy 2.14 lacks important updates.
So until Puppy4's kernel is finalised, there are really only 2 kernels that need to be supported:
2.6.18.1 and 2.6.21.7

That's not too bad. And Puppy4-retro has the same 2.6.21.7 kernel as Puppy3, so this is a solution for HCF/HSF users who want to use Puppy4.
Back to top
View user's profile Send_private_message 
Display_posts:   Sort by:   
Page 2 of 2 Posts_count   Goto page: Previous 1, 2
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » House Training » HOWTO ( Solutions )
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0854s ][ Queries: 13 (0.0089s) ][ GZIP on ]