You are not logged in.
Pages: 1
I'm customizing my kernel and trying to find these modules in menuconfig
cdrom.ko
i2c-algo-bit.ko
libata.ko
mperf.ko
snd-page-alloc.ko
usb-common.ko
usbcore.ko
I just can't find them anywhere. Please help me.
Offline
You can use F8 to search and look at /proc/config.gz for your current config. For example, i2c-algo-bit is I2C_ALGOBIT. Also, try searching: http://cateee.net/lkddb/
Steven [ web : git ]
GPG: 327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com
Offline
You can use F8 to search and look at /proc/config.gz for your current config
sry for noobishness, but F8 doesn't seem to work in menuconfig, and I do not have config.gz in /proc directory (I'm not arch user)
Offline
(I'm not arch user)
Well, which distribution are you using??
Offline
Use nconfig instead of menuconfig.
Steven [ web : git ]
GPG: 327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com
Offline
Use nconfig instead of menuconfig
ok it's working, but it seem that F8 in nconfig is exactly the same that "/" in menuconfig. It searches the exact parameter name, and modules often have different names. So the problem is how to match module name to parameter name in menuconfig/nconfig.
I'm using debian
Offline
I'm using debian
This forum is meant for Arch Support Only.
Debian forums:
Is where you should be.
Offline
My question doesn't concern any specific distro but configuring linux kernel in general, and the answer would be equally useful for arch users.
I'm not debian fanboy but just regular linux user gathering knowledge and experience. Debian match my current state of knowledge. When it'll be improved I'll move to more advanced distros.
I've posted it already in debian forum but didn't receive the answer.
I chose to post it here because I thought that there's a lot of advanced competent and helpful linux users here.
Last edited by junex (2013-02-21 19:01:52)
Offline
Theres always LinuxQuestions.org.
Offline
So you know the answer but don't tell me cause I'm not using arch?
Offline
Another way to get the modules you need, in Arch and adapt the instructions for other distributions, is "make localmodconfig":
https://wiki.archlinux.org/index.php/Mo … om_kernels
That will select only the modules that are loaded at the time you execute the command. So, your cdrom.ko and such would be automatically marked if they were loaded - you had booted into a full kernel and that loaded it as part of the boot process.
The catch with localmodconfig is that everything you might need must be loaded at the time you execute the command or it will not be built into your custom kernel. A non-obvious example of this is the character encoding for the NTFS file-system. If you need that then make sure you have an NTFS volume, USB or otherwise, mounted when you execute localmodconfig. Then it will be built into your resulting kernel, otherwise it will not.
Offline
Thank you
I read about it earlier here:
http://stackoverflow.com/questions/1147 … ell-script
but author mentioned this:
Its important to know that it does not always work flawlessly. So you should tweak your config further using make menuconfig. You will see some modules are still marked to be built which is in reality unnecessary for your system
So I thought there's maybe more accurate way to do it manually.
In menuconfig's help descriptions every parameter that can be compiled as a module have something like this:
This support is also available as a module. If so, the module will be called XXXX
I think the problem is that F8 or "/" can search only the exact name of kernel parameters and not the whole content of help descriptions (so also the module names).
So it's not always obvious where to find parameter that enables module XXXX.ko
Offline
I'm customizing my kernel and trying to find these modules in menuconfig
cdrom.ko
i2c-algo-bit.ko
libata.ko
mperf.ko
snd-page-alloc.ko
usb-common.ko
usbcore.koI just can't find them anywhere. Please help me.
Of course part of using Linux is learning it, constantly.
I use menuconfig almost exclusively, as it doesn't depend on any distro. I think just the dialog package.
Simply take all or part of the module filename, change to uppercase string you think it would be, and search via grep.
$ grep _ATA= .config
CONFIG_SCSI_SAS_ATA=y
CONFIG_ATA=y
As simple as that.
I also suggest when using menuconfig, to select 'help' while an option is highlighted. It shows you what it corresponds to in the .config file. This is also true of the other menu-based config options.
--------------------------The only wasted day is one in which you learn nothing.--------------------------
Offline
Pages: 1