AW: AW: modconf doesn't show drivers

["Yildiz, Murat" <murat.yildiz@atosorigin.com>]

Oh sorry ,
of course I did "make modules_install"....But I remember somethinlike
"nothing found" and "leaving directory".
As I said the directory 2.4.19 was created under /lib/modules but still I
cannot see any drivers info within modconf.

Murat

-----Ursprüngliche Nachricht-----
Von: Russell Shaw [mailto:rjshaw@iprimus.com.au]
Gesendet: Mittwoch, 19. Februar 2003 11:40
An: debian-user@lists.debian.org
Cc: debian-user@lists.debian.org
Betreff: Re: AW: modconf doesn't show drivers


Yildiz, Murat wrote:

>On Tue, Feb 18, 2003 at 01:33:16PM +0100, Yildiz, Murat wrote:
>  
>
>>I have woody 3.0 with kernel 2.4.19 self-compiled and now want to load a
>>kernel module but when I run modconf no package is being shown.
>>I have checked /lib/modules/2.4.19  , it exist.Where does modconf read
>>available modules information?
>>    
>>
>
>After a quick look at modconf, it looks like it would get its module
>listings by looking through all the directories in /lib/modules/2.4.19,
>and finding *.o.  Are modules in /lib/modules/2.4.19?
>
>  
>
> Hi,
> I have run "make modules" and "make modules-install" and the
> /lib/modules/2.4.19 was created but with an empty modules.dep file.I think
> it is reading the drivers information from modules.dep, but it is empty.

Should use modules_install, not modules-install.
I think modules.dep is generated by "make modules_install".
This generates
/lib/modules/$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
which comes from the kernel top-level Makefile:

VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 20
EXTRAVERSION = <put your own version here>
KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)




-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org