[hsflinux] Re: Contents of hsflinux digest
Rajic Igor
irajic at beotel.net
Thu Sep 9 00:41:37 EDT 2004
hsflinux-request at lists.linuxant.com wrote:
>Send hsflinux mailing list submissions to
> hsflinux at lists.linuxant.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://www.linuxant.com/mailman/listinfo/hsflinux
>or, via email, send a message with subject or body 'help' to
> hsflinux-request at lists.linuxant.com
>
>You can reach the person managing the list at
> hsflinux-owner at lists.linuxant.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of hsflinux digest..."
>
>
>Today's Topics:
>
> 1. problem with install on 2.6.4 system (Robert E. Blair)
> 2. Re: HSF driver with kernel 2.6.8.1 (Linuxant support (Jonathan))
> 3. Re: Linuxant Driver no longer working after Suse 9.0 upgrade
> (Linuxant support (Jonathan))
> 4. Re: problem with install on 2.6.4 system
> (Linuxant support (Jonathan))
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 08 Sep 2004 11:39:56 -0500
>From: "Robert E. Blair" <reb at anl.gov>
>Subject: [hsflinux] problem with install on 2.6.4 system
>To: hsflinux at lists.linuxant.com
>Message-ID: <413F35DC.8040103 at anl.gov>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>I'm running RHEL 3 with a custom 2.6.4 kernel (I need ACPI support and a
>custom software package that requires a module that is prebuilt). When
>I try to install the hsfmodem rpm it fails (see below). What are my
>options?
>
>[root at pclap34 tmp]# rpm -Uvh hsfmodem-6.03.00lnxt04082400full-1.i386.rpm
>warning: hsfmodem-6.03.00lnxt04082400full-1.i386.rpm: V3 DSA signature:
>NOKEY, key ID 5dfbf7dc
>Preparing... ###########################################
>[100%]
> 1:hsfmodem ###########################################
>[100%]
>Conexant HSF softmodem driver, version 6.03.00lnxt04082400full
>
>If you need license keys, assistance or more information, please go to:
> http://www.linuxant.com/
>
>When reporting a problem for the first time, please send
>us the file generated by "hsfconfig --dumpdiag".
>
>Warning: existing driver modules found under:
> /lib/modules/2.6.4-03-NeTraverse-i686-UP-4GB/misc/
>
>No pre-built modules for: RedHat-3 linux-2.6.4-03-NeTraverse-i686-UP-4GB
>i686
>
>Trying to automatically build the driver modules...
>(this requires a C compiler and proper kernel sources to be installed)
>
>Building modules for kernel 2.6.4-03-NeTraverse-i686-UP-4GB, using
>source directory
>/lib/modules/2.6.4-03-NeTraverse-i686-UP-4GB/build. Please wait...
>done.
>/usr/sbin/hsfconfig: Cannot find major device number for hsfdcp in range
>240-249error: %post(hsfmodem-6.03.00lnxt04082400full-1) scriptlet
>failed, exit status 1[root at pclap34 tmp]#
>
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 09 Sep 2004 09:51:10 +0000
>From: "Linuxant support (Jonathan)" <support at linuxant.com>
>Subject: Re: [hsflinux] HSF driver with kernel 2.6.8.1
>To: Dave Driver <reluctantconexantuser at driveconsultants.com>
>Cc: hsflinux at lists.linuxant.com, Igor GomeZZ <igor.gomezz at gmx.net>
>Message-ID: <4140278E.5020807 at linuxant.com>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>Hi,
>
>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.
>
>Regards,
>
>
>Jonathan
>Technical specialist / Linuxant
>www.linuxant.com
>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 2.6.8.1 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
>>https://www.linuxant.com/mailman/listinfo/hsflinux
>>
>>
>
>------------------------------
>
>Message: 3
>Date: Thu, 09 Sep 2004 11:24:11 +0000
>From: "Linuxant support (Jonathan)" <support at linuxant.com>
>Subject: Re: [hsflinux] Linuxant Driver no longer working after Suse
> 9.0 upgrade
>To: Brian Burridge <brian at burridge.net>
>Cc: hsflinux at lists.linuxant.com
>Message-ID: <41403D5B.4070802 at linuxant.com>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>Hi,
>
>did you remove the pre-compiled RPM before you have installed the
>generic RPM? If not, then this is most likely the problem. Please remove
>both packages with the following command in a root shell :
>
>---
>rpm -e --allmatches driverloader
>---
>
>Then, try again to install the generic package and use the 'dldrconfig'
>command in a root shell to compile the DriverLoader module.
>
>Regards,
>
>
>Jonathan
>Technical specialist / Linuxant
>www.linuxant.com
>support at linuxant.com
>
>
>Brian Burridge wrote:
>
>
>>I've been using Suse 9, 2.4.21-243-default kernel without problems.
>>Recently I did an upgrade and it looks like I'm now i686 instead of
>>i586. When I do dldrconfig --auto I get:
>>
>>Linuxant DriverLoader for Wireless LAN devices, version 1.63
>>
>>No pre-built modules for: SuSE-9.0 linux-2.4.21-243-default i686
>>
>>Please obtain the appropriate variant of this package for your system
>>or try the generic RPM or tar version.
>>
>>So I downloaded the generic rpms and it seemed to install ok, using the
>>kernel-source package I had installed. However, when I run dldrconfig
>>--kernel, I get the same message as before (pasted above).
>>
>>Brian
>>
>>_______________________________________________
>>hsflinux mailing list
>>hsflinux at lists.linuxant.com
>>https://www.linuxant.com/mailman/listinfo/hsflinux
>>
>>
>
>------------------------------
>
>Message: 4
>Date: Thu, 09 Sep 2004 11:49:08 +0000
>From: "Linuxant support (Jonathan)" <support at linuxant.com>
>Subject: Re: [hsflinux] problem with install on 2.6.4 system
>To: "Robert E. Blair" <reb at anl.gov>
>Cc: hsflinux at lists.linuxant.com
>Message-ID: <41404334.9000201 at linuxant.com>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>Hi,
>
>it seems that you have run out of available major device numbers in the
>240-249 range, this is probably because Win4Lin uses to much major
>numbers in this range.
>
>After you have installed the package, even if it fails with the error
>message you have sent us, you could try to edit the file
>'/usr/sbin/hsfconfig' and change the allowed range in the
>'choose_major()' function. For example, you could change the line :
>
>---
> first=240
>---
>
>to
>
>---
> first=230
>---
>
>in this function. It is important to know that if you increase the
>range, now some of these major numbers are already attributed to
>specific devices so it is possible that it might creates a conflict.
>
>After you have made modifications to the '/usr/sbin/hsfconfig' file,
>please run the 'hsfconfig' command in a root shell to complete the
>installation.
>
>Please also note that we do not officially supports patched kernels.
>
>Regards,
>
>
>Jonathan
>Technical specialist / Linuxant
>www.linuxant.com
>support at linuxant.com
>
>
>Robert E. Blair wrote:
>
>
>>I'm running RHEL 3 with a custom 2.6.4 kernel (I need ACPI support and a
>>custom software package that requires a module that is prebuilt). When
>>I try to install the hsfmodem rpm it fails (see below). What are my
>>options?
>>
>>[root at pclap34 tmp]# rpm -Uvh hsfmodem-6.03.00lnxt04082400full-1.i386.rpm
>>warning: hsfmodem-6.03.00lnxt04082400full-1.i386.rpm: V3 DSA signature:
>>NOKEY, key ID 5dfbf7dc
>>Preparing... ###########################################
>>[100%]
>> 1:hsfmodem ###########################################
>>[100%]
>>Conexant HSF softmodem driver, version 6.03.00lnxt04082400full
>>
>>If you need license keys, assistance or more information, please go to:
>> http://www.linuxant.com/
>>
>>When reporting a problem for the first time, please send
>>us the file generated by "hsfconfig --dumpdiag".
>>
>>Warning: existing driver modules found under:
>> /lib/modules/2.6.4-03-NeTraverse-i686-UP-4GB/misc/
>>
>>No pre-built modules for: RedHat-3 linux-2.6.4-03-NeTraverse-i686-UP-4GB
>>i686
>>
>>Trying to automatically build the driver modules...
>>(this requires a C compiler and proper kernel sources to be installed)
>>
>>Building modules for kernel 2.6.4-03-NeTraverse-i686-UP-4GB, using
>>source directory
>>/lib/modules/2.6.4-03-NeTraverse-i686-UP-4GB/build. Please wait...
>>done.
>>/usr/sbin/hsfconfig: Cannot find major device number for hsfdcp in range
>>240-249error: %post(hsfmodem-6.03.00lnxt04082400full-1) scriptlet
>>failed, exit status 1[root at pclap34 tmp]#
>>
>>
>>_______________________________________________
>>hsflinux mailing list
>>hsflinux at lists.linuxant.com
>>https://www.linuxant.com/mailman/listinfo/hsflinux
>>
>>
>
>------------------------------
>
>_______________________________________________
>hsflinux mailing list
>hsflinux at lists.linuxant.com
>https://www.linuxant.com/mailman/listinfo/hsflinux
>
>End of hsflinux Digest, Vol 14, Issue 4
>***************************************
>
>.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.linuxant.com/pipermail/hsflinux/attachments/20040908/a1669ea7/attachment.htm
More information about the hsflinux
mailing list