linux/module.h problem
im just trying to compile this code

Quote:
#define MODULE
#include <linux/module.h>

int init_module (void) /* Loads a module in the kernel */
{
printk("Hello kernel n");
return 0;
}

void cleanup_module(void) /* Removes module from kernel */
{
printk("GoodBye Kerneln");
}
the compiler is showing this error

Quote:
gizmo@ubuntu:~/driver$ sudo gcc -c hello.c
hello.c:2:26: error: linux/module.h: No such file or directory


can anyone help me please?

and i find this answer

Replace the KDIR with the path where your linux sources are.

& i am using ubuntu 12.04 !
with 3.2.0-23-generic-pae

(Do you really think kernel programming is for beginners?)
You should have a file called /usr/include/linux/module.h -- if not, you have to install package kernel-source or kernel-headers.

PS: and please use those famous [code] and [/code] tags; you have been asked countless times to do so.

Sir , please help me , i want to create my own product in c langauge but i know that i have not enough knowledge for creating that product , so i am trying this .

but i am beginner !

please give me solution , i love c language , but its too typical for me , to join the programming of device drivers , i want to code at higher level , like where i can create something good !

&you know , whenever i see your comment , i think that today i will get something new from you !

You don't use GCC (gcc) directly when compiling a Kernel module; use a Makefile instead.

Here's an example Makefile that could be used for a file named 'hello.c':

You do NOT need to be root (via sudo) to compile your Kernel module into a kernel object file. You will however need to be root to install (insmod) and remove (rmmod) it from the running kernel.

If any of what I have stated is above your current comprehension, then I suggest that you pursue learning the basics of C programming, then move on perhaps to learning about Makefiles. A good online tutorial for C programming is available for download at: http://beej.us/guide/bgc/

You should ask help from a competent linux-admin to do the following things:

1. install kernel source under /usr/src/linux
(most likely via a symlink to the actual location, eg:

/usr/src/linux -> /usr/local/src/linux
/usr/local/src/linux -> /usr/local/src/linux-3.3.7

2. Create symlinks in /usr/include (after renaming the previous content):

Check:
When it is done, #include <linux/module.h> will work. But, as I've already warned you, it's not for beginners.

Not every Linux distro uses the location /usr/src/linux; perhaps Debian does, but Ubuntu and Redhat/Fedora do not.

However, it is my understanding that the "universal" way to locate the Linux header files is to reference /lib/modules/`uname -r`/build. This target is a symbolic link to the location where the Kernel Header files are located; for example, on my Fedora 16 system, this is at /usr/src/kernels/3.4.2.-1.fc16.x86_64. Under Kubuntu 12.04, it is located at /usr/src/linux-headers-3.2.0-24-generic.

If the OP is unable to locate "linux/module.h", then they need to install the Kernel Header files. How that is accomplished varies from one distro to another. The OP should first attempt to use his system's package manager.

Another method for people who usually compile kernel for themselves:

put the current version of kernel-source into /usr/local/src/linux-x.y.z
then at boot time from rc.local:

This way /usr/src/linux is always points to the current source; links linux, scsi, asm and asm-generic in /usr/include point to the right place, too.

PS: this line can also be useful:

@Tushar_pandey:
Check the below link, it will answer most of your questions.
http://www.freesoftwaremagazine.com/.../drivers_linux

That does indeed seems like a great tutorial. But the section containing information on how to build a module is incorrect (and has a syntax error). Aside from the hard-coded Kernel version number (which the author acknowledged may not be the same for other systems), not every system stores kernel header files in /usr/src. The usage of "pwd" is also incorrect. In summary, the command will not work on all systems.

The proper way is to use something like:
If one hates to type lengthy commands such as the one above, then the solution is to augment the Makefile to contain a similar statement. The OP can refer to my previous post for an example.