Kernel 2.6 config and modules, modules, modules...

[Crocodil]

Hi everybody!!

I've decided to give Gentoo a try, untill now I were using Mandrake, SuSe and lately Fedora but I'm pretty much a newbie...

I started last Saturday and with various problems got into one of the last stages - configuring and compiling kernel, that is I'm using the gentoo-dev-sources.

I have a couple of questions:

1. How to decide which options should be compiled into kernel and which should be made modules? I would be very grateful for any suggestions and/or links to tutorials/documentation

2. What kernel config (regarding agpgart and DRM) would be apriopriate to get OpenGL supoort with ATI Radeon 9200?

3. I've already compiled the kernel a couple of times... When I compile the kernel as a monolith, everything is OK, the system boots and works But when I try to make a kernel with modules I run into problems... The system doesn't start, there aren't even any error messages.

How am I to know which modules should be added to /etc/modules.autoload.d/kernel-2.6 ?? All of them?

I've always thought that it wasn't up to the user to decide which modules should be loaded but to the "autoloading" If I'm wrong, could somebody please explain how does autoloading work?

I'm sorry if the questions are very "newbish" and please excuse my bad English...

Best regards,

Crocodil

[NeddySeagoon]

Crocodil,

1 and 3. You should compile in (say "Y") to any modules you need to boot. The root filesystem driver is a good example. If its not compiled in, the kernel cannot mount the filesystem to read the module to mount the file...... Another is any drivers for hardware required for booting. e.g. a Serial ATA dirver if you need to boot from it but not network card drivers.

Everything else should be modules, particularly when you start. You can compile and load modules without rebooting, you can unload modules then reload them with different parameters without rebooting. Diagnostics are easier.

2. You aren't ready for an answer to this question yet. Build X, make it work with the window manager of your choice and the basic VGA or VESA drivers. After it works make it faster.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[peterton]

The most important things are filesystem and ide/scsi drivers which need to be built in to read the root file system. for me that would be reiserfs and intel piix.
Don't forget to run make modules_install after make.
In /etc/modules.autoload.d/kernel-2.6 you'll only have to put what's not loaded by hotplug (rc-update add hotplug default). It takes a little figuring out which ones don't. I have ACPI support as modules and have to load them manually.
Basically you'll have to ask youself, in order to access all modules and continue loading, what will I need? How will you get to those modules. I.e. proper CPU, IDE/SCSI, file system, input/output (/dev/pts for example).
Or give genkernel a try. I never did but it might get you started.

[Crocodil]

Hi

Thank you for your answers

This means "back to the drawing board" for me I guess... Well, I do like challenges

Thanks again

Regards,

Crocodil.

PS. Maybe you could paste your "autoload" files as examples?

[peterton]

/etc/modules.autoload.d/kernel-2.6

[Crocodil]

Hi peterton

Thank you for your help

I must say I've never heard of hotplug before I've searched the forums and I think I have a "general understanding" of what it is for But could you please explain it in simple words?

Is "emerge hotplug" all I have to do? Do I have to enable anything in kernel? I remember disabling "hotplug" option because I'm not planning on using USB...

BTW. I'm sorry for all the questions. What is the policy of this forum? Are newbie questions alright or should I shut up and try to do everything by myself?

Best regards,

Crocodil.

[NeddySeagoon]

Crocodil,

My /etc/modules.autoload