Find the answer to your Linux question:
Results 1 to 3 of 3
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    kernel and unresolved symbols problems

    I have RedHat Linux AS 3.0 and need to install PATHpilot Pro 2.0 for our RAID testing. The problem is that the server component of the PATHpilot pro keeps on displaying errors which make me unable to start the server component.

    this is the displayed error:

    Warning: kernel-module version mismatch /usr/lib/PATHpilot/upv64G/picd.o was compiled for kernel version 2.4.7-10 while this kernel is version 2.4.21-4.EL

    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol interruptible_sleep_on_timeout_Re0838aee
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol scsi_devicelist_Re94a7c6e
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol gendisk_head_R82d1383c
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol scsi_release_request_Ra7f81f05
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol scsi_wait_req_R47c07365f
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol create_proc_entry_R323a5564
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol remove_proc_entry_Rfc2814bb
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol send_sig_R6347e5fd
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol scsi_allocate_request_Rab9a1bc6
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol scsi_hostlist_Rc29223a0
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol free_pages_R234535e0
    /usr/lib/PATHpilot/upv64G/picd.o: unresolved symbol __get_free_pages_R5b3b8f78
    Hint: You are trying to load a module without a GPL compatible license and it has unresolved symbols. Contact the module supplier for assistance, only they can help you.

    the PATHpilot installation is in an Installshield package and the RPM inside the Installshield package already have precompiled components and just copies them into the specified directories, so i can't recompile it for my kernel version...

    i'm having trouble with this and would really be very grateful if anyone would have a solution or even a suggestion which i could try...

  2. #2
    Linux Guru sarumont's Avatar
    Join Date
    Apr 2003
    Try getting the source tree for the kernel specified and compiling a new kernel since you can't get the source for the driver.
    "Time is an illusion. Lunchtime, doubly so."
    ~Douglas Adams, The Hitchhiker's Guide to the Galaxy

  3. #3
    thanx for your advice...

    ...i tried to install a different kernel the one specified by the component (2.4.7-10). i was able to get it to boot using that kernel, the kernel incompatibility wasn't there anymore but the unresolved symbols thingys were still there...

    ...what could be causing that problem?

  4. $spacer_open

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts