10/4/2023 0 Comments Virtualbox chromebookTo build the kernel on a Chromebook Pixel 2 with a 3.14 Kernel gcc 4.9 was required. chromeos/scripts/prepareconfig chromeos-intel-pineview More info on which flavor to choose see the kernel config info site mentioned above.īefore proceeding, don't forget to modify the script scripts/setlocalversion to remove the conditionals that append the text "-dirty" to the kernel version and package name see above. We have x86_64 so we setup the config for chromeos-intel-pineview. Look at which flavor you need for your chromebook. Search for CONFIG_ERROR_ON_WARNING=y and make it CONFIG_ERROR_ON_WARNING=n Just use your favorite text editor and edit "chromeos/config/nfig" in the kernel dir. This could be a problem with the gcc compiler I used. More info can be found on the chromium dev pagesįirst I had to run with -Werror, because I got one small problem when building some wifi module. Search for text "-dirty" and remark out the "case" and "if" structures that append the text "-dirty".īefore we start building we need to setup our kernel config. The simplest way to prevent this is to make a quick edit to script scripts/setlocalversion. This can cause problems when building the Virtualbox modules later. One may need to repeat the above steps a number of times, each time increasing the commit number in brackets, to get back to the appropriate version of the kernel source, and some trial and error may be needed to find your matching version.īecause we're not building the latest version of the source in the git repository, building a package from an older version will result in a package and installed version appended with "-dirty". If the version from the uname command above does not match what is displayed, and is indeed a later version, then one can do the following to download an earlier version: $ git reset -hard origin/chromeos-3.18 First, determine the kernel version for the source we just downloaded: $ cd kernel Then we may need to download the correct revision of the kernel source from the git repository, if the downloaded source version doesn't match that of what we're currently running, by rolling back to a previous commit. $ cd ~įor example, may be 3.18 or some other value see the value returned by uname above to determine this. Then clone the kernel branch chromeos- to our home folder. Next, we need to determine the version of the kernel we're currently running. $ sudo apt-get install git-core make kernel-package bc Note: All the shell commands on this page need to be done in the shell of your chroot if not specified otherwise. I did this on a precise with xfce chroot, but it should also work on others. On the HP chromebook 14 I have kernel 3.8.11 so I need the chromeos-3.8 branch in the kernel repo.įirst we need some tools installed in our chroot. NOTE: Mostly you will need the kernel repo. Branches can be identified by chromeos- version where version is your kernel version. There are two git repos kernel and kernel-next where the kernel sources can be found, but you have to know which branch you're on. You can post any problems by creating a new issue on divx118/crouton-packages git Getting the kernel source NOTE: If you are just interested in installing kernel headers and virtualbox you can go and read this README.md It is a ppa with most of the kernel versions and architectures for chromebooks. In the section below we explain how you can boxodo that. However there are no kernel headers available to install that work with the kernel of your chromebook. Just be sure you clone the right kernel source for your device.įor installing virtualbox we need a kernel headers package to compile the virtualbox modules. However, it should work for any x86 chromebook.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |