sean.mcavoy at megawheels.com
Fri May 21 13:01:00 CDT 2004
I'm still having troubles building a usable module(i.e. no unresolved
symbols), could it be some option in .config that could cause this
I went as far as setting up a fresh debian install on a PE1600sc,
downloaded linux-2.4.26.tar.gz from ftp.kernel.org, copied my existing
.config into the root of the kernel source tree. I then ran `make-kpkg
--append_to_version -kernel.org --revision 3 buildpackage kernel_image
then sym linked /usr/src/linux-2.4.26 -> /usr/src/linux-2.4. I then
installed the kernel-image package
rebooted, installed dellomsa-drivers and it built the module, but it
has unresolved symbols (local_bh_enable and local_bh_disable)
could you possibly send contents of
/usr/lib/dell/openmanage/omsa/drivers/open_src/esm_log so I can compare
it to my own? Thanks in advance.
On 21-May-04, at 7:31 AM, Charlie Orford wrote:
> Sean McAvoy wrote:
>> I'm having trouble building even using 4.90-3825. It builds the esm.o
>> module, but I still get unresolved symbols (local_bh_enable and
>> Other than making sure /lib/modules/`uname -r`/misc and
>> /usr/src/linux-2.4 are symlinked to the source tree, was there
>> anything special you had to do to get it to build a usable module?
> I have just removed the currently installed 4.90-3825 version
> and installed the latest release (4.120-3925) and it works as
> advertised here. I haven't had to do anything funky with my source
> trees. /usr/src/linux is symed to /usr/src/linux-2.4.26 and
> /lib/modules/2.4.26 exists as its own directory.
> This is a vanilla install of debian (woody), running a vanilla 2.4.26
> kernel from www.kernel.org
> Is there anything else I can check/report on that might help?
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> Please read the FAQ at http://lists.us.dell.com/faq or search the list
> archives at http://lists.us.dell.com/htdig/
Megawheels Technologies Inc.
Phone: 416.360-8211 x242
More information about the Linux-PowerEdge