Harry Putnam wrote: > Nikos Chantziaras <[email protected]> writes: > > >> Harry Putnam wrote: >> >>> Nikos Chantziaras <[email protected]> writes: >>> [...] >>> >>> >>>>>> Well, my bit of wisdom here: Don't use modules. Do a "make >>>>>> menuconfig", disable everything you don't need, and compile >>>>>> everything you need in-kernel instead of as a module. >>>>>> >>>>> I'd say the "disable everything you don't need" part is what Harry's >>>>> mail is all about. >>>>> >>>> Well, finding out what every installed module does isn't going to >>>> help anyway. I'd start with only the modules currently used after a >>>> fresh boot (lsmod). If you compile those in-kernel, it will boot. >>>> Everything else can be tweaked later. >>>> >>> Yeah, I talked about that in OP. But the only kernel I've got working >>> at the moment is a genkernel and it installs 80+ modules. >>> >> The way I do it, is to simply know what hardware is in the machine >> (dmesg, lspci and hwinfo for things I'm not sure about) and look for >> it in the kernel configuration. For the few modules that remain where >> I don't know what they do, I just google their names. The important >> stuff is just the PATA/SATA controller, SCSI disk support and >> keyboard/mouse though. The rest I add later. >> > > Sounds like a plan... thanks. Maybe eventually some of that output > will be a little easier. Here I just mean dmesg... lspci is easy > enough. > > I must need some specific package to see hwinfo. Its unknown > to bash here. > > > >
emerge hwinfo should help with that. Dale :-) :-)
