[driverloader] unresolved symbols?

[Marc Boucher]

Hi Doug, Tobin,

I suspect that this problem is related to the existence of different  
2.4.19-4GB SuSE kernels with small binary level incompatibilities, and  
would suggest as workaround to use the generic RPM instead of the  
kernel-specific one.

Marc

--
Marc Boucher
Linuxant inc.

On Apr 20, 2004, at 8:34 PM, Doug Gallarda wrote:

> I'm in the same situation as Tobin.
>
> Anyone have any ideas?
>
> Thanks,
>
> Doug.
>
> Tobin Coziahr <tobin at coziahr.com> wrote:
>>
>> I just got the RPM for my laptop, running SuSe 2.4.19-4GB.
>>
>> After doing an rpm -i on it, I get the following:
>>
>> depmod: *** Unresolved symbols in
>> /usr/lib/driverloader/modules/binaries/i586/suse/linux-2.4.19-4GB/ 
>> driverl
>> oader.o
>> depmod: schedule
>> execution of driverloader-1.64_k2.4.19_4GB-lsuse script failed, exit
>> status 1
>>
>> What am I missing?  I didn't think the RPM had any prerequisites?
>>
>> Thanks.
>>
>> -Tobin
>
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader
>