On Tue, 2004-04-13 at 11:05, Christopher Ness wrote: > On Tue, 2004-04-13 at 10:56, Etanisla Lopez-Ortiz wrote: > > Morning all, > > > > Tonight I'll be trying the kernel compile again, but before I do, I want to > > bounce the changes off you wonderful, helping people. > > > > -1: Start with fresh install of FC1 (2.4.22-1.2115) > > 0: Insert desired version number where x.x.x is present. > > 1: Get desired kernel and extract it. > > 2: "mv /scratch/directory/linux-x.x.x /usr/src" > > 3: "cd /usr/src/linux-x.x.x" > > 4: Copy .config from old kernel to /usr/src/linux-x.x.x > > Since first compile since initial install, use config file found in > > /boot. > > 5: "make oldconfig" (Keep the stuff that works, and only answer new > > questions) > > 6: "make xconfig" (Make sure kernel options for Prism54 are set properly) > > 7: "make dep" > > 8: "make clean" > > 9: "make bzImage" > > 10: "cp /arch/i386/boot/bzImage /boot/vmlinuz-x.x.x" > > 11: "ln -s /boot/vmlinuz-x.x.x /boot/vmlinuz-x.x.x-new-kernel" > > 12: "make modules" > > 13: "make modules_install" > > 14: "make install" > > 15: Edit /etc/rc.sysinit and change '/proc/sys/kernel/modprobe' to > > /sbin/modprobe'. > > 16: "shutdown -r now" > > 17: After rebooting, and selecting new kernel option, type "uname -r" to > > verify the new kernel is running. > > > > So, whaddya think? > > --Etanisla > > Good Morning Etanisla, > > Looks good. Some thoughts. > > I prefer to use the `make menuconfig` instead of pulling up in X you can > run this from the CLI. I find it a little faster once you get used to > reading it - but that's a personal preference. > > Just be sure to tell people that this is for a 2.4.x kernel series. > 2.6.x is a little different in that you don't need to do the `make dep` > in fact your compile line for a 2.6 basically comes down to this: > > make && make modules_install && make install > > The `&&` between commands means that the next command will be started > iff the previous command exits without errors. Use `;` between commands > if you want it to run the next command no matter what happens. > > You may not need to do `make modules_install` if you make a monolithic > kernel without modules. > > Cheers, > Chris One more item make -j # > /dev/null allows parallel compiling of components where # is the number of forks. I use about 1 per 64 meg allowing for overhead, and dumping messages also speeds the process and you still get warnings and errors.-- jludwig <wralphie@xxxxxxxxxxx>
