Greg, One further thing is that I noticed that the file cciss.mod.c file was not created. When I did a full make modules before this file was compiled into cciss.mod.o which was then linked with cciss.o to make the cciss.ko module. I am wondering if you know the purpose of the cciss.mod.c file which is created by the kernel. When I looked at it seemed to contain version information. I will keep testing either way, but I would love to understand why this has changed in the 2.6 kernel if you happen to know. Thanks, Chase ----- Original Message ----- From: "Greg KH" <greg@kroah.com> To: <chase.maupin@sbcglobal.net> Cc: "kernelnewbies" <kernelnewbies@nl.linux.org> Sent: Saturday, April 10, 2004 11:50 AM Subject: Re: compiling select modules with kernel 2.6.x > On Sat, Apr 10, 2004 at 11:03:26AM -0500, chase.maupin@sbcglobal.net wrote: > > Greg, > > > > Thank you for getting back to me. Yes I have tried this and unfortunately I > > get the error that there is "No rule to make target drivers/block/cciss.ko". > > I looked at the drivers/block/Makefile and the targe is listed as > > "obj-$(CONFIG_BLK_CPQ_CISS_DA) += cciss.o. > > Are you sure your .config file is set up properly so that you can build > the driver normally? > > What about just doing 'make SUBDIRS=drivers/block' ? > If the driver builds that way, the way I specified should also work. > > Good luck, > > greg k-h -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/