for one, this ensures that the header files that your module will be using are the _same_ ones that were used to build your current running version of the kernel! this might not be true if you use the kernel source headers... On Thu, 2005-01-27 at 13:13, anil dahiya wrote: > Hi Pankaj & Mandeep > your solution is also right one & my solution is also > work fine . > Now question arises which is more good one ??? > can u tell me wht advantage we will get by using ur > method ??? > -----anil > > --- pankaj dekate <kernelhackers@xxxxxxxxx> wrote: > > > > i think it's the other way around.... i.e the > > modules is being > > > compiled for a 2.4.20 (a typical modversions > > prob.!)...whereas > > > the one ver. of the kernel from which he's trying > > to "insmod" > > > is the std. RH 9 (2.4.20-8). And it's advisable > > not to use kernel > > > source headers, rather the path for your header > > files should be > > > > > > /lib/modules/<kernel ver.#>/build/include/ > > Yeps.This is the right solution.Even i had faced > > this problem.Include > > kernel headers from the above mentioned path and the > > issue will be > > resolved. > > > > Pankaj > > > > -- > > Kernelnewbies: Help each other learn about the Linux > > kernel. > > Archive: > > http://mail.nl.linux.org/kernelnewbies/ > > FAQ: http://kernelnewbies.org/faq/ > > > > > > > > > __________________________________ > Do you Yahoo!? > The all-new My Yahoo! - Get yours free! > http://my.yahoo.com > > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
