Koozali.org: home of the SME Server

unresolved symbols ....

Kelvin

unresolved symbols ....
« on: May 31, 2003, 11:47:29 AM »
Hi E-Smithers,

I'm trying to configure an IDE RAID card as an add-on card for testing on an SME 5.6 machine.

When I issue the command :-

insmod drivername.o

it comes back with

unresolved symbol scsi_register_R(some number)
unresolved symbol pci_find.....
.
.
and a few others.

The driver module was extracted from the driver disk from the 2.4.18-5 folder, which I assume would match the kernel on SME 5.6.

I have previously verified that the drivers work out of the box with a stock RH 7.3 and RH 8.0 distro (stock meaning the standard available version).

So, then I decided to try insmod -f drivername.o with the drivers from both 2.4.18-5 as well as 2.4.18-3 with exactly the same results.

Any ideas why ?

Kelvin

Charlie Brady

Re: unresolved symbols ....
« Reply #1 on: June 01, 2003, 04:02:45 AM »
Kelvin wrote:

> When I issue the command :-
>
> insmod drivername.o
>
> it comes back with
>
> unresolved symbol scsi_register_R(some number)
> unresolved symbol pci_find.....

You need "modprobe drivername". Or you need to know which other modules your module requires, and load those first (modprobe automatically loads all required modules). I'd guess "scsi_mod.o" is what you need in your case.

Charlie

Kelvin

Re: unresolved symbols ....
« Reply #2 on: June 01, 2003, 04:36:02 AM »
G'Day Charlie,

Thanks for your suggestion.

I had previously looked at modules.dep on the driver disk already and it lists scsi_mod as a required module. Doing an lsmod shows that scsi_mod is already loaded (incidentally, all SME 5.6 servers I've built so far using only IDE devices always has scsi_mod, ide_scsi and sd_mod loaded even when there is no tape drive in the system which usually uses ide_scsi support (IDE tape drives)).

Anyway, I tried "modprobe drivername" and it came back with the same unresolved symbol errors.

Any further suggestions on what to try next ? Unfortunately, I don't have access to driver source files to try a recompile. I thought having a driver for the relevant kernel version was sufficient ? And, to help me understand it better, if attempting an insmod -f with the kernel 2.4.18-3 module, would there be significant enough differences between the 2.4.18-3 and 2.4.18-5 kernels to stop the lower version one from loading with the same errors ? I have tested the lower version driver with the stock RH 7.3 distro and it loads fine.

Thanks.

Kelvin

Charlie Brady

Re: unresolved symbols ....
« Reply #3 on: June 01, 2003, 04:44:30 AM »
Kelvin wrote:

> Anyway, I tried "modprobe drivername" and it came back with
> the same unresolved symbol errors.

Then your module doesn't match the version and architecture of the installed kernel.

> Unfortunately,
> I don't have access to driver source files to try a
> recompile.

Then (IMO) you should avoid that hardware.

Charlie

Kelvin

Re: unresolved symbols ....
« Reply #4 on: June 01, 2003, 05:55:12 AM »
Thanks for the reply Charlie,

Don't mean to sound like a doubting thomas, but ...

>Then your module doesn't match the version and architecture of the installed
>kernel.

Hmm... by architecture I take it you mean i686, i386, athlon, etc ?

Doesn't the SME and RH installer automatically determine the architecture of the PC it's installing on ? If so, and since this is the same one PC we're talking about, both RH and SME should install for the same architecture right ?

Assuming the above is right, then architecture is not an issue. I have confirmed the driver will load under a stock RH 7.3 with 2.4.18-3 on the same PC.

Now, kernel version. When I loaded RH 8 onto the same PC again, I tried to insmod the RH 7.3 driver and RH obviously complained and reported that the module was compiled for kernel 2.4.18-3, which is correct. I then tried to insmod the 2.4.18-5 version and again, RH complained reporting that the module was compiled for kernel version 2.4.18-5, which is what I was expecting.

So, I can only conclude at this point that the architecture and kernel version of the driver module should not be an issue, but it still will not work.

Any further suggestions ?

Kelvin

Kelvin

Re: unresolved symbols ....
« Reply #5 on: June 01, 2003, 06:24:29 AM »
By the way Charlie,

Is the kernel-2.4.18-5.xxx.rpm from the SME 5.6 CD the original one (as downloaded without modifications from RedHat) or is it compiled by Mitel ?

Kelvin

Charlie Brady

Re: unresolved symbols ....
« Reply #6 on: June 01, 2003, 09:00:23 PM »
Kelvin wrote:

> Is the kernel-2.4.18-5.xxx.rpm from the SME 5.6 CD the
> original one (as downloaded without modifications from
> RedHat) or is it compiled by Mitel ?

"rpm -qi kernel" will tell you.

Charlie