problems loading i2c-proc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It appears that this problem was due to my mistakely compiling
the modules for a SMP kernel with a uniprocessor kernel config.
Have fixed that, and things load OK now.

Steve Timm


On Thu, 7 Jul 2005, Jean Delvare wrote:

> Hi Steven,
>
>> Problems happen in i686 and athlon architectures.  Opteron (x86_64)is
>> ok. Compiles are clean on all.
>> When I do  modprobe i2c-proc, the following happens:
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol create_proc_entry_R0be93f3a
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kmalloc_R93d4cfe6
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol __generic_copy_to_user_Rd523fdd3
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol remove_proc_entry_Re94539f7
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol proc_bus_Rd6eafc0f
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol sprintf_R1d26aa98
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol kfree_R037a0cba
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o:
>> unresolved  symbol printk_R1b7d4074
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o failed
>> /lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/i2c/i2c-core.o: insmod
>>
>> i2c-procfailed
>>
>>
>> Any idea what might be wrong?  Some wrong header getting into the
>> compile somewhere?  Other?  As I say, x86_64 version is OK.
>
> Make sure you have File Systems > /proc file system support enabled
> (CONFIG_PROC_FS). In theory i2c-proc should depend on it (in Config.in),
> but now it looks like it doesn't...
>
> Another possibility is a problem with symbol versioning, which you seem
> to have enabled. It should work, but maybe you could try without
> versioning, just in case.
>
> Hope that helps,
>

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm at fnal.gov  http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux