On Thu, 2013-05-09 at 08:49 -0700, Vishal Study wrote: > Hello targetcli experts, > > I'm using Debian-7.0 on a MIPS platform and did following to get > targetcli running on my platform. > > #apt-get install targetcli > > It went ahead and downloaded a bunch of packages and all seemed to > have downloaded OK. > > When I try to start targetcli, I get following error: > --------------------------------------------------------------------------------------------------------------------- > # targetcli > Welcome to the targetcli shell: > > Copyright (c) 2011 by RisingTide Systems LLC. > > Visit us at http://www.risingtidesystems.com. > > Kernel module target_core_mod does not exists on disk and is not > loaded. > -------------------------------------------------------------------------------------------------------------------------- > > I have target_core_mod.ko locally and when I try to insmod it, it > gives following error: > > # insmod target_core_mod.ko > target_core_mod: exports duplicate symbol __transport_register_session > (owned by kernel) > Error: could not insert module target_core_mod.ko: Invalid module format > This would seem to indicate that the target is already built into the kernel, or the way that these external modules are being built against the running kernel is bogus.. Does __transport_register_session appear in /proc/kallsyms without a [target_core_mod] suffix..? > # file target_core_mod.ko > target_core_mod.ko: ELF 64-bit MSB relocatable, MIPS, MIPS64 rel2 > version 1 (SYSV), BuildID[sha1]=0x4a0c71 > 73d4ef98d42cb28ca3fe7b2cade9ed114e, with unknown capability > 0x410000000f676e75 = 0x1000000070403, not stri > pped > > target_core_mod was built as a Module [M] per kernel config.. > > Any ideas what could have gone wrong....any pointers really appreciated. > Some background about the running kernel (cat /proc/version) and the source that this target_core_mod.ko is being built from would be helpful. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
