Re: [gentoo-user] Re: kernel config hell

2008-12-28 Thread Dirk Heinrichs
Am Samstag, 27. Dezember 2008 16:48:19 schrieb Harry Putnam: Dirk Heinrichs dirk.heinri...@online.de writes: What could help you here is a make xconfig. It's similar to make menuconfig but has a nice QT user interface. I would recommend to browse through it once and look at the help

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Nikos Chantziaras
Harry Putnam wrote: Summary of request for help: Are there hardcore kernel builders in the house who can steer me to a faster way of figuring out what the installed modules do... for sure. Well, my bit of wisdom here: Don't use modules. Do a make menuconfig, disable everything you

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Dirk Heinrichs
Am Samstag, 27. Dezember 2008 20:27:37 schrieb Nikos Chantziaras: Harry Putnam wrote: Summary of request for help: Are there hardcore kernel builders in the house who can steer me to a faster way of figuring out what the installed modules do... for sure. Well, my bit of wisdom

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Nikos Chantziaras
Dirk Heinrichs wrote: Am Samstag, 27. Dezember 2008 20:27:37 schrieb Nikos Chantziaras: Harry Putnam wrote: Summary of request for help: Are there hardcore kernel builders in the house who can steer me to a faster way of figuring out what the installed modules do... for sure. Well, my

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Harry Putnam
Nikos Chantziaras rea...@arcor.de 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

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Nikos Chantziaras
Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de 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

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Hung Dang
I would suggest to follow the Gentoo handbook first. Leave all options you are not sure as default, using lspci to find out more about your hardware specifications. From my experiences I will make sure that the kernel is bootable first then adapt it to hardware later. Use modules or not is your

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Harry Putnam
Nikos Chantziaras rea...@arcor.de writes: Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de 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

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread kashani
Hung Dang wrote: I would suggest to follow the Gentoo handbook first. Leave all options you are not sure as default, using lspci to find out more about your hardware specifications. From my experiences I will make sure that the kernel is bootable first then adapt it to hardware later. Use

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Cocoy Dayao
back in the day, this was why i went gentoo in the first place. i needed a better scheduler and compiling a new kernel off red hat for instance almost always broke other stuff. gentoo made my life easier. On 12 28, 08, at 7:32 AM, kashani wrote: I'll second what Hung said, getting your

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Jerry McBride
On Saturday 27 December 2008 10:48:19 am Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de 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.

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Dale
You may also want to try lspci -v. It shows you what modules the hardware uses and it should be able to boot with those at least. Example: 00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ABIT Computer Corp. Device 1c02

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Dale
Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de writes: Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de 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

[gentoo-user] Re: kernel config hell

2008-12-27 Thread Harry Putnam
Dale rdalek1...@gmail.com writes: You may also want to try lspci -v. It shows you what modules the hardware uses and it should be able to boot with those at least. Example: Well son-of-a-gun... that is nice. Thanks

Re: [gentoo-user] Re: kernel config hell

2008-12-27 Thread Dale
Harry Putnam wrote: Dale rdalek1...@gmail.com writes: You may also want to try lspci -v. It shows you what modules the hardware uses and it should be able to boot with those at least. Example: Well son-of-a-gun... that is nice. Thanks Yea, thanks to whoever mentioned it