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