https://wiki.archlinux.org/api.php?action=feedcontributions&user=1cawk&feedformat=atomArchWiki - User contributions [en]2024-03-29T06:08:04ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Xiaomi_Mi_Notebook_Air_13.3&diff=493956Talk:Xiaomi Mi Notebook Air 13.32017-10-24T02:43:30Z<p>1cawk: /* Graphics Card Configuration intel only */ new section</p>
<hr />
<div>== fn keys ==<br />
Has anyone gotten the 2 fn keys which do not output any keycodes to work? (F7 and F9)<br />
F9 at least shows up in dmesg <code><br />
[ 253.732780] atkbd serio0: Unknown key released (translated set 2, code 0x86 on isa0060/serio0).<br />
[ 253.732785] atkbd serio0: Use 'setkeycodes e006 <keycode>' to make it known.<br />
</code><br />
<br />
However using setkeycodes does not work for me, there is still no recognized input.<br />
- [[User:Blubbblubb|Blubbblubb]] ([[User talk:Blubbblubb|talk]]) 14:20, 12 April 2017 (UTC)<br />
<br />
== <s>linux-nvme</s> ==<br />
<br />
Has anyone tried [https://github.com/damige/linux-nvme linux-nvme] (kernel power saving patches)? There are [https://github.com/damige/linux-nvme/issues/2 known] [https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?h=20160512-nvme-test&id=452aefdcb67a819d185c6042b7ababacb26c708c stability issues] with the SM951. My model is reported as PM951 by [https://github.com/linux-nvme/nvme-cli nvme-cli] [[User:Tlvince|Tlvince]]. ([[User talk:Tlvince|talk]]) 19:06, 18 March 2017 (UTC)<br />
<br />
: Yep, the 13.3 Xiaomi has a PM951 for sure... is it noticeable the power saving improvement with this patched kernel? Looks like SM951 problems have been specifically patched and reached mainline... Should we try this or has it any risk for our data or drive [[User:Manudroid19|Manudroid19]] ([[User talk:Manudroid19|talk]]) 14:32, 19 March 2017 (UTC)<br />
<br />
:: I'm running the patches against 4.10.3 and am seeing ~1W reduction at idle. See [https://github.com/tlvince/linux-nvme/blob/04a7ceead5686f414bb7ba1ebfbeb594b660fad4/BENCHMARKS benchmarks]. Will update on any stability issues [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 21:05, 19 March 2017 (UTC)<br />
<br />
::: How do you measure the energy usage? I don't see such stadistics in tlp-stat... EDIT: I found out. Let's see if it improves. [[User:Manudroid19|Manudroid19]] ([[User talk:Manudroid19|talk]]) 22:28, 20 March 2017 (UTC)<br />
<br />
:::: Via [https://aur.archlinux.org/packages/powerstat-git powerstat-git] [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 09:44, 21 March 2017 (UTC)<br />
<br />
::::: Note, this nvme patch was required for my machine to enter into lower power states (p-states below C3), see [https://mjg59.dreamwidth.org/41713.html Skylake's power management under Linux is dreadful and you shouldn't buy one until it's fixed] [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 12:02, 15 April 2017 (UTC)<br />
<br />
:::::: Fixed in kernel 4.11.x [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 08:27, 24 May 2017 (UTC)<br />
<br />
== <s>WiFi</s> ==<br />
<br />
I think the wifi section shouldn't be removed, as it still concerns the LTS kernel as well as other distributions of arch. Antergos, for example, still ahs this bug. [[User:Manudroid19|Manudroid19]] ([[User talk:Manudroid19|talk]]) 19:43 8 April 2017 (UTC)<br />
<br />
: Makes sense. Removed the notice. -- [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 12:44, 10 April 2017 (UTC)<br />
<br />
== BIOS updates ==<br />
<br />
According to the MIUI forums ([http://en.miui.com/forum-106-1.html 1], [http://en.miui.com/thread-545654-1-1.html 2]), some Mi Airs are shipping with BIOS version A06. Mine's running A05. Has anyone found an updater? [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 12:06, 15 April 2017 (UTC)<br />
<br />
: Here ([http://en.miui.com/thread-574787-1-1.html 1]) someone made a dump and provided a flash tool. However, it's not official and hence it's not signed. I'm afraid of flashing it and messing my bios so I'll just wait for the official update if it comes. [[User:Manudroid19|Manudroid19]] ([[User talk:Manudroid19|talk]]) 10:59, 4 May 2017 (UTC)<br />
<br />
== Display Calibration ==<br />
The linked ICC profiles are for the Sharp LQ133M1JW15, however my Mi Air contains a Samsung 133HL09-M01. Shouldn't the different models be mentioned in the section to stop users from applying a profile for the wrong screen?<br />
<br />
Maybe there should also be a mention how to determine the lcd model for those who do not know how. One suggestion would be:<br />
<br />
<code>cat /sys/class/drm/card0-eDP-1/edid | edid-decode</code><br />
<br />
which requires [https://aur.archlinux.org/packages/edid-decode-git/ edid-decode-git]<br />
<br />
The source post ([http://en.miui.com/thread-418478-1-1.html]) for the icc profiles was updated as well to include profiles for the Samsung Panel, as i do not have an account for the miui forums i would appreciate it if those could be added to the linked git repository. - [[User:Blubbblubb|Blubbblubb]] ([[User talk:Blubbblubb|talk]]) 08:40, 26 May 2017 (UTC)<br />
<br />
: Thanks, added to repo. Mine was identified as SHP Model 1447, which I assume is the Sharp LQ133M1JW15 (its ICC profile certainly looks better to my eyes than the Samsung's either way). [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 09:46, 26 May 2017 (UTC)<br />
<br />
:: i can't find the other icc profiles, maybe you forgot to push the changes? - [[User:Blubbblubb|Blubbblubb]] ([[User talk:Blubbblubb|talk]]) 14:12, 26 May 2017 (UTC)<br />
<br />
::: All here [https://github.com/tlvince/xiaomi-mi-notebook-air-13/tree/master/display-calibration display calibration] - [[User:Tlvince|Tlvince]] ([[User talk:Tlvince|talk]]) 15:01, 26 May 2017 (UTC)<br />
<br />
:::: Oh sorry, i just clicked the link on the Wiki page, which linked to the initial commit, i just changed the link to the master branch - [[User:Blubbblubb|Blubbblubb]] ([[User talk:Blubbblubb|talk]]) 15:36, 26 May 2017 (UTC)<br />
<br />
== Graphics Card Configuration intel only ==<br />
<br />
Followed the instructions to disable the nvidia gpu and it didn't seem to work. Was tested on a fresh install, but I managed to blacklist the module using a different way.<br />
<br />
<code><br />
modprobe -r nouveau<br />
</code><br />
<br />
Additionally it seemed that nvidia doesn't need to be installed/blacklisted. Does this sound alright to you guys, or is this incorrect? Just checking with you guys before editing the wiki page.<br />
<br />
[[User:1cawk|1cawk]] ([[User talk:1cawk|talk]]) 02:43, 24 October 2017 (UTC)</div>1cawkhttps://wiki.archlinux.org/index.php?title=Termite&diff=481935Termite2017-07-15T10:14:03Z<p>1cawk: Changed the part about where to copy the config file from</p>
<hr />
<div>[[Category:Terminal emulators]]<br />
[[ja:Termite]]<br />
[https://www.github.com/thestinger/termite Termite] is a minimal [[:Category:Terminal emulators|terminal emulator]] designed for use with tiling [[window manager]]s. It is a ''modal'' application, similar to [[Vim]], with an insert mode and command mode where keybindings have different functions. Termite is based on the [https://developer.gnome.org/vte/unstable/ VTE] library.<br />
<br />
The configuration file allows to change colors and set some options. Termite supports transparency along with both the 256 color and true color (16 million colors) palettes. It has a similar look and feel to [[urxvt]].<br />
<br />
== Installation ==<br />
<br />
Install the {{Pkg|termite}} package, or {{AUR|termite-git}} for the development version. For Wayland tiling WM users, you may want to install {{AUR|termite-nocsd}} which disable client side decorations.<br />
<br />
== Usage ==<br />
<br />
Termite starts in insert mode by default. Text may be selected using the mouse, or by using command-mode keys. In insert mode, {{ic|Ctrl+Shift+c}} is used to copy selected text to the [[X]] clipboard, {{ic|Ctrl+Shift+v}} to paste. {{ic|Ctrl+Tab}} starts scrollback completion, and {{ic|Ctrl+Shift+Up}} / {{ic|Ctrl+Shift+Down}} scroll the screen up or down.<br />
<br />
{{ic|Ctrl+Shift+Space}} enters command-mode. Many commands are borrowed from [[Vim]], for example {{ic|v}} for visual mode, {{ic|Shift+v}} for visual line mode, {{ic|Ctrl+v}} for visual block mode, {{ic|y}} to copy ("yank") selected text, {{ic|/}} and {{ic|?}} for searching, {{ic|w}}, {{ic|b}}, {{ic|^}}, {{ic|$}} for movement, and {{ic|Escape}} to go back to insert mode.<br />
<br />
== Configuration ==<br />
Termite looks for configuration files in {{ic|$XDG_CONFIG_HOME/termite/config}}, {{ic|~/.config/termite/config}}, {{ic|$XDG_CONFIG_DIRS/termite/config}} and {{ic|/etc/xdg/termite.cfg}}. The configuration file is used to change options such as font, colors, window hints, etc. The configuration file is in ''ini'' format, with three sections: ''options'', ''colors'', and ''hints''.<br />
<br />
To start customizing termite copy the base example file to your home dir first:<br />
cp /etc/xdg/termite/config ~/.config/termite/config<br />
<br />
=== Font ===<br />
Fonts are specified in the format {{ic|1=font=<font_name> <font_size>}} under the ''options'' section. {{ic|<font_name>}} is specified according to [[fontconfig]], not [[X Logical Font Description|Xft]]. Use {{ic|fc-list}} to see which fonts are available on the system (see also [[Font configuration#Font paths]]).<br />
<br />
{{hc|~/.config/termite/config|2=<br />
[options]<br />
font = Monospace 9<br />
font = xos4 Terminus 12px<br />
font = Droid Sans Mono 8}}<br />
<br />
=== Colors ===<br />
Colors consist of either a 24-bit hex value (e.g. {{ic|#4a32b1}}), or an rgba vector (e.g. {{ic|rgba(16, 32, 64, 0.5)}}). Valid properties for colors are {{ic|foreground}}, {{ic|foreground_bold}}, {{ic|foreground_dim}}, {{ic|background}}, {{ic|cursor}}, and {{ic|colorN}} (where N is an integer from zero through 254; used to assign a 24-bit color value to terminal colorN).<br />
<br />
An amazing collection of termite color schemes can be found here: https://github.com/khamer/base16-termite/tree/master/themes<br />
<br />
{{hc|~/.config/termite/config|2=<br />
[colors]<br />
foreground = #dcdccc<br />
background = #3f3f3f}}<br />
<br />
== Transparency ==<br />
As of version 9, Termite supports true transparency via color definitions that specify an alpha channel value [https://github.com/thestinger/termite/issues/191]. This requires a compositor to be running, such as [[Compton]] or {{pkg|xcompmgr}}. Most compositors do not require special configuration for Termite to use transparency.<br />
<br />
{{hc|~/.config/termite/config|2=<br />
[colors]<br />
background = rgba(63, 63, 63, 0.8)<br />
}}<br />
<br />
{{Note|In [[i3]], in stacked/tabbed layout, this shows all windows "stacked" on top of each other, in the order they were most recently in the foreground, rather than showing the desktop (the root window) directly behind Termite. This is due to i3 reordering windows rather than hiding invisible windows in tiling mode. You can configure your compositor to make windows with {{ic|1=_NET_WM_STATE=_NET_WM_STATE_HIDDEN}} fully transparent to solve this. For example, for compton use<br />
{{hc|head=~/.compton.conf|output=opacity-rule = [<br />
"0:_NET_WM_STATE@:32a *= '_NET_WM_STATE_HIDDEN'"<br />
];}}<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Ctrl+Shift+t ===<br />
<br />
If opening a new tab through {{ic|Ctrl+Shift+t}} fails with {{ic|no directory uri set}}, [[source]] {{ic|/etc/profile.d/vte.sh}}. See [[GNOME/Tips and tricks#New terminals adopt current directory]].<br />
<br />
== See also ==<br />
<br />
* [https://github.com/thestinger/termite/blob/master/README.rst Termite readme]</div>1cawkhttps://wiki.archlinux.org/index.php?title=Xiaomi_Mi_Notebook_Air_13.3&diff=478145Xiaomi Mi Notebook Air 13.32017-05-24T05:12:44Z<p>1cawk: just fixed up a small typo</p>
<hr />
<div>[[Category:Xiaomi]]<br />
[[ja:Xiaomi Mi Notebook Air 13.3]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Working}} || ?<br />
|-<br />
| Webcam || {{G|Working}} || uvcvideo<br />
|-<br />
| USB-C / Thunderbolt 3 || {{G|Working}} || ?<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}} || ?<br />
|}<br />
<br />
The Mi Notebook Air 13.3 is an aluminium Ultrabook. It is a product by the Chinese Company Xiaomi and is currently only available in China or through import online-shops. Using the Intel Core i5 6200U @ 2.3 Ghz and the NVIDIA GeForce 940MX, it provides good power for a decent price.<br />
<br />
The installation should be going without any problems, if you follow the following steps.<br />
<br />
== Pre-Installation System Settings ==<br />
<br />
It is actually very easy getting the Arch Installation Medium to boot properly. Prior to booting the Arch installation ISO enter the UEFI menu by pressing F2 during Boot.<br />
<br />
* Security -> set password<br />
* Security -> Disable Secure Boot<br />
* reset the password by setting the password again but letting the "New Password" fields blank<br />
<br />
Installation of Arch can proceed normally. Refer to the [[Installation guide]] for more info.<br />
{{Note|1=Remember that your SSD is called {{ic|nvme0n1}}, not {{ic|sda}}.}}<br />
<br />
== Graphics Card Configuration ==<br />
<br />
The Mi Book has an Intel, as well as a Nvidia GPU. <br />
<br />
=== Intel Only ===<br />
<br />
If you want to completely disable the Nvidia GPU and save batterylife, do the following:<br />
<br />
* Install the {{pkg|xf86-video-intel}} package<br />
* Blacklist the {{pkg|nvidia}} and {{pkg|xf86-video-nouveau}} kernel modules [[Kernel modules#Blacklisting]]<br />
<br />
{{hc|/etc/modprobe.d/nouveau.conf|2=<br />
blacklist nouveau<br />
blacklist nvidia<br />
}}<br />
<br />
* Install {{pkg|bbswitch}} to [[Bumblebee#Power_management|turn off the card]]<br />
<br />
{{hc|/etc/modprobe.d/bbswitch|2=<br />
options bbswitch load_state=0 unload_state=0<br />
}}<br />
<br />
=== Intel/Nvidia Hybrid Configuration ===<br />
<br />
You can enable hybrid GPUs by either using [[Bumblebee]] or [[NVIDIA Optimus]]. Bumblebee is generally better for battery-life and compatibility but not officially supported by NVIDIA.<br />
<br />
Refer to the respective articles.<br />
<br />
== Input ==<br />
<br />
=== Touchpad ===<br />
<br />
To use the touchpad like a normal one, you have to use {{pkg|xf86-input-libinput}}. If you use {{pkg|xf86-input-evdev}}, your touchpad acts like a touchscreen (e.g it maps your movements directly to your screen). But if you are using {{pkg|xf86-input-synaptics}} (although you really should not, because it is deprecated (see [[Synaptics]])) things are only working sporadically. This configuration of {{pkg|libinput}} using XOrg configuration files enables two finger gestures, tap-to-click and 2-and 3-finger clicks (for right- and middle-click respectively).<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-touchpad.conf|2=<br />
Section "InputClass"<br />
Identifier "libinput touchpad"<br />
Driver "libinput"<br />
MatchIsTouchpad "on"<br />
MatchDevicePath "/dev/input/event*"<br />
Option "Tapping" "on"<br />
Option "ClickMethod" "clickfinger"<br />
Option "NaturalScrolling" "true"<br />
EndSection<br />
}}<br />
<br />
=== Fn-Keys ===<br />
<br />
On this notebook the Fn-keys are enabled as default (e.g. pressing F1 mutes the sound). If pressing the keys does nothing you are most likely using a [[Window manager]] and not a [[Desktop environment]]. Use the respective configuration files to bind the keys to their use. For example [[Xbindkeys]] or [[i3]]'s {{ic|bindsym}}.<br />
<br />
Most Fn-keys return the correct keycodes. Here is a table containing that information:<br />
<br />
{| class="wikitable"<br />
! Fn-F-Key<br />
! Keycode<br />
|-<br />
| {{ic|F1}}<br />
| {{ic|XF86AudioMute}}<br />
|-<br />
| {{ic|F2}}<br />
| {{ic|XF86AudioLowerVolume}}<br />
|-<br />
| {{ic|F3}}<br />
| {{ic|XF86AudioRaiseVolume}}<br />
|-<br />
| {{ic|F4}}<br />
| {{ic|XF86MonBrightnessDown}}<br />
|-<br />
| {{ic|F5}}<br />
| {{ic|XF86MonBrightnessUp}}<br />
|-<br />
| {{ic|F6}}<br />
| {{ic|Super_L + P}}<br />
|-<br />
| {{ic|F7}}<br />
| {{ic|Nothing}}<br />
|-<br />
| {{ic|F8}}<br />
| {{ic|Super_L + Tab}}<br />
|-<br />
| {{ic|F9}}<br />
| {{ic|Nothing}}<br />
|-<br />
| {{ic|F10}}<br />
| {{ic|Turns Keyboard backlight on/off}}<br />
|-<br />
| {{ic|F11}}<br />
| {{ic|Print}}<br />
|-<br />
| {{ic|F12}}<br />
| {{ic|Insert}}<br />
|}<br />
<br />
== Display Calibration ==<br />
<br />
Factory display calibration is poor. In lieu of a colorimeter, try the [[ICC profiles]] at [https://github.com/tlvince/xiaomi-mi-notebook-air-13/tree/085e5ad7034563256a42d8fb106e8c95057ddf6e/display-calibration tlvince/xiaomi-mi-notebook-air-13].<br />
<br />
== NVM Express SSD ==<br />
=== linux-nvme ===<br />
<br />
{{Out of date|This patch is now included in mainline (4.11rc1); the following steps will be redundant when 4.11 is released|section=linux-nvme}}<br />
<br />
Andy Lutomirski has created a patchset which fixes powersaving for NVME devices in Linux. Currently, this patch is not merged into mainline yet. Until it lands in mainline kernel use the AUR or repository linked below.<br />
<br />
{{App|linux-nvme|Mainline linux kernel patched with Andy's patch for NVME powersaving APST.|https://github.com/damige/linux-nvme|{{AUR|linux-nvme}}}} (check out [http://linuxnvme.damige.net/] for compiled packages)<br />
<br />
== Troubleshoothing ==<br />
<br />
=== Backlight ===<br />
<br />
If you use a tool like {{pkg|xorg-xbacklight}} in its default configuration, nothing happens, because the path to the backlighting variable is not standard. To fix this issue, you have to use a X-Org configuration file:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/10-backlight.conf|2=<br />
Section "Device" <br />
Identifier "Card0" <br />
Driver "intel" <br />
Option "Backlight" "intel_backlight" <br />
BusID "PCI:0:2:0" <br />
EndSection <br />
}}<br />
<br />
=== WiFi ===<br />
<br />
If you are having issues with the auto-detected WiFi drivers, that is because there is a conflict between two of them, as you can see using {{ic|rfkill list}} To solve it, block the wrong driver:<br />
<br />
{{hc|/etc/modprobe.d/blacklist.conf|2=<br />
blacklist acer-wmi<br />
}}<br />
<br />
Note, this issue is fixed in kernel version 4.9 and above.</div>1cawk