Do I really have to follow those steps like editing grub.. I could see that those changes are aleady done in menu.lst also this doesn't mention of anything like creating initrd .. http://kernelnewbies.org/FAQ/KernelCompilation following is updated grub configuration.. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/sda1 # initrd /boot/initrd-[generic-]version.img #boot=/dev/sda default=1 timeout=0 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.35.5) root (hd0,0) kernel /boot/vmlinuz-2.6.35.5 ro root=UUID=2eafbf21-6f1e-4fd9-b276-c207d8bd612c rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk rhgb quiet initrd /boot/initramfs-2.6.35.5.img title Fedora (2.6.33.3-85.fc13.i686) root (hd0,0) kernel /boot/vmlinuz-2.6.33.3-85.fc13.i686 ro root=UUID=2eafbf21-6f1e-4fd9-b276-c207d8bd612c rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk rhgb quiet initrd /boot/initramfs-2.6.33.3-85.fc13.i686.img - Rahul Ruikar On 22 September 2010 22:15, Adam M. Dutko <dutko.adam@xxxxxxxxx> wrote: > I believe you missed step #6 an step #7. > > On Wed, Sep 22, 2010 at 12:35 PM, Rahul Ruikar <rahul.ruikar@xxxxxxxxx> > wrote: >> >> Adam, >> >> I Followed this link >> http://www.cyberciti.biz/tips/compiling-linux-kernel-26.html >> >> in Summary >> >> make menuconfig ( here I enabled many option included debug related ) >> make >> make modules_install ( with root ) >> make install ( with root ) >> >> while compilation of other kernels these 4 steps worked for me. >> Am i missing something in compilation process... >> and yes important thing.... can we see compilation logs / error logs >> ??? if yes then please help me to locate this one.. >> >> >> - Rahul Ruikar >> >> >> >> >> >> On 22 September 2010 21:57, Adam M. Dutko <dutko.adam@xxxxxxxxx> wrote: >> > Seems you didn't compile the code into the kernel and selected them as >> > modules. I'm not familiar with the install.sh script. I usually do a >> > lot >> > by hand. Did you regenerate your ramdisk? >> > >> > On Wed, Sep 22, 2010 at 12:09 PM, Rahul Ruikar <rahul.ruikar@xxxxxxxxx> >> > wrote: >> >> >> >> Hi All, >> >> >> >> I compiled kernel 2.6.35.5 on Fedora 13 ( laptop ) i got following >> >> errors. >> >> After completing installation I boot up system with this kernel but >> >> sound is not working ..that is >> >> >> >> [root@Ganesha linux-2.6.35.5]# make install >> >> sh /home/rahul/Downloads/stable/linux-2.6.35.5/arch/x86/boot/install.sh >> >> 2.6.35.5 arch/x86/boot/bzImage \ >> >> System.map "/boot" >> >> ERROR: modinfo: could not find module snd_hda_codec_idt >> >> ERROR: modinfo: could not find module snd_hda_intel >> >> ERROR: modinfo: could not find module snd_hda_codec >> >> ERROR: modinfo: could not find module snd_hwdep >> >> ERROR: modinfo: could not find module snd_seq >> >> ERROR: modinfo: could not find module snd_seq_device >> >> ERROR: modinfo: could not find module snd_pcm >> >> ERROR: modinfo: could not find module snd_timer >> >> ERROR: modinfo: could not find module snd >> >> ERROR: modinfo: could not find module soundcore >> >> ERROR: modinfo: could not find module snd_page_alloc >> >> -- >> >> To unsubscribe from this list: send the line "unsubscribe >> >> kernel-janitors" >> >> in >> >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >> > > > -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html