![]() ![]() #If all is well, everything in /lib/modules is umounted so we can install our two deb files. ![]() #You can now logout and login again in your chroot to see if the script rc.local works. #Also be sure to change the execution bit Loaded=$( cat /proc/modules|grep -o vboxdrv ) || loaded="empty"Įcho 1 > /sys/module/lsm/parameters/module_lockingĬhmod 0400 /sys/module/lsm/parameters/module_locking # disable module locking and try to load vboxdrvĬhmod 0666 /sys/module/lsm/parameters/module_lockingĮcho 0 > /sys/module/lsm/parameters/module_locking # umount bindmounts /lib/modules from enter-chrootįor m in `cat /proc/mounts | /usr/bin/cut -d ' ' -f2 | grep /lib/modules| grep -v "^/$" ` do # In order to enable or disable this script just change the execution # Make sure that the script will "exit 0" on success or any other # This script is executed at the end of each multiuser runlevel. #Create the following /etc/rc.local or add this to your /etc/rc.local if you already have one. #We also need to disable module_locking for loading the vboxdrv kernel modules and actually load the modules. #Before we can install we need to umount /lib/modules which is bind mounted in enter-chroot. If you followed #this guide to the letter it should be your home dir. #After it is finished without errors you should now see two *.deb files in the directory above kernel-next. $ make-kpkg -rootcmd fakeroot kernel_image kernel_headers #Now we can start building kernel_headers and kernel_image. #Building kernel headers and kernel image chromeos/scripts/prepareconfig chromeos-intel-pineview #More info on which flavor to choose see the kernel config info site mentioned 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-next dir. This could be a problem with the gcc compiler I used. #First I had to run with -Werror, because I got one small problem when building some wifi module. More info can be found on the chromium dev pages ![]() #Before we start building we need to setup our kernel config. #Cloning the kernel branch chromeos-3.8 to our home folder. $ sudo apt-get install git-core make kernel-package Note: All the shell commands on this page need to be done in the shell of your chroot(ie inside ubuntu) if not specified otherwise. I did this on a precise with xfce chroot, but it should also work on others. Note: Older devices will use "kernel" instead of "kernel-next".įirst we need some tools installed in our chroot. On the HP chromebook 14 I have kernel 3.8.11 so I need the chromeos-3.8 branch. Branches can be identified by chromeos-version where version is your kernel version. There's a git repo where the kernel sources can be found, but you have to know which branch you're on. In the section below we explain how you can do 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. This guide is tested on an HP chromebook 14 which has an Intel Celeron 2955U CPU. Ie version: VirtualBox 4.3.14 (released July 15th 2014) build kernel headers as per this diff method: NB: do this ALTERNATIVE INSTEAD(it solves multi reboots on vagrant up)ġ. Only pasted here so I can be sure I will always have it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |