* Rebuild kernel so complicated?
@ 2013-12-07 11:57 乃宏周
2013-12-08 18:25 ` Sudip Mukherjee
2014-03-14 0:14 ` Razvan Ghitulete
0 siblings, 2 replies; 3+ messages in thread
From: 乃宏周 @ 2013-12-07 11:57 UTC (permalink / raw)
To: kernelnewbies
AFAIK, rebuild the kernel should follow those steps at least:
- *copy /boot/system-$(uname -r).map to ${kernel_src}*
- *copy /boot/config-$(uname -r) to ${kernel_src}*
- *cd ${kernel_src}*
- *make menuconfig*, save config(If I don't wanna change anything for
test).
- *make -j9 bzImage.*
- *override /boot/vmlinuz-$(uname -r) with
${kernel_src}/arch/x86/boot/bzImage*
Maybe those steps contains some typo or has some different paths. Buts the
point is I don't change any features from original setting, I just copy my
system.map and config to kernel source's one and rebuild the kernel(should
be the same with mine).
When I override new kernel and reboot, It just hanged, no any message print
out(No Oops, No panics). But if I do those steps with
this<http://it.livekn.com/2013/01/compile-kernel.html>,
everything goes fine. I just don't know the differences between the
standard way and debian's way. Is ubuntu abnormal ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131207/010fa902/attachment.html
^ permalink raw reply [flat|nested] 3+ messages in thread* Rebuild kernel so complicated? 2013-12-07 11:57 Rebuild kernel so complicated? 乃宏周 @ 2013-12-08 18:25 ` Sudip Mukherjee 2014-03-14 0:14 ` Razvan Ghitulete 1 sibling, 0 replies; 3+ messages in thread From: Sudip Mukherjee @ 2013-12-08 18:25 UTC (permalink / raw) To: kernelnewbies On Dec 8, 2013 2:27 AM, "???" <naive231@gmail.com> wrote: > > AFAIK, rebuild the kernel should follow those steps at least: > copy /boot/system-$(uname -r).map to ${kernel_src} > copy /boot/config-$(uname -r) to ${kernel_src} > cd ${kernel_src} > make menuconfig, save config(If I don't wanna change anything for test). > make -j9 bzImage. > override /boot/vmlinuz-$(uname -r) with ${kernel_src}/arch/x86/boot/bzImage i think you have missed the step to create the initrd image and try updating grub after all the steps are over. Regards Sudip -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131208/34c4623a/attachment.html ^ permalink raw reply [flat|nested] 3+ messages in thread
* Rebuild kernel so complicated? 2013-12-07 11:57 Rebuild kernel so complicated? 乃宏周 2013-12-08 18:25 ` Sudip Mukherjee @ 2014-03-14 0:14 ` Razvan Ghitulete 1 sibling, 0 replies; 3+ messages in thread From: Razvan Ghitulete @ 2014-03-14 0:14 UTC (permalink / raw) To: kernelnewbies On 12/07/2013 12:57 PM, ??? wrote: > AFAIK, rebuild the kernel should follow those steps at least: > > * /copy /boot/system-$(uname -r).map to ${kernel_src}/ > * /copy /boot/config-$(uname -r) to ${kernel_src}/ > * /cd ${kernel_src}/ > * /make menuconfig/, save config(If I don't wanna change anything > for test). > * /make -j9 bzImage./ > * /override /boot/vmlinuz-$(uname -r) with > ${kernel_src}/arch/x86/boot/bzImage/ > I might be in the wrong...but why are you copying your running kernel system.map to the src dir? AFAIK the system.map is generated during the build process. Also you should consider building the modules and installing them. Most probably your distro modules will have some problems with a custom built kernel(even though you have the same config). -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20140314/caad0ed1/attachment.html ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-03-14 0:14 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-12-07 11:57 Rebuild kernel so complicated? 乃宏周 2013-12-08 18:25 ` Sudip Mukherjee 2014-03-14 0:14 ` Razvan Ghitulete
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).