| View previous topic :: View next topic |
| Author |
Message |
flysoul
n00b
Joined: 18 Feb 2004
Posts: 10
|
 Posted: Wed Jan 12, 2005 11:40 pm Post subject: Unresolved symbols |
 |
|
I'm trying to load a module and i get some unresolved symbols:
| Code: |
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol register_chrdev_R07a6f6f0
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol scsi_register_R6180b425
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_read_config_byte_R0e425a9e
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_read_config_word_Rd25f3240
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_write_config_word_R97d04e11
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol scsi_delete_timer_R4f0b4564
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_alloc_consistent_R7c1256bc
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol bread_R1213bc58
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_read_config_dword_R43e318de
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_write_config_dword_R7fbf61ba
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol boot_cpu_data_R0657d037
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol scsi_unblock_requests_R241b371c
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_free_consistent_R63356fa0
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol scsi_block_requests_Rb6327a47
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_write_config_byte_R62c99bc3
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_enable_device_R30af41e2
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol __brelse_R2b69a6ab
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_set_master_Rc4d9ced5
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol proc_scsi_R217c68d4
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol pci_find_device_R2ec905d7
a320raid-2.4.20-20.9-i386: a320raid-2.4.20-20.9-i386: unresolved symbol scsi_add_timer_R6b2aec52
|
This module isn't open source, so I can't compile it for my kernel. I searched the kernel symbols and found symbols with the same name as the ones on the module, but with a different number at the end:
(the first is the symbol the module uses and the other is the symbol my kernel has)
| Code: |
register_chrdev_R07a6f6f0 => register_chrdev_Rd8643192
scsi_register_R6180b425 => scsi_register_Rbc540852
pci_read_config_byte_R0e425a9e => pci_read_config_byte_R3ccefab4
pci_read_config_word_Rd25f3240 => pci_read_config_word_R923654cb
pci_write_config_word_R97d04e11 => pci_write_config_word_Rf23d8795
scsi_delete_timer_R4f0b4564 => scsi_delete_timer_R7b0578f3
pci_alloc_consistent_R7c1256bc => pci_alloc_consistent_Rca1c24c8
bread_R1213bc58 => bread_Rebb3891a
pci_read_config_dword_R43e318de => pci_read_config_dword_R0bf170e2
pci_write_config_dword_R7fbf61ba => pci_write_config_dword_R77f7f940
boot_cpu_data_R0657d037 => boot_cpu_data_R4a8db2ac
scsi_unblock_requests_R241b371c => scsi_unblock_requests_R3f9a9d6a
pci_free_consistent_R63356fa0 => pci_free_consistent_R1bfc1908
scsi_block_requests_Rb6327a47 => scsi_block_requests_R55960f01
pci_write_config_byte_R62c99bc3 => pci_write_config_byte_R364fc2a2
pci_enable_device_R30af41e2 => pci_enable_device_R1bc741d2
__brelse_R2b69a6ab => __brelse_R267cf110
pci_set_master_Rc4d9ced5 => pci_set_master_R99cc7ae2
proc_scsi_R217c68d4 => proc_scsi_R503bfc5e
pci_find_device_R2ec905d7 => pci_find_device_Rc584f4e3
scsi_add_timer_R6b2aec52 => scsi_add_timer_Rd8dbb025
|
Can I change the symbols name on the binary module? |
|
| Back to top |
|
 |
Evil Petting Zoo
n00b
Joined: 30 Nov 2002
Posts: 41
Location: Minneapolis, MN
|
| Posted: Thu Jan 13, 2005 8:16 am Post subject: |
|
|
| First thing I would check is to make sure that you are running the same kernel version as the module was built for. If you are running anything but Linux 2.4.20 I'd try switching kernels right away. Another thing to check is to make sure you have SCSI support and other possible dependencies enabled in your kernel. |
|
| Back to top |
|
|
flysoul
n00b
Joined: 18 Feb 2004
Posts: 10
|
| Posted: Thu Jan 13, 2005 1:09 pm Post subject: |
|
|
| I'm using 2.4.20. I have scsi support on my kernel. As I said before, all the symbols are on my kernel/drivers, but they have a different number at the end. This way, when the module tries to import the symbols it fails. |
|
| Back to top |
|
|
Evil Petting Zoo
n00b
Joined: 30 Nov 2002
Posts: 41
Location: Minneapolis, MN
|
| Posted: Thu Jan 13, 2005 9:00 pm Post subject: |
|
|
| You could try switching all the SCSI stuff to being module based, but I'm not sure if that would help. Try posting a bit more information about your configuration. Include the output from uname -a and which SCSI module you're using. |
|
| Back to top |
|
|
A.S. Pushkin
Guru
Joined: 09 Nov 2002
Posts: 418
Location: dx/dt, dy/dt, dz/dt, t
|
| Posted: Sat Jan 15, 2005 7:50 am Post subject: unresolved symbols |
|
|
I'm in the process of setting up my first Gentto box and I ran into a similar problem. Some may be as I expect, but I was told that if drivers are compiled into the kernel they may come up as unresolved if probed and not found.
_________________
ASPushkin
"In a time of universal deceit - telling the truth is a revolutionary act." -- George Orwell |
|
| Back to top |
|
|
|
Kernel & Hardware
