OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Seth Arnold (sarnoldwirex.com)
Date: Mon Oct 08 2001 - 13:43:38 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    On Tue, Oct 09, 2001 at 01:57:55AM +0800, Leon Harris wrote:
    > I am having a bastard of a time with compiling the i2c and lm_sensor
    > support on immunix.
    >
    > ( see http://www2.lm-sensors.nu/~lm78/news.html)

    I took a look at their website, and was unable to easily find out if
    their modules are able to work on 2.2.x -- I see that they have support
    for the 2.4 series of kernels, but they weren't real clear about other
    kernels. (Perhaps the download packages are pretty obvious about this..)

    > These are modules which give access to hardware parameter monitoring
    > functions on modern motherboards.
    > Despite using module versioning in my kernel config, I still end up with
    > undefined symbols.
    > A typical case would be for a module such as w83781d.o, which allows
    > reading of cpu fan status, temperature etc.
    > /lib/modules/2.2.19-3_imnx/misc/w83781d.o: unresolved symbol __release_region
    > /lib/modules/2.2.19-3_imnx/misc/w83781d.o: unresolved symbol __check_region
    > /lib/modules/2.2.19-3_imnx/misc/w83781d.o: unresolved symbol __request_region
    > /lib/modules/2.2.19-3_imnx/misc/w83781d.o: unresolved symbol ioport_resource

    I've got several thoughts. First, did you run depmod -a since building
    the modules? Did you use 'modprobe' to load the modules, or did you use
    'insmod'?

    Another possibility, but getting further out of my experience, is the
    possibility that some kernel support is plain missing that is required
    for these modules. I *think* the __{release,check}_region and
    ioport_resource functions are all standard PCI kernel functions, which
    is all the more surprising why your kernel doesn't have them. (Well, one
    of our 2.2.19 machines here doesn't have them, but my development 2.4.x
    kernel does have them -- which makes me wonder if these are 2.4 modules
    trying to be loaded into 2.2.)

    You probably want to use 'modprobe' to load the modules, and run 'depmod
    -a' to fix up the dependencies before trying to load the modules. If
    neither of these thoughts work, let us know and we'll take a closer
    look. (Oh yeah, and double-check that the modules are for 2.2, not 2.4. :)

    Thanks

    _______________________________________________
    Immunix-users mailing list
    Immunix-usersmail.wirex.com
    http://mail.wirex.com/mailman/listinfo/immunix-users