[hsflinux] HSF driver with kernel 188.8.131.52
Linuxant support (Jonathan)
support at linuxant.com
Thu Sep 9 10:51:10 EDT 2004
instead of modifying the file '/etc/init.d/modules', you could modify
the file '/etc/modules.d/hsf' and remove the line 'probeall hsfserial'
and then run the 'update-modules' command in a root shell. It should fix
the problem without disabling a mechanism of your Linux distribution.
All top level modules are inserted into the kernel to find the right one
for your modem or in other words, probing is used. Depending on the
Linux kernel used, the unused modules are either kept in the kernel or
not inserted at all.
Technical specialist / Linuxant
support at linuxant.com
Dave Driver wrote:
> I think I finally know what the problem is, at least in my case. Oddly
> enough, the problem isn't directly with the Linuxant driver, more of a
> problem with my distro, (Gentoo) and probably several others.
> After running hsfconfig for the first time, the modem works. All the
> modules load correctly. This is good until after the next reboot. Then
> on accessing the modem the system goes screwy and tries to load the
> modules over and over again, in an alias loop caused by the fragile
> contents of /etc/modprobe.conf. However, modprobe.conf on my system
> isn't the same as when it was first configured by hsfconfig, and here
> lies the problem. During each boot, the /etc/init.d/modules script runs
> modules-update. Now I don't think it ought to be doing this for a 2.6.x
> system, since modules-update is a 2.4 function. It updates modules.conf
> from the contents of the files in modules.d. It also calls another
> script that converts modules.conf to modprobe.conf, and this puts a lot
> of extra hsf stuff in that isn't meant to be there. I believe that this
> conversion from modules.conf to modprobe.conf should only be done once
> ever, at the time you upgrade from 2.4 to 2.6.
> So my fix is to edit the file /etc/init.d/modules, and comment out the
> line that runs modules-update. After that it will work fine.
> I'm not sure that I agree with the concept of forcing all the hardware
> modules to load on all systems. If I have a system with a PCI modem, I
> don't see why I should load up the hsfmc97ich, hsfmc97via, hsfmc97ali,
> and hsfusbcd2 modules. There's room for improvement here Linuxant.
> Any comments from Linuxant Support?
> > Igor GomeZZ wrote:
> >> Hello all...
> >> I used the old driver (hsflinmodem-5.03.27.tar.gz) with my old
> >> kernel (2.4) with success.
> >> But now, with kernel 184.108.40.206 and the newest driver, I'm having
> >> problems. When I type "hsfconfig" in terminal, my system crash.
> >> Anyone have success with this kernel and this driver?
> >> Thanks
> hsflinux mailing list
> hsflinux at lists.linuxant.com
More information about the hsflinux