Ralf Mardorf wrote: > rosea grammostola wrote: > >> There is. But I'm wondering if it's different when I just build for my >> own system or for 'all' pc's. >> How do I know which packages I should have installed for the kernel >> build, to support as much hardware as possible... >> > > For the kernel build it's not important what packages you have got > installed. Important is, that you keep the CPU type at x86 or x86_64 > instead of optimizing it e.g. to amd64. It's also important that you > don't fit the number of CPUs to your hardware, keep it at e.g. 512 > instead of using 2. This issues, timer resolution, rt support etc. is > set by the config file. Copy /boot/config-2.6.29-1-multimedia-amd64 to > your source directory and rename it to .config, then load it when you > run "# make menuconfig", if needed, IIRC I didn'd need to copy the > config file. For the build you might need: > fakeroot > gcc > kernel-package > make > libncurses5-dev > Btw. the patch command has got a --dry-run option. > _______________________________________________ > >
Ok, I did manage to build a kernel. But I had to force install it cause it shared some drivers with the alsa packages. Do you normally build the alsa packages with or against the kernel or something? Regards, \r _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
