/lib/modules/`uname -r`/misc - shouldn't this be a directory?

[Ben Lancaster]

Hey,

I can't seem to install the standalone imon_vfd drivers from http:// 
venky.ws:

# make install
depmod
/usr/bin/install imon_vfd.ko /lib/modules/`uname -r`/misc

Following that:
# modprobe imon_vfd
FATAL: Module imon_vfd not found.

By my logic, shouldn't the install process have effectively copied  
the imon_vfd driver to a directory called misc within my running kernel?

Here's what stat says:

# stat /lib/modules/`uname -r`/misc
   File: `/lib/modules/2.6.16-1.2122_FC5smp/misc'
   Size: 139196          Blocks: 280        IO Block: 4096   regular  
file
Device: 304h/772d       Inode: 28935873    Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2006-06-04 19:32:39.000000000 +0100
Modify: 2006-06-04 19:32:39.000000000 +0100
Change: 2006-06-04 19:32:39.000000000 +0100

It's an executable file! Is that right??

# yum list installed | grep kernel
kernel-smp.i686                          2.6.16-1.2122_FC5       
installed
kernel-smp.i686                          2.6.15-1.2054_FC5       
installed
kernel-smp-devel.i686                    2.6.16-1.2122_FC5       
installed

Thanks!

Ben

[Sam Varshavchik]

Ben Lancaster writes:

>  Hey,
>  
>  I can't seem to install the standalone imon_vfd drivers from http:// 
>  venky.ws:
>  
>  # make install
>  depmod
>  /usr/bin/install imon_vfd.ko /lib/modules/`uname -r`/misc
>  
>  Following that:
>  # modprobe imon_vfd
>  FATAL: Module imon_vfd not found.
>  
>  By my logic, shouldn't the install process have effectively copied  
>  the imon_vfd driver to a directory called misc within my running kernel? 
Correct.

>  
>  Here's what stat says:
>  
>  It's an executable file! Is that right?? 
No.

The driver makefile is broken.  It assumes that the misc subdirectory 
already exists.

[Mikkel]

Sam Varshavchik wrote:
>  Ben Lancaster writes:
>  
> > Hey,
> >
> > I can't seem to install the standalone imon_vfd drivers from http://
> > venky.ws:
> >
> > # make install
> > depmod
> > /usr/bin/install imon_vfd.ko /lib/modules/`uname -r`/misc
> >
> > Following that:
> > # modprobe imon_vfd
> > FATAL: Module imon_vfd not found.
> >
> > By my logic, shouldn't the install process have effectively copied 
> > the imon_vfd driver to a directory called misc within my running kernel?
>  
>  Correct.
>  
> >
> > Here's what stat says:
> >
> > It's an executable file! Is that right??
>  
>  No.
>  
>  The driver makefile is broken.  It assumes that the misc subdirectory
>  already exists.
>   
It is broken in another way as well - depmod should be run after the
module is installed, not before. The depmod command updates the
modules table. If you do not do that after installing a new module,
the kennel and the module utilities will not know about the module.
A reboot will take care of this as well, because depmod is run at
bootup as part of the init scripts. The make file should probably
use "depmod -A" to save a bit of time.

Mikkel
-- 

  Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!

[Ben Lancaster]

On 4 Jun 2006, at 21:23, Mikkel L. Ellertson wrote:

>  Sam Varshavchik wrote:
> > Ben Lancaster writes:
> >
> >> Hey,
> >>
> >> I can't seem to install the standalone imon_vfd drivers from http://
> >> venky.ws:
> >>
> >> # make install
> >> depmod
> >> /usr/bin/install imon_vfd.ko /lib/modules/`uname -r`/misc
> >>
> >> Following that:
> >> # modprobe imon_vfd
> >> FATAL: Module imon_vfd not found.
> >>
> >> By my logic, shouldn't the install process have effectively copied
> >> the imon_vfd driver to a directory called misc within my running  
> >> kernel?
> >
> > Correct.
> >
> >>
> >> Here's what stat says:
> >>
> >> It's an executable file! Is that right??
> >
> > No.
> >
> > The driver makefile is broken.  It assumes that the misc subdirectory
> > already exists.
> >
>  It is broken in another way as well - depmod should be run after the
>  module is installed, not before. The depmod command updates the
>  modules table. If you do not do that after installing a new module,
>  the kennel and the module utilities will not know about the module.
>  A reboot will take care of this as well, because depmod is run at
>  bootup as part of the init scripts. The make file should probably
>  use "depmod -A" to save a bit of time.
>
>  Mikkel 
All in all, that's one broken makefile!

So a quick fix would be to remove the 'misc' file, create a directory  
in its place, and re-install, followed by 'depmod'?

Ben

[Mikkel]

Ben Lancaster wrote:
>  
>  So a quick fix would be to remove the 'misc' file, create a directory in
>  its place, and re-install, followed by 'depmod'?
>  
>  Ben
>   
Yes.

[Sam Varshavchik]

Ben Lancaster writes:

>  On 4 Jun 2006, at 21:23, Mikkel L. Ellertson wrote:
>  
> > Sam Varshavchik wrote:
> >> Ben Lancaster writes:
> >>
> >>> Hey,
> >>>
> >>> I can't seem to install the standalone imon_vfd drivers from http://
> >>> venky.ws:
> >>>
> >>> # make install
> >>> depmod
> >>> /usr/bin/install imon_vfd.ko /lib/modules/`uname -r`/misc
> >>>
> >>> Following that:
> >>> # modprobe imon_vfd
> >>> FATAL: Module imon_vfd not found.
> >>>
> >>> By my logic, shouldn't the install process have effectively copied
> >>> the imon_vfd driver to a directory called misc within my running  
> >>> kernel?
> >>
> >> Correct.
> >>
> >>>
> >>> Here's what stat says:
> >>>
> >>> It's an executable file! Is that right??
> >>
> >> No.
> >>
> >> The driver makefile is broken.  It assumes that the misc subdirectory
> >> already exists.
> >>
> > It is broken in another way as well - depmod should be run after the
> > module is installed, not before. The depmod command updates the
> > modules table. If you do not do that after installing a new module,
> > the kennel and the module utilities will not know about the module.
> > A reboot will take care of this as well, because depmod is run at
> > bootup as part of the init scripts. The make file should probably
> > use "depmod -A" to save a bit of time.
> >
> > Mikkel
>  
>  All in all, that's one broken makefile!
>  
>  So a quick fix would be to remove the 'misc' file, create a directory  
>  in its place, and re-install, followed by 'depmod'? 
Why don't you try it, and see what happens/

[Ben Lancaster]

On 4 Jun 2006, at 22:40, Sam Varshavchik wrote:

> > All in all, that's one broken makefile!
> > So a quick fix would be to remove the 'misc' file, create a  
> > directory  in its place, and re-install, followed by 'depmod'?
>
>  Why don't you try it, and see what happens/ 
Worked a charm.

Thanks for the assistance.