1 |
Nikos Chantziaras <realnc@×××××.de> writes: |
2 |
|
3 |
> Harry Putnam wrote: |
4 |
>> Nikos Chantziaras <realnc@×××××.de> writes: |
5 |
>> [...] |
6 |
>> |
7 |
>>>>> Well, my bit of wisdom here: Don't use modules. Do a "make |
8 |
>>>>> menuconfig", disable everything you don't need, and compile |
9 |
>>>>> everything you need in-kernel instead of as a module. |
10 |
>>>> I'd say the "disable everything you don't need" part is what Harry's |
11 |
>>>> mail is all about. |
12 |
>>> Well, finding out what every installed module does isn't going to |
13 |
>>> help anyway. I'd start with only the modules currently used after a |
14 |
>>> fresh boot (lsmod). If you compile those in-kernel, it will boot. |
15 |
>>> Everything else can be tweaked later. |
16 |
>> |
17 |
>> Yeah, I talked about that in OP. But the only kernel I've got working |
18 |
>> at the moment is a genkernel and it installs 80+ modules. |
19 |
> |
20 |
> The way I do it, is to simply know what hardware is in the machine |
21 |
> (dmesg, lspci and hwinfo for things I'm not sure about) and look for |
22 |
> it in the kernel configuration. For the few modules that remain where |
23 |
> I don't know what they do, I just google their names. The important |
24 |
> stuff is just the PATA/SATA controller, SCSI disk support and |
25 |
> keyboard/mouse though. The rest I add later. |
26 |
|
27 |
Sounds like a plan... thanks. Maybe eventually some of that output |
28 |
will be a little easier. Here I just mean dmesg... lspci is easy |
29 |
enough. |
30 |
|
31 |
I must need some specific package to see hwinfo. Its unknown |
32 |
to bash here. |