https://wiki.archlinux.org/api.php?action=feedcontributions&user=Thomas+Do&feedformat=atomArchWiki - User contributions [en]2024-03-29T02:27:01ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ICC_profiles&diff=645583ICC profiles2020-12-14T08:59:19Z<p>Thomas Do: Replacing xsane color management link with mirror because original link is dead</p>
<hr />
<div>[[Category:Multimedia]]<br />
[[ja:ICC プロファイル]]<br />
[[ru:ICC profiles]]<br />
As it pertains to general desktop use, an [[Wikipedia:ICC profile|ICC profile]] is a binary file which contains precise data regarding the color attributes of an input, or output device. Single, or multiple profiles can be applied across a system and its devices to produce consistent and repeatable results for graphic and document editing and publishing. ICC profiles are typically calibrated with a [[Wikipedia:Tristimulus colorimeter|(tristimulus) colorimeter]], or a spectrophotometer when absolute color accuracy is required.<br />
<br />
== Utilities ==<br />
<br />
* {{App|ArgyllCMS|ICC compatible color management system. It supports accurate ICC profile creation for scanners, cameras and film recorders, and calibration and profiling of displays and RGB & CMYK printers.|https://argyllcms.com/|{{Pkg|argyllcms}}}}<br />
* {{App|ColorHug|The Hughski ColorHug Colorimeter is a low cost open-source hardware sensor used to calibrate screens. This package includes the client tools which allows the user to upgrade the firmware on the sensor or to query the sensor from command line scripts.|https://github.com/hughski/colorhug-client|{{Pkg|colorhug-client}}}}<br />
* {{App|DisplayCAL|Display calibration and profiling solution with a focus on accuracy and versatility. At its core it relies on ArgyllCMS color management system, to take measurements, create calibrations and profiles, and for a variety of other advanced color related tasks.|https://displaycal.net/|{{Pkg|displaycal}}}}<br />
* {{App|GNOME Color Manager|Set of graphical utilities for color management to be used in the GNOME desktop.|https://gitlab.gnome.org/GNOME/gnome-color-manager|{{Pkg|gnome-color-manager}}}}<br />
* {{App|xcalib|Lightweight monitor calibration loader which can load an ICC monitor profile to be shared across desktop applications.|https://github.com/OpenICC/xcalib|{{Pkg|xcalib}}}}<br />
<br />
== Profile generation ==<br />
<br />
Color management is a workflow of hardware calibration, software profiling and embedding the profile into the picture or video. It's all based on using an [[Wikipedia:ICC profile|ICC profile]].<br />
<br />
=== Colorimeter or spectrometer ===<br />
<br />
It is highly recommended to use a colorimeter or spectrometer device for hardware-assisted display, printer and scanner calibration. For home use there are several affordable colorimeters available. Some are well- or even better-supported under Linux than on other operating systems. Frequently recommended devices are [http://www.xrite.com/colormunki-display X-Rite ColorMunki Display], [http://spyder.datacolor.com/portfolio-view/spyder5express/ DataColor Spyder5 Express] and the open source hardware [http://www.hughski.com/ ColorHug]. You can find more Linux-supported devices listed in the [http://www.argyllcms.com/doc/instruments.html AgyllCMS documentation].<br />
<br />
=== Argyll CMS ===<br />
<br />
The [http://www.argyllcms.com/ Argyll Color Management System] is a complete suite of command-line profile creation and loading tools listed under {{Pkg|argyllcms}}. <br />
<br />
Review the official [http://www.argyllcms.com/doc/ArgyllDoc.html Argyll CMS documentation] for details on how to profile selected devices.<br />
<br />
=== Monitor calibration and profiling with additional calibration hardware ===<br />
<br />
There is a GUI frontend for ArgyllCMS called [http://displaycal.net DisplayCal], available as {{Pkg|displaycal}}. In most common cases you will want to use its default settings. It is a common way to calibrate to a daylight color of 6500K and gamma 2,2. Read the DispalGui documentation for more. Many tutorials are available on the net.<br />
<br />
=== Scanner calibration ===<br />
<br />
Follow the scanner part of the [https://blog.simon-dreher.de/color-management.html scanner calibration] tutorial.<br />
<br />
=== Printer calibration ===<br />
<br />
See {{man|8|cups-calibrate}}.<br />
<br />
=== File transfer ===<br />
<br />
Profile generation on a Windows or macOS system is one of the easiest and most widely recommended methods to obtain a ICC monitor profile. Since ICC color profiles are written to an open specification, they are compatible across operating systems. Transferring profiles from one OS to another can be used as a workaround for the lack of support for certain spectrophotometers or colorimeters under Linux: one can simply produce a profile on a different OS and then use it in a Linux workflow. Note that the system on which the profile is generated must host the exact same video card and monitor for which the profile is to be used. Once generation of an ICC profile, or a series of profiles is complete on a Windows system, copy the file(s) from the default path:<br />
<br />
C:\WINDOWS\System32\spool\drivers\color<br />
<br />
macOS generally stores saved ICC profiles in one of two locations:<br />
<br />
/Library/ColorSync/Profiles<br />
/Users/USER_NAME/Library/ColorSync/Profile<br />
<br />
Once the appropriate {{Ic|.icc/.icm}} files have been copied, install the device profiles to your desired system. Common installation device profiles directories on Linux include:<br />
<br />
/usr/share/color/icc<br />
/usr/local/share/color/icc<br />
/home/USER_NAME/.color/icc<br />
<br />
{{Note|Ensure that the calibrated contrast, brightness and RGB settings of the monitor do not change between the time of calibration and the loading of the ICC profile. Use this method only if you are absolutely certain that neither Linux nor the other OS does anything behind your back (in video drivers or vendor utilities) that alters the signal actually sent to the display, or the way the display interprets the signal. Watch out for "Broadcast RGB" or similar settings. One concrete example where profiling in Windows and Linux yields [https://bugzilla.kernel.org/show_bug.cgi?id&#61;70721 significantly different results] is the Lenovo Ideapad Yoga 2 Pro laptop, because these OSes program the flat panel controller in very different ways.|}}<br />
<br />
=== Gnome Color Manager ===<br />
<br />
On Gnome, an ICC profile can easily be created by using {{pkg|gnome-color-manager}}. Under Gnome, this is accessible via the Control Center and is pretty straightforward to use. You'll need a colorimeter device to use this feature.<br />
<br />
=== LPROF ICC Profiler ===<br />
<br />
[http://lprof.sourceforge.net/ LPROF] is an ICC profiler with a graphical user interface listed under {{AUR|lprof}} in the [[AUR]]. <br />
<br />
{{Note|The following walkthrough has been modified from the ArchWiki article [[Using LPROF to profile monitors]].}}<br />
<br />
==== Monitor calibration ====<br />
<br />
===== Contrast/Brightness =====<br />
<br />
Adjust the lighting in the room to what you will be using when working. Even if your screen is coated with an anti-reflective coating, you should avoid light falling directly on it. Let your monitor warm up for at least an hour for the image to get stabilized. If your calibration device has an ambient diffuser, adjust your room brightness to reach the recommended target lux point.<br />
<br />
# Set the monitor contrast to maximum, or 100%. <br />
# Next, display a pure black over entire screen by creating a small, black PNG image (all pixels have RGB = 0, 0, 0) and opening it up in a picture viewer that is capable of displaying an image in fullscreen mode without any controls.<br />
# Reduce the vertical size of the monitor screen (not the PNG image displayed by a picture viewer but the whole of what's displayed on the screen) to 60% to 70% of the full height. What is revealed above and below the picture is called a ''non-scanned area'', and since that area is not receiving any voltage, it is the blackest of black your monitor is capable of displaying. <br />
# Locate the brightness control (usually a sun, circle with rays projecting from it's edges) and lower the value until the black ''image'' matches the non-scanned area.<br />
<br />
===== Color temperature =====<br />
<br />
As we said in the introduction, setting color temperature must occur at noon. If you only have fixed factory default color temperature, you do not really need to wait for the sunny day to come. Just set it to 6500K.<br />
<br />
Place your monitor so that you can see outside the window ''and'' your screen at the same time. For this step, you also need to create a white square image (RGB = 255, 255, 255), roughly 10 by 10 centimeters (4 by 3 inches). Using the same Gwenview technique as with brightness/contrast, display the white square on a pure black background.<br />
<br />
# First, prepare your eyes by staring at the outside world for a while. Let them adjust to the daylight viewing condition for a few minutes.<br />
# Glance at the monitor, and the white square for a few second (it has to be short, because eyes will readjust quickly).<br />
# If the square seems yellowish, you need higher color temperature, or if it has a blueish cast, the temperature needs to be lowered.<br />
# Keep glancing, looking out the window, and adjusting the white temperature, until the square looks pure white<br />
<br />
Take your time with the steps described above. It is essential to get it right.<br />
<br />
==== Monitor profiling without additional calibration hardware ====<br />
<br />
Start lprof. You will be presented by a fairly large window with multiple tabs on the right. <br />
<br />
# Click on the ''Monitor Profiler'' tab. Then click on the large ''Enter monitor values >>'' button.<br />
# White point should be set to ''6500K (daylight)''.<br />
# Primaries should be set to either ''SMPTE RP145-1994'', or ''EBU Tech.3213-E'' or ''P22'', or whatever appropriate values for your monitor. If you come across correct values for your monitor, enter those by selecting ''User Defined'' from the drop-down. If in doubt, you may use ''P22'' for all monitors with Trinitron CRTs (in this case, ''Trinitron'' is not related to Sony Trinitron mointors and TVs), and ''SMPTE RP145-1994'' for other CRTs.<br />
# Click the ''Set Gamma and Black Point'' button.<br />
# You will now see a full-screen view of two charts with some controls at the bottom.<br />
# Uncheck the ''Link channels'' check-box and adjust individual Red, Green, and Blue gamma by either moving the slider left or right, or by entering and changing values in the three boxes to the left. The goal is to make the chart on the left (the smaller square one) flat. When you are satisfied with how it looks, check the ''Link channels'' check-box and adjust the gamma again.<br />
# When you are done, click ''OK''. Click ''OK'' again.<br />
<br />
When you are finished entering monitor values, you might want to enter some information about the monitor. This is not mandatory, but it is always nice to know what profile is for what.<br />
<br />
# Click ''Profile identification'' button.<br />
# Fill in the data.<br />
# Click ''OK'' to finish.<br />
<br />
After you are all done, click on the '...' button next to ''Output Profile File'' box. Enter the name of your profile: ''somemonitor.icc''. Click ''Create Profile'' button, and you are done.<br />
<br />
=== ThinkPads ===<br />
<br />
See [http://www.thinkwiki.org/wiki/Colour_profile color profiles] for IBM/Lenovo [[Wikipedia:ThinkPad|ThinkPad]] notebook [http://www-307.ibm.com/pc/support/site.wss/migr-62923.html monitor profile] ([http://www-307.ibm.com/pc/support/site.wss/migr-44320.html generic]) support.<br />
<br />
== Loading ICC profiles ==<br />
<br />
ICC profiles are loaded either by the session daemon or by a dedicated ICC loader. Both Gnome and KDE have daemons capable of loading ICC profiles from {{pkg|colord}}. If you use colord in combination with either {{pkg|gnome-settings-daemon}} or {{Pkg|colord-kde}}, the profile will be loaded automatically. If you're not using either Gnome or KDE, you may install an independent daemon, [https://github.com/agalakhov/xiccd xiccd], which does the same but does not depend on your desktop environment. Do not start two ICC-capable daemons (e.g. gnome-settings-daemon and {{AUR|xiccd}}) at the same time.<br />
<br />
If you're not using any ICC-capable session daemon, make sure you use only one ICC loader - either xcalib, dispwin, dispcalGUI-apply-profiles or others. Otherwise, you can easily end up with an uncontrolled environment. (The most recently run loader sets the calibration, and the earlier loaded calibration is overwritten.)<br />
<br />
Before using a particular ICC loader, you should understand that some tools set only the calibration curves (e.g. xcalib), some tools set only the display profile to X.org _ICC_PROFILE atom (e.g. xicc), and other tools do both tasks at once (e.g. dispwin, dispcalGUI-apply-profiles).<br />
<br />
{{Note|Running nvidia-settings or using the -load-config-only argument will override the ICC file when using the .xinitrc examples.}}<br />
<br />
=== xiccd ===<br />
<br />
* {{AUR|xiccd}}is a simple bridge between colord and X. It allows non-Gnome and non-KDE desktop environment to load and apply icc profiles. <br />
<br />
<br />
<br />
Make sure {{Pkg|colord}} is installed, then install {{AUR|xiccd}}. <br />
<br />
<br />
Copy your icc profiles to the profile directory.<br />
<pre># cp icc_profile /usr/share/color/icc/colord/</pre><br />
<br />
<br />
Enable and start {{Pkg|colord}}:<br />
<pre># systemctl enable --now colord</pre><br />
If {{ic|colord}} was already running, you need to restart {{ic|colord.service}} via {{ic|systemctl restart colord}}, otherwise new profiles won't show up. <br />
<br />
<br />
Execute {{ic|xiccd}} in a terminal as a backend and ignore any verbose messages. Keep {{ic|xiccd}} running during the next steps.<br />
<pre>$ xiccd</pre><br />
This will enumerate displays and register them for colormgr(colord).<br />
<br />
<br />
Open another terminal and execute {{ic|colormgr}}. Note the {{ic|Device ID}} of your screen.<br />
<pre>$ colormgr get-devices</pre><br />
<br />
Note the {{ic|Profile ID}} which you added earlier and want to use.<br />
<pre>$ colormgr get-profiles</pre><br />
<br />
Add your profile to the display device.<br />
<pre># colormgr device-add-profile device_id profile_id</pre><br />
<br />
Make the profile as the default to the display device.<br />
<pre># colormgr device-make-profile-default device_id profile_id</pre><br />
<br />
<br />
Double-check that {{aur|xiccd}} installed {{ic|/etc/xdg/autostart/xiccd.desktop}} so that it [[Autostarting|autostarts]] at system startup.<br />
<pre># cat /etc/xdg/autostart/xiccd.desktop</pre><br />
<br />
<br />
Close all terminals, and reboot the system to check whether the icc profile is being applied.<br />
If {{ic|colord}} was already running, you need to restart colord.service via {{ic|systemctl restart colord}}.<br />
<br />
=== xcalib ===<br />
<br />
* [http://xcalib.sourceforge.net/ xcalib] is a lightweight monitor calibration loader which can load an ICC monitor profile to be shared across desktop applications. Installation: install the package {{Pkg|xcalib}}.<br />
<br />
==== Xinitrc example ====<br />
<br />
Load profile {{ic|P221W-sRGB.icc}} in {{Ic|/usr/share/color/icc}} on display host:0 when X server starts<br />
<pre>#!/bin/bash<br />
<br />
/usr/bin/xcalib -d :0 /usr/share/color/icc/P221W-sRGB.icc</pre><br />
<br />
==== JWM {{ic|<StartupCommand>}} example ====<br />
<br />
Load profile {{ic|P221W-Native.icc}} in {{Ic|/usr/local/share/color/icc}} on display host:0 when JWM starts<br />
{{ic|<StartupCommand>}}xcalib -d :0 /usr/local/share/color/icc/P221W-Native.icc{{ic|</StartupCommand>}}<br />
<br />
=== dispwin ===<br />
* [http://www.argyllcms.com/doc/dispwin.html dispwin] is a part of {{Pkg|argyllcms}}.<br />
<br />
==== Xinitrc example ====<br />
<br />
Load profile {{ic|906w-6500K.icc}} in {{Ic|/home/arch/.color/icc}} on display 0 when X server starts<br />
<pre>#!/bin/bash<br />
<br />
/usr/bin/dispwin -d0 /home/arch/.color/icc/906w-6500K.icc</pre><br />
<br />
==== JWM {{ic|<StartupCommand>}} example ====<br />
<br />
Load Argyll calibration file {{ic|906w-7000K.cal}} in {{Ic|/usr/local/share/color/icc}} on display 1 when JWM starts<br />
{{ic|<StartupCommand>}}dispwin -d1 /usr/local/share/color/icc/906w-7000K.cal{{ic|</StartupCommand>}}<br />
<br />
You can easily use one of these loaders to apply the color profile in early boot stage when starting a display manager, e.g. using [https://wiki.ubuntu.com/LightDM#Adding_System_Hooks LightDM startup script]. This allows to load a single icc profile file. This won't work with loading several profile files when using a multi monitopr setup.<br />
<br />
== Applications that support ICC profiles ==<br />
<br />
* [http://soppalco.ovunque-si.it/doc/linux/xsane/html/sane-xsane-color-management-doc.html Xsane] can use ICC profiles for color-corrected scanning.<br />
* [[CUPS]] can use ICC profiles for color-corrected printing using [https://www.freedesktop.org/software/colord/faq.html#cups Colord], but the actual implementation and usability is [https://lists.cups.org/pipermail/cups/2016-December/056399.html unclear].<br />
* [[GIMP]] can use ICC profiles for display of the image being edited. The use of the installed ICC profile has to be explicitly enabled in the settings dialog, though.<br />
* [[mpv]] can take an ICC profile into account when playing a video. The command line argument is: <code>--icc-profile=/path/to/profile.icc</code> or <code>--icc-profile-auto</code>. Only <code>--vo=opengl</code> does color management; other VO drivers will silently ignore the ICC profile options.<br />
* [[Firefox]], by default, uses the system-wide ICC profile only when displaying images that are already tagged with an ICC profile. To assume that untagged images use sRGB and apply color correction also to them, set the {{ic|gfx.color_management.mode}} preference to 1. Firefox can also use an ICC profile using the configuration option {{ic|gfx.color_management.display_profile}}.<br />
* Both Eye of Gnome ({{Pkg|eog}}) and Eye of MATE ({{Pkg|eom}}) automatically use the system-installed ICC profile.<br />
<br />
== See also ==<br />
<br />
* [[Using LPROF to profile monitors]] - Additional details on how to profile monitors<br />
* [[Wikipedia:Linux color management]]<br />
* [http://www.argyllcms.com/ Argyll Color Management System] - Official Site<br />
* [http://lprof.sourceforge.net/help/lprof-help.html LPROF Main Help Window] - Details on profiling printers and scanners<br />
* [http://displaycal.net/#concept DisplayCal: Basic concept of display calibration and profiling]<br />
* [https://encrypted.pcode.nl/blog/2013/11/24/display-color-profiling-on-linux/ Display color profiling on Linux (XFCE)]<br />
* [https://linuxtidbits.wordpress.com/2013/04/20/handling-display-calibration/ Monitor Hardware Calibration]</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_Yoga_260&diff=467511Lenovo ThinkPad Yoga 2602017-02-03T09:18:02Z<p>Thomas Do: /* Overview */ Changing info for kernel and accelerometer</p>
<hr />
<div>[[Category:Lenovo]]<br />
<br />
==Overview==<br />
<br />
Most functionality works out of the box, although a kernel of version 4.3 or higher is necessary for the video card and the wifi adapter and a kernel of version 4.9 or higher for the accelerometer to be recognized. Suspending the machine also works.<br />
<br />
{| class="wikitable" <br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Graphics || style="color:green" | '''Working''' || i915<br />
|-<br />
| Wireless || style="color:green" | '''Working''' || iwlwifi<br />
|-<br />
| Audio || style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Touchscreen || style="color:green" | '''Working''' || wacom<br />
|-<br />
| Stylus || style="color:green" | '''Working''' ¹ || wacom,usbhid<br />
|-<br />
| Accelerometer || style="color:green" | '''Working''' || hid_sensor_accel_3d<br />
|-<br />
| Touchpad || style="color:green" | '''Working''' || psmouse<br />
|-<br />
| Trackpoint || style="color:green" | '''Working''' || psmouse<br />
|-<br />
| Camera || style="color:green" | '''Working''' || uvcvideo<br />
|-<br />
| Card Reader || style="color:green" | '''Working''' || mmc_core<br />
|-<br />
| Bluetooth || style="color:green" | '''Working''' || btintel<br />
|-<br />
| Fingerprint Reader || style="color:red" | '''Not working''' ² ||<br />
|-<br />
| Smartcard reader || style="color:green" | '''Working''' ||<br />
|}<br />
<br />
¹Pen-buttons can be assigned with xsetwacom, see [[Wacom_Tablet#Remapping_Buttons]]. Device name is "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus".<br />
<br />
²https://bugs.freedesktop.org/show_bug.cgi?id=94536<br />
<br />
== Installation ==<br />
Newer kernels boot without problems and the wifi should be available. If you get a blank screen after booting, the power modes are not supported by your kernel; refer to Troubleshooting.<br />
<br />
=== Booting the install USB ===<br />
<br />
To access the boot menu and BIOS, use "F1". Disable secure boot from the BIOS. UEFI boot mode works fine.<br />
<br />
==Configuration==<br />
===TrackPad===<br />
TrackPad works fine with {{Pkg|xf86-input-synaptics}}.<br />
<br />
=== TrackPoint ===<br />
<br />
See [[TrackPoint]]. Sometimes the TrackPoint stops working and dmesg reports a stream of garbage when it is touched. Removing and probing the kernel module solves the problem:<br />
<br />
# rmmod psmouse<br />
# modprobe psmouse<br />
<br />
===TouchScreen and Stylus===<br />
Touchscreen works with the Wacom driver (package: {{pkg|xf86-input-wacom}}).<br />
Also using the Stylus, only one of the two buttons on the pen is usable.<br />
<br />
===Video===<br />
<br />
The kernel supports HD Graphics 520 from version 4.3. With default configuration, tearing is apparent when playing videos. DRI3 and glamor are supported. To solve tearing and use DRI3 and glamor, create the file {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:<br />
<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "glamor"<br />
Option "DRI" "3"<br />
Option "TearFree" "true"<br />
EndSection<br />
<br />
The miniDP port works, at least when used with a VGA adapter. The connected display shows up in ''xrandr'' correctly. The HDMI output works with Xorg and xf86-video-intel 1:2.99.917+730.<br />
<br />
===Card reader===<br />
The microSD-card reader works out of the box.<br />
<br />
===Bluetooth===<br />
The Bluetooth adapter works out of the box. It was tested with Android tethering and file transfer.<br />
<br />
<br />
== Hardware information ==<br />
<br />
The output of ''lspci'' is<br />
<br />
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 08)<br />
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07)<br />
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model<br />
00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)<br />
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)<br />
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)<br />
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)<br />
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)<br />
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)<br />
00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1)<br />
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)<br />
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)<br />
00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)<br />
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)<br />
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21)<br />
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 522a (rev 01)<br />
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)<br />
<br />
The output of ''lsusb'' is<br />
<br />
Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. <br />
Bus 001 Device 003: ID 13d3:5248 IMC Networks <br />
Bus 001 Device 002: ID 8087:0a2b Intel Corp. <br />
Bus 001 Device 005: ID 056a:5048 Wacom Co., Ltd <br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== High CPU usage in idle ===<br />
If the Thinkpad has unusually high CPU usage in idle then it might be an acpi firmware issue. On Windows this behaviour stops after a regular update. On Linux you can workaround by disabling whatever device is interrupting excessively.<br />
<br />
Find the interrupting source:<br />
<br />
grep . -r /sys/firmware/acpi/interrupts<br />
<br />
This might output something like this:<br />
<br />
...<br />
/sys/firmware/acpi/interrupts/gpe34: 30289 enabled <-- this causes many interrupts<br />
/sys/firmware/acpi/interrupts/gpe35: 3 enabled<br />
...<br />
<br />
Disable it (as root, not just sudo):<br />
<br />
echo "disable" > /sys/firmware/acpi/interrupts/gpe34<br />
<br />
Now the CPU should idle at 0-2% usage.<br />
<br />
<br />
Unfortunately you have to do that on every startup. A systemd service can do that automatically for you.<br />
<br />
Create {{ic|/etc/systemd/system/disable-interrupts.service}}:<br />
<br />
[Unit]<br />
Description=Disable acpi interrupts<br />
[Service]<br />
ExecStart=/usr/bin/bash -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe34'<br />
[Install]<br />
WantedBy=multi-user.target<br />
<br />
Then [[enable]] the {{ic|disable-interrupts.service}} systemd unit.<br />
<br />
=== Blank screen after loading kernel ===<br />
This happens with older kernels because the Intel P-State driver had problems. The workaround is to disable the buggy part of the driver. To achieve this, add {{ic|intel_pstate&#61;no_hwp}} as a kernel parameter. If you use GRUB, edit your {{ic|/etc/default/grub}} file and add the following:<br />
<br />
GRUB_CMDLINE_LINUX="intel_pstate=no_hwp"<br />
<br />
Don't forget to generate the config files with {{ic|grub-mkconfig}}.<br />
<br />
With a standard Arch-USB-ISO this can be done by pressing the Tabulator-Key on selecting the boot-menu-entry.<br />
<br />
=== Screen rotation not working ===<br />
Enabling the option {{ic|"TearFree"}} might break screen rotation: ''xrandr -o left'' will either result in a blank screen or in an error message ({{ic|xrandr: Configure crtc 0 failed}}). The X.org Intel driver above version 1:2.99.917+641+ge4ef6e9 no longer has this bug. Either upgrade the driver or disable the tear-free playback.</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Talk:Lenovo_ThinkPad_Yoga_260&diff=467394Talk:Lenovo ThinkPad Yoga 2602017-02-01T20:36:27Z<p>Thomas Do: </p>
<hr />
<div>'''Concerning Stylus'''. After updating to kernel 4.9 accelerometer is now working. When testing the stylus buttons these now work for me to (simulating left and right mouse click under Gnome). Not sure whether this is also due to the kernel update.<br />
Can anyone confirm the correct function of the buttons? In that case I would like to change the corresponding entry.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 14:26, 31 January 2017 (UTC)<br />
<br />
:I can confirm that the accelerometer is working. However, one of the stylus buttons still doesn't work for me; I'm running on: 4.9.0-rc8-ge5517c2<br />
:[[User:Myzt|Myzt]] ([[User talk:Myzt|talk]]) 14:52, 31 January 2017 (UTC)<br />
<br />
<br />
I am not sure what I did ;-). I first tried to change the buttons in gnome settings "Wacom tablets" upper and lower button, with no effect.<br />
<br />
Then I experimented with xsetwacom:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 'key a'<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 'key b'<br />
<br />
That worked and gave me an "a" when pressing the lower button and a "b" when pressing the upper button. After that changing the buttons to left and right click via the system settings seemed to work. But now, I can not reproduce that. What definitely works is using xsetwacom to assign the mouse click buttons:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 +1<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 +2<br />
<br />
Please, try to reproduce this.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 17:23, 31 January 2017 (UTC)<br />
<br />
:I played around a bit and figured out Button 1 triggers when you press the tip on the screen and Button 2 is the one farthest from the tip. The Button closer to the tip apparently now changes the stylus to 'eraser' mode which changes the behaviour of the tip (Button 1).<br />
:xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 'key a' #prints 'a' when pushing tip on screen.<br />
:xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 'key b' #prints 'b' when pressing button farthest from tip.<br />
:xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen eraser" Button 1 'key c' #prints 'c' when pressing both button closest to tip and pressing tip on screen.<br />
:I guess this is expected behaviour, so all my stylus buttons indeed seem to work in 4.9. Thanks for the update!<br />
:[[User:Myzt|Myzt]] ([[User talk:Myzt|talk]]) 14:14, 1 February 2017 (UTC)<br />
<br />
== How to use the stylus ==<br />
<br />
Hi, i try to get the Stylus working: the wacom and buttons are recongnised of xinput, but i did not know how to use the stylus now -> any help? - do i have to remove a plate for a battery in the stylus or so?<br />
<br />
The stylus should be loaded just by inserting into the side of the Yoga.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 20:36, 1 February 2017 (UTC)</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_Yoga_260&diff=467376Lenovo ThinkPad Yoga 2602017-02-01T16:05:45Z<p>Thomas Do: /* Overview */ Changing stylus working partial to working.</p>
<hr />
<div>[[Category:Lenovo]]<br />
<br />
==Overview==<br />
<br />
Most functionality works out of the box, although a kernel of version 4.3 or higher is necessary for the video card and the wifi adapter. Suspending the machine also works. The accelerometer does not show up.<br />
<br />
{| class="wikitable" <br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Graphics || style="color:green" | '''Working''' || i915<br />
|-<br />
| Wireless || style="color:green" | '''Working''' || iwlwifi<br />
|-<br />
| Audio || style="color:green" | '''Working''' || snd_hda_intel<br />
|-<br />
| Touchscreen || style="color:green" | '''Working''' || wacom<br />
|-<br />
| Stylus || style="color:green" | '''Working''' ¹ || wacom,usbhid<br />
|-<br />
| Accelerometer || style="color:green" | '''Working in Linux 4.9''' || hid_sensor_accel_3d<br />
|-<br />
| Touchpad || style="color:green" | '''Working''' || psmouse<br />
|-<br />
| Trackpoint || style="color:green" | '''Working''' || psmouse<br />
|-<br />
| Camera || style="color:green" | '''Working''' || uvcvideo<br />
|-<br />
| Card Reader || style="color:green" | '''Working''' || mmc_core<br />
|-<br />
| Bluetooth || style="color:green" | '''Working''' || btintel<br />
|-<br />
| Fingerprint Reader || style="color:red" | '''Not working''' ² ||<br />
|-<br />
| Smartcard reader || style="color:green" | '''Working''' ||<br />
|}<br />
<br />
¹Pen-buttons can be assigned with xsetwacom, see [[Wacom_Tablet#Remapping_Buttons]]. Device name is "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus".<br />
<br />
²https://bugs.freedesktop.org/show_bug.cgi?id=94536<br />
<br />
== Installation ==<br />
Newer kernels boot without problems and the wifi should be available. If you get a blank screen after booting, the power modes are not supported by your kernel; refer to Troubleshooting.<br />
<br />
=== Booting the install USB ===<br />
<br />
To access the boot menu and BIOS, use "F1". Disable secure boot from the BIOS. UEFI boot mode works fine.<br />
<br />
==Configuration==<br />
===TrackPad===<br />
TrackPad works fine with {{Pkg|xf86-input-synaptics}}.<br />
<br />
=== TrackPoint ===<br />
<br />
See [[TrackPoint]]. Sometimes the TrackPoint stops working and dmesg reports a stream of garbage when it is touched. Removing and probing the kernel module solves the problem:<br />
<br />
# rmmod psmouse<br />
# modprobe psmouse<br />
<br />
===TouchScreen and Stylus===<br />
Touchscreen works with the Wacom driver (package: {{pkg|xf86-input-wacom}}).<br />
Also using the Stylus, only one of the two buttons on the pen is usable.<br />
<br />
===Video===<br />
<br />
The kernel supports HD Graphics 520 from version 4.3. With default configuration, tearing is apparent when playing videos. DRI3 and glamor are supported. To solve tearing and use DRI3 and glamor, create the file {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} with the following content:<br />
<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "glamor"<br />
Option "DRI" "3"<br />
Option "TearFree" "true"<br />
EndSection<br />
<br />
The miniDP port works, at least when used with a VGA adapter. The connected display shows up in ''xrandr'' correctly. The HDMI output works with Xorg and xf86-video-intel 1:2.99.917+730.<br />
<br />
===Card reader===<br />
The microSD-card reader works out of the box.<br />
<br />
===Bluetooth===<br />
The Bluetooth adapter works out of the box. It was tested with Android tethering and file transfer.<br />
<br />
<br />
== Hardware information ==<br />
<br />
The output of ''lspci'' is<br />
<br />
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 08)<br />
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07)<br />
00:08.0 System peripheral: Intel Corporation Sky Lake Gaussian Mixture Model<br />
00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)<br />
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)<br />
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)<br />
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)<br />
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)<br />
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)<br />
00:1c.2 PCI bridge: Intel Corporation Device 9d12 (rev f1)<br />
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)<br />
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)<br />
00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)<br />
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)<br />
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21)<br />
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 522a (rev 01)<br />
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)<br />
<br />
The output of ''lsusb'' is<br />
<br />
Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. <br />
Bus 001 Device 003: ID 13d3:5248 IMC Networks <br />
Bus 001 Device 002: ID 8087:0a2b Intel Corp. <br />
Bus 001 Device 005: ID 056a:5048 Wacom Co., Ltd <br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== High CPU usage in idle ===<br />
If the Thinkpad has unusually high CPU usage in idle then it might be an acpi firmware issue. On Windows this behaviour stops after a regular update. On Linux you can workaround by disabling whatever device is interrupting excessively.<br />
<br />
Find the interrupting source:<br />
<br />
grep . -r /sys/firmware/acpi/interrupts<br />
<br />
This might output something like this:<br />
<br />
...<br />
/sys/firmware/acpi/interrupts/gpe34: 30289 enabled <-- this causes many interrupts<br />
/sys/firmware/acpi/interrupts/gpe35: 3 enabled<br />
...<br />
<br />
Disable it (as root, not just sudo):<br />
<br />
echo "disable" > /sys/firmware/acpi/interrupts/gpe34<br />
<br />
Now the CPU should idle at 0-2% usage.<br />
<br />
<br />
Unfortunately you have to do that on every startup. A systemd service can do that automatically for you.<br />
<br />
Create {{ic|/etc/systemd/system/disable-interrupts.service}}:<br />
<br />
[Unit]<br />
Description=Disable acpi interrupts<br />
[Service]<br />
ExecStart=/usr/bin/bash -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpe34'<br />
[Install]<br />
WantedBy=multi-user.target<br />
<br />
Then [[enable]] the {{ic|disable-interrupts.service}} systemd unit.<br />
<br />
=== Blank screen after loading kernel ===<br />
This happens with older kernels because the Intel P-State driver had problems. The workaround is to disable the buggy part of the driver. To achieve this, add {{ic|intel_pstate&#61;no_hwp}} as a kernel parameter. If you use GRUB, edit your {{ic|/etc/default/grub}} file and add the following:<br />
<br />
GRUB_CMDLINE_LINUX="intel_pstate=no_hwp"<br />
<br />
Don't forget to generate the config files with {{ic|grub-mkconfig}}.<br />
<br />
With a standard Arch-USB-ISO this can be done by pressing the Tabulator-Key on selecting the boot-menu-entry.<br />
<br />
=== Screen rotation not working ===<br />
Enabling the option {{ic|"TearFree"}} might break screen rotation: ''xrandr -o left'' will either result in a blank screen or in an error message ({{ic|xrandr: Configure crtc 0 failed}}). The X.org Intel driver above version 1:2.99.917+641+ge4ef6e9 no longer has this bug. Either upgrade the driver or disable the tear-free playback.</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Talk:Lenovo_ThinkPad_Yoga_260&diff=467306Talk:Lenovo ThinkPad Yoga 2602017-01-31T17:25:23Z<p>Thomas Do: formating</p>
<hr />
<div>'''Concerning Stylus'''. After updating to kernel 4.9 accelerometer is now working. When testing the stylus buttons these now work for me to (simulating left and right mouse click under Gnome). Not sure whether this is also due to the kernel update.<br />
Can anyone confirm the correct function of the buttons? In that case I would like to change the corresponding entry.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 14:26, 31 January 2017 (UTC)<br />
<br />
:I can confirm that the accelerometer is working. However, one of the stylus buttons still doesn't work for me; I'm running on: 4.9.0-rc8-ge5517c2<br />
:[[User:Myzt|Myzt]] ([[User talk:Myzt|talk]]) 14:52, 31 January 2017 (UTC)<br />
<br />
<br />
I am not sure what I did ;-). I first tried to change the buttons in gnome settings "Wacom tablets" upper and lower button, with no effect.<br />
<br />
Then I experimented with xsetwacom:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 'key a'<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 'key b'<br />
<br />
That worked and gave me an "a" when pressing the lower button and a "b" when pressing the upper button. After that changing the buttons to left and right click via the system settings seemed to work. But now, I can not reproduce that. What definitely works is using xsetwacom to assign the mouse click buttons:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 +1<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 +2<br />
<br />
Please, try to reproduce this.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 17:23, 31 January 2017 (UTC)</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Talk:Lenovo_ThinkPad_Yoga_260&diff=467305Talk:Lenovo ThinkPad Yoga 2602017-01-31T17:24:14Z<p>Thomas Do: </p>
<hr />
<div>'''Concerning Stylus'''. After updating to kernel 4.9 accelerometer is now working. When testing the stylus buttons these now work for me to (simulating left and right mouse click under Gnome). Not sure whether this is also due to the kernel update.<br />
Can anyone confirm the correct function of the buttons? In that case I would like to change the corresponding entry.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 14:26, 31 January 2017 (UTC)<br />
<br />
:I can confirm that the accelerometer is working. However, one of the stylus buttons still doesn't work for me; I'm running on: 4.9.0-rc8-ge5517c2<br />
:[[User:Myzt|Myzt]] ([[User talk:Myzt|talk]]) 14:52, 31 January 2017 (UTC)<br />
<br />
<br />
I am not sure what I did ;-). I first tried to change the buttons in gnome settings "Wacom tablets" upper and lower button, with no effect.<br />
<br />
Then I experimented with xsetwacom:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 'key a'<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 'key b'<br />
<br />
That worked and gave me an "a" when pressing the lower button and a "b" when pressing the upper button. After that changing the buttons to left and right click via the system settings seemed to work. But now, I can not reproduce that. What definitely works is using xsetwacom to assign the mouse click buttons:<br />
<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 1 +1<br />
xsetwacom set "Wacom Co.,Ltd. Pen and multitouch sensor Pen stylus" Button 2 +2<br />
<br />
Please, try to reproduce this.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 17:23, 31 January 2017 (UTC)</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Talk:Lenovo_ThinkPad_Yoga_260&diff=467291Talk:Lenovo ThinkPad Yoga 2602017-01-31T14:26:13Z<p>Thomas Do: Stylus button work now?</p>
<hr />
<div>'''Concerning Stylus'''. After updating to kernel 4.9 accelerometer is now working. When testing the stylus buttons these now work for me to (simulating left and right mouse click under Gnome). Not sure whether this is also due to the kernel update.<br />
Can anyone confirm the correct function of the buttons? In that case I would like to change the corresponding entry.<br />
<br />
[[User:Thomas Do|Thomas Do]] ([[User talk:Thomas Do|talk]]) 14:26, 31 January 2017 (UTC)</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=Firefox&diff=220092Firefox2012-08-28T08:10:53Z<p>Thomas Do: /* "I'm Feeling Lucky" Mode */</p>
<hr />
<div>[[cs:Firefox]]<br />
[[es:Firefox]]<br />
[[fr:Firefox]]<br />
[[it:Firefox]]<br />
[[ko:Firefox]]<br />
[[ru:Firefox]]<br />
[[tr:Firefox]]<br />
[[zh-CN:Firefox]]<br />
[[Category:Web Browser]]<br />
<br />
<br />
{{Article summary start}}<br />
{{Article summary text|Installing and troubleshooting the Firefox browser and plugins}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Browser Plugins}}: Acquiring and installing plugins such as [[Flash]]<br />
{{Article summary wiki|Firefox Tweaks}}: Configuration and modifications<br />
{{Article summary end}}<br />
<br />
[http://www.firefox.com Firefox] is a popular open-source graphical web browser from [http://www.mozilla.com Mozilla].<br />
<br />
== Installing ==<br />
The {{Pkg|firefox}} package can be found in the [[Official Repositories|official repositories]] and can be installed with [[pacman]].<br />
<br />
There are a number of language packs available if English is not your preferred language. To see a list of available language packs, try:<br />
{{bc|$ pacman -Ss firefox-i18n}}<br />
<br />
If Firefox does not anti-alias and/or hint your fonts, try to install {{AUR|ttf-win7-fonts}} (preferred) or {{AUR|ttf-ms-fonts}} and take a look at [[Font Configuration]].<br />
<br />
== Add-ons ==<br />
Firefox is well known for its large library of add-ons which can be used to add new features or modify the behavior of existing features of Firefox. You can find new add-ons or manage installed add-ons with Firefox's "Add-ons Manager."<br />
<br />
For a list of popular add-ons, see: [https://addons.mozilla.org/en-US/firefox/extensions/?sort=popular Mozilla's add-on list sorted by popularity].<br />
<br />
== Plugins ==<br />
''See: [[Browser Plugins]]''<br />
<br />
To find out what plugins are installed/enabled, enter:<br />
about:plugins<br />
in the Firefox address bar. Or go to ''Addons'' from the main bar drop downs <!-- I use vimperator so I do not know what's the name --> and select the ''Plugins'' tab.<br />
<br />
=== GNOME integration ===<br />
Install {{AUR|firefox-extension-gnome-keyring-git}} from the [[Arch User Repository|AUR]] to integrate Firefox 3.6.x with Gnome-keyring.<br />
<br />
You can also install {{AUR|firefox-extension-firefoxnotify-git}} to get libnotify/notifyOSD integration.<br />
<br />
=== Dictionaries for spell checking ===<br />
Right click in any text entry field and add the dictionary for the solicited language. Restart Firefox, and click in a text entry field again to enable spell checking.<br />
<br />
Or get it from pacman:<br />
pacman -Ss hunspell<br />
<br />
=== Adding Firefox search engines ===<br />
<br />
Visit https://addons.mozilla.org/en-US/firefox/browse/type:4/ and install.<br />
<br />
If you want to custom one, take a look at: {{ic|~/.mozilla/firefox/xxx.default/searchplugins/}} where xxx is your profile ID).<br />
<br />
Yet another repository of premade searchbar engines: [http://mycroft.mozdev.org/ http://mycroft.mozdev.org/]<br />
<br />
Also, you can use [https://firefox.maltekraus.de/extensions/add-to-search-bar add-to-searchbar] extension to add a search to your search bar from any web site, like Opera browser.<br />
<br />
====arch-firefox-search====<br />
Adds Arch-specific searches (AUR, wiki, forum, etc, as specified by user) to the Firefox search toolbar.<br />
# pacman -S arch-firefox-search<br />
<br />
== Projects related to Firefox ==<br />
=== Firefox derivatives ===<br />
Two different forks of Mozilla Firefox:<br />
<br />
*Debian’s Iceweasel ([[Wikipedia:Iceweasel]]; http://wiki.debian.org/Iceweasel). It is being developed by Debian and is based on 2.0.<br />
*GNU/IceCat ([[Wikipedia:GNU IceCat]]; AUR: {{AUR|icecat}}) - formerly known as GNU IceWeasel, is a web browser distributed by the GNU Project. IceCat is made entirely of free software. It is compatible with the GNU/Linux operating system and almost all of Firefox's addons. GNU/IceCat really can fully replace Firefox.<br />
<br />
=== Firefox with better KDE integration ===<br />
*{{AUR|firefox-kde-opensuse}}<br />
:with OpenSUSE patch, integrates better with KDE. OpenSUSE's patch and integration of Firefox with KDE is considered the best by many users.<br />
<br />
*{{Pkg|kpartsplugin}}<br />
:This plugin uses KDE's KParts to embed file viewers into non-KDE browsers<br />
<br />
*[http://kde-look.org/content/show.php/?content=117962 Oxygen KDE]<br />
:This addon provides further integration with KDE's Oxygen theme, color scheme detection, Faenza icons and various customizations.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Firefox 4 New Menu Bar/Firefox Button ===<br />
By default, Arch Linux shows the classic layout of the menu bar. To activate the new Firefox 4 layout with the "Firefox" button replacing the menu bar, uncheck View -> Toolbars -> Menubar.<br />
<br />
In GNU/Linux, you will just get a plain grey button instead of the new orange one from Windows. However you can change this to either a Firefox icon or the icon followed by the "Firefox" text.<br />
<br />
Adding the following to your {{ic|~/.mozilla/firefox/userprofile/chrome/userChrome.css}} file will place the icon before the text:<br />
{{bc|#appmenu-toolbar-button {<br />
list-style-image: url("chrome://branding/content/icon16.png");<br />
}<br />
}}<br />
Adding the following to the same file will ''remove'' the "Firefox" text:<br />
{{bc|#appmenu-toolbar-button > .toolbarbutton-text,<br />
#appmenu-toolbar-button > .toolbarbutton-menu-dropmarker {<br />
display: none !important;<br />
}<br />
}}<br />
<br />
{{Note|You need to create both the {{ic|chrome}} directory and {{ic|userChrome.css}}, if they do not already exist.}}<br />
<br />
=== Open containing folder problems (KDE) ===<br />
If Firefox launches something other than your preferred file manager when using the "Open Containing Folder" option in the Downloads manager, make sure you select your file manager of choice (e.g. Dolphin) in KDE's System Settings:<br />
:'''System Settings -> Default Applications -> File Manager'''<br />
<br />
If you have already selected your file manager of choice and Cervisia (or a file manager other than your favorite) is opening modify your user's {{ic|~/.local/share/applications/defaults.list}} to include these two lines:<br />
x-directory/normal=kde4-dolphin.desktop;kde4-kfmclient_dir.desktop;<br />
inode/directory=kde4-dolphin.desktop;kde4-kfmclient_dir.desktop;kde4-gwenview.desktop;kde4-filelight.desktop;kde4-cervisia.desktop;<br />
<br />
=== Firefox keeps creating ~/Desktop even when this is not desired ===<br />
Firefox uses {{ic|~/Desktop}} as the default place for download and upload files. To set it to another folder, create {{ic|~/.config/user-dirs.dirs}} and add:<br />
XDG_DESKTOP_DIR="/home/<user>/"<br />
XDG_DOWNLOAD_DIR="/home/<user>/<dir>"<br />
XDG_TEMPLATES_DIR="/home/<user>/<dir>"<br />
XDG_PUBLICSHARE_DIR="/home/<user>/<dir>"<br />
XDG_DOCUMENTS_DIR="/home/<user>/<dir>"<br />
XDG_MUSIC_DIR="/home/<user>/<dir>"<br />
XDG_PICTURES_DIR="/home/<user>/<dir>"<br />
XDG_VIDEOS_DIR="/home/<user>/<dir>"<br />
Change {{ic|<user>}} and {{ic|<dir>}} to the actual directory.<br />
<br />
=== How to prevent plugins from allowing popups? ===<br />
Ever wondered why pop-ups appear even though you have blocked them? It seems that the Flash plugin can bypass default settings and annoy us with those pesky pop-ups. Fear not, for we can prevent it from doing that.<br />
<br />
To get around it:<br />
# Type about:config into the Firefox location bar.<br />
# Right-click on the page and select New and then Integer.<br />
# Name it privacy.popups.disable_from_plugins<br />
# Set the value to 2.<br />
<br />
The possible values are:<br />
* 0: Allow all popups from plugins.<br />
* 1: Allow popups, but limit them to dom.popup_maximum.<br />
* 2: Block popups from plugins.<br />
* 3: Block popups from plugins, even on whitelisted sites.<br />
<br />
=== Middle-click errors ===<br />
! The URL is not valid and cannot be loaded.<br />
Another symptom is that middle-clicking results in unexpected behavior, like accessing a random web page.<br />
<br />
The reason stems from the use of the middle mouse buttons in UNIX-like operating systems. The middle mouse button is used to paste whatever text has been highlighted/added to the clipboard. Then there is the possibly conflicting feature in Firefox, which defaults to loading the URL of the corresponding text when the button is depressed. This can be disabled like so:<br />
<br />
Open the browser, and type the following into the address bar:<br />
about:config<br />
Search for '''middlemouse.contentLoadURL''' and set it to false.<br />
<br />
Alternatively, having the traditional scroll cursor on middle-click (default behaviour on Windows browsers) can be achieved by searching for '''general.autoScroll''' and setting it to true.<br />
<br />
=== Backspace does not work as the 'Back' button ===<br />
As per [http://ubuntu.wordpress.com/2006/12/21/fix-firefox-backspace-to-take-you-to-the-previous-page/ this article], the feature has been removed in order to fix a bug. Follow the next steps to retain the original behaviour.<br />
<br />
Open the browser and type the following address:<br />
about:config<br />
Search for '''browser.backspace_action''' and set it to 0 (zero).<br />
<br />
=== Firefox does not remember login information ===<br />
It may be due to a corrupted {{ic|cookies.sqlite}} file in [http://support.mozilla.com/en-US/kb/Profiles#How_to_find_your_profile Firefox's profile] folder. In order to fix this, just rename or remove the cookie.sqlite while Firefox is not running.<br />
<br />
Open a terminal of choice and type the following:<br />
$ cd ~/.mozilla/firefox/xxxxxxxx.default/<br />
$ rm -f cookies.sqlite<br />
{{Note|xxxxxxxx represents a random string of 8 characters.}}<br />
<br />
Restart Firefox and see if it solved the problem.<br />
<br />
=== Broken websites / input fields with dark Gtk Themes ===<br />
When using a dark [[GTK]] theme, one might encounter Internet pages with unreadable input and text fields (p.e. Amazon - white text on white background). This can happen because the site only sets either background or text color, and Firefox takes the other one from the theme.<br />
<br />
A work around is to explicitly setting standard colours for all web pages in {{ic|~/.mozilla/firefox/.../chrome/userContent.css}}.<br />
<br />
The following sets input fields to standard black text / white background; both can be overridden by the displayed site, so that colors are seen as intended:<br />
{{bc|<br />
input {<br />
-moz-appearance: none !important;<br />
background-color: white;<br />
color: black;<br />
}<br />
<br />
textarea {<br />
-moz-appearance: none !important;<br />
background-color: white;<br />
color: black;<br />
}<br />
}}<br />
This will force the colours ("Allow pages to choose their own colors [..]" setting, in the '''Preferences > Content > Color''' dialog):<br />
{{bc|<br />
input {<br />
-moz-appearance: none !important;<br />
background-color: pink !important;<br />
color: green !important;<br />
}<br />
<br />
textarea {<br />
-moz-appearance: none !important;<br />
background-color: pink !important;<br />
color: green !important;<br />
}<br />
}}<br />
Change color values to suit, or use an add-on like [https://addons.mozilla.org/en-US/firefox/addon/2108 Stylish].<br />
<br />
=== File association problems ===<br />
For non-[[GNOME]] users, Firefox may not associate file types (in the "Open With" part of the download dialog). Installing {{Pkg|libgnome}} amends the problem:<br />
pacman -S libgnome<br />
If you are using KDE you can also do the following:<br />
ln -s ~/.local/share/applications/mimeapps.list ~/.local/share/applications/mimeinfo.cache<br />
From now on Firefox should use the applications which are explicitly set in KDE.<br />
<br />
=== "I'm Feeling Lucky" Mode ===<br />
Some search engines have a feeling lucky feature. For example Google has "I'm Feeling Lucky" and DuckDuckGo has "I'm Feeling Ducky".<br />
<br />
To activate them:<br />
# Type "'''about:config'''" in the address bar.<br />
# Search for the string '''keyword.url'''<br />
# Modify its value (if any) to the URL of the search engine. <br />
<br />
:: For google, set it to:<br />
:: {{bc|<nowiki>http://www.google.com/search?btnI=I%27m+Feeling+Lucky&q=</nowiki>}}<br />
:: For DuckDuckGo, set it to:<br />
:: {{bc|<nowiki>https://duckduckgo.com/?q=\</nowiki>}}<br />
<br />
=== "Do you want Firefox to save your tabs for the next time it starts?" dialog does not appear ===<br />
From the [http://support.mozilla.com/en-US/questions/767751 Mozilla Support] site:<br />
<br />
# Type "'''about:config'''" in the address bar.<br />
# Set '''browser.warnOnQuit''' to '''true'''.<br />
# Set '''browser.showQuitWarning''' to '''true'''.<br />
<br />
=== Firefox has high CPU usage and feels slow on scrolling with nVidia GPUs ===<br />
<br />
In some cases, forcing the proprietary nVidia driver to store pixmaps in video memory instead of system memory can yield massive improvements in the perceived performance of pixmap-intensive applications like Firefox. Run<br />
<br />
$ nvidia-settings -a InitialPixmapPlacement=2<br />
<br />
from the terminal; if desired results are achieved add this line to a script and use your desktop environment's autorun facilities to execute it on every startup. Alternatively, add the parameter to your {{ic|~/.nvidia-settings-rc}} and run<br />
<br />
$ nvidia-settings --load-config-only<br />
<br />
on startup. This setting is documented in [http://cgit.freedesktop.org/~aplattner/nvidia-settings/tree/src/libXNVCtrl/NVCtrl.h?id=b27db3d10d58b821e87fbe3f46166e02dc589855#n2797 nvidia-settings source code]. Make sure you have added other perfomance-improving settings, see [[NVIDIA]].<br />
<br />
=== Firefox uses ugly fonts on certain webpages ===<br />
<br />
When Firefox uses bitmap fonts, it can happen that on certain webpages the fonts are very ugly (compared to Google Chrome for example):<br />
<br />
http://i.imgur.com/SMVdi.png vs http://i.imgur.com/jNmxU.png<br />
<br />
To fix that, just disable bitmap fonts for X:<br />
$ sudo ln -s /etc/fonts/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d/<br />
<br />
=== The menu can't pop up after updating to Firefox 13 ===<br />
<br />
This problem may happen to some Chinese user who use {{pkg|fcitx}} as an input method. The problem may be caused by false environment variables of fcitx, please check it.<br />
Or you may solve it by installing {{pkg|fcitx-gtk2}}, {{pkg|fcitx-gtk3}}, and {{pkg|fcitx-qt}}.<br />
<br />
==See also==<br />
* [http://web.glandium.org/blog/?p=97 Facts about Debian and Mozilla® Firefox]<br />
:An account of the trademark issues from the Firefox package maintainer for Debian.<br />
* [http://www.gnu.org/software/gnuzilla/ Gnuzilla and IceWeasel]<br />
:Official website for the GNU Mozilla forks.</div>Thomas Dohttps://wiki.archlinux.org/index.php?title=VMware&diff=169632VMware2011-11-11T14:04:10Z<p>Thomas Do: /* 3.1 kernels */</p>
<hr />
<div>[[Category:Virtualization]]<br />
{{i18n|VMware}}<br />
<br />
{{Article summary start}}<br />
{{Article summary text|This article will explain how to install and configure VMware Workstation/Player in Arch.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Installing Arch Linux in VMware}}<br />
{{Article summary wiki|Virtualbox}}<br />
{{Article summary end}}<br />
<br />
This article is about installing VMware in Arch, you may also be interested in [[Installing Arch Linux in VMware]].<br />
<br />
==Installation==<br />
<br />
===VMware Server===<br />
<br />
{{Note|VMware ended support for VMware Server on June 30, 2011.}}<br />
<br />
'''1.''' Install [http://aur.archlinux.org/packages.php?ID=6182 vmware-server] from the [[AUR]].<br />
<br />
'''2.''' Install [http://aur.archlinux.org/packages.php?ID=9604 vmware-server-console] or the [http://aur.archlinux.org/packages.php?ID=31169 bin32 version], if on a 64-bit Arch.<br />
<br />
'''3.''' Download the image from the [http://www.vmware.com/products/server/overview.html VMware website].<br />
<br />
'''4.''' Copy the image to the build directory.<br />
<br />
'''5.''' Finish building.<br />
<br />
===VMware Workstation/Player===<br />
<br />
{{Note| VMware Workstation/Player will '''not''' be manageable with pacman as the files are not installed with it.}}<br />
<br />
To install Workstation or Player on a Linux host using a bundle:<br />
<br />
'''1.''' Download [http://downloads.vmware.com/d/info/desktop_downloads/vmware_workstation/8_0 VMware Workstation] (you may also try the [http://communities.vmware.com/community/beta/ws testing (Beta/RC) versions]).<br />
<br />
'''2.''' Start the installation ({{Codeline|--console}} uses terminal instead of the GUI):<br />
# chmod +x VMware-<edition>-<version>.<release>.<architecture>.bundle<br />
# ./VMware-<edition>-<version>.<release>.<architecture>.bundle --console<br />
<br />
'''3.''' Read & accept the EULA to continue.<br />
<br />
'''4.''' Set {{Codeline|System service scripts}} to:<br />
/etc/rc.d<br />
<br />
'''5.''' (Optional) Enter the directory path to the Integrated Virtual Debugger for Eclipse, if it is installed.<br />
<br />
'''6.''' You will now get an error about the "rc*.d style init script" not being set. This can, however, be safely ignored.<br />
<br />
'''7.''' Create links for the daemons:<br />
# ln -s /etc/init.d/vmware /etc/rc.d/vmware<br />
# ln -s /etc/init.d/vmware-workstation-server /etc/rc.d/vmware-workstation-server<br />
<br />
==Configuration==<br />
<br />
===VMware patches===<br />
{{Note|VMware Workstation 8 and VMware Player 4 only require patching for 3.1 kernels.}}<br />
{{Tip|There is also a package called {{Package AUR|vmware-patch}} in the [[AUR]] with the intention of trying to automate the patching process.}}<br />
<br />
====3.1 kernels====<br />
With VMware Workstation 8 or VMware Player 4 you can use [http://weltall.heliohost.org/wordpress/2011/09/29/vmware-workstationplayer-fix-for-linux-3-1/ this] script:<br />
$ cd /tmp<br />
$ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/09/vmware8linux31fix.tar.gz<br />
$ tar -xvzf vmware8linux31fix.tar.gz<br />
# ./patch-modules_3.1.0.sh<br />
<br />
With older VMware versions you need to use [http://weltall.heliohost.org/wordpress/2011/08/10/vmware-workstation-7-1-4-fix-for-linux-3-1/ this] one instead:<br />
$ cd /tmp<br />
$ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/08/fullvmwarelinux310patch.tar.gz<br />
$ tar -xvzf fullvmwarelinux310patch.tar.gz<br />
# ./patch-modules_2.6.39.sh<br />
<br />
====3.0 kernels====<br />
The patch for 3.0 is available [http://weltall.heliohost.org/wordpress/2011/05/14/running-vmware-workstation-player-on-linux-2-6-39-updated/ here]:<br />
$ cd /tmp<br />
$ wget http://weltall.heliohost.org/wordpress/wp-content/uploads/2011/05/vmware2.6.39patchv3.tar.bz2<br />
$ tar -xvjf vmware2.6.39patchv3.tar.bz2<br />
# ./patch-modules_2.6.39.sh<br />
<br />
In addition, VMware module builder does not handle the new two-part version string (3.x instead of 2.6.x) of the kernel correctly. See [https://bbs.archlinux.org/viewtopic.php?id=123695 this] thread.<br />
<br />
The easy solution is to patch two binaries:<br />
# sed 's/\x83\xe8\x03\x83\xf8\x01\x0f\x96\xc0/\x83\xe8\x02\x83\xf8\x01\x0f\x96\xc0/' -i /usr/lib/vmware/lib/libvmware-modconfig-console.so/libvmware-modconfig-console.so<br />
# sed 's/\x83\xe8\x03\x83\xf8\x01\x0f\x96\xc0/\x83\xe8\x02\x83\xf8\x01\x0f\x96\xc0/' -i /usr/lib/vmware/lib/libvmware-modconfig.so/libvmware-modconfig.so<br />
<br />
====2.6.39 kernels====<br />
$ mkdir /tmp/vmware && cd /tmp/vmware<br />
# for t in /usr/lib/vmware/modules/source/*.tar; do tar xf $t; mv $t{,.original}; done<br />
# wget -qO- http://kaslit.com/downloads/vmware2.6.39fixed.patch | patch -Np1<br />
# for d in *-only; do tar cf /usr/lib/vmware/modules/source/${d/%-only/}.tar $d; done<br />
A Fedora community member has also uploaded the {{Filename|sources/}} folder in a compressed tarball [http://www.fedoraforum.org/leigh123linux/vm/source.tar.lzma here].<br />
<br />
====2.6.37 and .38 kernels====<br />
$ cd /tmp<br />
$ wget http://www.russo79.com/vmware7.1.3-patch-kernel-2.6.37.sh<br />
$ chmod +x vmware7.1.3-patch-kernel-2.6.37.sh<br />
# ./vmware7.1.3-patch-kernel-2.6.37.sh<br />
<br />
====2.6.36 kernels====<br />
$ cd /tmp<br />
$ wget http://files.archlinux.org.il/vmmon_fix_2.6.36.sh<br />
$ chmod +x vmmon_fix_2.6.36.sh<br />
# ./vmmon_fix_2.6.36.sh<br />
<br />
====2.6.35 kernels====<br />
$ cd /tmp<br />
$ wget http://www.sputnick-area.net/scripts/vmware7.1.1-patch-kernel-2.6.35.bash<br />
$ chmod +x vmware7.1.1-patch-kernel-2.6.35.bash<br />
# ./vmware7.1.1-patch-kernel-2.6.35.bash<br />
<br />
===VMware modules===<br />
<br />
'''8.''' At this point you would want to install the modules. First you need to either change the {{Codeline|lsmod binary path}} in {{Filename|/etc/rc.d/vmware}} from {{Filename|/sbin/lsmod}} to {{Filename|/bin/lsmod}}:<br />
<br />
# sed -i "s|/sbin/lsmod|/bin/lsmod|g" /etc/rc.d/vmware<br />
<br />
or create a symlink with:<br />
# ln -s /bin/lsmod /sbin/lsmod<br />
<br />
'''9.''' Now you can install the modules. You can do this by either launching VMware and letting it install the modules with the GUI or executing:<br />
# vmware-modconfig --console --install-all<br />
<br />
'''10.''' (Optional) Add '''vmware''' to the DAEMONS array in {{Filename|/etc/[[rc.conf]]}} so that the service is started automatically on boot.<br />
<br />
'''11.''' Now, open your VMware Workstation ({{Codeline|vmware}} in the console) or VMware Player ({{Codeline|vmplayer}} in the console) to configure & use!<br />
<br />
{{Warning|When upgrading the kernel you <u>will</u> have to rebuild the vmware modules with:<br />
# vmware-modconfig --console --install-all<br />
Failure to do so may result in a system crash upon powering up virtual machines.}}<br />
<br />
==Tips & Tricks==<br />
<br />
===Extracting the VMware BIOS===<br />
To extract the VMware BIOS, which can be manipulated and later used with your virtual machines:<br />
objcopy /usr/lib/vmware/bin/vmware-vmx -O binary -j bios440 --set-section-flags bios440=a bios440.rom.Z<br />
perl -e 'use Compress::Zlib; my $v; read STDIN, $v, '$(stat -c%s "./bios440.rom.Z")'; $v = uncompress($v); print $v;' < bios440.rom.Z > bios440.rom<br />
<br />
====Using the modified BIOS====<br />
If and when you decide to modify the extractd BIOS you can make your virtual machine use it by moving it to {{Filename|~/vmware/<Virtual machine name>}}:<br />
mv bios440.rom ~/vmware/<Virtual machine name>/<br />
then adding the name to the {{Codeline|<Virtual machine name>.vmx}} file:<br />
{{File|name=~/vmware/<Virtual machine name>/<Virtual machine name>.vmx|content=bios440.filename = "bios440.rom"}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Could not open /dev/vmmon: No such file or directory. ===<br />
The full error is:<br />
Could not open /dev/vmmon: No such file or directory.<br />
Please make sure that the kernel module `vmmon' is loaded.<br />
This means that at least the {{Codeline|vmmon}} VMware service is not running. All VMware services can be started with:<br />
# rc.d start vmware<br />
<br />
=== Kernel headers for version 3.x-xxxx were not found. If you installed them[...] ===<br />
Install them with:<br />
# pacman -S linux-headers<br />
<br />
=== Printing does not work ===<br />
If printing from the guest OS is not working there may be a permission problem with the ThinPrint CUPS filter ('''thnucups'''), which is used by VMware. First make sure your {{Filename|/var/log/cups/error_log}} says something like:<br />
E [22/Nov/2010:14:10:11 -0800] Unable to execute /usr/lib/cups/filter/thnucups: insecure file permissions (0104755)<br />
<br />
In which case you may try:<br />
# chmod u-sw /usr/lib/cups/filter/thnucups<br />
# rc.d restart cupsd<br />
<br />
=== The installer fails to start ===<br />
If you just get back to the prompt when opening the {{Filename|.bundle}}, then you probably have an old version of the {{Codeline|vmware installer}} and you should remove it (you may also refer to the [https://wiki.archlinux.org/index.php/VMware#Uninstallation Uninstallation] section of this article):<br />
# rm -r /etc/vmware-installer<br />
<br />
==Uninstallation==<br />
<br />
Check the product name:<br />
<br />
# vmware-installer -l<br />
<br />
and uninstall with:<br />
<br />
# vmware-installer -u <vmware-product><br />
<br />
Manually included symlinks in {{Filename|/etc/rc.d}} have to be removed manually:<br />
<br />
# unlink /etc/rc.d/vmware<br />
# unlink /etc/rc.d/vmware-workstation-server<br />
<br />
Remember to also remove {{Codeline|vmware}} from the {{Filename|/etc/rc.conf}} {{Codeline|DAEMONS}} array.</div>Thomas Do