Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
toshiba_chromebook_2 [19.11.2014 13:07] – Pascal Suter | toshiba_chromebook_2 [14.08.2017 23:50] (current) – [Sound] Pascal Suter | ||
---|---|---|---|
Line 5: | Line 5: | ||
one thing though makes the notebook almost unusable.. chromeos :) at least for me.. it heavily depends on being connected to the internet and this at least in my case is not always given.. i often use my notebook in a datacenter at a customers where i can't simply plug it into the network and get access.. or on an airplane etc. plus despite being a gmail user i don't consier myself a heavy cloud user.. but i am a fulltime linux user and that's where the chromebook gets interesting.. it's one of the only notebooks available in stores that run a pre installed linux kernel.. and thanks to crouton it's quite easy to get a fully capable linux environment running on it.. i had this notebook running with standby working and everything an far less time than many regular windows notebooks.. | one thing though makes the notebook almost unusable.. chromeos :) at least for me.. it heavily depends on being connected to the internet and this at least in my case is not always given.. i often use my notebook in a datacenter at a customers where i can't simply plug it into the network and get access.. or on an airplane etc. plus despite being a gmail user i don't consier myself a heavy cloud user.. but i am a fulltime linux user and that's where the chromebook gets interesting.. it's one of the only notebooks available in stores that run a pre installed linux kernel.. and thanks to crouton it's quite easy to get a fully capable linux environment running on it.. i had this notebook running with standby working and everything an far less time than many regular windows notebooks.. | ||
+ | |||
+ | It turns out that the chrooted crouton wasn't satisfying after all as some stuff was not working and it was just too tedious to work with. so my chomebook sat in the cellar for a while. i recently researched again and found that the chromebook' | ||
+ | |||
+ | ====== The new solution ====== | ||
+ | in short, this is what i have done: | ||
+ | * disable bios flash lock | ||
+ | * flash [[https:// | ||
+ | * install ubuntu-gnome from a usb stick like on any other pc | ||
+ | * fix some issues | ||
+ | ===== bios flash lock ===== | ||
+ | in order to flash the bios you need to disable the hardware lock.. this is very simple once you know where to look :) .. simply remove the 8 screws on the underside of the chromebook, then remove the two rubber feet which are further away from the hinges and remove the two additional screws from there. open up the cover starting from the hinges and then remove the large silver shield that is held in place with 6 screws. underneath of screw nr. 5 you will see a silver washer-like sticker on the mainboard whichcovers two copper contacts. remove that sticker, put some electrical tape over those two half-circles on the board and reassemble everything. you can leave screw 5 away. | ||
+ | now your bios is no longer write protected and you can go ahead and follow the instructions on mrchromebox.tech | ||
+ | ===== fix some issues ===== | ||
+ | i wanted to use ubuntu-gnome, | ||
+ | ==== Sound ==== | ||
+ | the sound card in the toshiba chrombeook 2 with Bay Trail cpu is a max98090 chip which does not seem to be supported. | ||
+ | there is a [[https:// | ||
+ | |||
+ | i have installed his repo and then added some apt preferences to keep the kernel at an older version in order to stay with the patched one from aguirre: | ||
+ | |||
+ | # cat / | ||
+ | Package: linux-generic linux-headers-generic linux-image-generic linux-restricted-modules-generic | ||
+ | Pin: version 4.10.0-30 | ||
+ | Pin-Priority: | ||
+ | |||
+ | ==== Keyboard remapping ==== | ||
+ | the keyboard needs remapping in order to get the multimedia keys to work. | ||
+ | |||
+ | |||
+ | |||
+ | ====== The old solution ====== | ||
+ | here follows my original post from just after i bought the chromebook just for reference.. i wasn't happy in the end with this setup and never really used my chromebook.. | ||
+ | |||
+ | |||
there is a second possibility called chrubuntu which aims at installing a directly bootable ubuntu running a patched ubuntu kernel rather than the chromeos kernel.. however this solution did not work for the toshiba chromebook 2 at the moment of wrinting because right now this chromebook does not support legacy boot which wold be needed for that.. there is a possibility to boot into chrubuntu with a few commands in chromeos, however the author describing this solution did not get the sound card nor the standby functionality running so far and i don't see any advantage so far over runnign crouton which runs ubuntu in its own chroot environment with everyting working flawlessly.. | there is a second possibility called chrubuntu which aims at installing a directly bootable ubuntu running a patched ubuntu kernel rather than the chromeos kernel.. however this solution did not work for the toshiba chromebook 2 at the moment of wrinting because right now this chromebook does not support legacy boot which wold be needed for that.. there is a possibility to boot into chrubuntu with a few commands in chromeos, however the author describing this solution did not get the sound card nor the standby functionality running so far and i don't see any advantage so far over runnign crouton which runs ubuntu in its own chroot environment with everyting working flawlessly.. | ||
Line 29: | Line 63: | ||
* run crouton. at best you first look at the available command line options by running < | * run crouton. at best you first look at the available command line options by running < | ||
* this will install a ubuntu trusty 14.04 lts version with a basic gnome environment. as the script tells you you can now start your ubuntu by typing < | * this will install a ubuntu trusty 14.04 lts version with a basic gnome environment. as the script tells you you can now start your ubuntu by typing < | ||
- | ===== customize | + | ===== customize |
- | * crouton installs a very minimalistic gnome desktop. in order for it to look pretty and to have all the gnome tools you might have gotten used to you need to install additional packages. the easyest way to just get everyting that belongs to it you simply `apt-get install gnome` but that takes over 3GB of disk space and includes many games and stuff you probably don't ever need. | + | * crouton installs a very minimalistic gnome desktop |
- | instead you can run `apt-cache depends gnome` to see what packages get installed and then work your way from there to compile a list of what you really want installed on your system and what not. here's the list i've compiled: | + | |
- | < | + | |
- | * i also recommend to install update-manager-core | + | |
===== autostart crouton ===== | ===== autostart crouton ===== | ||
Line 41: | Line 72: | ||
* make sure the parameters are matching your needs and installation | * make sure the parameters are matching your needs and installation | ||
* touch a file called crouton.init in your downloads directory. | * touch a file called crouton.init in your downloads directory. | ||
+ | ===== simulate middle mouse button ===== | ||
+ | on a normal trackpad you would simply click the left and right mouse key at the same time to simulate a center key klick, but the chromebook has only one button. so this leaves us with the mac solution: tap the pad with one finger for a left click, two fingers for a right click and.. you might guess it.. three fingers for the center click... you can enable this by opening a command prompt and running this command < | ||
+ | chmod +x ~/ | ||
+ | </ | ||
===== sidenote: updating ubuntu ===== | ===== sidenote: updating ubuntu ===== | ||
- | if you need to update to a new releae simply use do-release-upgrade as youwould in any ubuntu installation.then log off and in chrome os run the crouton script to update its side of the installation: | + | if you need to update to a new releae simply use do-release-upgrade as youwould in any ubuntu installation.then log off and in chrome os run the crouton script to update its side of the installation: |
- | in oder to keep it that way even after the upgrad we need to rename the chroot name by running < | + | |
====== OpenVPN with config file ====== | ====== OpenVPN with config file ====== | ||
Line 61: | Line 95: | ||
script | script | ||
- | openvpn --config / | + | |
+ | | ||
end script </ | end script </ | ||
+ |