![]() I tried again with a VM with more resources (8GB RAM, 4 cpu cores) and it was done within about 30 minutes. In my case the Linux kernel build took several hours and then ran out of space on my virtual machine. It really depends on the computer/resources you are using and how much you are compiling. To get a feel for how long the build time might be, check out these here and here. Installing dwarves did the trick and the rest of the build went ok. Thankfully there was a stackoverflow question with an answer – install the ‘ dwarves‘ package. This failed with an error that ‘pahole is not available’. This seemed to do the trick, although I also needed to update the config for No rule to make target 'debian/canonical-certs.pem', needed by 'certs/x509_certificate_list'įrom this link it looks like I need to update the config to set (In retrospect, I may have been better starting from the same kernel version as my distro (lubuntu 20.04) so I wouldn’t see so many ‘NEW’ config options.) Fixing Certs IssuesĪfter building for a while, I got an error: In my case I initially copied the configuration from an Ubuntu build, which is likely to be fairly generalised and include more than a more bespoke option might need. This page actually suggests some other ways of setting up your config including automatically accepting defaults on new configuration options or only building a minimal version to speed up build time. Lots of them seemed to be about including compatibility with various hardware. Having no idea what I was doing, I just accepted the defaults for each question until the build got started. I think the config file I used (from lubuntu 20.04) was quite out of date compared to the kernel as there were many questions not configured and appeared as ‘NEW’. config file, it will complain that there isn’t one there. This appends an extra label to the name of any kernel built which helps avoid name clashes. It is also a good idea to update CONFIG_LOCALVERSION in the new config. Updating the build configurationĪs per the guide, I found a kernel config file in /boot/and copied it to. If you keep having problems, you could use the GitHub mirror if you just want to be able to build recent-ish kernel code. This still didn’t work and after mucking about with pinging and checking IP addresses I found this solution to temporarily change the nameserver to 8.8.8.8.įinally, I came across this page which mentions there had been issues with , which could be related to the same problem Pinging the IP address of (via this website) gave the same error. This still was not working, so tried pinging in the virtual machine and got the error ‘Temporary failure in name resolution’. Name Resolution Errorįatal: unable to look up (port 9418) (Temporary failure in name resolution)Īnd also tried to change to https version of origin (rather than ‘git:’ in the guide): This was fixed by upping the amount of memory I gave it. Read more about how much space the kernel requires for building.Īs I was running a virtual machine, i think I may have had the issue that it goes into pause mode when it it struggling with memory. I didn’t follow the guidance on sensible virtual disk space and ran out of space on my first attempt. They weren’t joking when they said it took over 5GB! The guide recommends cloning the repository on a fast, stable, unlimited connection. Cloning the Kernel Repo Performance Issues This might be something I build up to, but realistically I didn’t think I would be submitting patches any time soon, so I skipped the email setup. The guide I followed is actually for submitting patches. I used a lubuntu install with 10GB virtual hard disk initially, but upped that to 20GB when I ran out of space cloning the repo. Some of the later steps are quite resource intensive, so set your virtual machine memory, CPU and Virtual Disk relatively high if you can spare it on your host machine. ![]() I used VirtualBox rather than VMWare suggested in the guide, but don’t think didn’t encounter many differences. I followed this guide and while it mostly made sense there were a few areas that I found less clear or had unexpected errors. I was interested to see how to do a Linux Kernel Build from the source code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |