![]() ![]() The laptop must have 4GB RAM (up from 2GB), 16GB storage, an Intel or AMD x86 64-bit processor, full BIOS access, and ideally have been manufactured after 2010 (previously 2007). Like standard ChromeOS, ChromeOS Flex’s system requirements are fairly minimal, though they have become more stringent compared to before. The major changes: You now need 4GB RAM (up from 2GB), and a processor manufactured after 2010. Some of the ebuilds have been modified to allow usage on CrOS, and some are slightly behind the latest version for compatability reasons.ChromeOS Flex’s system requirements have increased, compared to its previous incarnation as CloudReady. ebuilds, DO NOT replace them with upstream Gentoo's, instead modify them in place. It is annoying and more work, I know, and might dissuade newbies from trying ChromiumOS, but there is no way around this. If I were to do that, after just a couple of people installing and signing in on my builds, the servers would refuse any more requests. Public ones used to be available, but now private ones are needed, and I can't just share my own, because there is a quota on their usage to prevent wide distribution. Unfortunately, to enable sync in Chromium on desktop and indeed to sign in at all on ChromiumOS, API Keys are needed. It used to not be this way, until Mawhen Google vindictively restricted API Keys as per >, much to the displeasure of many developers and linux distributions. As per the API keys document above, you also have to add your Google Account to. To get back to the GUI, press Ctrl+Alt+F1, and reboot to take effect. googleapikeys file and putting the file in your home directory will bake them into the build (only if building Chromium locally), otherwise, after login press Ctrl+Alt+F2 to get to a shell, type chronos as the user name, then type sudo mount -o rw,remount / to mount the RootFS as read/write, then edit /etc/chrome_dev.conf with sudo nano /etc/chrome_dev.conf, modeling it after the sample, but actually adding your API Key info into it. googleapikeys and chrome_dev.conf files are provided. NEW NOTE - My releases now have API keys baked in, but follow below if you are building for yourself.The exports file has other useful commands like updating the ChromiumOS checkout, flashing to usb, deleting the build output directory, and mounting the image locally.Run the sed -i 's/ALL_BOARDS=(/ALL_BOARDS=(\n amd64-frick\n/' $ -noenable_rootfs_verification dev setup.sh, which will copy needed files over the chromiumos source tree and create a new overlay named overlay-amd64-frick. I don't know where you will put these dirs, so I just prefix things below with //.įirst, we assume the chromiumos source, chromium source, and this repo are all in $HOME. Note that it is best if depot_tools, chromium, and chromiumos are all in $HOME. If you built your own image, API Keys will be needed to sign in. However when running /usr/sbin/chromeos-install append -dst /dev/sdxx, where sdxx is your hard drive i.e. 7z files in Releases contain chromiumos_image.bin which can be flashed to a USB Drive with, dd, or cros_flash and booted on most processors supporting AVX or later. Here is Arnold's source code which this project is based on > - if you don't know how to work with these overlays, I invite you to learn, but one can just download the premade image in releases. – Inspired by and based off of ArnoldTheBat's builds which can be downloaded here > – Also added a script I made called memr to drop all caches, added handy aliases which can be found in the dot-bashrc file, and added good cmdline flags which can be found in the chrome_dev.conf file. ![]() – Sceenfetch is like neofetch for ChromiumOS – NOTE: Please see PACKAGES.md for the full list of extra packages! Extra packages include iotop, iotools, sysstat, i2ctools, haveged, telnet, bridge-utils, lm-sensors, pydf, cpuid, htop, sl, custom wallpapers, screenfetch-dev, pak, and TrImLy: a fstrim and e4defrag automator script I made for ChromiumOS.ThoriumOS uses the Thorium Browser, which I also make for Linux, Windows, MacOS (圆4 and M1), and other platforms like the Raspberry Pi >.It contains a variety of extra developer friendly packages, and trys to support as much hardware as possible via kernel configuration, graphics stack configuration, and USE flags. It is based on tip-o-tree, and contains the compiler optimizations of Thorium applied to the whole OS. SYNOPSIS: ThoriumOS aims to be the ChromiumOS counterpart to Thorium. ChromiumOS fork with Thorium Browser, x264/x265 codecs, Widevine, Kernel 5.15, Linux Firmware/Modules support, Nouveau, Intel/AMD microcode, and extra packages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |