<div dir="auto"><div><div dir="auto">Yes, similar procedure I've followed.</div><div dir="auto">I didn't forget step 4. I actually always did `sudo make install_modules`. I'm not sure what's going on.<br></div><div dir="auto"><br></div><div dir="auto">Maybe it has sth to do with Ubuntu, that's why specifically mention I was using Ubuntu.</div><div dir="auto"><br></div><div dir="auto">Maybe I can try with some other distro. Probably Manjaro has better support for latest kernel releases.</div><div dir="auto"><br></div><div dir="auto"><span style="font-family:sans-serif">It's late here. I'll keep trying and let you know in case I figure out sth.</span><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Jan 30, 2017 1:27 AM, "Guru Das S" <<a href="mailto:gurooodas@gmail.com">gurooodas@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On 29 January 2017 at 16:19, Abel <<a href="mailto:akronix5@gmail.com">akronix5@gmail.com</a>> wrote:<br>
> I've posted a mail with the screenshot (waiting for moderation) when I try<br>
> to boot from make defconfig built kernel. Basically the kernel doesn't boot<br>
> because "Missing modules (cat /proc/modules; ls /dev " it says...It's the<br>
> same screen that appeared when I tried using make oldconfig pressing enter<br>
> for default values.<br>
><br>
> I tried using make localmodconfig but It again asks for many config params<br>
> that I don't know anything about.<br>
><br>
> Saludos,<br>
><br>
> Abel.<br>
<br>
</div>Hi Abel,<br>
<br>
The procedure I followed in order to compile, install and boot my<br>
custom compiled kernel is:<br>
<br>
1. Copy .config from existing distribution to kernel tree.<br>
<br>
2. Run make localmodconfig (I also got a bunch of prompts for<br>
parameters I had no idea about. I just pressed down Enter till the<br>
stream of options stopped flowing!)<br>
<br>
3. Run make -j<N> where N is a good number for your system.<br>
<br>
4. Run make modules_install<br>
<br>
5. Run make install (This ran update-grub for me at the end, though,<br>
which was convenient)<br>
<br>
That's it. I was able to boot into this newly compiled kernel via<br>
grub's selection menu upon rebooting. I think you may have missed<br>
doing Step 4 above.<br>
<br>
<br>
Guru Das Srinagesh.<br>
<div class="elided-text"><br>
<br>
><br>
> On 30 January 2017 at 01:11, Abel <<a href="mailto:akronix5@gmail.com">akronix5@gmail.com</a>> wrote:<br>
>><br>
>> Hi.<br>
>><br>
>> I just built using make defconfig and it, again, doesn't boot. Instead it<br>
>> displays the error that I've described before (sorry I forgot to attach the<br>
>> screenshot, I attach it here).<br>
>><br>
>> As I already stated, neither /boot/${uname -r} nor make oldconfig work for<br>
>> me, they both show the screen above.<br>
>><br>
>> Saludos,<br>
>><br>
>> Abel.<br>
>><br>
>> On 30 January 2017 at 01:08, Guru Das S <<a href="mailto:gurooodas@gmail.com">gurooodas@gmail.com</a>> wrote:<br>
>>><br>
>>> On 29 January 2017 at 15:32, 慕冬亮 <<a href="mailto:mudongliangabcd@gmail.com">mudongliangabcd@gmail.com</a>> wrote:<br>
>>> > Hello,<br>
>>> > If you want to reuse the config of current kernel, you can use<br>
>>> > `make oldconfig` to generate config file.<br>
>>> ><br>
>>> > --<br>
>>> > My best regards to you.<br>
>>> ><br>
>>> > No System Is Safe!<br>
>>> > Dongliang Mu<br>
>>> ><br>
>>> > 2017-01-29 18:24 GMT-05:00 Ozgur Karatas <<a href="mailto:mueddib@goosey.org">mueddib@goosey.org</a>>:<br>
>>> >><br>
>>> >> Hello,<br>
>>> >><br>
>>> >> you can get .config files in two ways, firstly get the existing<br>
>>> >> .config file<br>
>>> >> and compile to kernel.<br>
>>> >><br>
>>> >> $ cp /boot/config-x.x.x /bla/linux/.config<br>
>>> >><br>
>>> >> Second, use the generate command:<br>
>>> >><br>
>>> >> $ make defconfig<br>
>>> >><br>
>>> >> Regards,<br>
>>> >><br>
>>> >> ~Ozgur<br>
>>> >><br>
>>> >> 30.01.2017, 01:18, "Abel" <<a href="mailto:akronix5@gmail.com">akronix5@gmail.com</a>>:<br>
>>> >><br>
>>> >> Hi!<br>
>>> >><br>
>>> >> Where do you get the config file from? or do you generate it yourself?<br>
>>> >><br>
>>> >> I'm using xUbuntu 16.04 in a VM inside VMWare, following the<br>
>>> >> instructions<br>
>>> >> described in kernelnewbies wiki. (By the way, the download links to<br>
>>> >> the iso<br>
>>> >> images of Ubuntu don't work for me)<br>
>>> >><br>
>>> >> If I copy the latest config file in /boot, kernel 4.4.0, it starts to<br>
>>> >> ask me<br>
>>> >> many config parameters that I don't know what to answer. I tried to<br>
>>> >> press<br>
>>> >> always <enter> to set up the default parameters, but after compiling I<br>
>>> >> get<br>
>>> >> an error trying to boot from that kernel (see atachment).<br>
>>> >><br>
>>> >> I tried with make menuconfig and that seems to work, but it takes too<br>
>>> >> long<br>
>>> >> because it builds and includes many many drivers modules.<br>
>>> >> Yeah, I know I could navigate through the ncurses window and select<br>
>>> >> the<br>
>>> >> stuff I want and deselect what I don't want, but I'd rather prefer<br>
>>> >> just a<br>
>>> >> simple config file that builds and works and don't waste time in<br>
>>> >> understanding all the stuff that it's in there.<br>
>>> >><br>
>>> >> So, isn't there a way to get a simple config file just to develop<br>
>>> >> kernel<br>
>>> >> stuff for an Ubuntu image?<br>
>>> >> I've even gone to the kernel ppa sources for Ubuntu:<br>
>>> >> <a href="http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.5/" rel="noreferrer" target="_blank">http://kernel.ubuntu.com/~<wbr>kernel-ppa/mainline/v4.9.5/</a>; but it only<br>
>>> >> provides<br>
>>> >> a patch using the debian config files (which don't come from git<br>
>>> >> sources of<br>
>>> >> course).<br>
>>> >><br>
>>> >> I just want a config file, copy it to the kernel root code and<br>
>>> >> compile.<br>
>>> >><br>
>>> >> Greetings,<br>
>>> >><br>
>>> >> Abel<br>
>>> >><br>
>>> >><br>
>>> >> ______________________________<wbr>_________________<br>
>>> >> Kernelnewbies mailing list<br>
>>> >> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
>>> >> <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
>>> >><br>
>>> ><br>
>>> > ______________________________<wbr>_________________<br>
>>> > Kernelnewbies mailing list<br>
>>> > <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
>>> > <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
>>><br>
>>> Hi Abel,<br>
>>><br>
>>> To add to what Ozgur said, you may first copy the existing .config<br>
>>> file that comes along with your Linux distribution to your kernel<br>
>>> tree, and then use:<br>
>>><br>
>>> $ make localmodconfig<br>
>>><br>
>>> instead of defconfig. A quick Google search should tell you the<br>
>>> differences between the two - and from what I've read, localmodconfig<br>
>>> is preferred to defconfig.<br>
>>><br>
>>> Hope this helps.<br>
>>><br>
>>><br>
>>> Guru Das Srinagesh.<br>
>><br>
>><br>
><br>
</div></blockquote></div><br></div></div></div>