[driverloader] unresolved symbols?
marc at linuxant.com
Wed Apr 21 12:03:43 EDT 2004
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
On Apr 20, 2004, at 8:34 PM, Doug Gallarda wrote:
> I'm in the same situation as Tobin.
> Anyone have any ideas?
> 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
>> 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?
> driverloader mailing list
> driverloader at lists.linuxant.com
More information about the driverloader