https://wiki.archlinux.org/api.php?action=feedcontributions&user=Netadmin&feedformat=atomArchWiki - User contributions [en]2024-03-29T15:29:09ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Udev&diff=435573Talk:Udev2016-05-19T14:01:00Z<p>Netadmin: Marking talk section on Hot Plug for deletion and already added feedback to main page.</p>
<hr />
<div>== usbtiny extra udev rule? ==<br />
In the udev rules for usbtiny, there are 2 rules listed. Howver, adding the second one to my udev rules resulted in me not an "rc=-1" communication error when I tried to use my usbtiny. When I commented out this rule:<br />
"SBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"<br />
everything worked fine. Not sure what the root of the issue is, but this rule makes the usbtiny programer unusable. -- [[User:Ssalenik|Ssalenik]] ([[User talk:Ssalenik|talk]]) 04:09, 6 March 2012<br />
<br />
== About udev rules ==<br />
udevadm info -a -n [device name]<br />
and<br />
udevadm info -a -p $(udevadm info -q path -n [device name])<br />
gives the same output but the latter is recommended by some [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)<br />
<br />
== Use of 'uaccess' instead of GROUP and MODE? ==<br />
<br />
Bug [https://bugs.archlinux.org/task/35602 openobex - relies on non-existing group plugdev, conflict with systemd] made me rethink the rules I have been using for [[Logitech_Unifying_Receiver]].<br />
<br />
Currently, the following rule is taught to the user:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"<br />
What about changing it to:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess"<br />
<br />
As a developer note, Ubuntu versions before 13.04 Raring needs {{ic|<nowiki>TAG+="udev-acl"</nowiki>}} instead of uaccess. For compatibility with modern and legacy systems:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess", TAG+="udev-acl"<br />
<br />
References:<br />
* http://cgit.freedesktop.org/systemd/systemd/tree/src/login/70-uaccess.rules<br />
[[User:Lekensteyn|Lekensteyn]] ([[User talk:Lekensteyn|talk]]) 10:16, 6 June 2013 (UTC)<br />
<br />
== Printers ==<br />
<br />
[[Udev#Printers]]:<br />
<br />
If you use multiple printers, /dev/lp[0-9] devices will be assigned randomly on boot, which will break e.g. CUPS configuration.<br />
<br />
I don't use multiple printers, but doesn't {{Pkg|system-config-printer}} handle this automatically? If so, a tip could be added. --[[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:38, 28 June 2014 (UTC)<br />
<br />
:It might, unfortunately its {{Pkg|gtk3}} dependency discouraged me from even trying... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:01, 28 June 2014 (UTC)<br />
<br />
== <s>Additional detail on "Execute on VGA cable plug"</s> ==<br />
<br />
Not sure if it belongs in this wiki, but worth noting in the hot plug example that the Xauthority may be located elsewhere based on display manager. <br />
<br />
This is the example:<br />
<br />
KERNEL=="card0", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/username/.Xauthority", RUN+="/usr/bin/arandr"<br />
<br />
If you have GDM and you check the Xauthority location as follows:<br />
<br />
$ env | grep XAUTHORITY<br />
XAUTHORITY=/run/user/1000/gdm/Xauthority<br />
<br />
You will see the file is not in a home directory and you need to tweak the ENV{XAUTHORITY} accordingly.<br />
<br />
Not sure if this bit of information is useful in the wiki or consider overly specific for this use case. [[User:Netadmin|Netadmin]] ([[User talk:Netadmin|talk]]) 16:22, 10 May 2016 (UTC)<br />
<br />
:Well this is another example why you should never hardcode [[Xorg]] variables. I agree it should be fixed. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 16:27, 10 May 2016 (UTC)<br />
<br />
::In this rule the hard-coded value is ''assigned'' to ENV{XAUTHORITY}. In any case, you can't make the udev rule work without hardcoding, because udev does not have access to the environment of the ''currently active'' session. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:46, 10 May 2016 (UTC)<br />
<br />
:::Well, you could run a wrapper script in the udev rule, which retrieves the XAUTHORITY env (e.g from {{ic|/proc/foo/environ}}) and passes it to arandr. Would take some experimenting to get it universally working, but should be good to have. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:12, 10 May 2016 (UTC)<br />
<br />
: I updated the Hot Plug section to note that .Xauthority may be located in different locations based on the display manager. [[User:Netadmin|Netadmin]] ([[User talk:Netadmin|talk]]) 14:00, 19 May 2016 (UTC)</div>Netadminhttps://wiki.archlinux.org/index.php?title=Udev&diff=434736Udev2016-05-12T13:26:48Z<p>Netadmin: Cleanup execute on VGA DM comment I just added</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Hardware detection and troubleshooting]]<br />
[[cs:Udev]]<br />
[[de:Udev]]<br />
[[es:Udev]]<br />
[[fr:Udev]]<br />
[[it:Udev]]<br />
[[ja:Udev]]<br />
[[ru:Udev]]<br />
[[zh-CN:Udev]]<br />
[[zh-TW:Udev]]<br />
{{Related articles start}}<br />
{{Related|udisks}}<br />
{{Related articles end}}<br />
<br />
From [[Wikipedia:udev|Wikipedia article]]:<br />
<br />
:udev is a device manager for the Linux kernel. As the successor of devfsd and hotplug, udev primarily manages device nodes in the {{ic|/dev}} directory. At the same time, udev also handles all user space events raised while hardware devices are added into the system or removed from it, including firmware loading as required by certain devices.<br />
<br />
{{ic|udev}} replaces the functionality of both {{ic|hotplug}} and {{ic|hwdetect}}.<br />
<br />
Udev loads kernel modules by utilizing coding parallelism to provide a potential performance advantage versus loading these modules serially. The modules are therefore loaded asynchronously. The inherent disadvantage of this method is that udev does not always load modules in the same order on each boot. If the machine has multiple block devices, this may manifest itself in the form of device nodes changing designations randomly. For example, if the machine has two hard drives, {{ic|/dev/sda}} may randomly become {{ic|/dev/sdb}}. See below for more info on this.<br />
<br />
== Installation ==<br />
<br />
Udev is now part of {{Pkg|systemd}} and is installed by default. See the {{ic|systemd-udevd.service(8)}} [[man page]] for information.<br />
<br />
A standalone fork is available in AUR: [[eudev]].<br />
<br />
== About udev rules ==<br />
<br />
Udev rules written by the administrator go in {{ic|/etc/udev/rules.d/}}, their file name has to end with ''.rules''. The udev rules shipped with various packages are found in {{ic|/usr/lib/udev/rules.d/}}. If there are two files by the same name under {{ic|/usr/lib}} and {{ic|/etc}}, the ones in {{ic|/etc}} take precedence.<br />
<br />
=== Writing udev rules ===<br />
<br />
{{Expansion|You can workaround the FUSE errors (caused by udev killing the mount process) by using a systemd service [https://github.com/Ferk/udev-media-automount] [http://jasonwryan.com/blog/2014/01/20/udev/]}}<br />
<br />
{{Warning|To mount removable drives, do not call {{ic|mount}} from udev rules. In case of FUSE filesystems, you will get {{ic|Transport endpoint not connected}} errors. Instead, you could use [[udisks]] that handles automount correctly or to make mount work inside udev rules, copy {{ic|/usr/lib/systemd/system/systemd-udevd.service}} to {{ic|/etc/systemd/system/systemd-udevd.service}} and replace {{ic|1=MountFlags=slave}} to {{ic|1=MountFlags=shared}}.[http://unix.stackexchange.com/a/154318] Keep in mind though that udev is not intended to invoke long-running processes.}}<br />
<br />
* To learn how to write udev rules, see [http://www.reactivated.net/writing_udev_rules.html Writing udev rules].<br />
* To see an example udev rule, follow the [http://www.reactivated.net/writing_udev_rules.html#example-printer Examples] section of the above guide.<br />
<br />
This is an example of a rule that places a symlink {{ic|/dev/video-cam1}} when a webcamera is connected. First, we have found out that this camera is connected and has loaded with the device {{ic|/dev/video2}}. The reason for writing this rule is that at the next boot the device might just as well show up under a different name like {{ic|/dev/video0}}.<br />
<br />
{{hc|# udevadm info -a -p $(udevadm info -q path -n /dev/video2)|<nowiki><br />
Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device.<br />
<br />
looking at device '/devices/pci0000:00/0000:00:04.1/usb3/3-2/3-2:1.0/video4linux/video2':<br />
KERNEL=="video2"<br />
SUBSYSTEM=="video4linux"<br />
...<br />
looking at parent device '/devices/pci0000:00/0000:00:04.1/usb3/3-2/3-2:1.0':<br />
KERNELS=="3-2:1.0"<br />
SUBSYSTEMS=="usb"<br />
...<br />
looking at parent device '/devices/pci0000:00/0000:00:04.1/usb3/3-2':<br />
KERNELS=="3-2"<br />
SUBSYSTEMS=="usb"<br />
...<br />
ATTRS{idVendor}=="05a9"<br />
...<br />
ATTRS{manufacturer}=="OmniVision Technologies, Inc."<br />
ATTRS{removable}=="unknown"<br />
ATTRS{idProduct}=="4519"<br />
ATTRS{bDeviceClass}=="00"<br />
ATTRS{product}=="USB Camera"<br />
...<br />
</nowiki>}}<br />
<br />
From the video4linux device we use {{ic|<nowiki>KERNEL=="video2"</nowiki>}} and {{ic|<nowiki>SUBSYSTEM=="video4linux"</nowiki>}}, then we match the webcam using vendor and product ID's from the usb parent {{ic|<nowiki>SUBSYSTEMS=="usb"</nowiki>}}, {{ic|<nowiki>ATTRS{idVendor}=="05a9"</nowiki>}} and {{ic|<nowiki>ATTRS{idProduct}=="4519"</nowiki>}}.<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam.rules|<nowiki><br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="05a9", ATTRS{idProduct}=="4519", SYMLINK+="video-cam1"<br />
</nowiki>}}<br />
<br />
In the example above we create a symlink using {{ic|<nowiki>SYMLINK+="video-cam1"</nowiki>}} but we could easily set user {{ic|<nowiki>OWNER="john"</nowiki>}} or group using {{ic|<nowiki>GROUP="video"</nowiki>}} or set the permissions using {{ic|<nowiki>MODE="0660"</nowiki>}}. However, if you intend to write a rule to do something when a device is being removed, be aware that device attributes may not be accessible. In this case, you will have to work with preset device [[environment variables]]. To monitor those environment variables, execute the following command while unplugging your device:<br />
<br />
# udevadm monitor --environment --udev<br />
<br />
In this command's output, you will see value pairs such as ID_VENDOR_ID and ID_MODEL_ID, which match your previously used attributes "idVendor" and "idProduct". A rule that uses device environment variables may look like this:<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam-removed.rules|<nowiki><br />
ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="05a9", ENV{ID_MODEL_ID}=="4519", RUN+="/path/to/your/script"<br />
</nowiki>}}<br />
<br />
=== List attributes of a device ===<br />
<br />
To get a list of all of the attributes of a device you can use to write rules, run this command:<br />
<br />
# udevadm info -a -n [device name]<br />
<br />
Replace {{ic|[device name]}} with the device present in the system, such as {{ic|/dev/sda}} or {{ic|/dev/ttyUSB0}}.<br />
<br />
If you do not know the device name you can also list all attributes of a specific system path:<br />
<br />
# udevadm info -a -p /sys/class/backlight/acpi_video0<br />
<br />
=== Testing rules before loading ===<br />
<br />
# udevadm test $(udevadm info -q path -n [device name]) 2>&1<br />
<br />
This will not perform all actions in your new rules but it will however process symlink rules on existing devices which might come in handy if you are unable to load them otherwise. You can also directly provide the path to the device you want to test the udev rule for:<br />
<br />
# udevadm test /sys/class/backlight/acpi_video0/<br />
<br />
=== Loading new rules ===<br />
<br />
Udev automatically detects changes to rules files, so changes take effect immediately without requiring udev to be restarted. However, the rules are not re-triggered automatically on already existing devices. Hot-pluggable devices, such as USB devices, will probably have to be reconnected for the new rules to take effect, or at least unloading and reloading the ohci-hcd and ehci-hcd kernel modules and thereby reloading all USB drivers.<br />
<br />
If rules fail to reload automatically<br />
<br />
# udevadm control --reload<br />
<br />
To manually force udev to trigger your rules<br />
<br />
# udevadm trigger<br />
<br />
== Udisks ==<br />
<br />
See [[Udisks]].<br />
<br />
== Tips and tricks ==<br />
<br />
=== Accessing firmware programmers and USB virtual comm devices ===<br />
<br />
{{Accuracy|Making a device world-writable is not secure.}}<br />
{{Style|One example is enough, others can surely be found with {{ic|lsusb}}.}}<br />
<br />
The following ruleset will allow normal users (within the "users" group) the ability to access the [http://www.ladyada.net/make/usbtinyisp/ USBtinyISP] USB programmer for AVR microcontrollers and a generic (SiLabs [http://www.silabs.com/products/interface/usbtouart CP2102]) USB to UART adapter, the [http://www.atmel.com/tools/AVRDRAGON.aspx?tab=overview Atmel AVR Dragon] programmer, and the [http://www.atmel.com/tools/AVRISPMKII.aspx Atmel AVR ISP mkII]. Adjust the permissions accordingly. Verified as of 31-10-2012.<br />
<br />
{{hc|/etc/udev/rules.d/50-embedded_devices.rules|2=<nowiki><br />
# USBtinyISP Programmer rules<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"<br />
<br />
# USBasp Programmer rules http://www.fischl.de/usbasp/<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="users", MODE="0666"<br />
<br />
# Mdfly.com Generic (SiLabs CP2102) 3.3v/5v USB VComm adapter<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", GROUP="users", MODE="0666"<br />
<br />
#Atmel AVR Dragon (dragon_isp) rules<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2107", GROUP="users", MODE="0666"<br />
<br />
#Atmel AVR JTAGICEMKII rules<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2103", GROUP="users", MODE="0666"<br />
<br />
#Atmel Corp. AVR ISP mkII<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2104", GROUP="users", MODE="0666"<br />
<br />
#Atmel Copr. JTAGICE3<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2140", GROUP="users", MODE="0666"<br />
</nowiki>}}<br />
<br />
=== Execute on USB insert ===<br />
<br />
See the [[Execute on USB insert]] article or the [http://igurublog.wordpress.com/downloads/script-devmon/ devmon wrapper script].<br />
<br />
=== Execute on VGA cable plug in ===<br />
<br />
Create the rule {{ic|/etc/udev/rules.d/95-monitor-hotplug.rules}} with the following content to launch {{Pkg|arandr}} on plug in of a VGA monitor cable:<br />
<br />
KERNEL=="card0", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/''username''/.Xauthority", RUN+="/usr/bin/arandr"<br />
<br />
Some display managers store the .Xauthority outside the user home directory. You will need to update the ENV{XAUTHORITY} accordingly. As an example [[GDM|GNOME Display Manager]] looks as follows:<br />
<br />
# env | grep XAUTHORITY<br />
XAUTHORITY=/run/user/1000/gdm/Xauthority<br />
<br />
=== Detect new eSATA drives ===<br />
<br />
If your eSATA drive is not detected when you plug it in, there are a few things you can try. You can reboot with the eSATA plugged in. Or you could try<br />
<br />
# echo 0 0 0 | tee /sys/class/scsi_host/host*/scan<br />
<br />
Or you could install {{AUR|scsiadd}} (from the AUR) and try<br />
<br />
# scsiadd -s<br />
<br />
Hopefully, your drive is now in {{ic|/dev}}. If it is not, you could try the above commands while running<br />
<br />
# udevadm monitor<br />
<br />
to see if anything is actually happening.<br />
<br />
=== Mark internal SATA ports as eSATA ===<br />
<br />
If you connected a eSATA bay or an other eSATA adapter the system will still recognize this disk as an internal SATA drive. [[GNOME]] and [[KDE]] will ask you for your root password all the time. The following rule will mark the specified SATA-Port as an external eSATA-Port. With that, a normal GNOME user can connect their eSATA drives to that port like a USB drive, without any root password and so on.<br />
<br />
{{hc|/etc/udev/rules.d/10-esata.rules|2=<nowiki><br />
DEVPATH=="/devices/pci0000:00/0000:00:1f.2/host4/*", ENV{UDISKS_SYSTEM}="0"<br />
</nowiki>}}<br />
<br />
{{Note|The {{ic|DEVPATH}} can be found after connection the eSATA drive with the following commands (replace {{ic|sdb}} accordingly):<br />
<br />
# udevadm info -q path -n /dev/sdb<br />
/devices/pci0000:00/0000:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdb<br />
<br />
# find /sys/devices/ -name sdb<br />
/sys/devices/pci0000:00/0000:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdb<br />
}}<br />
<br />
=== Setting static device names ===<br />
<br />
Because udev loads all modules asynchronously, they are initialized in a different order. This can result in devices randomly switching names. A udev rule can be added to use static device names.<br />
<br />
See also [[Persistent block device naming]] for block devices and [[Network configuration#Device names]] for network devices.<br />
<br />
==== Video devices ====<br />
<br />
For setting up the webcam in the first place, refer to [[Webcam setup#Webcam configuration|Webcam configuration]].<br />
<br />
Using multiple webcams, useful for example with {{pkg|motion}} (software motion detector which grabs images from video4linux devices and/or from webcams), will assign video devices as /dev/video0..n randomly on boot. The recommended solution is to create symlinks using an ''udev'' rule (as in the example in [[#Writing udev rules]]):<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam.rules|<nowiki><br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="05a9", ATTRS{idProduct}=="4519", SYMLINK+="video-cam1"<br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="08f6", SYMLINK+="video-cam2"<br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0840", SYMLINK+="video-cam3"<br />
</nowiki>}}<br />
<br />
{{Note|Using names other than {{ic|/dev/video*}} will break preloading of {{ic|v4l1compat.so}} and perhaps {{ic|v4l2convert.so}}}}<br />
<br />
==== Printers ====<br />
<br />
If you use multiple printers, {{ic|/dev/lp[0-9]}} devices will be assigned randomly on boot, which will break e.g. [[CUPS]] configuration. <br />
<br />
You can create following rule, which will create symlinks under {{ic|/dev/lp/by-id}} and {{ic|/dev/lp/by-path}}, similar to [[Persistent block device naming]] scheme:<br />
<br />
{{hc|/etc/udev/rules.d/60-persistent-printer.rules|<nowiki><br />
ACTION=="remove", GOTO="persistent_printer_end"<br />
<br />
# This should not be necessary<br />
#KERNEL!="lp*", GOTO="persistent_printer_end"<br />
<br />
SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"<br />
ENV{ID_TYPE}!="printer", GOTO="persistent_printer_end"<br />
<br />
ENV{ID_SERIAL}=="?*", SYMLINK+="lp/by-id/$env{ID_BUS}-$env{ID_SERIAL}"<br />
<br />
IMPORT{builtin}="path_id"<br />
ENV{ID_PATH}=="?*", SYMLINK+="lp/by-path/$env{ID_PATH}"<br />
<br />
LABEL="persistent_printer_end"<br />
</nowiki>}}<br />
<br />
==== USB flash device ====<br />
<br />
USB flash devices usually contain partitions, and partition labels are one way to have a static naming for a device. Another way is to create a udev rule for it. <br />
<br />
Get the serial number and USB ids from the USB flash drive (if you use multiple of the same make, you might have to check the serial is indeed unique):<br />
lsusb -v | grep -A 5 Vendor<br />
<br />
Create a udev rule for it by adding the following to a file in {{ic|/etc/udev/rules.d/}}, such as {{ic|8-usbstick.rules}}:<br />
KERNEL=="sd*", ATTRS{serial}=="$SERIAL", ATTRS{idVendor}=="$VENDOR", ATTRS{idProduct}=="$PRODUCT" SYMLINK+="$SYMLINK%n"<br />
<br />
Replace {{ic|$SERIAL}}, {{ic|$VENDOR}}, {{ic|$PRODUCT}} from above output accordingly and {{ic|$SYMLINK}} with the desired name. {{ic|%n}} will expand to the partition number. For example, if the device has two partitions, two symlinks will be created. You do not need to go with the 'serial' attribute. If you have a custom rule of your own, you can put it in as well (e.g. using the vendor name).<br />
<br />
Rescan sysfs:<br />
udevadm trigger<br />
Now check the contents of {{ic|/dev}}:<br />
ls /dev<br />
It should show the device with the desired name.<br />
<br />
=== Waking from suspend with USB device ===<br />
<br />
First, find vendor and product ID of your device, for example<br />
<br />
{{hc|<nowiki># lsusb | grep Logitech</nowiki>|Bus 007 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver}}<br />
<br />
Now change the {{ic|power/wakeup}} attribute of the device and the USB controller it is connected to, which is in this case {{ic|driver/usb7/power/wakeup}}. Use the following rule:<br />
<br />
{{hc|/etc/udev/rules.d/50-wake-on-device.rules|<nowiki><br />
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ATTR{power/wakeup}="enabled", ATTR{driver/usb7/power/wakeup}="enabled"<br />
</nowiki>}}<br />
<br />
{{Note|Also make sure the USB controller is enabled in {{ic|/proc/acpi/wakeup}}.}}<br />
<br />
=== Triggering events ===<br />
<br />
{{Merge|#Testing rules before loading|similar trick}}<br />
<br />
It can be useful to trigger various udev events. For example, you might want to simulate a USB device disconnect on a remote machine. In such cases, use {{ic|udevadm trigger}}:<br />
<br />
# udevadm trigger -v -t subsystems -c remove -s usb -a "idVendor=abcd"<br />
<br />
This command will trigger a USB remove event on all USB devices with vendor ID {{ic|abcd}}.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Blacklisting modules ===<br />
<br />
In rare cases, udev can make mistakes and load the wrong modules. To prevent it from doing this, you can blacklist modules. Once blacklisted, udev will never load that module. See [[blacklisting]]. Not at boot-time ''or'' later on when a hotplug event is received (eg, you plug in your USB flash drive).<br />
<br />
=== Debug output ===<br />
<br />
To get hardware debug info, use the [[kernel parameter]] {{ic|1=udev.log-priority=debug}}. Alternatively you can set<br />
<br />
{{hc|/etc/udev/udev.conf|2=udev_log="debug"}}<br />
<br />
This option can also be compiled into your initramfs by adding the config file to your {{ic|FILES}} array<br />
<br />
{{hc|/etc/mkinitcpio.conf|2=FILES="... /etc/udev/udev.conf"}}<br />
<br />
and then rebuilding the initramfs with<br />
<br />
# mkinitcpio -p linux<br />
<br />
=== udevd hangs at boot ===<br />
<br />
After migrating to LDAP or updating an LDAP-backed system udevd can hang at boot at the message "Starting UDev Daemon". This is usually caused by udevd trying to look up a name from LDAP but failing, because the network is not up yet. The solution is to ensure that all system group names are present locally.<br />
<br />
Extract the group names referenced in udev rules and the group names actually present on the system:<br />
<br />
# fgrep -r GROUP /etc/udev/rules.d/ /usr/lib/udev/rules.d | perl -nle '/GROUP\s*=\s*"(.*?)"/ && print $1;' | sort | uniq > udev_groups<br />
# cut -f1 -d: /etc/gshadow /etc/group | sort | uniq > present_groups<br />
<br />
To see the differences, do a side-by-side diff:<br />
<br />
# diff -y present_groups udev_groups<br />
...<br />
network <<br />
nobody <<br />
ntp <<br />
optical optical<br />
power | pcscd<br />
rfkill <<br />
root root<br />
scanner scanner<br />
smmsp <<br />
storage storage<br />
...<br />
<br />
In this case, the {{ic|pcscd}} group is for some reason not present in the system. [[Users and groups#Group management|Add the missing groups]]. Also, make sure that local resources are looked up before resorting to LDAP. {{ic|/etc/nsswitch.conf}} should contain the following line:<br />
<br />
group: files ldap<br />
<br />
=== BusLogic devices can be broken and will cause a freeze during startup ===<br />
<br />
This is a kernel bug and no fix has been provided yet.<br />
<br />
=== Some devices, that should be treated as removable, are not ===<br />
<br />
You need to create a custom udev rule for that particular device. To get definitive information of the device you can use either {{ic|ID_SERIAL}} or {{ic|ID_SERIAL_SHORT}} (remember to change {{ic|/dev/sdb}} if needed):<br />
<br />
$ udevadm info /dev/sdb | grep ID_SERIAL<br />
<br />
Then we create a rule in {{ic|/etc/udev/rules.d/}} and set variables for either udisks or udisks2.<br />
<br />
For udisks, set {{ic|1=UDISKS_SYSTEM_INTERNAL="0"}}, which will mark the device as "removable" and thus "eligible for automounting". See [http://udisks.freedesktop.org/docs/1.0.5/udisks.7.html udisks(7)] for details.<br />
<br />
{{hc|/etc/udev/rules.d/50-external-myhomedisk.rules|2=<br />
ENV{ID_SERIAL_SHORT}=="''serial_number''", ENV{UDISKS_SYSTEM_INTERNAL}="0"<br />
}}<br />
<br />
For udisks2, set {{ic|1=UDISKS_AUTO="1"}} to mark the device for automounting and {{ic|1=UDISKS_SYSTEM="0"}} to mark the device as "removable". See [http://udisks.freedesktop.org/docs/1.93.0/udisks.8.html udisks(8)] for details.<br />
<br />
{{hc|/etc/udev/rules.d/99-removable.rules|2=<br />
ENV{ID_SERIAL_SHORT}=="''serial_number''", ENV{UDISKS_AUTO}="1", ENV{UDISKS_SYSTEM}="0"<br />
}}<br />
<br />
Remember to reload udev rules with {{ic|udevadm control --reload}}. Next time you plug your device in, it will be treated as an external drive.<br />
<br />
=== Sound problems with some modules not loaded automatically ===<br />
<br />
Some users have traced this problem to old entries in {{ic|/etc/modprobe.d/sound.conf}}. Try cleaning that file out and trying again.<br />
<br />
{{Note|Since {{ic|1=udev>=171}}, the OSS emulation modules ({{ic|snd_seq_oss}}, {{ic|snd_pcm_oss}}, {{ic|snd_mixer_oss}}) are not automatically loaded by default.}}<br />
<br />
=== IDE CD/DVD-drive support ===<br />
<br />
Starting with version 170, udev does not support CD-ROM/DVD-ROM drives that are loaded as traditional IDE drives with the {{ic|ide_cd_mod}} module and show up as {{ic|/dev/hd*}}. The drive remains usable for tools which access the hardware directly, like ''cdparanoia'', but is invisible for higher userspace programs, like KDE.<br />
<br />
A cause for the loading of the ide_cd_mod module prior to others, like sr_mod, could be e.g. that you have for some reason the module piix loaded with your [[initramfs]]. In that case you can just replace it with ata_piix in your {{ic|/etc/mkinitcpio.conf}}.<br />
<br />
=== Optical drives have group ID set to "disk" ===<br />
<br />
If the group ID of your optical drive is set to {{ic|disk}} and you want to have it set to {{ic|optical}}, you have to create a custom udev rule:<br />
<br />
{{hc|/etc/udev/rules.d|2=<nowiki><br />
# permissions for IDE CD devices<br />
SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTR{removable}=="1", ATTRS{media}=="cdrom*", GROUP="optical"<br />
<br />
# permissions for SCSI CD devices<br />
SUBSYSTEMS=="scsi", KERNEL=="s[rg][0-9]*", ATTRS{type}=="5", GROUP="optical"</nowiki>}}<br />
<br />
== See also ==<br />
<br />
* [https://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/udev.html udev home page]<br />
* [https://www.linux.com/news/hardware/peripherals/180950-udev An Introduction to udev]<br />
* [http://vger.kernel.org/vger-lists.html#linux-hotplug udev mailing list information]<br />
* [http://jasonwryan.com/blog/2014/01/20/udev/ Scripting with udev]<br />
* [http://www.reactivated.net/writing_udev_rules.html Writing udev rules]</div>Netadminhttps://wiki.archlinux.org/index.php?title=Udev&diff=434735Udev2016-05-12T13:24:46Z<p>Netadmin: Adding comment about .Xauthority being stored in alternate places based on DM</p>
<hr />
<div>{{Lowercase title}}<br />
[[Category:Hardware detection and troubleshooting]]<br />
[[cs:Udev]]<br />
[[de:Udev]]<br />
[[es:Udev]]<br />
[[fr:Udev]]<br />
[[it:Udev]]<br />
[[ja:Udev]]<br />
[[ru:Udev]]<br />
[[zh-CN:Udev]]<br />
[[zh-TW:Udev]]<br />
{{Related articles start}}<br />
{{Related|udisks}}<br />
{{Related articles end}}<br />
<br />
From [[Wikipedia:udev|Wikipedia article]]:<br />
<br />
:udev is a device manager for the Linux kernel. As the successor of devfsd and hotplug, udev primarily manages device nodes in the {{ic|/dev}} directory. At the same time, udev also handles all user space events raised while hardware devices are added into the system or removed from it, including firmware loading as required by certain devices.<br />
<br />
{{ic|udev}} replaces the functionality of both {{ic|hotplug}} and {{ic|hwdetect}}.<br />
<br />
Udev loads kernel modules by utilizing coding parallelism to provide a potential performance advantage versus loading these modules serially. The modules are therefore loaded asynchronously. The inherent disadvantage of this method is that udev does not always load modules in the same order on each boot. If the machine has multiple block devices, this may manifest itself in the form of device nodes changing designations randomly. For example, if the machine has two hard drives, {{ic|/dev/sda}} may randomly become {{ic|/dev/sdb}}. See below for more info on this.<br />
<br />
== Installation ==<br />
<br />
Udev is now part of {{Pkg|systemd}} and is installed by default. See the {{ic|systemd-udevd.service(8)}} [[man page]] for information.<br />
<br />
A standalone fork is available in AUR: [[eudev]].<br />
<br />
== About udev rules ==<br />
<br />
Udev rules written by the administrator go in {{ic|/etc/udev/rules.d/}}, their file name has to end with ''.rules''. The udev rules shipped with various packages are found in {{ic|/usr/lib/udev/rules.d/}}. If there are two files by the same name under {{ic|/usr/lib}} and {{ic|/etc}}, the ones in {{ic|/etc}} take precedence.<br />
<br />
=== Writing udev rules ===<br />
<br />
{{Expansion|You can workaround the FUSE errors (caused by udev killing the mount process) by using a systemd service [https://github.com/Ferk/udev-media-automount] [http://jasonwryan.com/blog/2014/01/20/udev/]}}<br />
<br />
{{Warning|To mount removable drives, do not call {{ic|mount}} from udev rules. In case of FUSE filesystems, you will get {{ic|Transport endpoint not connected}} errors. Instead, you could use [[udisks]] that handles automount correctly or to make mount work inside udev rules, copy {{ic|/usr/lib/systemd/system/systemd-udevd.service}} to {{ic|/etc/systemd/system/systemd-udevd.service}} and replace {{ic|1=MountFlags=slave}} to {{ic|1=MountFlags=shared}}.[http://unix.stackexchange.com/a/154318] Keep in mind though that udev is not intended to invoke long-running processes.}}<br />
<br />
* To learn how to write udev rules, see [http://www.reactivated.net/writing_udev_rules.html Writing udev rules].<br />
* To see an example udev rule, follow the [http://www.reactivated.net/writing_udev_rules.html#example-printer Examples] section of the above guide.<br />
<br />
This is an example of a rule that places a symlink {{ic|/dev/video-cam1}} when a webcamera is connected. First, we have found out that this camera is connected and has loaded with the device {{ic|/dev/video2}}. The reason for writing this rule is that at the next boot the device might just as well show up under a different name like {{ic|/dev/video0}}.<br />
<br />
{{hc|# udevadm info -a -p $(udevadm info -q path -n /dev/video2)|<nowiki><br />
Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device.<br />
<br />
looking at device '/devices/pci0000:00/0000:00:04.1/usb3/3-2/3-2:1.0/video4linux/video2':<br />
KERNEL=="video2"<br />
SUBSYSTEM=="video4linux"<br />
...<br />
looking at parent device '/devices/pci0000:00/0000:00:04.1/usb3/3-2/3-2:1.0':<br />
KERNELS=="3-2:1.0"<br />
SUBSYSTEMS=="usb"<br />
...<br />
looking at parent device '/devices/pci0000:00/0000:00:04.1/usb3/3-2':<br />
KERNELS=="3-2"<br />
SUBSYSTEMS=="usb"<br />
...<br />
ATTRS{idVendor}=="05a9"<br />
...<br />
ATTRS{manufacturer}=="OmniVision Technologies, Inc."<br />
ATTRS{removable}=="unknown"<br />
ATTRS{idProduct}=="4519"<br />
ATTRS{bDeviceClass}=="00"<br />
ATTRS{product}=="USB Camera"<br />
...<br />
</nowiki>}}<br />
<br />
From the video4linux device we use {{ic|<nowiki>KERNEL=="video2"</nowiki>}} and {{ic|<nowiki>SUBSYSTEM=="video4linux"</nowiki>}}, then we match the webcam using vendor and product ID's from the usb parent {{ic|<nowiki>SUBSYSTEMS=="usb"</nowiki>}}, {{ic|<nowiki>ATTRS{idVendor}=="05a9"</nowiki>}} and {{ic|<nowiki>ATTRS{idProduct}=="4519"</nowiki>}}.<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam.rules|<nowiki><br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="05a9", ATTRS{idProduct}=="4519", SYMLINK+="video-cam1"<br />
</nowiki>}}<br />
<br />
In the example above we create a symlink using {{ic|<nowiki>SYMLINK+="video-cam1"</nowiki>}} but we could easily set user {{ic|<nowiki>OWNER="john"</nowiki>}} or group using {{ic|<nowiki>GROUP="video"</nowiki>}} or set the permissions using {{ic|<nowiki>MODE="0660"</nowiki>}}. However, if you intend to write a rule to do something when a device is being removed, be aware that device attributes may not be accessible. In this case, you will have to work with preset device [[environment variables]]. To monitor those environment variables, execute the following command while unplugging your device:<br />
<br />
# udevadm monitor --environment --udev<br />
<br />
In this command's output, you will see value pairs such as ID_VENDOR_ID and ID_MODEL_ID, which match your previously used attributes "idVendor" and "idProduct". A rule that uses device environment variables may look like this:<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam-removed.rules|<nowiki><br />
ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="05a9", ENV{ID_MODEL_ID}=="4519", RUN+="/path/to/your/script"<br />
</nowiki>}}<br />
<br />
=== List attributes of a device ===<br />
<br />
To get a list of all of the attributes of a device you can use to write rules, run this command:<br />
<br />
# udevadm info -a -n [device name]<br />
<br />
Replace {{ic|[device name]}} with the device present in the system, such as {{ic|/dev/sda}} or {{ic|/dev/ttyUSB0}}.<br />
<br />
If you do not know the device name you can also list all attributes of a specific system path:<br />
<br />
# udevadm info -a -p /sys/class/backlight/acpi_video0<br />
<br />
=== Testing rules before loading ===<br />
<br />
# udevadm test $(udevadm info -q path -n [device name]) 2>&1<br />
<br />
This will not perform all actions in your new rules but it will however process symlink rules on existing devices which might come in handy if you are unable to load them otherwise. You can also directly provide the path to the device you want to test the udev rule for:<br />
<br />
# udevadm test /sys/class/backlight/acpi_video0/<br />
<br />
=== Loading new rules ===<br />
<br />
Udev automatically detects changes to rules files, so changes take effect immediately without requiring udev to be restarted. However, the rules are not re-triggered automatically on already existing devices. Hot-pluggable devices, such as USB devices, will probably have to be reconnected for the new rules to take effect, or at least unloading and reloading the ohci-hcd and ehci-hcd kernel modules and thereby reloading all USB drivers.<br />
<br />
If rules fail to reload automatically<br />
<br />
# udevadm control --reload<br />
<br />
To manually force udev to trigger your rules<br />
<br />
# udevadm trigger<br />
<br />
== Udisks ==<br />
<br />
See [[Udisks]].<br />
<br />
== Tips and tricks ==<br />
<br />
=== Accessing firmware programmers and USB virtual comm devices ===<br />
<br />
{{Accuracy|Making a device world-writable is not secure.}}<br />
{{Style|One example is enough, others can surely be found with {{ic|lsusb}}.}}<br />
<br />
The following ruleset will allow normal users (within the "users" group) the ability to access the [http://www.ladyada.net/make/usbtinyisp/ USBtinyISP] USB programmer for AVR microcontrollers and a generic (SiLabs [http://www.silabs.com/products/interface/usbtouart CP2102]) USB to UART adapter, the [http://www.atmel.com/tools/AVRDRAGON.aspx?tab=overview Atmel AVR Dragon] programmer, and the [http://www.atmel.com/tools/AVRISPMKII.aspx Atmel AVR ISP mkII]. Adjust the permissions accordingly. Verified as of 31-10-2012.<br />
<br />
{{hc|/etc/udev/rules.d/50-embedded_devices.rules|2=<nowiki><br />
# USBtinyISP Programmer rules<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"<br />
<br />
# USBasp Programmer rules http://www.fischl.de/usbasp/<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="users", MODE="0666"<br />
<br />
# Mdfly.com Generic (SiLabs CP2102) 3.3v/5v USB VComm adapter<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", GROUP="users", MODE="0666"<br />
<br />
#Atmel AVR Dragon (dragon_isp) rules<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2107", GROUP="users", MODE="0666"<br />
<br />
#Atmel AVR JTAGICEMKII rules<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2103", GROUP="users", MODE="0666"<br />
<br />
#Atmel Corp. AVR ISP mkII<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2104", GROUP="users", MODE="0666"<br />
<br />
#Atmel Copr. JTAGICE3<br />
SUBSYSTEM=="usb", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="2140", GROUP="users", MODE="0666"<br />
</nowiki>}}<br />
<br />
=== Execute on USB insert ===<br />
<br />
See the [[Execute on USB insert]] article or the [http://igurublog.wordpress.com/downloads/script-devmon/ devmon wrapper script].<br />
<br />
=== Execute on VGA cable plug in ===<br />
<br />
Create the rule {{ic|/etc/udev/rules.d/95-monitor-hotplug.rules}} with the following content to launch {{Pkg|arandr}} on plug in of a VGA monitor cable:<br />
<br />
KERNEL=="card0", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/''username''/.Xauthority", RUN+="/usr/bin/arandr"<br />
<br />
Some display managers store the .Xauthority outside the user home directory. You will need to update the ENV{XAUTHORITY} accordingly. As an example [[GDM|GNOME Display Manager looks as follows:]]<br />
<br />
# env | grep XAUTHORITY<br />
XAUTHORITY=/run/user/1000/gdm/Xauthority<br />
<br />
=== Detect new eSATA drives ===<br />
<br />
If your eSATA drive is not detected when you plug it in, there are a few things you can try. You can reboot with the eSATA plugged in. Or you could try<br />
<br />
# echo 0 0 0 | tee /sys/class/scsi_host/host*/scan<br />
<br />
Or you could install {{AUR|scsiadd}} (from the AUR) and try<br />
<br />
# scsiadd -s<br />
<br />
Hopefully, your drive is now in {{ic|/dev}}. If it is not, you could try the above commands while running<br />
<br />
# udevadm monitor<br />
<br />
to see if anything is actually happening.<br />
<br />
=== Mark internal SATA ports as eSATA ===<br />
<br />
If you connected a eSATA bay or an other eSATA adapter the system will still recognize this disk as an internal SATA drive. [[GNOME]] and [[KDE]] will ask you for your root password all the time. The following rule will mark the specified SATA-Port as an external eSATA-Port. With that, a normal GNOME user can connect their eSATA drives to that port like a USB drive, without any root password and so on.<br />
<br />
{{hc|/etc/udev/rules.d/10-esata.rules|2=<nowiki><br />
DEVPATH=="/devices/pci0000:00/0000:00:1f.2/host4/*", ENV{UDISKS_SYSTEM}="0"<br />
</nowiki>}}<br />
<br />
{{Note|The {{ic|DEVPATH}} can be found after connection the eSATA drive with the following commands (replace {{ic|sdb}} accordingly):<br />
<br />
# udevadm info -q path -n /dev/sdb<br />
/devices/pci0000:00/0000:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdb<br />
<br />
# find /sys/devices/ -name sdb<br />
/sys/devices/pci0000:00/0000:00:1f.2/host4/target4:0:0/4:0:0:0/block/sdb<br />
}}<br />
<br />
=== Setting static device names ===<br />
<br />
Because udev loads all modules asynchronously, they are initialized in a different order. This can result in devices randomly switching names. A udev rule can be added to use static device names.<br />
<br />
See also [[Persistent block device naming]] for block devices and [[Network configuration#Device names]] for network devices.<br />
<br />
==== Video devices ====<br />
<br />
For setting up the webcam in the first place, refer to [[Webcam setup#Webcam configuration|Webcam configuration]].<br />
<br />
Using multiple webcams, useful for example with {{pkg|motion}} (software motion detector which grabs images from video4linux devices and/or from webcams), will assign video devices as /dev/video0..n randomly on boot. The recommended solution is to create symlinks using an ''udev'' rule (as in the example in [[#Writing udev rules]]):<br />
<br />
{{hc|/etc/udev/rules.d/83-webcam.rules|<nowiki><br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="05a9", ATTRS{idProduct}=="4519", SYMLINK+="video-cam1"<br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="08f6", SYMLINK+="video-cam2"<br />
KERNEL=="video[0-9]*", SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="0840", SYMLINK+="video-cam3"<br />
</nowiki>}}<br />
<br />
{{Note|Using names other than {{ic|/dev/video*}} will break preloading of {{ic|v4l1compat.so}} and perhaps {{ic|v4l2convert.so}}}}<br />
<br />
==== Printers ====<br />
<br />
If you use multiple printers, {{ic|/dev/lp[0-9]}} devices will be assigned randomly on boot, which will break e.g. [[CUPS]] configuration. <br />
<br />
You can create following rule, which will create symlinks under {{ic|/dev/lp/by-id}} and {{ic|/dev/lp/by-path}}, similar to [[Persistent block device naming]] scheme:<br />
<br />
{{hc|/etc/udev/rules.d/60-persistent-printer.rules|<nowiki><br />
ACTION=="remove", GOTO="persistent_printer_end"<br />
<br />
# This should not be necessary<br />
#KERNEL!="lp*", GOTO="persistent_printer_end"<br />
<br />
SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id"<br />
ENV{ID_TYPE}!="printer", GOTO="persistent_printer_end"<br />
<br />
ENV{ID_SERIAL}=="?*", SYMLINK+="lp/by-id/$env{ID_BUS}-$env{ID_SERIAL}"<br />
<br />
IMPORT{builtin}="path_id"<br />
ENV{ID_PATH}=="?*", SYMLINK+="lp/by-path/$env{ID_PATH}"<br />
<br />
LABEL="persistent_printer_end"<br />
</nowiki>}}<br />
<br />
==== USB flash device ====<br />
<br />
USB flash devices usually contain partitions, and partition labels are one way to have a static naming for a device. Another way is to create a udev rule for it. <br />
<br />
Get the serial number and USB ids from the USB flash drive (if you use multiple of the same make, you might have to check the serial is indeed unique):<br />
lsusb -v | grep -A 5 Vendor<br />
<br />
Create a udev rule for it by adding the following to a file in {{ic|/etc/udev/rules.d/}}, such as {{ic|8-usbstick.rules}}:<br />
KERNEL=="sd*", ATTRS{serial}=="$SERIAL", ATTRS{idVendor}=="$VENDOR", ATTRS{idProduct}=="$PRODUCT" SYMLINK+="$SYMLINK%n"<br />
<br />
Replace {{ic|$SERIAL}}, {{ic|$VENDOR}}, {{ic|$PRODUCT}} from above output accordingly and {{ic|$SYMLINK}} with the desired name. {{ic|%n}} will expand to the partition number. For example, if the device has two partitions, two symlinks will be created. You do not need to go with the 'serial' attribute. If you have a custom rule of your own, you can put it in as well (e.g. using the vendor name).<br />
<br />
Rescan sysfs:<br />
udevadm trigger<br />
Now check the contents of {{ic|/dev}}:<br />
ls /dev<br />
It should show the device with the desired name.<br />
<br />
=== Waking from suspend with USB device ===<br />
<br />
First, find vendor and product ID of your device, for example<br />
<br />
{{hc|<nowiki># lsusb | grep Logitech</nowiki>|Bus 007 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver}}<br />
<br />
Now change the {{ic|power/wakeup}} attribute of the device and the USB controller it is connected to, which is in this case {{ic|driver/usb7/power/wakeup}}. Use the following rule:<br />
<br />
{{hc|/etc/udev/rules.d/50-wake-on-device.rules|<nowiki><br />
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ATTR{power/wakeup}="enabled", ATTR{driver/usb7/power/wakeup}="enabled"<br />
</nowiki>}}<br />
<br />
{{Note|Also make sure the USB controller is enabled in {{ic|/proc/acpi/wakeup}}.}}<br />
<br />
=== Triggering events ===<br />
<br />
{{Merge|#Testing rules before loading|similar trick}}<br />
<br />
It can be useful to trigger various udev events. For example, you might want to simulate a USB device disconnect on a remote machine. In such cases, use {{ic|udevadm trigger}}:<br />
<br />
# udevadm trigger -v -t subsystems -c remove -s usb -a "idVendor=abcd"<br />
<br />
This command will trigger a USB remove event on all USB devices with vendor ID {{ic|abcd}}.<br />
<br />
== Troubleshooting ==<br />
<br />
=== Blacklisting modules ===<br />
<br />
In rare cases, udev can make mistakes and load the wrong modules. To prevent it from doing this, you can blacklist modules. Once blacklisted, udev will never load that module. See [[blacklisting]]. Not at boot-time ''or'' later on when a hotplug event is received (eg, you plug in your USB flash drive).<br />
<br />
=== Debug output ===<br />
<br />
To get hardware debug info, use the [[kernel parameter]] {{ic|1=udev.log-priority=debug}}. Alternatively you can set<br />
<br />
{{hc|/etc/udev/udev.conf|2=udev_log="debug"}}<br />
<br />
This option can also be compiled into your initramfs by adding the config file to your {{ic|FILES}} array<br />
<br />
{{hc|/etc/mkinitcpio.conf|2=FILES="... /etc/udev/udev.conf"}}<br />
<br />
and then rebuilding the initramfs with<br />
<br />
# mkinitcpio -p linux<br />
<br />
=== udevd hangs at boot ===<br />
<br />
After migrating to LDAP or updating an LDAP-backed system udevd can hang at boot at the message "Starting UDev Daemon". This is usually caused by udevd trying to look up a name from LDAP but failing, because the network is not up yet. The solution is to ensure that all system group names are present locally.<br />
<br />
Extract the group names referenced in udev rules and the group names actually present on the system:<br />
<br />
# fgrep -r GROUP /etc/udev/rules.d/ /usr/lib/udev/rules.d | perl -nle '/GROUP\s*=\s*"(.*?)"/ && print $1;' | sort | uniq > udev_groups<br />
# cut -f1 -d: /etc/gshadow /etc/group | sort | uniq > present_groups<br />
<br />
To see the differences, do a side-by-side diff:<br />
<br />
# diff -y present_groups udev_groups<br />
...<br />
network <<br />
nobody <<br />
ntp <<br />
optical optical<br />
power | pcscd<br />
rfkill <<br />
root root<br />
scanner scanner<br />
smmsp <<br />
storage storage<br />
...<br />
<br />
In this case, the {{ic|pcscd}} group is for some reason not present in the system. [[Users and groups#Group management|Add the missing groups]]. Also, make sure that local resources are looked up before resorting to LDAP. {{ic|/etc/nsswitch.conf}} should contain the following line:<br />
<br />
group: files ldap<br />
<br />
=== BusLogic devices can be broken and will cause a freeze during startup ===<br />
<br />
This is a kernel bug and no fix has been provided yet.<br />
<br />
=== Some devices, that should be treated as removable, are not ===<br />
<br />
You need to create a custom udev rule for that particular device. To get definitive information of the device you can use either {{ic|ID_SERIAL}} or {{ic|ID_SERIAL_SHORT}} (remember to change {{ic|/dev/sdb}} if needed):<br />
<br />
$ udevadm info /dev/sdb | grep ID_SERIAL<br />
<br />
Then we create a rule in {{ic|/etc/udev/rules.d/}} and set variables for either udisks or udisks2.<br />
<br />
For udisks, set {{ic|1=UDISKS_SYSTEM_INTERNAL="0"}}, which will mark the device as "removable" and thus "eligible for automounting". See [http://udisks.freedesktop.org/docs/1.0.5/udisks.7.html udisks(7)] for details.<br />
<br />
{{hc|/etc/udev/rules.d/50-external-myhomedisk.rules|2=<br />
ENV{ID_SERIAL_SHORT}=="''serial_number''", ENV{UDISKS_SYSTEM_INTERNAL}="0"<br />
}}<br />
<br />
For udisks2, set {{ic|1=UDISKS_AUTO="1"}} to mark the device for automounting and {{ic|1=UDISKS_SYSTEM="0"}} to mark the device as "removable". See [http://udisks.freedesktop.org/docs/1.93.0/udisks.8.html udisks(8)] for details.<br />
<br />
{{hc|/etc/udev/rules.d/99-removable.rules|2=<br />
ENV{ID_SERIAL_SHORT}=="''serial_number''", ENV{UDISKS_AUTO}="1", ENV{UDISKS_SYSTEM}="0"<br />
}}<br />
<br />
Remember to reload udev rules with {{ic|udevadm control --reload}}. Next time you plug your device in, it will be treated as an external drive.<br />
<br />
=== Sound problems with some modules not loaded automatically ===<br />
<br />
Some users have traced this problem to old entries in {{ic|/etc/modprobe.d/sound.conf}}. Try cleaning that file out and trying again.<br />
<br />
{{Note|Since {{ic|1=udev>=171}}, the OSS emulation modules ({{ic|snd_seq_oss}}, {{ic|snd_pcm_oss}}, {{ic|snd_mixer_oss}}) are not automatically loaded by default.}}<br />
<br />
=== IDE CD/DVD-drive support ===<br />
<br />
Starting with version 170, udev does not support CD-ROM/DVD-ROM drives that are loaded as traditional IDE drives with the {{ic|ide_cd_mod}} module and show up as {{ic|/dev/hd*}}. The drive remains usable for tools which access the hardware directly, like ''cdparanoia'', but is invisible for higher userspace programs, like KDE.<br />
<br />
A cause for the loading of the ide_cd_mod module prior to others, like sr_mod, could be e.g. that you have for some reason the module piix loaded with your [[initramfs]]. In that case you can just replace it with ata_piix in your {{ic|/etc/mkinitcpio.conf}}.<br />
<br />
=== Optical drives have group ID set to "disk" ===<br />
<br />
If the group ID of your optical drive is set to {{ic|disk}} and you want to have it set to {{ic|optical}}, you have to create a custom udev rule:<br />
<br />
{{hc|/etc/udev/rules.d|2=<nowiki><br />
# permissions for IDE CD devices<br />
SUBSYSTEMS=="ide", KERNEL=="hd[a-z]", ATTR{removable}=="1", ATTRS{media}=="cdrom*", GROUP="optical"<br />
<br />
# permissions for SCSI CD devices<br />
SUBSYSTEMS=="scsi", KERNEL=="s[rg][0-9]*", ATTRS{type}=="5", GROUP="optical"</nowiki>}}<br />
<br />
== See also ==<br />
<br />
* [https://www.kernel.org/pub/linux/utils/kernel/hotplug/udev/udev.html udev home page]<br />
* [https://www.linux.com/news/hardware/peripherals/180950-udev An Introduction to udev]<br />
* [http://vger.kernel.org/vger-lists.html#linux-hotplug udev mailing list information]<br />
* [http://jasonwryan.com/blog/2014/01/20/udev/ Scripting with udev]<br />
* [http://www.reactivated.net/writing_udev_rules.html Writing udev rules]</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434733Lenovo IdeaPad Yoga 9002016-05-12T12:42:39Z<p>Netadmin: Noting bug has been fixed for network manager. Striking bug details for future removal.</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{G|Working}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Card Reader ===<br />
<br />
Initial testing shows the card read working fine out of the box. There are a few errors on boot that need more research.<br />
<br />
Boot message:<br />
<br />
{{bc|kernel: mmc0: Unknown controller version (3). You may experience problems.}}<br />
<br />
Insert of card message:<br />
<br />
{{bc|kernel: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock<br />
kernel: mmc0: tuning execution failed<br />
kernel: mmc0: ddr50 tuning failed}}<br />
<br />
=== External Monitor ===<br />
<br />
{{note|Updating to the latest {{Pkg|xf86-video-intel}} and {{Pkg|linux}} kernel has fixed some of the external display issues with VGA and HDMI dongles.}}<br />
<br />
Several issues occur when trying to display on an external monitor. This laptop only has a display port over USBC-C, which requires dongles to connect to most monitors. Testing to a monitor with a display port connection has yielded the best result. Testing with HDMI and VGA dongles have revealed several issues. Often xrandr does not show a display connected. Rebooting with the monitor attached does not fix the issue. Sometimes running xrandr several times will show a connection.<br />
<br />
<s>Still researching the issue but may be related to this [https://bugs.freedesktop.org/show_bug.cgi?id=93578 bug]. </s><br />
<br />
If you try to force xrandr to display with the following:<br />
<br />
{{bc|xrandr --output eDP1 --auto --output DP1 --auto --right-of eDP1}}<br />
<br />
Sometimes you will see the following kernel message:<br />
<br />
{{bc| kernel: ------------[ cut here ]------------<br />
kernel: WARNING: CPU: 1 PID: 1253 at drivers/gpu/drm/i915/intel_pm.c:3553 skl_update_other_pipe_wm+0x177/0x180 [i915]()<br />
kernel: WARN_ON(!wm_changed)<br />
kernel: Modules linked in:<br />
kernel: ccm snd_hda_codec_hdmi deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_<br />
kernel: hid_rmi ax88179_178a usbnet mii iwlmvm mac80211 snd_soc_skl snd_soc_skl_ipc i2c_designware_platform i2c_designwar<br />
kernel: fan i2c_hid thermal wmi battery bluetooth intel_hid int3400_thermal rfkill pinctrl_sunrisepoint pinctrl_intel int<br />
kernel: <br />
kernel: CPU: 1 PID: 1253 Comm: Xorg Tainted: G U W O 4.5.2-1-ARCH #1<br />
kernel: Hardware name: LENOVO 80MK/VIUU4, BIOS C6CN35WW 12/17/2015<br />
kernel: 0000000000000286 000000000f1007b6 ffff88044bf4f918 ffffffff812dad91<br />
kernel: ffff88044bf4f960 ffffffffa01b8d20 ffff88044bf4f950 ffffffff81078e52<br />
kernel: ffff8804604ec000 ffff88044bf4f9dc ffff88045d629bd4 ffff8804604eb000<br />
kernel: Call Trace:<br />
kernel: [<ffffffff812dad91>] dump_stack+0x63/0x82<br />
kernel: [<ffffffff81078e52>] warn_slowpath_common+0x82/0xc0<br />
kernel: [<ffffffff81078eec>] warn_slowpath_fmt+0x5c/0x80<br />
kernel: [<ffffffffa00e77c7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
kernel: [<ffffffffa00e795e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
kernel: [<ffffffffa01725ff>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
kernel: [<ffffffffa00eb06e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
kernel: [<ffffffffa0155e61>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
kernel: [<ffffffffa0151777>] intel_atomic_commit+0x737/0x1870 [i915]<br />
kernel: [<ffffffffa0020581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
kernel: [<ffffffffa0020a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
kernel: [<ffffffffa00908b6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
kernel: [<ffffffffa000f1b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
kernel: [<ffffffffa00142c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
kernel: [<ffffffffa0005892>] drm_ioctl+0x152/0x540 [drm]<br />
kernel: [<ffffffffa0013ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
kernel: [<ffffffff811ece7c>] ? __vfs_write+0xcc/0x100<br />
kernel: [<ffffffff811ffdd1>] do_vfs_ioctl+0xa1/0x5b0<br />
kernel: [<ffffffff81084df1>] ? __set_task_blocked+0x41/0xa0<br />
kernel: [<ffffffff8120a1f7>] ? __fget+0x77/0xb0<br />
kernel: [<ffffffff81200359>] SyS_ioctl+0x79/0x90<br />
kernel: [<ffffffff8108793e>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
kernel: [<ffffffff815b0b6e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
kernel: ---[ end trace 4d86447ef15dd94e ]---<br />
}}<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
{{note|This bug has been resolved with version 1.2.2-1 of [[NetworkManager]].}}<br />
<br />
<s><br />
The current [[NetworkManager]] has a [https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 bug] that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. You can read about the issue in this [https://bbs.archlinux.org/viewtopic.php?id=210868&p=2 thread]<br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package which is located in [[Arch_Linux_Archive]]<br />
</s><br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the {{AUR|iio-sensor-proxy}} package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434664Lenovo IdeaPad Yoga 9002016-05-11T12:49:27Z<p>Netadmin: Added external monitor fixes and some cleanup</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{G|Working}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Card Reader ===<br />
<br />
Initial testing shows the card read working fine out of the box. There are a few errors on boot that need more research.<br />
<br />
Boot message:<br />
<br />
{{bc|kernel: mmc0: Unknown controller version (3). You may experience problems.}}<br />
<br />
Insert of card message:<br />
<br />
{{bc|kernel: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock<br />
kernel: mmc0: tuning execution failed<br />
kernel: mmc0: ddr50 tuning failed}}<br />
<br />
=== External Monitor ===<br />
<br />
{{note|Updating to the latest {{Pkg|xf86-video-intel}} and {{Pkg|linux}} kernel has fixed some of the external display issues with VGA and HDMI dongles.}}<br />
<br />
Several issues occur when trying to display on an external monitor. This laptop only has a display port over USBC-C, which requires dongles to connect to most monitors. Testing to a monitor with a display port connection has yielded the best result. Testing with HDMI and VGA dongles have revealed several issues. Often xrandr does not show a display connected. Rebooting with the monitor attached does not fix the issue. Sometimes running xrandr several times will show a connection.<br />
<br />
<s>Still researching the issue but may be related to this [https://bugs.freedesktop.org/show_bug.cgi?id=93578 bug]. </s><br />
<br />
If you try to force xrandr to display with the following:<br />
<br />
{{bc|xrandr --output eDP1 --auto --output DP1 --auto --right-of eDP1}}<br />
<br />
Sometimes you will see the following kernel message:<br />
<br />
{{bc| kernel: ------------[ cut here ]------------<br />
kernel: WARNING: CPU: 1 PID: 1253 at drivers/gpu/drm/i915/intel_pm.c:3553 skl_update_other_pipe_wm+0x177/0x180 [i915]()<br />
kernel: WARN_ON(!wm_changed)<br />
kernel: Modules linked in:<br />
kernel: ccm snd_hda_codec_hdmi deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_<br />
kernel: hid_rmi ax88179_178a usbnet mii iwlmvm mac80211 snd_soc_skl snd_soc_skl_ipc i2c_designware_platform i2c_designwar<br />
kernel: fan i2c_hid thermal wmi battery bluetooth intel_hid int3400_thermal rfkill pinctrl_sunrisepoint pinctrl_intel int<br />
kernel: <br />
kernel: CPU: 1 PID: 1253 Comm: Xorg Tainted: G U W O 4.5.2-1-ARCH #1<br />
kernel: Hardware name: LENOVO 80MK/VIUU4, BIOS C6CN35WW 12/17/2015<br />
kernel: 0000000000000286 000000000f1007b6 ffff88044bf4f918 ffffffff812dad91<br />
kernel: ffff88044bf4f960 ffffffffa01b8d20 ffff88044bf4f950 ffffffff81078e52<br />
kernel: ffff8804604ec000 ffff88044bf4f9dc ffff88045d629bd4 ffff8804604eb000<br />
kernel: Call Trace:<br />
kernel: [<ffffffff812dad91>] dump_stack+0x63/0x82<br />
kernel: [<ffffffff81078e52>] warn_slowpath_common+0x82/0xc0<br />
kernel: [<ffffffff81078eec>] warn_slowpath_fmt+0x5c/0x80<br />
kernel: [<ffffffffa00e77c7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
kernel: [<ffffffffa00e795e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
kernel: [<ffffffffa01725ff>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
kernel: [<ffffffffa00eb06e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
kernel: [<ffffffffa0155e61>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
kernel: [<ffffffffa0151777>] intel_atomic_commit+0x737/0x1870 [i915]<br />
kernel: [<ffffffffa0020581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
kernel: [<ffffffffa0020a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
kernel: [<ffffffffa00908b6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
kernel: [<ffffffffa000f1b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
kernel: [<ffffffffa00142c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
kernel: [<ffffffffa0005892>] drm_ioctl+0x152/0x540 [drm]<br />
kernel: [<ffffffffa0013ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
kernel: [<ffffffff811ece7c>] ? __vfs_write+0xcc/0x100<br />
kernel: [<ffffffff811ffdd1>] do_vfs_ioctl+0xa1/0x5b0<br />
kernel: [<ffffffff81084df1>] ? __set_task_blocked+0x41/0xa0<br />
kernel: [<ffffffff8120a1f7>] ? __fget+0x77/0xb0<br />
kernel: [<ffffffff81200359>] SyS_ioctl+0x79/0x90<br />
kernel: [<ffffffff8108793e>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
kernel: [<ffffffff815b0b6e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
kernel: ---[ end trace 4d86447ef15dd94e ]---<br />
}}<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a [https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 bug] that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. You can read about the issue in this [https://bbs.archlinux.org/viewtopic.php?id=210868&p=2 thread]<br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the {{AUR|iio-sensor-proxy}} package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Talk:Udev&diff=434536Talk:Udev2016-05-10T16:23:21Z<p>Netadmin: Noticed udev hotplug example assumes xauthority is in home directory, but display mangers may differ.</p>
<hr />
<div>== usbtiny extra udev rule? ==<br />
In the udev rules for usbtiny, there are 2 rules listed. Howver, adding the second one to my udev rules resulted in me not an "rc=-1" communication error when I tried to use my usbtiny. When I commented out this rule:<br />
"SBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"<br />
everything worked fine. Not sure what the root of the issue is, but this rule makes the usbtiny programer unusable. -- [[User:Ssalenik|Ssalenik]] ([[User talk:Ssalenik|talk]]) 04:09, 6 March 2012<br />
<br />
== About udev rules ==<br />
udevadm info -a -n [device name]<br />
and<br />
udevadm info -a -p $(udevadm info -q path -n [device name])<br />
gives the same output but the latter is recommended by some [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)<br />
<br />
== Use of 'uaccess' instead of GROUP and MODE? ==<br />
<br />
Bug [https://bugs.archlinux.org/task/35602 openobex - relies on non-existing group plugdev, conflict with systemd] made me rethink the rules I have been using for [[Logitech_Unifying_Receiver]].<br />
<br />
Currently, the following rule is taught to the user:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"<br />
What about changing it to:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess"<br />
<br />
As a developer note, Ubuntu versions before 13.04 Raring needs {{ic|<nowiki>TAG+="udev-acl"</nowiki>}} instead of uaccess. For compatibility with modern and legacy systems:<br />
<br />
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess", TAG+="udev-acl"<br />
<br />
References:<br />
* http://cgit.freedesktop.org/systemd/systemd/tree/src/login/70-uaccess.rules<br />
[[User:Lekensteyn|Lekensteyn]] ([[User talk:Lekensteyn|talk]]) 10:16, 6 June 2013 (UTC)<br />
<br />
== Printers ==<br />
<br />
[[Udev#Printers]]:<br />
<br />
If you use multiple printers, /dev/lp[0-9] devices will be assigned randomly on boot, which will break e.g. CUPS configuration.<br />
<br />
I don't use multiple printers, but doesn't {{Pkg|system-config-printer}} handle this automatically? If so, a tip could be added. --[[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:38, 28 June 2014 (UTC)<br />
<br />
:It might, unfortunately its {{Pkg|gtk3}} dependency discouraged me from even trying... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:01, 28 June 2014 (UTC)<br />
<br />
== Additional detail on "Execute on VGA cable plug" ==<br />
<br />
Not sure if it belongs in this wiki, but worth noting in the hot plug example that the Xauthority may be located elsewhere based on display manager. <br />
<br />
This is the example:<br />
<br />
KERNEL=="card0", SUBSYSTEM=="drm", ENV{DISPLAY}=":0", ENV{XAUTHORITY}="/home/username/.Xauthority", RUN+="/usr/bin/arandr"<br />
<br />
If you have GDM and you check the Xauthority location as follows:<br />
<br />
$ env | grep XAUTHORITY<br />
XAUTHORITY=/run/user/1000/gdm/Xauthority<br />
<br />
You will see the file is not in a home directory and you need to tweak the ENV{XAUTHORITY} accordingly.<br />
<br />
Not sure if this bit of information is useful in the wiki or consider overly specific for this use case. [[User:Netadmin|Netadmin]] ([[User talk:Netadmin|talk]]) 16:22, 10 May 2016 (UTC)</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434442Lenovo IdeaPad Yoga 9002016-05-09T20:18:23Z<p>Netadmin: Added details of external monitor problems</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{G|Working}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Card Reader ===<br />
<br />
Initial testing shows the card read working fine out of the box. There are a few errors on boot that need more research.<br />
<br />
Boot message:<br />
<br />
{{bc|kernel: mmc0: Unknown controller version (3). You may experience problems.}}<br />
<br />
Insert of card message:<br />
<br />
{{bc|kernel: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock<br />
kernel: mmc0: tuning execution failed<br />
kernel: mmc0: ddr50 tuning failed}}<br />
<br />
=== External Monitor ===<br />
<br />
Several issues occur when trying to display on an external monitor. This laptop only has a display port over USBC-C, which requires dongles to connect to most monitors. Testing to a monitor with a display port connection has yielded the best result. Testing with HDMI and VGA dongles have revealed several issues. Often xrandr does not show a display connected. Rebooting with the monitor attached does not fix the issue. Sometimes running xrandr several times will show a connection.<br />
<br />
Still researching the issue but may be related to this [https://bugs.freedesktop.org/show_bug.cgi?id=93578 bug].<br />
<br />
If you try to force xrandr to display with the following:<br />
<br />
{{bc|xrandr --output eDP1 --auto --output DP1 --auto --right-of eDP1}}<br />
<br />
Sometimes you will see the following kernel message:<br />
<br />
{{bc| kernel: ------------[ cut here ]------------<br />
kernel: WARNING: CPU: 1 PID: 1253 at drivers/gpu/drm/i915/intel_pm.c:3553 skl_update_other_pipe_wm+0x177/0x180 [i915]()<br />
kernel: WARN_ON(!wm_changed)<br />
kernel: Modules linked in:<br />
kernel: ccm snd_hda_codec_hdmi deflate ctr twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_<br />
kernel: hid_rmi ax88179_178a usbnet mii iwlmvm mac80211 snd_soc_skl snd_soc_skl_ipc i2c_designware_platform i2c_designwar<br />
kernel: fan i2c_hid thermal wmi battery bluetooth intel_hid int3400_thermal rfkill pinctrl_sunrisepoint pinctrl_intel int<br />
kernel: <br />
kernel: CPU: 1 PID: 1253 Comm: Xorg Tainted: G U W O 4.5.2-1-ARCH #1<br />
kernel: Hardware name: LENOVO 80MK/VIUU4, BIOS C6CN35WW 12/17/2015<br />
kernel: 0000000000000286 000000000f1007b6 ffff88044bf4f918 ffffffff812dad91<br />
kernel: ffff88044bf4f960 ffffffffa01b8d20 ffff88044bf4f950 ffffffff81078e52<br />
kernel: ffff8804604ec000 ffff88044bf4f9dc ffff88045d629bd4 ffff8804604eb000<br />
kernel: Call Trace:<br />
kernel: [<ffffffff812dad91>] dump_stack+0x63/0x82<br />
kernel: [<ffffffff81078e52>] warn_slowpath_common+0x82/0xc0<br />
kernel: [<ffffffff81078eec>] warn_slowpath_fmt+0x5c/0x80<br />
kernel: [<ffffffffa00e77c7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
kernel: [<ffffffffa00e795e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
kernel: [<ffffffffa01725ff>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
kernel: [<ffffffffa00eb06e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
kernel: [<ffffffffa0155e61>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
kernel: [<ffffffffa0151777>] intel_atomic_commit+0x737/0x1870 [i915]<br />
kernel: [<ffffffffa0020581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
kernel: [<ffffffffa0020a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
kernel: [<ffffffffa00908b6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
kernel: [<ffffffffa000f1b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
kernel: [<ffffffffa00142c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
kernel: [<ffffffffa0005892>] drm_ioctl+0x152/0x540 [drm]<br />
kernel: [<ffffffffa0013ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
kernel: [<ffffffff811ece7c>] ? __vfs_write+0xcc/0x100<br />
kernel: [<ffffffff811ffdd1>] do_vfs_ioctl+0xa1/0x5b0<br />
kernel: [<ffffffff81084df1>] ? __set_task_blocked+0x41/0xa0<br />
kernel: [<ffffffff8120a1f7>] ? __fget+0x77/0xb0<br />
kernel: [<ffffffff81200359>] SyS_ioctl+0x79/0x90<br />
kernel: [<ffffffff8108793e>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
kernel: [<ffffffff815b0b6e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
kernel: ---[ end trace 4d86447ef15dd94e ]---<br />
}}<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a [https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 bug] that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. You can read about the issue in this [https://bbs.archlinux.org/viewtopic.php?id=210868&p=2 thread]<br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434352Lenovo IdeaPad Yoga 9002016-05-08T20:06:28Z<p>Netadmin: Added details of testing card reader</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{G|Working}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Card Reader ===<br />
<br />
Initial testing shows the card read working fine out of the box. There are a few errors on boot that need more research.<br />
<br />
Boot message:<br />
<br />
{{bc|kernel: mmc0: Unknown controller version (3). You may experience problems.}}<br />
<br />
Insert of card message:<br />
<br />
{{bc|kernel: sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock<br />
kernel: mmc0: tuning execution failed<br />
kernel: mmc0: ddr50 tuning failed}}<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a [https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 bug] that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. You can read about the issue in this [https://bbs.archlinux.org/viewtopic.php?id=210868&p=2 thread]<br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434234Lenovo IdeaPad Yoga 9002016-05-07T13:40:48Z<p>Netadmin: Added back details of network-manager bug and added link to thread and bug</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a [https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=dd4d8b24da29abfc786ce0b3030c74559b93d034 bug] that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. You can read about the issue in this [https://bbs.archlinux.org/viewtopic.php?id=210868&p=2 thread]<br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434077Lenovo IdeaPad Yoga 9002016-05-06T12:38:03Z<p>Netadmin: Added note on side issue with mapping trackpad F6 key</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Toggle Trackpad ===<br />
<br />
{{note| This fix has an unintended consequence that needs more research. The mapping will work and it disables the trackpad when you go into tablet mode. The issue is the trackpad will be automatically disabled if you close the laptop lid and re-open it. This requires you to hit F6 to re-enable it. Not mapping this key will leave the trackpad enabled in tablet mode, but otherwise all other operations are normal.}}<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434046Lenovo IdeaPad Yoga 9002016-05-06T03:09:42Z<p>Netadmin: Updated camera status</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{G|Working}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Toggle Trackpad ===<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=434045Lenovo IdeaPad Yoga 9002016-05-06T02:37:22Z<p>Netadmin: Add UDEV comment for trackpad toggle</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note|<br />
* BIOS has a setting to flip the behavior of the FN key.<br />
* The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the ''Intel Virtual Technology'' option.<br />
<br />
=== HiDPI ===<br />
<br />
See [[HiDPI]].<br />
<br />
=== Sensors ===<br />
<br />
Install the {{AUR|iio-sensor-proxy}} to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Toggle Trackpad ===<br />
<br />
The trackpad key (F6) is not mapped correctly to toggle the trackpad. Using UDEV to [[Map_scancodes_to_keycodes]] will restore this function. This is a custom hwdb file to restore the feature.<br />
<br />
<pre><br />
# Lenovo YOGA 900-13ISK<br />
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrLenovoYOGA900*<br />
KEYBOARD_KEY_bf=f21 # Fn+F6 Disable Touchpad<br />
</pre><br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the {{AUR|iio-sensor-proxy}} package.</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433998Lenovo IdeaPad Yoga 9002016-05-05T18:59:52Z<p>Netadmin: Add status table for keyboard function keys</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Keyboard ===<br />
<br />
{{note| BIOS has a setting to flip the behavior of the FN key.}}<br />
<br />
{{note| The status below is based on Gnome}}<br />
<br />
{| class="wikitable"<br />
! Keys!! Function !! Status <br />
|-<br />
| {{ic|Fn+F1}} || Audio mute/unmute || Working<br />
|-<br />
| {{ic|Fn+F2}} || Audio volume down || Working<br />
|-<br />
| {{ic|Fn+F3}} || Audio volume up || Working<br />
|-<br />
| {{ic|Fn+F4}} || Close application || Working<br />
|-<br />
| {{ic|Fn+F5}} || Refresh page || Working<br />
|-<br />
| {{ic|Fn+F6}} || Disable Touchpad || Not Working<br />
|-<br />
| {{ic|Fn+F7}} || Airplane mode || Working<br />
|-<br />
| {{ic|Fn+F8}} || Display active apps || Not Working<br />
|-<br />
| {{ic|Fn+F9}} || Turn off LCD || Working<br />
|-<br />
| {{ic|Fn+F10}} || Toggle display || Working<br />
|-<br />
| {{ic|Fn+F11}} || Dim LCD backlight || Working<br />
|-<br />
| {{ic|Fn+F12}} || Brighten LCD backlight || Working<br />
|-<br />
| {{ic|Fn+Space}} || Toggle keyboard backlight || Working<br />
|}<br />
<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the "Intel Virtual Technology" option.<br />
=== Gnome ===<br />
Out of the box all the [[Gnome]] windows will be real small on this HiDPI screen.You will want to install the GNOME Tweak Tool ([https://www.archlinux.org/packages/extra/any/gnome-tweak-tool/ gnome-tweak-tool]) and set the HiDPI window scaling to 2.<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] pckage.<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433997Lenovo IdeaPad Yoga 9002016-05-05T18:50:23Z<p>Netadmin: Added configuration details for GNOME to support HiDPI scaling</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the "Intel Virtual Technology" option.<br />
=== Gnome ===<br />
Out of the box all the [[Gnome]] windows will be real small on this HiDPI screen.You will want to install the GNOME Tweak Tool ([https://www.archlinux.org/packages/extra/any/gnome-tweak-tool/ gnome-tweak-tool]) and set the HiDPI window scaling to 2.<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] pckage.<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433894Lenovo IdeaPad Yoga 9002016-05-04T20:29:12Z<p>Netadmin: Added details on KVM and upper cased BIOS</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== BIOS ===<br />
<br />
Lenovo does not currently offer a BIOS update ISO image. This means you can only upgrade the BIOS from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== KVM ===<br />
<br />
KVM can be enabled in the BIOS via the "Intel Virtual Technology" option.<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] pckage.<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433846Lenovo IdeaPad Yoga 9002016-05-04T12:29:06Z<p>Netadmin: Added note on light sensor bug</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== Bios ===<br />
<br />
Lenovo does not currently offer a bios update ISO image. This means you can only upgrade the bios from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] package.<br />
<br />
=== Light Sensor ===<br />
<br />
===== Bug =====<br />
<br />
When you first boot the light sensor for automatic screen brightness may not work. A bug currently requires you to suspend and resume the laptop before the light sensor will work using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] pckage.<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_Yoga_900&diff=433799Lenovo Yoga 9002016-05-04T02:24:32Z<p>Netadmin: Netadmin moved page Lenovo Yoga 900 to Lenovo IdeaPad Yoga 900: Move to page name that matches other Yoga laptops</p>
<hr />
<div>#REDIRECT [[Lenovo IdeaPad Yoga 900]]</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433798Lenovo IdeaPad Yoga 9002016-05-04T02:24:32Z<p>Netadmin: Netadmin moved page Lenovo Yoga 900 to Lenovo IdeaPad Yoga 900: Move to page name that matches other Yoga laptops</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== Bios ===<br />
<br />
Lenovo does not currently offer a bios update ISO image. This means you can only upgrade the bios from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy].<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433797Lenovo IdeaPad Yoga 9002016-05-04T02:22:26Z<p>Netadmin: </p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== Bios ===<br />
<br />
Lenovo does not currently offer a bios update ISO image. This means you can only upgrade the bios from Windows 10.<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy].<br />
<br />
== Tips and tricks ==</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433796Lenovo IdeaPad Yoga 9002016-05-04T01:49:13Z<p>Netadmin: Assign the Lenovo category to page</p>
<hr />
<div>[[Category:Lenovo]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy].<br />
<br />
== Tips and tricks ==<br />
<br />
=== Font Text Size ===</div>Netadminhttps://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_900&diff=433795Lenovo IdeaPad Yoga 9002016-05-04T01:47:09Z<p>Netadmin: Initial page for Lenovo Yoga 900. I will add other items as I get the laptop fully functional.</p>
<hr />
<div>[[Category:LENOVO]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Intel || {{G|Working}} || xf86-video-intel<br />
|-<br />
| Wireless || {{G|Working}} || iwlwifi<br />
|-<br />
| Audio || {{G|Working}} ||<br />
|-<br />
| Touchpad || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Touchscreen || {{G|Working}} || xf86-input-libinput<br />
|-<br />
| Camera || {{Y|Unknown}} || <br />
|-<br />
| Card Reader || {{Y|Unknown}} ||<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|}<br />
<br />
The [http://shop.lenovo.com/us/en/laptops/yoga/900-series/yoga-900-13/#tab-tech_specs Lenovo Yoga 900] is a 2 in 1 laptop with a QHD+ display.<br />
<br />
For a general overview of laptop-related articles and recommendations, see [[Laptop]]. <br />
<br />
== Installation ==<br />
<br />
=== Font Size===<br />
<br />
The console text is hard to read during install with this high resolution screen. You can temporarily use a default larger font like sun12x22.<br />
<br />
{{bc|setfont sun12x22}}<br />
<br />
Consider installing the [https://www.archlinux.org/packages/community/any/terminus-font/ Terminus] font package for access to even larger fonts and making it permanent with vconsole.conf ([[Fonts#Persistent_configuration]]).<br />
<br />
=== Wifi ===<br />
<br />
During install the wifi-menu may show no networks. This is caused by a soft-block. Using rfkill should fix the issue.<br />
<br />
{{bc|rfkill unblock all}}<br />
<br />
== Configuration ==<br />
<br />
=== Sensors ===<br />
Install the package [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy] to get the accelerometer and light sensor working<br />
<br />
== Troubleshooting ==<br />
<br />
=== Networking ===<br />
<br />
===== Bug =====<br />
<br />
The current [[NetworkManager]] has a bug that causes intermittent issues when the NetworkManager.service is set to enable via [[systemd]]. <br />
<br />
A simple stop/start will fix the issue for that session.<br />
<br />
{{bc|systemctl stop NetworkManager.service}}<br />
<br />
{{bc|systemctl start NetworkManager.service}}<br />
<br />
As a work around you can downgrade the NetworkManger package to 1.0.10-1 which is located in [[Arch_Linux_Archive]]<br />
<br />
=== Screen Rotation ===<br />
<br />
When you first boot the screen rotation may not work. A bug currently requires you to suspend and resume the laptop before the screen will rotate using the [https://aur.archlinux.org/packages/iio-sensor-proxy iio-sensor-proxy].<br />
<br />
== Tips and tricks ==<br />
<br />
=== Font Text Size ===</div>Netadmin