Hi, I had suggested that solution(insmod -f) only for quicker approach. Compile the module with the following flag(along with the other options/flags whatever you are using currently) gcc -I/kernel_path <exixting command line string> where kernel_path is path of the code of the currently running kernel. If you are using 'Makefile' please modify gcc'c command line options as above. Note: you may verify kernel's current version by 'uname -r' and version of kernel code(i.e. being used for compiling the module)by seeing the first 4-lines of 'Makefile' of the kernel code. you will get rid from the '-f'. Best of luck rgrds Ashish -----Original Message----- From: Vinay Kalkoti [mailto:kalkoti.vinay@xxxxxxxxx] Sent: Wednesday, July 13, 2005 5:14 PM To: Ketan Mukadam Cc: Gaurav Dhiman; Ashish Kumar Verma, Noida; Sarang Radke; kernelnewbies@xxxxxxxxxxxx Subject: Re: insmod error So, will anyone tell whats the good practice. I have been inserting modules using -f till now. On 7/13/05, Ketan Mukadam <ketanm@xxxxxxxxx> wrote: > On 7/13/05, Gaurav Dhiman <gaurav4lkg@xxxxxxxxx> wrote: > > On 7/12/05, Ashish Kumar Verma, Noida <ashishv@xxxxxxxxxxx> wrote: > > > u may try insmod with -f option. > > > It works normally. > > > > -f option I believe disregard the version checking. Although its kind > of by-passing the check, it is not considered a good practise to do > that since it might lead to different set of issues later in the > development or porting. > > Also if a newbie starts to acquire bad programming habits that is much > more dangerous :-) > > Ketan > > -- > 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/
