https://wiki.archlinux.org/api.php?action=feedcontributions&user=Pierro78&feedformat=atomArchWiki - User contributions [en]2024-03-29T12:32:54ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Chromium&diff=731915Chromium2022-06-07T12:19:14Z<p>Pierro78: /* Tips and tricks */ link to the Not yet, AV1 discussion/information</p>
<hr />
<div>[[Category:Web browser]]<br />
[[Category:Google]]<br />
[[de:Chromium]]<br />
[[ja:Chromium]]<br />
[[zh-hans:Chromium]]<br />
{{Related articles start}}<br />
{{Related|Browser extensions}}<br />
{{Related|Firefox}}<br />
{{Related|Opera}}<br />
{{Related|Vivaldi}}<br />
{{Related articles end}}<br />
<br />
[[Wikipedia:Chromium (web browser)|Chromium]] is an open-source graphical web browser based on the [[Wikipedia:Blink (web engine)|Blink]] rendering engine. It is the basis for the proprietary Google Chrome browser.<br />
<br />
See [https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md this page] for an explanation of the differences between Chromium and Google Chrome. Additionally:<br />
<br />
* Sync is unavailable in Chromium 89+ (2021-03-02) [https://archlinux.org/news/chromium-losing-sync-support-in-early-march/]<br />
<br />
{{Note|Sync can be temporarily restored by [https://gist.github.com/foutrelis/14e339596b89813aa9c37fd1b4e5d9d5 using Chrome's OAuth2 credentials] or [https://www.chromium.org/developers/how-tos/api-keys getting your own], but pay attention to the disclaimers and do not consider this to be a long-term solution.<br />
Consider switching to [https://www.xbrowsersync.org xbrowsersync] for bookmarks syncing as long term solution.<br />
}}<br />
<br />
See [[List of applications/Internet#Blink-based]] for other browsers based on Chromium.<br />
<br />
== Installation ==<br />
<br />
There are several packages available to [[install]] Chromium with:<br />
<br />
* {{Pkg|chromium}} — stable release;<br />
* {{AUR|chromium-dev}} — development release;<br />
* {{AUR|chromium-snapshot-bin}} — nightly build.<br />
<br />
Google Chrome packages:<br />
<br />
* {{AUR|google-chrome}} — stable release;<br />
* {{AUR|google-chrome-beta}} — beta release;<br />
* {{AUR|google-chrome-dev}} — development release.<br />
<br />
{{Note|From the [https://www.chromium.org/Home/chromium-privacy Chromium privacy page]: "Features that communicate with Google made available through the compilation of code in Chromium are subject to the [https://www.google.com/policies/privacy/ Google Privacy Policy]." For those who want to avoid all integration with Google services, there are some [[List of applications/Internet#Privacy-focused chromium spin-offs|privacy-focused spin-offs]].}}<br />
<br />
== Configuration ==<br />
<br />
=== Default applications ===<br />
<br />
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see [[default applications]].<br />
<br />
=== Certificates ===<br />
<br />
Chromium uses [[Network Security Services]] for certificate management. Certificates can be managed in {{ic|chrome://settings/certificates}}.<br />
<br />
=== Making flags persistent ===<br />
<br />
{{Note|The {{ic|chromium-flags.conf}} file and the accompanying custom launcher script are specific to the Arch Linux {{Pkg|chromium}} package. For {{AUR|google-chrome}} and {{AUR|google-chrome-dev}}, use {{ic|chrome-flags.conf}} and {{ic|chrome-dev-flags.conf}} instead.}}<br />
<br />
You can put your flags in a {{ic|chromium-flags.conf}} file under {{ic|$HOME/.config/}} (or under {{ic|$XDG_CONFIG_HOME}} if you have configured that environment variable).<br />
<br />
No special syntax is used; flags are defined as if they were written in a terminal.<br />
<br />
* The arguments are split on whitespace and shell quoting rules apply, but no further parsing is performed.<br />
* In case of improper quoting anywhere in the file, a fatal error is raised.<br />
* Flags can be placed in separate lines for readability, but this is not required.<br />
* Lines starting with a hash symbol (#) are skipped. (This is only supported by the {{Pkg|chromium}} launcher script and will not work when using {{ic|chrome-flags.conf}} with the {{AUR|google-chrome}} package.)<br />
<br />
Below is an example {{ic|chromium-flags.conf}} file that defines the flags {{ic|--start-maximized --incognito}}:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
# This line will be ignored.<br />
--start-maximized<br />
--incognito<br />
}}<br />
<br />
=== Force GPU acceleration ===<br />
<br />
{{Warning|Disabling the rendering blacklist may cause unstable behavior, including crashes of the host. See the bug reports in {{ic|chrome://gpu}} for details.}}<br />
<br />
By default Chromium on Linux does not use any GPU acceleration. To force GPU acceleration, [[append]] the following flags to [[/Tips and tricks#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
--enable-zero-copy<br />
}}<br />
<br />
Additionally the flag {{ic|--disable-gpu-driver-bug-workarounds}} may need to be passed to prevent GPU workaround from being used. Flags in {{ic|chrome://gpu}} should state "Hardware accelerated" when configured and available.<br />
<br />
{{Out of date|A fix has been merged into mesa as of May 2021. [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10850]}}<br />
<br />
{{ic|--enable-native-gpu-memory-buffers}} is broken since mesa 20.1.1 [https://gitlab.freedesktop.org/mesa/mesa/-/issues/3119#note_533902]<br />
<br />
=== Hardware video acceleration ===<br />
<br />
{{Note|1=<nowiki/><br />
* There is no official support from Chromium or Arch Linux for this feature [https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/vaapi.md#vaapi-on-linux]. However, {{Pkg|chromium}} from official repositories is compiled with VA-API support and you may ask for help in [https://bbs.archlinux.org/viewtopic.php?id=244031 the dedicated forum thread].<br />
* VA-API does not work with the {{Pkg|chromium}} package when using the native Wayland backend, but it does work in {{AUR|chromium-wayland-vaapi}}.<br />
}}<br />
<br />
To enable VA-API support in Chromium:<br />
<br />
* Install the correct VA-API driver for your video card and verify VA-API has been enabled and working correctly, see [[Hardware video acceleration]]. For proprietary NVIDIA support, installing {{AUR|libva-vdpau-driver-chromium}} or {{AUR|libva-vdpau-driver-vp9-git}} is required.<br />
* Set the option {{ic|1=--enable-features=VaapiVideoDecoder}}. This is enough when using ANGLE GL renderer and {{Pkg|libva-intel-driver}}.<br />
* When using ANGLE, Chromium forces the older i965 driver and fails when {{Pkg|intel-media-driver}} is used. As a workaround, [[Hardware video acceleration#Configuring VA-API|configure VA-API manually]]. See [https://github.com/intel/media-driver/issues/818] for details.<br />
* To use the system GL renderer on Xorg, use either {{ic|1=--use-gl=egl}} or {{ic|1=--use-gl=desktop}}. On XWayland, use the {{ic|1=--use-gl=egl}} flag (Currently exhibits choppiness {{Bug|67035}} on some systems).<br />
* If VA-API still does not work, try the {{ic|1=--disable-features=UseChromeOSDirectVideoDecoder}} flag [https://bbs.archlinux.org/viewtopic.php?pid=2021090#p2021090]<br />
<br />
==== Tips and tricks ====<br />
<br />
To check if it is working play a video which is using a codec supported by your VA-API driver (''vainfo'' tells you which codecs are supported, but Chromium will only support VP9 and h264):<br />
<br />
* Open the DevTools by pressing {{ic|Ctrl+Shift+I}} or on the ''Inspect'' button of the context (right-click) menu<br />
* Add the Media inspection tab: ''Hamburger menu > More tools > Media''<br />
* In the newly opened Media tab, look at the hardware decoder state of the video decoder<br />
<br />
Test on a large enough video. Starting with version 86, Chromium on desktop [https://bugs.chromium.org/p/chromium/issues/detail?id=684792 will only accelerate videos larger than 720p].<br />
<br />
To reduce CPU usage while watching YouTube where VP8/VP9 hardware decoding is not available use the [https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal h264ify], [https://chrome.google.com/webstore/detail/enhanced-h264ify/omkfmpieigblcllmkgbflkikinpkodlk enhanced-h264ify] or [https://chrome.google.com/webstore/detail/not-yet-av1/dcmllfkiihingappljlkffafnlhdpbai Not yet, AV1][https://bbs.archlinux.org/viewtopic.php?pid=2039884#p2039884] extension.<br />
<br />
On some systems (especially on XWayland) you might need to [[#Force GPU acceleration]]. Only {{ic|--ignore-gpu-blocklist}} is enough for our purposes.<br />
<br />
{{Expansion|Provide a link to some bug report.}}<br />
<br />
You might need to disable the Skia renderer, as it is currently not compatible with video decode acceleration: {{ic|1=--disable-features=UseSkiaRenderer}}<br />
<br />
=== PDF viewer plugin ===<br />
<br />
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin. If you do not want to use this plugin, check ''Download PDFs'' in {{ic|chrome://settings/content/pdfDocuments}}.<br />
<br />
=== Flash Player plugin ===<br />
<br />
Support for Flash Player was removed in Chromium 88.[https://www.chromium.org/flash-roadmap#TOC-Flash-Support-Removed-from-Chromium-Target:-Chrome-88---Jan-2021-]<br />
<br />
=== Running on XWayland ===<br />
<br />
If you are using NVIDIA's proprietary driver, running Chromium on XWayland may cause the GPU process to occasionally crash. To prevent the GPU process from crashing, add the following flags:<br />
<br />
--use-angle=vulkan --use-cmd-decoder=passthrough<br />
<br />
{{Note|This does not prevent all XWayland-related crashes.}}<br />
<br />
=== Native Wayland support ===<br />
<br />
Since version 97, native [[Wayland]] support in Chromium can be enabled with the following flags [https://chromium.googlesource.com/chromium/src/+/43cfb2f92a5cdc1a787d7326e74676884abf5052]:<br />
<br />
--ozone-platform-hint=auto<br />
<br />
See [[#Making flags persistent]] for a permanent configuration. The flag is also available via [[#chrome://_URLs|browser flags menu]].<br />
<br />
This will select wayland Ozone backend when in wayland session, so you can use a single desktop entry if you switch between X11 and Wayland often.<br />
<br />
== Tips and tricks ==<br />
<br />
The following tips and tricks should work for both Chromium and Chrome unless explicitly stated.<br />
<br />
=== Browsing experience ===<br />
<br />
==== chrome:// URLs ====<br />
<br />
A number of tweaks can be accessed via Chrome URLs. See '''chrome://chrome-urls''' for a complete list.<br />
<br />
* '''chrome://flags''' - access experimental features such as WebGL and rendering webpages with GPU, etc.<br />
* '''chrome://extensions''' - view, enable and disable the currently used Chromium extensions.<br />
* '''chrome://gpu''' - status of different GPU options.<br />
* '''chrome://sandbox''' - indicate sandbox status.<br />
* '''chrome://version''' - display version and switches used to invoke the active {{ic|/usr/bin/chromium}}.<br />
<br />
An automatically updated, complete listing of Chromium switches (command line parameters) is available [https://peter.sh/experiments/chromium-command-line-switches/ here].<br />
<br />
==== Chromium task manager ====<br />
<br />
Shift+ESC can be used to bring up the browser task manager wherein memory, CPU, and network usage can be viewed.<br />
<br />
==== Chromium overrides/overwrites Preferences file ====<br />
<br />
If you enabled syncing with a Google Account, then Chromium will override any direct edits to the Preferences file found under {{ic|~/.config/chromium/Default/Preferences}}. To work around this, start Chromium with the {{ic|--disable-sync-preferences}} switch:<br />
$ chromium --disable-sync-preferences<br />
<br />
If Chromium is started in the background when you login in to your desktop environment, make sure the command your desktop environment uses is:<br />
$ chromium --disable-sync-preferences --no-startup-window<br />
<br />
==== Search engines ====<br />
<br />
Make sites like [https://wiki.archlinux.org wiki.archlinux.org] and [https://en.wikipedia.org wikipedia.org] easily searchable by first executing a search on those pages, then going to ''Settings > Search'' and click the ''Manage search engines..'' button. From there, "Edit" the Wikipedia entry and change its keyword to '''w''' (or some other shortcut you prefer). Now searching Wikipedia for "Arch Linux" from the address bar is done simply by entering "'''w arch linux'''".<br />
<br />
{{Note| Google search is used automatically when typing something into the URL bar. A hard-coded keyword trigger is also available using the '''?''' prefix.}}<br />
<br />
==== Tmpfs ====<br />
<br />
===== Cache in tmpfs =====<br />
<br />
{{Note|Chromium stores its cache separate from its browser profile directory.}}<br />
<br />
To limit Chromium from writing its cache to a physical disk, one can define an alternative location via the {{ic|--disk-cache-dir}} flag:<br />
$ chromium --disk-cache-dir="$XDG_RUNTIME_DIR/chromium-cache"<br />
<br />
Cache should be considered temporary and will '''not''' be saved after a reboot or hard lock. Another option is to setup the space in {{ic|/etc/fstab}}:<br />
<br />
{{hc|/etc/fstab|2=<br />
tmpfs /home/''username''/.cache tmpfs noatime,nodev,nosuid,size=400M 0 0<br />
}}<br />
<br />
===== Profile in tmpfs =====<br />
<br />
Relocate the browser profile to a [[Wikipedia:Tmpfs|tmpfs]] filesystem, including {{ic|/tmp}}, or {{ic|/dev/shm}} for improvements in application response as the entire profile is now stored in RAM.<br />
<br />
Use an active profile management tool such as {{Pkg|profile-sync-daemon}} for maximal reliability and ease of use. It symlinks or bind mounts and syncs the browser profile directories to RAM. For more, see [[Profile-sync-daemon]].<br />
<br />
==== Launch a new browser instance ====<br />
<br />
When you launch the browser, it first checks if another instance using the same data directory is already running. If there is one, the new window is associated with the old instance. If you want to launch an independent instance of the browser, you must specify separate directory using the {{ic|--user-data-dir}} parameter:<br />
<br />
$ chromium --user-data-dir=''/path/to/some/directory''<br />
<br />
{{Note|The default location of the user data is {{ic|~/.config/chromium/}}.}}<br />
<br />
==== Directly open *.torrent files and magnet links with a torrent client ====<br />
<br />
By default, Chromium downloads {{ic|*.torrent}} files directly and you need to click the notification from the bottom-left corner of the screen in order for the file to be opened with your default torrent client. This can be avoided with the following method:<br />
<br />
* Download a {{ic|*.torrent}} file.<br />
* Right-click the notification displayed at the bottom-left corner of the screen.<br />
* Check the "''Always Open Files of This Type''" checkbox.<br />
<br />
See [[xdg-open]] to change the default assocation.<br />
<br />
==== Touch Scrolling on touchscreen devices ====<br />
<br />
You may need to specify which touch device to use. Find your touchscreen device with {{ic| xinput list}} then launch Chromium with the {{ic|1=--touch-devices='''x'''}} parameter, where "'''x'''" is the id of your device. {{Note|If the device is designated as a slave pointer, using this may not work, use the master pointer's ID instead.}}<br />
<br />
==== Reduce memory usage ====<br />
<br />
By default, Chromium uses a separate OS process for each ''instance'' of a visited web site. [https://www.chromium.org/developers/design-documents/process-models#Supported_Models] However, you can specify command-line switches when starting Chromium to modify this behaviour.<br />
<br />
For example, to share one process for all instances of a website:<br />
<br />
$ chromium --process-per-site<br />
<br />
To use a single process model:<br />
<br />
$ chromium --single-process<br />
<br />
{{Warning|The single-process model is discouraged because it is unsafe and may contain bugs not present in other models.[https://www.chromium.org/developers/design-documents/process-models#TOC-Single-process]}}<br />
<br />
In addition, you can suspend or store inactive Tabs with extensions such as [https://chrome.google.com/webstore/detail/tab-suspender/fiabciakcmgepblmdkmemdbbkilneeeh?hl=en Tab Suspender] and [https://chrome.google.com/webstore/detail/onetab/chphlpgkkbolifaimnlloiipkdnihall?hl=en OneTab].<br />
<br />
==== User Agent ====<br />
<br />
The User Agent can be arbitrarily modified at the start of Chromium's base instance via its {{Ic|<nowiki>--user-agent="[string]"</nowiki>}} parameter.<br />
<br />
==== DOM Distiller ====<br />
<br />
Chromium has a similar reader mode to Firefox. In this case it is called DOM Distiller, which is an [https://github.com/chromium/dom-distiller open source project].<br />
It is disabled by default, but can be enabled using the {{Ic|chrome://flags/#enable-reader-mode}} flag, which you can also make [[#Making flags persistent|persistent]].<br />
Not only does DOM Distiller provide a better reading experience by distilling the content of the page, it also simplifies pages for print. Even though the latter checkbox option has been removed from the print dialog, you can still print the distilled page, which basically has the same effect.<br />
<br />
After enabling the flag, you will find a new "Enter reader mode" menu item and corresponding icon in the address bar when Chromium thinks the website you are visiting could do with some distilling.<br />
<br />
==== Forcing specific GPU ====<br />
<br />
In multi-GPU systems, Chromium automatically detects which GPU should be used for rendering (discrete or integrated). This works 99% of the time, except when it does not - if a unavailable GPU is picked (for example, discrete graphics on VFIO GPU passthrough-enabled systems), {{ic|chrome://gpu}} will complain about not being able to initialize the GPU process. On the same page below '''Driver Information''' there will be multiple GPUs shown (GPU0, GPU1, ...). There is no way to switch between them in a user-friendly way, but you can read the device/vendor IDs present there and configure Chromium to use a specific GPU with flags:<br />
<br />
$ chromium --gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x1912<br />
<br />
...where {{ic|0x8086}} and {{ic|0x1912}} is replaced by the IDs of the GPU you want to use (as shown on the {{ic|chrome://gpu}} page).<br />
<br />
==== Import bookmarks from Firefox ====<br />
<br />
To ease the transition, you can import bookmarks from [[Firefox]] into Chromium.<br />
<br />
Navigate Chromium to {{ic|chrome://settings/importData}}<br />
<br />
If Firefox is already installed on your computer, you can directly import bookmarks as well as many other things from Firefox.<br />
<br />
Make sure '''Mozilla Firefox''' is selected. Optionally, you can uncheck some unwanted items here. Click the '''Import''' and then '''Done'''. You are done with it.<br />
<br />
{{note|If you have not created any bookmarks in Chromium yet, the bookmarks will show up in your bookmarks bar. If you already have bookmarks, the bookmarks will be in a new folder labeled "Imported From Firefox"}}<br />
<br />
If you import bookmarks from another PC, you have to export bookmarks from Firefox first.<br />
<br />
{{ic|''Ctrl + Shift + O > Import and Backup > Export Bookmarks To HTML}} in Firefox''<br />
<br />
The procedure is pretty much the same. You need to go to {{ic|chrome://settings/importData}}. However, this time, in the '''From''' drop-down menu, select '''Bookmarks HTML File''' and click the '''Choose File''' button and upload the desired bookmark file.<br />
<br />
==== Enabling native notifications ====<br />
<br />
Go to {{ic|chrome://flags#enable-system-notifications}} and select ''Enabled''.<br />
<br />
==== U2F authentication ====<br />
<br />
Install {{Pkg|libfido2}} library. This provides the udev rules required to enable access to the [[U2F]] key as a user.<br />
U2F keys are by default only accessible by root, and without these rules Chromium will give an error.<br />
<br />
==== Dark mode ====<br />
<br />
To enable dark mode (used in ''prefers-color-scheme'' in CSS, JavaScript, Settings and Dev-Tools) and enable the dark theme (normally used for incognito mode) [[append]] the following flag to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--force-dark-mode<br />
--enable-features=WebUIDarkMode<br />
}}<br />
<br />
===== Dark mode by system preference =====<br />
<br />
[https://bugs.chromium.org/p/chromium/issues/detail?id=998903 This Chromium issue] aims to bring dark mode based on GTK theme selection into Chromium.<br />
<br />
In the future, all that will be required to properly use system preference, is setting ''Designs'' to GTK in {{ic|chrome://settings/appearance}}.<br />
<br />
==== Enable Side Panel ====<br />
<br />
The Side Panel can be enabled through {{ic|chrome://flags}}. You can enable or disable '''Side panel''', and change options such as '''Side panel border''' and '''Side panel drag and drop'''.<br />
<br />
=== Profile maintenance ===<br />
<br />
Chromium uses [[SQLite]] databases to manage history and the like. Sqlite databases become fragmented over time and empty spaces appear all around. But, since there are no managing processes checking and optimizing the database, these factors eventually result in a performance hit. A good way to improve startup and some other bookmarks- and history-related tasks is to defragment and trim unused space from these databases.<br />
<br />
{{Pkg|profile-cleaner}} and {{AUR|browser-vacuum}} in the [[AUR]] do just this.<br />
<br />
=== Security ===<br />
<br />
==== Disable JIT ====<br />
<br />
At the cost of reduced performance, you can disable just-in-time compilation of JavaScript to native code, which is responsible for [https://microsoftedge.github.io/edgevr/posts/Super-Duper-Secure-Mode/ roughly half of the security vulnerabilities in the JS engine], using the flag {{ic|1=--js-flags=--jitless}}.<br />
<br />
==== WebRTC ====<br />
<br />
WebRTC is a communication protocol that relies on JavaScript that can leak one's actual IP address and hardware hash from behind a VPN. While some software may prevent the leaking scripts from running, it is probably a good idea to block this protocol directly as well, just to be safe. As of October 2016, there is no way to disable WebRTC on Chromium on desktop, there are extensions available to disable local IP address leak, one is this [https://chrome.google.com/webstore/detail/webrtc-network-limiter/npeicpdbkakmehahjeeohfdhnlpdklia extension].<br />
<br />
One can test WebRTC via https://browserleaks.com/webrtc.<br />
<br />
{{Warning|Even though IP leak can be prevented, Chromium still sends your unique hash, and there is no way to prevent this. Read more on https://www.browserleaks.com/webrtc#webrtc-disable}}<br />
<br />
==== SSL certificates ====<br />
<br />
Chromium does not have an SSL certificate manager. It relies on the NSS Shared DB {{ic|~/.pki/nssdb}}. In order to add SSL certificates to the database, users will have to use the shell.<br />
<br />
===== Adding CAcert certificates for self-signed certificates =====<br />
<br />
Grab the CAcerts and create an {{ic|nssdb}}, if one does not already exist. To do this, first install the {{Pkg|nss}} package, then complete these steps:<br />
<br />
$ mkdir -p $HOME/.pki/nssdb<br />
$ cd $HOME/.pki/nssdb<br />
$ certutil -N -d sql:.<br />
<br />
$ curl -k -o "cacert-root.crt" "http://www.cacert.org/certs/root.crt"<br />
$ curl -k -o "cacert-class3.crt" "http://www.cacert.org/certs/class3.crt"<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org" -i cacert-root.crt <br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org Class 3" -i cacert-class3.crt<br />
<br />
{{Note|Users will need to create a password for the database, if it does not exist.}}<br />
<br />
Now users may manually import a self-signed certificate.<br />
<br />
===== Example 1: Using a shell script to isolate the certificate from TomatoUSB =====<br />
<br />
Below is a simple script that will extract and add a certificate to the user's {{ic|nssdb}}:<br />
<br />
#!/bin/sh<br />
#<br />
# usage: import-cert.sh remote.host.name [port]<br />
#<br />
REMHOST=$1<br />
REMPORT=${2:-443}<br />
exec 6>&1<br />
exec > $REMHOST<br />
echo | openssl s_client -connect ${REMHOST}:${REMPORT} 2>&1 |sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'<br />
certutil -d sql:$HOME/.pki/nssdb -A -t "P,," -n "$REMHOST" -i $REMHOST <br />
exec 1>&6 6>&-<br />
<br />
Syntax is advertised in the commented lines.<br />
<br />
References:<br />
*https://web.archive.org/web/20180718193807/https://blog.avirtualhome.com/adding-ssl-certificates-to-google-chrome-linux-ubuntu<br />
*https://chromium.googlesource.com/chromium/src/+/master/docs/linux/cert_management.md<br />
<br />
===== Example 2: Using Firefox to isolate the certificate from TomatoUSB =====<br />
<br />
The {{Pkg|firefox}} browser can be used to save the certificate to a file for manual import into the database.<br />
<br />
Using firefox:<br />
#Browse to the target URL.<br />
#Upon seeing the "This Connection is Untrusted" warning screen, click: ''I understand the Risks > Add Exception...''<br />
#Click: ''View > Details > Export'' and save the certificate to a temporary location ({{ic|/tmp/easy.pem}} in this example).<br />
<br />
Now import the certificate for use in Chromium:<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "easy" -i /tmp/easy.pem<br />
<br />
{{Note|Adjust the name to match that of the certificate. In the example above, "easy" is the name of the certificate.}}<br />
<br />
Reference:<br />
*https://sahissam.blogspot.com/2012/06/new-ssl-certificates-for-tomatousb-and.html<br />
<br />
==== Canvas Fingerprinting ====<br />
<br />
Canvas fingerprinting is a technique that allows websites to identify users by detecting differences when rendering to an HTML5 canvas. This information can be made inaccessible by using the {{ic|--disable-reading-from-canvas}} flag.<br />
<br />
To confirm this is working run [https://panopticlick.eff.org this test] and make sure "hash of canvas fingerprint" is reported as undetermined in the full results.<br />
<br />
{{Note|1=<nowiki></nowiki><br />
* Some extensions require reading from canvas and may be broken by setting {{ic|--disable-reading-from-canvas}}.<br />
* YouTube player does not work properly without canvas reading. [https://github.com/qutebrowser/qutebrowser/issues/5345][https://bbs.archlinux.org/viewtopic.php?pid=1907406]<br />
}}<br />
<br />
==== Privacy extensions ====<br />
<br />
See [[Browser extensions#Privacy]].<br />
<br />
{{Tip|Installing too many extensions might take up much space in the toolbar. Those extensions which you would not interact with anyway (e.g. [https://chrome.google.com/webstore/detail/gcbommkclmclpchllfjekcdonpmejbdp HTTPS Everywhere]) can be hidden by right-clicking on the extension and choosing ''Hide in Chromium menu''.}}<br />
<br />
==== Do Not Track ====<br />
<br />
To enable [[wikipedia:Do Not Track|Do Not Track]], visit {{ic|chrome://settings}}, scroll down to ''Advanced'' and under ''Privacy and security'', check ''Send a "Do Not Track" request with your browsing traffic''.<br />
<br />
==== Force a password store ====<br />
<br />
Chromium uses a password store to store your passwords and the ''Chromium Safe Storage'' key, which is used to encrypt cookie values. [https://codereview.chromium.org/24734007]<br />
<br />
By default Chromium auto-detects which password store to use, which can lead to you apparently losing your passwords and cookies when switching to another desktop environment or window manager.<br />
<br />
You can force Chromium to use a specific password store by launching it with the {{ic|--password-store}} flag with one of following the values [https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md]:<br />
<br />
* {{ic|gnome}}, uses [[Gnome Keyring]]<br />
* {{ic|kwallet5}}, uses [[KDE Wallet]]<br />
* {{ic|basic}}, saves the passwords and the cookies' encryption key as plain text in the file {{ic|Login Data}}<br />
* {{ic|detect}}, the default auto-detect behavior<br />
<br />
For example, to force Chromium to use Gnome Keyring in another desktop or WM use {{ic|1=--password-store=gnome}}, see [[#Making flags persistent]] for making it permanent.<br />
<br />
When using a password store of another desktop environment you probably also want to unlock it automatically. See [[GNOME/Keyring#Using the keyring]] and [[KDE Wallet#Unlock KDE Wallet automatically on login]].<br />
<br />
== Troubleshooting ==<br />
<br />
=== Fonts ===<br />
<br />
{{Note|Chromium does not fully integrate with fontconfig/GTK/Pango/X/etc. due to its sandbox. For more information, see the [https://dev.chromium.org/developers/linux-technical-faq Linux Technical FAQ].}}<br />
<br />
==== Tab font size is too large ====<br />
<br />
Chromium will use the GTK settings as described in [[GTK#Configuration]]. When configured, Chromium will use the {{ic|gtk-font-name}} setting for tabs (which may mismatch window font size). To override these settings, use {{ic|1=--force-device-scale-factor=1.0}}.<br />
<br />
=== WebGL ===<br />
<br />
There is the possibility that your graphics card has been blacklisted by Chromium. See [[#Force GPU acceleration]].<br />
<br />
If you are using Chromium with [[Bumblebee]], WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with {{ic|optirun chromium --disable-gpu-sandbox}}.<br />
<br />
Visit {{ic|chrome://gpu/}} for debugging information about WebGL support.<br />
<br />
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in {{ic|chrome://gpu}} even when you are not using it or primusrun/optirun). Running using a different user directory, e.g, {{ic|1=chromium --user-data-dir=$(mktemp -d)}} may solve this issue. For a persistent solution you can reset the GPU information by deleting {{ic|~/.config/chromium/Local\ State}}.<br />
<br />
=== Incorrect HiDPI rendering ===<br />
<br />
Chromium will automatically scale for a [[HiDPI]] display, however, this may cause an incorrect rendered GUI.<br />
<br />
The flag {{ic|1=--force-device-scale-factor=1}} may be used to overrule the automatic scaling factor.<br />
<br />
When [[#Native Wayland support|native Wayland support]] is enabled, Chromium will automatically scale based on the configured scale of each monitor.<br />
<br />
=== Password prompt on every start with GNOME Keyring ===<br />
<br />
See [[GNOME/Keyring#Passwords are not remembered]].<br />
<br />
=== Chromecasts in the network are not discovered ===<br />
<br />
You will need to enable the Media Router Component Extension in {{ic|chrome://flags/#load-media-router-component-extension}}.<br />
<br />
=== Everything is syncing except for password ===<br />
<br />
If synchronization is not working for password only (you can check it on {{ic|chrome://sync-internals/}}) delete profile login data:<br />
<br />
$ rm ~/.config/chromium/Default/Login\ Data*<br />
<br />
See [https://support.google.com/chrome/thread/9947763?hl=en&msgid=23687608 Google Chrome Help forum] for details.<br />
<br />
=== Losing cookies and passwords when switching between desktop environments ===<br />
<br />
If you see the message {{ic|Failed to decrypt token for service AccountId-*}} in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Hang on startup when Google Sync enabled ===<br />
<br />
Try launching Chrome with {{ic|1=--password-store=basic}} or another appropriate password store.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Chromium asks to be set as the default browser every time it starts ===<br />
<br />
If you are using KDE and have once set Firefox as the default browser (by clicking the button inside Firefox), you might find Chromium asks to be set as the default browser every time it starts, even if you click the "set as default" button.<br />
<br />
Chromium checks for this status by running {{ic|xdg-settings check default-web-browser chromium.desktop}}. If the output is "no", it is not considering itself to be the default browser. The script {{ic|xdg-settings}} checks for the following MIME associations and expect all of them to be {{ic|chromium.desktop}}:<br />
<br />
{{bc|<br />
x-scheme-handler/http<br />
x-scheme-handler/https<br />
text/html}}<br />
<br />
To fix it, go to ''System settings > Applications > Default applications > Web browser'' and choose Chromium. Then, set the MIME association for {{ic|text/html}}:<br />
<br />
$ xdg-mime default chromium.desktop text/html<br />
<br />
Finally, [[XDG_MIME_Applications#New_MIME_types|update the MIME database]]:<br />
<br />
$ update-mime-database ~/.local/share/mime<br />
<br />
=== "This browser or app may not be secure" error logging in to Google ===<br />
<br />
As of 2020.04.20 if you run chromium with {{ic|1=--remote-debugging-port=9222}} flag for web development, you cannot log in to your Google account. Temporarily disable this flag to login and then you can enable it back.<br />
<br />
=== Chromium stuck at 60fps when using a 144Hz + 60Hz monitor ===<br />
<br />
There is a suitable workaround for this issue, [[append]] the following flags to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--use-gl=egl<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
}}<br />
<br />
This should make Chromium run at 144fps when used on your 144hz display, assuming your compositor is refreshing at 144fps. <br />
Keep in mind it might be a little choppy {{Bug|67035}}, but this is way better than it being stuck at 60fps.<br />
<br />
=== Chromium slow scroll speed ===<br />
<br />
Mouse whell scrolling in chromium and electron based applications may be too slow for daily usage. Here are some solutions.<br />
<br />
[[Libinput#Mouse wheel scrolling speed scaling]] injects {{ic|libinput_event_pointer_get_axis_value}} function in libinput and provides an interface to change scale factor. This is not a application level injection, so an addition script for application specific scale factor tuning is needed. Note that scroll on chromium's small height developer tools may be too fast when scale factor is big enough.<br />
<br />
[[IMWheel]] increases scroll distance by replaying X wheel button event for multiple times. However, chromium assumes the real scroll and the replayed ones as two events. There is a small but noticeable delay between them, so one mouse wheel scroll leads to twice page jumps. Also, touchpad scroll needs additional care.<br />
<br />
[https://chrome.google.com/webstore/detail/linux-scroll-speed-fix/mlboohjioameadaedfjcpemcaangkkbp Linux Scroll Speed Fix] and [https://chrome.google.com/webstore/detail/smoothscroll/nbokbjkabcmbfdlbddjidfmibcpneigj SmoothScroll] are two chromium extensions with suppport for scroll distance modification. Upon wheel scroll in a web page, the closest scrollable ancestor of current focused node will be found, then a scroll method with given pixel distance will be called on it, even if it has been scrolled to bottom. So once you scroll into a text editor or any scrollable element, you can never scroll out of it, except moving mouse. Also, extension based methods can not be used outside chromium.<br />
<br />
== See also ==<br />
<br />
* [https://www.chromium.org/ Chromium homepage]<br />
* [https://chromereleases.googleblog.com/ Google Chrome release notes]<br />
* [https://chrome.google.com/webstore/ Chrome web store]<br />
* [[Wikipedia:Chromium (web browser)#Differences from Google Chrome|Differences between Chromium and Google Chrome]]<br />
* [https://peter.sh/experiments/chromium-command-line-switches/ List of Chromium command-line switches]<br />
* [[Profile-sync-daemon]] - Systemd service that saves Chromium profile in tmpfs and syncs to disk<br />
* [[Tmpfs]] - Tmpfs Filesystem in {{ic|/etc/fstab}}<br />
* [https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html Official tmpfs kernel Documentation]</div>Pierro78https://wiki.archlinux.org/index.php?title=Chromium&diff=731913Chromium2022-06-07T11:58:59Z<p>Pierro78: /* Tips and tricks */ link syntax</p>
<hr />
<div>[[Category:Web browser]]<br />
[[Category:Google]]<br />
[[de:Chromium]]<br />
[[ja:Chromium]]<br />
[[zh-hans:Chromium]]<br />
{{Related articles start}}<br />
{{Related|Browser extensions}}<br />
{{Related|Firefox}}<br />
{{Related|Opera}}<br />
{{Related|Vivaldi}}<br />
{{Related articles end}}<br />
<br />
[[Wikipedia:Chromium (web browser)|Chromium]] is an open-source graphical web browser based on the [[Wikipedia:Blink (web engine)|Blink]] rendering engine. It is the basis for the proprietary Google Chrome browser.<br />
<br />
See [https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md this page] for an explanation of the differences between Chromium and Google Chrome. Additionally:<br />
<br />
* Sync is unavailable in Chromium 89+ (2021-03-02) [https://archlinux.org/news/chromium-losing-sync-support-in-early-march/]<br />
<br />
{{Note|Sync can be temporarily restored by [https://gist.github.com/foutrelis/14e339596b89813aa9c37fd1b4e5d9d5 using Chrome's OAuth2 credentials] or [https://www.chromium.org/developers/how-tos/api-keys getting your own], but pay attention to the disclaimers and do not consider this to be a long-term solution.<br />
Consider switching to [https://www.xbrowsersync.org xbrowsersync] for bookmarks syncing as long term solution.<br />
}}<br />
<br />
See [[List of applications/Internet#Blink-based]] for other browsers based on Chromium.<br />
<br />
== Installation ==<br />
<br />
There are several packages available to [[install]] Chromium with:<br />
<br />
* {{Pkg|chromium}} — stable release;<br />
* {{AUR|chromium-dev}} — development release;<br />
* {{AUR|chromium-snapshot-bin}} — nightly build.<br />
<br />
Google Chrome packages:<br />
<br />
* {{AUR|google-chrome}} — stable release;<br />
* {{AUR|google-chrome-beta}} — beta release;<br />
* {{AUR|google-chrome-dev}} — development release.<br />
<br />
{{Note|From the [https://www.chromium.org/Home/chromium-privacy Chromium privacy page]: "Features that communicate with Google made available through the compilation of code in Chromium are subject to the [https://www.google.com/policies/privacy/ Google Privacy Policy]." For those who want to avoid all integration with Google services, there are some [[List of applications/Internet#Privacy-focused chromium spin-offs|privacy-focused spin-offs]].}}<br />
<br />
== Configuration ==<br />
<br />
=== Default applications ===<br />
<br />
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see [[default applications]].<br />
<br />
=== Certificates ===<br />
<br />
Chromium uses [[Network Security Services]] for certificate management. Certificates can be managed in {{ic|chrome://settings/certificates}}.<br />
<br />
=== Making flags persistent ===<br />
<br />
{{Note|The {{ic|chromium-flags.conf}} file and the accompanying custom launcher script are specific to the Arch Linux {{Pkg|chromium}} package. For {{AUR|google-chrome}} and {{AUR|google-chrome-dev}}, use {{ic|chrome-flags.conf}} and {{ic|chrome-dev-flags.conf}} instead.}}<br />
<br />
You can put your flags in a {{ic|chromium-flags.conf}} file under {{ic|$HOME/.config/}} (or under {{ic|$XDG_CONFIG_HOME}} if you have configured that environment variable).<br />
<br />
No special syntax is used; flags are defined as if they were written in a terminal.<br />
<br />
* The arguments are split on whitespace and shell quoting rules apply, but no further parsing is performed.<br />
* In case of improper quoting anywhere in the file, a fatal error is raised.<br />
* Flags can be placed in separate lines for readability, but this is not required.<br />
* Lines starting with a hash symbol (#) are skipped. (This is only supported by the {{Pkg|chromium}} launcher script and will not work when using {{ic|chrome-flags.conf}} with the {{AUR|google-chrome}} package.)<br />
<br />
Below is an example {{ic|chromium-flags.conf}} file that defines the flags {{ic|--start-maximized --incognito}}:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
# This line will be ignored.<br />
--start-maximized<br />
--incognito<br />
}}<br />
<br />
=== Force GPU acceleration ===<br />
<br />
{{Warning|Disabling the rendering blacklist may cause unstable behavior, including crashes of the host. See the bug reports in {{ic|chrome://gpu}} for details.}}<br />
<br />
By default Chromium on Linux does not use any GPU acceleration. To force GPU acceleration, [[append]] the following flags to [[/Tips and tricks#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
--enable-zero-copy<br />
}}<br />
<br />
Additionally the flag {{ic|--disable-gpu-driver-bug-workarounds}} may need to be passed to prevent GPU workaround from being used. Flags in {{ic|chrome://gpu}} should state "Hardware accelerated" when configured and available.<br />
<br />
{{Out of date|A fix has been merged into mesa as of May 2021. [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10850]}}<br />
<br />
{{ic|--enable-native-gpu-memory-buffers}} is broken since mesa 20.1.1 [https://gitlab.freedesktop.org/mesa/mesa/-/issues/3119#note_533902]<br />
<br />
=== Hardware video acceleration ===<br />
<br />
{{Note|1=<nowiki/><br />
* There is no official support from Chromium or Arch Linux for this feature [https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/vaapi.md#vaapi-on-linux]. However, {{Pkg|chromium}} from official repositories is compiled with VA-API support and you may ask for help in [https://bbs.archlinux.org/viewtopic.php?id=244031 the dedicated forum thread].<br />
* VA-API does not work with the {{Pkg|chromium}} package when using the native Wayland backend, but it does work in {{AUR|chromium-wayland-vaapi}}.<br />
}}<br />
<br />
To enable VA-API support in Chromium:<br />
<br />
* Install the correct VA-API driver for your video card and verify VA-API has been enabled and working correctly, see [[Hardware video acceleration]]. For proprietary NVIDIA support, installing {{AUR|libva-vdpau-driver-chromium}} or {{AUR|libva-vdpau-driver-vp9-git}} is required.<br />
* Set the option {{ic|1=--enable-features=VaapiVideoDecoder}}. This is enough when using ANGLE GL renderer and {{Pkg|libva-intel-driver}}.<br />
* When using ANGLE, Chromium forces the older i965 driver and fails when {{Pkg|intel-media-driver}} is used. As a workaround, [[Hardware video acceleration#Configuring VA-API|configure VA-API manually]]. See [https://github.com/intel/media-driver/issues/818] for details.<br />
* To use the system GL renderer on Xorg, use either {{ic|1=--use-gl=egl}} or {{ic|1=--use-gl=desktop}}. On XWayland, use the {{ic|1=--use-gl=egl}} flag (Currently exhibits choppiness {{Bug|67035}} on some systems).<br />
* If VA-API still does not work, try the {{ic|1=--disable-features=UseChromeOSDirectVideoDecoder}} flag [https://bbs.archlinux.org/viewtopic.php?pid=2021090#p2021090]<br />
<br />
==== Tips and tricks ====<br />
<br />
To check if it is working play a video which is using a codec supported by your VA-API driver (''vainfo'' tells you which codecs are supported, but Chromium will only support VP9 and h264):<br />
<br />
* Open the DevTools by pressing {{ic|Ctrl+Shift+I}} or on the ''Inspect'' button of the context (right-click) menu<br />
* Add the Media inspection tab: ''Hamburger menu > More tools > Media''<br />
* In the newly opened Media tab, look at the hardware decoder state of the video decoder<br />
<br />
Test on a large enough video. Starting with version 86, Chromium on desktop [https://bugs.chromium.org/p/chromium/issues/detail?id=684792 will only accelerate videos larger than 720p].<br />
<br />
To reduce CPU usage while watching YouTube where VP8/VP9 hardware decoding is not available use the [https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal h264ify] or [https://chrome.google.com/webstore/detail/enhanced-h264ify/omkfmpieigblcllmkgbflkikinpkodlk enhanced-h264ify] or [https://chrome.google.com/webstore/detail/not-yet-av1/dcmllfkiihingappljlkffafnlhdpbai?hl=en Not yet, AV1] extension.<br />
<br />
On some systems (especially on XWayland) you might need to [[#Force GPU acceleration]]. Only {{ic|--ignore-gpu-blocklist}} is enough for our purposes.<br />
<br />
{{Expansion|Provide a link to some bug report.}}<br />
<br />
You might need to disable the Skia renderer, as it is currently not compatible with video decode acceleration: {{ic|1=--disable-features=UseSkiaRenderer}}<br />
<br />
=== PDF viewer plugin ===<br />
<br />
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin. If you do not want to use this plugin, check ''Download PDFs'' in {{ic|chrome://settings/content/pdfDocuments}}.<br />
<br />
=== Flash Player plugin ===<br />
<br />
Support for Flash Player was removed in Chromium 88.[https://www.chromium.org/flash-roadmap#TOC-Flash-Support-Removed-from-Chromium-Target:-Chrome-88---Jan-2021-]<br />
<br />
=== Running on XWayland ===<br />
<br />
If you are using NVIDIA's proprietary driver, running Chromium on XWayland may cause the GPU process to occasionally crash. To prevent the GPU process from crashing, add the following flags:<br />
<br />
--use-angle=vulkan --use-cmd-decoder=passthrough<br />
<br />
{{Note|This does not prevent all XWayland-related crashes.}}<br />
<br />
=== Native Wayland support ===<br />
<br />
Since version 97, native [[Wayland]] support in Chromium can be enabled with the following flags [https://chromium.googlesource.com/chromium/src/+/43cfb2f92a5cdc1a787d7326e74676884abf5052]:<br />
<br />
--ozone-platform-hint=auto<br />
<br />
See [[#Making flags persistent]] for a permanent configuration. The flag is also available via [[#chrome://_URLs|browser flags menu]].<br />
<br />
This will select wayland Ozone backend when in wayland session, so you can use a single desktop entry if you switch between X11 and Wayland often.<br />
<br />
== Tips and tricks ==<br />
<br />
The following tips and tricks should work for both Chromium and Chrome unless explicitly stated.<br />
<br />
=== Browsing experience ===<br />
<br />
==== chrome:// URLs ====<br />
<br />
A number of tweaks can be accessed via Chrome URLs. See '''chrome://chrome-urls''' for a complete list.<br />
<br />
* '''chrome://flags''' - access experimental features such as WebGL and rendering webpages with GPU, etc.<br />
* '''chrome://extensions''' - view, enable and disable the currently used Chromium extensions.<br />
* '''chrome://gpu''' - status of different GPU options.<br />
* '''chrome://sandbox''' - indicate sandbox status.<br />
* '''chrome://version''' - display version and switches used to invoke the active {{ic|/usr/bin/chromium}}.<br />
<br />
An automatically updated, complete listing of Chromium switches (command line parameters) is available [https://peter.sh/experiments/chromium-command-line-switches/ here].<br />
<br />
==== Chromium task manager ====<br />
<br />
Shift+ESC can be used to bring up the browser task manager wherein memory, CPU, and network usage can be viewed.<br />
<br />
==== Chromium overrides/overwrites Preferences file ====<br />
<br />
If you enabled syncing with a Google Account, then Chromium will override any direct edits to the Preferences file found under {{ic|~/.config/chromium/Default/Preferences}}. To work around this, start Chromium with the {{ic|--disable-sync-preferences}} switch:<br />
$ chromium --disable-sync-preferences<br />
<br />
If Chromium is started in the background when you login in to your desktop environment, make sure the command your desktop environment uses is:<br />
$ chromium --disable-sync-preferences --no-startup-window<br />
<br />
==== Search engines ====<br />
<br />
Make sites like [https://wiki.archlinux.org wiki.archlinux.org] and [https://en.wikipedia.org wikipedia.org] easily searchable by first executing a search on those pages, then going to ''Settings > Search'' and click the ''Manage search engines..'' button. From there, "Edit" the Wikipedia entry and change its keyword to '''w''' (or some other shortcut you prefer). Now searching Wikipedia for "Arch Linux" from the address bar is done simply by entering "'''w arch linux'''".<br />
<br />
{{Note| Google search is used automatically when typing something into the URL bar. A hard-coded keyword trigger is also available using the '''?''' prefix.}}<br />
<br />
==== Tmpfs ====<br />
<br />
===== Cache in tmpfs =====<br />
<br />
{{Note|Chromium stores its cache separate from its browser profile directory.}}<br />
<br />
To limit Chromium from writing its cache to a physical disk, one can define an alternative location via the {{ic|--disk-cache-dir}} flag:<br />
$ chromium --disk-cache-dir="$XDG_RUNTIME_DIR/chromium-cache"<br />
<br />
Cache should be considered temporary and will '''not''' be saved after a reboot or hard lock. Another option is to setup the space in {{ic|/etc/fstab}}:<br />
<br />
{{hc|/etc/fstab|2=<br />
tmpfs /home/''username''/.cache tmpfs noatime,nodev,nosuid,size=400M 0 0<br />
}}<br />
<br />
===== Profile in tmpfs =====<br />
<br />
Relocate the browser profile to a [[Wikipedia:Tmpfs|tmpfs]] filesystem, including {{ic|/tmp}}, or {{ic|/dev/shm}} for improvements in application response as the entire profile is now stored in RAM.<br />
<br />
Use an active profile management tool such as {{Pkg|profile-sync-daemon}} for maximal reliability and ease of use. It symlinks or bind mounts and syncs the browser profile directories to RAM. For more, see [[Profile-sync-daemon]].<br />
<br />
==== Launch a new browser instance ====<br />
<br />
When you launch the browser, it first checks if another instance using the same data directory is already running. If there is one, the new window is associated with the old instance. If you want to launch an independent instance of the browser, you must specify separate directory using the {{ic|--user-data-dir}} parameter:<br />
<br />
$ chromium --user-data-dir=''/path/to/some/directory''<br />
<br />
{{Note|The default location of the user data is {{ic|~/.config/chromium/}}.}}<br />
<br />
==== Directly open *.torrent files and magnet links with a torrent client ====<br />
<br />
By default, Chromium downloads {{ic|*.torrent}} files directly and you need to click the notification from the bottom-left corner of the screen in order for the file to be opened with your default torrent client. This can be avoided with the following method:<br />
<br />
* Download a {{ic|*.torrent}} file.<br />
* Right-click the notification displayed at the bottom-left corner of the screen.<br />
* Check the "''Always Open Files of This Type''" checkbox.<br />
<br />
See [[xdg-open]] to change the default assocation.<br />
<br />
==== Touch Scrolling on touchscreen devices ====<br />
<br />
You may need to specify which touch device to use. Find your touchscreen device with {{ic| xinput list}} then launch Chromium with the {{ic|1=--touch-devices='''x'''}} parameter, where "'''x'''" is the id of your device. {{Note|If the device is designated as a slave pointer, using this may not work, use the master pointer's ID instead.}}<br />
<br />
==== Reduce memory usage ====<br />
<br />
By default, Chromium uses a separate OS process for each ''instance'' of a visited web site. [https://www.chromium.org/developers/design-documents/process-models#Supported_Models] However, you can specify command-line switches when starting Chromium to modify this behaviour.<br />
<br />
For example, to share one process for all instances of a website:<br />
<br />
$ chromium --process-per-site<br />
<br />
To use a single process model:<br />
<br />
$ chromium --single-process<br />
<br />
{{Warning|The single-process model is discouraged because it is unsafe and may contain bugs not present in other models.[https://www.chromium.org/developers/design-documents/process-models#TOC-Single-process]}}<br />
<br />
In addition, you can suspend or store inactive Tabs with extensions such as [https://chrome.google.com/webstore/detail/tab-suspender/fiabciakcmgepblmdkmemdbbkilneeeh?hl=en Tab Suspender] and [https://chrome.google.com/webstore/detail/onetab/chphlpgkkbolifaimnlloiipkdnihall?hl=en OneTab].<br />
<br />
==== User Agent ====<br />
<br />
The User Agent can be arbitrarily modified at the start of Chromium's base instance via its {{Ic|<nowiki>--user-agent="[string]"</nowiki>}} parameter.<br />
<br />
==== DOM Distiller ====<br />
<br />
Chromium has a similar reader mode to Firefox. In this case it is called DOM Distiller, which is an [https://github.com/chromium/dom-distiller open source project].<br />
It is disabled by default, but can be enabled using the {{Ic|chrome://flags/#enable-reader-mode}} flag, which you can also make [[#Making flags persistent|persistent]].<br />
Not only does DOM Distiller provide a better reading experience by distilling the content of the page, it also simplifies pages for print. Even though the latter checkbox option has been removed from the print dialog, you can still print the distilled page, which basically has the same effect.<br />
<br />
After enabling the flag, you will find a new "Enter reader mode" menu item and corresponding icon in the address bar when Chromium thinks the website you are visiting could do with some distilling.<br />
<br />
==== Forcing specific GPU ====<br />
<br />
In multi-GPU systems, Chromium automatically detects which GPU should be used for rendering (discrete or integrated). This works 99% of the time, except when it does not - if a unavailable GPU is picked (for example, discrete graphics on VFIO GPU passthrough-enabled systems), {{ic|chrome://gpu}} will complain about not being able to initialize the GPU process. On the same page below '''Driver Information''' there will be multiple GPUs shown (GPU0, GPU1, ...). There is no way to switch between them in a user-friendly way, but you can read the device/vendor IDs present there and configure Chromium to use a specific GPU with flags:<br />
<br />
$ chromium --gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x1912<br />
<br />
...where {{ic|0x8086}} and {{ic|0x1912}} is replaced by the IDs of the GPU you want to use (as shown on the {{ic|chrome://gpu}} page).<br />
<br />
==== Import bookmarks from Firefox ====<br />
<br />
To ease the transition, you can import bookmarks from [[Firefox]] into Chromium.<br />
<br />
Navigate Chromium to {{ic|chrome://settings/importData}}<br />
<br />
If Firefox is already installed on your computer, you can directly import bookmarks as well as many other things from Firefox.<br />
<br />
Make sure '''Mozilla Firefox''' is selected. Optionally, you can uncheck some unwanted items here. Click the '''Import''' and then '''Done'''. You are done with it.<br />
<br />
{{note|If you have not created any bookmarks in Chromium yet, the bookmarks will show up in your bookmarks bar. If you already have bookmarks, the bookmarks will be in a new folder labeled "Imported From Firefox"}}<br />
<br />
If you import bookmarks from another PC, you have to export bookmarks from Firefox first.<br />
<br />
{{ic|''Ctrl + Shift + O > Import and Backup > Export Bookmarks To HTML}} in Firefox''<br />
<br />
The procedure is pretty much the same. You need to go to {{ic|chrome://settings/importData}}. However, this time, in the '''From''' drop-down menu, select '''Bookmarks HTML File''' and click the '''Choose File''' button and upload the desired bookmark file.<br />
<br />
==== Enabling native notifications ====<br />
<br />
Go to {{ic|chrome://flags#enable-system-notifications}} and select ''Enabled''.<br />
<br />
==== U2F authentication ====<br />
<br />
Install {{Pkg|libfido2}} library. This provides the udev rules required to enable access to the [[U2F]] key as a user.<br />
U2F keys are by default only accessible by root, and without these rules Chromium will give an error.<br />
<br />
==== Dark mode ====<br />
<br />
To enable dark mode (used in ''prefers-color-scheme'' in CSS, JavaScript, Settings and Dev-Tools) and enable the dark theme (normally used for incognito mode) [[append]] the following flag to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--force-dark-mode<br />
--enable-features=WebUIDarkMode<br />
}}<br />
<br />
===== Dark mode by system preference =====<br />
<br />
[https://bugs.chromium.org/p/chromium/issues/detail?id=998903 This Chromium issue] aims to bring dark mode based on GTK theme selection into Chromium.<br />
<br />
In the future, all that will be required to properly use system preference, is setting ''Designs'' to GTK in {{ic|chrome://settings/appearance}}.<br />
<br />
==== Enable Side Panel ====<br />
<br />
The Side Panel can be enabled through {{ic|chrome://flags}}. You can enable or disable '''Side panel''', and change options such as '''Side panel border''' and '''Side panel drag and drop'''.<br />
<br />
=== Profile maintenance ===<br />
<br />
Chromium uses [[SQLite]] databases to manage history and the like. Sqlite databases become fragmented over time and empty spaces appear all around. But, since there are no managing processes checking and optimizing the database, these factors eventually result in a performance hit. A good way to improve startup and some other bookmarks- and history-related tasks is to defragment and trim unused space from these databases.<br />
<br />
{{Pkg|profile-cleaner}} and {{AUR|browser-vacuum}} in the [[AUR]] do just this.<br />
<br />
=== Security ===<br />
<br />
==== Disable JIT ====<br />
<br />
At the cost of reduced performance, you can disable just-in-time compilation of JavaScript to native code, which is responsible for [https://microsoftedge.github.io/edgevr/posts/Super-Duper-Secure-Mode/ roughly half of the security vulnerabilities in the JS engine], using the flag {{ic|1=--js-flags=--jitless}}.<br />
<br />
==== WebRTC ====<br />
<br />
WebRTC is a communication protocol that relies on JavaScript that can leak one's actual IP address and hardware hash from behind a VPN. While some software may prevent the leaking scripts from running, it is probably a good idea to block this protocol directly as well, just to be safe. As of October 2016, there is no way to disable WebRTC on Chromium on desktop, there are extensions available to disable local IP address leak, one is this [https://chrome.google.com/webstore/detail/webrtc-network-limiter/npeicpdbkakmehahjeeohfdhnlpdklia extension].<br />
<br />
One can test WebRTC via https://browserleaks.com/webrtc.<br />
<br />
{{Warning|Even though IP leak can be prevented, Chromium still sends your unique hash, and there is no way to prevent this. Read more on https://www.browserleaks.com/webrtc#webrtc-disable}}<br />
<br />
==== SSL certificates ====<br />
<br />
Chromium does not have an SSL certificate manager. It relies on the NSS Shared DB {{ic|~/.pki/nssdb}}. In order to add SSL certificates to the database, users will have to use the shell.<br />
<br />
===== Adding CAcert certificates for self-signed certificates =====<br />
<br />
Grab the CAcerts and create an {{ic|nssdb}}, if one does not already exist. To do this, first install the {{Pkg|nss}} package, then complete these steps:<br />
<br />
$ mkdir -p $HOME/.pki/nssdb<br />
$ cd $HOME/.pki/nssdb<br />
$ certutil -N -d sql:.<br />
<br />
$ curl -k -o "cacert-root.crt" "http://www.cacert.org/certs/root.crt"<br />
$ curl -k -o "cacert-class3.crt" "http://www.cacert.org/certs/class3.crt"<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org" -i cacert-root.crt <br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org Class 3" -i cacert-class3.crt<br />
<br />
{{Note|Users will need to create a password for the database, if it does not exist.}}<br />
<br />
Now users may manually import a self-signed certificate.<br />
<br />
===== Example 1: Using a shell script to isolate the certificate from TomatoUSB =====<br />
<br />
Below is a simple script that will extract and add a certificate to the user's {{ic|nssdb}}:<br />
<br />
#!/bin/sh<br />
#<br />
# usage: import-cert.sh remote.host.name [port]<br />
#<br />
REMHOST=$1<br />
REMPORT=${2:-443}<br />
exec 6>&1<br />
exec > $REMHOST<br />
echo | openssl s_client -connect ${REMHOST}:${REMPORT} 2>&1 |sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'<br />
certutil -d sql:$HOME/.pki/nssdb -A -t "P,," -n "$REMHOST" -i $REMHOST <br />
exec 1>&6 6>&-<br />
<br />
Syntax is advertised in the commented lines.<br />
<br />
References:<br />
*https://web.archive.org/web/20180718193807/https://blog.avirtualhome.com/adding-ssl-certificates-to-google-chrome-linux-ubuntu<br />
*https://chromium.googlesource.com/chromium/src/+/master/docs/linux/cert_management.md<br />
<br />
===== Example 2: Using Firefox to isolate the certificate from TomatoUSB =====<br />
<br />
The {{Pkg|firefox}} browser can be used to save the certificate to a file for manual import into the database.<br />
<br />
Using firefox:<br />
#Browse to the target URL.<br />
#Upon seeing the "This Connection is Untrusted" warning screen, click: ''I understand the Risks > Add Exception...''<br />
#Click: ''View > Details > Export'' and save the certificate to a temporary location ({{ic|/tmp/easy.pem}} in this example).<br />
<br />
Now import the certificate for use in Chromium:<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "easy" -i /tmp/easy.pem<br />
<br />
{{Note|Adjust the name to match that of the certificate. In the example above, "easy" is the name of the certificate.}}<br />
<br />
Reference:<br />
*https://sahissam.blogspot.com/2012/06/new-ssl-certificates-for-tomatousb-and.html<br />
<br />
==== Canvas Fingerprinting ====<br />
<br />
Canvas fingerprinting is a technique that allows websites to identify users by detecting differences when rendering to an HTML5 canvas. This information can be made inaccessible by using the {{ic|--disable-reading-from-canvas}} flag.<br />
<br />
To confirm this is working run [https://panopticlick.eff.org this test] and make sure "hash of canvas fingerprint" is reported as undetermined in the full results.<br />
<br />
{{Note|1=<nowiki></nowiki><br />
* Some extensions require reading from canvas and may be broken by setting {{ic|--disable-reading-from-canvas}}.<br />
* YouTube player does not work properly without canvas reading. [https://github.com/qutebrowser/qutebrowser/issues/5345][https://bbs.archlinux.org/viewtopic.php?pid=1907406]<br />
}}<br />
<br />
==== Privacy extensions ====<br />
<br />
See [[Browser extensions#Privacy]].<br />
<br />
{{Tip|Installing too many extensions might take up much space in the toolbar. Those extensions which you would not interact with anyway (e.g. [https://chrome.google.com/webstore/detail/gcbommkclmclpchllfjekcdonpmejbdp HTTPS Everywhere]) can be hidden by right-clicking on the extension and choosing ''Hide in Chromium menu''.}}<br />
<br />
==== Do Not Track ====<br />
<br />
To enable [[wikipedia:Do Not Track|Do Not Track]], visit {{ic|chrome://settings}}, scroll down to ''Advanced'' and under ''Privacy and security'', check ''Send a "Do Not Track" request with your browsing traffic''.<br />
<br />
==== Force a password store ====<br />
<br />
Chromium uses a password store to store your passwords and the ''Chromium Safe Storage'' key, which is used to encrypt cookie values. [https://codereview.chromium.org/24734007]<br />
<br />
By default Chromium auto-detects which password store to use, which can lead to you apparently losing your passwords and cookies when switching to another desktop environment or window manager.<br />
<br />
You can force Chromium to use a specific password store by launching it with the {{ic|--password-store}} flag with one of following the values [https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md]:<br />
<br />
* {{ic|gnome}}, uses [[Gnome Keyring]]<br />
* {{ic|kwallet5}}, uses [[KDE Wallet]]<br />
* {{ic|basic}}, saves the passwords and the cookies' encryption key as plain text in the file {{ic|Login Data}}<br />
* {{ic|detect}}, the default auto-detect behavior<br />
<br />
For example, to force Chromium to use Gnome Keyring in another desktop or WM use {{ic|1=--password-store=gnome}}, see [[#Making flags persistent]] for making it permanent.<br />
<br />
When using a password store of another desktop environment you probably also want to unlock it automatically. See [[GNOME/Keyring#Using the keyring]] and [[KDE Wallet#Unlock KDE Wallet automatically on login]].<br />
<br />
== Troubleshooting ==<br />
<br />
=== Fonts ===<br />
<br />
{{Note|Chromium does not fully integrate with fontconfig/GTK/Pango/X/etc. due to its sandbox. For more information, see the [https://dev.chromium.org/developers/linux-technical-faq Linux Technical FAQ].}}<br />
<br />
==== Tab font size is too large ====<br />
<br />
Chromium will use the GTK settings as described in [[GTK#Configuration]]. When configured, Chromium will use the {{ic|gtk-font-name}} setting for tabs (which may mismatch window font size). To override these settings, use {{ic|1=--force-device-scale-factor=1.0}}.<br />
<br />
=== WebGL ===<br />
<br />
There is the possibility that your graphics card has been blacklisted by Chromium. See [[#Force GPU acceleration]].<br />
<br />
If you are using Chromium with [[Bumblebee]], WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with {{ic|optirun chromium --disable-gpu-sandbox}}.<br />
<br />
Visit {{ic|chrome://gpu/}} for debugging information about WebGL support.<br />
<br />
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in {{ic|chrome://gpu}} even when you are not using it or primusrun/optirun). Running using a different user directory, e.g, {{ic|1=chromium --user-data-dir=$(mktemp -d)}} may solve this issue. For a persistent solution you can reset the GPU information by deleting {{ic|~/.config/chromium/Local\ State}}.<br />
<br />
=== Incorrect HiDPI rendering ===<br />
<br />
Chromium will automatically scale for a [[HiDPI]] display, however, this may cause an incorrect rendered GUI.<br />
<br />
The flag {{ic|1=--force-device-scale-factor=1}} may be used to overrule the automatic scaling factor.<br />
<br />
When [[#Native Wayland support|native Wayland support]] is enabled, Chromium will automatically scale based on the configured scale of each monitor.<br />
<br />
=== Password prompt on every start with GNOME Keyring ===<br />
<br />
See [[GNOME/Keyring#Passwords are not remembered]].<br />
<br />
=== Chromecasts in the network are not discovered ===<br />
<br />
You will need to enable the Media Router Component Extension in {{ic|chrome://flags/#load-media-router-component-extension}}.<br />
<br />
=== Everything is syncing except for password ===<br />
<br />
If synchronization is not working for password only (you can check it on {{ic|chrome://sync-internals/}}) delete profile login data:<br />
<br />
$ rm ~/.config/chromium/Default/Login\ Data*<br />
<br />
See [https://support.google.com/chrome/thread/9947763?hl=en&msgid=23687608 Google Chrome Help forum] for details.<br />
<br />
=== Losing cookies and passwords when switching between desktop environments ===<br />
<br />
If you see the message {{ic|Failed to decrypt token for service AccountId-*}} in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Hang on startup when Google Sync enabled ===<br />
<br />
Try launching Chrome with {{ic|1=--password-store=basic}} or another appropriate password store.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Chromium asks to be set as the default browser every time it starts ===<br />
<br />
If you are using KDE and have once set Firefox as the default browser (by clicking the button inside Firefox), you might find Chromium asks to be set as the default browser every time it starts, even if you click the "set as default" button.<br />
<br />
Chromium checks for this status by running {{ic|xdg-settings check default-web-browser chromium.desktop}}. If the output is "no", it is not considering itself to be the default browser. The script {{ic|xdg-settings}} checks for the following MIME associations and expect all of them to be {{ic|chromium.desktop}}:<br />
<br />
{{bc|<br />
x-scheme-handler/http<br />
x-scheme-handler/https<br />
text/html}}<br />
<br />
To fix it, go to ''System settings > Applications > Default applications > Web browser'' and choose Chromium. Then, set the MIME association for {{ic|text/html}}:<br />
<br />
$ xdg-mime default chromium.desktop text/html<br />
<br />
Finally, [[XDG_MIME_Applications#New_MIME_types|update the MIME database]]:<br />
<br />
$ update-mime-database ~/.local/share/mime<br />
<br />
=== "This browser or app may not be secure" error logging in to Google ===<br />
<br />
As of 2020.04.20 if you run chromium with {{ic|1=--remote-debugging-port=9222}} flag for web development, you cannot log in to your Google account. Temporarily disable this flag to login and then you can enable it back.<br />
<br />
=== Chromium stuck at 60fps when using a 144Hz + 60Hz monitor ===<br />
<br />
There is a suitable workaround for this issue, [[append]] the following flags to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--use-gl=egl<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
}}<br />
<br />
This should make Chromium run at 144fps when used on your 144hz display, assuming your compositor is refreshing at 144fps. <br />
Keep in mind it might be a little choppy {{Bug|67035}}, but this is way better than it being stuck at 60fps.<br />
<br />
=== Chromium slow scroll speed ===<br />
<br />
Mouse whell scrolling in chromium and electron based applications may be too slow for daily usage. Here are some solutions.<br />
<br />
[[Libinput#Mouse wheel scrolling speed scaling]] injects {{ic|libinput_event_pointer_get_axis_value}} function in libinput and provides an interface to change scale factor. This is not a application level injection, so an addition script for application specific scale factor tuning is needed. Note that scroll on chromium's small height developer tools may be too fast when scale factor is big enough.<br />
<br />
[[IMWheel]] increases scroll distance by replaying X wheel button event for multiple times. However, chromium assumes the real scroll and the replayed ones as two events. There is a small but noticeable delay between them, so one mouse wheel scroll leads to twice page jumps. Also, touchpad scroll needs additional care.<br />
<br />
[https://chrome.google.com/webstore/detail/linux-scroll-speed-fix/mlboohjioameadaedfjcpemcaangkkbp Linux Scroll Speed Fix] and [https://chrome.google.com/webstore/detail/smoothscroll/nbokbjkabcmbfdlbddjidfmibcpneigj SmoothScroll] are two chromium extensions with suppport for scroll distance modification. Upon wheel scroll in a web page, the closest scrollable ancestor of current focused node will be found, then a scroll method with given pixel distance will be called on it, even if it has been scrolled to bottom. So once you scroll into a text editor or any scrollable element, you can never scroll out of it, except moving mouse. Also, extension based methods can not be used outside chromium.<br />
<br />
== See also ==<br />
<br />
* [https://www.chromium.org/ Chromium homepage]<br />
* [https://chromereleases.googleblog.com/ Google Chrome release notes]<br />
* [https://chrome.google.com/webstore/ Chrome web store]<br />
* [[Wikipedia:Chromium (web browser)#Differences from Google Chrome|Differences between Chromium and Google Chrome]]<br />
* [https://peter.sh/experiments/chromium-command-line-switches/ List of Chromium command-line switches]<br />
* [[Profile-sync-daemon]] - Systemd service that saves Chromium profile in tmpfs and syncs to disk<br />
* [[Tmpfs]] - Tmpfs Filesystem in {{ic|/etc/fstab}}<br />
* [https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html Official tmpfs kernel Documentation]</div>Pierro78https://wiki.archlinux.org/index.php?title=Chromium&diff=731912Chromium2022-06-07T11:58:25Z<p>Pierro78: /* Tips and tricks */ added "Not yet, AV1" extension as seen on https://bbs.archlinux.org/viewtopic.php?pid=2039884#p2039884</p>
<hr />
<div>[[Category:Web browser]]<br />
[[Category:Google]]<br />
[[de:Chromium]]<br />
[[ja:Chromium]]<br />
[[zh-hans:Chromium]]<br />
{{Related articles start}}<br />
{{Related|Browser extensions}}<br />
{{Related|Firefox}}<br />
{{Related|Opera}}<br />
{{Related|Vivaldi}}<br />
{{Related articles end}}<br />
<br />
[[Wikipedia:Chromium (web browser)|Chromium]] is an open-source graphical web browser based on the [[Wikipedia:Blink (web engine)|Blink]] rendering engine. It is the basis for the proprietary Google Chrome browser.<br />
<br />
See [https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md this page] for an explanation of the differences between Chromium and Google Chrome. Additionally:<br />
<br />
* Sync is unavailable in Chromium 89+ (2021-03-02) [https://archlinux.org/news/chromium-losing-sync-support-in-early-march/]<br />
<br />
{{Note|Sync can be temporarily restored by [https://gist.github.com/foutrelis/14e339596b89813aa9c37fd1b4e5d9d5 using Chrome's OAuth2 credentials] or [https://www.chromium.org/developers/how-tos/api-keys getting your own], but pay attention to the disclaimers and do not consider this to be a long-term solution.<br />
Consider switching to [https://www.xbrowsersync.org xbrowsersync] for bookmarks syncing as long term solution.<br />
}}<br />
<br />
See [[List of applications/Internet#Blink-based]] for other browsers based on Chromium.<br />
<br />
== Installation ==<br />
<br />
There are several packages available to [[install]] Chromium with:<br />
<br />
* {{Pkg|chromium}} — stable release;<br />
* {{AUR|chromium-dev}} — development release;<br />
* {{AUR|chromium-snapshot-bin}} — nightly build.<br />
<br />
Google Chrome packages:<br />
<br />
* {{AUR|google-chrome}} — stable release;<br />
* {{AUR|google-chrome-beta}} — beta release;<br />
* {{AUR|google-chrome-dev}} — development release.<br />
<br />
{{Note|From the [https://www.chromium.org/Home/chromium-privacy Chromium privacy page]: "Features that communicate with Google made available through the compilation of code in Chromium are subject to the [https://www.google.com/policies/privacy/ Google Privacy Policy]." For those who want to avoid all integration with Google services, there are some [[List of applications/Internet#Privacy-focused chromium spin-offs|privacy-focused spin-offs]].}}<br />
<br />
== Configuration ==<br />
<br />
=== Default applications ===<br />
<br />
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see [[default applications]].<br />
<br />
=== Certificates ===<br />
<br />
Chromium uses [[Network Security Services]] for certificate management. Certificates can be managed in {{ic|chrome://settings/certificates}}.<br />
<br />
=== Making flags persistent ===<br />
<br />
{{Note|The {{ic|chromium-flags.conf}} file and the accompanying custom launcher script are specific to the Arch Linux {{Pkg|chromium}} package. For {{AUR|google-chrome}} and {{AUR|google-chrome-dev}}, use {{ic|chrome-flags.conf}} and {{ic|chrome-dev-flags.conf}} instead.}}<br />
<br />
You can put your flags in a {{ic|chromium-flags.conf}} file under {{ic|$HOME/.config/}} (or under {{ic|$XDG_CONFIG_HOME}} if you have configured that environment variable).<br />
<br />
No special syntax is used; flags are defined as if they were written in a terminal.<br />
<br />
* The arguments are split on whitespace and shell quoting rules apply, but no further parsing is performed.<br />
* In case of improper quoting anywhere in the file, a fatal error is raised.<br />
* Flags can be placed in separate lines for readability, but this is not required.<br />
* Lines starting with a hash symbol (#) are skipped. (This is only supported by the {{Pkg|chromium}} launcher script and will not work when using {{ic|chrome-flags.conf}} with the {{AUR|google-chrome}} package.)<br />
<br />
Below is an example {{ic|chromium-flags.conf}} file that defines the flags {{ic|--start-maximized --incognito}}:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
# This line will be ignored.<br />
--start-maximized<br />
--incognito<br />
}}<br />
<br />
=== Force GPU acceleration ===<br />
<br />
{{Warning|Disabling the rendering blacklist may cause unstable behavior, including crashes of the host. See the bug reports in {{ic|chrome://gpu}} for details.}}<br />
<br />
By default Chromium on Linux does not use any GPU acceleration. To force GPU acceleration, [[append]] the following flags to [[/Tips and tricks#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|~/.config/chromium-flags.conf|<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
--enable-zero-copy<br />
}}<br />
<br />
Additionally the flag {{ic|--disable-gpu-driver-bug-workarounds}} may need to be passed to prevent GPU workaround from being used. Flags in {{ic|chrome://gpu}} should state "Hardware accelerated" when configured and available.<br />
<br />
{{Out of date|A fix has been merged into mesa as of May 2021. [https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10850]}}<br />
<br />
{{ic|--enable-native-gpu-memory-buffers}} is broken since mesa 20.1.1 [https://gitlab.freedesktop.org/mesa/mesa/-/issues/3119#note_533902]<br />
<br />
=== Hardware video acceleration ===<br />
<br />
{{Note|1=<nowiki/><br />
* There is no official support from Chromium or Arch Linux for this feature [https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/vaapi.md#vaapi-on-linux]. However, {{Pkg|chromium}} from official repositories is compiled with VA-API support and you may ask for help in [https://bbs.archlinux.org/viewtopic.php?id=244031 the dedicated forum thread].<br />
* VA-API does not work with the {{Pkg|chromium}} package when using the native Wayland backend, but it does work in {{AUR|chromium-wayland-vaapi}}.<br />
}}<br />
<br />
To enable VA-API support in Chromium:<br />
<br />
* Install the correct VA-API driver for your video card and verify VA-API has been enabled and working correctly, see [[Hardware video acceleration]]. For proprietary NVIDIA support, installing {{AUR|libva-vdpau-driver-chromium}} or {{AUR|libva-vdpau-driver-vp9-git}} is required.<br />
* Set the option {{ic|1=--enable-features=VaapiVideoDecoder}}. This is enough when using ANGLE GL renderer and {{Pkg|libva-intel-driver}}.<br />
* When using ANGLE, Chromium forces the older i965 driver and fails when {{Pkg|intel-media-driver}} is used. As a workaround, [[Hardware video acceleration#Configuring VA-API|configure VA-API manually]]. See [https://github.com/intel/media-driver/issues/818] for details.<br />
* To use the system GL renderer on Xorg, use either {{ic|1=--use-gl=egl}} or {{ic|1=--use-gl=desktop}}. On XWayland, use the {{ic|1=--use-gl=egl}} flag (Currently exhibits choppiness {{Bug|67035}} on some systems).<br />
* If VA-API still does not work, try the {{ic|1=--disable-features=UseChromeOSDirectVideoDecoder}} flag [https://bbs.archlinux.org/viewtopic.php?pid=2021090#p2021090]<br />
<br />
==== Tips and tricks ====<br />
<br />
To check if it is working play a video which is using a codec supported by your VA-API driver (''vainfo'' tells you which codecs are supported, but Chromium will only support VP9 and h264):<br />
<br />
* Open the DevTools by pressing {{ic|Ctrl+Shift+I}} or on the ''Inspect'' button of the context (right-click) menu<br />
* Add the Media inspection tab: ''Hamburger menu > More tools > Media''<br />
* In the newly opened Media tab, look at the hardware decoder state of the video decoder<br />
<br />
Test on a large enough video. Starting with version 86, Chromium on desktop [https://bugs.chromium.org/p/chromium/issues/detail?id=684792 will only accelerate videos larger than 720p].<br />
<br />
To reduce CPU usage while watching YouTube where VP8/VP9 hardware decoding is not available use the [https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal h264ify] or [https://chrome.google.com/webstore/detail/enhanced-h264ify/omkfmpieigblcllmkgbflkikinpkodlk enhanced-h264ify] or [[https://chrome.google.com/webstore/detail/not-yet-av1/dcmllfkiihingappljlkffafnlhdpbai?hl=en Not yet, AV1]] extension.<br />
<br />
On some systems (especially on XWayland) you might need to [[#Force GPU acceleration]]. Only {{ic|--ignore-gpu-blocklist}} is enough for our purposes.<br />
<br />
{{Expansion|Provide a link to some bug report.}}<br />
<br />
You might need to disable the Skia renderer, as it is currently not compatible with video decode acceleration: {{ic|1=--disable-features=UseSkiaRenderer}}<br />
<br />
=== PDF viewer plugin ===<br />
<br />
Chromium and Google Chrome are bundled with the ''Chromium PDF Viewer'' plugin. If you do not want to use this plugin, check ''Download PDFs'' in {{ic|chrome://settings/content/pdfDocuments}}.<br />
<br />
=== Flash Player plugin ===<br />
<br />
Support for Flash Player was removed in Chromium 88.[https://www.chromium.org/flash-roadmap#TOC-Flash-Support-Removed-from-Chromium-Target:-Chrome-88---Jan-2021-]<br />
<br />
=== Running on XWayland ===<br />
<br />
If you are using NVIDIA's proprietary driver, running Chromium on XWayland may cause the GPU process to occasionally crash. To prevent the GPU process from crashing, add the following flags:<br />
<br />
--use-angle=vulkan --use-cmd-decoder=passthrough<br />
<br />
{{Note|This does not prevent all XWayland-related crashes.}}<br />
<br />
=== Native Wayland support ===<br />
<br />
Since version 97, native [[Wayland]] support in Chromium can be enabled with the following flags [https://chromium.googlesource.com/chromium/src/+/43cfb2f92a5cdc1a787d7326e74676884abf5052]:<br />
<br />
--ozone-platform-hint=auto<br />
<br />
See [[#Making flags persistent]] for a permanent configuration. The flag is also available via [[#chrome://_URLs|browser flags menu]].<br />
<br />
This will select wayland Ozone backend when in wayland session, so you can use a single desktop entry if you switch between X11 and Wayland often.<br />
<br />
== Tips and tricks ==<br />
<br />
The following tips and tricks should work for both Chromium and Chrome unless explicitly stated.<br />
<br />
=== Browsing experience ===<br />
<br />
==== chrome:// URLs ====<br />
<br />
A number of tweaks can be accessed via Chrome URLs. See '''chrome://chrome-urls''' for a complete list.<br />
<br />
* '''chrome://flags''' - access experimental features such as WebGL and rendering webpages with GPU, etc.<br />
* '''chrome://extensions''' - view, enable and disable the currently used Chromium extensions.<br />
* '''chrome://gpu''' - status of different GPU options.<br />
* '''chrome://sandbox''' - indicate sandbox status.<br />
* '''chrome://version''' - display version and switches used to invoke the active {{ic|/usr/bin/chromium}}.<br />
<br />
An automatically updated, complete listing of Chromium switches (command line parameters) is available [https://peter.sh/experiments/chromium-command-line-switches/ here].<br />
<br />
==== Chromium task manager ====<br />
<br />
Shift+ESC can be used to bring up the browser task manager wherein memory, CPU, and network usage can be viewed.<br />
<br />
==== Chromium overrides/overwrites Preferences file ====<br />
<br />
If you enabled syncing with a Google Account, then Chromium will override any direct edits to the Preferences file found under {{ic|~/.config/chromium/Default/Preferences}}. To work around this, start Chromium with the {{ic|--disable-sync-preferences}} switch:<br />
$ chromium --disable-sync-preferences<br />
<br />
If Chromium is started in the background when you login in to your desktop environment, make sure the command your desktop environment uses is:<br />
$ chromium --disable-sync-preferences --no-startup-window<br />
<br />
==== Search engines ====<br />
<br />
Make sites like [https://wiki.archlinux.org wiki.archlinux.org] and [https://en.wikipedia.org wikipedia.org] easily searchable by first executing a search on those pages, then going to ''Settings > Search'' and click the ''Manage search engines..'' button. From there, "Edit" the Wikipedia entry and change its keyword to '''w''' (or some other shortcut you prefer). Now searching Wikipedia for "Arch Linux" from the address bar is done simply by entering "'''w arch linux'''".<br />
<br />
{{Note| Google search is used automatically when typing something into the URL bar. A hard-coded keyword trigger is also available using the '''?''' prefix.}}<br />
<br />
==== Tmpfs ====<br />
<br />
===== Cache in tmpfs =====<br />
<br />
{{Note|Chromium stores its cache separate from its browser profile directory.}}<br />
<br />
To limit Chromium from writing its cache to a physical disk, one can define an alternative location via the {{ic|--disk-cache-dir}} flag:<br />
$ chromium --disk-cache-dir="$XDG_RUNTIME_DIR/chromium-cache"<br />
<br />
Cache should be considered temporary and will '''not''' be saved after a reboot or hard lock. Another option is to setup the space in {{ic|/etc/fstab}}:<br />
<br />
{{hc|/etc/fstab|2=<br />
tmpfs /home/''username''/.cache tmpfs noatime,nodev,nosuid,size=400M 0 0<br />
}}<br />
<br />
===== Profile in tmpfs =====<br />
<br />
Relocate the browser profile to a [[Wikipedia:Tmpfs|tmpfs]] filesystem, including {{ic|/tmp}}, or {{ic|/dev/shm}} for improvements in application response as the entire profile is now stored in RAM.<br />
<br />
Use an active profile management tool such as {{Pkg|profile-sync-daemon}} for maximal reliability and ease of use. It symlinks or bind mounts and syncs the browser profile directories to RAM. For more, see [[Profile-sync-daemon]].<br />
<br />
==== Launch a new browser instance ====<br />
<br />
When you launch the browser, it first checks if another instance using the same data directory is already running. If there is one, the new window is associated with the old instance. If you want to launch an independent instance of the browser, you must specify separate directory using the {{ic|--user-data-dir}} parameter:<br />
<br />
$ chromium --user-data-dir=''/path/to/some/directory''<br />
<br />
{{Note|The default location of the user data is {{ic|~/.config/chromium/}}.}}<br />
<br />
==== Directly open *.torrent files and magnet links with a torrent client ====<br />
<br />
By default, Chromium downloads {{ic|*.torrent}} files directly and you need to click the notification from the bottom-left corner of the screen in order for the file to be opened with your default torrent client. This can be avoided with the following method:<br />
<br />
* Download a {{ic|*.torrent}} file.<br />
* Right-click the notification displayed at the bottom-left corner of the screen.<br />
* Check the "''Always Open Files of This Type''" checkbox.<br />
<br />
See [[xdg-open]] to change the default assocation.<br />
<br />
==== Touch Scrolling on touchscreen devices ====<br />
<br />
You may need to specify which touch device to use. Find your touchscreen device with {{ic| xinput list}} then launch Chromium with the {{ic|1=--touch-devices='''x'''}} parameter, where "'''x'''" is the id of your device. {{Note|If the device is designated as a slave pointer, using this may not work, use the master pointer's ID instead.}}<br />
<br />
==== Reduce memory usage ====<br />
<br />
By default, Chromium uses a separate OS process for each ''instance'' of a visited web site. [https://www.chromium.org/developers/design-documents/process-models#Supported_Models] However, you can specify command-line switches when starting Chromium to modify this behaviour.<br />
<br />
For example, to share one process for all instances of a website:<br />
<br />
$ chromium --process-per-site<br />
<br />
To use a single process model:<br />
<br />
$ chromium --single-process<br />
<br />
{{Warning|The single-process model is discouraged because it is unsafe and may contain bugs not present in other models.[https://www.chromium.org/developers/design-documents/process-models#TOC-Single-process]}}<br />
<br />
In addition, you can suspend or store inactive Tabs with extensions such as [https://chrome.google.com/webstore/detail/tab-suspender/fiabciakcmgepblmdkmemdbbkilneeeh?hl=en Tab Suspender] and [https://chrome.google.com/webstore/detail/onetab/chphlpgkkbolifaimnlloiipkdnihall?hl=en OneTab].<br />
<br />
==== User Agent ====<br />
<br />
The User Agent can be arbitrarily modified at the start of Chromium's base instance via its {{Ic|<nowiki>--user-agent="[string]"</nowiki>}} parameter.<br />
<br />
==== DOM Distiller ====<br />
<br />
Chromium has a similar reader mode to Firefox. In this case it is called DOM Distiller, which is an [https://github.com/chromium/dom-distiller open source project].<br />
It is disabled by default, but can be enabled using the {{Ic|chrome://flags/#enable-reader-mode}} flag, which you can also make [[#Making flags persistent|persistent]].<br />
Not only does DOM Distiller provide a better reading experience by distilling the content of the page, it also simplifies pages for print. Even though the latter checkbox option has been removed from the print dialog, you can still print the distilled page, which basically has the same effect.<br />
<br />
After enabling the flag, you will find a new "Enter reader mode" menu item and corresponding icon in the address bar when Chromium thinks the website you are visiting could do with some distilling.<br />
<br />
==== Forcing specific GPU ====<br />
<br />
In multi-GPU systems, Chromium automatically detects which GPU should be used for rendering (discrete or integrated). This works 99% of the time, except when it does not - if a unavailable GPU is picked (for example, discrete graphics on VFIO GPU passthrough-enabled systems), {{ic|chrome://gpu}} will complain about not being able to initialize the GPU process. On the same page below '''Driver Information''' there will be multiple GPUs shown (GPU0, GPU1, ...). There is no way to switch between them in a user-friendly way, but you can read the device/vendor IDs present there and configure Chromium to use a specific GPU with flags:<br />
<br />
$ chromium --gpu-testing-vendor-id=0x8086 --gpu-testing-device-id=0x1912<br />
<br />
...where {{ic|0x8086}} and {{ic|0x1912}} is replaced by the IDs of the GPU you want to use (as shown on the {{ic|chrome://gpu}} page).<br />
<br />
==== Import bookmarks from Firefox ====<br />
<br />
To ease the transition, you can import bookmarks from [[Firefox]] into Chromium.<br />
<br />
Navigate Chromium to {{ic|chrome://settings/importData}}<br />
<br />
If Firefox is already installed on your computer, you can directly import bookmarks as well as many other things from Firefox.<br />
<br />
Make sure '''Mozilla Firefox''' is selected. Optionally, you can uncheck some unwanted items here. Click the '''Import''' and then '''Done'''. You are done with it.<br />
<br />
{{note|If you have not created any bookmarks in Chromium yet, the bookmarks will show up in your bookmarks bar. If you already have bookmarks, the bookmarks will be in a new folder labeled "Imported From Firefox"}}<br />
<br />
If you import bookmarks from another PC, you have to export bookmarks from Firefox first.<br />
<br />
{{ic|''Ctrl + Shift + O > Import and Backup > Export Bookmarks To HTML}} in Firefox''<br />
<br />
The procedure is pretty much the same. You need to go to {{ic|chrome://settings/importData}}. However, this time, in the '''From''' drop-down menu, select '''Bookmarks HTML File''' and click the '''Choose File''' button and upload the desired bookmark file.<br />
<br />
==== Enabling native notifications ====<br />
<br />
Go to {{ic|chrome://flags#enable-system-notifications}} and select ''Enabled''.<br />
<br />
==== U2F authentication ====<br />
<br />
Install {{Pkg|libfido2}} library. This provides the udev rules required to enable access to the [[U2F]] key as a user.<br />
U2F keys are by default only accessible by root, and without these rules Chromium will give an error.<br />
<br />
==== Dark mode ====<br />
<br />
To enable dark mode (used in ''prefers-color-scheme'' in CSS, JavaScript, Settings and Dev-Tools) and enable the dark theme (normally used for incognito mode) [[append]] the following flag to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--force-dark-mode<br />
--enable-features=WebUIDarkMode<br />
}}<br />
<br />
===== Dark mode by system preference =====<br />
<br />
[https://bugs.chromium.org/p/chromium/issues/detail?id=998903 This Chromium issue] aims to bring dark mode based on GTK theme selection into Chromium.<br />
<br />
In the future, all that will be required to properly use system preference, is setting ''Designs'' to GTK in {{ic|chrome://settings/appearance}}.<br />
<br />
==== Enable Side Panel ====<br />
<br />
The Side Panel can be enabled through {{ic|chrome://flags}}. You can enable or disable '''Side panel''', and change options such as '''Side panel border''' and '''Side panel drag and drop'''.<br />
<br />
=== Profile maintenance ===<br />
<br />
Chromium uses [[SQLite]] databases to manage history and the like. Sqlite databases become fragmented over time and empty spaces appear all around. But, since there are no managing processes checking and optimizing the database, these factors eventually result in a performance hit. A good way to improve startup and some other bookmarks- and history-related tasks is to defragment and trim unused space from these databases.<br />
<br />
{{Pkg|profile-cleaner}} and {{AUR|browser-vacuum}} in the [[AUR]] do just this.<br />
<br />
=== Security ===<br />
<br />
==== Disable JIT ====<br />
<br />
At the cost of reduced performance, you can disable just-in-time compilation of JavaScript to native code, which is responsible for [https://microsoftedge.github.io/edgevr/posts/Super-Duper-Secure-Mode/ roughly half of the security vulnerabilities in the JS engine], using the flag {{ic|1=--js-flags=--jitless}}.<br />
<br />
==== WebRTC ====<br />
<br />
WebRTC is a communication protocol that relies on JavaScript that can leak one's actual IP address and hardware hash from behind a VPN. While some software may prevent the leaking scripts from running, it is probably a good idea to block this protocol directly as well, just to be safe. As of October 2016, there is no way to disable WebRTC on Chromium on desktop, there are extensions available to disable local IP address leak, one is this [https://chrome.google.com/webstore/detail/webrtc-network-limiter/npeicpdbkakmehahjeeohfdhnlpdklia extension].<br />
<br />
One can test WebRTC via https://browserleaks.com/webrtc.<br />
<br />
{{Warning|Even though IP leak can be prevented, Chromium still sends your unique hash, and there is no way to prevent this. Read more on https://www.browserleaks.com/webrtc#webrtc-disable}}<br />
<br />
==== SSL certificates ====<br />
<br />
Chromium does not have an SSL certificate manager. It relies on the NSS Shared DB {{ic|~/.pki/nssdb}}. In order to add SSL certificates to the database, users will have to use the shell.<br />
<br />
===== Adding CAcert certificates for self-signed certificates =====<br />
<br />
Grab the CAcerts and create an {{ic|nssdb}}, if one does not already exist. To do this, first install the {{Pkg|nss}} package, then complete these steps:<br />
<br />
$ mkdir -p $HOME/.pki/nssdb<br />
$ cd $HOME/.pki/nssdb<br />
$ certutil -N -d sql:.<br />
<br />
$ curl -k -o "cacert-root.crt" "http://www.cacert.org/certs/root.crt"<br />
$ curl -k -o "cacert-class3.crt" "http://www.cacert.org/certs/class3.crt"<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org" -i cacert-root.crt <br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "CAcert.org Class 3" -i cacert-class3.crt<br />
<br />
{{Note|Users will need to create a password for the database, if it does not exist.}}<br />
<br />
Now users may manually import a self-signed certificate.<br />
<br />
===== Example 1: Using a shell script to isolate the certificate from TomatoUSB =====<br />
<br />
Below is a simple script that will extract and add a certificate to the user's {{ic|nssdb}}:<br />
<br />
#!/bin/sh<br />
#<br />
# usage: import-cert.sh remote.host.name [port]<br />
#<br />
REMHOST=$1<br />
REMPORT=${2:-443}<br />
exec 6>&1<br />
exec > $REMHOST<br />
echo | openssl s_client -connect ${REMHOST}:${REMPORT} 2>&1 |sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p'<br />
certutil -d sql:$HOME/.pki/nssdb -A -t "P,," -n "$REMHOST" -i $REMHOST <br />
exec 1>&6 6>&-<br />
<br />
Syntax is advertised in the commented lines.<br />
<br />
References:<br />
*https://web.archive.org/web/20180718193807/https://blog.avirtualhome.com/adding-ssl-certificates-to-google-chrome-linux-ubuntu<br />
*https://chromium.googlesource.com/chromium/src/+/master/docs/linux/cert_management.md<br />
<br />
===== Example 2: Using Firefox to isolate the certificate from TomatoUSB =====<br />
<br />
The {{Pkg|firefox}} browser can be used to save the certificate to a file for manual import into the database.<br />
<br />
Using firefox:<br />
#Browse to the target URL.<br />
#Upon seeing the "This Connection is Untrusted" warning screen, click: ''I understand the Risks > Add Exception...''<br />
#Click: ''View > Details > Export'' and save the certificate to a temporary location ({{ic|/tmp/easy.pem}} in this example).<br />
<br />
Now import the certificate for use in Chromium:<br />
$ certutil -d sql:$HOME/.pki/nssdb -A -t TC -n "easy" -i /tmp/easy.pem<br />
<br />
{{Note|Adjust the name to match that of the certificate. In the example above, "easy" is the name of the certificate.}}<br />
<br />
Reference:<br />
*https://sahissam.blogspot.com/2012/06/new-ssl-certificates-for-tomatousb-and.html<br />
<br />
==== Canvas Fingerprinting ====<br />
<br />
Canvas fingerprinting is a technique that allows websites to identify users by detecting differences when rendering to an HTML5 canvas. This information can be made inaccessible by using the {{ic|--disable-reading-from-canvas}} flag.<br />
<br />
To confirm this is working run [https://panopticlick.eff.org this test] and make sure "hash of canvas fingerprint" is reported as undetermined in the full results.<br />
<br />
{{Note|1=<nowiki></nowiki><br />
* Some extensions require reading from canvas and may be broken by setting {{ic|--disable-reading-from-canvas}}.<br />
* YouTube player does not work properly without canvas reading. [https://github.com/qutebrowser/qutebrowser/issues/5345][https://bbs.archlinux.org/viewtopic.php?pid=1907406]<br />
}}<br />
<br />
==== Privacy extensions ====<br />
<br />
See [[Browser extensions#Privacy]].<br />
<br />
{{Tip|Installing too many extensions might take up much space in the toolbar. Those extensions which you would not interact with anyway (e.g. [https://chrome.google.com/webstore/detail/gcbommkclmclpchllfjekcdonpmejbdp HTTPS Everywhere]) can be hidden by right-clicking on the extension and choosing ''Hide in Chromium menu''.}}<br />
<br />
==== Do Not Track ====<br />
<br />
To enable [[wikipedia:Do Not Track|Do Not Track]], visit {{ic|chrome://settings}}, scroll down to ''Advanced'' and under ''Privacy and security'', check ''Send a "Do Not Track" request with your browsing traffic''.<br />
<br />
==== Force a password store ====<br />
<br />
Chromium uses a password store to store your passwords and the ''Chromium Safe Storage'' key, which is used to encrypt cookie values. [https://codereview.chromium.org/24734007]<br />
<br />
By default Chromium auto-detects which password store to use, which can lead to you apparently losing your passwords and cookies when switching to another desktop environment or window manager.<br />
<br />
You can force Chromium to use a specific password store by launching it with the {{ic|--password-store}} flag with one of following the values [https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md]:<br />
<br />
* {{ic|gnome}}, uses [[Gnome Keyring]]<br />
* {{ic|kwallet5}}, uses [[KDE Wallet]]<br />
* {{ic|basic}}, saves the passwords and the cookies' encryption key as plain text in the file {{ic|Login Data}}<br />
* {{ic|detect}}, the default auto-detect behavior<br />
<br />
For example, to force Chromium to use Gnome Keyring in another desktop or WM use {{ic|1=--password-store=gnome}}, see [[#Making flags persistent]] for making it permanent.<br />
<br />
When using a password store of another desktop environment you probably also want to unlock it automatically. See [[GNOME/Keyring#Using the keyring]] and [[KDE Wallet#Unlock KDE Wallet automatically on login]].<br />
<br />
== Troubleshooting ==<br />
<br />
=== Fonts ===<br />
<br />
{{Note|Chromium does not fully integrate with fontconfig/GTK/Pango/X/etc. due to its sandbox. For more information, see the [https://dev.chromium.org/developers/linux-technical-faq Linux Technical FAQ].}}<br />
<br />
==== Tab font size is too large ====<br />
<br />
Chromium will use the GTK settings as described in [[GTK#Configuration]]. When configured, Chromium will use the {{ic|gtk-font-name}} setting for tabs (which may mismatch window font size). To override these settings, use {{ic|1=--force-device-scale-factor=1.0}}.<br />
<br />
=== WebGL ===<br />
<br />
There is the possibility that your graphics card has been blacklisted by Chromium. See [[#Force GPU acceleration]].<br />
<br />
If you are using Chromium with [[Bumblebee]], WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with {{ic|optirun chromium --disable-gpu-sandbox}}.<br />
<br />
Visit {{ic|chrome://gpu/}} for debugging information about WebGL support.<br />
<br />
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in {{ic|chrome://gpu}} even when you are not using it or primusrun/optirun). Running using a different user directory, e.g, {{ic|1=chromium --user-data-dir=$(mktemp -d)}} may solve this issue. For a persistent solution you can reset the GPU information by deleting {{ic|~/.config/chromium/Local\ State}}.<br />
<br />
=== Incorrect HiDPI rendering ===<br />
<br />
Chromium will automatically scale for a [[HiDPI]] display, however, this may cause an incorrect rendered GUI.<br />
<br />
The flag {{ic|1=--force-device-scale-factor=1}} may be used to overrule the automatic scaling factor.<br />
<br />
When [[#Native Wayland support|native Wayland support]] is enabled, Chromium will automatically scale based on the configured scale of each monitor.<br />
<br />
=== Password prompt on every start with GNOME Keyring ===<br />
<br />
See [[GNOME/Keyring#Passwords are not remembered]].<br />
<br />
=== Chromecasts in the network are not discovered ===<br />
<br />
You will need to enable the Media Router Component Extension in {{ic|chrome://flags/#load-media-router-component-extension}}.<br />
<br />
=== Everything is syncing except for password ===<br />
<br />
If synchronization is not working for password only (you can check it on {{ic|chrome://sync-internals/}}) delete profile login data:<br />
<br />
$ rm ~/.config/chromium/Default/Login\ Data*<br />
<br />
See [https://support.google.com/chrome/thread/9947763?hl=en&msgid=23687608 Google Chrome Help forum] for details.<br />
<br />
=== Losing cookies and passwords when switching between desktop environments ===<br />
<br />
If you see the message {{ic|Failed to decrypt token for service AccountId-*}} in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Hang on startup when Google Sync enabled ===<br />
<br />
Try launching Chrome with {{ic|1=--password-store=basic}} or another appropriate password store.<br />
<br />
See [[#Force a password store]].<br />
<br />
=== Chromium asks to be set as the default browser every time it starts ===<br />
<br />
If you are using KDE and have once set Firefox as the default browser (by clicking the button inside Firefox), you might find Chromium asks to be set as the default browser every time it starts, even if you click the "set as default" button.<br />
<br />
Chromium checks for this status by running {{ic|xdg-settings check default-web-browser chromium.desktop}}. If the output is "no", it is not considering itself to be the default browser. The script {{ic|xdg-settings}} checks for the following MIME associations and expect all of them to be {{ic|chromium.desktop}}:<br />
<br />
{{bc|<br />
x-scheme-handler/http<br />
x-scheme-handler/https<br />
text/html}}<br />
<br />
To fix it, go to ''System settings > Applications > Default applications > Web browser'' and choose Chromium. Then, set the MIME association for {{ic|text/html}}:<br />
<br />
$ xdg-mime default chromium.desktop text/html<br />
<br />
Finally, [[XDG_MIME_Applications#New_MIME_types|update the MIME database]]:<br />
<br />
$ update-mime-database ~/.local/share/mime<br />
<br />
=== "This browser or app may not be secure" error logging in to Google ===<br />
<br />
As of 2020.04.20 if you run chromium with {{ic|1=--remote-debugging-port=9222}} flag for web development, you cannot log in to your Google account. Temporarily disable this flag to login and then you can enable it back.<br />
<br />
=== Chromium stuck at 60fps when using a 144Hz + 60Hz monitor ===<br />
<br />
There is a suitable workaround for this issue, [[append]] the following flags to [[#Making flags persistent|persistent configuration]]:<br />
<br />
{{hc|1=~/.config/chromium-flags.conf|2=<br />
--use-gl=egl<br />
--ignore-gpu-blocklist<br />
--enable-gpu-rasterization<br />
}}<br />
<br />
This should make Chromium run at 144fps when used on your 144hz display, assuming your compositor is refreshing at 144fps. <br />
Keep in mind it might be a little choppy {{Bug|67035}}, but this is way better than it being stuck at 60fps.<br />
<br />
=== Chromium slow scroll speed ===<br />
<br />
Mouse whell scrolling in chromium and electron based applications may be too slow for daily usage. Here are some solutions.<br />
<br />
[[Libinput#Mouse wheel scrolling speed scaling]] injects {{ic|libinput_event_pointer_get_axis_value}} function in libinput and provides an interface to change scale factor. This is not a application level injection, so an addition script for application specific scale factor tuning is needed. Note that scroll on chromium's small height developer tools may be too fast when scale factor is big enough.<br />
<br />
[[IMWheel]] increases scroll distance by replaying X wheel button event for multiple times. However, chromium assumes the real scroll and the replayed ones as two events. There is a small but noticeable delay between them, so one mouse wheel scroll leads to twice page jumps. Also, touchpad scroll needs additional care.<br />
<br />
[https://chrome.google.com/webstore/detail/linux-scroll-speed-fix/mlboohjioameadaedfjcpemcaangkkbp Linux Scroll Speed Fix] and [https://chrome.google.com/webstore/detail/smoothscroll/nbokbjkabcmbfdlbddjidfmibcpneigj SmoothScroll] are two chromium extensions with suppport for scroll distance modification. Upon wheel scroll in a web page, the closest scrollable ancestor of current focused node will be found, then a scroll method with given pixel distance will be called on it, even if it has been scrolled to bottom. So once you scroll into a text editor or any scrollable element, you can never scroll out of it, except moving mouse. Also, extension based methods can not be used outside chromium.<br />
<br />
== See also ==<br />
<br />
* [https://www.chromium.org/ Chromium homepage]<br />
* [https://chromereleases.googleblog.com/ Google Chrome release notes]<br />
* [https://chrome.google.com/webstore/ Chrome web store]<br />
* [[Wikipedia:Chromium (web browser)#Differences from Google Chrome|Differences between Chromium and Google Chrome]]<br />
* [https://peter.sh/experiments/chromium-command-line-switches/ List of Chromium command-line switches]<br />
* [[Profile-sync-daemon]] - Systemd service that saves Chromium profile in tmpfs and syncs to disk<br />
* [[Tmpfs]] - Tmpfs Filesystem in {{ic|/etc/fstab}}<br />
* [https://www.kernel.org/doc/html/latest/filesystems/tmpfs.html Official tmpfs kernel Documentation]</div>Pierro78https://wiki.archlinux.org/index.php?title=Talk:PHC&diff=614764Talk:PHC2020-05-21T23:32:40Z<p>Pierro78: /* phc-intel setup (or phc-k8 setup) not needed anymore */</p>
<hr />
<div>november 2009, seems that acpi_cpufreq was replaced by phc-intel module.<br />
<br />
that's why the tutorial won't work for intel cpu's anymore.<br />
<br />
----<br />
now we NEED person to test it<br />
<br />
for reporting cpus supported<br />
<br />
and<br />
<br />
how config it<br />
<br />
----<br />
Yaourt is not the AUR's client. It is an unsupported third party tool. - [[User:Louipc|louipc]] 09:32, 7 August 2009 (EDT)<br />
<br />
----<br />
<br />
phctool doesn't work any more... You need more explain about Voltage controlling without gui tool! ;) linux-phc-optimize script from AUR doesn't work eather, there's link for working script in comments... Please change this... ;) Pyntux<br />
<br />
----<br />
==himself vs. herself==<br />
Buhman, I am not a native English speaker but know for a fact that alternating between genders in documentation is something that is frequently done in order to make the documentation “gender neutral” (in a sense.) When you changed “herself” to “himself” the previous time, I asked a native (American) English speaker and he confirmed this to me. “himself” is not gender neutral, it’s masculine.<br />
Alternatively, it is possible to use “users … themselves” instead of alternating genders. [[User:Stqn|Stqn]] ([[User talk:Stqn|talk]]) 17:34, 8 December 2012 (UTC)<br />
<br />
== phc-intel setup (or phc-k8 setup) not needed anymore ==<br />
<br />
as told in https://bbs.archlinux.org/viewtopic.php?pid=1786330#p1786330 phc-intel setup (or phc-k8 setup) is not needed anymore<br />
<br />
On a machine (i7 1st gen) I had the phc_intel kernel module loaded after a reboot but I can't have it loaded on another machine (although modinfo phc_intel shows that the module has been built correctly) (but this machine has a sandy brige i5 2nd gen and apparently it uses intel pstate which is not compatible with phc-intel)<br />
<br />
[[User:Pierro78|Pierro78]] ([[User talk:Pierro78|talk]]) 22:06, 21 May 2020 (UTC)</div>Pierro78https://wiki.archlinux.org/index.php?title=Talk:PHC&diff=614761Talk:PHC2020-05-21T22:59:02Z<p>Pierro78: /* phc-intel setup (or phc-k8 setup) not needed anymore */</p>
<hr />
<div>november 2009, seems that acpi_cpufreq was replaced by phc-intel module.<br />
<br />
that's why the tutorial won't work for intel cpu's anymore.<br />
<br />
----<br />
now we NEED person to test it<br />
<br />
for reporting cpus supported<br />
<br />
and<br />
<br />
how config it<br />
<br />
----<br />
Yaourt is not the AUR's client. It is an unsupported third party tool. - [[User:Louipc|louipc]] 09:32, 7 August 2009 (EDT)<br />
<br />
----<br />
<br />
phctool doesn't work any more... You need more explain about Voltage controlling without gui tool! ;) linux-phc-optimize script from AUR doesn't work eather, there's link for working script in comments... Please change this... ;) Pyntux<br />
<br />
----<br />
==himself vs. herself==<br />
Buhman, I am not a native English speaker but know for a fact that alternating between genders in documentation is something that is frequently done in order to make the documentation “gender neutral” (in a sense.) When you changed “herself” to “himself” the previous time, I asked a native (American) English speaker and he confirmed this to me. “himself” is not gender neutral, it’s masculine.<br />
Alternatively, it is possible to use “users … themselves” instead of alternating genders. [[User:Stqn|Stqn]] ([[User talk:Stqn|talk]]) 17:34, 8 December 2012 (UTC)<br />
<br />
== phc-intel setup (or phc-k8 setup) not needed anymore ==<br />
<br />
as told in https://bbs.archlinux.org/viewtopic.php?pid=1786330#p1786330 phc-intel setup (or phc-k8 setup) is not needed anymore<br />
<br />
On a machine I had the phc_intel kernel module loaded after a reboot but I can't have it loaded on another machine (although modinfo phc_intel shows that the module has been built correctly)<br />
<br />
[[User:Pierro78|Pierro78]] ([[User talk:Pierro78|talk]]) 22:06, 21 May 2020 (UTC)</div>Pierro78https://wiki.archlinux.org/index.php?title=Talk:PHC&diff=614754Talk:PHC2020-05-21T22:06:38Z<p>Pierro78: /* phc-intel setup (or phc-k8 setup) not needed anymore */</p>
<hr />
<div>november 2009, seems that acpi_cpufreq was replaced by phc-intel module.<br />
<br />
that's why the tutorial won't work for intel cpu's anymore.<br />
<br />
----<br />
now we NEED person to test it<br />
<br />
for reporting cpus supported<br />
<br />
and<br />
<br />
how config it<br />
<br />
----<br />
Yaourt is not the AUR's client. It is an unsupported third party tool. - [[User:Louipc|louipc]] 09:32, 7 August 2009 (EDT)<br />
<br />
----<br />
<br />
phctool doesn't work any more... You need more explain about Voltage controlling without gui tool! ;) linux-phc-optimize script from AUR doesn't work eather, there's link for working script in comments... Please change this... ;) Pyntux<br />
<br />
----<br />
==himself vs. herself==<br />
Buhman, I am not a native English speaker but know for a fact that alternating between genders in documentation is something that is frequently done in order to make the documentation “gender neutral” (in a sense.) When you changed “herself” to “himself” the previous time, I asked a native (American) English speaker and he confirmed this to me. “himself” is not gender neutral, it’s masculine.<br />
Alternatively, it is possible to use “users … themselves” instead of alternating genders. [[User:Stqn|Stqn]] ([[User talk:Stqn|talk]]) 17:34, 8 December 2012 (UTC)<br />
<br />
== phc-intel setup (or phc-k8 setup) not needed anymore ==<br />
<br />
as told in https://bbs.archlinux.org/viewtopic.php?pid=1786330#p1786330<br />
<br />
I rebooted and I had the phc_intel kernel module loaded<br />
<br />
[[User:Pierro78|Pierro78]] ([[User talk:Pierro78|talk]]) 22:06, 21 May 2020 (UTC)</div>Pierro78https://wiki.archlinux.org/index.php?title=Talk:PHC&diff=614753Talk:PHC2020-05-21T22:06:18Z<p>Pierro78: /* phc-intel setup (or phc-k8 setup) not needed anymore */ new section</p>
<hr />
<div>november 2009, seems that acpi_cpufreq was replaced by phc-intel module.<br />
<br />
that's why the tutorial won't work for intel cpu's anymore.<br />
<br />
----<br />
now we NEED person to test it<br />
<br />
for reporting cpus supported<br />
<br />
and<br />
<br />
how config it<br />
<br />
----<br />
Yaourt is not the AUR's client. It is an unsupported third party tool. - [[User:Louipc|louipc]] 09:32, 7 August 2009 (EDT)<br />
<br />
----<br />
<br />
phctool doesn't work any more... You need more explain about Voltage controlling without gui tool! ;) linux-phc-optimize script from AUR doesn't work eather, there's link for working script in comments... Please change this... ;) Pyntux<br />
<br />
----<br />
==himself vs. herself==<br />
Buhman, I am not a native English speaker but know for a fact that alternating between genders in documentation is something that is frequently done in order to make the documentation “gender neutral” (in a sense.) When you changed “herself” to “himself” the previous time, I asked a native (American) English speaker and he confirmed this to me. “himself” is not gender neutral, it’s masculine.<br />
Alternatively, it is possible to use “users … themselves” instead of alternating genders. [[User:Stqn|Stqn]] ([[User talk:Stqn|talk]]) 17:34, 8 December 2012 (UTC)<br />
<br />
== phc-intel setup (or phc-k8 setup) not needed anymore ==<br />
<br />
as told in https://bbs.archlinux.org/viewtopic.php?pid=1786330#p1786330<br />
<br />
I rebooted and I had the phc_intel kernel module loaded</div>Pierro78https://wiki.archlinux.org/index.php?title=Laptop/Toshiba&diff=563480Laptop/Toshiba2019-01-16T17:35:48Z<p>Pierro78: /* Portege */</p>
<hr />
<div>[[Category:Toshiba]]<br />
[[ja:ノートパソコン/Toshiba]]<br />
{{Laptops navigation}}<br />
<br />
== Satellite ==<br />
<br />
{{HCL/Laptops table header}}<br />
|Satellite C650-160 || 2017.2 || Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller support with xf86-video-intel driver || sound works with PulseAudio - volume buttons work || Qualcomm Atheros AR8152 v1.1 works || Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) works with linux-libre || not tested || Suspend to<br>RAM: works<br> Disk: NA <br> Battery: 3hr<br>Dimming of display: works<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \> Card reader: not tested || Kernel 4.9.11-gnu-1 linux-libre<br />
|- <br />
<br />
|Satellite U405-S2856 || current || Intel GMA X3100 3D support with xf86-video-intel driver || sound works with snd_hda_intel and [[ALSA]]. Volume dial requires xorg configuration || Marvell 88E8040 works with sky2 kernel module || Atheros AR928X works with ma80211 and ath9k || not tested || Suspend to<br>RAM: works<br> Disk: NA <br> Battery: 3hr<br>Dimming of display: works<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \> Card reader: works || Kernel 2.6.27 fixes bugs in card reader, includes wireless modules<br />
|- <br />
<br />
|Satellite A200-1TO || Current || ATI HD2400 (128-892MB Shared) Fully supported by latest ATI Catalyst Drivers || Sound works perfectly under current (2.6.25) kernel, using snd_hda_intel and ALSA. || Yes || Intel 3945 wireless. Works with stock Arch kernel || NA || Power Management working flawlessly. Setup as per Wiki instructions || Not tested. || NA || NA<br />
|-<br />
<br />
|Satellite C50-B032 || 2016.07.01 || xf86-video-intel || Yes (works out of the box)|| Yes (works out of the box) || Yes (works out of the box) || works out of the box || works out of the box || NA || NA || NA<br />
|-<br />
<br />
|Satellite P100-PSPA3C-MA502C || Current || 3D supported with latest NVIDIA Driver || Sound works with snd_hda_intel and DSDT modification. See [http://www.gentoo-wiki.com/HARDWARE_Toshiba_Satellite_P100 Gentoo Wiki] for info. || Yes || Works with ipw3945 || NA || Suspend to<br>RAM: NA<br>Disk: NA<br>Battery: 2h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Works with linuxant non-free driver || NA || need BIOS Update V.2.40. Don't use BIOS v. 3.30; GPU may overheat.<br />
<br />
<br />
|-<br />
<br />
|Satellite U305-S7446 || current || Intel GMA X3100 3D support with xf86-video-intel driver || Sound works. Volume Control Dial is buggy. Keep getting events even when not turning the wheel. Most likely a bug in Xorg || Yes || Intel PRO/Wireless 3945ABG works || NA || Suspend to<br>RAM: NA<br>Disk: NA<br>Battery: 2.5h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>5 in 1 Bridge Media Adapter: Not tested || NA<br />
|-<br />
<br />
|Satellite Pro L300-EZ1501 || current || Intel Corporation Mobile 4 Series Chipset with xf86-video-intel driver || Sound works by default as do onboard speakers|| Yes || Qualcomm Atheros AR242x/AR542x (wicd) || N\A || Not tested || Not tested || N\A || N\A<br />
|-<br />
<br />
|Satellite Pro L300D-13S || current || tested with open-source ati, works fine || Sound works by default as do onboard speakers|| Yes || Works with rtl8187 module || N\A || Not tested || Not tested || Chicony webcam works with linux-uvc driver || N\A<br />
|-<br />
<br />
|Satellite Pro U300 || current || Intel GMA X3100 <br \> xf86-video-intel driver || Works with snd_hda_intel driver and Alsa || Yes || Works perfectly with iwl4965 driver || Works well with [https://aur.archlinux.org/packages.php?ID=6919 Omnibook module] and ectype=14 || Suspend to<br>RAM: yes<br>Disk: yes<br>Battery: 2.5h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver] || N\A<br />
|-<br />
<br />
|Satellite U405-S2856 || current || Intel GMA X3100 3D support with xf86-video-intel driver || Sound works snd_hda_intel and alsa|| Marvell 88E8040 works with sky2 module || needs modules: mac80211 and ath9k (kernel>= 2.6.27 or compat-wireless) || not tested || Suspend to<br>RAM: works <br>Disk: not tested<br>Battery: 3h<br>Dimming of display: OK<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>5 in 1 Bridge Media Adapter: Not tested || NA<br />
|-<br />
<br />
|Satellite A200-1M5 || Current 2008.6 || Intel 945GM support with xf86-video-intel driver || Sound works snd-hda-intel model=lenovo and alsa || works || works Intel PRO Wireless 4965 || works with omnibook driver || NA || Winmodem, doesn't work || Chicony USB 2.0 Camera works out of the box. Card reader works. || NA<br />
|- <br />
<br />
|Satellite A300D || Current || ATI Mobility Radeon HD 3650 3D support with catalyst drivers || Sound works. Volume control wheel works. || Marvell 88E8040T works || Atheros AR5008 works with ar9k, support for passive monitoring. || NA || Suspend to<br />RAM: NA<br>Disk: NA<br>Battery: NA<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>Microphone works out-of-box with ALSA. || NA<br />
|}<br />
<br />
== Portege ==<br />
<br />
{{HCL/Laptops table header}}<br />
|Portege z835-P330 || Current || Intel HD Graphics (Sandy Bridge: make sure to enable i915_enable_rc6 and i915_enable_fbc for maximum battery life) || Sound (hda) works. Volume control works. || Intel 82579LM works || Centrino Wireless-N 1000 (iwlagn) works. || NA || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 3h/5h with power saving<br>Dimming of display: brightness control only works with intel_backlight from intel-gpu-tools-git <br>Frequency scaling of CPU: OK <br> Fan control: no (noisy fan fixed with 1.6 bios update; instructions [http://benobs.blogspot.fr/2012/04/toshiba-z835-p330-bios-update-from.html here]) || NA || Camera works <br \>Microphone works (need to change options in skype) || NA<br />
|- <br />
<br />
|Portege z930-S9311 || Current || Intel® Ivybridge Mobile || Sound works. Also the keyboard shortcuts || works || works. || Not tested || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 2h/3:50h with power saving<br>Dimming of display: brightness control works even after suspend with gnome-settings-daemon-backlight-toshiba 3.18.2-1 from AUR || NA || Camera works <br \>Microphone works || NA<br />
|-<br />
<br />
|[[Toshiba Portege Z20t|Portege Z20t]]-B2112 || Current || Intel® HD Graphics 5300 (Broadwell GT2)<br>Touschscreen also works fine (Gnome)<br>Side note: To use dual monitor setup one cable has to be connected to the screen and the other one to the base (keyboard), both cables to the base doesn't work. || Sound works [https://bbs.archlinux.org/viewtopic.php?id=213720 except no sound from speaker after resuming from suspend to RAM]. Also the keyboard shortcuts to mute/unmute <br> Vol Buttons on the screen works too || works || works. || Not tested || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 2h/3:50h with power saving<br>Dimming of display: works<br />
|| NA || Camera works <br \>Microphone works || NA<br />
|}</div>Pierro78https://wiki.archlinux.org/index.php?title=Laptop/Toshiba&diff=563479Laptop/Toshiba2019-01-16T17:35:17Z<p>Pierro78: /* Portege */</p>
<hr />
<div>[[Category:Toshiba]]<br />
[[ja:ノートパソコン/Toshiba]]<br />
{{Laptops navigation}}<br />
<br />
== Satellite ==<br />
<br />
{{HCL/Laptops table header}}<br />
|Satellite C650-160 || 2017.2 || Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller support with xf86-video-intel driver || sound works with PulseAudio - volume buttons work || Qualcomm Atheros AR8152 v1.1 works || Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) works with linux-libre || not tested || Suspend to<br>RAM: works<br> Disk: NA <br> Battery: 3hr<br>Dimming of display: works<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \> Card reader: not tested || Kernel 4.9.11-gnu-1 linux-libre<br />
|- <br />
<br />
|Satellite U405-S2856 || current || Intel GMA X3100 3D support with xf86-video-intel driver || sound works with snd_hda_intel and [[ALSA]]. Volume dial requires xorg configuration || Marvell 88E8040 works with sky2 kernel module || Atheros AR928X works with ma80211 and ath9k || not tested || Suspend to<br>RAM: works<br> Disk: NA <br> Battery: 3hr<br>Dimming of display: works<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \> Card reader: works || Kernel 2.6.27 fixes bugs in card reader, includes wireless modules<br />
|- <br />
<br />
|Satellite A200-1TO || Current || ATI HD2400 (128-892MB Shared) Fully supported by latest ATI Catalyst Drivers || Sound works perfectly under current (2.6.25) kernel, using snd_hda_intel and ALSA. || Yes || Intel 3945 wireless. Works with stock Arch kernel || NA || Power Management working flawlessly. Setup as per Wiki instructions || Not tested. || NA || NA<br />
|-<br />
<br />
|Satellite C50-B032 || 2016.07.01 || xf86-video-intel || Yes (works out of the box)|| Yes (works out of the box) || Yes (works out of the box) || works out of the box || works out of the box || NA || NA || NA<br />
|-<br />
<br />
|Satellite P100-PSPA3C-MA502C || Current || 3D supported with latest NVIDIA Driver || Sound works with snd_hda_intel and DSDT modification. See [http://www.gentoo-wiki.com/HARDWARE_Toshiba_Satellite_P100 Gentoo Wiki] for info. || Yes || Works with ipw3945 || NA || Suspend to<br>RAM: NA<br>Disk: NA<br>Battery: 2h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Works with linuxant non-free driver || NA || need BIOS Update V.2.40. Don't use BIOS v. 3.30; GPU may overheat.<br />
<br />
<br />
|-<br />
<br />
|Satellite U305-S7446 || current || Intel GMA X3100 3D support with xf86-video-intel driver || Sound works. Volume Control Dial is buggy. Keep getting events even when not turning the wheel. Most likely a bug in Xorg || Yes || Intel PRO/Wireless 3945ABG works || NA || Suspend to<br>RAM: NA<br>Disk: NA<br>Battery: 2.5h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>5 in 1 Bridge Media Adapter: Not tested || NA<br />
|-<br />
<br />
|Satellite Pro L300-EZ1501 || current || Intel Corporation Mobile 4 Series Chipset with xf86-video-intel driver || Sound works by default as do onboard speakers|| Yes || Qualcomm Atheros AR242x/AR542x (wicd) || N\A || Not tested || Not tested || N\A || N\A<br />
|-<br />
<br />
|Satellite Pro L300D-13S || current || tested with open-source ati, works fine || Sound works by default as do onboard speakers|| Yes || Works with rtl8187 module || N\A || Not tested || Not tested || Chicony webcam works with linux-uvc driver || N\A<br />
|-<br />
<br />
|Satellite Pro U300 || current || Intel GMA X3100 <br \> xf86-video-intel driver || Works with snd_hda_intel driver and Alsa || Yes || Works perfectly with iwl4965 driver || Works well with [https://aur.archlinux.org/packages.php?ID=6919 Omnibook module] and ectype=14 || Suspend to<br>RAM: yes<br>Disk: yes<br>Battery: 2.5h<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver] || N\A<br />
|-<br />
<br />
|Satellite U405-S2856 || current || Intel GMA X3100 3D support with xf86-video-intel driver || Sound works snd_hda_intel and alsa|| Marvell 88E8040 works with sky2 module || needs modules: mac80211 and ath9k (kernel>= 2.6.27 or compat-wireless) || not tested || Suspend to<br>RAM: works <br>Disk: not tested<br>Battery: 3h<br>Dimming of display: OK<br>Frequency scaling of CPU: not tested || NA || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>5 in 1 Bridge Media Adapter: Not tested || NA<br />
|-<br />
<br />
|Satellite A200-1M5 || Current 2008.6 || Intel 945GM support with xf86-video-intel driver || Sound works snd-hda-intel model=lenovo and alsa || works || works Intel PRO Wireless 4965 || works with omnibook driver || NA || Winmodem, doesn't work || Chicony USB 2.0 Camera works out of the box. Card reader works. || NA<br />
|- <br />
<br />
|Satellite A300D || Current || ATI Mobility Radeon HD 3650 3D support with catalyst drivers || Sound works. Volume control wheel works. || Marvell 88E8040T works || Atheros AR5008 works with ar9k, support for passive monitoring. || NA || Suspend to<br />RAM: NA<br>Disk: NA<br>Battery: NA<br>Dimming of display: OK<br>Frequency scaling of CPU: OK || Didn't test || Chicony USB 2.0 Camera works with [http://linux-uvc.berlios.de Linux UVC driver].<br \>Microphone works out-of-box with ALSA. || NA<br />
|}<br />
<br />
== Portege ==<br />
<br />
{{HCL/Laptops table header}}<br />
|Portege z835-P330 || Current || Intel HD Graphics (Sandy Bridge: make sure to enable i915_enable_rc6 and i915_enable_fbc for maximum battery life) || Sound (hda) works. Volume control works. || Intel 82579LM works || Centrino Wireless-N 1000 (iwlagn) works. || NA || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 3h/5h with power saving<br>Dimming of display: brightness control only works with intel_backlight from intel-gpu-tools-git <br>Frequency scaling of CPU: OK <br> Fan control: no (noisy fan fixed with 1.6 bios update; instructions [http://benobs.blogspot.fr/2012/04/toshiba-z835-p330-bios-update-from.html here]) || NA || Camera works <br \>Microphone works (need to change options in skype) || NA<br />
|- <br />
<br />
|Portege z930-S9311 || Current || Intel® Ivybridge Mobile || Sound works. Also the keyboard shortcuts || works || works. || Not tested || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 2h/3:50h with power saving<br>Dimming of display: brightness control works even after suspend with gnome-settings-daemon-backlight-toshiba 3.18.2-1 from AUR || NA || Camera works <br \>Microphone works || NA<br />
|-<br />
<br />
|[[Toshiba Portege Z20t|Portege Z20t]]-B2112 || Current || Intel® HD Graphics 5300 (Broadwell GT2)<br>Touschscreen also works fine (Gnome)<br>Side note: To use dual monitor setup one cable has to be connected to the screen and the other one to the base (keyboard), both cables to the base doesn't work. || Sound works [https://bbs.archlinux.org/viewtopic.php?id=213720 except no sound from speaking after resuming from suspend to RAM]. Also the keyboard shortcuts to mute/unmute <br> Vol Buttons on the screen works too || works || works. || Not tested || Suspend to<br />RAM: works<br>Disk: not tested<br>Battery: 2h/3:50h with power saving<br>Dimming of display: works<br />
|| NA || Camera works <br \>Microphone works || NA<br />
|}</div>Pierro78https://wiki.archlinux.org/index.php?title=Toshiba_Portege_Z20t&diff=563478Toshiba Portege Z20t2019-01-16T17:27:43Z<p>Pierro78: /* No speaker sound when resuming from suspend */</p>
<hr />
<div>[[Category:Toshiba]]<br />
[[ja:Toshiba dynabook R82]]<br />
The power of an enterprise-class laptop. The freedom and convenience of a tablet. Why choose when you can get the best of both? The Toshiba Portégé® Z20t Ultrabook® offers innovative 2-in-1 versatility in a supremely crafted chassis, along with outstanding battery life and an exceptional handwriting experience.<br />
<br />
== Specifications ==<br />
{| class="wikitable"<br />
|-<br />
|Name || Series Toshiba Portege Z20t<br />
|-<br />
|Processor || Intel Core M-5Y71<br />
|-<br />
|Screen || 12.5" Touchscreen<br />
|-<br />
|RAM || 4-8-16GB<br />
|-<br />
|HDD || Toshiba SDD (256 [MZNTE256HMHP], 256, 512 GB)<br />
|-<br />
|Optical Drive || none<br />
|-<br />
|Graphics || Intel® HD Graphics 5300 (Broadwell GT2) <br />
|-<br />
|Network || Ethernet - Intel I218-LM, Wifi - Intel Wireless 7265<br />
|-<br />
|Touchpad || ALPS (Trackstick+Mousepad)<br />
|-<br />
|Fingerprint reader || none<br />
|-<br />
|Smart Card Reader || Realtec (Micro SD card reader)<br />
|-<br />
|Webcam || Toshiba Web Camera (Front and Back)<br />
|}<br />
<br />
==Installation and configuration==<br />
===CPU & Graphics===<br />
Works fine after installation, the video have some issues with lightdm locker when locking the session or after resume, if that's the case the configuration recommended for Intel works [[Intel_graphics#Configuration|Intel Arch]]{{Broken section link}}<br />
<br><br />
Touchscreen works fine tested in gnome.<br />
<br />
=== Touchpad ===<br />
It Works without any modification including gestures.<br />
<br />
=== Bluetooth ===<br />
Works<br />
<br />
=== Wifi ===<br />
Works<br />
<br />
=== LTE/3G ===<br />
Works in some situations. Some providers might not connect with the default configuration.<br />
<br />
The built-in Sierra EM7305 is operating in mbim-mode, which is the default configuration on Windows 8/10 Systems. mbim is still not well supported in Linux. Switching to QMI-Mode can solve some problems. [http://www.0xf8.org/2015/07/dell-wireless-5809e-support-in-linux-a-followup/#more-1258 Source]<br />
{{hc|99-em7305.rules|<nowiki>ACTION!="add|change", GOTO="mbim_to_qmi_rules_end"<br />
SUBSYSTEM!="usb|drivers", GOTO="mbim_to_qmi_rules_end"<br />
<br />
# force Sierra EM7305 to configuration #1<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
ATTR{bConfigurationValue}="1"<br />
<br />
# load qcserial module<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
RUN+="/sbin/modprobe -b qcserial"<br />
<br />
# add the new id in the qcserial driver<br />
SUBSYSTEM=="drivers", \<br />
ENV{DEVPATH}=="/bus/usb-serial/drivers/qcserial", \<br />
ATTR{new_id}="1199 9063"<br />
<br />
# load qmi_wwan module<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
RUN+="/sbin/modprobe -b qmi_wwan"<br />
<br />
<br />
# add the new id in the qmi_wwan driver<br />
SUBSYSTEM=="drivers", \<br />
ENV{DEVPATH}=="/bus/usb/drivers/qmi_wwan", \<br />
ATTR{new_id}="1199 9063"<br />
<br />
LABEL="mbim_to_qmi_rules_end"</nowiki><br />
}}<br />
<br />
=== Smart Card Reader ===<br />
Works fine, it is a mini SD card reader not a regular SD Card.<br />
<br />
=== Display Backlight Control ===<br />
It works out of the box, even after resume, no additional package has been installed<br />
<br />
=== Keyboard Backlight control ===<br />
Works<br />
<br />
For instructions on Keyboard backlight toggle see [[Toshiba Portege Z30-A#Installation and configuration]]. <br />
<br />
Since changing sys values requires root, one can either write a wrapper for bash scripts for setuid, which is generally considered insecure. Here is a simple toggle switch: [https://github.com/Exel232/Configurations/raw/master/Toshiba/kbdback.c KbdBacklightToggle in C]<br />
<br />
=== Fn-F9 Touchpad Toggle ===<br />
Needs custom hwdb to work. See [[Extra keyboard keys]]. Example hwdb provided here, but you might want to choose a different keycode: [https://github.com/Exel232/Configurations/raw/master/Toshiba/60-toshiba-input.hwdb HWDB Config]<br />
<br />
==Issues==<br />
<br />
=== No speaker sound when resuming from suspend to RAM ===<br />
See https://bbs.archlinux.org/viewtopic.php?id=213720</div>Pierro78https://wiki.archlinux.org/index.php?title=Toshiba_Portege_Z20t&diff=563451Toshiba Portege Z20t2019-01-16T10:49:37Z<p>Pierro78: /* Installation and configuration */</p>
<hr />
<div>[[Category:Toshiba]]<br />
[[ja:Toshiba dynabook R82]]<br />
The power of an enterprise-class laptop. The freedom and convenience of a tablet. Why choose when you can get the best of both? The Toshiba Portégé® Z20t Ultrabook® offers innovative 2-in-1 versatility in a supremely crafted chassis, along with outstanding battery life and an exceptional handwriting experience.<br />
<br />
== Specifications ==<br />
{| class="wikitable"<br />
|-<br />
|Name || Series Toshiba Portege Z20t<br />
|-<br />
|Processor || Intel Core M-5Y71<br />
|-<br />
|Screen || 12.5" Touchscreen<br />
|-<br />
|RAM || 4-8-16GB<br />
|-<br />
|HDD || Toshiba SDD (256 [MZNTE256HMHP], 256, 512 GB)<br />
|-<br />
|Optical Drive || none<br />
|-<br />
|Graphics || Intel® HD Graphics 5300 (Broadwell GT2) <br />
|-<br />
|Network || Ethernet - Intel I218-LM, Wifi - Intel Wireless 7265<br />
|-<br />
|Touchpad || ALPS (Trackstick+Mousepad)<br />
|-<br />
|Fingerprint reader || none<br />
|-<br />
|Smart Card Reader || Realtec (Micro SD card reader)<br />
|-<br />
|Webcam || Toshiba Web Camera (Front and Back)<br />
|}<br />
<br />
==Installation and configuration==<br />
===CPU & Graphics===<br />
Works fine after installation, the video have some issues with lightdm locker when locking the session or after resume, if that's the case the configuration recommended for Intel works [[Intel_graphics#Configuration|Intel Arch]]{{Broken section link}}<br />
<br><br />
Touchscreen works fine tested in gnome.<br />
<br />
=== Touchpad ===<br />
It Works without any modification including gestures.<br />
<br />
=== Bluetooth ===<br />
Works<br />
<br />
=== Wifi ===<br />
Works<br />
<br />
=== LTE/3G ===<br />
Works in some situations. Some providers might not connect with the default configuration.<br />
<br />
The built-in Sierra EM7305 is operating in mbim-mode, which is the default configuration on Windows 8/10 Systems. mbim is still not well supported in Linux. Switching to QMI-Mode can solve some problems. [http://www.0xf8.org/2015/07/dell-wireless-5809e-support-in-linux-a-followup/#more-1258 Source]<br />
{{hc|99-em7305.rules|<nowiki>ACTION!="add|change", GOTO="mbim_to_qmi_rules_end"<br />
SUBSYSTEM!="usb|drivers", GOTO="mbim_to_qmi_rules_end"<br />
<br />
# force Sierra EM7305 to configuration #1<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
ATTR{bConfigurationValue}="1"<br />
<br />
# load qcserial module<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
RUN+="/sbin/modprobe -b qcserial"<br />
<br />
# add the new id in the qcserial driver<br />
SUBSYSTEM=="drivers", \<br />
ENV{DEVPATH}=="/bus/usb-serial/drivers/qcserial", \<br />
ATTR{new_id}="1199 9063"<br />
<br />
# load qmi_wwan module<br />
SUBSYSTEM=="usb", \<br />
ATTR{idVendor}=="1199", ATTR{idProduct}=="9063", \<br />
RUN+="/sbin/modprobe -b qmi_wwan"<br />
<br />
<br />
# add the new id in the qmi_wwan driver<br />
SUBSYSTEM=="drivers", \<br />
ENV{DEVPATH}=="/bus/usb/drivers/qmi_wwan", \<br />
ATTR{new_id}="1199 9063"<br />
<br />
LABEL="mbim_to_qmi_rules_end"</nowiki><br />
}}<br />
<br />
=== Smart Card Reader ===<br />
Works fine, it is a mini SD card reader not a regular SD Card.<br />
<br />
=== Display Backlight Control ===<br />
It works out of the box, even after resume, no additional package has been installed<br />
<br />
=== Keyboard Backlight control ===<br />
Works<br />
<br />
For instructions on Keyboard backlight toggle see [[Toshiba Portege Z30-A#Installation and configuration]]. <br />
<br />
Since changing sys values requires root, one can either write a wrapper for bash scripts for setuid, which is generally considered insecure. Here is a simple toggle switch: [https://github.com/Exel232/Configurations/raw/master/Toshiba/kbdback.c KbdBacklightToggle in C]<br />
<br />
=== Fn-F9 Touchpad Toggle ===<br />
Needs custom hwdb to work. See [[Extra keyboard keys]]. Example hwdb provided here, but you might want to choose a different keycode: [https://github.com/Exel232/Configurations/raw/master/Toshiba/60-toshiba-input.hwdb HWDB Config]<br />
<br />
==Issues==<br />
<br />
=== No speaker sound when resuming from suspend ===<br />
See https://bbs.archlinux.org/viewtopic.php?id=213720</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78&diff=560178User:Pierro782018-12-24T11:26:01Z<p>Pierro78: </p>
<hr />
<div>[[User:Pierro78/Dell Precision M6500]]<br />
<br />
[[User_talk:Pierro78/Asus_chromebook_flip]]<br />
<br />
[https://www.facebook.com/groups/ArchLinuxDerives/permalink/149248619018299/?comment_id=344916496118176 Panasonic Toughbook Let's Note N10 & Let's Note AX3 (francais/french)]</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=550547User:Pierro78/Dell Precision M65002018-10-24T09:35:14Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]] ( NV92 (G92) on https://nouveau.freedesktop.org/wiki/CodeNames/ )<br />
<br />
<br />
<br />
nvidia-340xx-ck-nehalem doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312<br />
<br>Had to add this line to pacman.conf to use pacman with my old nvidia-340xx driver :<br />
<pre>IgnorePkg = xorg-server xorg-server-common xorg-server-xvfb xorg-server-xwayland nvidia-340xx-utils nvidia-340xx-ck-nehalem linux-ck-nehalem </pre><br />
Actually nvidia-340xx-ck-nehalem was too old but newer version of nvidia-340xx are working (using regular "linux" instead of "linux-ck" fixes the issue)</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=550546User:Pierro78/Dell Precision M65002018-10-24T09:35:02Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]] ( NV92 (G92) on https://nouveau.freedesktop.org/wiki/CodeNames/ )<br />
<br />
nvidia-340xx-ck-nehalem doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312<br />
<br>Had to add this line to pacman.conf to use pacman with my old nvidia-340xx driver :<br />
<pre>IgnorePkg = xorg-server xorg-server-common xorg-server-xvfb xorg-server-xwayland nvidia-340xx-utils nvidia-340xx-ck-nehalem linux-ck-nehalem </pre><br />
Actually nvidia-340xx-ck-nehalem was too old but newer version of nvidia-340xx are working (using regular "linux" instead of "linux-ck" fixes the issue)</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=550379User:Pierro78/Dell Precision M65002018-10-23T16:24:35Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]] ( NV92 (G92) on https://nouveau.freedesktop.org/wiki/CodeNames/ )<br />
<br />
nvidia-340xx doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312<br />
<br>Had to add this line to pacman.conf to use pacman with my old nvidia-340xx driver :<br />
<pre>IgnorePkg = xorg-server xorg-server-common xorg-server-xvfb xorg-server-xwayland nvidia-340xx-utils nvidia-340xx-ck-nehalem linux-ck-nehalem </pre></div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=549466User:Pierro78/Dell Precision M65002018-10-21T13:10:21Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]]<br />
<br />
nvidia-340xx doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312<br />
<br>Had to add this line to pacman.conf to use pacman with my old nvidia-340xx driver :<br />
<pre>IgnorePkg = xorg-server xorg-server-common xorg-server-xvfb xorg-server-xwayland nvidia-340xx-utils nvidia-340xx-ck-nehalem linux-ck-nehalem </pre></div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=549273User:Pierro78/Dell Precision M65002018-10-21T09:11:35Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]]<br />
<br />
nvidia-340xx doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312<br />
<br>Had to add this line to pacman.conf to use pacman :<br />
<pre>IgnorePkg = xorg-server xorg-server-common xorg-server-xvfb xorg-server-xwayland nvidia-340xx-utils nvidia-340xx-ck-nehalem linux-ck-nehalem </pre></div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Dell_Precision_M6500&diff=549256User:Pierro78/Dell Precision M65002018-10-21T08:51:24Z<p>Pierro78: </p>
<hr />
<div>NVIDIA Quadro FX 2800M needs nvidia-340xx [[NVIDIA#Installing]]<br />
<br />
nvidia-340xx doesnt support xorg 1.20, need to install nouveau : https://bbs.archlinux.org/viewtopic.php?id=237312</div>Pierro78https://wiki.archlinux.org/index.php?title=Mac&diff=475081Mac2017-04-25T09:33:04Z<p>Pierro78: /* April 2016 12" - Version 9,1 */ *** (nov 2016) keyboard backlight issue https://bbs.archlinux.org/viewtopic.php?id=219631</p>
<hr />
<div>[[Category:Apple]]<br />
[[de:ArchLinux auf einem MacBook]]<br />
[[fr:MacBook]]<br />
[[it:MacBook]]<br />
[[ja:MacBook]]<br />
[[zh-hans:MacBook]]<br />
{{Related articles start}}<br />
{{Related|Installation guide}}<br />
{{Related|General recommendations}}<br />
{{Related|MacBook4,2 (late 2008)}}<br />
{{Related|MacBook5,2 (early-mid 2009)}}<br />
{{Related|MacBookPro7,1}}<br />
{{Related|MacBookPro8,1/8,2/8,3 (2011)}}<br />
{{Related|MacBookPro9,2 (Mid-2012)}}<br />
{{Related|MacBookPro10,x}}<br />
{{Related|MacBookPro11,x}}<br />
{{Related|iMac Aluminum}}<br />
{{Related|Apple Fusion Drive}}<br />
{{Related articles end}}<br />
<br />
Installing Arch Linux on a MacBook (12"/Air/Pro) or an iMac is quite similar to installing it on any other computer. However, due to the specific hardware configuration of a Mac, there are a few deviations and special considerations which warrant a separate guide. For more background information, please see the [[Installation guide]] and [[UEFI]]. This guide contains installation-instructions that can be used on any Apple computer whose hardware is supported by the Linux kernel. Please see 'related' pages (on the top right of this page) for model-specific tips and troubleshooting.<br />
<br />
== Overview ==<br />
<br />
Specifically, the procedure for installing Arch Linux on a MacBook is:<br />
<br />
# '''[[#Firmware updates|Firmware updates]]''': It always helps to start from a clean, backed up, and up-to-date install of OS X.<br />
# '''[[#Partitions|Partition]]''': Resizing or deleting the OS X partition to create partitions for Arch Linux.<br />
# '''[[#Setup bootloader|Setup bootloader]]''': Making sure that the new partition is bootable.<br />
# '''[[#Installation|Install Arch Linux]]''': Actually installing Arch Linux.<br />
# '''[[#Post-installation|Post-installation]]''': MacBook-specific configuration.<br />
<br />
== Firmware updates ==<br />
<br />
Before proceeding with the installation of Arch Linux, it is important to ensure that the latest firmware updates for you MacBook are installed. This procedure requires OS X.<br />
In OS X, open the App Store and check for updates. If your mac finds and installs any updates, make sure to '''reboot''' your computer, and then check again for updates to make sure that you installed everything.<br />
<br />
{{Note|If you uninstalled OS X or want to reinstall it, [https://support.apple.com/en-us/HT204904 Apple] has great instructions.}}<br />
<br />
It is advisable to keep OS X installed, because MacBook firmware updates can only be installed using OS X. However, if you plan to remove OS X completely, make backups of these files, which you will need in Linux for adjusting the [[#Color Profile|color profile]]:<br />
/Library/ColorSync/Profiles/Displays/*<br />
<br />
Continue to [[#Partitions]]<br />
<br />
== Partitions ==<br />
<br />
Partitioning of the storage drive is no different from any other PC or laptop. However, if you plan on keeping OS X for dual booting, you should consider that, by default, a MacBook's drive is formatted using GPT and contains at least 3 partitions:<br />
<br />
* '''EFI''': the ~200 MB [[EFI System Partition]].<br />
* '''OS X''': the main partition containing your OS X installation. It is formatted using [[File_systems|HFS+]].<br />
* '''Recovery''': A recovery partition present in almost all MacBooks running OS X 10.7 or newer. It is usually hidden from OS X but can be viewed with partitioning tools.<br />
<br />
{{Note|In Macs that use the [[Apple Fusion Drive]], the partition scheme could be different.}}<br />
<br />
How to partition depends on how many operating systems you want install. The following options will be explained:<br />
<br />
* Single boot: [[#Arch Linux only]]<br />
* Dual boot: [[#Arch Linux with OS X or other operating systems]] ''(recommended so you can still return to OS X when needed)''<br />
* Triple boot: [[#OS X, Windows XP, and Arch Linux triple boot]]<br />
<br />
<br />
=== Arch Linux only ===<br />
<br />
This situation is the easiest to deal with. Partitioning is the same as any other hardware that Arch Linux can be installed on. Please refer to the standard [[Installation guide]] for details.<br />
<br />
{{Note|It is advisable to '''disable''' the MacBook startup sound before proceeding with partitioning. Just boot in OS X, mute your system sound and reboot again to the Arch Linux Installation media. Please keep in mind that the volume of the startup sound can only be modified reliably in OS X.}}<br />
<br />
If you want to configure you system in order to have full-disk encryption, please look at the [[Dm-crypt/Encrypting an entire system]] page for details.<br />
<br />
An example for a very basic partitioning, that does not consider a separate {{ic|/home}} partition nor encryption or LVM, is the following:<br />
partition mountpoint size type label<br />
/dev/sda1 /boot 200MiB vfat EFI<br />
/dev/sda2 /swap adjust swap swap<br />
/dev/sda3 / remain ext4 root<br />
<br />
* Done, you can continue to [[#Installation]]<br />
<br />
<br />
=== Arch Linux with OS X or other operating systems ===<br />
<br />
You need to partition your hard drive while keeping the partitions used for OS X/Windows. If you wish to keep OS X, the easiest way is to use partitioning tools in OS X and then finish with Arch Linux tools.<br />
<br />
{{Warning| If you OS X partition is encrypted with FileVault 2, you '''must''' disable the disk encryption before proceeding. After the OS X partition has been resized, FileVault 2 can be re-enabled.}}<br />
<br />
'''Procedure''':<br />
* In OS X, run ''Disk Utility.app'' (located in {{ic|/Applications/Utilities}})<br />
* Select the drive to be partitioned in the left-hand column (not the partitions!). Click on the '''Partition''' button.<br />
* Add a new partition by pressing the '''+''' button and choose how much space you want to leave for OS X, and how much for the new partition. Keep in mind the new partition will be formatted in Arch Linux, so you can choose any partition type you want. <br />
* If the above completed successfully, then you can continue. If not, then you may need to fix your partitions from within OS X first.<br />
* Boot the Arch installation media or [[USB flash installation media|LiveUSB]] by holding down the {{ic|Alt}} '''during boot'''. Proceed with [[#Installation]].<br />
<br />
It is possible to resize the newly created partition from within the Arch installation media, or delete it in order to proceed with the creation of other partitions (eg. swap).<br />
<br />
{{Tip|Instead of cluttering your drive with different partition, it is possible to use a [[swapfile]] instead of a dedicated partition. Another solution can be setting up [[LVM]] in order to use the newly-created partition as a container. Please refer to the linked articles.}}<br />
<br />
<br />
==== Option 1: EFI ====<br />
<br />
* Run ''cgdisk''<br />
<br />
* Delete the partition you made in ''Disk Utility.app'' and create the necessary partitions for Arch Linux. OS X likes to see a 128 MiB gap after partitions, so when you create the first partition after the last OS X-partition, type in '''+128M''' when cgdisk asks for the first sector for the partition. More information about Apple's partitioning policy can be read [https://developer.apple.com/library/mac/technotes/tn2166/_index.html#//apple_ref/doc/uid/DTS10003927-CH1-SUBSECTION5 here]. A simple example (no LVM, crypto):<br />
<br />
{{Note|<br />
* The swap partition is optional on machines with 4GB of RAM or more. A '''[[swap file]]''' can be created later.<br />
* The easiest dual-boot option is to install rEFInd from inside OS X, to its root directory (default for {{ic|install.sh}}). Following that, copy the driver folder from the installation tarball into the new rEFInd location, and uncomment the lines ''"scan_all_linux_kernels"'' and ''"also_scan_dirs"'' options in {{ic|refind.conf}}. Configuration of boot options can then be done from a {{ic|refind_linux.conf}} in Arch's {{ic|/boot}} directory.<br />
* If you want to be able to boot GRUB from the Apple boot loader, you can create a small hfs+ partition (for convenience, use OS X to format it in ''Disk Utility.app'' afterwards). Follow the GRUB EFI install procedure, and mount your {{ic|/boot/efi}} directory to the hfs+ partition you created. Finally, finish up again in OS X by blessing the partition. This will set GRUB as the default boot option (holding alt at startup goes to the mac boot options screen still. See http://mjg59.dreamwidth.org/7468.html).,<br />
* OS X's EFI partition can be shared with Arch Linux, making the creation of an additional EFI partition dedicated to Arch completely optional.<br />
}}<br />
<br />
{{Note|For more information on partitioning, see [[Partitioning]]}}<br />
partition mountpoint size type label<br />
/dev/sda1 /boot/efi 200MiB vfat EFI<br />
/dev/sda2 - ? hfs+ OS X<br />
/dev/sda3 - ? hfs+ Recovery<br />
/dev/sda4 - 100MiB hfs+ Boot Arch Linux from the Apple boot loader (optional)<br />
/dev/sda5 /boot 100MiB boot boot<br />
/dev/sda6 - ? swap swap (optional)<br />
/dev/sda7 / 10GiB ext4 root<br />
/dev/sda8 /home remaining ext4 home<br />
<br />
* Done, you can continue to [[#Installation]]<br />
<br />
==== Option 2: BIOS-compatibility ====<br />
<br />
* Run ''parted'' as root.<br />
<br />
* Delete the empty space partition and partition the space as you would for any other installation. Note that MBR is limited to 4 primary partitions (including the efi partition). That leaves 2 primary partitions for Arch. One strategy is to have a system and home partition, and use a swap file (I have not tried to use logical partitions). Another is to dedicate one partition to a shared partition (see below).<br />
<br />
* Next, create new filesystems on those partitions which need them, especially the partition which will contain {{ic|/boot}}. If you are not sure how to do this using {{ic|mkfs.ext2}} (or whatever), run {{ic|/arch/setup}} and work through until you get to Prepare Hard Drive and use the ''"Manually configure block devices..."'' option, then exit the installer. This is necessary so that rEFIt will set the right partition type in the MBR in the next step (without an existing filesystem, it seems to ignore the partition type set by parted), without which GRUB will refuse to install to the right partition.<br />
<br />
* At this point you should reboot your computer and have rEFIt fix the partition tables on your hard drive. (If you do not do this, you may have to reinstall GRUB later on in order to have your Mac recognize the Linux partition.) When you are into the rEFIt menu, select '''update partition table''', then press {{ic|y}}. Reboot.<br />
<br />
* Done, you can continue with [[#Installation]].<br />
<br />
=== OS X, Windows XP, and Arch Linux triple boot ===<br />
<br />
This may not work for everyone but it has been successfully tested on a MacBook from late 2009.<br />
<br />
The easiest way to partition your hard drive, so that all these operating systems can co-exist, is to use disk utility in OS X, use the formatter on windows XP, install XP and then finish with Arch Linux tools.<br />
<br />
{{Warning|It is highly recommended that this only be attempted after a clean install of OS X. Using these methods on a pre-existing system may have undesired results. At least back your stuff up with timemachine or clonezilla before you begin.}}<br />
<br />
'''Procedure''':<br />
* In OS X, run '''Disk Utility''' (located in {{ic|/Applications/Utilities}}).<br />
<br />
* Select the drive to be partitioned in the left-hand column (not the partitions!). Click on the '''partition''' tab on the right.<br />
<br />
* Select the volume to be resized in the '''volume scheme.'''<br />
<br />
* Decide how much space you wish to have for your OS X partition, how much for XP, and how much for Arch Linux. Remember that a typical installation of OS X requires around 15-20 GiB, and XP about the same, depending on the number of software applications and files. Something like OS X 200Gb, XP 25Gb, Arch 25Gb should be fine.<br />
<br />
* Put your decisions into action by pressing the + button and adding the new partitions, Label them as you like and make sure that your XP partition is the last one on the disk and is formatted for FAT32. It is probably best to have Arch formatted in HFS format as to not confuse you later, it will be reformatted anyway.<br />
<br />
So in linux terms your partitions will be something like:<br />
<br />
:*sda (disk)<br />
:*sda1 (Mac boot partition - you cannot see this one in OS X)<br />
:*sda2 (OS X install in HFS+)<br />
:*sda3 (Arch install temporarly in HFS)<br />
:*sda4 (XP install in FAT32)<br />
<br />
* Finally, click '''apply'''. This will create a new partition out of the empty space.<br />
<br />
{{Note|Using this method you may not be able to have a shared partition between OS X and Arch Linux, this is because the mac will only allow for 4 active partitions. You will however be able to mount a HFS partition in Arch for one workaround. There are other workarounds possible also.}}<br />
<br />
* If the above completed successfully, you can continue. If not, then you may need to fix your partitions from within OS X first.<br />
<br />
* You will not be needing boot camp this way, the program rEFIt is much more flexible (though not as flexible as GRUB). Download and install rEFIt [http://refit.sourceforge.net/]<br />
<br />
* Go into a terminal in OS X and perform the following, this will enable the rEFIt boot manager. <br />
<br />
cd /efi/refit<br />
./enable.sh<br />
<br />
* Reboot to check the rEFIt is working, it should appear on boot. When it comes up go to the rEFIt partition manager and agree to the changes.<br />
<br />
* Put your XP install CD and boot it with rEFIt - You may have to reboot a few times until it is recognized by the boot loader. Install XP and once it is installed use the OS X installation CD to get your drivers running nicely in XP.<br />
** Note: when installing XP make sure you select your XP partition and format it again inside the XP installer. If you do not reformat it will not work.<br />
<br />
* Boot the Arch install CD, log in as root and run {{ic|# /arch/setup}}.<br />
<br />
* Follow the install as normal but note that you will have to tell that arch installer to mount sda3 as the root partition and format it as ext3, there will not be a /boot or swap partition so ignore those warnings.<br />
<br />
* At this point, if you are dual booting, you should reboot your computer and have rEFIt fix the partition tables on your hard drive. (If you do not do this, you may have to reinstall GRUB later on in order to have your Mac recognize the Linux partition.) When you are into the rEFIt menu, select '''update partition table''', then press Y.<br />
# reboot<br />
<br />
* Done! You can continue to [[#Installation]].<br />
<br />
== Setup bootloader ==<br />
<br />
=== Using the native Apple bootloader with systemd-boot (Recommended) ===<br />
<br />
Apple's native EFI bootloader reads {{ic|.efi}} files located inside the [[EFI System Partition]] at {{ic|/EFI/BOOT/BOOTX64.EFI}}. Luckily, this is also the default install location for the [[systemd-boot]] binary. This means that booting linux using ''systemd-boot'' is very simple.<br />
* First, make sure you mounted the EFI System Partition at {{ic|/boot}}<br />
* Proceed with [[#Installation]] normally<br />
* Once inside the chrooted enviroment, type the following command to install ''systemd-boot'':<br />
{{bc|1=# bootctl --path=/boot install}}<br />
The above command will copy the ''systemd-boot'' binary to {{ic|/boot/EFI/BOOT/BOOTX64.EFI}} and add ''systemd-boot'' itself as the default EFI application (default boot entry) loaded by the EFI Boot Manager. <br />
* Proceed to [[systemd-boot#Configuration]] in order to correctly set up the bootloader<br />
At the next reboot, the Apple Boot Manager, shown when holding down the option key when booting the MacBook, should display Arch Linux (it will be displayed as {{ic|EFI Boot}} as a possible boot option.<br />
{{Tip|If you installed Arch Linux alongside OS X, you will be able to change the default boot location from system Settings inside OS X. If Arch Linux does not show up as a possible boot option, you will have to mount the EFI System Partition inside OS X before selecting your boot option:<br />
{{bc|$ diskutil mount disk0s1}}<br />
}}<br />
<br />
=== Using the native Apple bootloader with GRUB ===<br />
<br />
{{Style|Uses [[partial upgrade]] procedure and explicitly lists many basic commands.}}<br />
<br />
Despite using UEFI, the MacBook's native EFI bootloader [http://refit.sourceforge.net/myths/ does not use the EFI partition for booting]. Instead, it looks for .efi files inside all the partitions in internal and external drives and shows them as possible boot options if certain conditions are satisfied. For example, MacBooks can detect an existing OSX installation after checking that:<br />
* there is a partition formatted as HFS+<br />
* the partition contains the partition id {{ic|af00}} <br />
* in the root of that partition, there is a file called {{ic|mach_kernel}}<br />
* inside that partition, there a {{ic|boot.efi}} file inside {{ic|/System/Library/CoreServices}}<br />
<br />
This means that configuring an Arch installation to be automatically recognized by the MacBook bootloader is possible. Moreover, it simply requires a properly-formatted HFS+ {{ic|/boot}} partition and does not require meddling with the EFI system partition. The advantage of this method is that it can coexist with OS X nicely and allows to avoid other bootloaders such as rEFInd. However, this requires manual configuration. The following steps will illustrate how to perform this configuration using GRUB.<br />
* First, while configuring a new Arch installation, create a separate {{ic|/boot}} partition. Many tools are available in the Arch ISO, for example '''cgdisk'''.<br />
* Make sure the partition is at least ~250 MB in size, since it will be used to store the kernel as well as any custom kernel you will install in the future. Moreover, make sure the partition type is set as Apple HFS/HFS+ (it will appear as {{ic|Apple HFS/HFS+}} in fdisk/cgdisk or {{ic|af00}} in gdisk)<br />
* Since the Arch installation ISO does not include the {{Pkg|hfsprogs}} package, we need to install it in the installation environment before proceeding with formatting the new partition as HFS+<br />
# pacman -Sy hfsprogs<br />
# modprobe hfsplus<br />
# mkfs.hfsplus /dev/sd'''X''' -v "Arch Linux"<br />
<br />
Note: replace /dev/sd'''X''' with the correct device as appropriate<br />
<br />
* Done, proceed with [[#Installation]]<br />
<br />
{{Warning|<br />
Once inside the chrooted enviroment, don’t forget to install the {{Pkg|hfsprogs}} package on the newly installed system as well. After the installation of the package, regenerate the initramfs while chrooted<br />
# mkinitcpio -p linux<br />
}}<br />
<br />
* Once inside the chrooted enviroment, install the {{Pkg|grub}} and {{Pkg|efibootmgr}} packages. The following steps install the GRUB UEFI application to {{ic|/boot/EFI/arch/System/Library/CoreServices/boot.efi}} and install its modules to {{ic|/boot/grub/x86_64-efi}}.<br />
# grub-install --target=x86_64-efi --efi-directory=/boot<br />
<br />
After that, remember to create a standard configuration file:<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
As you can see, the directory structure of the {{ic|boot.efi}} is not correct, as the {{ic|/System/Library/CoreServices}} directory is not supposed to be a subdirectory of the {{ic|/boot/EFI/}} folder. For this reason, we need to relocate the {{ic|boot.efi}} stub in a location the MacBook bootloader is able to recognize:<br />
# mv /boot/EFI/arch/System/ /boot/<br />
# rm -r /boot/EFI/<br />
<br />
Also, create a dummy {{ic|mach_kernel}} file<br />
# touch /boot/mach_kernel<br />
<br />
After that, you need to create the following file <br />
<br />
{{hc|1=# nano /boot/System/Library/CoreServices/SystemVersion.plist|2=<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<plist version="1.0"><br />
<dict><br />
<key>ProductBuildVersion</key><br />
<string></string><br />
<key>ProductName</key><br />
<string>Linux</string><br />
<key>ProductVersion</key><br />
<string>Arch Linux</string><br />
</dict><br />
</plist><br />
}}<br />
<br />
At the next reboot, the Apple Boot Manager, shown when holding down the option key when booting the MacBook, should display Arch Linux as a possible boot option. Selecting that option will boot GRUB.<br />
<br />
Done! GRUB can now be selected on the standard MacBook bootloader and you can boot into your newly installed Arch Linux.<br />
<br />
{{Tip| After the installation, it is optionally possible to set a custom icon that will be displayed in the MacBook boot loader. In order to do that, you need to install the {{Pkg|wget}}, {{Pkg|librsvg}} and {{AUR|libicns}} packages. After that, just follow the following commands:<br />
$ wget -O /tmp/archlinux.svg https://www.archlinux.org/logos/archlinux-icon-crystal-64.svg<br />
$ rsvg-convert -w 128 -h 128 -o /tmp/archlogo.png /tmp/archlinux.svg<br />
$ sudo png2icns /boot/.VolumeIcon.icns /tmp/archlogo.png<br />
$ rm /tmp/archlogo.png<br />
$ rm /tmp/archlinux.svg<br />
Obviously, you can replace the Arch logo with any other icon you like.<br />
}}<br />
<br />
=== Other methods ===<br />
<br />
{{Out of date | Section that describes bootloader setup for other setups should be revised and re-structured into more readable way}}<br />
{{Tip|rEFIt is a popular bootloader for EFI-firmware computers (including Macs). It can be installed at any time during the installation. For instructions, please see [[#rEFIt]]. }}<br />
<br />
If you are going for an Arch Linux-only setup, installing the bootloader is no different than on any other machine: Install [[systemd-boot]], [[rEFInd]] or other bootloader of your choice.<br />
<br />
If, on the other hand, you are dual/triple booting, then read on.<br />
<br />
<br />
=== Installing GRUB to EFI partition directly ===<br />
<br />
* If you would like to use GRUB as your main bootloader and use the "boot while holding the Alt/Option key" method to go back to OS X rather than using alternatives such as rEFIt (http://refit.sourceforge.net/, mentioned previously in [[#Option 2: BIOS-compatibility]] and [[#OS X, Windows XP, and Arch Linux triple boot]]) then you must install {{Pkg|grub}} to your Mac's '''already-existing''' EFI partition (see below). <br />
<br />
{{Note| These instructions are known to work on a MacBook Pro (Early 2011). Please read the procedure carefully '''as well as the details following it'''.}}<br />
<br />
{{Note| With a new MacBook Pro (Mid 2014), this procedure worked only after installing the<br />
{{Pkg|efibootmgr}} package.}}<br />
<br />
'''Procedure''':<br />
<br />
* Install {{Pkg|grub}}<br />
<br />
* Make a directory named {{ic|efi}} in {{ic|/boot}} <br />
<br />
* Mount the '''already-existing''' EFI partition on your Mac to this {{ic|/boot/efi}} directory<br />
<br />
* Install GRUB to this directory<br />
<br />
* Make a directory named {{ic| locale}} in {{ic| /boot/grub}}<br />
<br />
* Copy {{ic| grub.mo}} from {{ic| /usr/share/locale/en\@quot/LC_MESSAGES/}} to {{ic| /boot/grub/locale}} <br />
<br />
* Generate a configuration for GRUB<br />
<br />
* Done! GRUB will now start on reboot and you can boot into your newly installed Arch Linux.<br />
<br />
* Remember to hold ALT/Option key '''while''' starting your computer if you want to boot back into OS X.<br />
<br />
'''Details (quoted from [[GRUB EFI Examples#M5A97]]):'''<br />
<br />
Finish the standard Arch install procedures, making sure that you install {{Pkg|grub}} and partition your boot hard disk as GPT.<br />
<br />
From [[GRUB#UEFI systems]]:<br />
<br />
The UEFI system partition will need to be mounted at {{ic|/boot/efi/}} for the GRUB install script to detect it:<br />
<br />
# mkdir -p /boot/efi<br />
# mount -t vfat /dev/sdXY /boot/efi<br />
<br />
Where X is your boot hard disk and Y is the efi partition you created earlier.<br />
<br />
Install GRUB UEFI application to and its modules to {{ic|/boot/grub/x86_64-efi}} using:<br />
<br />
# modprobe dm-mod<br />
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug<br />
# mkdir -p /boot/grub/locale<br />
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br />
<br />
Generate a configuration for GRUB<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
=== Using blessing ===<br />
<br />
It is possible to boot directly from GRUB in EFI mode without using rEFIt through what is known as "blessing" after placing GRUB on a '''separate partition'''. These instructions are known to work on a MacBook7,1. It is advisable to host GRUB on either a FAT32 or HFS+ partition, but ext2 or ext3 may also work. GRUB's appleloader command does not currently work with the 7,1, but support can be added with the patch available [https://savannah.gnu.org/bugs/index.php?33185 here].<br />
<br />
After the GRUB install is in the desired location, the firmware needs to be instructed to boot from that location. This can be done from either an existing OS X install or an OS X install disk. The following command assumes that the GRUB install is in {{ic|/efi/grub}} on an existing OS X partition:<br />
# bless --folder /efi/grub --file /efi/grub/grub.efi<br />
<br />
=== Compilation ===<br />
<br />
Some models may need EFI_ARCH set to i386.<br />
bzr branch --revision -2 bzr://bzr.savannah.gnu.org/grub/trunk/grub grub<br />
cd grub<br />
./autogen.sh<br />
patch -p1 < appleloader_macbook_7_1.patch<br />
export EFI_ARCH=x86_64<br />
./configure --with-platform=efi --target=${EFI_ARCH} --program-prefix=""<br />
make<br />
cd grub-core<br />
../grub-mkimage -O ${EFI_ARCH}-efi -d . -o grub.efi -p "" part_gpt part_msdos ntfs ntfscomp hfsplus fat ext2 normal chain boot configfile linux multiboot<br />
cp grub.efi *.mod *.lst yourinstalllocation<br />
<br />
== Installation ==<br />
<br />
{{Note|This section is only required if you want to have OS X installed along with Arch Linux. If not, follow the steps in the official install guide, then skip to [[#Post-installation]].}}<br />
<br />
* Boot from the Arch Linux install CD, from the latest [[Archboot]] iso (unofficial), or from a [[USB flash installation media#Using manual formatting|manually created]] bootable USB drive.<br />
{{Note|<br />
* On a MacBookPro7,1, I had an error booting the installation media Version 2012.12.01: "unable to handle kernel NULL pointer dereference at 0000000000000010" during pacpi_set_dmamode. To fix this problem, boot with the option: acpi&#61;off. After chrooting, add MODULES&#61;"ata_generic" into /etc/mkinitcpio.conf and execute mkinitcpio -p linux, see: [[Installation guide#Configure_the_system|Installation Guide, 9 Configure the system]].<br />
* Some MacBook users report strange keyboard output such as long delays and character doubling. To fix this problem, boot with the following options: arch noapic irqpoll acpi&#61;force}}<br />
<br />
* Proceed through the installation as described in the [[Installation guide]] '''except''' in the following areas:<br />
** Skip the [[Installation guide#Partition the disks|partition the disks]] stage, do only the [[Installation guide#Format the partitions|partition formatting]] and [[Installation guide#Mount the partitions|mounting]] steps, taking care to assign the correct partitions. Partitions have already been created if you followed [[#Partitions]]<br />
** '''(for booting with EFI''') After the [[Installation guide#Boot loader|install boot loader]] stage, exit the installer and install [[GRUB]].<br />
** '''(for booting with BIOS-compatibility)''' In the [[Installation guide#Boot loader|install boot loader]] stage, edit the menu.lst file and add '''reboot=pci''' to the end of the '''kernel''' lines, for example: {{bc|1=kernel /vmlinuz-linux root=/dev/sda5 ro reboot=pci}} This will allow your MacBook to reboot correctly from Arch.<br />
** '''(for booting with BIOS-compatibility)''' Also in the [[Installation guide#Boot loader|install boot loader]] stage, install GRUB on whatever partition that {{ic|/boot}} is on. {{Warning|Do not install GRUB onto ''/dev/sda'' !!! Doing so is likely to lead to an unstable post-environment.}}<br />
** In the [[Installation guide#Configure the system|configure system]] stage, edit /etc/mkinitcpio.conf and ensure the '''keyboard''' hook is in the '''HOOKS''' line somewhere after the '''autodetect''' hook. This will load the drivers for your keyboard in case you need to use it before Arch boots (e.g. entering a [[LUKS]] password or using the troubleshooting shell).<br />
<br />
* When the install process is complete, reboot your computer.<br />
<br />
* If using optical media, hold down the eject key as your MacBook starts, this should eject the Arch Linux install disk.<br />
<br />
* If dual-booting OS X and Arch Linux, hold down the alt (option) key while the system boots to use the Mac bootloader to select which OS to boot.<br />
<br />
== Post-installation ==<br />
<br />
{{Style|Duplicated information, does not comply with [[Help:Style]].}}<br />
<br />
See [[General recommendations]] for system management directions and post-installation tutorials like setting up a graphical user interface, sound or a touchpad.<br />
<br />
==== Video ====<br />
<br />
Different MacBook models have different graphic cards.<br />
To see which graphics card you have type:<br />
<br />
$ lspci | grep VGA<br />
<br />
* If it returns a string containing '''Intel''', read [[Intel graphics]].<br />
<br />
* If it returns '''NVIDIA''', read [[NVIDIA]].<br />
<br />
* Otherwise if it returns '''ATI''' or '''AMD''', read [[ATI]].<br />
<br />
===== NVIDIA note =====<br />
<br />
{{Tip|If you have installed OS in EFI mode and NVIDIA binary drivers are working only in BIOS mode (e.g. you get black screen on EFI boot), try this approach: http://askubuntu.com/a/613573/492886 }}<br />
<br />
For MacBooks with NVIDIA graphics, for the backlight to work properly you may need the {{AUR|nvidia-bl}} package.<br />
<br />
{{Tip|<br />
* If backlight control does not work after installing nvidia-bl, you should [[blacklist]] apple_bl kernel module.<br />
* If backlight control does not work even this way, try setting module parameters. Uncommenting {{ic|1=options nvidia_bl max_level=0x1ffff shift=11}} in {{ic|/etc/modprobe.d/nvidia_bl.conf}} should do the trick.<br />
* Alternatively, you can choose to use the {{AUR|pommed-light}} package. If you do so, you may wish to change the step settings in {{ic|/etc/pommed.conf.mactel}} to something around 5000-10000 depending on how many levels of brightness you desire. The max brightness is around 80000, so take that into account.}}<br />
<br />
==== Touchpad ====<br />
<br />
The touchpad should have basic functionality by default. A true multitouch driver which behaves very similarly to native OS X is included in the {{AUR|xf86-input-mtrack-git}} package. Configuration options are documented in the [https://github.com/BlueDragonX/xf86-input-mtrack readme].<br />
<br />
The following mtrack options work well on a MacBook7,1:<br />
<br />
Option "Thumbsize" "50"<br />
Option "ScrollDistance" "100"<br />
<br />
Probably you need also to add:<br />
<br />
MatchDevicePath "/dev/input/event10"<br />
<br />
To disable tap-to-click (that is, to press down to click) by default, add the following to your mtrack configuration section<br />
<br />
Option "TapButton1" "0" <br />
Option "TapButton2" "0"<br />
Option "TapButton3" "0"<br />
<br />
'''Natural scrolling:''' To configure natural two finger scrolling similar to [http://www.apple.com/au/osx/what-is/gestures.html#gallery-gestures-scroll OS X], refer to [[Touchpad Synaptics#Natural scrolling]].<br />
<br />
If you are using {{AUR|xf86-input-mtrack-git}}, you can simply swap the scroll up and scroll down buttons (along with the scroll left and scroll right):<br />
{{hc|/etc/X11/xorg.conf.d/10-mtrack.conf|<br />
...<br />
Option "ScrollUpButton" "5"<br />
Option "ScrollDownButton" "4"<br />
Option "ScrollLeftButton" "7"<br />
Option "ScrollRightButton" "6"<br />
...}}<br />
<br />
<br />
'''Special Note About Older Macbook Models (confirmed on MacBook2,1):''' On older Macbook models (pre-multitouch), the touchpad will not function properly until you install the xf86-input-synaptics package. Please see [[Touchpad Synaptics]] for more information on installing and configuring this package.<br />
<br />
'''Note on MacBookPro5,5:''' I found it is much simpler to use the {{Pkg|xf86-input-synaptics}} in Extra. Although it does not have much function as 3 finger swipe, this driver provides faster response. {{Pkg|gpointing-device-settings}} also provides a simple GUI config. Below is a Xorg config file /etc/X11/xorg.conf.d/60-synaptics.conf for reference only.<br />
Section "InputClass"<br />
Identifier "touchpad catchall"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "SHMConfig" "on"<br />
Option "TapButton1" "1"<br />
Option "TapButton2" "3"<br />
Option "TapButton3" "2"<br />
Option "PalmDetect" "on"<br />
Option "VertEdgeScroll" "off"<br />
Option "HorizEdgeScroll" "off"<br />
Option "CornerCoasting" "off"<br />
Option "EdgeMotionUseAlways" "off"<br />
Option "AreaLeftEdge" "10"<br />
Option "AreaRightEdge" "1270"<br />
EndSection<br />
'''For some users, the two-finger right-click may not work correctly and trackpad may also become less responsive after these settings. For me, removing the 'AreaLeftEdge' and 'AreaRightEdge', solved that problem.'''<br />
'''OS X like MultiTouch Gestures''' ''currently broken due to newer synaptic drivers!'' For users looking to add more of OS X's multitouch gestures to Arch, [https://github.com/iberianpig/xSwipe xSwipe] is a highly customisable, light weight perl script, which does just that. Once installed and configured (see xSwipe wiki on Github) I would recommend adding xSwipe as a [[Autostarting|start up item]].<br />
<br />
==== Keyboard ====<br />
<br />
MacBook keyboards work by default. For swaping fn keys with Fx keys see [[Apple Keyboard]].<br />
<br />
To enable it you can map with right application like '''xbindkeys''' or through DE preferences; but another very good way, that we recommend, is to install the {{AUR|pommed-light}} package.<br />
<br />
Edit the {{ic|/etc/pommed.conf}} according to your hardware on MacBook, building it from {{ic|/etc/pommed.conf.mac}} or {{ic|/etc/pommed.conf.ppc}} example files.<br />
<br />
Note that you can also run it without a configuration file, the defaults may work for you. Then [[enable]] and start {{ic|pommed.service}}.<br />
<br />
{{Tip|if you are using Gnome or KDE you can easily configure ''3rd level functionality'', ''multimedia key'', etc. in Keyboard Preferences.}}<br />
<br />
{{Note|See the [[Xorg input hotplugging]] page for other configuration information.}}<br />
<br />
===== Keyboard Backlight =====<br />
<br />
The keyboard backlight is controlled by {{ic|/sys/class/leds/smc::kbd_backlight}}. Write the desired value to {{ic|brightness}} in that directory.<br />
<br />
Both {{AUR|acpilight}} or {{AUR|kbdlight}} allow to control keyboard backlight though scripts. With the appropriate udev rules or [[sxhkd]] they allow light-level changes without being root.<br />
<br />
====== NVIDIA note ======<br />
<br />
If the brightness does not function correctly through pommed, make sure you have installed the {{AUR|nvidia-bl}} package and insert<br />
<br />
find . -name "*" -exec sed -i 's/mbp_backlight/nvidia_backlight/' '{}' \;<br />
<br />
into the second line of the pommed PKGBUILD build() function and remake the package. From [https://bbs.archlinux.org/viewtopic.php?id=105091 this forum post].<br />
<br />
Another possible solution is to modify the pommed PKGBUILD build():<br />
<br />
find . -name "*" -exec sed -i 's/nvidia_backlight/apple_backlight/' '{}' \;<br />
<br />
If the previous does not work try the following,<br />
<br />
run nvidia-settings, edit the file '/etc/X11/xorg.conf' and add this line into the Device section:<br />
<br />
Option "RegistryDwords" "EnableBrightnessControl=1"<br />
Save and reboot and check backlight buttons work.<br />
More information available at [https://help.ubuntu.com/community/MacBookPro5-5/Precise#LCD Ubuntu MacBookPro5,5]<br />
<br />
=== Wi-Fi ===<br />
<br />
Different MacBook models have different wireless cards.<br />
<br />
You can easily check what card do your MacBook have by:<br />
<br />
# lspci | grep Network<br />
<br />
* If you have an Atheros card, all should work out-of-the-box.<br />
<br />
* If you have a Broadcom card, follow the [[Broadcom wireless]] page.<br />
<br />
* 5.0 and 6.0 generation MacBooks may have a BCM43xx, follow the instructions for the broadcom-wl driver on the [[Broadcom wireless]] page. The interfaces can swap during reboot so its best to define them in a udev rule (instructions on the [[Broadcom wireless]] page).<br />
<br />
* 8.1 generation MacBooks have BCM4331, for which support is not present in either Linux (3.0 and 3.1) or the proprietary drivers by Broadcom. There is however preliminary support for it in Linux 3.2. To run the drivers on earlier kernels, you will need to use [https://backports.wiki.kernel.org/index.php/Documentation/compat-drivers compat-drivers]<br />
<br />
* If you have the correct broadcom DKMS driver (i.e. broadcom-wl-dkms) installed and your wifi card is still not being recognised, try rebuilding the driver (See [[Dynamic Kernel Module Support]]).<br />
<br />
{{Note|If your connection frequently drops, you may have to turn off Wi-Fi power management. If you are running [[pm-utils]], you may override wireless power management by creating an executable file {{ic|/etc/pm/wireless}} with the lines:<br />
#!/bin/sh<br />
iwconfig wlp2s0 power off<br />
}}<br />
<br />
=== Power management ===<br />
<br />
[[Powerdown]] is a very simple to set up set of scripts what will maximize your battery duration. A MacBook Air 2013 with powerdown provides about 11 hours of light usage with just powerdown installed.<br />
All the usual [[power management]] recomendations apply as well.<br />
<br />
Adding 'acpi_osi=' to kernel parameters reportedly brings the battery life of a MacBook Air 2013 from 5 hours to 11-12 hours. See [https://bbs.archlinux.org/viewtopic.php?pid=1530283#p1530283 this forum post] for more information.<br />
<br />
==== Suspend and Hibernate ====<br />
<br />
Suspending (suspend to ram) and hibernating (suspend to disk) work fine out of the box:<br />
<br />
systemctl suspend<br />
<br />
Issues were reported where the machine would "suspend immediately after resume" in certain conditions when suspending by closing the lid. This was solved by setting the option "sleep-inactive-ac-type" to "nothing" using dconf-editor, option path: org &rarr; gnome &rarr; settings-daemon &rarr; plugins &rarr; power).<br />
<br />
See [[Suspend and hibernate]] for details on how to configure hibernation. Noticably, you'll need a swap partition or file (see the mentioned article for further instructions).<br />
<br />
If after suspend laptop is woken up after few seconds, may help to disable all stuff in /proc/acpi/wakeup, exclude LID0:<br />
# echo XHC1 > /proc/acpi/wakeup<br />
$ cat /proc/acpi/wakeup<br />
Device S-state Status Sysfs node<br />
P0P2 S3 *disabled<br />
EC S3 *disabled<br />
HDEF S3 *disabled pci:0000:00:1b.0<br />
RP01 S3 *disabled pci:0000:00:1c.0<br />
RP02 S3 *disabled pci:0000:00:1c.1<br />
RP03 S3 *disabled pci:0000:00:1c.2<br />
ARPT S4 *disabled pci:0000:03:00.0<br />
RP05 S3 *disabled pci:0000:00:1c.4<br />
RP06 S3 *disabled pci:0000:00:1c.5<br />
SPIT S3 *disabled<br />
XHC1 S3 *disabled pci:0000:00:14.0<br />
ADP1 S3 *disabled<br />
LID0 S3 *enabled<br />
And for permanent disabling:<br />
$ cat /etc/udev/rules.d/90-xhc_sleep.rules <br />
<br />
# disable wake from S3 on XHC1<br />
SUBSYSTEM=="pci", KERNEL=="0000:00:14.0", ATTR{power/wakeup}="disabled"<br />
<br />
If this does not work, check that ARPT is disabled, and add a corresponding rule to udev, like this:<br />
<br />
SUBSYSTEM=="pci", KERNEL=="0000:03:00.0", ATTR{power/wakeup}="disabled"<br />
<br />
If this still does not work, try disabling LID0.<br />
This way suspending via lid-closing should be made impossible, so you might want to follow the instructions in [https://bbs.archlinux.org/viewtopic.php?pid=1556046#p1556046 this forum post] to make suspending via both lid-closing and systemd possible, by using systemd services.<br />
<br />
=== Light sensor ===<br />
<br />
The values can be read from:<br />
<br />
/sys/devices/platform/applesmc.768/light<br />
<br />
A "cat" on this path returns two-tuples like (4,0). The below referenced lighter script ignores the second value - which always seems to be 0 - and uses the first number as measured environment lighting brightness value.<br />
<br />
If you want to use the built in light sensor to automatically adjust screen and keyboard backlight brightness check out<br />
'''Lighter''' [https://github.com/Janhouse/lighter] (simple perl script, easy to fine-tune) and '''Lightum''' [https://github.com/poliva/lightum] (Requires Gnome or KDE but is older and more complete than Lighter).<br />
<br />
=== Sound ===<br />
<br />
{{Tip| If using [[ALSA]], the internal speaker might not be disabled when using the headphone jack. To solve this, enable "Auto-mute" using {{ic|alsamixer}}}}<br />
<br />
First of all follow [[ALSA]] wiki page, then if something does not work correctly, continue reading this part.<br />
<br />
Edit your {{ic|/etc/modprobe.d/50-sound.conf}} or {{ic|/etc/modprobe.d/modprobe.conf}} appending this line:<br />
<br />
options snd_hda_intel model=intel-mac-auto<br />
<br />
This should automatically specify the codec in your MacBook. If you have a MacBookPro12,1, you might need<br />
<br />
options snd-hda-intel index=1,0<br />
<br />
instead. Alternatively, for MacBookPro5,X, you can use:<br />
<br />
options snd_hda_intel model=mb5<br />
<br />
(note that the jack output is controlled with "HP").<br />
<br />
If you have an iMac8,1, you should instead use<br />
<br />
options snd-hda-intel model=mbp3 position_fix=2<br />
<br />
You can try to specify other options, that depend on your hardware. All other possible settings are listed in Kernel Documentation, avaible online:<br />
<br />
* [http://www.kernel.org/doc/Documentation/sound/alsa/ALSA-Configuration.txt ALSA-Configuration.txt]<br />
* [http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio.txt HD-Audio.txt]<br />
* [http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt HD-Audio-Models.txt].}}<br />
<br />
Then, reboot.<br />
<br />
=== Bluetooth ===<br />
<br />
Bluetooth should work out-of-the box. See the article on [[Bluetooth]] to install and configure all software needed.<br />
<br />
=== Magic Mouse ===<br />
<br />
If you use a magic mouse you will find it works nicely out of the box. You might want to tweak some settings such as ''scroll-speed'' or ''acceleration''. There is no GUI for this at this time. The only way to set these settings is to instruct the kernel driver ({{ic|hid_magicmouse}}) with parameters. Create a modprobe config file for your mouse.<br />
<br />
{{hc|1=/etc/modprobe.d/magicmouse.conf|2=<br />
options hid_magicmouse scroll-speed=55 scroll-acceleration=1 emulate_3button=0<br />
}}<br />
<br />
<br />
This will instruct the driver to have a fast scroll-speed, do exponential acceleration and do not emulate a 3 button mouse. You can find an overview of all parameters and their current settings in {{ic|/sys/module/hid_magicmouse/parameters}}.<br />
<br />
To play with the settings without rebooting you can also set them through the command line, like so: <br />
<br />
# echo 55 | sudo tee /sys/module/hid_magicmouse/parameters/scroll_speed<br />
<br />
=== Webcam ===<br />
<br />
==== iSight ====<br />
<br />
{{Note|Linux kernel from 2.6.26 includes the Linux UVC driver natively. '''MBP 6,2+ (Kernel ~2.6.37+) iSight works out of the box''' without the need to use firmware from OS X. Only use {{ic|isight-firmware-tools}} if it doesn't work normally.}}<br />
<br />
iSight webcams on MacBooks or pre 6,2 MacBook Pros (6,2 came out around 2010) require the Apple's proprietary firmware that cannot be redistributed. It must be extracted from OS X and loaded onto Arch.<br />
<br />
You will need to install {{AUR|isight-firmware-tools}} to extract the firmware. This package also includes a udev rule and ELF binary that are necessary, even once you have extracted the firmware file into {{ic|/lib/firmware/isight.fw}}, for the file to be loaded every time you boot your computer (namely {{ic|/etc/udev/rules.d/isight.rules}} which uses {{ic|/usr/lib/udev/ift-load}}).<br />
<br />
Instructions:<br />
<br />
First you need to get the firmware out of a particular file located on your OS X install. It is located in {{ic|/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBVideoSupport.kext/Contents/MacOS/AppleUSBVideoSupport}}.<br />
<br />
{{ Tip | The {{ic|AppleUSBVideoSupport}} file from a OS X 10.6 (Snow Leopard) installation may not work properly. If possible, use the file from OS X 10.5 or earlier.}}<br />
<br />
To mount the OS X drive if multi-booting:<br />
<br />
# sudo mkdir /media/OSX<br />
# sudo mount -t hfsplus /dev/sda2 /media/OSX<br />
<br />
Then, install the {{AUR|isight-firmware-tools}} package.<br />
<br />
Locate the {{ic|AppleUSBVideoSupport}} file in the OS X directory listed above. Either copy it over to your Arch system (Any OS X installation should do, such as an iMac, not just one specific to your system) or, if multi-booting, mount the OS X drive and navigate to the directory. (On 10.7 (Lion) the directory is {{ic|/System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBVideoSupport.kext/Contents/MacOS}}.) In that directory you can go ahead and extract the driver:<br />
<br />
# ift-extract --apple-driver AppleUSBVideoSupport<br />
<br />
When it's done, check that the firmware has been found:<br />
<br />
# ls /lib/firmware/isight.fw<br />
<br />
Once successful, completely '''SHUTDOWN''' your Mac and start it back up again (to clear the hardware state of the webcam). Do ''not'' reboot.<br />
<br />
It should be automatically loaded at boot; if it isn't you can load the '''uvcvideo''' module [[Kernel modules|manually or load it at boot]].<br />
<br />
You can use many applications to test the webcam:<br />
<br />
* MPlayer<br />
<br />
# mplayer tv:// -tv driver=v4l2:width=320:height=240:device=/dev/video0 -fps 30<br />
<br />
* Cheese<br />
* Skype<br />
* Ekiga<br />
<br />
A simple solution to take snapshots is:<br />
<br />
# mplayer tv:// -vf screenshot<br />
<br />
and the pressing the s key to take a snapshot. Files are of the format {{ic|shot\d\d\d\d.png}} and are reported in the standard output.<br />
<br />
==== Facetime HD ====<br />
According to Apple, all recent MacBook models contain a Facetime HD camera instead of the iSight. The following list is an example:<br />
* iMac (21,5" mid 2011)<br />
* iMac (27" mid 2011)<br />
* MacBook Air (mid 2011)<br />
* MacBook Pro (15" early 2011)<br />
* MacBook Pro (17" early 2011)<br />
* MacBook Pro (13" early 2011)<br />
If your MacBook is more recent than the models listed above, it is likely equipped with the Facetime HD camera as well.<br />
<br />
In order to make the camera work, you need to install the {{AUR|bcwc-pcie-dkms}} and {{AUR|bcwc-pcie-firmware}} packages. This will enable camera video support through the {{ic|facetimehd}} kernel module.<br />
<br />
In order to verify if the Facetime camera is working after the installation of both packages, you'll need to reboot your system.<br />
<br />
{{Note|Keep in mind that, although working, this is a reverse-engineered driver. PC suspension is not supported if a program that is keeping the camera active is running.}}<br />
<br />
=== Temperature Sensors ===<br />
<br />
For reading temperature just install {{Pkg|lm_sensors}}. See the [[lm_sensors]] page for more information.<br />
<br />
=== Color Profile ===<br />
<br />
We can use color profiles from OS X.<br />
<br />
First, install the {{AUR|xcalib}} package.<br />
<br />
Second copy pre-saved color profiles placed in {{ic|/Library/ColorSync/Profiles/Displays/}} on OS X partition to {{ic|~/colorprofiles/}} for example.<br />
<br />
There are color profile files agree with in MacBook models; select the right one:<br />
<br />
* '''Color LCD-4271800.icc''' for MacBook Pro with CoreDuo CPU<br />
* '''Color LCD-4271880.icc''' for MacBook with Core2Duo<br />
* '''Color LCD-4271780.icc''' for MacBook (non-Pro) based on CoreDuo or Core2Duo.<br />
<br />
{{Tip|Also OS X allows to save current color profile from ''Displays > Color'' section of the ''Mac OS System Preferences'', in this case file is saved to {{ic|/Users/<username>/Library/ColorSync/Profiles}}.}}<br />
<br />
Finally you can activate it by running<br />
<br />
# xcalib ~/colorprofile.icc<br />
<br />
{{Note|Previous command set the color profile only for the current session; this mean that you must run it every time you login in your system. For automating it you can execute the command by '''Autostart Application''', concording with your DE (or add the command to your login manager's initialization script, e.g. /etc/gdm/Init/Default).}}<br />
<br />
{{Warning|GNOME will revert the profile set by xcalib. It's preferable to set the profile using '''Color''' in settings.}}<br />
<br />
=== Apple Remote ===<br />
<br />
First, to correctly install and configure the '''lirc''' software that control IR see [[LIRC]] wiki.<br />
<br />
Then make LIRC use {{ic|/dev/usb/hiddev0}} (or {{ic|/dev/hiddev0}}) by editing {{ic|/etc/conf.d/lircd}}. Here is how mine look:<br />
<br />
#<br />
# Parameters for lirc daemon<br />
#<br />
LIRC_DEVICE="/dev/usb/hiddev0"<br />
LIRC_DRIVER="macmini"<br />
LIRC_EXTRAOPTS=""<br />
LIRC_CONFIGFILE="/etc/lirc/lircd.conf"<br />
<br />
Use '''irrecord''' (available when installing '''lirc''') to create a configuration file matching your remote control signals (alternatively, you can try to use the {{ic|lircd.conf}} below):<br />
<br />
# irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file<br />
<br />
Start '''lircd''' and use '''irw''' to check if it works.<br />
<br />
Example of an {{ic|/etc/lirc/lircd.conf}}:<br />
<br />
begin remote<br />
<br />
name lircd.conf.macbook<br />
bits 8<br />
eps 30<br />
aeps 100<br />
<br />
one 0 0<br />
zero 0 0<br />
pre_data_bits 24<br />
pre_data 0x87EEFD<br />
gap 211994<br />
toggle_bit_mask 0x87EEFD01<br />
<br />
begin codes<br />
Repeat 0x01<br />
Menu 0x03<br />
Play 0x05<br />
Prev 0x09<br />
Next 0x06<br />
Up 0x0A<br />
Down 0x0C<br />
end codes<br />
<br />
end remote<br />
<br />
=== HFS partition sharing ===<br />
<br />
First, install the {{Pkg|hfsprogs}} package. <br />
<br />
we have to list our partitions. Use<br />
<br />
fdisk -l /dev/sda<br />
<br />
example output:<br />
<br />
# fdisk -l /dev/sda<br />
Device Boot Start End Blocks Id Type<br />
/dev/sda1 1 26 204819 ee GPT<br />
/dev/sda2 26 13602 109051903+ af Unknown<br />
/dev/sda3 * 13602 14478 7031250 83 Linux<br />
/dev/sda4 14478 14594 932832+ 82 Linux swap / Solaris<br />
<br />
As we see, the "Unknown" partition is our OS X partition, which is located in {{ic|/dev/sda2}}.<br />
<br />
Create a "mac" folder in /media:<br />
<br />
# mkdir /media/mac<br />
<br />
Add at the end of ''/etc/fstab'' this line:<br />
<br />
/dev/sda2 /media/mac hfsplus auto,user,rw,exec 0 0<br />
<br />
Mount it :<br />
<br />
mount /media/mac<br />
<br />
and check it:<br />
<br />
ls /media/mac<br />
<br />
=== HFS+ Partitions ===<br />
<br />
==== Journaling ====<br />
<br />
HFS+ partitions, now the default in OS X, are not fully supported by Linux and are mounted as read-only by default. In order to write to an HFS+ partition, the safe way is to disable journaling. This can be accomplished using the OS X Disk Utility. Refer to this [http://support.apple.com/kb/ht2355 Apple support page] for more information or try to do it from the command line:<br />
<br />
Find your partition:<br />
<br />
$ diskutil list<br />
/dev/disk0<br />
#: TYPE NAME SIZE IDENTIFIER<br />
0: GUID_partition_scheme *750.2 GB disk0<br />
1: EFI EFI 209.7 MB disk0s1<br />
2: Apple_HFS OSX 149.5 GB disk0s2<br />
3: Apple_HFS Macintosh HD 599.2 GB disk0s3<br />
4: Apple_Boot Recovery HD 650.0 MB disk0s4<br />
<br />
In this example we will use ''disk0s3'' partition named as ''Macintosh HD''. To know if journaling is activate or not you could execute:<br />
<br />
$ diskutil info /dev/disk0s3 | grep -i journal<br />
File System Personality: Journaled HFS+<br />
Name (User Visible): Mac OS Extended (Journaled)<br />
Journal: Journal size 49152 KB at offset 0x1176000<br />
<br />
As you can read the journaling is active. To turn off the journaling you could execute:<br />
<br />
$ sudo diskutil disableJournal disk0s3<br />
Password:<br />
Journaling has been disabled for volume Macintosh HD on disk0s3<br />
<br />
To verify it is done execute the info command again:<br />
<br />
$diskutil info /dev/disk0s3 | grep -i journal<br />
$<br />
<br />
If you get noting as output, then journaling is disabled.<br />
<br />
However, if you fail to disable journaling. You can change "auto,user,rw,exec" in "/etc/fstab" to "auto,user,force,rw,exec" and mount it.<br />
<br />
====Yosemite and later====<br />
<br />
Since Yosemite, HFS+ partitions are now wrapped a CoreStorage volume. Verify that you have an CoreStorage volume.<br />
<br />
# fdisk -l /dev/sdX<br />
Disk /dev/sdX: 298.1 GiB, 320072933376 bytes, 625142448 sectors<br />
Units: sectors of 1* 512 = 512 bytes<br />
Sector size (logical/physical): 512 bytes / 4096 bytes<br />
I/O size (minimum/optimal): 4096 bytes / 4096 bytes<br />
Disklabel type: gpt<br />
Device Start End Sectors Size Type<br />
/dev/sdX1 40 409639 409600 200M EFI System<br />
/dev/sdX2 409640 623872871 623463232 297.3G Apple Core storage<br />
/dev/sdX3 623872872 625142407 1269536 916.0M Apple boot<br />
<br />
HFS+ uses two volume headers, one 1024 bytes into the device and one 1024 from the end of the device. With the HFS+ partition wrapped in the CoreStorage volume the end of the partition is not actually 1024 bytes from the end of the {{ic|/dev/sdX2}} partition.<br />
To fix this you need to specify {{ic|1=sizelimit=X}} when mounting.<br />
<br />
To determine {{ic|sizelimit}} do the following:<br />
<br />
# Run {{ic|testdisk /dev/sdX}} and select your drive<br />
# Select {{ic|EFI GPT}}<br />
# Select {{ic|Analyse}} and then {{ic|Quick Search}}<br />
<br />
Sample output:<br />
TestDisk 7.0, Data Recovery Utility, April 2015<br />
Christophe GRENIER <grenier@cgsecurity.org><br />
http://www.cgsecurity.org<br />
<br />
Disk /dev/sdX - 320 GB / 298 GiB - CHS 38913 255 63<br />
Partition Start End Size in sectors<br />
P EFI System 40 409639 409600 [EFI]<br />
P Mac HFS 409640 623147815 622738176<br />
P Mac HFS 623872872 625142407 1269536<br />
<br />
What you see now is the output of the HFS partition itself without the CoreStorage volume. Take the size in sectors (622738176 in this example) and multiply by the number of bytes in your logical sector size (512 in this example).<br />
<br />
622738176 * 512 = 318841946112<br />
<br />
Finally, mount your disk with the {{ic|1=sizelimit=X}} option.<br />
<br />
mount /dev/sdX -t hfsplus -o ro,sizelimit=318841946112<br />
<br />
===Home Sharing===<br />
<br />
'''''UID Synchronization'''''<br />
<br />
==== In OS X ====<br />
<br />
{{Note|It is strongly recommended that UID/GID manipulation be done immediately after a new user account is created, in OS X as well as in Arch Linux. If you installed OS X from scratch, then this operation is guaranteed to work after logging into your account for the first time.}}<br />
<br />
===== Step 1: change UID and GID(s) =====<br />
<br />
'''''Pre-Leopard'''''<br />
<br />
# Open '''NetInfo Manager''' located in the ''/Applications/Utilities'' folder.<br />
# If not done for you already, enable access to user account transactions by clicking on the closed lock at the bottom of the window, and entering your account password, or root password if you have created a root account.<br />
# Navigate to ''/users/<new user name>'' where <new user name> is the name of the account that will have read/write access to the folder that will be shared with the primary user in Arch.<br />
# Change the '''UID''' value to 1000 (the value used by default for first user created in Arch).<br />
# Also change the '''GID''' value to 1000 (the value used by default for user account creation in Arch).<br />
# Navigate to {{ic|/groups/<new user name>}}, automatically saving the changes you have made so far.<br />
<br />
{{Note|If you get an error message that the transaction is not allowed, log out and log back in.}}<br />
<br />
'''''Leopard'''''<br />
<br />
In Leopard, the '''NetInfo Manager''' application is not present. A different set of steps is required for UID synchronization:<br />
<br />
# Open '''System Preferences'''.<br />
# Click on '''Users & Groups'''.<br />
# Unlock the pane if not already done so.<br />
# Right-click on the desired user and select '''Advanced Options'''.<br />
# Write down the value of the '''User ID''' field, you will need it later on. Change both the UID and GID to match the UID and GID of the account wished to be shared with in Arch (1000 by default for the first user created in Arch).<br />
<br />
===== Step 2: change "Home" permissions =====<br />
<br />
# Open up '''Terminal''' in the {{ic|/Applications/Utilities}} folder.<br />
<br />
# Enter the following command to reclaim the permission settings of your home folder, replacing <your user name>, <your user group> and <your old UID> with the user name whose UID and GID values you just changed, the group name whose GID value you just changed and the old UID number, respectively.<br />
<br />
# find /User/<your user name> -user <your old UID> -exec chown <your user name>:<your user group> {} \;<br />
<br />
==== In Arch ====<br />
<br />
To synchronize your UID in Arch Linux, you are advised to perform this operation ''while creating a new user account''.<br />
It is therefore recommended that you do this as soon as you install Arch Linux.<br />
<br />
Now you must substitute Arch's home with OS X's home, by modify entries of {{ic|/etc/fstab}}.<br />
<br />
=== Avoid long EFI wait before booting ===<br />
<br />
If your MacBook spends 30 seconds with "white screen" before booting you need to tell the firmware where is the booting partition.<br />
<br />
Boot OS X, if do not have it installed, you can use the install DVD (select language, then click Utilities->Terminal), or another MacBook with OS X (connect the two computers via firewire or thunderbolt, start the other MacBook keeping pressed T, boot your MacBook keeping pressed Options).<br />
<br />
Either way, once you got a OS X terminal running on your MacBook you need to execute, as root, a different command if the boot partition is EFI or it is not:<br />
<br />
# bless --device /dev/disk0s1 --setBoot # if the booting partition is EFI<br />
or<br />
# bless --device /dev/disk0s1 --setBoot --legacy # if the booting partition is not EFI<br />
<br />
(given that if your GRUB or EFI is on sda1, /dev/disk1s2 if it is on sdb2, etc). See also https://bbs.archlinux.org/viewtopic.php?pid=833215 and https://support.apple.com/kb/HT1533 .<br />
<br />
=== Mute startup chime ===<br />
<br />
The startup chime volume is controlled by the EFI variable ''SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82''. So it can be muted with<br />
<br />
# printf "\x07\x00\x00\x00\x00" > /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82<br />
<br />
Alternatively, you can use a OS X install disk to mute the chime. Boot from it, select language, then click ''Utilities > Terminal'', and enter<br />
<br />
# /usr/sbin/nvram SystemAudioVolume=%01<br />
<br />
(or whatever volume you want).<br />
<br />
{{Note|Required formatting of the value provided for key SystemAudioVolume may differ depending on MacBook model and perhaps the version of OS X install media. If the above command fails to work, try enclosing the value in double quotes.}}<br />
<br />
=== kworker using high CPU ===<br />
Sometime with the addition of Yosemite, some users found that kworker CPU usage will spike, as disccused [https://bbs.archlinux.org/viewtopic.php?id=171883&p=11 here]. This is sometimes the result of runaway ACPI interrupts.<br />
<br />
To check and see, you can count the number of recent ACPI interrupts and see if any of them are out of control.<br />
<br />
grep . -r /sys/firmware/acpi/interrupts/<br />
<br />
<br />
If you see that one particular interrupt is out of control (possibly GPE66), i.e., registering hundreds of thousands of lines, you can try disabling it (replace XX with the runaway interrupt):<br />
<br />
<br />
echo "disable" > /sys/firmware/acpi/interrupts/gpeXX<br />
<br />
<br />
Disabling random ACPI interrupts could cause all kinds of problems, so do this at your own risk. If this fixes the problem, there is discussion about how to make a systemd service that automatically disables an interrupt at every boot [https://bbs.archlinux.org/viewtopic.php?pid=1488371 here].<br />
<br />
== rEFIt ==<br />
<br />
{{Note|<br />
* You probably want to have a look at [http://www.rodsbooks.com/refind/ rEFInd], which is some type of successor of rEFIt.<br />
* This is not a requirement. It only gives you a menu to choose between OS X and Arch Linux upon every boot.<br />
}}<br />
<br />
For more see, [http://refit.sourceforge.net/myths/ rEFIt myths].<br />
<br />
In OS X, download the ".dmg" from [http://refit.sourceforge.net/ rEFIt Homepage] and install it.<br />
<br />
{{Note|If you have already partitioned your hard disk in preparation for the Arch installation, rEFIt may not be enabled by default. You will have to run the "enable.sh" script installed in /efi/refit/.}}<br />
<br />
Open up '''Terminal''' and enter:<br />
<br />
cd /efi/refit;<br />
./enable.sh<br />
<br />
=== Problems with rEFIt ===<br />
<br />
If you experience problems after the install of Arch or rEFIt, especially is the right OS is not showing up to boot to or if it dumps you at a GRUB prompt stuck like the following:<br />
<br />
GRUB>_<br />
<br />
Then have a look at this link:<br />
<br />
http://mac.linux.be/content/problems-refit-and-grub-after-installation<br />
<br />
It can give you a basic idea on how to boot off the Arch live cd, mount the problem Arch install, chroot, use gptsync, and reinstall GRUB. This is probably for more advanced users who can translate the commands from a debian system to an Arch system and also apply it to the partitions on their machine. Be careful not to install GRUB in the wrong spot.<br />
<br />
If you need a copy of gptsync you can wget it from here:<br />
http://packages.debian.org/sid/gptsync<br />
or try these, for 64 bit:<br />
<br />
wget http://ftp.us.debian.org/debian/pool/main/r/refit/gptsync_0.14-2_amd64.deb<br />
<br />
and for i386:<br />
<br />
wget http://ftp.us.debian.org/debian/pool/main/r/refit/gptsync_0.14-2_i386.deb<br />
<br />
since they are .deb packages you will need the program {{AUR|deb2targz}}.<br />
<br />
==== Mavericks upgrade breaks Arch boot option ====<br />
For some multi-boot users who utilize a separate Linux boot partition, the OS X Mavericks upgrade may overwrite the boot partition with Apple's own recovery boot filesystem. This breaks the Arch Linux boot option in rEFIt/rEFInd. The best way to proceed in this situation is to abandon a separate boot partition and use the EFI system partition (ESP) to install the bootloader of your choice. It is also recommended that you use rEFInd instead of rEFIt as development on the latter has halted.<br />
<br />
Assuming grub2 as the bootloader:<br />
<br />
Use the Arch LiveCD to boot to a shell and [[Change root|chroot]] to your broken Arch Linux environment.<br />
<br />
Mount the ESP on /boot.<br />
<br />
Edit the fstab and remove the old boot partition and make ESP the new boot partition. Now mount the ESP as the new /boot parition.<br />
# mount -a<br />
<br />
[[install|Reinstall]] the {{pkg|linux}} package.<br />
<br />
Create a new initramfs and vmlinuz in /boot.<br />
# mkinitcpio -p linux<br />
<br />
Install grub.<br />
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub --recheck --debug<br />
<br />
Create a new grub.cfg file.<br />
# grub-mkconfig -o /boot/EFI/grub/grub.cfg<br />
<br />
Make sure that grub.cfg is in the same directory as grubx64.efi.<br />
<br />
Generate a new refind_linux.conf file in /boot simply by running mkrlconf.sh which comes with rEFInd.<br />
<br />
Exit the chroot environment.<br />
<br />
Reboot. You should see a new entry for Arch Linux in rEFInd and it should boot to your Arch Linux installation.<br />
<br />
== Model-specific information ==<br />
<br />
=== MacBook ===<br />
<br />
==== April 2016 12" - Version 9,1 ====<br />
<br />
* Booting from USB via EFI works fine, when giving the {{ic|noapic}} kernel option. (On Ubuntu, also {{ic|noacpi nomodeset}} seem to be necessary.) Remember to hold the Alt key on booting.<br />
<br />
* The wireless card works out of the box with {{ic|brcmfmac}}.<br />
<br />
* Suspend / hibernate does not work.<br />
<br />
* The built-in flash drive does ''not'' work with kernel 4.5.4-1-ARCH, but it ''does'' work with kernel 4.6.0-mainline (install {{AUR|linux-mainline}}). As long as a [http://lists.infradead.org/pipermail/linux-nvme/2016-May/004618.html rather trivial patch] is not merged into the kernel, either this patch must be applied locally or one puts {{ic|modprobe nvme; echo 106b 2003 > /sys/bus/pci/drivers/nvme/new_id}} into a mkinitcpio hook (to be started after the udev hook). The reason is that the NVMe controller of the flash drive doesn't advertise itself with the correct PCI device class. Note that with the patch, a short sleep still seems to be necessary.<br />
<br />
* Audio recording works out of the box. Audio playback doesn't work (still looking for a solution).<br />
<br />
* The keyboard and the touchpad do ''not'' work (still looking for a solution).<br />
** There's a WIP driver [https://github.com/cb22/macbook12-spi-driver here] that sort of works with a DSDT hack (the previous problem with this driver related to battery drain has been fixed now).<br />
*** (nov 2016) keyboard backlight issue https://bbs.archlinux.org/viewtopic.php?id=219631<br />
<br />
==== Mid 2007 13" - Version 2,1 ====<br />
<br />
{{Note|I used the 201212 ISO image.}}<br />
<br />
Since older Macbooks have a 32bit EFI running, the usual installation image is not recognized. You need to either remove the UEFI support from the disc ([[Unified_Extensible_Firmware_Interface#Remove_UEFI_boot_support_from_ISO]]) or build a 32bit EFI version of the disc. The paragraphs below will take the first path to success, booting into BIOS mode and its pitfalls. For a try the other way round, read [[Unified_Extensible_Firmware_Interface#Create_UEFI_bootable_USB_from_ISO]] first.<br />
<br />
First prepare your harddisc according to your wishes. In this scenario it was a "Linux only" approach with<br />
<br />
/dev/sda1 HFS+ AF00 200M -> EFI boot system on Apple HFS+ partition<br />
/dev/sda2 ext4 8300 147G -> arch system<br />
/dev/sda3 swap 8200 1G -> swap<br />
<br />
The {{AUR|hfsprogs}} package contains the tools to handle HFS/HFS+ filesystems. The rEFInd bootloader recognizes it on its own. Usually the partition for the EFI bootloader is a FAT32 (vfat) partition. In this case I tried rEFIt first, which apparently needs the HFS+ filesystem to work, and kept it at that.<br />
<br />
The mount points are:<br />
<br />
/dev/sda2 -> /<br />
/dev/sda1 -> /boot<br />
<br />
The bootloader in use was [http://www.rodsbooks.com/refind/index.html rEFInd] instead of rEFIt. To install it, the rEFInd homepage provides a good guide. Usually it is simply done by copying rEFInd:<br />
<br />
mkdir /boot/EFI<br />
cp -vr /usr/share/refind/drivers_ia32 /boot/EFI/refind/<br />
cp -vr /usr/share/refind/tools_ia32 /boot/EFI/refind/<br />
cp -vr /usr/share/refind/fonts /boot/EFI/refind/<br />
cp -vr /usr/share/refind/icons /boot/EFI/refind/<br />
cp -v /usr/share/refind/refind_ia32.efi /boot/EFI/refind/<br />
cp -v /usr/share/refind/refind.conf-sample /boot/EFI/refind/refind.conf<br />
cp -v /usr/share/refind/refind_linux.conf-sample /boot/refind_linux.conf<br />
<br />
{{Note|I'm using the 32bit version of Arch and refind, since the EFI of the old MacBooks is 32bit. I'm not sure about 32bit rEFInd booting a 64bit Arch...}}<br />
<br />
The pitfall here is, that the system bootet in BIOS compatibility mode and not in EFI mode. You cannot therefore use {{ic|efibootmgr}}, because the EFI variables (even with 'modprobe efivars') are not available. While installing the system get {{AUR|mactel-boot}}. The {{ic|hfs-bless}} utility comes in handy, when blessing the EFI bootloader. This is done by calling:<br />
<br />
hfs-bless /boot/EFI/refind/refind_ia32.efi<br />
<br />
Since the Linux kernel does come with EFI stub enabled, it seems a good idea to run it through a bootloader first. Especially if it runs not out of the box. But using rEFInd makes GRUB (or any other bootloader) obsolete, because of that.<br />
<br />
{{Note|In the refind_linux.conf you add any kernel option you may want as long as you use the EFI stub of your kernel. In refind.conf you adjust your needs for the bootloader itself, like menu entries. If you use them (menu entries), rEFInd should not look for these EFI stub kernels itself, so blacklist the directories used in here, like {{ic|/boot/}}.}}<br />
<br />
Not running out of the box is unfortunately the initial stage for the kernel. Since we installed it in BIOS mode, two modules are missing to grant access to the root partition while booting. Hence the 'initfsram-linux.img' can not be found/loaded. Adding the following modules to your 'MODULES' line in {{ic|/etc/mkinitcpio.conf}} solved this ([https://bbs.archlinux.org/viewtopic.php?pid=1139226#p1139226 original post]).<br />
<br />
{{hc|/etc/mkinitcpio.conf|2=<br />
MODULES="ahci sd_mod"}}<br />
<br />
Rebuild your kernel image:<br />
<br />
mkinitcpio -p linux<br />
<br />
The bootloader rEFInd can scan kernels even out of the '/boot/...' directory and assumes an efi kernel even without the extension '.efi'. If you do not want to try out special kernels, this should work without the hassle to copy each kernel after building to some spot special.<br />
<br />
If you happen to get multiple entries for one boot image, it often results of a previous installation of a bootloader within the MBR. To remove that, try the following - taken from the [http://ubuntuforums.org/showpost.php?p=7828260&postcount=4 original post]. This is valid for GPT partitioned discs, so please check your environment and save your MBR first.<br />
<br />
# dd if=/dev/zero of=/dev/sda bs=440 count=1<br />
<br />
=== MacBook Pro ===<br />
<br />
==== Early 2015 13"/15" - Version 12,x/11,4+ ====<br />
<br />
===== Wireless =====<br />
The {{ic|brcmfmac}} driver is working as of 2015-11-20, with newer firmware necessary for working 5GHz support ([https://bugzilla.kernel.org/show_bug.cgi?id=100201#c65 see here.])<br />
<br />
{{<br />
Note| On the Macbook Pro 12,1 if the {{ic|brcmfmac}} driver can not be started and the following errors occur in the journal:<br />
<br />
{{bc|<nowiki><br />
brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported<br />
brcmfmac: brcmf_pcie_probe: failed 14e4:43ba<br />
</nowiki>}}<br />
<br />
then check whether [[Power_management#PCI_Runtime_Power_Management|PCI runtime power management]] is enabled on the device, and disable it if so.<br />
<br />
}}<br />
<br />
===== Bluetooth =====<br />
Bluetooth is fully supported starting from kernel-4.4.0.<br />
<br />
===== Suspend & Power Off (11,4+) =====<br />
The 11,4 and 11,5 MacBook Pros do not shutdown or suspend correctly with the default kernel. This issue is being addressed in [https://bugzilla.kernel.org/show_bug.cgi?id=103211 Bug 103211] and a temporary patch is currently available in {{AUR|linux-macbook}}.<br />
<br />
===== Keyboard & Trackpad =====<br />
Haptic feedback works out of the box due to the trackpad's built-in firmware.<br />
<br />
There are several drivers available that provide multitouch support. The following have been confirmed working with the MacBookPro12,1.<br />
<br />
For {{Pkg|xf86-input-libinput}} the following configuration emulates some features from the OS X functionality. For more options see {{man|4|libinput|url=https://www.mankier.com/4/libinput}}.<br />
{{hc|1=/etc/X11/xorg.conf.d/90-libinput.conf|2=<br />
Section "InputClass"<br />
Identifier "libinput touchpad catchall"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Driver "libinput"<br />
Option "NaturalScrolling" "true"<br />
EndSection<br />
}}<br />
<br />
For {{Pkg|xf86-input-synaptics}} the following configuration is necessary to make the touchpad work fully.<br />
{{hc|1=/etc/X11/xorg.conf.d/60-magictrackpad.conf|2=<br />
Section "InputClass"<br />
Identifier "Trackpad"<br />
Driver "synaptics"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
EndSection<br />
}}<br />
<br />
Further, some US/ANSI keyboards suffer from an issue where the tilde key (~, the key vertically between Esc and Tab) registers as < and >. The following config file fixes this issue.<br />
<br />
{{hc|1=/etc/modprobe.d/hid_apple.conf|2=<br />
options hid_apple iso_layout=0<br />
}}<br />
<br />
See [https://bugzilla.kernel.org/show_bug.cgi?id=96771 this kernel bugzilla] for more details and the relevant patches for earlier kernels.<br />
<br />
===== Graphics =====<br />
For Intel-only graphics, install the {{Pkg|xf86-video-intel}} package. For more information or OpenGL/3D support, follow instructions at [[Intel graphics]].<br />
<br />
For Dual Graphics see [[MacBookPro11,x#Graphics]].<br />
<br />
{{Note|The kernel parameters ''acpi_backlight'', ''i915.lvds_downclock'', ''i915.enable_ips'', and ''intel_iommu'' are no longer necessary as of kernel 4.2.}}<br />
{{Note|(Kernel 4.10.8, MacBook Pro 11,4) If you experience system lock ups and/or tearing in Xorg, remove the .{{Pkg|xf86-video-intel}} completely, including any config file you made for it. Xorg will default to its modesetting DDX driver. The performance of this driver is good and the locks go away. See also: [[Intel graphics]]}}<br />
<br />
==== 2012 - 2014 models ====<br />
<br />
* [[MacBookPro11,x]] (Late 2013—Mid 2014)<br />
* [[MacBookPro10,x]] (Mid 2012—Early 2013)<br />
<br />
=== MacBook Air===<br />
<br />
==== Early 2014 11" - Version 6,1 ====<br />
This is almost the same as the 2013 version, where the only known difference is a slightly faster processor. The version numbers have not been changed since the 2013 version.<br />
<br />
It works excellently after following the instructions for the MBA 2013 13" here and in the forum thread.<br />
Bluetooth, which has been reported not working for some people with the 2013 version, works without trouble for the 2014 version, although it should be excactly the same.<br />
<br />
{{Note| Unless you have a local repository on a USB disk, you need a USB to ethernet adaptor or a USB wireless adaptor supported natively by the kernel to easily install Arch Linux, since you have to install the {{AUR|broadcom-wl-dkms}} package to make the internal wireless adaptor work.}}<br />
<br />
Unresolved issues:<br />
* There is no driver for the webcam yet.<br />
* rEFInd uses 30 seconds to start booting. Using the bless trick stops rEFInd from loading, and it has to be re-installed.<br />
<br />
==== Mid 2013 13" - Version 6,2 ====<br />
[https://bbs.archlinux.org/viewtopic.php?id=165899 Dedicated forum thread]<br />
===== Installing and booting =====<br />
Booting from a normal 2013.6 USB key works fine, but I could not seem to get either GRUB or Syslinux working.<br />
<br />
I was able to boot by first installing Arch Linux following the MacBook guide at the wiki (having a separate FAT32 /boot partition). Skip the bootloader installation. <br />
<br />
Installing [http://www.rodsbooks.com/refind/getting.html rEFInd] from OS X (important!) and installing the EFI stub loader made me able to boot fine.<br />
<br />
[https://bbs.archlinux.org/viewtopic.php?id=165710 Dedicated thread].<br />
<br />
{{Note| Installing [http://www.rodsbooks.com/refind/getting.html rEFInd] from Linux (or from OS X, but to the esp) also works fine}}<br />
<br />
===== Arch Only Installation =====<br />
This method works without rEFInd and uses grub to boot EFI. Partition as follows:<br />
<br />
/dev/sda1 200M Microsoft basic data<br />
/dev/sda2 256M Linux filesystem<br />
/dev/sda3 4G Linux swap<br />
/dev/sda4 108.6G Linux filesystem<br />
<br />
sda1 can also be a HFS+ partition for EFI. This example chooses to use FAT32 (vfat). Although swap is optional, it is required for hibernation. Instead of sda4 for root and home, an alternative partition scheme would be to make sda4 as root and sda5 as home.<br />
<br />
Format and mount:<br />
<br />
mkfs.vfat -F 32 /dev/sda1<br />
mkfs.ext2 /dev/sda2<br />
mkswap /dev/sda3<br />
swapon /dev/sda3<br />
mkfs.ext4 /dev/sda4<br />
<br />
mount /dev/sda4 /mnt<br />
mkdir /mnt/boot<br />
mount/dev/sda2 /mnt/boot<br />
mkdir /mnt/boot/efi<br />
mount /dev/sda1 /mnt/boot/efi<br />
<br />
Finish the installation according to the [[Installation guide]] and skip anything after the bootloader. After you have generated your initramfs and set root passwd follow below to setup grub:<br />
<br />
pacman -S grub efibootmgr<br />
mount -t efivarfs efivarfs /sys/firmware/efi/efivars<br />
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck --debug<br />
grub-mkconfig -o /boot/efi/EFI/grub/grub.cfg<br />
cp /boot/efi/EFI/grub/grub.cfg /boot/grub/grub.cfg<br />
cp /boot/efi/EFI/grub/grubx64.efi /boot/efi/EFI/boot/bootx64.efi}}<br />
<br />
Now you can exit/unmount/reboot:<br />
exit<br />
umount -R /mnt<br />
reboot<br />
<br />
===== Stability problems =====<br />
{{Note| Passing {{ic|<nowiki>libata.force=1:noncq</nowiki>}} to the kernel parameters solves the problem.}}<br />
This is the big worry for me. Every now and then my system hangs for a brief moment and everything involving net or disk access just hangs there for a while and then it seems to work. <br />
So far it only seems to happen when I run something disk- or CPU-intensive. Also had an occassion when I could not start X and just got this repeating all over my screen:<br />
<br />
ata1.00: failed command: WRITE FPDMA QUEUED<br />
ata1.00: cmd 61/08:f0:10:8c:c2/00:00:0b:00:00/40 tag 30 ncq 4096 out<br />
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)<br />
ata1.00: status: { DRDY }<br />
<br />
On the next attempt it worked fine.<br />
I did SMART short and long tests on my disk and they returned fine:<br />
<br />
[http://pastebin.com/vRE4T2Ld smartctl -a]<br />
<br />
There are some messages in my boot that indicate this could be disk and/or ACPI related.<br />
<br />
These are with 2013-06 ISO, 3.9.7-1 2013 x86_64 kernel.<br />
<br />
[http://pastebin.com/mjTJaPFa journalctl -b]<br />
Seems to only work with the headphone jack, not with the speakers.<br />
<br />
[http://pastebin.com/SdAcHuKh dmesg]<br />
<br />
===== Marvell ATA suspend bugs =====<br />
If you have 2013 MacBook Air with a Marvell 128 or 256 GB drive, you might get the following ata errors instead after pm-suspend/resumes:<br />
<br />
ata1: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen<br />
ata1: irq_stat 0x00400000, PHY RDY changed<br />
ata1: SError: { PHYRdyChg }<br />
ata1: hard resetting link<br />
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)<br />
ata1.00: unexpected _GTF length (8)<br />
ata1.00: unexpected _GTF length (8)<br />
ata1.00: configured for UDMA/33<br />
ata1: EH complete<br />
<br />
Try what Patrick and Tejun figured out on the [https://bugzilla.kernel.org/show_bug.cgi?id=62351 linux bug]. I followed what Patrick describes with sata_alpm, and I haven't seen the issue since.<br />
<br />
There are more steps on how to resolve this issue in [https://bbs.archlinux.org/viewtopic.php?pid=1562168#p1562168 this thread on the Arch forum]<br />
<br />
===== Suspend/Resume =====<br />
Brightness is either 0% or 100% after resuming from suspend. Until the kernel is fixed, use patjak's fix by installing {{AUR|mba6x_bl-dkms}}. Patjak's github is at [https://github.com/patjak/mba6x_bl].<br />
===== WiFi =====<br />
WiFi does not work out of the box. Install {{AUR|broadcom-wl-dkms}} to connect to a network. <br />
<br />
===== Touchpad =====<br />
Since 3.10.3 kernel touchpad works perfectly with {{Pkg|xf86-input-synaptics}}.<br />
<br />
===== Audio =====<br />
As of Linux 3.12, sound works out of the box. If you do not get sound with only {{pkg|alsa-utils}}, you may need to create a /etc/asound.conf with below entries:<br />
<br />
defaults.pcm.card 1<br />
defaults.pcm.device 0<br />
defaults.ctl.card 1<br />
<br />
==== Mid 2012 13" — version 5,2 ====<br />
<br />
Kernel panics using default boot media under arch kernel 3.5. Adding <code>intremap=off</code> fixes this. Additionally, there are problems loading the <code>applesmc</code> module (meaning the temperature sensors, fan, and keyboard backlight do not work). These problems are fixed in the linux 3.6-rc4 mainline kernel (I have tested).<br />
<br />
==== Mid 2012 11.5" — Version 5,1 ====<br />
<br />
If you have issues with waking from sleep while in X11 such as a black screen or showing the console with a frozen mouse cursor then remove {{Pkg|xf86-input-synaptics}} and install {{AUR|xf86-input-mtrack-git}}. This fixed errors such as <br />
(EE) [dix] bcm5974: unable to find touch point 0<br />
and backtraces that causes X11 to crash. This might apply to Version 5,2 assuming they use the same trackpad.<br />
<br />
==== Mid 2011 — version 4,x ====<br />
<br />
Works out-of-the-box since kernel 3.2. It is recommended to use [[Archboot]], install [[GRUB]] and use EFI.<br />
<br />
==== Early 2008 — version 1,1 ====<br />
<br />
Everything works out of the box though you will need the {{Pkg|b43-fwcutter}} package (or simply {{AUR|b43-firmware}}) for the wireless adapter to work.<br />
<br />
Since this model has only one USB port, you may find it easiest to install Arch with a powered USB hub. Plug a USB network adapter (wireless or ethernet adapter to plug into a USB port) and your Arch installation media into the USB hub.<br />
<br />
If you can't get any result by scanning wireless network after boot, unload modules <code>b43</code> and <code>ssb</code> and load them again:<br />
<br />
rmmod ssb<br />
rmmod b43<br />
modprobe b43<br />
<br />
There is a good chance you will find what's wrong with DMA from the dmesg log.<br />
<br />
Even if you can scan wireless networks after reloading the modules, it's still possible that you will only be able to connect to some networks, but not all of them. According to a more detailed discussion here: http://crunchbang.org/forums/viewtopic.php?id=17368, adding <code>pio=1,qos=0</code> options to the b43 module can solve this problem.<br />
<br />
I tested this for a 13' MacBookAir1,1 with a BCM4321 chipset, and it works.<br />
<br />
== See also ==<br />
* '''MacBook Air'''<br />
** [http://dabase.com/blog/Macbook_Air_Early_2014_Archlinux/ Macbook Air Early 2014 — dabase.com]<br />
** [http://www.frankshin.com/installing-archlinux-on-macbook-air-2013/ Installing Archlinux on Macbook Air 2013 — Frank Shin]<br />
** [http://blog.panks.me/posts/2013/06/arch-linux-installation-with-os-x-on-macbook-air-dual-boot/ Arch Linux Installation with OS X on Macbook Air (Dual Boot) — Pankaj Kumar]<br />
** [http://ryangehrig.com/index.php/arch-linux-on-macbook-air-2013/ Arch Linux – MacBook Air 2013 — Ryan Gehrig]<br />
** [http://www.nico.schottelius.org/blog/macbook-air-42-archlinux/ Installing Linux on a Macbook Air (4,2) — Nico Schottelius]<br />
** [http://www.dm9.se/?p=398 Arch linux single, pure efi boot on the macbook air3,1/3,2 — DIMENSION9]<br />
* '''MacBook Pro'''<br />
** http://www.netsoc.tcd.ie/~theorie/interblag/2010/01/30/installing-arch-linux-on-a-mac-pro/<br />
** http://allanmcrae.com/2010/04/installing-arch-on-a-macbook-pro-5-5/<br />
** http://allanmcrae.com/2012/04/installing-arch-on-a-macbook-pro-8-1/<br />
** http://linux-junky.blogspot.com/2011/08/triple-boot-archlinux-windows-7-and-mac.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=471755User talk:Pierro78/Asus chromebook flip2017-03-24T15:36:24Z<p>Pierro78: </p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
* wifi after suspend/resume : for wifi to work after resume blacklist btsdio as explained by keenerd : https://archlinuxarm.org/forum/viewtopic.php?f=60&t=9477<br />
<br />
Issues :<br />
* after suspend/resume wifi didn't reconnect well to the 5Ghz band of my archer C7 but the regular 2.4Ghz band seems to be doing fine<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html<br />
* Facebook Group : Asus Chromebook Flip C100PA - Flippin' Awesome : https://www.facebook.com/groups/1880671302151825/ <br>(as of 2016 there is more activity in the google plus communities though ...)</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=466407User talk:Pierro78/Asus chromebook flip2017-01-23T16:23:34Z<p>Pierro78: g+ communities remark</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
* wifi after suspend/resume : for wifi to work after resume blacklist btsdio as explained by keenerd : https://archlinuxarm.org/forum/viewtopic.php?f=60&t=9477<br />
<br />
Issues :<br />
* after suspend/resume wifi didn't reconnect well to the 5Ghz band of my acer C7 but the regular 2.4Ghz band seems to be doing fine<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html<br />
* Facebook Group : Asus Chromebook Flip C100PA - Flippin' Awesome : https://www.facebook.com/groups/1880671302151825/ <br>(as of 2016 there is more activity in the google plus communities though ...)</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=466406User talk:Pierro78/Asus chromebook flip2017-01-23T16:21:49Z<p>Pierro78: add fb group</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
* wifi after suspend/resume : for wifi to work after resume blacklist btsdio as explained by keenerd : https://archlinuxarm.org/forum/viewtopic.php?f=60&t=9477<br />
<br />
Issues :<br />
* after suspend/resume wifi didn't reconnect well to the 5Ghz band of my acer C7 but the regular 2.4Ghz band seems to be doing fine<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html<br />
* Facebook Group : Asus Chromebook Flip C100PA - Flippin' Awesome : https://www.facebook.com/groups/1880671302151825/</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=461037User talk:Pierro78/Asus chromebook flip2017-01-01T09:57:37Z<p>Pierro78: minor</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
* wifi after suspend/resume : for wifi to work after resume blacklist btsdio as explained by keenerd : https://archlinuxarm.org/forum/viewtopic.php?f=60&t=9477<br />
<br />
Issues :<br />
* after suspend/resume wifi didn't reconnect well to the 5Ghz band of my acer C7 but the regular 2.4Ghz band seems to be doing fine<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=461036User talk:Pierro78/Asus chromebook flip2017-01-01T09:55:52Z<p>Pierro78: suspend/resume and issue</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
* suspend/resume : blacklist btsdio as explained by keenerd : https://archlinuxarm.org/forum/viewtopic.php?f=60&t=9477<br />
<br />
Issues :<br />
* after suspend/resume wifi didn't reconnect well to the 5Ghz band of my acer C7 but the regular 2.4Ghz band seems to be doing fine<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=460969User talk:Pierro78/Asus chromebook flip2016-12-31T17:02:23Z<p>Pierro78: minor</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* chromium 55 doesn t seem to work as of 31th of december 2016 but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=460968User talk:Pierro78/Asus chromebook flip2016-12-31T17:01:58Z<p>Pierro78: chromium issue</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* chromium 55 doesn t seem to work as of 31th of decembre but chromium 54 is OK : https://archlinuxarm.org/forum/viewtopic.php?f=15&t=11034<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=460967User talk:Pierro78/Asus chromebook flip2016-12-31T16:58:25Z<p>Pierro78: timezone</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* timezone : il you live in Europe/Paris you may need to run : timedatectl set-timezone Europe/Paris<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=460966User talk:Pierro78/Asus chromebook flip2016-12-31T16:40:46Z<p>Pierro78: keyboard</p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* keyboard : if you have a gb keyboard run : localectl set-x11-keymap gb chromebook (see [[Chrome_OS_devices#xkeyboard_configuration]])<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=457414User talk:Pierro78/Asus chromebook flip2016-11-21T23:04:01Z<p>Pierro78: </p>
<hr />
<div>How to install archlinux :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=457411User talk:Pierro78/Asus chromebook flip2016-11-21T22:29:32Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675<br />
<br />
See also :<br />
* General information (Crouton, etc ...) : http://www.bitkistl.com/2016/06/chromebook-flip-c100-user-guide.html</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=456194User talk:Pierro78/Asus chromebook flip2016-11-06T23:49:59Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
* video player : vlc seems to work better than smplayer with mpv but you need to set video output mode and alsa-audio-device as explained on http://kmkeen.com/c100p-tweaks/<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=456190User talk:Pierro78/Asus chromebook flip2016-11-06T23:28:30Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)<br />
<br />
Issues :<br />
* it looks like there are issues getting xorg hardware acceleration / 3D working, see : https://archlinuxarm.org/forum/viewtopic.php?f=9&t=10675</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=456188User talk:Pierro78/Asus chromebook flip2016-11-06T22:58:52Z<p>Pierro78: minor</p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio (working for me, [[User:Pierro78]])<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=456187User talk:Pierro78/Asus chromebook flip2016-11-06T22:58:04Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio<br />
** also on https://hackaday.io/project/8770-archmbook :<br>To enable audio run<br>amixer -c 0 sset “Right Speaker Mixer Right DAC” unmute<br>amixer -c 0 sset “Left Speaker Mixer Left DAC” unmute<br>sudo alsactl store<br>that will enable sound somehow (I still only have sound from one youtube instance, but for me that is ok)</div>Pierro78https://wiki.archlinux.org/index.php?title=Chrome_OS_devices/Chromebook&diff=455672Chrome OS devices/Chromebook2016-10-31T22:09:32Z<p>Pierro78: /* Hardware Comparisons */ added link to some notes for the chromebook flip</p>
<hr />
<div>[[Category:Laptops]]<br />
[[ja:Chromebook]]<br />
Main article: [[Chrome OS devices]].<br />
<br />
== Introduction ==<br />
<br />
=== First generation of Chromebooks ===<br />
<br />
The first generation of Chromebooks: Google Cr-48, Samsung Series 5 500 and Acer AC700 use [http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/custom-firmware#TOC-H2C Insyde H2O firmware] and not Coreboot firmware. There are three approaches how to install Arch Linux on these devices:<br />
* Flash a custom H2C firmware (only available for Google Cr-48) and install Arch as on any other UEFI laptop.<br />
* Take the ChrUbuntu approach which uses the Chrome OS kernel and modules.<br />
* Build and sign your own kernel, see [https://plus.google.com/+OlofJohansson/posts/34PYU79eUqP].<br />
<br />
== Hardware Comparisons ==<br />
<br />
{{Warning|The availability of SeaBIOS does not promise device compatibility for Linux or that the pre-installed SeaBIOS works properly. Before purchasing a device visit its page on the ArchWiki and look for Linux users' posts about that model.}}<br />
<br />
<center><br />
{| class="wikitable"<br />
|-<br />
|+ style="background:#BFD7FF"| Chromebook Models<br />
|-<br />
! Available<br />
! Brand<br />
! Model<br />
! Processor<br />
! RAM<br />
! Storage<br />
! Upgradable<br />
! Screen<br />
! Resolution<br />
! SeaBIOS<br />
! Remarks<br />
|-<br />
| Dec 2010<br />
| Google <br />
| Cr-48<br />
| 1.66 GHz Intel Atom N455<br />
| rowspan="3"|2GB<br>DDR3<br />
| rowspan="4"|16GB SSD<br />
| {{G|mSATA}}<br />
| rowspan="2"|12.1 in<br>(30.7 cm)<br />
| rowspan="2"|1280x800<br>(16:10)<br />
| {{R|Unavailable for<br>1st generation}}<br />
| {{G|[http://cr-48.wikispaces.com/Flash+BIOS Custom H2C<br>firmware available]}}<br />
|-<br />
| Jun 2011<br />
| Samsung<br />
| Series 5<br>XE500C21<br />
| rowspan="2"|1.66 GHz Intel Atom N570<br />
| {{G|mSATA}}<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| Jul 2011<br />
| Acer<br />
| AC700<br />
| {{G|mSATA<br>Mini}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| May 2012<br />
| rowspan="2"|Samsung<br />
| Series 5<br>XE550C22<br />
| 1.3 GHz Intel Celeron 867<br>1.6 Ghz Intel Core i5 2467M<br />
| 4GB<br>DDR3<br />
| {{G|mSATA}}<br />
| 12.1 in<br>(30.7 cm)<br />
| 1280x800<br>(16:10)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2012<br />
| [[Samsung_Chromebook_(ARM)|Series 3<br>XE303C12]]<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Nov 2012<br />
| Acer<br />
| [[Acer_C710_Chromebook|C710]]<br />
| 1.1 GHz Intel Celeron 847<br>1.5 GHz Intel Celeron 1007U<br />
| rowspan="2"|2-4GB<br>DDR3<br />
| rowspan="2"|320GB HDD<br>16GB SSD<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="3"|Feb 2013<br />
| HP<br />
| Pavilion 14<br>Chromebook<br />
| 1.1 GHz Intel Celeron 847<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| 14 in<br>(35.6 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Lenovo<br />
| ThinkPad X131e<br>Chromebook<br />
| 1.5 GHz Intel Celeron 1007U<br />
| 4GB<br>DDR3<br />
| 16GB SSD<br />
| {{G|mSATA}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Google<br />
| Chromebook<br>Pixel<br />
| 1.8 GHz Intel Core i5 3427U<br />
| 4GB<br>DDR3<br />
| 32GB iSSD<br>64GB iSSD<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br>(3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2013<br />
| rowspan="2"|HP<br />
| Chromebook 11<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| rowspan="9"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM<br>installation identical to<br>[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Samsung XE303C12]}}<br />
|-<br />
| rowspan="2"|Nov 2013<br />
| [[HP_Chromebook_14|Chromebook 14]]<br />
| 1.4 GHz Intel Celeron 2955U<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 14 in<br>( 35.6 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Acer<br />
| [[Acer_C720_Chromebook|C720/C720P<br>Chromebook]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Jan 2014<br />
| Toshiba<br />
| CB30/CB35<br>Chromebook<br />
| 1.4 GHz Intel Celeron 2955U<br />
| 2GB DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 13.3 in<br>(33.8 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Apr 2014<br />
| Dell<br />
| [[Dell Chromebook 11|Chromebook 11]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| 2GB DDR3<br>4GB DDR3<br />
|rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires stock<br>SeaBIOS patching}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="5"|Jun 2014<br />
| Lenovo<br />
| N20/N20P<br>Chromebook<br />
| rowspan="2"|2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Asus<br />
| Chromebook <br>C200/C300<br />
| 2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Lenovo<br />
| ThinkPad 11e<br>Chromebook<br />
| rowspan="2"|1.83 GHz Intel BayTrail-M N2930<br />
| rowspan="4"|4GB DDR3<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| ThinkPad Yoga 11e<br>Chromebook<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE503C12/C32<br />
| 1.9 GHz Exynos 5 Octa 5420<br>2 GHz Exynos 5 Octa 5800<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook-2 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Jul 2014<br />
| HEXA<br />
| Chromebook Pi<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{No}}<br />
| {{R|Custom firmware<br>not available yet}}<br />
|-<br />
| Aug 2014<br />
| Acer<br />
| CB5-311<br>Chromebook 13<br />
| 2.1 GHz Nvidia Tegra K1<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| rowspan="2"|13.3 in<br>(33.8 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| rowspan="2"|Sep 2014<br />
| Toshiba<br />
| [[Toshiba Chromebook 2|CB30/CB35<br>Chromebook 2]]<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Acer<br />
| [[CB3-111 | CB3-111]]<br>Chromebook 11<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="4"|Oct 2014<br />
| C730<br>Chromebook 11<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|HP<br />
| Chromebook 14<br>G3<br />
| 2.1 GHz Nvidia Tegra K1<br />
| {{No}}<br />
| 14 in<br>(35.6 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Chromebook 11<br>G3<br />
| rowspan="3"|2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="4"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE500C12<br />
| 2GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Feb 2015<br />
| Dell<br />
| Chromebook 11<br>3120<br />
| rowspan="3"| 2GB DDR3<br>4GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Acer<br />
| C740 (EDU)<br>Chromebook 11<br />
| rowspan="2"|1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| CB5-571<br>Chromebook 15<br />
| 16GB<br>32GB<br />
| {{G|42mm M.2<br>NGFF}}<br />
| rowspan="2"|15.6 in<br>(39.6 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| rowspan="5"|Mar 2015<br />
| C910 (EDU)<br>Chromebook 15<br />
| 1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br>2.2 GHz Intel Core i5-5200U<br />
| 4GB DDR3<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|[https://www.reddit.com/r/chromeos/comments/3asc4f/no_physical_differences_beteen_acer_chromebook/ 42mm M.2<br>NGFF]}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Google<br />
| [[Chromebook Pixel 2|Chromebook<br>Pixel 2]]<br />
| 2.2 GHz Intel Core i5-5200U<br>2.4 GHz Intel Core i7-5500U<br />
| 8GB DDR3<br>16GB DDR3<br />
| 32GB<br>64GB<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br> (3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Lenovo<br />
| N21<br>Chromebook<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| 2GB DDR3<br>4GB DDR3<br />
| rowspan="4"|16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Haier<br />
| HR-166R<br>Chromebook 11<br />
| rowspan="3"|1.8 GHz Rockchip RK3288<br />
| rowspan="2"|2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Hisense<br />
| Chromebook C11<br />
| {{No}}<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/rockchip/hisense-chromebook-c11 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| June 2015<br />
| Asus<br />
| C100PA<br>(Chromebook flip)<br />
| 2/4GB<br />
| {{No}}<br />
| 10.1 in<br />
| 1280 x 800<br>(16:10)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p Supported by<br>Arch Linux ARM]}}<small><br>[[User talk:Pierro78/Asus chromebook flip|notes]]</small><br />
|}<br />
</center></div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Asus_chromebook_flip&diff=455671User:Pierro78/Asus chromebook flip2016-10-31T22:06:59Z<p>Pierro78: </p>
<hr />
<div>TBD<br />
<br />
some notes on [[User talk:Pierro78/Asus chromebook flip]]</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455670User talk:Pierro78/Asus chromebook flip2016-10-31T22:04:59Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : <br>pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455669User talk:Pierro78/Asus chromebook flip2016-10-31T22:01:06Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455667User talk:Pierro78/Asus chromebook flip2016-10-31T21:51:13Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* audio : https://wiki.debian.org/InstallingDebianOn/Asus/C201#Audio</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455660User talk:Pierro78/Asus chromebook flip2016-10-31T21:04:28Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : pacman -Syu xorg-server xorg-xinit xorg-server-utils</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455613User talk:Pierro78/Asus chromebook flip2016-10-31T17:38:58Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://kmkeen.com/c100p-tweaks/<br />
<br />
Other tips :<br />
* install xorg-server : pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* configure touchpad : TBD - see https://wiki.debian.org/InstallingDebianOn/Asus/C201#Touchpad</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455612User talk:Pierro78/Asus chromebook flip2016-10-31T17:34:18Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://kmkeen.com/c100p-tweaks/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
<br />
Other tips :<br />
* install xorg-server : pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* configure touchpad : TBD - see https://wiki.debian.org/InstallingDebianOn/Asus/C201#Touchpad</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455611User talk:Pierro78/Asus chromebook flip2016-10-31T17:34:00Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://kmkeen.com/c100p-tweaks/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
<br />
Other tips :<br />
* install xorg server : pacman -Syu xorg-server xorg-xinit xorg-server-utils<br />
* configure touchpad : TBD - see https://wiki.debian.org/InstallingDebianOn/Asus/C201#Touchpad</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455610User talk:Pierro78/Asus chromebook flip2016-10-31T17:33:16Z<p>Pierro78: </p>
<hr />
<div>some info on :<br />
<br />
* http://kmkeen.com/c100p-tweaks/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/<br />
<br />
Other tips :<br />
* install xorg server : pacman -Syu xorg-server xorg-xinit xorg-server-utils</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78&diff=455568User:Pierro782016-10-31T09:44:33Z<p>Pierro78: </p>
<hr />
<div>[[User:Pierro78/Dell Precision M6500]]<br />
<br />
[[User_talk:Pierro78/Asus_chromebook_flip]]</div>Pierro78https://wiki.archlinux.org/index.php?title=User_talk:Pierro78/Asus_chromebook_flip&diff=455289User talk:Pierro78/Asus chromebook flip2016-10-27T14:47:32Z<p>Pierro78: Created page with "some info on : * http://kmkeen.com/c100p-tweaks/ * https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p * http://www.muktware.io/how-to-install-arch-l..."</p>
<hr />
<div>some info on :<br />
<br />
* http://kmkeen.com/c100p-tweaks/<br />
* https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p<br />
* http://www.muktware.io/how-to-install-arch-linux-arm-on-asus-chromebook-flip/</div>Pierro78https://wiki.archlinux.org/index.php?title=User:Pierro78/Asus_chromebook_flip&diff=455288User:Pierro78/Asus chromebook flip2016-10-27T14:46:01Z<p>Pierro78: Created page with "TBD"</p>
<hr />
<div>TBD</div>Pierro78https://wiki.archlinux.org/index.php?title=Chrome_OS_devices/Chromebook&diff=455286Chrome OS devices/Chromebook2016-10-27T14:45:33Z<p>Pierro78: /* Hardware Comparisons */ link</p>
<hr />
<div>[[Category:Laptops]]<br />
[[ja:Chromebook]]<br />
Main article: [[Chrome OS devices]].<br />
<br />
== Introduction ==<br />
<br />
=== First generation of Chromebooks ===<br />
<br />
The first generation of Chromebooks: Google Cr-48, Samsung Series 5 500 and Acer AC700 use [http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/custom-firmware#TOC-H2C Insyde H2O firmware] and not Coreboot firmware. There are three approaches how to install Arch Linux on these devices:<br />
* Flash a custom H2C firmware (only available for Google Cr-48) and install Arch as on any other UEFI laptop.<br />
* Take the ChrUbuntu approach which uses the Chrome OS kernel and modules.<br />
* Build and sign your own kernel, see [https://plus.google.com/+OlofJohansson/posts/34PYU79eUqP].<br />
<br />
== Hardware Comparisons ==<br />
<br />
{{Warning|The availability of SeaBIOS does not promise device compatibility for Linux or that the pre-installed SeaBIOS works properly. Before purchasing a device visit its page on the ArchWiki and look for Linux users' posts about that model.}}<br />
<br />
<center><br />
{| class="wikitable"<br />
|-<br />
|+ style="background:#BFD7FF"| Chromebook Models<br />
|-<br />
! Available<br />
! Brand<br />
! Model<br />
! Processor<br />
! RAM<br />
! Storage<br />
! Upgradable<br />
! Screen<br />
! Resolution<br />
! SeaBIOS<br />
! Remarks<br />
|-<br />
| Dec 2010<br />
| Google <br />
| Cr-48<br />
| 1.66 GHz Intel Atom N455<br />
| rowspan="3"|2GB<br>DDR3<br />
| rowspan="4"|16GB SSD<br />
| {{G|mSATA}}<br />
| rowspan="2"|12.1 in<br>(30.7 cm)<br />
| rowspan="2"|1280x800<br>(16:10)<br />
| {{R|Unavailable for<br>1st generation}}<br />
| {{G|[http://cr-48.wikispaces.com/Flash+BIOS Custom H2C<br>firmware available]}}<br />
|-<br />
| Jun 2011<br />
| Samsung<br />
| Series 5<br>XE500C21<br />
| rowspan="2"|1.66 GHz Intel Atom N570<br />
| {{G|mSATA}}<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| Jul 2011<br />
| Acer<br />
| AC700<br />
| {{G|mSATA<br>Mini}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| May 2012<br />
| rowspan="2"|Samsung<br />
| Series 5<br>XE550C22<br />
| 1.3 GHz Intel Celeron 867<br>1.6 Ghz Intel Core i5 2467M<br />
| 4GB<br>DDR3<br />
| {{G|mSATA}}<br />
| 12.1 in<br>(30.7 cm)<br />
| 1280x800<br>(16:10)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2012<br />
| [[Samsung_Chromebook_(ARM)|Series 3<br>XE303C12]]<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Nov 2012<br />
| Acer<br />
| [[Acer_C710_Chromebook|C710]]<br />
| 1.1 GHz Intel Celeron 847<br>1.5 GHz Intel Celeron 1007U<br />
| rowspan="2"|2-4GB<br>DDR3<br />
| rowspan="2"|320GB HDD<br>16GB SSD<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="3"|Feb 2013<br />
| HP<br />
| Pavilion 14<br>Chromebook<br />
| 1.1 GHz Intel Celeron 847<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| 14 in<br>(35.6 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Lenovo<br />
| ThinkPad X131e<br>Chromebook<br />
| 1.5 GHz Intel Celeron 1007U<br />
| 4GB<br>DDR3<br />
| 16GB SSD<br />
| {{G|mSATA}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Google<br />
| Chromebook<br>Pixel<br />
| 1.8 GHz Intel Core i5 3427U<br />
| 4GB<br>DDR3<br />
| 32GB iSSD<br>64GB iSSD<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br>(3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2013<br />
| rowspan="2"|HP<br />
| Chromebook 11<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| rowspan="9"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM<br>installation identical to<br>[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Samsung XE303C12]}}<br />
|-<br />
| rowspan="2"|Nov 2013<br />
| [[HP_Chromebook_14|Chromebook 14]]<br />
| 1.4 GHz Intel Celeron 2955U<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 14 in<br>( 35.6 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Acer<br />
| [[Acer_C720_Chromebook|C720/C720P<br>Chromebook]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Jan 2014<br />
| Toshiba<br />
| CB30/CB35<br>Chromebook<br />
| 1.4 GHz Intel Celeron 2955U<br />
| 2GB DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 13.3 in<br>(33.8 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Apr 2014<br />
| Dell<br />
| [[Dell Chromebook 11|Chromebook 11]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| 2GB DDR3<br>4GB DDR3<br />
|rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires stock<br>SeaBIOS patching}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="5"|Jun 2014<br />
| Lenovo<br />
| N20/N20P<br>Chromebook<br />
| rowspan="2"|2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Asus<br />
| Chromebook <br>C200/C300<br />
| 2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Lenovo<br />
| ThinkPad 11e<br>Chromebook<br />
| rowspan="2"|1.83 GHz Intel BayTrail-M N2930<br />
| rowspan="4"|4GB DDR3<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| ThinkPad Yoga 11e<br>Chromebook<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE503C12/C32<br />
| 1.9 GHz Exynos 5 Octa 5420<br>2 GHz Exynos 5 Octa 5800<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook-2 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Jul 2014<br />
| HEXA<br />
| Chromebook Pi<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{No}}<br />
| {{R|Custom firmware<br>not available yet}}<br />
|-<br />
| Aug 2014<br />
| Acer<br />
| CB5-311<br>Chromebook 13<br />
| 2.1 GHz Nvidia Tegra K1<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| rowspan="2"|13.3 in<br>(33.8 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| rowspan="2"|Sep 2014<br />
| Toshiba<br />
| [[Toshiba Chromebook 2|CB30/CB35<br>Chromebook 2]]<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Acer<br />
| [[CB3-111 | CB3-111]]<br>Chromebook 11<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="4"|Oct 2014<br />
| C730<br>Chromebook 11<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|HP<br />
| Chromebook 14<br>G3<br />
| 2.1 GHz Nvidia Tegra K1<br />
| {{No}}<br />
| 14 in<br>(35.6 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Chromebook 11<br>G3<br />
| rowspan="3"|2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="4"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE500C12<br />
| 2GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Feb 2015<br />
| Dell<br />
| Chromebook 11<br>3120<br />
| rowspan="3"| 2GB DDR3<br>4GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Acer<br />
| C740 (EDU)<br>Chromebook 11<br />
| rowspan="2"|1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| CB5-571<br>Chromebook 15<br />
| 16GB<br>32GB<br />
| {{G|42mm M.2<br>NGFF}}<br />
| rowspan="2"|15.6 in<br>(39.6 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| rowspan="5"|Mar 2015<br />
| C910 (EDU)<br>Chromebook 15<br />
| 1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br>2.2 GHz Intel Core i5-5200U<br />
| 4GB DDR3<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|[https://www.reddit.com/r/chromeos/comments/3asc4f/no_physical_differences_beteen_acer_chromebook/ 42mm M.2<br>NGFF]}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Google<br />
| [[Chromebook Pixel 2|Chromebook<br>Pixel 2]]<br />
| 2.2 GHz Intel Core i5-5200U<br>2.4 GHz Intel Core i7-5500U<br />
| 8GB DDR3<br>16GB DDR3<br />
| 32GB<br>64GB<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br> (3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Lenovo<br />
| N21<br>Chromebook<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| 2GB DDR3<br>4GB DDR3<br />
| rowspan="4"|16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Haier<br />
| HR-166R<br>Chromebook 11<br />
| rowspan="3"|1.8 GHz Rockchip RK3288<br />
| rowspan="2"|2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Hisense<br />
| Chromebook C11<br />
| {{No}}<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/rockchip/hisense-chromebook-c11 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| June 2015<br />
| Asus<br />
| C100P<br>([[Asus chromebook flip|Chromebook flip]])<br />
| 2/4GB<br />
| {{No}}<br />
| 10.1 in<br />
| 1280 x 800<br>(16:10)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p Supported by<br>Arch Linux ARM]}}<br />
|}<br />
</center></div>Pierro78https://wiki.archlinux.org/index.php?title=Chrome_OS_devices/Chromebook&diff=455285Chrome OS devices/Chromebook2016-10-27T14:41:33Z<p>Pierro78: /* Hardware Comparisons */ bios info</p>
<hr />
<div>[[Category:Laptops]]<br />
[[ja:Chromebook]]<br />
Main article: [[Chrome OS devices]].<br />
<br />
== Introduction ==<br />
<br />
=== First generation of Chromebooks ===<br />
<br />
The first generation of Chromebooks: Google Cr-48, Samsung Series 5 500 and Acer AC700 use [http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/custom-firmware#TOC-H2C Insyde H2O firmware] and not Coreboot firmware. There are three approaches how to install Arch Linux on these devices:<br />
* Flash a custom H2C firmware (only available for Google Cr-48) and install Arch as on any other UEFI laptop.<br />
* Take the ChrUbuntu approach which uses the Chrome OS kernel and modules.<br />
* Build and sign your own kernel, see [https://plus.google.com/+OlofJohansson/posts/34PYU79eUqP].<br />
<br />
== Hardware Comparisons ==<br />
<br />
{{Warning|The availability of SeaBIOS does not promise device compatibility for Linux or that the pre-installed SeaBIOS works properly. Before purchasing a device visit its page on the ArchWiki and look for Linux users' posts about that model.}}<br />
<br />
<center><br />
{| class="wikitable"<br />
|-<br />
|+ style="background:#BFD7FF"| Chromebook Models<br />
|-<br />
! Available<br />
! Brand<br />
! Model<br />
! Processor<br />
! RAM<br />
! Storage<br />
! Upgradable<br />
! Screen<br />
! Resolution<br />
! SeaBIOS<br />
! Remarks<br />
|-<br />
| Dec 2010<br />
| Google <br />
| Cr-48<br />
| 1.66 GHz Intel Atom N455<br />
| rowspan="3"|2GB<br>DDR3<br />
| rowspan="4"|16GB SSD<br />
| {{G|mSATA}}<br />
| rowspan="2"|12.1 in<br>(30.7 cm)<br />
| rowspan="2"|1280x800<br>(16:10)<br />
| {{R|Unavailable for<br>1st generation}}<br />
| {{G|[http://cr-48.wikispaces.com/Flash+BIOS Custom H2C<br>firmware available]}}<br />
|-<br />
| Jun 2011<br />
| Samsung<br />
| Series 5<br>XE500C21<br />
| rowspan="2"|1.66 GHz Intel Atom N570<br />
| {{G|mSATA}}<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| Jul 2011<br />
| Acer<br />
| AC700<br />
| {{G|mSATA<br>Mini}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{R|Unavailable for<br>1st generation}}<br />
|<br />
|-<br />
| May 2012<br />
| rowspan="2"|Samsung<br />
| Series 5<br>XE550C22<br />
| 1.3 GHz Intel Celeron 867<br>1.6 Ghz Intel Core i5 2467M<br />
| 4GB<br>DDR3<br />
| {{G|mSATA}}<br />
| 12.1 in<br>(30.7 cm)<br />
| 1280x800<br>(16:10)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2012<br />
| [[Samsung_Chromebook_(ARM)|Series 3<br>XE303C12]]<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Nov 2012<br />
| Acer<br />
| [[Acer_C710_Chromebook|C710]]<br />
| 1.1 GHz Intel Celeron 847<br>1.5 GHz Intel Celeron 1007U<br />
| rowspan="2"|2-4GB<br>DDR3<br />
| rowspan="2"|320GB HDD<br>16GB SSD<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="3"|Feb 2013<br />
| HP<br />
| Pavilion 14<br>Chromebook<br />
| 1.1 GHz Intel Celeron 847<br />
| {{G|SATA<br>2.5" 7,9.5mm}}<br />
| 14 in<br>(35.6 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Lenovo<br />
| ThinkPad X131e<br>Chromebook<br />
| 1.5 GHz Intel Celeron 1007U<br />
| 4GB<br>DDR3<br />
| 16GB SSD<br />
| {{G|mSATA}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|In custom<br>firmware only}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Google<br />
| Chromebook<br>Pixel<br />
| 1.8 GHz Intel Core i5 3427U<br />
| 4GB<br>DDR3<br />
| 32GB iSSD<br>64GB iSSD<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br>(3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Oct 2013<br />
| rowspan="2"|HP<br />
| Chromebook 11<br />
| 1.7 GHz Samsung Exynos 5250<br />
| 2GB<br>DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| rowspan="9"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM<br>installation identical to<br>[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook Samsung XE303C12]}}<br />
|-<br />
| rowspan="2"|Nov 2013<br />
| [[HP_Chromebook_14|Chromebook 14]]<br />
| 1.4 GHz Intel Celeron 2955U<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 14 in<br>( 35.6 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Acer<br />
| [[Acer_C720_Chromebook|C720/C720P<br>Chromebook]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| {{G|42mm M.2<br>NGFF}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Jan 2014<br />
| Toshiba<br />
| CB30/CB35<br>Chromebook<br />
| 1.4 GHz Intel Celeron 2955U<br />
| 2GB DDR3<br />
| 16GB eMMC<br />
| {{No}}<br />
| 13.3 in<br>(33.8 cm)<br />
| {{Yes}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| Apr 2014<br />
| Dell<br />
| [[Dell Chromebook 11|Chromebook 11]]<br />
| 1.4 GHz Intel Celeron 2955U<br>1.7 GHz Intel Core i3-4005U<br />
| 2GB DDR3<br>4GB DDR3<br />
|rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires stock<br>SeaBIOS patching}}<br />
| {{G|Custom firmware<br>available}}<br />
|-<br />
| rowspan="5"|Jun 2014<br />
| Lenovo<br />
| N20/N20P<br>Chromebook<br />
| rowspan="2"|2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Asus<br />
| Chromebook <br>C200/C300<br />
| 2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Lenovo<br />
| ThinkPad 11e<br>Chromebook<br />
| rowspan="2"|1.83 GHz Intel BayTrail-M N2930<br />
| rowspan="4"|4GB DDR3<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| ThinkPad Yoga 11e<br>Chromebook<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE503C12/C32<br />
| 1.9 GHz Exynos 5 Octa 5420<br>2 GHz Exynos 5 Octa 5800<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br>13.3 in<br>(33.8 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook-2 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| Jul 2014<br />
| HEXA<br />
| Chromebook Pi<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 32GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{No}}<br />
| {{R|Custom firmware<br>not available yet}}<br />
|-<br />
| Aug 2014<br />
| Acer<br />
| CB5-311<br>Chromebook 13<br />
| 2.1 GHz Nvidia Tegra K1<br />
| rowspan="2"|2GB DDR3<br>4GB DDR3<br />
| 16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| rowspan="2"|13.3 in<br>(33.8 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| rowspan="2"|Sep 2014<br />
| Toshiba<br />
| [[Toshiba Chromebook 2|CB30/CB35<br>Chromebook 2]]<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="2"| 16GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|Acer<br />
| [[CB3-111 | CB3-111]]<br>Chromebook 11<br />
| 2.1 GHz Intel BayTrail-M N2830<br />
| 2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="4"|Oct 2014<br />
| C730<br>Chromebook 11<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|2GB DDR3<br>4GB DDR3<br />
| rowspan="2"|16GB eMMC<br>32GB eMMC<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="2"|HP<br />
| Chromebook 14<br>G3<br />
| 2.1 GHz Nvidia Tegra K1<br />
| {{No}}<br />
| 14 in<br>(35.6 cm)<br />
| 1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Chromebook 11<br>G3<br />
| rowspan="3"|2.16 GHz Intel BayTrail-M N2840<br />
| rowspan="3"|16GB eMMC<br />
| {{No}}<br />
| rowspan="4"|11.6 in<br>(29.5 cm)<br />
| rowspan="4"|1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Samsung<br />
| Chromebook 2<br>XE500C12<br />
| 2GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Feb 2015<br />
| Dell<br />
| Chromebook 11<br>3120<br />
| rowspan="3"| 2GB DDR3<br>4GB DDR3<br />
| {{No}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| rowspan="3"|Acer<br />
| C740 (EDU)<br>Chromebook 11<br />
| rowspan="2"|1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|42mm M.2<br>NGFF}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| CB5-571<br>Chromebook 15<br />
| 16GB<br>32GB<br />
| {{G|42mm M.2<br>NGFF}}<br />
| rowspan="2"|15.6 in<br>(39.6 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br>1920x1080<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| rowspan="5"|Mar 2015<br />
| C910 (EDU)<br>Chromebook 15<br />
| 1.5 GHz Intel Celeron 3205U<br>2.00 GHz Intel Core i3-5005U<br>2.2 GHz Intel Core i5-5200U<br />
| 4GB DDR3<br />
| 16GB SSD<br>32GB SSD<br />
| {{G|[https://www.reddit.com/r/chromeos/comments/3asc4f/no_physical_differences_beteen_acer_chromebook/ 42mm M.2<br>NGFF]}}<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Google<br />
| [[Chromebook Pixel 2|Chromebook<br>Pixel 2]]<br />
| 2.2 GHz Intel Core i5-5200U<br>2.4 GHz Intel Core i7-5500U<br />
| 8GB DDR3<br>16GB DDR3<br />
| 32GB<br>64GB<br />
| {{No}}<br />
| 12.85 in<br>(32.6 cm)<br />
| 2560x1700<br> (3:2)<br />
| {{Yes}}<br />
| {{G|Custom firmware script<br>only writes to RW_LEGACY}}<br />
|-<br />
| Lenovo<br />
| N21<br>Chromebook<br />
| 2.16 GHz Intel BayTrail-M N2840<br />
| 2GB DDR3<br>4GB DDR3<br />
| rowspan="4"|16GB eMMC<br />
| {{No}}<br />
| 11.6 in<br>(29.5 cm)<br />
| 1366x768<br>(16:9)<br />
| {{G|Requires writing<br>SeaBIOS}}<br />
| {{G|Custom firmware script<br>only writes to BOOT_STUB}}<br />
|-<br />
| Haier<br />
| HR-166R<br>Chromebook 11<br />
| rowspan="3"|1.8 GHz Rockchip RK3288<br />
| rowspan="2"|2GB DDR3<br />
| {{No}}<br />
| rowspan="2"|11.6 in<br>(29.5 cm)<br />
| rowspan="2"|1366x768<br>(16:9)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{R|Unsupported by<br>Arch Linux ARM}}<br />
|-<br />
| Hisense<br />
| Chromebook C11<br />
| {{No}}<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[http://archlinuxarm.org/platforms/armv7/rockchip/hisense-chromebook-c11 Supported by<br>Arch Linux ARM]}}<br />
|-<br />
| June 2015<br />
| Asus<br />
| C100P<br>(Chromebook flip)<br />
| 2/4GB<br />
| {{No}}<br />
| 10.1 in<br />
| 1280 x 800<br>(16:10)<br />
| {{R|Unavailable <br>on ARM}}<br />
| {{G|[https://archlinuxarm.org/platforms/armv7/rockchip/asus-chromebook-flip-c100p Supported by<br>Arch Linux ARM]}}<br />
|}<br />
</center></div>Pierro78https://wiki.archlinux.org/index.php?title=Talk:Chrome_OS_devices&diff=455284Talk:Chrome OS devices2016-10-27T14:25:58Z<p>Pierro78: /* Remarks / suggestion about the Chromebook sub-page */ flip</p>
<hr />
<div>== Guidelines for Chrome OS devices page and its subpages ==<br />
<br />
{{note|Please do not comment at this section but only at the [[#Discussion about the guidelines]] subsection}}<br />
<br />
=== Intro ===<br />
<br />
This page is a bit special because it bundles installation and configuration steps for a collection of devices, this is due to the fact these steps are the same for this type of devices dubbed {{ic|Chrome OS devices}}.<br />
<br />
As we already have an Installation and Beginner's guide pages (and also pages about specific topics) this page has the potential to duplicate much of the information that available on other pages, because of that and also as we want to keep uniformity between the misc subpages and devices pages, these following guidelines were constructed in the hope they'll help contributing here and would avoid confusing.<br />
<br />
Notice that these guidelines collected here from the misc talk sections at this page and from ArchWiki maintainers suggestions and requests.<br />
<br />
=== Guidelines ===<br />
<br />
==== Main page: Chrome OS devices ====<br />
<br />
===== Post installation configuration section =====<br />
<br />
* Limit the code posting in this section, especially on the Audio and Hotkeys topics, instead post the code somewhere else (e.g. Github's gists) and link to it here.<br />
<br />
==== Chromebook subpage ====<br />
<br />
===== Hardware comparison table =====<br />
<br />
* Remarks column is for firmwares related remarks only.<br />
* Storage type and upgradability: Please do not guess, we try to keep these details precise, please keep in mind that there're single chip SSD devices (SATA and PCIe), if the storage is soldered to the board it doesn't means it's eMMC so it might be wise googling the storage device model. Also note that sometimes Amazon is wrong and confuse eMMC with SSD. <br />
* Please do not add new column, start a new discussion about it.<br />
<br />
==== Custom firmware subpage ====<br />
<br />
===== Adding detailed information about flashing firmware and unbricking =====<br />
<br />
* A brief explanation of the process of unbricking and the way the write protection works were added in order to give the user enough details so users would have some sense of understanding what steps they should take in case of a problem.<br />
* The ArchWiki should not duplicate information from other sources and it's not an electrical engineering guide to Chromebooks.<br />
* If you're considering adding more detailed how-to on this page about: flashing firmware, unbricking, or anything related to hardware hacking then PLEASE DON'T !, instead post it somewhere else (the forums, your blog) and just add links in the See also section.<br />
<br />
==== Specific device pages ====<br />
<br />
=== Discussion about the guidelines ===<br />
<br />
Here we can discuss the Guidelines section, I hope this would help to limit confusion of users who wants to contribute and will improve communication with the ArchWiki maintainers. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 00:37, 1 April 2015 (UTC)<br />
<br />
== removed old content ==<br />
<br />
=== cgpt command ===<br />
:I moved this from the Chromebook page as it's cluttering the page and not fitted there. We should adapt the [[Chromebook#Alternative_Installation.2C_Install_Arch_Linux_in_addition_to_Chrome_OS|Alternative_Installation.2C_Install_Arch_Linux_in_addition_to_Chrome_OS]] to example the cgpt command or/and create a specific cgpt page but not put this topic on the Chromebook page. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 17:23, 29 September 2014 (UTC)<br />
<br />
You'll save your self a lot of time if you understand this command before you attempt to install Arch on a chromebook.<br />
<br />
This is NON-EXHAUSTIVE but it'll help most people reading this. cgpt --help is nice too.<br />
<br />
Use:<br />
cgpt create /dev/sda<br />
Used to initialise a disk with GPT headers. <br />
<br />
Use:<br />
cgpt show /dev/sda<br />
To list all partitions on disk with boot information for each.<br />
<br />
Use:<br />
cgpt add [options] /dev/sda<br />
Used to modify boot options<br />
<br />
===== Example =====<br />
cgpt add -i 6 -P 5 -S 0 -T 1 /dev/sda<br />
Example: modify partition #6, set priority to 5, successful to false, and boot tries to once(1), on device /dev/sda<br />
cgpt add -i 6 -t unused /dev/sda<br />
Example: delete partition #6.<br />
<br />
cgpt add -i 1-12 <br />
:Partition number to change<br />
cgpt add -P 9-0<br />
:Priority 9 > 1 (Higher number will try to boot first) <br />
cgpt add -T 0-99<br />
:Tries, used with the successful flag. Will try to boot this partition x times until tries = 0 then it will try next lower priority partition. <br />
cgpt add -S 0-1<br />
:Successful flag, if 1 will try to boot this partition forever. Be careful with this one! If 0 and tries > 0 it will try to boot this partition until it' out of tries.<br />
<br />
If installing yourself, don't forget to copy this onto your arch partition!.<br />
<br />
== CD burner for 64 bits ==<br />
<br />
Hi,<br />
<br />
Can you post an equivalent method for burning CD for install 64 bit, like you did [https://wiki.archlinux.org/index.php/Chromebook#64-bit_installation here]? Thanks a lot,--[[User:Xan|Xan]] ([[User talk:Xan|talk]]) 13:23, 29 December 2014 (UTC)<br />
<br />
== Transitioning the page to a generic Chrome OS devices page ==<br />
<br />
Due to the fact that both the Installation and Post installation sections fit to all Chrome OS devices it seem like the logical step is to convert this page to a generic 'Chrome OS devices' page.<br />
<br />
Per ArchWiki admins advice ([[User:Kynikos]], [[User:Alad]]) it been suggested that the best approach would be:<br />
* Keep the common steps in the main page.<br />
* Create sub pages for specific information for each type of devices (Chromebook, Chromebox, Chromebase(?)).<br />
* Link on the main page to these sub pages (Chromebook, ...), not using transclusions.<br />
<br />
With accordance to the above I devised the following steps, notice they are numbered, I recommend following this order and annotate 'DONE' when each step is finished.<br />
# Change each (appropriate) occurrence of Chromebook(s) in the common sections Chrome OS device(s). DONE, mostly, the rest of the renaming can be done at the end of this process. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 10:24, 17 March 2015 (UTC)<br />
# Transition the [[Chromebook#Introduction]] section to a common intro and move the specific Chromebook details from the [[Chromebook#Introduction]] to the [[Chromebook#Chromebook models]] section. DONE, further refinements of the Introduction can be done later. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 10:52, 17 March 2015 (UTC)<br />
# Rename the page to 'Chrome OS devices' page. Done. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 08:12, 22 March 2015 (UTC)<br />
# Rename [[Custom firmware for Chrome OS devices]] page to 'Chrome OS devices/Custom firmware' Done. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 08:12, 22 March 2015 (UTC)<br />
# Move out the [[Chromebook#Chromebook models]] section to 'Chrome OS devices/Chromebook' and link on the 'Chrome OS devices' page. Done, need to add introduction for the sub-page and short explanation of the link to the sub-page on the main page. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 08:12, 22 March 2015 (UTC)<br />
# Create 'Chrome OS devices/Chromebox' with hardware comparison (important columns are existence of SeaBios in stock firmware and availability of custom firmware).<br />
# Add details on how to flash a custom firmware on Chromebox (the recommend method only, EZ Setup Script) to the 'Chrome OS devices' page.<br />
<br />
Suggested guidelines:<br />
* The main page should be a simple walkthrough installation guide, linear and easy to follow, would only mention the recommended method of each type of device (Chromebook, ...) for flashing custom firmware and the needed steps (link to custom firmware for more details).<br />
* The Specific sub pages for each type of device (Chromebook, ...) would only include short introduction and hardware comparison, no installation how to and post configuration sections.<br />
<br />
If anyone has any suggestions or remarks please comment here, I added the steps above and guidelines so anyone could help making the necessary changes (though I'll do my best to getting this done shortly). [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 08:35, 17 March 2015 (UTC)<br />
<br />
: Commenting to myself: renaming the page to 'Google devices' is not a good idea, it a little bit confusing due to the existence of Android, also I guessing the page will better indexed in search engines if it actually include 'Chrome' in its name so it will be ranked better when users will google how to install Arch on Chromebook/Chromebox, so I believe renaming to 'Chrome OS devices' would be better, I'll update this section in accordance if there no objection. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 09:17, 17 March 2015 (UTC)<br />
<br />
:: p.s. I'm holding renaming the page for a day or two so other will have the time to respond. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 10:55, 17 March 2015 (UTC)<br />
<br />
=== Product names ===<br />
<br />
:Merged from [[Talk:Acer C720 Chromebook]] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:40, 20 March 2015 (UTC)<br />
<br />
Are there objections to naming this page "Acer C720" (without the Chromebook) ? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:16, 20 March 2015 (UTC)<br />
<br />
: Not really, though I will point out that in order to keep it simple to clients Acer actually publicize the product as "Acer C720 Chromebook 11", also the C740 is "Acer C740 Chromebook 11", C910 is "Acer C910 Chromebook 15" and so on (actually this might be coming from Google). Also I don't know how this will affect search ranking (google: "Arch on Acer Chromebook"). In any way, this should be a uniform change and should added as a directive in a section in the (current) Chromebook talk page about adding a new ChromeOs device page. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:50, 20 March 2015 (UTC)<br />
<br />
:: Alad, did you reached a decision? anyway you decide we should add it to the guidelines section above (keep the device page name simple, only brand and model or have also {{ic|Chromebook}} and screen size in the name string), and close this discussion.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 00:46, 1 April 2015 (UTC)<br />
<br />
:::Well, simplicity is important but shouldn't prioritize over clarity or upstream naming, though cf. [http://us.acer.com/ac/en/US/content/series/c720]). Third-party resellers seem to prefer the "Chromebook" naming. If we keep redirects in place search ranking shouldn't be affected, but don't quote me on that. I'll leave the decision up to you. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:26, 1 April 2015 (UTC)<br />
<br />
== Remarks / suggestion about the Chromebook sub-page ==<br />
<br />
* Chromeos has codenames for the various hardware products, it might help if the table had a column with the codename to disambiguate which chromebook is what (better than comparing marketing names) [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: Personally I'm against adding more columns and further details about each device in the Chromebook table. These code names are available at [http://chromium.org/chromium-os/developer-information-for-chrome-os-devices Chromium OS site] which is linked at the main page, we should not duplicate this info. We tried (well I can testify about myself) to limit the information in the hardware comparison table while still keep it useful for quick comparison with focus about the specific features of Chromebook that might be limiting (like limited storage soldered on board). I agree that the code names are useful but the table would be just to big with another column and therefore on small screen / low res would expand down / drop down another line (at least it is true for my Chromebook (C720)). I was thinking about removing the Weight column but only for expanding a little the firmware related columns.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:38, 21 July 2015 (UTC)<br />
* I noticed that all arm chromebooks have a column which says Seabios is not supported, as if it's a bad thing. Arm Chromebooks don't need seabios, arch linux arm boots just fine on them without it. [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: Let's be a little precise, the text in the cell saying "Unavailable on Arm" which is different from "Seabios is not supported", but yep, it isn't the best phrasing, but saying that SeaBIOS isn't needed for ARM would be a little confusing as users might believe that running Arch Linux on all ARM based Chromebook models is all fine and dandy. I would prefer to keep the text as it is but maybe remove the red color. A better rephrasing is welcome.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]])<br />
* The "not needing seabios" way of doing things is also available on intel since the chromeos stock firmware/bootloader works the same way. As long as you partition the drive properly and you provide a kernel partition, the bootloader should load it just fine. No firmware flashing/warranty voiding should be required if there's no seabios. [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: To be blunt, I think it's silly for us, Arch Linux users, to give this a place in the official Arch Wiki. AFAIK you need to load Chrome OS kernel or bring your own kernel. We should not instruct Arch Linux users with band aid solutions, the goal of Arch Linux users buying Chromebook is to have official Arch kernel package running on their devices. I would love to stand corrected but I don't believe that just re-partitioning is gonna get Arch kernel running on Chromebook without SeaBIOS payload.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:38, 21 July 2015 (UTC)<br />
::: p.s. we already telling users what their options if their device didn't come with a SeaBIOS payload, [[Chrome_OS_devices#Models_without_SeaBIOS]].[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:54, 21 July 2015 (UTC)<br />
:::: I think this is too poorly advertised and it yields to more people looking for ways to flash(read: brick) their chromebooks instead of just using the default feature of the chromeos bootloader. sadly... [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 23:43, 21 July 2015 (UTC)<br />
* RK3288 max frequency is 1.8GHz, the 2.5GHz is a mistake. [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: Thanks, now it's fixed. [[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:46, 21 July 2015 (UTC)<br />
* The ASUS rk3288 based chromebooks are missing(C201(2/4GB), C100(aka flip, 2/4GB)). [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: You're welcome to add them to the table.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:46, 21 July 2015 (UTC)<br />
::: I ve added the flip as I may try to install arch on it. [[User:Pierro78|Pierro78]] ([[User talk:Pierro78|talk]]) 14:25, 27 October 2016 (UTC)<br />
* The Haier chromebook, while there's no arch linux arm page for it, is essentially identical functionality wise with the other rk3288 chromebooks. The instructions are interchangeable, therefore that chromebook is supported. [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 20:07, 21 July 2015 (UTC)<br />
:: Are you sure? if so then you're welcome to add it to the hardware comparison table, be advised that users might buy a device based on the information in the table so just make sure this is true.[[User:Dhead|Dhead]] ([[User talk:Dhead|talk]]) 21:38, 21 July 2015 (UTC)<br />
::: Yep, I worked on the veyron chromebooks. I convinced leming to include all the veyron_ variants in the [https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-veyron/kernel.its its file](veyron_jerry is the one of interest in this case). I already had arch booting on that chromebook :) [[User:Amstan|Amstan]] ([[User talk:Amstan|talk]]) 23:43, 21 July 2015 (UTC)<br />
*I have recently (succesfully) installed Arch on my Dell Chromebook 11 2015 (3120). Is there a specific page for this model, where I can put my findings, or should I rather try to fit it into this page somehow?<br />
:: In my opinion, create a new page for your experience, if it needs some specific steps rather than Chromebook general guide--[[User:Xan|Xan]] ([[User talk:Xan|talk]]) 07:07, 9 April 2016 (UTC)</div>Pierro78