https://wiki.archlinux.org/api.php?action=feedcontributions&user=Latgarf&feedformat=atomArchWiki - User contributions [en]2024-03-28T16:40:28ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=EFI_system_partition&diff=636853EFI system partition2020-10-01T08:33:36Z<p>Latgarf: "start efistub-update.service", not "start efistub-update.path", right?</p>
<hr />
<div>[[Category:Boot process]]<br />
[[es:EFI system partition]]<br />
[[fr:ESP]]<br />
[[ja:EFI システムパーティション]]<br />
[[pt:EFI system partition]]<br />
[[ru:EFI system partition]]<br />
[[zh-hans:EFI system partition]]<br />
{{Related articles start}}<br />
{{Related|Unified Extensible Firmware Interface}}<br />
{{Related|Boot loader}}<br />
{{Related articles end}}<br />
The [[Wikipedia:EFI system partition|EFI system partition]] (also called ESP) is an OS independent partition that acts as the storage place for the EFI bootloaders, applications and drivers to be launched by the UEFI firmware. It is mandatory for UEFI boot. <br />
<br />
{{Move|Unified Extensible Firmware Interface#UEFI drivers|Drivers for non-FAT file systems are out of scope of this article.}}<br />
<br />
The UEFI specification mandates support for the FAT12, FAT16, and FAT32 file systems (see [https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf#G17.1019485 UEFI specification version 2.8, section 13.3.1.1]), but any conformant vendor can optionally add support for additional file systems; for example, the firmware in Apple [[Mac]]s supports the HFS+ file system.<br />
<br />
== Check for an existing partition ==<br />
<br />
If you are installing Arch Linux on an UEFI-capable computer with an installed operating system, like [[Dual boot with Windows|Windows]] 10 for example, it is very likely that you already have an EFI system partition.<br />
<br />
To find out the disk partition scheme and the system partition, use [[fdisk]] as root on the disk you want to boot from:<br />
<br />
# fdisk -l /dev/sd''x''<br />
<br />
The command returns:<br />
<br />
* The disk's partition table: it indicates {{ic|Disklabel type: gpt}} if the partition table is [[GPT]] or {{ic|Disklabel type: dos}} if it is [[MBR]].<br />
* The list of partitions on the disk: Look for the EFI system partition in the list, it is usually at least 100 MiB in size and has the type {{ic|EFI System}} or {{ic|EFI (FAT-12/16/32)}}. To confirm this is the ESP, [[mount]] it and check whether it contains a directory named {{ic|EFI}}, if it does this is definitely the ESP.<br />
<br />
{{Tip|To find out whether it is a FAT12, FAT16 or FAT32 file system, follow [[FAT#Detecting FAT type]].}}<br />
<br />
{{Warning|When dual-booting, avoid reformatting the ESP, as it may contain files required to boot other operating systems.}}<br />
<br />
If you found an existing EFI system partition, simply proceed to [[#Mount the partition]]. If you did not find one, you will need to create it, proceed to [[#Create the partition]].<br />
<br />
== Create the partition ==<br />
<br />
The following two sections show how to create an EFI system partition (ESP).<br />
<br />
{{Warning|The EFI system partition must be a physical partition in the main partition table of the disk, not under LVM or software RAID etc.}}<br />
<br />
{{Note|It is recommended to use [[GPT]] since some firmwares might not support UEFI/MBR booting due to it not being supported by [[Dual boot with Windows|Windows Setup]]. See also [[Partitioning#Choosing between GPT and MBR]] for the advantages of GPT in general.}}<br />
<br />
To provide adequate space for storing boot loaders and other files required for booting, and to prevent interoperability issues with other operating systems[https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions#diskpartitionrules][https://superuser.com/questions/1310927/what-is-the-absolute-minimum-size-a-uefi-partition-can-be/1310938] the partition should be at least 260 MiB. For early and/or buggy UEFI implementations the size of at least 512 MiB might be needed.[https://www.rodsbooks.com/efi-bootloaders/principles.html]<br />
<br />
=== GPT partitioned disks ===<br />
<br />
EFI system partition on a [[GUID Partition Table]] is identified by the [[Wikipedia:GUID Partition Table#Partition type GUIDs|partition type GUID]] {{ic|C12A7328-F81F-11D2-BA4B-00A0C93EC93B}}.<br />
<br />
'''Choose one''' of the following methods to create an ESP for a GPT partitioned disk:<br />
<br />
* [[fdisk]]: Create a partition with partition type {{ic|EFI System}}.<br />
* [[gdisk]]: Create a partition with partition type {{ic|EF00}}.<br />
* [[GNU Parted]]: Create a partition with {{ic|fat32}} as the file system type and set the {{ic|esp}} flag on it.<br />
<br />
Proceed to [[#Format the partition]] section below.<br />
<br />
=== MBR partitioned disks ===<br />
<br />
EFI system partition on a [[Master Boot Record]] partition table is identified by the [[Wikipedia:Partition type|partition type ID]] {{ic|EF}}.<br />
<br />
'''Choose one''' of the following methods to create an ESP for a MBR partitioned disk:<br />
<br />
* [[fdisk]]: Create a primary partition with partition type {{ic|EFI (FAT-12/16/32)}}.<br />
* [[GNU Parted]]: Create a primary partition with {{ic|fat32}} as the file system type and set the {{ic|esp}} flag on it.<br />
<br />
Proceed to [[#Format the partition]] section below.<br />
<br />
== Format the partition ==<br />
<br />
The UEFI specification mandates support for the FAT12, FAT16, and FAT32 file systems[https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf#G17.1019485]. To prevent potential issues with other operating systems and also since the UEFI specification only mandates supporting FAT16 and FAT12 on removable media[https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_final.pdf#G17.1345080], it is recommended to use FAT32.<br />
<br />
After creating the partition, [[format]] it as [[FAT32]]. To use the {{ic|mkfs.fat}} utility, [[install]] {{Pkg|dosfstools}}.<br />
<br />
# mkfs.fat -F32 /dev/sd''xY''<br />
<br />
If you get the message {{ic|WARNING: Not enough clusters for a 32 bit FAT!}}, reduce cluster size with {{ic|mkfs.fat -s2 -F32 ...}} or {{ic|-s1}}; otherwise the partition may be unreadable by UEFI. See {{man|8|mkfs.fat}} for supported cluster sizes.<br />
<br />
== Mount the partition ==<br />
<br />
The kernels, initramfs files, and, in most cases, the processor's [[microcode]], need to be accessible by the [[boot loader]] or UEFI itself to successfully boot the system. Thus if you want to keep the setup simple, your boot loader choice limits the available mount points for EFI system partition.<br />
<br />
=== Typical mount points ===<br />
<br />
The simplest scenarios for mounting EFI system partition are:<br />
<br />
* [[mount]] ESP to {{ic|/efi}} and use a [[boot loader]] which is capable of accessing the kernel(s) and initramfs image(s) that are stored elsewhere (typically [[Partitioning#/boot|/boot]]). See [[Arch boot process#Boot loader]] for more information on boot loader requirements and capabilities.<br />
* [[mount]] ESP to {{ic|/boot}}. This is the preferred method when directly booting an [[EFISTUB]] kernel from UEFI.<br />
<br />
{{Tip|<br />
* {{ic|/efi}} is a replacement[https://github.com/systemd/systemd/pull/3757#issuecomment-234290236] for the previously popular (and possibly still used by other Linux distributions) ESP mountpoint {{ic|/boot/efi}}.<br />
* The {{ic|/efi}} directory is not available by default, you will need to first create it with {{man|1|mkdir}} before mounting the ESP to it.<br />
}}<br />
<br />
=== Alternative mount points ===<br />
<br />
If you do not use one of the simple methods from [[#Mount the partition]], you will need to copy your boot files to ESP (referred to hereafter as {{ic|''esp''}}).<br />
<br />
# mkdir -p ''esp''/EFI/arch<br />
# cp -a /boot/vmlinuz-linux ''esp''/EFI/arch/<br />
# cp -a /boot/initramfs-linux.img ''esp''/EFI/arch/<br />
# cp -a /boot/initramfs-linux-fallback.img ''esp''/EFI/arch/<br />
<br />
{{Note|You may also need to copy the [[Microcode]] to the boot-entry location.}}<br />
<br />
Furthermore, you will need to keep the files on the ESP up-to-date with later kernel updates. Failure to do so could result in an unbootable system. The following sections discuss several mechanisms for automating it.<br />
<br />
{{Note|If ESP is not mounted to {{ic|/boot}}, make sure to not rely on the [[fstab#Automount with systemd|systemd automount mechanism]] (including that of {{man|8|systemd-gpt-auto-generator}}). Always have it mounted manually prior to any system or kernel update, otherwise you may not be able to mount it after the update, locking you in the currently running kernel with no ability to update the copy of kernel on ESP.<br />
<br />
Alternatively [[Kernel module#Automatic module loading with systemd|preload the required kernel modules on boot]], e.g.:<br />
<br />
{{hc|/etc/modules-load.d/vfat.conf|<br />
vfat<br />
nls_cp437<br />
nls_iso8859-1<br />
}}<br />
<br />
}}<br />
<br />
==== Using bind mount ====<br />
<br />
Instead of mounting the ESP itself to {{ic|/boot}}, you can mount a directory of the ESP to {{ic|/boot}} using a bind [[mount]] (see {{man|8|mount}}). This allows [[pacman]] to update the kernel directly while keeping the ESP organized to your liking.<br />
<br />
{{Note|1=This requires a [[FAT#Kernel configuration|kernel]] and [[bootloader]] compatible with FAT32. This is not an issue for a regular Arch install, but could be problematic for other distributions (namely those that require symlinks in {{ic|/boot/}}). See the forum post [https://bbs.archlinux.org/viewtopic.php?pid=1331867#p1331867].}}<br />
<br />
Just like in [[#Alternative mount points]], copy all boot files to a directory on your ESP, but mount the ESP '''outside''' {{ic|/boot}}. Then bind mount the directory:<br />
<br />
# mount --bind ''esp''/EFI/arch /boot<br />
<br />
After verifying success, edit your [[Fstab]] to make the changes persistent:<br />
<br />
{{hc|/etc/fstab|<br />
''esp''/EFI/arch /boot none defaults,bind 0 0<br />
}}<br />
<br />
==== Using systemd ====<br />
<br />
[[Systemd]] features event triggered tasks. In this particular case, the ability to detect a change in path is used to sync the EFISTUB kernel and initramfs files when they are updated in {{ic|/boot/}}. The file watched for changes is {{ic|initramfs-linux-fallback.img}} since this is the last file built by mkinitcpio, to make sure all files have been built before starting the copy. The ''systemd'' path and service files to be created are:<br />
<br />
{{hc|/etc/systemd/system/efistub-update.path|2=<br />
[Unit]<br />
Description=Copy EFISTUB Kernel to EFI system partition<br />
<br />
[Path]<br />
PathChanged=/boot/initramfs-linux-fallback.img<br />
<br />
[Install]<br />
WantedBy=multi-user.target<br />
WantedBy=system-update.target<br />
}}<br />
<br />
{{hc|/etc/systemd/system/efistub-update.service|2=<br />
[Unit]<br />
Description=Copy EFISTUB Kernel to EFI system partition<br />
<br />
[Service]<br />
Type=oneshot<br />
ExecStart=/usr/bin/cp -af /boot/vmlinuz-linux ''esp''/EFI/arch/<br />
ExecStart=/usr/bin/cp -af /boot/initramfs-linux.img ''esp''/EFI/arch/<br />
ExecStart=/usr/bin/cp -af /boot/initramfs-linux-fallback.img ''esp''/EFI/arch/<br />
}}<br />
<br />
Then [[enable]] and [[start]] {{ic|efistub-update.service}}.<br />
<br />
{{Tip|For [[Secure Boot]] with your own keys, you can set up the service to also sign the image using {{Pkg|sbsigntools}}:<br />
<br />
{{bc|1=ExecStart=/usr/bin/sbsign --key ''/path/to/db.key'' --cert ''/path/to/db.crt'' --output ''esp''/EFI/arch/vmlinuz-linux /boot/vmlinuz-linux}}<br />
<br />
}}<br />
<br />
==== Using filesystem events ====<br />
<br />
[[Autostarting#On filesystem events|Filesystem events]] can be used to run a script syncing the EFISTUB Kernel after kernel updates. An example with [[incron]] follows.<br />
<br />
{{hc|/usr/local/bin/efistub-update|<br />
#!/bin/sh<br />
cp -af /boot/vmlinuz-linux ''esp''/EFI/arch/<br />
cp -af /boot/initramfs-linux.img ''esp''/EFI/arch/<br />
cp -af /boot/initramfs-linux-fallback.img ''esp''/EFI/arch/<br />
}}<br />
<br />
{{Note|The first parameter {{ic|/boot/initramfs-linux-fallback.img}} is the file to watch. The second parameter {{ic|IN_CLOSE_WRITE}} is the action to watch for. The third parameter {{ic|/usr/local/bin/efistub-update}} is the script to execute.}}<br />
<br />
{{hc|/etc/incron.d/efistub-update.conf|<br />
/boot/initramfs-linux-fallback.img IN_CLOSE_WRITE /usr/local/bin/efistub-update<br />
}}<br />
<br />
In order to use this method, [[enable]] the {{ic|incrond.service}}.<br />
<br />
==== Using mkinitcpio hook ====<br />
<br />
Mkinitcpio can generate a hook that does not need a system level daemon to function. It spawns a background process which waits for the generation of {{ic|vmlinuz}}, {{ic|initramfs-linux.img}}, and {{ic|initramfs-linux-fallback.img}} before copying the files.<br />
<br />
Add {{ic|efistub-update}} to the list of hooks in {{ic|/etc/mkinitcpio.conf}}.<br />
<br />
{{hc|/etc/initcpio/install/efistub-update|<nowiki><br />
#!/usr/bin/env bash<br />
build() {<br />
/usr/local/bin/efistub-copy $$ &<br />
}<br />
<br />
help() {<br />
cat <<HELPEOF<br />
This hook waits for mkinitcpio to finish and copies the finished ramdisk and kernel to the ESP<br />
HELPEOF<br />
}<br />
</nowiki>}}<br />
<br />
{{hc|/usr/local/bin/efistub-copy|<br />
#!/usr/bin/env bash<br />
<br />
<nowiki>if [[ $1 -gt 0 ]]</nowiki><br />
then<br />
while [ -e /proc/$1 ]<br />
do<br />
sleep .5<br />
done<br />
fi<br />
<br />
rsync -a /boot/ ''esp''/<br />
<br />
echo "Synced /boot with ESP"<br />
}}<br />
<br />
==== Using mkinitcpio preset ====<br />
<br />
As the presets in {{ic|/etc/mkinitcpio.d/}} support shell scripting, the kernel and initramfs can be copied by just editing the presets.<br />
<br />
===== Replacing the above mkinitcpio hook =====<br />
<br />
Edit the file {{ic|/etc/mkinitcpio.d/linux.preset}}:<br />
<br />
{{hc|/etc/mkinitcpio.d/linux.preset|<nowiki><br />
# mkinitcpio preset file for the 'linux' package<br />
<br />
# Directory to copy the kernel, the initramfs...<br />
ESP_DIR="''esp''/EFI/arch"<br />
<br />
ALL_config="/etc/mkinitcpio.conf"<br />
ALL_kver="${ESP_DIR}/vmlinuz-linux"<br />
cp -af /boot/vmlinuz-linux "${ESP_DIR}/"<br />
[[ -e /boot/intel-ucode.img ]] && cp -af /boot/intel-ucode.img "${ESP_DIR}/"<br />
[[ -e /boot/amd-ucode.img ]] && cp -af /boot/amd-ucode.img "${ESP_DIR}/"<br />
<br />
PRESETS=('default' 'fallback')<br />
<br />
#default_config="/etc/mkinitcpio.conf"<br />
default_image="${ESP_DIR}/initramfs-linux.img"<br />
default_options="-A esp-update-linux"<br />
<br />
#fallback_config="/etc/mkinitcpio.conf"<br />
fallback_image="${ESP_DIR}/initramfs-linux-fallback.img"<br />
fallback_options="-S autodetect"<br />
</nowiki>}}<br />
To test that, just run:<br />
<br />
# rm /boot/initramfs-linux-fallback.img<br />
# rm /boot/initramfs-linux.img<br />
# mkinitcpio -p linux<br />
<br />
===== Another example =====<br />
<br />
{{hc|/etc/mkinitcpio.d/0.preset|2=<br />
ESP_DIR="''esp''/EFI/arch"<br />
cp -af "/boot/vmlinuz-linux${suffix}" "$ESP_DIR/"<br />
ALL_config="/etc/mkinitcpio.conf"<br />
ALL_kver="$ESP_DIR/vmlinuz-linux${suffix}"<br />
PRESETS=('default')<br />
default_config="/etc/mkinitcpio.conf"<br />
default_image="$ESP_DIR/initramfs-linux${suffix}.img"<br />
}}<br />
<br />
{{hc|/etc/mkinitcpio.d/linux.preset|<br />
source /etc/mkinitcpio.d/0.preset<br />
}}<br />
<br />
{{hc|/etc/mkinitcpio.d/linux-zen.preset|2=<br />
suffix='-zen'<br />
source /etc/mkinitcpio.d/0.preset<br />
}}<br />
<br />
==== Using pacman hook ====<br />
<br />
A last option relies on the [[pacman hooks]] that are run at the end of the transaction.<br />
<br />
The first file is a hook that monitors the relevant files, and it is run if they were modified in the former transaction.<br />
<br />
{{hc|/etc/pacman.d/hooks/999-kernel-efi-copy.hook|<nowiki><br />
[Trigger]<br />
Type = Path<br />
Operation = Install<br />
Operation = Upgrade<br />
Target = usr/lib/modules/*/vmlinuz<br />
Target = usr/lib/initcpio/*<br />
Target = boot/*-ucode.img<br />
<br />
[Action]<br />
Description = Copying linux and initramfs to EFI directory...<br />
When = PostTransaction<br />
Exec = /usr/local/bin/kernel-efi-copy.sh<br />
</nowiki>}}<br />
<br />
The second file is the script itself. Create the file and make it [[executable]]:<br />
<br />
{{hc|/usr/local/bin/kernel-efi-copy.sh|<nowiki><br />
#!/usr/bin/env bash<br />
#<br />
# Copy kernel and initramfs images to EFI directory<br />
#<br />
<br />
ESP_DIR="</nowiki>''esp''<nowiki>/EFI/arch"<br />
<br />
for file in /boot/vmlinuz*<br />
do<br />
cp -af "$file" "$ESP_DIR/$(basename "$file").efi"<br />
[[ $? -ne 0 ]] && exit 1<br />
done<br />
<br />
for file in /boot/initramfs*<br />
do<br />
cp -af "$file" "$ESP_DIR/"<br />
[[ $? -ne 0 ]] && exit 1<br />
done<br />
<br />
[[ -e /boot/intel-ucode.img ]] && cp -af /boot/intel-ucode.img "$ESP_DIR/"<br />
[[ -e /boot/amd-ucode.img ]] && cp -af /boot/amd-ucode.img "$ESP_DIR/"<br />
<br />
exit 0<br />
</nowiki>}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== ESP on software RAID1 ===<br />
<br />
It is possible to make the ESP part of a RAID1 array, but doing so brings the risk of data corruption, and further considerations need to be taken when creating the ESP. See [https://bbs.archlinux.org/viewtopic.php?pid=1398710#p1398710] and [https://bbs.archlinux.org/viewtopic.php?pid=1390741#p1390741] for details and [https://outflux.net/blog/archives/2018/04/19/uefi-booting-and-raid1/ UEFI booting and RAID1] for an in-depth guide with a solution.<br />
<br />
The key part is to use {{ic|--metadata 1.0}} in order to keep the RAID metadata at the end of the partition, otherwise the firmware will not be able to access it:<br />
<br />
# mdadm --create --verbose --level=1 '''--metadata=1.0''' --raid-devices=2 /dev/md/ESP /dev/sda''X'' /dev/sdb''Y''<br />
<br />
=== Firmware does not see the EFI directory ===<br />
<br />
If you give the file system a volume name (with the {{ic|-n}} option), be sure to name it something other than "EFI". That can trigger a bug in some firmwares (due to the volume name matching the EFI directory name) that will cause the firmware to act like the EFI directory does not exist.<br />
<br />
== See also ==<br />
<br />
* [https://blog.uncooperative.org/blog/2014/02/06/the-efi-system-partition/ The EFI system partition and the default boot behavior]<br />
* [https://ramsdenj.com/2016/04/15/multi-boot-linux-with-one-boot-partition.html Multi Boot Linux With One Boot Partition | John Ramsden]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9360)&diff=623337Talk:Dell XPS 13 (9360)2020-07-02T06:45:43Z<p>Latgarf: More precise re-write.</p>
<hr />
<div>== Section Wireless ==<br />
<br />
This is just the data output by iw (or the ath10k driver being wrong). I have no problems downloading or uploading files over WLAN with a sustained speeds of several MByte/s (Ubuntu and Arch) while iw dev wlp58s0 link reports 1 or 6 Mbits/s<br />
<br />
[[User:Lachi|Lachi]] ([[User talk:Lachi|talk]]) 18:39, 29 October 2016 (UTC)<br />
<br />
- Thanks for the information. I directly switched the wlan card my XPS13 had to an Intel 8265 chip, which runs very nice with Linux. This was planed from the beginning, so i didn't check the 1 MByte/s iw gave me further. Feel free to add that.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:42, 29 October 2016 (UTC)<br />
<br />
- This is strange, my wireless connection isn't stable, and there seems to be a firmware file missing for ath10k. Are you sure it's properly included in the kernel?<br />
~ ➤ dmesg | grep ath10k <br />
[ 1.617988] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)<br />
[ 1.620576] ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0<br />
[ 1.634702] Modules linked in: vfat fat snd_hda_intel(+) evdev snd_hda_codec input_leds led_class pcspkr mac_hid snd_hda_core snd_hwdep snd_pcm snd_timer snd ath10k_pci(+) soundcore i2c_i801(+) i2c_smbus ath10k_core ath mac80211 i915(+) cfg80211 rtsx_pci_ms memstick mei_me mei shpchp idma64 drm_kms_helper intel_lpss_pci drm intel_gtt intel_pch_thermal syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit processor_thermal_device intel_soc_dts_iosf thermal i2c_hid wmi hid battery hci_uart intel_vbtn btbcm soc_button_array btqca btintel int3400_thermal bluetooth acpi_thermal_rel rfkill video intel_lpss_acpi intel_lpss int3403_thermal int340x_thermal_zone intel_hid sparse_keymap fjes acpi_pad ac button acpi_als kfifo_buf industrialio tpm_tis(+) tpm_tis_core tpm sch_fq_codel ip_tables x_tables ext4<br />
[ 1.889432] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889456] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889665] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2<br />
[ 1.889670] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2<br />
[ 1.890787] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535<br />
[ 1.890790] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0<br />
[ 1.892271] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5<br />
[ 1.955414] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7<br />
[ 4.078443] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1<br />
~ ➤<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 01:59, 17 November 2016 (UTC)<br />
<br />
- I hadn't had any problems, but was trying to get monitor mode working (failed). Found the same message, stuck https://github.com/sumdog/ath10k-firmware/blob/master/ath10k/QCA6174/hw3.0/firmware-5.bin in, saw no changes. Currently troubleshooting wifi breakage after suspend failing "Freezing of tasks failed" ("device poll D ...") which may or may not be related. Also "rtkit-daemon: The canary thread is apparently starving [...] "demoted /usr/bin/pulseaudio" but that's even less likely related.<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:15, 24 March 2017 (UTC)<br />
<br />
I haven't had a problem with my ath10k in quite some time, even though linux-firmware pacman upgrades have clobbered my firmware-6.bin file, downgrading it to WLAN.RM.4.4.1-00140-QCARMSWPZ-1 at the time of writing. If it is the case that linux-firmware contains sufficiently up-to-date firmware now, what do people think of removing these instructions?<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 08:44, 17 November 2019 (UTC)<br />
<br />
:I haven't had any issues recently either, but let's leave it for now, just in case. If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no? :) [[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:15, 17 November 2019 (UTC)<br />
<br />
> If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no?<br />
<br />
That's reasonable. I have not edited the Arch Wiki before and was unsure how to balance the conflicting priorities of de-cluttering and exhaustive troubleshooting resources. In that case, the problem is that the advice doesn't work! The linux-firmware package owns /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin. I have not tried this, but TIL you can prevent individual files from being upgraded by pacman as documented in https://wiki.archlinux.org/index.php/Pacman#Skip_file_from_being_upgraded. Adding that to the wiki might be prudent if we're going to keep the advice.<br />
<br />
I did not try the original wiki advice (patching firmware-4.bin) as it was superseded by patching firmware-6.bin. I'm not clear on how the firmware loading process works, but I'd guess that the firmware-6.bin laid down by linux-firmware would take precedence? If so then I reckon we should remove the firmware-4.bin directions as part of this cleanup. What do you think?<br />
<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 12:44, 17 November 2019 (UTC)<br />
<br />
:This is a page for a specific laptop model with specific hardware issues - generally you want to keep as much reliable info as possible on these, even if it's outdated or low quality, since you never know what issues people are going to have with their hardware revision. Consider this: Whatever caused the wireless problems in your Killer 1535 hardware revision might've been fixed in blobs available in current linux-firmware. But let's say that Qualcomm gets a new hw revision a few months later, same specs, same model number, just that they've introduced a few hardware fixes. And those hardware fixes, oops, introduce a minor bug elsewhere, so we need a firmware fix. But linux-firmware is slightly behind the latest firmware blobs from Qualcomm, so what do these users have to do in the meantime? Replace their adapter, use wired networking? Nah, they're going to google those issues, find a note that Dell and some random wikis recommended upgrading the firmware, so they'll do the same and now it kind of works. (Of course, if the only needed fix for a given issue is to upgrade the software to a decently recent version, that can be removed after a while since we're on Arch and the only supported system is a fully updated one. The same advice does not apply to software/guide/explanation pages, please purge or mark anything outdated on these :)<br />
<br />
:The advice mentions replacing the entire QCA6174 folder with the downloaded one - that is, to remove all the files provided by linux-firmware (pacman will still be able to upgrade the package just fine by overwriting your files). This works just fine, or at least it did on my laptop back when I needed those fixes.<br />
<br />
:[[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:59, 17 November 2019 (UTC)<br />
<br />
== Touchscreen ==<br />
<br />
Initially works out of the box but sometimes dies after resume from suspend. Anyone else getting this?<br />
<br />
[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 02:12, 31 October 2016 (UTC)<br />
<br />
Hey there, it's the same for me! I don't use it anyway so I just made a fast check and could not find a solution. Can't see something irregual in dmesg or journactl, so it could be a prolem with libinput...<br />
<br />
Update: When starting Arch I can see the ELAN Touchscreen in "libinput-list-devices" and also in xinput list as a virtual device. After suspend its gone from both...<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 08:15, 31 October 2016 (UTC)<br />
<br />
Found a answer to that problem on kernel.org and added it to the wiki. [https://bugzilla.kernel.org/show_bug.cgi?id=176361 kernel.org]<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 09:23, 31 October 2016 (UTC)<br />
<br />
== External Monitors ==<br />
<br />
Having trouble with an external monitor using a DisplayPort <-> USB-C cable. Anyone else seeing this? Monitor is detected fine by XPS, but no signal being sent by the XPS to the monitor.<br />
<br />
------<br />
<br />
I think you will need an active adapter to use that. I tried it with an combi adapter i bought from cable matters and could connect it via vga or hdmi withou any problem. Because i wanted to have a 4k display and 60 Hz i now bought an plugable thunderbolt to 2 times Display Port Adapter and will tell you how it works once i got it.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:10, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
I have a similar problem using the official Dell adapter when going from USB-C to HDMI. Interestingly it works if I use '''1280x800''' or anything lower as the resolution but for anything above that I don’t get any output. The supported resolutions seem to be recognized correctly by xrandr.<br />
<br />
[[User:cocreature|cocreature]] ([[User talk:cocreature|talk]]) 18:45, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
There is [https://bugs.freedesktop.org/show_bug.cgi?id=94567#c27 an open bug report] for this issue. Unfortunatly it's unfixed for quite some time.<br />
<br />
[[User:Kaueraal|Kaueraal]] ([[User talk:Kaueraal|talk]]) 14:13, 20 December 2016 (UTC)<br />
<br />
------<br />
<br />
So I am running the Anker Aluminium USB C to HDMI Adapter. I just plugged it in and it worked. I also got the HDMI to VGA Adapter from Ugreen (the active one) in case there is no HDMI available. It also worked right of the box. No need to change anything. I can link the products here if necessary.<br />
<br />
uname -r<br />
4.10.6-1-ARCH<br />
<br />
[[User:janphilippi|janphilippi]] ([[User talk:janphilippi|talk]]) 16:05, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
Checkout bug report here [bugs.freedesktop.org/show_bug.cgi?id=93578] for details on fix for official Dell adapter. The patch should be pushed out on 4.11 or 4.12.<br />
<br />
[[User:SnowLimit|SnowLimit]] ([[User talk:SnowLimit|talk]]) 17:52, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
== CPU ==<br />
Getting a lot of dmesg errors regarding some failure on pipe A<br />
<br />
[ 1832.400184] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=109958 end=109959) time 277 us, min 1788, max 1799, scanline start 1772, end 1803<br />
[ 1892.651578] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=113567 end=113568) time 379 us, min 1788, max 1799, scanline start 1773, end 1816<br />
[ 1907.727072] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=114470 end=114471) time 373 us, min 1788, max 1799, scanline start 1786, end 1828<br />
<br />
Following [https://bbs.archlinux.org/viewtopic.php?id=214177 this link], I've verified that I was correctly running the microcodes (although no microcode is added)<br />
<br />
$ sudo bsdtar -Oxf /boot/intel-ucode.img | iucode_tool -tb -lS - <br />
iucode_tool: system has processor(s) with signature 0x000806e9<br />
microcode bundle 1: (stdin)<br />
selected microcodes:<br />
$<br />
<br />
I tried to add ''i915.enable_psr=0'' to my boot entry without success<br />
<br />
title Arch Linux<br />
linux /vmlinuz-linux<br />
initrd /intel-ucode.img<br />
initrd /initramfs-linux.img<br />
options root=/dev/disk/by-label/ARCH_ROOT rw i915.enable_psr=0<br />
timeout 4<br />
editor 0<br />
<br />
And I could confirm that while running `sudo intel_gpu_top` in a shell, no new error was thrown in dmesg.<br />
<br />
Hasn't this happened to you guys?<br />
<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 02:29, 17 November 2016 (UTC)<br />
<br />
I had the same with intel-ucode, enable_psr=1 disable_power_well=0. Now testing enable_psr=2<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:21, 24 March 2017 (UTC)<br />
<br />
Also seeing FIFO underruns but much more rarely.<br />
<br />
[ 3556.126478] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 14:09, 27 March 2017 (UTC)<br />
<br />
== GPU hang kernel error ==<br />
There seems a problem in the driver (4.8.7-nvme): <br />
<pre><br />
Nov 27 16:01:51 horizon kernel: [drm] GPU HANG: ecode 9:0:0x87d6fffe, in Xorg [522], reason: Hang on render ring, action: reset<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.<br />
Nov 27 16:01:51 horizon kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel<br />
Nov 27 16:01:51 horizon kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.<br />
Nov 27 16:01:51 horizon kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error<br />
Nov 27 16:01:51 horizon kernel: drm/i915: Resetting chip after gpu hang<br />
Nov 27 16:01:51 horizon kernel: [drm] GuC firmware load skipped<br />
Nov 27 16:01:53 horizon kernel: [drm] RC6 on<br />
</pre><br />
This problem leads to a computer freeze (mouse, everything) for a few seconds and then things move on normally again.<br />
<br />
... to be investigated. I'll post updates and put the bug link here, once I get around to it. 14:59, 1 December 2016 Tormen<br />
<br />
Here's a bug I reported, which looks very similar: [https://bugs.freedesktop.org/show_bug.cgi?id=109072] , '''so this may have been fixed upstream (mesa).''' And this is not a kernel bug. [[User:Vladimir Pinchuk|Vladimir Pinchuk]] ([[User talk:Vladimir Pinchuk|talk]]) 11:02, 17 January 2019 (UTC)<br />
<br />
== Bluetooth ==<br />
<br />
Anyone else seeing an apparent race with bluetooth on resume (4.9.10)? Sometimes it works and sometimes it doesn't, leaving it in a state where it seems to be enabled but is useless, and giving errors when trying to power it back on. Sometimes merely suspending and resuming again fixes it, but not always. rfkill checks out. dmesg excerpt;<br />
<pre><br />
[359743.125259] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359745.205270] Bluetooth: hci0 command 0x200b tx timeout<br />
[359747.285300] Bluetooth: hci0 command 0x200c tx timeout<br />
[359749.365579] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359751.445385] Bluetooth: hci0 command 0x200b tx timeout<br />
[359753.525484] Bluetooth: hci0 command 0x200c tx timeout<br />
</pre><br />
<br />
The bluetoothd service also outputs errors like <code>Failed to set mode: Failed (0x03)</code> to the systemd journal when calling <code>power on</code> in <code>bluetoothctl</code>.<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 23:39, 5 March 2017 (UTC)<br />
<br />
Add one observation. The Bluetooth device cannot be detected when I restarted the laptop as I did many times yesterday. Interestingly, it can be found properly if I start the laptop completely today.<br />
<pre><br />
$ lsusb<br />
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet<br />
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub<br />
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 001 Device 006: ID 0bda:568b Realtek Semiconductor Corp. <br />
********************<br />
*Bus 001 Device 005: ID 0cf3:e300 Qualcomm Atheros Communications*<br />
********************<br />
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver<br />
Bus 001 Device 004: ID 413c:2113 Dell Computer Corp. <br />
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub<br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
</pre><br />
I remembered that the bluetooth device didn't show up yesterday when my Bluetooth wasn't working in the "restart" mode.<br />
<br />
--[[User:Tikilou|Tikilou]] ([[User talk:Tikilou|Tikilou]]) 00:36, 17 Sept 2018 (UTC)<br />
<br />
I've founded something interesting about bluetooth, all of this (can't work after suspend...) is because this is an old firmware wich are integrated inside the linux-firmware package.<br />
If we download latest firmware, rename and replaces files in the right directory, everything work perfectly, without any problem.<br />
[https://askubuntu.com/questions/1024281/dell-xps-13-9370-bluetooth-issues/1029749#1029749 issue is here]<br />
Maybe someone should contact the maintener of linux-firmware package about this update<br />
<br />
== Freeze on resume from suspend ==<br />
<br />
Anyone else? It's happened about once a week - Open it and try to wake, it seems to resume but freezes. No C+A+F*, haven't had a keyboard with SysRQ handy to try that.<br />
<br />
<br />
Haven't experienced this but AltGr + PrintScreen is SysRq (if you have AltGr).<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 13:38, 24 March 2017 (UTC)<br />
<br />
== USB-C Compatibility Chart ==<br />
<br />
{| class="wikitable"<br />
| '''Device''' || '''Ports''' || '''Status''' || '''Notes'''<br />
|-<br />
| [https://www.amazon.com/Anker-Adapter-Supports-Macbook-Chromebook/dp/B01MYUCWOK/ Anker USB-C to HDMI Adapter] || 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.apple.com/uk/shop/product/MJ262B/A/apple-29w-usb-c-power-adapter?fnode=8b Apple 29W USB-C Power Adapter] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF72B/A/61w-usb%E2%80%91c-power-adapter?fnode=8b Apple 61W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF82B/A/87w-usb-c-power-adapter?fnode=8b Apple 87W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MMEL2AM/A/thunderbolt-3-usb-c-to-thunderbolt-2-adapter Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter] || Thunderbolt 2, Thunderbolt || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MJ1K2AM/A/usb-c-digital-av-multiport-adapter Apple USB-C Digital AV Multiport Adapter] || USB-C, USB-A, HDMI || {{Y|Mostly Working}} || Charging does not work (tested w/ Apple 87W Power Adapter)<br />
|-<br />
| [https://www.arp.ch/fr/adaptateur-arp-usb-3-1-c-dvi-4044821-5115074 ARP USB 3.1 C - DVI] || DVI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/gp/product/B01H3K387Q/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Aukey USB-C Hub HDMI 4 Port] || USB-C, 4xUSB-A, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/dp/B06XGWD2VT/ Aukey Multiport USB-C Hub] || USB-C, 2x USB, HDMI, VGA, SD card, micro SD card, Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.belkin.com/us/p/P-F2CU037/ Belkin USB-C to VGA Adapter] || VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01C316EIK Cable Matters USB-C Multiport Adapter] || 4K HDMI or VGA, USB 3.0, Gigabit Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.cablematters.com/pc-893-114-usb-c-to-hdmi-adapter-supporting-4k-60hz-60w-charging-usb-c-thunderbolt-3-port-compatible-for-samsung-galaxy-note-9note-8-galaxy-s9s9s8s8.aspx Cable Matters USB-C to HDMI Adapter with Power Delivery] || USB-C Power (60W PD), 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.caldigit.com/thunderbolt-3-dock/thunderbolt-station-3-plus/index-eu.asp Caldigit TS3 Plus] || USB-C Power, Gbit Ethernet, SPDIF, 5x USB-A (3.0), 2x USB-C (1x 3.1, 1x 3.0), DP (4K), audio 3.5mm in/out, TB3 daisy-chain (or monitor), SD 4.0 UHS-II || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B012DT6KW2 Dell DA200] || USB-A, Ethernet, HDMI (max. 1920x1080), VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Dell-3GMVT-Thunderbolt-Dock-black/dp/B06XN6XWD7/ Dell TB16] || USB-C Power, VGA, mDP, HDMI, DP, Thunderbolt, Ethernet (only 100Mbit Mode), 2x USB 2.0, 3x USB 3.0 (Disable Thunderbolt Security in BIOS)|| {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01FN1YK92 Dell WD15 130W] || 3xUSB-A 3.0, 2xUSB-A 2.0, Ethernet, HDMI, Mini DisplayPort, VGA, Line Out, Line In || {{G|Working}} ||<br />
|-<br />
| [https://www.dodocool.com/p-dc58weu.html dodocool DC58 45W USB Type-C Wall Charger Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/Hama-135729-Multiport-USB-HDMI-Adapter/dp/B01MD0FWWY/ Hama 135729 Multiport 4 in 1] || 2 X USB A, USB c, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?t=3&v=494 i-Tec USB 3.0 / USB-C 5K Universal Dual Display Docking Station] || 2x 4K 60Hz Video, 2x HDMI, 2x Display Port, 1x GLAN Ethernet, 6x USB-A 3.0, 1x Audio Input / Output || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=443 i-Tec USB-C Dual Display MST Dock] || HDMI, DP (4K@30Hz Single Monitor, 1920x1200@60Hz Dual Monitor), Gbit Ethernet, 3xUSB-A, USB-C, Sound, Charging @ 60W || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=437 i-Tec USB-C Low Profile Docking Station] || HDMI 4K@30Hz, SD Card Reader, Gigabit Ethernet, 3x USB-A, USB-C, USB-PD@60W || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B074Z1YWHR/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 i-Tec USB-C 4K Travel Docking Station Multi Adapter] || 4K HDMI, Gigabit Ethernet (RTL8153), 2x USB 3.0, 1x USB-C Power, 1x USB-C || {{G|Working}} ||<br />
|-<br />
| [http://www.myinnergie.com/us/product/99 Innergie PowerGear USB-C 45] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Juiced-BizHUB-Multiport-Ethernet-Delivery/dp/B01J391C3W Juiced Systems BizHUB USB-C Multiport Gigabit HDMI Hub] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Kanex-USB-C-Adapter-Inches-White/dp/B00VBNSY0S Kanex USB-C to HDMI 4K Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://lmp-adapter.com/product/lmp-usb-c-mini-dock/ LMP USB-C mini Dock] || USB-C Power, Gigabit Ethernet, HDMI 4K, 3x USB 3.0, SD, microSD || {{G|Working}} || Retail price: 75€<br />
|-<br />
| [https://www.amazon.de/gp/product/B073WVKSSS/ Omars Type C Hub OMADTTCSL4PAL-UK] || Gigabit Ethernet, HDMI (4K@30 Hz), VGA, 2x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [http://www.pct-max.com.tw/cht/products.php?index=289 PCT UHC304] || HDMI (4K@30Hz, 2K@60Hz), Gigabit Ethernet, USB-A, USB-C || {{G|Working}} ||<br />
|-<br />
| [https://smile.amazon.com/QacQoc-Aluminum-Multi-Port-Charging-Ethernet/dp/B01MU1FFMP QacQoc GN30H USB-C HUB Aluminum Multi-Port TYPE C HUB Adapter with 4K HDMI] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B077XRLJ4S RAVPower Type C USB Power Delivery Charger 36W] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/nl/en/AV/usb-c-video-adapters/usb-c-hdmi-adapter~CDP2HD StarTech CDP2HD - USB-C to HDMI Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01ANR4CYE StarTech TB32DP2 - Thunderbolt 3 Adapter] || 2 x DP (4 K, 60 Hz) || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/StarTech-com-Thunderbolt-Adapter-Compatible-DisplayPort/dp/B019FPJDQ2 StarTech TBT3TBTADAP - Thunderbolt 3 to Thunderbolt Adapter] || Thunderbolt 2, Thunderbolt || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/AV/usb-c-video-adapters/usb-c-dp-mst-hub~MSTCDP122DP StarTech USB-C DP MST Hub] || 2x DP || {{Y|Buggy}} || Takes a few tries, sometimes freezes GPU<br />
|-<br />
| [https://www.amazon.com/Tripp-Lite-External-Charging-U444-06N-DGU-C/dp/B01LYQB1XI Tripp Lite USB-C to DVI External Video Adapter] || DVI, Gbit Ethernet, USB-A, USB-C PD Charging Port || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B075H85W43 UCOUSO USB-C Aluminium HDMI Adapter mit HDMI (4K@30HZ) und 3 USB 3.0 Ports] || HDMI, 3x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [https://ugreen.com/product/1258-en.html UGREEN USB Type-C 30W Wall Charger With Power Delivery] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://xiaomi-mi.com/accessories-for-laptops/xiaomi-usb-type-c-to-hdmi-multifunction-adapter/ Xiaomi USB Type-C to HDMI Multifunction Adapter] || 4K HDMI, 1x USB 3.0, USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://item.mi.com/1172800036.html?cfrom=list Xiaomi USB Type-C Clip On Car Charger Expansion] || USB-C Power || {{G|Working}} ||<br />
|}<br />
<br />
== Destroyed Display Panel ==<br />
<br />
I destroyed my display panel by not being super-careful when doing Step 6. There was no clear indication from the tool that disables ABC whether it's working or had finished. I thought it had completed, so I prematurely powered down the computer.<br />
<br />
I'm happy now after purchasing and installing the new display panel and finally succeding at disabling ABC by following these instructions. Strangely, however, the tool that disables ABC gave dozens of red "fail" messages while it was working on disabling ABC - seemingly properly judging from the good result. Also, flashing took quite a bit longer than I am used to - around 10-20 minutes.</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9360)&diff=623336Talk:Dell XPS 13 (9360)2020-07-02T06:40:59Z<p>Latgarf: Section name change to be more descriptive.</p>
<hr />
<div>== Section Wireless ==<br />
<br />
This is just the data output by iw (or the ath10k driver being wrong). I have no problems downloading or uploading files over WLAN with a sustained speeds of several MByte/s (Ubuntu and Arch) while iw dev wlp58s0 link reports 1 or 6 Mbits/s<br />
<br />
[[User:Lachi|Lachi]] ([[User talk:Lachi|talk]]) 18:39, 29 October 2016 (UTC)<br />
<br />
- Thanks for the information. I directly switched the wlan card my XPS13 had to an Intel 8265 chip, which runs very nice with Linux. This was planed from the beginning, so i didn't check the 1 MByte/s iw gave me further. Feel free to add that.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:42, 29 October 2016 (UTC)<br />
<br />
- This is strange, my wireless connection isn't stable, and there seems to be a firmware file missing for ath10k. Are you sure it's properly included in the kernel?<br />
~ ➤ dmesg | grep ath10k <br />
[ 1.617988] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)<br />
[ 1.620576] ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0<br />
[ 1.634702] Modules linked in: vfat fat snd_hda_intel(+) evdev snd_hda_codec input_leds led_class pcspkr mac_hid snd_hda_core snd_hwdep snd_pcm snd_timer snd ath10k_pci(+) soundcore i2c_i801(+) i2c_smbus ath10k_core ath mac80211 i915(+) cfg80211 rtsx_pci_ms memstick mei_me mei shpchp idma64 drm_kms_helper intel_lpss_pci drm intel_gtt intel_pch_thermal syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit processor_thermal_device intel_soc_dts_iosf thermal i2c_hid wmi hid battery hci_uart intel_vbtn btbcm soc_button_array btqca btintel int3400_thermal bluetooth acpi_thermal_rel rfkill video intel_lpss_acpi intel_lpss int3403_thermal int340x_thermal_zone intel_hid sparse_keymap fjes acpi_pad ac button acpi_als kfifo_buf industrialio tpm_tis(+) tpm_tis_core tpm sch_fq_codel ip_tables x_tables ext4<br />
[ 1.889432] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889456] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889665] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2<br />
[ 1.889670] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2<br />
[ 1.890787] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535<br />
[ 1.890790] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0<br />
[ 1.892271] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5<br />
[ 1.955414] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7<br />
[ 4.078443] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1<br />
~ ➤<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 01:59, 17 November 2016 (UTC)<br />
<br />
- I hadn't had any problems, but was trying to get monitor mode working (failed). Found the same message, stuck https://github.com/sumdog/ath10k-firmware/blob/master/ath10k/QCA6174/hw3.0/firmware-5.bin in, saw no changes. Currently troubleshooting wifi breakage after suspend failing "Freezing of tasks failed" ("device poll D ...") which may or may not be related. Also "rtkit-daemon: The canary thread is apparently starving [...] "demoted /usr/bin/pulseaudio" but that's even less likely related.<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:15, 24 March 2017 (UTC)<br />
<br />
I haven't had a problem with my ath10k in quite some time, even though linux-firmware pacman upgrades have clobbered my firmware-6.bin file, downgrading it to WLAN.RM.4.4.1-00140-QCARMSWPZ-1 at the time of writing. If it is the case that linux-firmware contains sufficiently up-to-date firmware now, what do people think of removing these instructions?<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 08:44, 17 November 2019 (UTC)<br />
<br />
:I haven't had any issues recently either, but let's leave it for now, just in case. If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no? :) [[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:15, 17 November 2019 (UTC)<br />
<br />
> If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no?<br />
<br />
That's reasonable. I have not edited the Arch Wiki before and was unsure how to balance the conflicting priorities of de-cluttering and exhaustive troubleshooting resources. In that case, the problem is that the advice doesn't work! The linux-firmware package owns /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin. I have not tried this, but TIL you can prevent individual files from being upgraded by pacman as documented in https://wiki.archlinux.org/index.php/Pacman#Skip_file_from_being_upgraded. Adding that to the wiki might be prudent if we're going to keep the advice.<br />
<br />
I did not try the original wiki advice (patching firmware-4.bin) as it was superseded by patching firmware-6.bin. I'm not clear on how the firmware loading process works, but I'd guess that the firmware-6.bin laid down by linux-firmware would take precedence? If so then I reckon we should remove the firmware-4.bin directions as part of this cleanup. What do you think?<br />
<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 12:44, 17 November 2019 (UTC)<br />
<br />
:This is a page for a specific laptop model with specific hardware issues - generally you want to keep as much reliable info as possible on these, even if it's outdated or low quality, since you never know what issues people are going to have with their hardware revision. Consider this: Whatever caused the wireless problems in your Killer 1535 hardware revision might've been fixed in blobs available in current linux-firmware. But let's say that Qualcomm gets a new hw revision a few months later, same specs, same model number, just that they've introduced a few hardware fixes. And those hardware fixes, oops, introduce a minor bug elsewhere, so we need a firmware fix. But linux-firmware is slightly behind the latest firmware blobs from Qualcomm, so what do these users have to do in the meantime? Replace their adapter, use wired networking? Nah, they're going to google those issues, find a note that Dell and some random wikis recommended upgrading the firmware, so they'll do the same and now it kind of works. (Of course, if the only needed fix for a given issue is to upgrade the software to a decently recent version, that can be removed after a while since we're on Arch and the only supported system is a fully updated one. The same advice does not apply to software/guide/explanation pages, please purge or mark anything outdated on these :)<br />
<br />
:The advice mentions replacing the entire QCA6174 folder with the downloaded one - that is, to remove all the files provided by linux-firmware (pacman will still be able to upgrade the package just fine by overwriting your files). This works just fine, or at least it did on my laptop back when I needed those fixes.<br />
<br />
:[[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:59, 17 November 2019 (UTC)<br />
<br />
== Touchscreen ==<br />
<br />
Initially works out of the box but sometimes dies after resume from suspend. Anyone else getting this?<br />
<br />
[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 02:12, 31 October 2016 (UTC)<br />
<br />
Hey there, it's the same for me! I don't use it anyway so I just made a fast check and could not find a solution. Can't see something irregual in dmesg or journactl, so it could be a prolem with libinput...<br />
<br />
Update: When starting Arch I can see the ELAN Touchscreen in "libinput-list-devices" and also in xinput list as a virtual device. After suspend its gone from both...<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 08:15, 31 October 2016 (UTC)<br />
<br />
Found a answer to that problem on kernel.org and added it to the wiki. [https://bugzilla.kernel.org/show_bug.cgi?id=176361 kernel.org]<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 09:23, 31 October 2016 (UTC)<br />
<br />
== External Monitors ==<br />
<br />
Having trouble with an external monitor using a DisplayPort <-> USB-C cable. Anyone else seeing this? Monitor is detected fine by XPS, but no signal being sent by the XPS to the monitor.<br />
<br />
------<br />
<br />
I think you will need an active adapter to use that. I tried it with an combi adapter i bought from cable matters and could connect it via vga or hdmi withou any problem. Because i wanted to have a 4k display and 60 Hz i now bought an plugable thunderbolt to 2 times Display Port Adapter and will tell you how it works once i got it.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:10, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
I have a similar problem using the official Dell adapter when going from USB-C to HDMI. Interestingly it works if I use '''1280x800''' or anything lower as the resolution but for anything above that I don’t get any output. The supported resolutions seem to be recognized correctly by xrandr.<br />
<br />
[[User:cocreature|cocreature]] ([[User talk:cocreature|talk]]) 18:45, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
There is [https://bugs.freedesktop.org/show_bug.cgi?id=94567#c27 an open bug report] for this issue. Unfortunatly it's unfixed for quite some time.<br />
<br />
[[User:Kaueraal|Kaueraal]] ([[User talk:Kaueraal|talk]]) 14:13, 20 December 2016 (UTC)<br />
<br />
------<br />
<br />
So I am running the Anker Aluminium USB C to HDMI Adapter. I just plugged it in and it worked. I also got the HDMI to VGA Adapter from Ugreen (the active one) in case there is no HDMI available. It also worked right of the box. No need to change anything. I can link the products here if necessary.<br />
<br />
uname -r<br />
4.10.6-1-ARCH<br />
<br />
[[User:janphilippi|janphilippi]] ([[User talk:janphilippi|talk]]) 16:05, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
Checkout bug report here [bugs.freedesktop.org/show_bug.cgi?id=93578] for details on fix for official Dell adapter. The patch should be pushed out on 4.11 or 4.12.<br />
<br />
[[User:SnowLimit|SnowLimit]] ([[User talk:SnowLimit|talk]]) 17:52, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
== CPU ==<br />
Getting a lot of dmesg errors regarding some failure on pipe A<br />
<br />
[ 1832.400184] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=109958 end=109959) time 277 us, min 1788, max 1799, scanline start 1772, end 1803<br />
[ 1892.651578] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=113567 end=113568) time 379 us, min 1788, max 1799, scanline start 1773, end 1816<br />
[ 1907.727072] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=114470 end=114471) time 373 us, min 1788, max 1799, scanline start 1786, end 1828<br />
<br />
Following [https://bbs.archlinux.org/viewtopic.php?id=214177 this link], I've verified that I was correctly running the microcodes (although no microcode is added)<br />
<br />
$ sudo bsdtar -Oxf /boot/intel-ucode.img | iucode_tool -tb -lS - <br />
iucode_tool: system has processor(s) with signature 0x000806e9<br />
microcode bundle 1: (stdin)<br />
selected microcodes:<br />
$<br />
<br />
I tried to add ''i915.enable_psr=0'' to my boot entry without success<br />
<br />
title Arch Linux<br />
linux /vmlinuz-linux<br />
initrd /intel-ucode.img<br />
initrd /initramfs-linux.img<br />
options root=/dev/disk/by-label/ARCH_ROOT rw i915.enable_psr=0<br />
timeout 4<br />
editor 0<br />
<br />
And I could confirm that while running `sudo intel_gpu_top` in a shell, no new error was thrown in dmesg.<br />
<br />
Hasn't this happened to you guys?<br />
<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 02:29, 17 November 2016 (UTC)<br />
<br />
I had the same with intel-ucode, enable_psr=1 disable_power_well=0. Now testing enable_psr=2<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:21, 24 March 2017 (UTC)<br />
<br />
Also seeing FIFO underruns but much more rarely.<br />
<br />
[ 3556.126478] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 14:09, 27 March 2017 (UTC)<br />
<br />
== GPU hang kernel error ==<br />
There seems a problem in the driver (4.8.7-nvme): <br />
<pre><br />
Nov 27 16:01:51 horizon kernel: [drm] GPU HANG: ecode 9:0:0x87d6fffe, in Xorg [522], reason: Hang on render ring, action: reset<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.<br />
Nov 27 16:01:51 horizon kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel<br />
Nov 27 16:01:51 horizon kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.<br />
Nov 27 16:01:51 horizon kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error<br />
Nov 27 16:01:51 horizon kernel: drm/i915: Resetting chip after gpu hang<br />
Nov 27 16:01:51 horizon kernel: [drm] GuC firmware load skipped<br />
Nov 27 16:01:53 horizon kernel: [drm] RC6 on<br />
</pre><br />
This problem leads to a computer freeze (mouse, everything) for a few seconds and then things move on normally again.<br />
<br />
... to be investigated. I'll post updates and put the bug link here, once I get around to it. 14:59, 1 December 2016 Tormen<br />
<br />
Here's a bug I reported, which looks very similar: [https://bugs.freedesktop.org/show_bug.cgi?id=109072] , '''so this may have been fixed upstream (mesa).''' And this is not a kernel bug. [[User:Vladimir Pinchuk|Vladimir Pinchuk]] ([[User talk:Vladimir Pinchuk|talk]]) 11:02, 17 January 2019 (UTC)<br />
<br />
== Bluetooth ==<br />
<br />
Anyone else seeing an apparent race with bluetooth on resume (4.9.10)? Sometimes it works and sometimes it doesn't, leaving it in a state where it seems to be enabled but is useless, and giving errors when trying to power it back on. Sometimes merely suspending and resuming again fixes it, but not always. rfkill checks out. dmesg excerpt;<br />
<pre><br />
[359743.125259] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359745.205270] Bluetooth: hci0 command 0x200b tx timeout<br />
[359747.285300] Bluetooth: hci0 command 0x200c tx timeout<br />
[359749.365579] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359751.445385] Bluetooth: hci0 command 0x200b tx timeout<br />
[359753.525484] Bluetooth: hci0 command 0x200c tx timeout<br />
</pre><br />
<br />
The bluetoothd service also outputs errors like <code>Failed to set mode: Failed (0x03)</code> to the systemd journal when calling <code>power on</code> in <code>bluetoothctl</code>.<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 23:39, 5 March 2017 (UTC)<br />
<br />
Add one observation. The Bluetooth device cannot be detected when I restarted the laptop as I did many times yesterday. Interestingly, it can be found properly if I start the laptop completely today.<br />
<pre><br />
$ lsusb<br />
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet<br />
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub<br />
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 001 Device 006: ID 0bda:568b Realtek Semiconductor Corp. <br />
********************<br />
*Bus 001 Device 005: ID 0cf3:e300 Qualcomm Atheros Communications*<br />
********************<br />
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver<br />
Bus 001 Device 004: ID 413c:2113 Dell Computer Corp. <br />
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub<br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
</pre><br />
I remembered that the bluetooth device didn't show up yesterday when my Bluetooth wasn't working in the "restart" mode.<br />
<br />
--[[User:Tikilou|Tikilou]] ([[User talk:Tikilou|Tikilou]]) 00:36, 17 Sept 2018 (UTC)<br />
<br />
I've founded something interesting about bluetooth, all of this (can't work after suspend...) is because this is an old firmware wich are integrated inside the linux-firmware package.<br />
If we download latest firmware, rename and replaces files in the right directory, everything work perfectly, without any problem.<br />
[https://askubuntu.com/questions/1024281/dell-xps-13-9370-bluetooth-issues/1029749#1029749 issue is here]<br />
Maybe someone should contact the maintener of linux-firmware package about this update<br />
<br />
== Freeze on resume from suspend ==<br />
<br />
Anyone else? It's happened about once a week - Open it and try to wake, it seems to resume but freezes. No C+A+F*, haven't had a keyboard with SysRQ handy to try that.<br />
<br />
<br />
Haven't experienced this but AltGr + PrintScreen is SysRq (if you have AltGr).<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 13:38, 24 March 2017 (UTC)<br />
<br />
== USB-C Compatibility Chart ==<br />
<br />
{| class="wikitable"<br />
| '''Device''' || '''Ports''' || '''Status''' || '''Notes'''<br />
|-<br />
| [https://www.amazon.com/Anker-Adapter-Supports-Macbook-Chromebook/dp/B01MYUCWOK/ Anker USB-C to HDMI Adapter] || 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.apple.com/uk/shop/product/MJ262B/A/apple-29w-usb-c-power-adapter?fnode=8b Apple 29W USB-C Power Adapter] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF72B/A/61w-usb%E2%80%91c-power-adapter?fnode=8b Apple 61W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF82B/A/87w-usb-c-power-adapter?fnode=8b Apple 87W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MMEL2AM/A/thunderbolt-3-usb-c-to-thunderbolt-2-adapter Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter] || Thunderbolt 2, Thunderbolt || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MJ1K2AM/A/usb-c-digital-av-multiport-adapter Apple USB-C Digital AV Multiport Adapter] || USB-C, USB-A, HDMI || {{Y|Mostly Working}} || Charging does not work (tested w/ Apple 87W Power Adapter)<br />
|-<br />
| [https://www.arp.ch/fr/adaptateur-arp-usb-3-1-c-dvi-4044821-5115074 ARP USB 3.1 C - DVI] || DVI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/gp/product/B01H3K387Q/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Aukey USB-C Hub HDMI 4 Port] || USB-C, 4xUSB-A, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/dp/B06XGWD2VT/ Aukey Multiport USB-C Hub] || USB-C, 2x USB, HDMI, VGA, SD card, micro SD card, Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.belkin.com/us/p/P-F2CU037/ Belkin USB-C to VGA Adapter] || VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01C316EIK Cable Matters USB-C Multiport Adapter] || 4K HDMI or VGA, USB 3.0, Gigabit Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.cablematters.com/pc-893-114-usb-c-to-hdmi-adapter-supporting-4k-60hz-60w-charging-usb-c-thunderbolt-3-port-compatible-for-samsung-galaxy-note-9note-8-galaxy-s9s9s8s8.aspx Cable Matters USB-C to HDMI Adapter with Power Delivery] || USB-C Power (60W PD), 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.caldigit.com/thunderbolt-3-dock/thunderbolt-station-3-plus/index-eu.asp Caldigit TS3 Plus] || USB-C Power, Gbit Ethernet, SPDIF, 5x USB-A (3.0), 2x USB-C (1x 3.1, 1x 3.0), DP (4K), audio 3.5mm in/out, TB3 daisy-chain (or monitor), SD 4.0 UHS-II || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B012DT6KW2 Dell DA200] || USB-A, Ethernet, HDMI (max. 1920x1080), VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Dell-3GMVT-Thunderbolt-Dock-black/dp/B06XN6XWD7/ Dell TB16] || USB-C Power, VGA, mDP, HDMI, DP, Thunderbolt, Ethernet (only 100Mbit Mode), 2x USB 2.0, 3x USB 3.0 (Disable Thunderbolt Security in BIOS)|| {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01FN1YK92 Dell WD15 130W] || 3xUSB-A 3.0, 2xUSB-A 2.0, Ethernet, HDMI, Mini DisplayPort, VGA, Line Out, Line In || {{G|Working}} ||<br />
|-<br />
| [https://www.dodocool.com/p-dc58weu.html dodocool DC58 45W USB Type-C Wall Charger Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/Hama-135729-Multiport-USB-HDMI-Adapter/dp/B01MD0FWWY/ Hama 135729 Multiport 4 in 1] || 2 X USB A, USB c, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?t=3&v=494 i-Tec USB 3.0 / USB-C 5K Universal Dual Display Docking Station] || 2x 4K 60Hz Video, 2x HDMI, 2x Display Port, 1x GLAN Ethernet, 6x USB-A 3.0, 1x Audio Input / Output || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=443 i-Tec USB-C Dual Display MST Dock] || HDMI, DP (4K@30Hz Single Monitor, 1920x1200@60Hz Dual Monitor), Gbit Ethernet, 3xUSB-A, USB-C, Sound, Charging @ 60W || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=437 i-Tec USB-C Low Profile Docking Station] || HDMI 4K@30Hz, SD Card Reader, Gigabit Ethernet, 3x USB-A, USB-C, USB-PD@60W || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B074Z1YWHR/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 i-Tec USB-C 4K Travel Docking Station Multi Adapter] || 4K HDMI, Gigabit Ethernet (RTL8153), 2x USB 3.0, 1x USB-C Power, 1x USB-C || {{G|Working}} ||<br />
|-<br />
| [http://www.myinnergie.com/us/product/99 Innergie PowerGear USB-C 45] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Juiced-BizHUB-Multiport-Ethernet-Delivery/dp/B01J391C3W Juiced Systems BizHUB USB-C Multiport Gigabit HDMI Hub] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Kanex-USB-C-Adapter-Inches-White/dp/B00VBNSY0S Kanex USB-C to HDMI 4K Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://lmp-adapter.com/product/lmp-usb-c-mini-dock/ LMP USB-C mini Dock] || USB-C Power, Gigabit Ethernet, HDMI 4K, 3x USB 3.0, SD, microSD || {{G|Working}} || Retail price: 75€<br />
|-<br />
| [https://www.amazon.de/gp/product/B073WVKSSS/ Omars Type C Hub OMADTTCSL4PAL-UK] || Gigabit Ethernet, HDMI (4K@30 Hz), VGA, 2x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [http://www.pct-max.com.tw/cht/products.php?index=289 PCT UHC304] || HDMI (4K@30Hz, 2K@60Hz), Gigabit Ethernet, USB-A, USB-C || {{G|Working}} ||<br />
|-<br />
| [https://smile.amazon.com/QacQoc-Aluminum-Multi-Port-Charging-Ethernet/dp/B01MU1FFMP QacQoc GN30H USB-C HUB Aluminum Multi-Port TYPE C HUB Adapter with 4K HDMI] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B077XRLJ4S RAVPower Type C USB Power Delivery Charger 36W] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/nl/en/AV/usb-c-video-adapters/usb-c-hdmi-adapter~CDP2HD StarTech CDP2HD - USB-C to HDMI Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01ANR4CYE StarTech TB32DP2 - Thunderbolt 3 Adapter] || 2 x DP (4 K, 60 Hz) || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/StarTech-com-Thunderbolt-Adapter-Compatible-DisplayPort/dp/B019FPJDQ2 StarTech TBT3TBTADAP - Thunderbolt 3 to Thunderbolt Adapter] || Thunderbolt 2, Thunderbolt || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/AV/usb-c-video-adapters/usb-c-dp-mst-hub~MSTCDP122DP StarTech USB-C DP MST Hub] || 2x DP || {{Y|Buggy}} || Takes a few tries, sometimes freezes GPU<br />
|-<br />
| [https://www.amazon.com/Tripp-Lite-External-Charging-U444-06N-DGU-C/dp/B01LYQB1XI Tripp Lite USB-C to DVI External Video Adapter] || DVI, Gbit Ethernet, USB-A, USB-C PD Charging Port || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B075H85W43 UCOUSO USB-C Aluminium HDMI Adapter mit HDMI (4K@30HZ) und 3 USB 3.0 Ports] || HDMI, 3x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [https://ugreen.com/product/1258-en.html UGREEN USB Type-C 30W Wall Charger With Power Delivery] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://xiaomi-mi.com/accessories-for-laptops/xiaomi-usb-type-c-to-hdmi-multifunction-adapter/ Xiaomi USB Type-C to HDMI Multifunction Adapter] || 4K HDMI, 1x USB 3.0, USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://item.mi.com/1172800036.html?cfrom=list Xiaomi USB Type-C Clip On Car Charger Expansion] || USB-C Power || {{G|Working}} ||<br />
|}<br />
<br />
== Destroyed Display Panel ==<br />
<br />
I've destroyed my display panel by not being super-careful when doing Step 6. Flashing took quite a bit longer than I was used to, and there was no clear indication from the tool that disables ABC whether it's working or had finished. I thought it had completed, so I prematurely powered down the computer.<br />
<br />
I'm happy now after purchasing and installing the new display panel and finally succeding at disabling ABC by following these instructions. Strangely, however, the tool that disables ABC gave a large number of "fail" messages while it was properly working on disabling ABC.</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9360)&diff=623335Talk:Dell XPS 13 (9360)2020-07-02T06:38:24Z<p>Latgarf: /* Content Adaptive Brightness Control */ new section</p>
<hr />
<div>== Section Wireless ==<br />
<br />
This is just the data output by iw (or the ath10k driver being wrong). I have no problems downloading or uploading files over WLAN with a sustained speeds of several MByte/s (Ubuntu and Arch) while iw dev wlp58s0 link reports 1 or 6 Mbits/s<br />
<br />
[[User:Lachi|Lachi]] ([[User talk:Lachi|talk]]) 18:39, 29 October 2016 (UTC)<br />
<br />
- Thanks for the information. I directly switched the wlan card my XPS13 had to an Intel 8265 chip, which runs very nice with Linux. This was planed from the beginning, so i didn't check the 1 MByte/s iw gave me further. Feel free to add that.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:42, 29 October 2016 (UTC)<br />
<br />
- This is strange, my wireless connection isn't stable, and there seems to be a firmware file missing for ath10k. Are you sure it's properly included in the kernel?<br />
~ ➤ dmesg | grep ath10k <br />
[ 1.617988] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)<br />
[ 1.620576] ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0<br />
[ 1.634702] Modules linked in: vfat fat snd_hda_intel(+) evdev snd_hda_codec input_leds led_class pcspkr mac_hid snd_hda_core snd_hwdep snd_pcm snd_timer snd ath10k_pci(+) soundcore i2c_i801(+) i2c_smbus ath10k_core ath mac80211 i915(+) cfg80211 rtsx_pci_ms memstick mei_me mei shpchp idma64 drm_kms_helper intel_lpss_pci drm intel_gtt intel_pch_thermal syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_algo_bit processor_thermal_device intel_soc_dts_iosf thermal i2c_hid wmi hid battery hci_uart intel_vbtn btbcm soc_button_array btqca btintel int3400_thermal bluetooth acpi_thermal_rel rfkill video intel_lpss_acpi intel_lpss int3403_thermal int340x_thermal_zone intel_hid sparse_keymap fjes acpi_pad ac button acpi_als kfifo_buf industrialio tpm_tis(+) tpm_tis_core tpm sch_fq_codel ip_tables x_tables ext4<br />
[ 1.889432] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889456] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2<br />
[ 1.889665] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2<br />
[ 1.889670] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2<br />
[ 1.890787] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535<br />
[ 1.890790] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0<br />
[ 1.892271] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5<br />
[ 1.955414] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7<br />
[ 4.078443] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1<br />
~ ➤<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 01:59, 17 November 2016 (UTC)<br />
<br />
- I hadn't had any problems, but was trying to get monitor mode working (failed). Found the same message, stuck https://github.com/sumdog/ath10k-firmware/blob/master/ath10k/QCA6174/hw3.0/firmware-5.bin in, saw no changes. Currently troubleshooting wifi breakage after suspend failing "Freezing of tasks failed" ("device poll D ...") which may or may not be related. Also "rtkit-daemon: The canary thread is apparently starving [...] "demoted /usr/bin/pulseaudio" but that's even less likely related.<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:15, 24 March 2017 (UTC)<br />
<br />
I haven't had a problem with my ath10k in quite some time, even though linux-firmware pacman upgrades have clobbered my firmware-6.bin file, downgrading it to WLAN.RM.4.4.1-00140-QCARMSWPZ-1 at the time of writing. If it is the case that linux-firmware contains sufficiently up-to-date firmware now, what do people think of removing these instructions?<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 08:44, 17 November 2019 (UTC)<br />
<br />
:I haven't had any issues recently either, but let's leave it for now, just in case. If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no? :) [[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:15, 17 November 2019 (UTC)<br />
<br />
> If you're not experiencing issues, you wouldn't search for troubleshooting steps in the first place, no?<br />
<br />
That's reasonable. I have not edited the Arch Wiki before and was unsure how to balance the conflicting priorities of de-cluttering and exhaustive troubleshooting resources. In that case, the problem is that the advice doesn't work! The linux-firmware package owns /usr/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin. I have not tried this, but TIL you can prevent individual files from being upgraded by pacman as documented in https://wiki.archlinux.org/index.php/Pacman#Skip_file_from_being_upgraded. Adding that to the wiki might be prudent if we're going to keep the advice.<br />
<br />
I did not try the original wiki advice (patching firmware-4.bin) as it was superseded by patching firmware-6.bin. I'm not clear on how the firmware loading process works, but I'd guess that the firmware-6.bin laid down by linux-firmware would take precedence? If so then I reckon we should remove the firmware-4.bin directions as part of this cleanup. What do you think?<br />
<br />
<br />
[[User:CraigFurman|CraigFurman]] ([[User talk:CraigFurman|talk]]) 12:44, 17 November 2019 (UTC)<br />
<br />
:This is a page for a specific laptop model with specific hardware issues - generally you want to keep as much reliable info as possible on these, even if it's outdated or low quality, since you never know what issues people are going to have with their hardware revision. Consider this: Whatever caused the wireless problems in your Killer 1535 hardware revision might've been fixed in blobs available in current linux-firmware. But let's say that Qualcomm gets a new hw revision a few months later, same specs, same model number, just that they've introduced a few hardware fixes. And those hardware fixes, oops, introduce a minor bug elsewhere, so we need a firmware fix. But linux-firmware is slightly behind the latest firmware blobs from Qualcomm, so what do these users have to do in the meantime? Replace their adapter, use wired networking? Nah, they're going to google those issues, find a note that Dell and some random wikis recommended upgrading the firmware, so they'll do the same and now it kind of works. (Of course, if the only needed fix for a given issue is to upgrade the software to a decently recent version, that can be removed after a while since we're on Arch and the only supported system is a fully updated one. The same advice does not apply to software/guide/explanation pages, please purge or mark anything outdated on these :)<br />
<br />
:The advice mentions replacing the entire QCA6174 folder with the downloaded one - that is, to remove all the files provided by linux-firmware (pacman will still be able to upgrade the package just fine by overwriting your files). This works just fine, or at least it did on my laptop back when I needed those fixes.<br />
<br />
:[[User:DragoonAethis|DragoonAethis]] ([[User talk:DragoonAethis|talk]]) 12:59, 17 November 2019 (UTC)<br />
<br />
== Touchscreen ==<br />
<br />
Initially works out of the box but sometimes dies after resume from suspend. Anyone else getting this?<br />
<br />
[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 02:12, 31 October 2016 (UTC)<br />
<br />
Hey there, it's the same for me! I don't use it anyway so I just made a fast check and could not find a solution. Can't see something irregual in dmesg or journactl, so it could be a prolem with libinput...<br />
<br />
Update: When starting Arch I can see the ELAN Touchscreen in "libinput-list-devices" and also in xinput list as a virtual device. After suspend its gone from both...<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 08:15, 31 October 2016 (UTC)<br />
<br />
Found a answer to that problem on kernel.org and added it to the wiki. [https://bugzilla.kernel.org/show_bug.cgi?id=176361 kernel.org]<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 09:23, 31 October 2016 (UTC)<br />
<br />
== External Monitors ==<br />
<br />
Having trouble with an external monitor using a DisplayPort <-> USB-C cable. Anyone else seeing this? Monitor is detected fine by XPS, but no signal being sent by the XPS to the monitor.<br />
<br />
------<br />
<br />
I think you will need an active adapter to use that. I tried it with an combi adapter i bought from cable matters and could connect it via vga or hdmi withou any problem. Because i wanted to have a 4k display and 60 Hz i now bought an plugable thunderbolt to 2 times Display Port Adapter and will tell you how it works once i got it.<br />
<br />
[[User:ColdBug|ColdBug]] ([[User talk:ColdBug|talk]]) 18:10, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
I have a similar problem using the official Dell adapter when going from USB-C to HDMI. Interestingly it works if I use '''1280x800''' or anything lower as the resolution but for anything above that I don’t get any output. The supported resolutions seem to be recognized correctly by xrandr.<br />
<br />
[[User:cocreature|cocreature]] ([[User talk:cocreature|talk]]) 18:45, 1 November 2016 (UTC)<br />
<br />
------<br />
<br />
There is [https://bugs.freedesktop.org/show_bug.cgi?id=94567#c27 an open bug report] for this issue. Unfortunatly it's unfixed for quite some time.<br />
<br />
[[User:Kaueraal|Kaueraal]] ([[User talk:Kaueraal|talk]]) 14:13, 20 December 2016 (UTC)<br />
<br />
------<br />
<br />
So I am running the Anker Aluminium USB C to HDMI Adapter. I just plugged it in and it worked. I also got the HDMI to VGA Adapter from Ugreen (the active one) in case there is no HDMI available. It also worked right of the box. No need to change anything. I can link the products here if necessary.<br />
<br />
uname -r<br />
4.10.6-1-ARCH<br />
<br />
[[User:janphilippi|janphilippi]] ([[User talk:janphilippi|talk]]) 16:05, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
Checkout bug report here [bugs.freedesktop.org/show_bug.cgi?id=93578] for details on fix for official Dell adapter. The patch should be pushed out on 4.11 or 4.12.<br />
<br />
[[User:SnowLimit|SnowLimit]] ([[User talk:SnowLimit|talk]]) 17:52, 07 April 2017 (UTC)<br />
<br />
------<br />
<br />
== CPU ==<br />
Getting a lot of dmesg errors regarding some failure on pipe A<br />
<br />
[ 1832.400184] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=109958 end=109959) time 277 us, min 1788, max 1799, scanline start 1772, end 1803<br />
[ 1892.651578] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=113567 end=113568) time 379 us, min 1788, max 1799, scanline start 1773, end 1816<br />
[ 1907.727072] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=114470 end=114471) time 373 us, min 1788, max 1799, scanline start 1786, end 1828<br />
<br />
Following [https://bbs.archlinux.org/viewtopic.php?id=214177 this link], I've verified that I was correctly running the microcodes (although no microcode is added)<br />
<br />
$ sudo bsdtar -Oxf /boot/intel-ucode.img | iucode_tool -tb -lS - <br />
iucode_tool: system has processor(s) with signature 0x000806e9<br />
microcode bundle 1: (stdin)<br />
selected microcodes:<br />
$<br />
<br />
I tried to add ''i915.enable_psr=0'' to my boot entry without success<br />
<br />
title Arch Linux<br />
linux /vmlinuz-linux<br />
initrd /intel-ucode.img<br />
initrd /initramfs-linux.img<br />
options root=/dev/disk/by-label/ARCH_ROOT rw i915.enable_psr=0<br />
timeout 4<br />
editor 0<br />
<br />
And I could confirm that while running `sudo intel_gpu_top` in a shell, no new error was thrown in dmesg.<br />
<br />
Hasn't this happened to you guys?<br />
<br />
--[[User:Fandekasp|Fandekasp]] ([[User talk:Fandekasp|talk]]) 02:29, 17 November 2016 (UTC)<br />
<br />
I had the same with intel-ucode, enable_psr=1 disable_power_well=0. Now testing enable_psr=2<br />
<br />
--[[User:Mal|Mal]] ([[User talk:Mal|talk]]) 03:21, 24 March 2017 (UTC)<br />
<br />
Also seeing FIFO underruns but much more rarely.<br />
<br />
[ 3556.126478] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 14:09, 27 March 2017 (UTC)<br />
<br />
== GPU hang kernel error ==<br />
There seems a problem in the driver (4.8.7-nvme): <br />
<pre><br />
Nov 27 16:01:51 horizon kernel: [drm] GPU HANG: ecode 9:0:0x87d6fffe, in Xorg [522], reason: Hang on render ring, action: reset<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.<br />
Nov 27 16:01:51 horizon kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel<br />
Nov 27 16:01:51 horizon kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.<br />
Nov 27 16:01:51 horizon kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.<br />
Nov 27 16:01:51 horizon kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error<br />
Nov 27 16:01:51 horizon kernel: drm/i915: Resetting chip after gpu hang<br />
Nov 27 16:01:51 horizon kernel: [drm] GuC firmware load skipped<br />
Nov 27 16:01:53 horizon kernel: [drm] RC6 on<br />
</pre><br />
This problem leads to a computer freeze (mouse, everything) for a few seconds and then things move on normally again.<br />
<br />
... to be investigated. I'll post updates and put the bug link here, once I get around to it. 14:59, 1 December 2016 Tormen<br />
<br />
Here's a bug I reported, which looks very similar: [https://bugs.freedesktop.org/show_bug.cgi?id=109072] , '''so this may have been fixed upstream (mesa).''' And this is not a kernel bug. [[User:Vladimir Pinchuk|Vladimir Pinchuk]] ([[User talk:Vladimir Pinchuk|talk]]) 11:02, 17 January 2019 (UTC)<br />
<br />
== Bluetooth ==<br />
<br />
Anyone else seeing an apparent race with bluetooth on resume (4.9.10)? Sometimes it works and sometimes it doesn't, leaving it in a state where it seems to be enabled but is useless, and giving errors when trying to power it back on. Sometimes merely suspending and resuming again fixes it, but not always. rfkill checks out. dmesg excerpt;<br />
<pre><br />
[359743.125259] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359745.205270] Bluetooth: hci0 command 0x200b tx timeout<br />
[359747.285300] Bluetooth: hci0 command 0x200c tx timeout<br />
[359749.365579] Bluetooth: hci0 command 0x2011 tx timeout<br />
[359751.445385] Bluetooth: hci0 command 0x200b tx timeout<br />
[359753.525484] Bluetooth: hci0 command 0x200c tx timeout<br />
</pre><br />
<br />
The bluetoothd service also outputs errors like <code>Failed to set mode: Failed (0x03)</code> to the systemd journal when calling <code>power on</code> in <code>bluetoothctl</code>.<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 23:39, 5 March 2017 (UTC)<br />
<br />
Add one observation. The Bluetooth device cannot be detected when I restarted the laptop as I did many times yesterday. Interestingly, it can be found properly if I start the laptop completely today.<br />
<pre><br />
$ lsusb<br />
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet<br />
Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. Hub<br />
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 001 Device 006: ID 0bda:568b Realtek Semiconductor Corp. <br />
********************<br />
*Bus 001 Device 005: ID 0cf3:e300 Qualcomm Atheros Communications*<br />
********************<br />
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver<br />
Bus 001 Device 004: ID 413c:2113 Dell Computer Corp. <br />
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub<br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
</pre><br />
I remembered that the bluetooth device didn't show up yesterday when my Bluetooth wasn't working in the "restart" mode.<br />
<br />
--[[User:Tikilou|Tikilou]] ([[User talk:Tikilou|Tikilou]]) 00:36, 17 Sept 2018 (UTC)<br />
<br />
I've founded something interesting about bluetooth, all of this (can't work after suspend...) is because this is an old firmware wich are integrated inside the linux-firmware package.<br />
If we download latest firmware, rename and replaces files in the right directory, everything work perfectly, without any problem.<br />
[https://askubuntu.com/questions/1024281/dell-xps-13-9370-bluetooth-issues/1029749#1029749 issue is here]<br />
Maybe someone should contact the maintener of linux-firmware package about this update<br />
<br />
== Freeze on resume from suspend ==<br />
<br />
Anyone else? It's happened about once a week - Open it and try to wake, it seems to resume but freezes. No C+A+F*, haven't had a keyboard with SysRQ handy to try that.<br />
<br />
<br />
Haven't experienced this but AltGr + PrintScreen is SysRq (if you have AltGr).<br />
<br />
--[[User:Zorael|Zorael]] ([[User talk:Zorael|talk]]) 13:38, 24 March 2017 (UTC)<br />
<br />
== USB-C Compatibility Chart ==<br />
<br />
{| class="wikitable"<br />
| '''Device''' || '''Ports''' || '''Status''' || '''Notes'''<br />
|-<br />
| [https://www.amazon.com/Anker-Adapter-Supports-Macbook-Chromebook/dp/B01MYUCWOK/ Anker USB-C to HDMI Adapter] || 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.apple.com/uk/shop/product/MJ262B/A/apple-29w-usb-c-power-adapter?fnode=8b Apple 29W USB-C Power Adapter] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF72B/A/61w-usb%E2%80%91c-power-adapter?fnode=8b Apple 61W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/uk/shop/product/MNF82B/A/87w-usb-c-power-adapter?fnode=8b Apple 87W USB-C Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MMEL2AM/A/thunderbolt-3-usb-c-to-thunderbolt-2-adapter Apple Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter] || Thunderbolt 2, Thunderbolt || {{R|Not Working}} ||<br />
|-<br />
| [https://www.apple.com/shop/product/MJ1K2AM/A/usb-c-digital-av-multiport-adapter Apple USB-C Digital AV Multiport Adapter] || USB-C, USB-A, HDMI || {{Y|Mostly Working}} || Charging does not work (tested w/ Apple 87W Power Adapter)<br />
|-<br />
| [https://www.arp.ch/fr/adaptateur-arp-usb-3-1-c-dvi-4044821-5115074 ARP USB 3.1 C - DVI] || DVI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/gp/product/B01H3K387Q/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Aukey USB-C Hub HDMI 4 Port] || USB-C, 4xUSB-A, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/dp/B06XGWD2VT/ Aukey Multiport USB-C Hub] || USB-C, 2x USB, HDMI, VGA, SD card, micro SD card, Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.belkin.com/us/p/P-F2CU037/ Belkin USB-C to VGA Adapter] || VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01C316EIK Cable Matters USB-C Multiport Adapter] || 4K HDMI or VGA, USB 3.0, Gigabit Ethernet || {{G|Working}} ||<br />
|-<br />
| [http://www.cablematters.com/pc-893-114-usb-c-to-hdmi-adapter-supporting-4k-60hz-60w-charging-usb-c-thunderbolt-3-port-compatible-for-samsung-galaxy-note-9note-8-galaxy-s9s9s8s8.aspx Cable Matters USB-C to HDMI Adapter with Power Delivery] || USB-C Power (60W PD), 4K@60Hz HDMI || {{G|Working}} ||<br />
|-<br />
| [http://www.caldigit.com/thunderbolt-3-dock/thunderbolt-station-3-plus/index-eu.asp Caldigit TS3 Plus] || USB-C Power, Gbit Ethernet, SPDIF, 5x USB-A (3.0), 2x USB-C (1x 3.1, 1x 3.0), DP (4K), audio 3.5mm in/out, TB3 daisy-chain (or monitor), SD 4.0 UHS-II || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B012DT6KW2 Dell DA200] || USB-A, Ethernet, HDMI (max. 1920x1080), VGA || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Dell-3GMVT-Thunderbolt-Dock-black/dp/B06XN6XWD7/ Dell TB16] || USB-C Power, VGA, mDP, HDMI, DP, Thunderbolt, Ethernet (only 100Mbit Mode), 2x USB 2.0, 3x USB 3.0 (Disable Thunderbolt Security in BIOS)|| {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01FN1YK92 Dell WD15 130W] || 3xUSB-A 3.0, 2xUSB-A 2.0, Ethernet, HDMI, Mini DisplayPort, VGA, Line Out, Line In || {{G|Working}} ||<br />
|-<br />
| [https://www.dodocool.com/p-dc58weu.html dodocool DC58 45W USB Type-C Wall Charger Power Adapter] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.co.uk/Hama-135729-Multiport-USB-HDMI-Adapter/dp/B01MD0FWWY/ Hama 135729 Multiport 4 in 1] || 2 X USB A, USB c, HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?t=3&v=494 i-Tec USB 3.0 / USB-C 5K Universal Dual Display Docking Station] || 2x 4K 60Hz Video, 2x HDMI, 2x Display Port, 1x GLAN Ethernet, 6x USB-A 3.0, 1x Audio Input / Output || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=443 i-Tec USB-C Dual Display MST Dock] || HDMI, DP (4K@30Hz Single Monitor, 1920x1200@60Hz Dual Monitor), Gbit Ethernet, 3xUSB-A, USB-C, Sound, Charging @ 60W || {{G|Working}} ||<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=437 i-Tec USB-C Low Profile Docking Station] || HDMI 4K@30Hz, SD Card Reader, Gigabit Ethernet, 3x USB-A, USB-C, USB-PD@60W || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B074Z1YWHR/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 i-Tec USB-C 4K Travel Docking Station Multi Adapter] || 4K HDMI, Gigabit Ethernet (RTL8153), 2x USB 3.0, 1x USB-C Power, 1x USB-C || {{G|Working}} ||<br />
|-<br />
| [http://www.myinnergie.com/us/product/99 Innergie PowerGear USB-C 45] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Juiced-BizHUB-Multiport-Ethernet-Delivery/dp/B01J391C3W Juiced Systems BizHUB USB-C Multiport Gigabit HDMI Hub] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/Kanex-USB-C-Adapter-Inches-White/dp/B00VBNSY0S Kanex USB-C to HDMI 4K Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://lmp-adapter.com/product/lmp-usb-c-mini-dock/ LMP USB-C mini Dock] || USB-C Power, Gigabit Ethernet, HDMI 4K, 3x USB 3.0, SD, microSD || {{G|Working}} || Retail price: 75€<br />
|-<br />
| [https://www.amazon.de/gp/product/B073WVKSSS/ Omars Type C Hub OMADTTCSL4PAL-UK] || Gigabit Ethernet, HDMI (4K@30 Hz), VGA, 2x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [http://www.pct-max.com.tw/cht/products.php?index=289 PCT UHC304] || HDMI (4K@30Hz, 2K@60Hz), Gigabit Ethernet, USB-A, USB-C || {{G|Working}} ||<br />
|-<br />
| [https://smile.amazon.com/QacQoc-Aluminum-Multi-Port-Charging-Ethernet/dp/B01MU1FFMP QacQoc GN30H USB-C HUB Aluminum Multi-Port TYPE C HUB Adapter with 4K HDMI] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B077XRLJ4S RAVPower Type C USB Power Delivery Charger 36W] || USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/nl/en/AV/usb-c-video-adapters/usb-c-hdmi-adapter~CDP2HD StarTech CDP2HD - USB-C to HDMI Adapter] || HDMI || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/dp/B01ANR4CYE StarTech TB32DP2 - Thunderbolt 3 Adapter] || 2 x DP (4 K, 60 Hz) || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.com/StarTech-com-Thunderbolt-Adapter-Compatible-DisplayPort/dp/B019FPJDQ2 StarTech TBT3TBTADAP - Thunderbolt 3 to Thunderbolt Adapter] || Thunderbolt 2, Thunderbolt || {{G|Working}} ||<br />
|-<br />
| [https://www.startech.com/AV/usb-c-video-adapters/usb-c-dp-mst-hub~MSTCDP122DP StarTech USB-C DP MST Hub] || 2x DP || {{Y|Buggy}} || Takes a few tries, sometimes freezes GPU<br />
|-<br />
| [https://www.amazon.com/Tripp-Lite-External-Charging-U444-06N-DGU-C/dp/B01LYQB1XI Tripp Lite USB-C to DVI External Video Adapter] || DVI, Gbit Ethernet, USB-A, USB-C PD Charging Port || {{G|Working}} ||<br />
|-<br />
| [https://www.amazon.de/gp/product/B075H85W43 UCOUSO USB-C Aluminium HDMI Adapter mit HDMI (4K@30HZ) und 3 USB 3.0 Ports] || HDMI, 3x USB 3.0 || {{G|Working}} ||<br />
|-<br />
| [https://ugreen.com/product/1258-en.html UGREEN USB Type-C 30W Wall Charger With Power Delivery] || USB-C Power || {{R|Not Working}} ||<br />
|-<br />
| [https://xiaomi-mi.com/accessories-for-laptops/xiaomi-usb-type-c-to-hdmi-multifunction-adapter/ Xiaomi USB Type-C to HDMI Multifunction Adapter] || 4K HDMI, 1x USB 3.0, USB-C Power || {{G|Working}} ||<br />
|-<br />
| [https://item.mi.com/1172800036.html?cfrom=list Xiaomi USB Type-C Clip On Car Charger Expansion] || USB-C Power || {{G|Working}} ||<br />
|}<br />
<br />
== Content Adaptive Brightness Control ==<br />
<br />
I've destroyed my display panel by not being super-careful when doing Step 6. Flashing took quite a bit longer than I was used to, and there was no clear indication from the tool that disables ABC whether it's working or had finished. I thought it had completed, so I prematurely powered down the computer.<br />
<br />
I'm happy now after purchasing and installing the new display panel and finally succeding at disabling ABC by following these instructions. Strangely, however, the tool that disables ABC gave a large number of "fail" messages while it was properly working on disabling ABC.</div>Latgarfhttps://wiki.archlinux.org/index.php?title=ArchWiki_talk:Sandbox&diff=623334ArchWiki talk:Sandbox2020-07-02T06:26:13Z<p>Latgarf: /* 2020-07-02 a1 */ new section</p>
<hr />
<div>==Comments==<br />
<br />
Hello guys, Arch is great!!! [[User:Cipher699|Cipher699]] ([[User talk:Cipher699|talk]]) 12:39, 14 June 2020 (UTC)<br />
<br />
Hello, how are you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
:Fine, thanks, and you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
::Tres bien) -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 05:33, 28 January 2014 (UTC)<br />
:: how do you edit the wiki?<br />
Testing [[User:Tech2077|Tech2077]] ([[User talk:Tech2077|talk]]) 21:38, 3 July 2015 (UTC)<br />
:::: Uh, tu parles francais [[User:Kycok|Kycok]]? I am from switzerland but I hated french in school and now I am learning it every single day. --[[User:Ndalliard|ndalliard]] ([[User talk:Ndalliard|talk]]) 04:42, 31 July 2015 (UTC)<br />
Trying to contribute here. ([[User:Amoros|Amoros]]) ([[User talk:Amoros|talk]]) 15:37, 12 August 2015 (UTC)<br />
<br />
Hi I'm new here [[User:Chrisfryer78|Chrisfryer78]] ([[User talk:Chrisfryer78|talk]]) 08:36, 7 November 2015 (UTC)<br />
:Hello, I'm new here too! This is a test. [[User:Nullifer|Nullifer]] ([[User talk:Nullifer|talk]]) 07:48, 30 December 2016 (UTC)<br />
:Hello this is a test reply :) [[User:Viktorstrate|Viktorstrate]] ([[User talk:Viktorstrate|talk]])viktorstrate 16:10, 4 July 2018 (UTC)<br />
<br />
How about we rewrite Arch? <br />
[[User:MrHritik|MrHritik]] ([[User talk:MrHritik|talk]]) 08:02, 4 April 2020 (UTC)<br />
<br />
This is a test comment. [[User:Latgarf|Latgarf]] ([[User talk:Latgarf|talk]]) 03:29, 28 April 2020 (UTC)<br />
<br />
== A new section should be added ==<br />
<br />
I'd like to propose to change blahdieblah!<br />
<br />
[[User:E-type|E-type]] ([[User talk:E-type|talk]]) 17:38, 9 October 2016 (UTC)<br />
<br />
<br />
adding my contributions to the new section, test edit blah blah ...<br />
<br />
[[User:Fawix|Fawix]] ([[User talk:Fawix|talk]]) 20:14, 1 January 2017 (UTC)<br />
<br />
Testing stuff in the sandbox [[User:RobU3|RobU3]] ([[User talk:RobU3|talk]]) 05:15, 30 January 2018 (UTC)<br />
<br />
== New test section ==<br />
<br />
Hello Sandbox! <br />
<br />
-- [[User:Raczek|Raczek]] ([[User talk:Raczek|talk]]) 13:43, 11 May 2017 (UTC)<br />
<br />
Just a test...<br />
[[User:Leventel|Leventel]] ([[User talk:Leventel|talk]]) 10:07, 12 May 2017 (UTC)<br />
<br />
Looks like I'm the newest user now. [[User:Mycatfishsteve|Mycatfishsteve]] ([[User talk:Mycatfishsteve|talk]]) 21:56, 6 June 2017 (UTC)<br />
: Short joy ! I myself wonder how to add {{ic|codelines}} [[User:Lafleur|la Fleur]] ([[User talk:Lafleur|talk]]) 23:55, 12 October 2018 (UTC)<br />
<br />
:: Hello :)<br />
<br />
== Add topic test ==<br />
<br />
test<br />
-- [[User:Z32O|Z32O]] ([[User talk:Z32O|talk]]) 17:14, 13 Oct 2017 (UTC)<br />
:I think it's nice test ;)<br />
:[[User:Elnee|Elnee]] ([[User talk:Elnee|talk]]) 09:02, 28 November 2018 (UTC)<br />
<br />
== New topic to talk about ==<br />
<br />
Bla bla bla bla bla.<br />
[[User:Mouseman|Mouseman]] ([[User talk:Mouseman|talk]]) 13:07, 21 October 2018 (UTC)<br />
<br />
== Test ==<br />
<br />
Talk test<br />
--[[User:Alpery|Alpery]] ([[User talk:Alpery|talk]]) 15:27, 5 January 2019 (UTC)<br />
<br />
== greetings ==<br />
<br />
hi i'm a new arch wiki person [[User:Starclimber|Starclimber]] ([[User talk:Starclimber|talk]]) 00:34, 23 January 2019 (UTC)<br />
:I am new to discussion pages. I hope this works. [[User:Brottweiler|Brottweiler]] ([[User talk:Brottweiler|talk]]) 15:58, 7 October 2019 (UTC)<br />
<br />
== shaks add topic test ==<br />
<br />
Hi every body! pls excuse my engrish in advance. Here comes my 4xtilda:<br />
<br />
[[User:Shak|Shak]] ([[User talk:Shak|talk]]) 21:30, 12 May 2019 (UTC)<br />
<br />
:Hey, your engrish is totally fine in advance don't worry! [[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== Here is my super discussion topic! Wanna taco 'bout it ? ==<br />
<br />
What do you guys think about that super discussion topic ? What a nice sandbox area!<br />
There's markhmm markdown ? Markup ? Markmatting symbols everywhere!<br />
<br />
[[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== This is a topic. ==<br />
<br />
Pretty neat, huh?<br />
<br />
[[User:Polygonerror|Polygonerror]] ([[User talk:Polygonerror|talk]]) 15:39, 20 December 2019 (UTC)<br />
<br />
== New test section. ==<br />
<br />
Beginning of a new test section. [[User:Latgarf|Latgarf]] ([[User talk:Latgarf|talk]]) 03:30, 28 April 2020 (UTC)<br />
<br />
== Testing ==<br />
<br />
Hey, is it working properly?<br />
<br />
Maybe<br />
<br />
I'm literally just testing, don't expect much from me<br />
<br />
<s>strikethrough, nice</s><br />
<br />
a<br />
<br />
b<br />
<br />
c<br />
<br />
d<br />
<br />
*aaaaaaaa<br />
<br />
:oh nice something<br />
::more<br />
:::::::::::::even more<br />
<br />
hmm<br />
<br />
*:<s>sdfsdf</s><br />
cool<br />
<br />
<br />
Okay, I messed with this more than I should have. Goodbye [[User:Andy3153|Andy3153]] ([[User talk:Andy3153|talk]]) 18:18, 13 May 2020 (UTC)<br />
<br />
== Is this how to sign? ==<br />
<br />
Does placing 4 dashes sign things [[User:Varriount|Varriount]] ([[User talk:Varriount|talk]]) 20:43, 20 June 2020 (UTC)<br />
<br />
== 2020-07-02 a1 ==<br />
<br />
Test a1.</div>Latgarfhttps://wiki.archlinux.org/index.php?title=ArchWiki_talk:Sandbox&diff=608585ArchWiki talk:Sandbox2020-04-28T03:30:01Z<p>Latgarf: /* New test section. */ new section</p>
<hr />
<div>==Comments==<br />
<br />
Hello, how are you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
:Fine, thanks, and you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
::Tres bien) -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 05:33, 28 January 2014 (UTC)<br />
:: how do you edit the wiki?<br />
Testing [[User:Tech2077|Tech2077]] ([[User talk:Tech2077|talk]]) 21:38, 3 July 2015 (UTC)<br />
:::: Uh, tu parles francais [[User:Kycok|Kycok]]? I am from switzerland but I hated french in school and now I am learning it every single day. --[[User:Ndalliard|ndalliard]] ([[User talk:Ndalliard|talk]]) 04:42, 31 July 2015 (UTC)<br />
Trying to contribute here. ([[User:Amoros|Amoros]]) ([[User talk:Amoros|talk]]) 15:37, 12 August 2015 (UTC)<br />
<br />
Hi I'm new here [[User:Chrisfryer78|Chrisfryer78]] ([[User talk:Chrisfryer78|talk]]) 08:36, 7 November 2015 (UTC)<br />
:Hello, I'm new here too! This is a test. [[User:Nullifer|Nullifer]] ([[User talk:Nullifer|talk]]) 07:48, 30 December 2016 (UTC)<br />
:Hello this is a test reply :) [[User:Viktorstrate|Viktorstrate]] ([[User talk:Viktorstrate|talk]])viktorstrate 16:10, 4 July 2018 (UTC)<br />
<br />
How about we rewrite Arch? <br />
[[User:MrHritik|MrHritik]] ([[User talk:MrHritik|talk]]) 08:02, 4 April 2020 (UTC)<br />
<br />
This is a test comment. [[User:Latgarf|Latgarf]] ([[User talk:Latgarf|talk]]) 03:29, 28 April 2020 (UTC)<br />
<br />
== A new section should be added ==<br />
<br />
I'd like to propose to change blahdieblah!<br />
<br />
[[User:E-type|E-type]] ([[User talk:E-type|talk]]) 17:38, 9 October 2016 (UTC)<br />
<br />
<br />
adding my contributions to the new section, test edit blah blah ...<br />
<br />
[[User:Fawix|Fawix]] ([[User talk:Fawix|talk]]) 20:14, 1 January 2017 (UTC)<br />
<br />
Testing stuff in the sandbox [[User:RobU3|RobU3]] ([[User talk:RobU3|talk]]) 05:15, 30 January 2018 (UTC)<br />
<br />
== New test section ==<br />
<br />
Hello Sandbox! <br />
<br />
-- [[User:Raczek|Raczek]] ([[User talk:Raczek|talk]]) 13:43, 11 May 2017 (UTC)<br />
<br />
Just a test...<br />
[[User:Leventel|Leventel]] ([[User talk:Leventel|talk]]) 10:07, 12 May 2017 (UTC)<br />
<br />
Looks like I'm the newest user now. [[User:Mycatfishsteve|Mycatfishsteve]] ([[User talk:Mycatfishsteve|talk]]) 21:56, 6 June 2017 (UTC)<br />
: Short joy ! I myself wonder how to add {{ic|codelines}} [[User:Lafleur|la Fleur]] ([[User talk:Lafleur|talk]]) 23:55, 12 October 2018 (UTC)<br />
<br />
:: Hello :)<br />
<br />
== Add topic test ==<br />
<br />
test<br />
-- [[User:Z32O|Z32O]] ([[User talk:Z32O|talk]]) 17:14, 13 Oct 2017 (UTC)<br />
:I think it's nice test ;)<br />
:[[User:Elnee|Elnee]] ([[User talk:Elnee|talk]]) 09:02, 28 November 2018 (UTC)<br />
<br />
== New topic to talk about ==<br />
<br />
Bla bla bla bla bla.<br />
[[User:Mouseman|Mouseman]] ([[User talk:Mouseman|talk]]) 13:07, 21 October 2018 (UTC)<br />
<br />
== Test ==<br />
<br />
Talk test<br />
--[[User:Alpery|Alpery]] ([[User talk:Alpery|talk]]) 15:27, 5 January 2019 (UTC)<br />
<br />
== greetings ==<br />
<br />
hi i'm a new arch wiki person [[User:Starclimber|Starclimber]] ([[User talk:Starclimber|talk]]) 00:34, 23 January 2019 (UTC)<br />
:I am new to discussion pages. I hope this works. [[User:Brottweiler|Brottweiler]] ([[User talk:Brottweiler|talk]]) 15:58, 7 October 2019 (UTC)<br />
<br />
== shaks add topic test ==<br />
<br />
Hi every body! pls excuse my engrish in advance. Here comes my 4xtilda:<br />
<br />
[[User:Shak|Shak]] ([[User talk:Shak|talk]]) 21:30, 12 May 2019 (UTC)<br />
<br />
:Hey, your engrish is totally fine in advance don't worry! [[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== Here is my super discussion topic! Wanna taco 'bout it ? ==<br />
<br />
What do you guys think about that super discussion topic ? What a nice sandbox area!<br />
There's markhmm markdown ? Markup ? Markmatting symbols everywhere!<br />
<br />
[[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== This is a topic. ==<br />
<br />
Pretty neat, huh?<br />
<br />
[[User:Polygonerror|Polygonerror]] ([[User talk:Polygonerror|talk]]) 15:39, 20 December 2019 (UTC)<br />
<br />
== New test section. ==<br />
<br />
Beginning of a new test section. [[User:Latgarf|Latgarf]] ([[User talk:Latgarf|talk]]) 03:30, 28 April 2020 (UTC)</div>Latgarfhttps://wiki.archlinux.org/index.php?title=ArchWiki_talk:Sandbox&diff=608584ArchWiki talk:Sandbox2020-04-28T03:29:09Z<p>Latgarf: test comment</p>
<hr />
<div>==Comments==<br />
<br />
Hello, how are you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
:Fine, thanks, and you? -- [[User:Acgtyrant|Acgtyrant]] ([[User talk:Acgtyrant|talk]]) 15:17, 27 August 2013 (UTC)<br />
::Tres bien) -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 05:33, 28 January 2014 (UTC)<br />
:: how do you edit the wiki?<br />
Testing [[User:Tech2077|Tech2077]] ([[User talk:Tech2077|talk]]) 21:38, 3 July 2015 (UTC)<br />
:::: Uh, tu parles francais [[User:Kycok|Kycok]]? I am from switzerland but I hated french in school and now I am learning it every single day. --[[User:Ndalliard|ndalliard]] ([[User talk:Ndalliard|talk]]) 04:42, 31 July 2015 (UTC)<br />
Trying to contribute here. ([[User:Amoros|Amoros]]) ([[User talk:Amoros|talk]]) 15:37, 12 August 2015 (UTC)<br />
<br />
Hi I'm new here [[User:Chrisfryer78|Chrisfryer78]] ([[User talk:Chrisfryer78|talk]]) 08:36, 7 November 2015 (UTC)<br />
:Hello, I'm new here too! This is a test. [[User:Nullifer|Nullifer]] ([[User talk:Nullifer|talk]]) 07:48, 30 December 2016 (UTC)<br />
:Hello this is a test reply :) [[User:Viktorstrate|Viktorstrate]] ([[User talk:Viktorstrate|talk]])viktorstrate 16:10, 4 July 2018 (UTC)<br />
<br />
How about we rewrite Arch? <br />
[[User:MrHritik|MrHritik]] ([[User talk:MrHritik|talk]]) 08:02, 4 April 2020 (UTC)<br />
<br />
This is a test comment. [[User:Latgarf|Latgarf]] ([[User talk:Latgarf|talk]]) 03:29, 28 April 2020 (UTC)<br />
<br />
== A new section should be added ==<br />
<br />
I'd like to propose to change blahdieblah!<br />
<br />
[[User:E-type|E-type]] ([[User talk:E-type|talk]]) 17:38, 9 October 2016 (UTC)<br />
<br />
<br />
adding my contributions to the new section, test edit blah blah ...<br />
<br />
[[User:Fawix|Fawix]] ([[User talk:Fawix|talk]]) 20:14, 1 January 2017 (UTC)<br />
<br />
Testing stuff in the sandbox [[User:RobU3|RobU3]] ([[User talk:RobU3|talk]]) 05:15, 30 January 2018 (UTC)<br />
<br />
== New test section ==<br />
<br />
Hello Sandbox! <br />
<br />
-- [[User:Raczek|Raczek]] ([[User talk:Raczek|talk]]) 13:43, 11 May 2017 (UTC)<br />
<br />
Just a test...<br />
[[User:Leventel|Leventel]] ([[User talk:Leventel|talk]]) 10:07, 12 May 2017 (UTC)<br />
<br />
Looks like I'm the newest user now. [[User:Mycatfishsteve|Mycatfishsteve]] ([[User talk:Mycatfishsteve|talk]]) 21:56, 6 June 2017 (UTC)<br />
: Short joy ! I myself wonder how to add {{ic|codelines}} [[User:Lafleur|la Fleur]] ([[User talk:Lafleur|talk]]) 23:55, 12 October 2018 (UTC)<br />
<br />
:: Hello :)<br />
<br />
== Add topic test ==<br />
<br />
test<br />
-- [[User:Z32O|Z32O]] ([[User talk:Z32O|talk]]) 17:14, 13 Oct 2017 (UTC)<br />
:I think it's nice test ;)<br />
:[[User:Elnee|Elnee]] ([[User talk:Elnee|talk]]) 09:02, 28 November 2018 (UTC)<br />
<br />
== New topic to talk about ==<br />
<br />
Bla bla bla bla bla.<br />
[[User:Mouseman|Mouseman]] ([[User talk:Mouseman|talk]]) 13:07, 21 October 2018 (UTC)<br />
<br />
== Test ==<br />
<br />
Talk test<br />
--[[User:Alpery|Alpery]] ([[User talk:Alpery|talk]]) 15:27, 5 January 2019 (UTC)<br />
<br />
== greetings ==<br />
<br />
hi i'm a new arch wiki person [[User:Starclimber|Starclimber]] ([[User talk:Starclimber|talk]]) 00:34, 23 January 2019 (UTC)<br />
:I am new to discussion pages. I hope this works. [[User:Brottweiler|Brottweiler]] ([[User talk:Brottweiler|talk]]) 15:58, 7 October 2019 (UTC)<br />
<br />
== shaks add topic test ==<br />
<br />
Hi every body! pls excuse my engrish in advance. Here comes my 4xtilda:<br />
<br />
[[User:Shak|Shak]] ([[User talk:Shak|talk]]) 21:30, 12 May 2019 (UTC)<br />
<br />
:Hey, your engrish is totally fine in advance don't worry! [[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== Here is my super discussion topic! Wanna taco 'bout it ? ==<br />
<br />
What do you guys think about that super discussion topic ? What a nice sandbox area!<br />
There's markhmm markdown ? Markup ? Markmatting symbols everywhere!<br />
<br />
[[User:Xse|Xse]] ([[User talk:Xse|talk]]) 03:42, 11 November 2019 (UTC)<br />
<br />
== This is a topic. ==<br />
<br />
Pretty neat, huh?<br />
<br />
[[User:Polygonerror|Polygonerror]] ([[User talk:Polygonerror|talk]]) 15:39, 20 December 2019 (UTC)</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9360)&diff=477751Dell XPS 13 (9360)2017-05-19T14:11:15Z<p>Latgarf: Changed link to the English (rather than German) version.</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9360)]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || ath10k<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Working}} || hid_multitouch (mousedev)<br />
|-<br />
| Webcam || {{G|Working}} || uvcvideo<br />
|-<br />
| USB-C / Thunderbolt 3 || {{G|Working}} || ?<br />
|-<br />
| Wireless switch || {{G|Working}} || intel_hid<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}} || ?<br />
|-<br />
| Fingerprint sensor || {{R|Not working}} || ?<br />
|}<br />
<br />
The Dell XPS 13 Late 2016 (9360) is the fourth-generation model of the XPS 13 line. The laptop is available since October (pre-2017 model) in both a standard edition with Windows installed as well as both a pre-2017 model and a 2017 model (with insignificant hardware differences) Developer Edition with Ubuntu 16.04 "SP1" installed, featuring kernel 4.8 as of now. There is only minor hardware differences between them, mostly in regards to the mainboard microchip manufacturers. Just like the older versions ([[Dell XPS 13 (9333)]], [[Dell XPS 13 (9343)]] and [[Dell XPS 13 (9350)]]) it is available in different hardware configurations as well. These fourth gen models includes Intel's Kaby Lake CPUs and advertised with up to 16GB LPDDR 1866 MHz RAM and a 1TB PCI SSD. It will now also be available in Rose Gold. Prior to previous information and current specifications available provided by Dell (at least to regular customers), it is not available with the 2133 MHz RAM speed. However, some models, including those available to employees and possibly Dell partners (and/or business customers), memory speed is indeed available up to 2133 Mhz LPDDR3 (non-upgradable). [https://codepaste.net/yr5n9i ref]. The same mentioned models are also available with the Intel Core i7-7660U (aswell as i7-7560U) with the Intel 640 Iris Plus onboard graphics. Respective clock frequencies are 2.5 Ghz (up to 4GHz in Turbo-mode) and 2,4 Ghz (up to 3.8 Ghz), respectively.<br />
<br />
The installation process for Arch on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]] and [[UEFI]]. This page covers the current status of hardware support on Arch, as well as post-installation recommendations.<br />
<br />
As of kernel 4.5, the Intel Kaby Lake architecture is supported.<br />
<br />
<br />
== Content adaptive brightness control ==<br />
In the XPS 13 the display panels (both FHD and QHD+) come with adaptive brightness embedded in the panel firmware, this "content adaptive brightness control" (usually referred to as CABC or DBC) will adjust the screen brightness depending on the content displayed on the screen and will generally be found undesirable, especially for Linux users who are likely to be switching between dark and light screen content. Dell has issued a fix for this however it is only available to run in Windows and for the QHD+ model of the laptop so this precaution should be taken before installing Linux, the FHD model of the XPS 13 (9360) cannot be fixed. This is not a problem with the panel but rather a problem with the way the panels are configured for the XPS 13, as the same panel exists in the Dell's Latitude 13 7000 series (e7370) FHD model but with CABC disabled. The fix is available directly from [http://www.dell.com/support/home/us/en/4/Drivers/DriversDetails?driverId=20JWV Dell].<br />
<br />
== NVM Express SSD ==<br />
=== NVME Power Saving Patch ===<br />
<br />
Andy Lutomirski has created a patchset which fixes powersaving for NVME devices in linux. Currently, this patch is not merged into mainline yet. Until it lands in mainline kernel use the AUR or repository linked below. <br />
{{App|Linux-nvme|Mainline linux kernel patched with Andy's patch for NVME powersaving APST.|https://github.com/damige/linux-nvme|{{AUR|linux-nvme}}}} (check out [http://linuxnvme.damige.net/] for compiled packages)<br />
<br />
This patch is now in mainline (4.11rc1), so it is a matter of time before the standard kernel can be used instead.<br />
<br />
== Video ==<br />
The video should work with the {{ic|i915}} driver of the current {{Pkg|linux}} kernel. Consult [[Intel graphics]] for a detailed installation and configuration guide as well as for [[Intel graphics#Troubleshooting|Troubleshooting]].<br />
<br />
If you have the QHD+ (3200x1800) model, also check out [[HiDPI]] for UI scaling configurations.<br />
<br />
=== Module-based Powersaving Options ===<br />
For the HD 620 graphics card the following modules are working: (see [[Intel graphics#Module-based Powersaving Options]])<br />
modeset=1 enable_rc6=1 enable_fbc=1 <br />
The first argument is to enable modesetting if it's not set by default. The second argument is needed to active power-saving C-States. Higher values than 1 are not available for kaby lake CPUs. The third argument is for frame buffer compression power savings. These values should work well!<br />
<br />
enable_guc_loading=1 enable_guc_submission=1<br />
These arguments are used to enable GuC updates. GuC is a small proprietary binary blob released by intel to update the GuC binary in faster intervals than the kernel release does. It is used for graphics workload scheduling on the various graphics parallel engines. More details at (https://01.org/linuxgraphics/downloads/firmware). The GuC binary for kaby lake is included since firmware release linux-firmware 20170217 in the official repository.<br />
<br />
enable_huc=1<br />
HuC is also an binary blob from intel. It's designed to offload some of the media functions from the CPU to GPU. More details at (https://01.org/linuxgraphics/downloads/firmware). As of kernel 4.11, HuC remains unsupported.<br />
<br />
enable_psr=1 disable_power_well=0 OR enable_psr=2 <br />
Enable psr level 2 is working, while level 1 has a lot of problems. Setting it on level 2 doesn't give much energy saving at the moment. It's said that 'disable_power_well=0 enable_psr=1' is working in this combination.<br />
<br />
NOT WORKING: semaphores=1 <br />
The semaphore option is NOT working for kaby lake CPUs and won't enable even if you set the option to 1.<br />
<br />
=== Blank screen issue after booting ===<br />
If using "late start" [[KMS]] (the default) and the screen goes blank when loading modules, it may help to add {{ic|i915}} and {{ic|intel_agp}} to the initramfs or using a special [[kernel parameter]]. Consult [[Intel graphics#Blank screen during boot, when "Loading modules"]] for more information about the kernel parameter way and have a look at [[Kernel mode setting#Early KMS start]] for a guide on how to setup the modules for the initramfs.<br />
<br />
== Wireless ==<br />
<br />
The Killer 1535 Wirless Adapter is functional and the ath10k firmware is included in recent linux kernel versions. The connection speed reported by iw is limited to 1-6Mbits/s. However this is just the output being wrong. The real connection speed is not limited to this value.<br />
<br />
Some users are experiencing issues, where the connection is dropped under heavy load but reconnects within a brief moment. This might not be noticed during browsing at all but becomes apparent in online games. There is no know solution so far.<br />
<br />
== Bluetooth ==<br />
<br />
After following the instructions given at [[Bluetooth]] tethering of internet connections via phone works immediately.<br />
<br />
<br />
== Thunderbolt 3 / USB 3.1 ==<br />
<br />
The USB-C port supports Thunderbolt 3, Displayport-over-USB-C and USB power delivery as well as USB 3.1.<br />
<br />
=== Ethernet repeatedly disconnects/reconnects with Dell USB-C adapter (DA200) ===<br />
<br />
Use of a power management package (such as [[TLP]]) may cause the ethernet adapter to repeatedly disconnect and reconnect. If this happens, disable/blacklist USB autosuspend for the ethernet adapter. (On my laptop, this is the device <tt>Bus 004 Device 007: ID 0bda:8153 Realtek Semiconductor Corp</tt> in the output of <tt>lsusb</tt>.)<br />
<br />
Also disabling or reducing power of wifi may help: http://en.community.dell.com/support-forums/network-internet-wireless/f/3324/t/19995423<br />
<br />
=== USB-C Compatibility Chart ===<br />
{| class="wikitable"<br />
| '''Device''' || '''Ports''' || '''Status'''<br />
|-<br />
| [http://www.apple.com/uk/shop/product/MJ1K2ZM/A/usb-c-digital-av-multiport-adapter Apple USB-C Digital AV Multiport Adapter] || USB-C, USB-A, HDMI || {{R|Not Working}}<br />
|-<br />
| [http://www.apple.com/uk/shop/product/MJ262B/A/apple-29w-usb-c-power-adapter?fnode=8b Apple 29W USB-C Power Adapter] || USB-C Power || {{R|Not Working}}<br />
|-<br />
| [https://www.amazon.co.uk/gp/product/B01H3K387Q/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 Aukey USB C Hub HDMI 4 Port] || USB-C, 4xUSB-A, HDMI || {{G|Working}}<br />
|-<br />
| [http://www.belkin.com/us/p/P-F2CU037/ Belkin USB-C to VGA Adapter] || VGA || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/dp/B012DT6KW2 Dell DA200] || USB-A, Ethernet, HDMI, VGA || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/dp/B01FN1YK92 Dell WD15 130W] || 3xUSB-A 3.0, 2xUSB-A 2.0, Ethernet, HDMI, Mini DisplayPort, VGA, Line Out, Line In || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/dp/B01ANR4CYE StarTech.com tb32dp2 - Thunderbolt 3 Adapter] || 2 x DP (4 K, 60 Hz) || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/dp/B01C316EIK Cable Matters USB-C Multiport Adapter] || 4K HDMI or VGA, USB 3.0, Gigabit Ethernet || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/Juiced-BizHUB-Multiport-Ethernet-Delivery/dp/B01J391C3W Juiced Systems BizHUB USB-C Multiport Gigabit HDMI Hub] || 4K@30Hz HDMI, 3x USB 3.0, Gigabit Ethernet, USB-C Power, SD, Micro-SD || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/Anker-Adapter-Supports-Macbook-Chromebook/dp/B01MYUCWOK/ Anker USB-C to HDMI Adapter] || 4K@60Hz HDMI || {{G|Working}}<br />
|-<br />
| [http://www.pct-max.com.tw/cht/products.php?index=289 PCT UHC304] || HDMI (4K@30Hz, 2K@60Hz), Gigabit Ethernet, USB-A, USB-C || {{G|Working}}<br />
|-<br />
| [https://www.i-tec-europe.eu/?lng=en&t=3&v=443 i-Tec USB-C Dual Display MST Dock] || HDMI, DP (4K@30Hz Single Monitor, 1920x1200@60Hz Dual Monitor), Gbit Ethernet, 3xUSB-A, USB-C, Sound, Charging @ 60W || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/Tripp-Lite-External-Charging-U444-06N-DGU-C/dp/B01LYQB1XI Tripp Lite USB-C to DVI External Video Adapter] || DVI, Gbit Ethernet, USB-A, USB-C PD Charging Port || {{G|Working}}<br />
|-<br />
| [https://www.startech.com/nl/en/AV/usb-c-video-adapters/usb-c-hdmi-adapter~CDP2HD StarTech CDP2HD - USB-C to HDMI Adapter] || HDMI || {{G|Working}}<br />
|-<br />
| [https://www.amazon.com/Kanex-USB-C-Adapter-Inches-White/dp/B00VBNSY0S Kanex USB-C to HDMI 4K Adapter] || HDMI || {{G|Working}}<br />
|}<br />
<br />
=== Thunderbolt Firmware updates ===<br />
The thunderbolt controller in the laptop has an embedded firmware. The laptop ships with firmware version NVM 18, and the most recent available version from Dell's website is NVM 21. If encountering compatibility problems with Thunderbolt accessories, the firmware may need to be updated. Dell maintains a [https://github.com/dell/thunderbolt-nvm-linux Github repository] explaining the process to update the firmware, but unfortunately, does not provide the updated payload files. These can be extracted from the Windows firmware update files. Mainline support for the firmware update process is pending the inclusion of [https://github.com/01org/thunderbolt-software-kernel-tree/tree/networking these patches] into the Linux kernel.<br />
<br />
Here is a short list of steps to update the Thunderbolt-Firmware (use at your own risk):<br />
<br />
* Install {{AUR|thunderbolt-icm-dkms-git}}, {{AUR|thunderboltd-git}}, {{AUR|libtbtfwu-git}} and {{AUR|tbtfwucli-git}}<br />
* Load the thunderbolt-icm kernel module and start thunderbolt.service<br />
* Download the Intel_TBT3_FW_UPDATE_*.exe from Dell's website<br />
* Unpack the exe with 7z x Intel_TBT3_FW_UPDATE_*.exe<br />
* Follow the update instructions at [https://github.com/dell/thunderbolt-nvm-linux Dell's TB Github repository], Using the correct Firmware file from the extracted exe (Intel/0x075B.bin for the 9360 according to the info in Dell's Repository<br />
* Hope everything goes well and reboot after finishing the update<br />
<br />
== SATA controller ==<br />
When the SATA-controller is set to {{ic|RAID On}} in Bios, the hard disk (at least the SSD) is not recognized. Set to {{ic|Off}} or {{ic|AHCI}} ({{ic|AHCI}} is recommended) before attempting to install Arch.<br />
<br />
== Touchpad ==<br />
The touchpad has no explicit buttons. The buttons are built into the pads surface. There is a small line printed on the pad separating left from right click button. The pad has a '''middle button''' built in! (works with libinput without any configuration): To issue a middle click, simply press on the middle area right between the virtual left and click buttons - so on the small printed separator line.<br />
<br />
=== Remove psmouse errors from dmesg ===<br />
<br />
If {{ic|<nowiki>dmesg | grep -i psmouse</nowiki>}} returns an error, but your touchpad still works, then it might be a good idea to disable {{ic|psmouse}}. First create a config file:<br />
<br />
# nano /etc/modprobe.d/modprobe.conf<br />
<br />
blacklist psmouse<br />
<br />
Then add this file to {{ic|/etc/mkinitcpio.conf}}:<br />
<br />
...<br />
FILES="/etc/modprobe.d/modprobe.conf"<br />
...<br />
<br />
Rebuild your initial ramdisk image (see [[Mkinitcpio#Image creation and activation]]).<br />
<br />
== Touchscreen ==<br />
The touchscreen works without additional configuration. The bug resulting in a disabled touchscreen after resume was fixed with kernel 4.8.5.<br />
<br />
=== Gestures ===<br />
Refer to [[libinput#Gestures]] for information about the current development state and available methods.<br />
<br />
=== Scrolling in Firefox ===<br />
See [[Firefox/Tweaks#Pixel-perfect trackpad scrolling]]. This enables both touchscreen scrolling and high-res trackpad scrolling.<br />
<br />
== Keyboard Backlight ==<br />
By default, the keyboard backlight turns off after 10 seconds of inactivity. Some users might find this too short and annoying.<br />
The delay can be increased (or decreased) by editing this file:<br />
/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout<br />
<br />
You can also change the brightness (0-2) by editing the following file. This is identical to pressing F10 on your keyboard:<br />
/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/brightness<br />
<br />
== Hidden Keyboard Keys ==<br />
There are additional Fn+<Key> (sequences) that are not marked at all on the keyboard but underlying hardware generates them anyway. Here they are (if you find more add them to the table below):<br />
{| class="wikitable"<br />
|+ Hidden Fn Keys<br />
! Fn+<Key> !! Resulting key (sequence)<br />
|-<br />
| Fn+Ins || XF86Sleep<br />
|-<br />
| Fn+Super_L || Super_R<br />
|-<br />
| Fn+B || Pause<br />
|-<br />
| Fn+R || Print<br />
|-<br />
| Fn+S || Scroll_Lock<br />
|-<br />
| Fn+A / D / E / F / G / T / Q / W || XF86Launch3<br />
|}<br />
<br />
== Firmware Updates ==<br />
Dell provides firmware updates via {{aur|fwupd}}. See [[Flashing BIOS from Linux#fwupd]]. Please note if you have used a bind mount partition for /boot, you will not be able to use the fwupd utility; Instead format a USB as FAT32 and put the bios update .exe on. Reboot into the one-time-boot menu and update the BIOS flash through there.<br />
<br />
Alternatively, the BIOS update can be downloaded from the Dell website, and placed in a location accessible to the firmware. This could be the '/boot' folder, or a FAT32 formatted USB stick. Then restart your laptop and hit F12 while starting. In the boot menu choose firmware update and select the new file!<br />
<br />
== Troubleshooting ==<br />
<br />
=== EFISTUB does not boot ===<br />
The BIOS does not pass any boot parameters to the kernel. Use a UEFI [[boot loader]] instead.<br />
<br />
=== Not waking from suspend ===<br />
Update the BIOS to 1.0.7 to patch this issue.<br />
<br />
=== Power Drain after waking from standby ===<br />
<br />
Some users recognised ~2W more power consumption after waking up from standby. Go to the UEFI Firmware Settings (tap the F2 key when the Dell logo appears) and uncheck the 'Enable Thunderbolt Boot Support'. You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour yourself. <br />
<br />
=== Popping Sound on headphones/external speakers ===<br />
<br />
Power saving being enabled on the audio chip will cause the hissing and popping to appear. <br />
<br />
Have a look at [[Advanced Linux Sound Architecture/Troubleshooting#Pops when starting and stopping playback]] and [[Advanced Linux Sound Architecture/Troubleshooting#Popping sound after resuming from suspension]].<br />
<br />
If you are using {{Pkg|tlp}}, it will activate power saving by default when on battery. Edit {{ic|/etc/default/tlp}} and disable it.<br />
<br />
=== Coil Whine ===<br />
<br />
Unfortunately Dell still did not fix this issue and the sound for my model was very loud. The issue seems to be connected to the graphic card. For some users, it is possible to reduce it a lot by activating frame buffer compression "enable_fbc=1" [[Intel graphics#Module-based Powersaving Options]]. The coil whine will then start again under heavy graphic load. For the touchscreen model, this may be very often, due to the high resolution screen. In a similar vein, the display can be run at a lower resolution, again reducing the load on the graphics card.<br />
<br />
=== Freezing after waking from suspend ===<br />
<br />
Installing {{aur|xf86-video-intel-git}} is [https://bbs.archlinux.org/viewtopic.php?pid=1698282#p1698282 reported] to fix this.<br />
<br />
=== Continuous hissing sound with headphones ===<br />
<br />
Open alsamixer and set "Headphone Mic Boost" gain to 10 dB (See discussion on [https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ reddit]). Note that this does reduce the volume slightly.<br />
<br />
You may also run the equivalent command:<br />
<br />
$ amixer -c PCH cset 'name=Headphone Mic Boost Volume' 1<br />
<br />
== See Also == <br />
<br />
* [https://bbs.archlinux.org/viewtopic.php?id=217865 Arch Forum thread for Dell XPS 13 (9360)]<br />
* [http://topics-cdn.dell.com/pdf/xps-13-9360-laptop_Service%20Manual_en-us.pdf Service Manual for Dell XPS 13 (9360)]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Arch_Linux_on_a_VPS&diff=382202Arch Linux on a VPS2015-07-15T08:52:07Z<p>Latgarf: Added new provider to the list. Moved Edis to the alphabetically correct place.</p>
<hr />
<div>[[Category:Getting and installing Arch]]<br />
[[Category:Virtualization]]<br />
{{Related articles start}}<br />
{{Related|Server}}<br />
{{Related articles end}}<br />
[[ja:Virtual Private Server]]<br />
[[zh-CN:Virtual Private Server]]<br />
From [[Wikipedia:Virtual private server]]:<br />
<br />
:''Virtual private server (VPS) is a term used by Internet hosting services to refer to a virtual machine. The term is used for emphasizing that the virtual machine, although running in software on the same physical computer as other customers' virtual machines, is in many respects functionally equivalent to a separate physical computer, is dedicated to the individual customer's needs, has the privacy of a separate physical computer, and can be configured to run server software.''<br />
<br />
This article discusses the use of Arch Linux on Virtual Private Servers, and includes some fixes and installation instructions specific to VPSes.<br />
<br />
{{Warning|<br />
* Linux 2.6.32 is not supported by systemd since version 205 (and will not work with systemd-212 or higher). Since many container-based virtualization environments rely on older kernels, it may be impossible to keep an Arch Linux install up-to-date in such an environment. However, OpenVZ, as of [http://openvz.org/Download/kernel/rhel6/042stab094.7 kernel build 042stab094.7], has backported the CLOCK_BOOTTIME feature and now works with the latest systemd.<br />
* Systemd since version 220 doesn't work on OpenVZ containers. [https://github.com/systemd/systemd/issues/421]}}<br />
<br />
==Providers that offer Arch Linux==<br />
<br />
{{Warning|We cannot vouch for the honesty or quality of any provider. Please conduct due diligence before ordering.}}<br />
{{Note|This list is for providers with a convenient Arch Linux template. Using Arch on other providers is possible but requires more work. Example methods include: <br />
* Loading custom disc images (requires hardware virtualization such as in Xen or KVM), <br />
* [[Installation guide|Installing under chroot]], for example with the help of the [https://github.com/drizzt/vps2arch vps2arch] script (it will download the latest iso; be particularly aware of the systemd 220/221 [https://github.com/systemd/systemd/issues/421 bug]), or <br />
* Following [[#Installing the latest Arch Linux on any OpenVZ provider]] instructions, using rsync to synchronize Arch over the top of another distribution.}}<br />
<br />
{| class="wikitable"<br />
! Provider !! Arch Release !! Virtualization !! Locations !! Notes<br />
|-<br />
| [http://www.milesweb.com/vps-hosting.php A MilesWeb VPS] || 2013.10.14 || OpenVZ || Europe, India, US || Latest Arch Linux available on OpenVZ platform. Quick setup, 24/7 support via Live Chat, Email and Phone. VPS starts from $20 / mo<br />
|-<br />
| [http://123systems.net 123 Systems] || 2010.05.xx || OpenVZ || Dallas, US-TX || Arch available as a selection upon reinstall. Very old (2.6.18-308) kernel - See [[#OpenVZ: kernel too old for glibc|OpenVZ troubleshooting]]. Limited information available before purchase. Cannot verify Arch Linux version without purchase.<br />
|-<br />
| [http://ausweb.com.au AUSWEB] || Latest Only (clarify?) || VMware ESXi || Sydney, AU || Latest ISO (clarify?) of Arch Available. Enterprise Service. <br />
|-<br />
| [https://www.affinity.net.nz affinity.net.nz] || 2013.08.01 || KVM || Auckland, New Zealand (NZ) || IRC channel is #affinity on ircs.kiwicon.org<br />
|-<br />
| [http://afterburst.com/ Afterburst] || 2012.12.01 || OpenVZ || Miami, US-FL; Nuremberg, DE || Formerly FanaticalVPS, kernel version depends on what node your VPS is on, the ones in Miami are fine (2.6.32-042stab072.10) but some of the ones in Germany require a [[#OpenVZ: kernel too old for glibc|custom glibc]].<br />
|-<br />
| [http://www.atlantic.net/ Atlantic.Net] || 2015.05.01 || KVM || NYC/SF/Toronto/Dallas/Orlando, US & Canada || 100% SSD 1-click ArchLinux from $5/mo for 512M/20GB SSD, ready in 30 seconds<br />
|-<br />
| [http://www.buyvm.net/ BuyVM] || 2013.07.01 || KVM || LA, Buffalo NY || Must chose a different OS at sign up. Once accessible, choose to mount the latest Arch ISO and reboot to install manually. <br />
|-<br />
| [https://coinshost.com/en/vps Coinshost] || 2015.04 || Xen || Zurich, Switzerland || $3/mo for 512M/20GB. Bitcoin and other cryptocurrencies accepted.<br />
|-<br />
| [https://www.directvps.nl/ DirectVPS] || 2014.01.xx || OpenVZ || Amsterdam, NL; Rotterdam, NL || Dutch language site. Version verifyable by clicking through https://www.directvps.nl/try-1.plp?p=31<br />
|-<br />
| [http://en.edis.at/ Edis] || [http://www.edis.at/en/support-and-service/faq/server-faq/which-distributions-are-available-with-edis-kvm-vps-plans/ 2013.03.01] || vServer, KVM, OpenVZ || [http://www.edis.at/en/server/kvm-vps/austria/ Multiple international locations]. || Also offer dedicated server options as well as an "off-shore" location at the Isle of Man (IM).<br />
|-<br />
| [https://www.gandi.net/hosting/ Gandi] || 2013.10.27 || Xen || Paris, FR; Baltimore, MD, US; Bissen, LU || Very granular scaling of system resources (e.g. RAM, disk space); IPv6-only option available; you can supply your own install image, version based on keyring package version ||<br />
|-<br />
| [https://www.gigatux.com/virtual.php GigaTux] || [https://www.gigatux.com/distro/ 2013.06.01] || Xen || Chicago, US-IL; Frankfurt, DE; London, GB; San Jose, US-CA ||<br />
|-<br />
| [http://www.vr.org/ Host Virtual] || [http://www.vr.org/os/linux-vps/archlinux-vps 2011.08.19] || KVM || [http://www.vr.org/cloud-locations/ Multiple International Locations] || Appears to use KVM virtualization. Site lists "Xen based virtualization" and [http://www.vr.org/features/ features] lists ability to install from ISO.<br />
|-<br />
| [https://hostigation.com/ Hostigation] || [https://hostigation.com/wiki/index.php?title=KVM:Install 2010.05 i686] || OpenVZ, KVM || Charlotte, US-NC; Los Angeles, US-CA || You can [[Migrating Between Architectures Without Reinstalling|migrate to x86_64]].<br />
|-<br />
| [http://www.intovps.com IntoVPS] || 2012.09.xx || OpenVZ || Amsterdam, NL; Bucharest, RO; Dallas, US-TX; Fremont, US-CA; London, GB || Blog has not been updated since September, 2012 which included the Arch Linux update.<br />
|-<br />
| [https://leapswitch.com Leapswitch Networks] || [2013.10.xx] || OpenVZ/KVM || USA, India, Portugal, Spain, Ukraine, Germany || ArchLinux currently available in Control Panel for reinstall, not on order form. <br />
|-<br />
| [https://www.linode.com Linode.com] || [https://www.linode.com/faq.cfm 2013.06.xx] || Xen, KVM || [https://www.linode.com/speedtest/ Tokyo, JP; Multiple US; London, GB] || To run a custom kernel, install {{AUR|linux-linode}}. ({{pkg|linux}} will break on a 32-bit Linode.)<br />
|-<br />
| [http://lylix.net/ LYLIX] || [http://lylix.net/archlinux 2014.01.xx] || OpenVZ || Multiple US; Europe || 32-bit and 64-bit available <br />
|-<br />
| [http://www.nodedeploy.com Node Deploy] || 2014.10.01 || OpenVZ, KVM || Germany (DE); Los Angeles, US-CA; Atlanta, US-GA; Phoenix, US-AZ || "At NodeDeploy we support virtually every linux distribution." Arch Linux is listed under their Operating Systems. No version information.<br />
|-<br />
| [http://netcup.de Netcup] || 2012.11.xx || KVM || Germany (DE)|| German language site. <br />
|-<br />
| [http://onepoundwebhosting.co.uk OnePoundWebHosting] || 2013.05.xx || Xen PV, Xen HVM || United Kingdom (UK) || They are a registrar too. Unable to verify server locations.<br />
|-<br />
| [https://www.proplay.biz/ proPlay.de] || 2012.12.xx || OpenVZ, KVM || Germany (DE) || German language site.<br />
|-<br />
| [https://www.quickvz.com QuickVZ] || 2013.10 || OpenVZ, Xen || Amsterdam, Netherlands (NL); Stockholm, Sweden (SE) || Provide hardened Arch Linux images along with Enterprise services (e,g. VPN, Virtual Private LAN Service (VPLS) and Virtual Routers.<br />
|-<br />
| [http://www.rackspace.com/cloud/cloud_hosting_products/servers/ Rackspace Cloud] || 2013.6 || Xen || [https://www.rackspace.com/whyrackspace/network/datacenters/ Multiple international locations] || Billed per hour. Use their "next gen" VPSes (using the mycloud.rackspace.com panel); the Arch image on the first gen Rackspace VPSes is out of date.<br />
|-<br />
| [http://www.ramhost.us RamHost.us] || [http://www.ramhost.us/?page=news 2013.05.01] || OpenVZ, KVM || Los Angeles, US-CA; Great Britain (GB); Atlanta, US-GA; Germany (DE) || You can request a newer ISO on RamHost's IRC network.<br />
|-<br />
| [http://www.ramnode.com RamNode] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=48 2013.07.01] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=39 SSD and SSD Cached:] [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=52 OpenVZ, KVM] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=18 Seattle, WA USA, Atlanta, GA USA] || [https://clientarea.ramnode.com/knowledgebase.php?action=displayarticle&id=66 You can request Host/CPU passthrough with KVM service.] [http://www.ramnode.com/about.php Customer service has been prompt and professional.] [https://twitter.com/search?q=ramnode%20code&src=typd Regular discount codes can be found (15-35% off).] [http://www.ramnode.com/index.php Modern hardware.] [https://clientarea.ramnode.com/cart.php?carttpl=svz Competitive pricing (before discounts).]<br />
|-<br />
| [http://www.tilaa.nl/ Tilaa] || 2014.10.01 || [https://www.tilaa.com/pages/vps/technology KVM] || Amsterdam, NL || English or Dutch language site.<br />
|-<br />
| [https://www.transip.eu/ TransIP] || [https://www.transip.eu/vps/vps-os/ 2013.05.01] || [https://www.transip.eu/vps/vps-technology/ KVM] || Amsterdam, NL || English language site. Registrar.<br />
|-<br />
| [http://www.xenvz.co.uk/ XenVZ] || 2009.12.07 || OpenVZ, Xen || United Kingdom (UK), United States (US) || [http://www.xenvz.co.uk/faq.php#use2 Hardware]<br />
|-<br />
| [http://www.virpus.com/ Virpus] || [http://virpus.com/linux-vps.php 2014.11.07] || Xen || Kansas City, US-KS; Los Angeles, US-CA || A subcompany of Wow Technologies, Inc. 24/7 support via Live Chat, Email, Phone, and Ticket System. Service starts at $5/month.<br />
|-<br />
| [http://www.vmline.pl/ Vmline] || 2013.09.01 || KVM, OpenVZ || Kraków, PL || [http://www.s-net.pl/en/ S-Net] reseller. Full virtualization. Polish language site.<br />
|-<br />
| [https://vpsbg.eu/ VPSBG.eu] || 2013.10 || OpenVZ || [https://vpsbg.eu/en/index.php?page=vps-datacenter Sofia, Bulgaria] || Offshore VPS in Bulgaria - anonymous registrations and Bitcoin are accepted.<br />
|-<br />
| [https://vps6.net/ VPS6.NET] || 2013.01.xx || OpenVZ, Xen, HVM-ISO || [http://vps6.net/network/ Multiple US]; Frankfurt, DE; Bucharest, RO; Istanbul, TR || Registrar.<br />
|-<br />
| [http://www.vps.net/ VPS.NET] || 2014.01.xx || OpenVZ, Xen, HVM-ISO || [http://vps.net/cloud-datacenter-locations US, Canada, UK, Brazil, Netherlands, France, Germany, Japan, Singapore, India, Austrlia]; Multiple || Managed & Un managed VPS service provider, multiple OS and configurations..<br />
|- <br />
| [http://www.world4you.com/ World4You] || 2015.02.17 || OpenVZ || Austria (AT) || Internet hosting provider; quick setup; 24/7 support; shared web hosting; also CentOS, Debian, Ubuntu, Fedora and Arch OpenVZ servers; starts with €2.5/month<br />
|-<br />
|}<br />
<br />
==Installation==<br />
<br />
===KVM===<br />
{{Expansion|Are there instructions specific to VPSes?}}<br />
See [[QEMU#Preparing an (Arch) Linux guest]].<br />
<br />
===OpenVZ===<br />
<br />
====Installing the latest Arch Linux on any OpenVZ provider====<br />
<br />
{{Warning|See the [[#top|above warning]] about older kernel builds and systemd.}}<br />
<br />
It is possible to directly copy an installation of Arch Linux over the top of a working OpenVZ VPS. This tutorial explains how to create a basic installation of Arch Linux with {{ic|pacstrap}} (as used in a standard install) and then replace the contents of a target VPS with it using [[rsync]].<br />
<br />
This process (with minor modification) also works to migrate existing Arch installations between various environments and has been confirmed to work in migrating from OpenVZ to Xen and from Xen to OpenVZ. For an install to Xen, other hardware-virtualized platforms, or probably even to physical hardware (unconfirmed), extra steps (basically running {{ic|mkinitcpio}} and [[Boot loaders|installing a bootloader]]) are needed.<br />
<br />
=====Prerequisites=====<br />
<br />
* A working Arch Linux installation<br />
** To keep things simple, it should match the architecture you want to install on your VPS (x86_64 or i686).<br />
** To build from other distributions, [[Archbootstrap|arch-bootstrap.sh]] can be used in place of {{ic|pacstrap}}.<br />
* The {{Pkg|arch-install-scripts}}, {{Pkg|rsync}}, and {{Pkg|openssh}} packages from the [[official repositories]]<br />
** SSH is not strictly required, but rsync over SSH is the method used here.<br />
* A VPS running any distribution, with {{ic|rsync}} and a working SSH server<br />
** Its architecture (x86_64 or i686) does not matter as long as the OpenVZ installation can support your target architecture.<br />
* OpenVZ's serial console feature (usually accessible via your provider's control panel)<br />
** Without this, any network configuration for the target VPS will have to be done immediately after the "Build" step below.<br />
<br />
=====Building a clean Arch Linux installation=====<br />
<br />
As root, build the installation (optionally replacing {{ic|build}} with your preferred target directory):<br />
<br />
# mkdir build<br />
# pacstrap -cd build<br />
<br />
Other tweaks for the {{ic|pacstrap}} command:<br />
<br />
*{{ic|-C custom-pacman-config.conf}} - Use a custom pacman configuration file. By default, pacstrap builds according to your local pacman.conf. This determines the architecture (i686 or x86_64) of the build, the mirror list, etc.<br />
*{{ic|-B}} - Prevent pacstrap from copying your system's pacman keyring to the new build. If you use this option, you will need to run {{ic|pacman-key --init}} and {{ic|pacman-key --populate archlinux}} in the [[#Configuration|Configuration]] step to set up the keyring.<br />
*{{ic|-M}} - Prevent pacstrap from copying your system's pacman mirror list to the new build.<br />
<br />
=====Replacing everything on the VPS with the Arch build=====<br />
<br />
Replace all files, directories, etc. on your target VPS with the contents of your {{ic|build}} directory (replacing "YOUR.VPS.IP.ADDRESS" below):<br />
<br />
{{Warning|Be careful with the following command. By design, {{ic|rsync}} is very destructive, especially with any of the {{ic|--delete}} options.}}<br />
<br />
# rsync -axH --delete-delay -e ssh --stats -P build/ YOUR.VPS.IP.ADDRESS:/<br />
<br />
Explanation of options:<br />
<br />
At minimum, only the {{ic|-a}} (preserve timestamps, permissions, etc.), {{ic|-x}} (do not cross filesystem boundaries), and {{ic|--delete}} (delete anything in the target that does not exist in the source) options are required. The {{ic|--delete-delay}} option is an alternate deletion mode which waits to delete anything until the synchronization is otherwise complete; this is not necessary but may reduce the risk of a slow transfer causing the target VPS to lock-up. The {{ic|-H}} causes hardlinks to be preserved. The {{ic|-e ssh}} (use rsync over SSH) option is recommended and makes things simple. The {{ic|--stats}} and {{ic|-P}} options are just to show more information.<br />
<br />
=====Configuration=====<br />
<br />
# Reboot the VPS externally (using your provider's control panel, for example).<br />
# Using OpenVZ's serial console feature, configure the [[network]] and [[Installation_guide#Configure_the_system|basic system settings]] (ignoring fstab generation and arch-chroot steps).<br />
#* If you do not have access to the serial console feature, you will need to preconfigure your network settings before synchronizing Arch to the VPS.<br />
<br />
===Xen===<br />
{{Expansion|Are there instructions specific to VPSes?}}<br />
See [[Xen#Arch as Xen guest (PVHVM mode)]] and/or [[Xen#Arch as Xen guest (PV mode)]].</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:USB_flash_installation_medium&diff=265377Talk:USB flash installation medium2013-07-07T15:15:58Z<p>Latgarf: /* dosfslabel */ new section</p>
<hr />
<div><br />
== Verifying the USB ==<br />
<br />
Before and after having performed the dd onto the USB disk, check that the md5sums are correct. For example:<br />
<br />
- $ md5sum archlinux-2008.06-core-x86_64.img && echo && cat md5sums.x86_64<br />
<br />
The next command will give similar results, but will also let you confirm that the data was written correctly and can be read correctly:<br />
- dd if=/dev/sdb count=661159 status=noxfer | md5sum && echo && cat md5sums.x86_64<br />
<br />
--[[User:Zatricky|Zatricky]] 06:45, 22 January 2009 (EST)<br />
<br />
== dd for Windows ==<br />
<br />
There is also '''dd''' for Windows. I tried it and it works perfectly: [http://www.chrysocome.net/dd]<br />
<br />
dd if=file.img of=\\.\e:<br />
<br />
where '''e:''' is your USB drive letter.<br />
<br />
--[[User:Liquen|Liquen]] 14:55, 4 April 2009 (EDT)<br />
<br />
== About making the installation media without overwriting ==<br />
<br />
I'm not totally sure if I misunderstood something, but I had to change the path of the entries of the *.cfg files. For instance:<br />
<br />
INCLUDE boot/syslinux/archiso_sys.cfg<br />
<br />
became:<br />
<br />
INCLUDE syslinux/archiso_sys.cfg<br />
<br />
It was the only way it worked with the unofficial ISO x86_64 image of march 13th, 2012. Looks like the syslinux command described in the page doesn't get the path as it should. <br />
<br />
I edited all of the .cfg files, but probably only editing this ones should have been enough:<br />
<br />
archiso.cfg<br />
archiso_head.cfg<br />
archiso_sys_inc.cfg<br />
<br />
I hope it could be useful to somebody, because I spend some time with this (I even thought that was a problem with the hardware). I think it could be possible to make a simple script (or give some command lines) to patch the files once they are copied into the USB and run syslinux.<br />
<br />
Thanks !!<br />
<br />
== Recovering the USB drive afterwards ==<br />
<br />
This didn't work for me:<br />
<br />
# dd count=1 bs=512 if=/dev/zero of=/dev/sdx<br />
<br />
I tried this multiple times. No matter how I formatted the disk, 'devmon' always mounted '/dev/sdd' as /media/ARCH_whatever.<br />
<br />
I finally just zeroed as much of the disk as I thought the ISO might have been written to.<br />
<br />
# dd count=100 bs=4M if=/dev/zero of=/dev/sdx; sync<br />
<br />
That worked. I believe we need to zero MORE than just the initial 512 bytes, but I have no idea how much. Maybe 2048?<br />
<br />
At any rate, put '; sync' in there somewhere.<br />
<br />
This is what I did eventually, taking a tip from:<br />
[http://www.patriotmemory.com/forums/showthread.php?3696-HOWTO-Increase-write-speed-by-aligning-FAT32]<br />
<br />
# dd count=100 bs=4M if=/dev/zero of=/dev/sdx; sync<br />
# fdisk -H 224 -S 56 /dev/sdx<br />
<br />
(new partition, primary, 1, 2048, whatever, type of partition, c (fat32 LBA), x, beginning data sector, 256, write)<br />
<br />
# mkfs.vfat -F 32 -n volume_label -s 32 -v /dev/sdx1; sync<br />
<br />
See the link for more details on the beginning data sector.<br />
<br />
* Um, zeroing out the first 512 bytes is fine for MBR-formatted drives. Were you using GPT? Because then you would need to zero out the first 512+512+16k, and the last 16k+512. See [[GPT]]. But assuming you used {{ic|dd}}, we're talking about MBR-formatted because the ISO contains a MBR (hybrid) partition table.--[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 06:25, 8 September 2012 (UTC)<br />
<br />
== flush file system buffers after dd ==<br />
<br />
I found that after using dd to write the data to my USB I had to wait for the file system to actually write it to my drive. (as dd completed and returned its stats) <br />
This could cause confusion, should we add 'sync' after the dd command on the artical?<br />
<br />
== Rationale for block size ==<br />
<br />
Why specifically ''bs=4M'' in the [[USB_Installation_Media#Overwrite_the_USB_drive|example]]:<br />
[[USB_Installation_Media#Overwrite_the_USB_drive|# dd '''bs=4M''' if=/path/to/archlinux.iso of=/dev/sdx]]<br />
[[User:NoobCp|NoobCp]] ([[User talk:NoobCp|talk]]) 11:08, 20 December 2012 (UTC)<br />
<br />
:Because it speeds up the process, that's why. I guess somebody decided that one warning, two notes and a tip would be too rainbow-like. See [https://wiki.archlinux.org/index.php?title=USB_Installation_Media&oldid=218405 this] older edit (which references [http://sprunge.us/SGIY this] script). I reduces the time it needs almost by half. --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 12:17, 4 February 2013 (UTC)<br />
<br />
==<s>UNetbootin should be removed</s>==<br />
<br />
I think UNetbootin should be removed. It was just added more information that basically tells you to use something else. This program is way too intrusive. It installs its own version of the bootloader, a crappy syslinux.cfg, and doesn't give a shit about labels. Unetbootin is totally NOT recommended for Arch Linux and it should be removed from the wiki. --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 11:20, 16 September 2012 (UTC)<br />
:Thanks. Good riddance! But, perhaps we should keep the warning? Or just refer them to this discussion page. --[[User:DSpider|DSpider]] ([[User talk:DSpider|talk]]) 06:01, 17 September 2012 (UTC)<br />
:: This is not the first time UNetbootin info is added and then removed (sadly by me.). Search the history you will find the same topic show up long time ago. If it is broken, we'd better clearly tell people it is broken. And it can prevent it from being recommended again. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 10:30, 17 September 2012 (UTC)<br />
:::Yes, please don't take example from what [[User:Danielwallace]] did; content should never be removed without at least a valid explanation in the edit summary, and anyway, in this case UNetbootin must be mentioned, even only as an non-recommended, discouraged alternative in a Warning: following the philosophy of the ArchWiki and Arch Linux in general, no available option must be hidden to the users, who are the only ones who can choose what's best for themselves in the end. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 13:22, 17 September 2012 (UTC)<br />
:::: Deletion reverted. Close. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 12:09, 24 September 2012 (UTC)<br />
:::::Reopening as the section has been restored. My opinion is unchanged. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 07:16, 20 April 2013 (UTC)<br />
::::::I'm sorry for re-opening the section but it was my first time that I wrote on this wiki. I know that UNetbooting overwrite the syslinux.cfg, infact my guide is to edit that file to permit the boot of the installation media. So I think you could remove the disclaimer. [[User:Mathias|Mathias]] ([[User talk:Mathias|talk]]) 14:44, 21 April 2013 (UTC)<br />
:::::::Lol, silly me, I added the disclaimer back without re-reading the section just because I remembered this has been the cause of some edit warring in the past, sorry... Of course you're right, however I've merged the disclaimer into the introduction paragraph in order to try to prevent future disputes. Closed (again). -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:57, 22 April 2013 (UTC)<br />
::::::::It appears to me that there has been an increase in the number of new users attempting to use unetbootin (and failing) since this section was changed. I think this tool should be more strongly discuraged. There really is no reason to use it, even with the syslinux warning. I'd like to at least amplify the warning about using another tool, and ideally return the original warning from DSpider (Do Not Use UNETBOOTIN). [[User:2ManyDogs|2ManyDogs]] ([[User talk:2ManyDogs|talk]]) 19:59, 13 June 2013 (UTC)<br />
:::::::::I admit it's been a while since I last tested UNetbootin: is the procedure described in the article working or not? In any case yes, please expand the warning about using another tool, specifying the reason ''why'' UNetbootin is worse. However let's not delete the section again, otherwise this cycle of deletions and restorations will never end... -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:25, 15 June 2013 (UTC)<br />
::::::::::It works, but it breaks syslinux.cfg so the USB stick does not boot properly. This is explained at the top of the topic. I changed the "Note" to a "Warning" and added a little more text to the first paragraph. I think this is sufficient for now. (I agree deleting the section is not the best solution -- I just wanted the warnings to be a bit stronger) [[User:2ManyDogs|2ManyDogs]] ([[User talk:2ManyDogs|talk]]) 15:49, 15 June 2013 (UTC)<br />
:::::::::::Ok, let's try to close this discussion again ^^ -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:41, 16 June 2013 (UTC)<br />
<br />
== dosfslabel ==<br />
<br />
{{ic|dosfslabel}} package is not in repositories :(</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Zenbook_Prime_UX31A&diff=264412Talk:ASUS Zenbook Prime UX31A2013-06-27T03:25:11Z<p>Latgarf: /* Terminal commands for Function Keys */</p>
<hr />
<div>== Clean up ==<br />
I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official [[Installation Guide]]. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. [[User:Drenninghoff|Drenninghoff]] ([[User talk:Drenninghoff|talk]])<br />
<br />
== Other function keys ==<br />
I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are '''not''' working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?<br />
<br />
Additionally the following info box says that since a ''newer'' kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...<br />
<br />
*"Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 21:26, 31 August 2012 (UTC)<br />
<br />
* Ah, I see! Thanks for the explanation. [[User:Mqt|Mqt]] ([[User talk:Mqt|talk]]) 21:42, 31 August 2012 (UTC)<br />
<br />
== Installation section ==<br />
<br />
The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...<br />
<br />
So I think that all the additional steps about encryption should be clearly flagged at optional. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 10:12, 1 September 2012 (UTC)<br />
<br />
I completely agree [[User:Nihathrael|Nihathrael]] ([[User talk:Nihathrael|talk]]) 21:27, 14 September 2012 (UTC)<br />
<br />
== HDMI Audio Sandbox ==<br />
<br />
This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right <br />
<br />
=== HDMI Audio ===<br />
<br />
The UX31A contains the following PCI souncard:<br />
<br />
$ lspci -nnn -k | grep -i audio<br />
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)<br />
<br />
This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.<br />
<br />
You will need the snd-hda-hdmi module:<br />
<br />
$ lsmod | grep hda<br />
snd_hda_codec_hdmi 21095 1 <br />
snd_hda_codec_realtek 49734 1 <br />
snd_hda_intel 22373 2 <br />
snd_hda_codec 71565 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel<br />
snd_pcm 60543 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel<br />
snd_page_alloc 5921 2 snd_pcm,snd_hda_intel<br />
snd_hwdep 5061 1 snd_hda_codec<br />
snd 48443 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel<br />
<br />
=== UDEV ===<br />
Here is how udev sees plugging in the HDMI cable:<br />
<br />
$ udevadm monitor<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
KERNEL[96692.710767] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
UDEV [96692.712940] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
<br />
=== Pulseaudio ===<br />
<br />
To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
<br />
Pulseaudio sees the soundcard as follows:<br />
<br />
$ pacmd list-cards<br />
Welcome to PulseAudio! Use "help" for usage information.<br />
>>> 1 card(s) available.<br />
index: 0<br />
name: <alsa_card.pci-0000_00_1b.0><br />
driver: <module-alsa-card.c><br />
owner module: 4<br />
properties:<br />
alsa.card = "0"<br />
alsa.card_name = "HDA Intel PCH"<br />
alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"<br />
alsa.driver_name = "snd_hda_intel"<br />
device.bus_path = "pci-0000:00:1b.0"<br />
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"<br />
device.bus = "pci"<br />
device.vendor.id = "8086"<br />
device.vendor.name = "Intel Corporation"<br />
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"<br />
device.form_factor = "internal"<br />
device.string = "0"<br />
device.description = "Built-in Audio"<br />
module-udev-detect.discovered = "1"<br />
device.icon_name = "audio-card-pci"<br />
profiles:<br />
output:analog-stereo: Analog Stereo Output (priority 6000)<br />
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)<br />
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)<br />
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)<br />
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)<br />
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)<br />
input:analog-stereo: Analog Stereo Input (priority 60)<br />
off: Off (priority 0)<br />
active profile: <output:hdmi-stereo><br />
sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)<br />
sources:<br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)<br />
ports:<br />
analog-output-speaker: Speakers (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-output-headphones: Headphones (priority 9000, available: no)<br />
properties:<br />
<br />
analog-input: Analog Input (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-input-microphone: Microphone (priority 8700, available: unknown)<br />
properties:<br />
<br />
hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)<br />
properties:<br />
<br />
The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).<br />
<br />
To change the profile, one can use the pactl command:<br />
<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:analog-stereo><br />
$ pactl set-card-profile 0 output:hdmi-stereo<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:hdmi-stereo><br />
<br />
== Terminal commands for Function Keys ==<br />
<br />
Would it be useful to add to this table<br />
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A#Function_keys <br><br />
one more column with suggested terminal commands for the functions needing shortcuts? <br><br />
I found them extremely useful in openbox, but not always easy to find. <br><br />
<u>Examples:</u> <br><br />
Fn+F1 pm-suspend <br><br />
Fn+F3 asus-kbd-backlight down <br><br />
Fn-F4 asus-kbd-backlight up <br><br />
Fn+F10 amixer sset Master toggle <br><br />
Fn+F11 amixer sset Master 2dB- <br><br />
Fn+F12 amixer sset Master 2dB+ <br><br />
<br><br />
[My first attempt at contributing to this Arch wiki]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Zenbook_Prime_UX31A&diff=264411Talk:ASUS Zenbook Prime UX31A2013-06-27T03:18:55Z<p>Latgarf: /* Terminal commands for Function Keys */</p>
<hr />
<div>== Clean up ==<br />
I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official [[Installation Guide]]. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. [[User:Drenninghoff|Drenninghoff]] ([[User talk:Drenninghoff|talk]])<br />
<br />
== Other function keys ==<br />
I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are '''not''' working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?<br />
<br />
Additionally the following info box says that since a ''newer'' kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...<br />
<br />
*"Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 21:26, 31 August 2012 (UTC)<br />
<br />
* Ah, I see! Thanks for the explanation. [[User:Mqt|Mqt]] ([[User talk:Mqt|talk]]) 21:42, 31 August 2012 (UTC)<br />
<br />
== Installation section ==<br />
<br />
The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...<br />
<br />
So I think that all the additional steps about encryption should be clearly flagged at optional. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 10:12, 1 September 2012 (UTC)<br />
<br />
I completely agree [[User:Nihathrael|Nihathrael]] ([[User talk:Nihathrael|talk]]) 21:27, 14 September 2012 (UTC)<br />
<br />
== HDMI Audio Sandbox ==<br />
<br />
This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right <br />
<br />
=== HDMI Audio ===<br />
<br />
The UX31A contains the following PCI souncard:<br />
<br />
$ lspci -nnn -k | grep -i audio<br />
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)<br />
<br />
This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.<br />
<br />
You will need the snd-hda-hdmi module:<br />
<br />
$ lsmod | grep hda<br />
snd_hda_codec_hdmi 21095 1 <br />
snd_hda_codec_realtek 49734 1 <br />
snd_hda_intel 22373 2 <br />
snd_hda_codec 71565 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel<br />
snd_pcm 60543 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel<br />
snd_page_alloc 5921 2 snd_pcm,snd_hda_intel<br />
snd_hwdep 5061 1 snd_hda_codec<br />
snd 48443 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel<br />
<br />
=== UDEV ===<br />
Here is how udev sees plugging in the HDMI cable:<br />
<br />
$ udevadm monitor<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
KERNEL[96692.710767] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
UDEV [96692.712940] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
<br />
=== Pulseaudio ===<br />
<br />
To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
<br />
Pulseaudio sees the soundcard as follows:<br />
<br />
$ pacmd list-cards<br />
Welcome to PulseAudio! Use "help" for usage information.<br />
>>> 1 card(s) available.<br />
index: 0<br />
name: <alsa_card.pci-0000_00_1b.0><br />
driver: <module-alsa-card.c><br />
owner module: 4<br />
properties:<br />
alsa.card = "0"<br />
alsa.card_name = "HDA Intel PCH"<br />
alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"<br />
alsa.driver_name = "snd_hda_intel"<br />
device.bus_path = "pci-0000:00:1b.0"<br />
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"<br />
device.bus = "pci"<br />
device.vendor.id = "8086"<br />
device.vendor.name = "Intel Corporation"<br />
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"<br />
device.form_factor = "internal"<br />
device.string = "0"<br />
device.description = "Built-in Audio"<br />
module-udev-detect.discovered = "1"<br />
device.icon_name = "audio-card-pci"<br />
profiles:<br />
output:analog-stereo: Analog Stereo Output (priority 6000)<br />
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)<br />
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)<br />
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)<br />
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)<br />
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)<br />
input:analog-stereo: Analog Stereo Input (priority 60)<br />
off: Off (priority 0)<br />
active profile: <output:hdmi-stereo><br />
sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)<br />
sources:<br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)<br />
ports:<br />
analog-output-speaker: Speakers (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-output-headphones: Headphones (priority 9000, available: no)<br />
properties:<br />
<br />
analog-input: Analog Input (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-input-microphone: Microphone (priority 8700, available: unknown)<br />
properties:<br />
<br />
hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)<br />
properties:<br />
<br />
The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).<br />
<br />
To change the profile, one can use the pactl command:<br />
<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:analog-stereo><br />
$ pactl set-card-profile 0 output:hdmi-stereo<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:hdmi-stereo><br />
<br />
== Terminal commands for Function Keys ==<br />
<br />
Would it be useful to add to this table<br />
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A#Function_keys <br><br />
one more column with suggested terminal commands for the functions needing shortcuts? <br><br />
I found them extremely useful in openbox, but not always easy to find. <br><br><br />
<u>Examples:</u><br />
<br />
Fn+F1 pm-suspend <br><br />
... <br><br />
Fn+F3 asus-kbd-backlight down <br><br />
Fn-F4 asus-kbd-backlight up <br><br />
... <br><br />
Fn+F10 amixer sset Master toggle <br><br />
Fn+F11 amixer sset Master 2dB- <br><br />
Fn+F12 amixer sset Master 2dB+ <br><br />
... <br><br />
<br><br />
[My first attempt at contributing to this Arch wiki]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Zenbook_Prime_UX31A&diff=264410Talk:ASUS Zenbook Prime UX31A2013-06-27T03:17:49Z<p>Latgarf: /* Terminal commands for Function Keys */</p>
<hr />
<div>== Clean up ==<br />
I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official [[Installation Guide]]. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. [[User:Drenninghoff|Drenninghoff]] ([[User talk:Drenninghoff|talk]])<br />
<br />
== Other function keys ==<br />
I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are '''not''' working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?<br />
<br />
Additionally the following info box says that since a ''newer'' kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...<br />
<br />
*"Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 21:26, 31 August 2012 (UTC)<br />
<br />
* Ah, I see! Thanks for the explanation. [[User:Mqt|Mqt]] ([[User talk:Mqt|talk]]) 21:42, 31 August 2012 (UTC)<br />
<br />
== Installation section ==<br />
<br />
The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...<br />
<br />
So I think that all the additional steps about encryption should be clearly flagged at optional. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 10:12, 1 September 2012 (UTC)<br />
<br />
I completely agree [[User:Nihathrael|Nihathrael]] ([[User talk:Nihathrael|talk]]) 21:27, 14 September 2012 (UTC)<br />
<br />
== HDMI Audio Sandbox ==<br />
<br />
This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right <br />
<br />
=== HDMI Audio ===<br />
<br />
The UX31A contains the following PCI souncard:<br />
<br />
$ lspci -nnn -k | grep -i audio<br />
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)<br />
<br />
This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.<br />
<br />
You will need the snd-hda-hdmi module:<br />
<br />
$ lsmod | grep hda<br />
snd_hda_codec_hdmi 21095 1 <br />
snd_hda_codec_realtek 49734 1 <br />
snd_hda_intel 22373 2 <br />
snd_hda_codec 71565 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel<br />
snd_pcm 60543 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel<br />
snd_page_alloc 5921 2 snd_pcm,snd_hda_intel<br />
snd_hwdep 5061 1 snd_hda_codec<br />
snd 48443 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel<br />
<br />
=== UDEV ===<br />
Here is how udev sees plugging in the HDMI cable:<br />
<br />
$ udevadm monitor<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
KERNEL[96692.710767] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
UDEV [96692.712940] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
<br />
=== Pulseaudio ===<br />
<br />
To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
<br />
Pulseaudio sees the soundcard as follows:<br />
<br />
$ pacmd list-cards<br />
Welcome to PulseAudio! Use "help" for usage information.<br />
>>> 1 card(s) available.<br />
index: 0<br />
name: <alsa_card.pci-0000_00_1b.0><br />
driver: <module-alsa-card.c><br />
owner module: 4<br />
properties:<br />
alsa.card = "0"<br />
alsa.card_name = "HDA Intel PCH"<br />
alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"<br />
alsa.driver_name = "snd_hda_intel"<br />
device.bus_path = "pci-0000:00:1b.0"<br />
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"<br />
device.bus = "pci"<br />
device.vendor.id = "8086"<br />
device.vendor.name = "Intel Corporation"<br />
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"<br />
device.form_factor = "internal"<br />
device.string = "0"<br />
device.description = "Built-in Audio"<br />
module-udev-detect.discovered = "1"<br />
device.icon_name = "audio-card-pci"<br />
profiles:<br />
output:analog-stereo: Analog Stereo Output (priority 6000)<br />
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)<br />
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)<br />
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)<br />
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)<br />
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)<br />
input:analog-stereo: Analog Stereo Input (priority 60)<br />
off: Off (priority 0)<br />
active profile: <output:hdmi-stereo><br />
sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)<br />
sources:<br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)<br />
ports:<br />
analog-output-speaker: Speakers (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-output-headphones: Headphones (priority 9000, available: no)<br />
properties:<br />
<br />
analog-input: Analog Input (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-input-microphone: Microphone (priority 8700, available: unknown)<br />
properties:<br />
<br />
hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)<br />
properties:<br />
<br />
The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).<br />
<br />
To change the profile, one can use the pactl command:<br />
<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:analog-stereo><br />
$ pactl set-card-profile 0 output:hdmi-stereo<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:hdmi-stereo><br />
<br />
== Terminal commands for Function Keys ==<br />
<br />
Would it be useful to add to this table<br />
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A#Function_keys <br><br />
one more column with suggested terminal commands for the functions needing shortcuts? <br><br />
I found them extremely useful in openbox, but not always easy to find. <br><br />
Examples:<br />
<br />
Fn+F1 pm-suspend <br><br />
... <br><br />
Fn+F3 asus-kbd-backlight down <br><br />
Fn-F4 asus-kbd-backlight up <br><br />
... <br><br />
Fn+F10 amixer sset Master toggle <br><br />
Fn+F11 amixer sset Master 2dB- <br><br />
Fn+F12 amixer sset Master 2dB+ <br><br />
... <br><br />
<br><br />
[My first attempt at contributing to this Arch wiki]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Zenbook_Prime_UX31A&diff=264409Talk:ASUS Zenbook Prime UX31A2013-06-27T03:16:54Z<p>Latgarf: /* Terminal commands for Function Keys */</p>
<hr />
<div>== Clean up ==<br />
I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official [[Installation Guide]]. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. [[User:Drenninghoff|Drenninghoff]] ([[User talk:Drenninghoff|talk]])<br />
<br />
== Other function keys ==<br />
I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are '''not''' working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?<br />
<br />
Additionally the following info box says that since a ''newer'' kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...<br />
<br />
*"Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 21:26, 31 August 2012 (UTC)<br />
<br />
* Ah, I see! Thanks for the explanation. [[User:Mqt|Mqt]] ([[User talk:Mqt|talk]]) 21:42, 31 August 2012 (UTC)<br />
<br />
== Installation section ==<br />
<br />
The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...<br />
<br />
So I think that all the additional steps about encryption should be clearly flagged at optional. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 10:12, 1 September 2012 (UTC)<br />
<br />
I completely agree [[User:Nihathrael|Nihathrael]] ([[User talk:Nihathrael|talk]]) 21:27, 14 September 2012 (UTC)<br />
<br />
== HDMI Audio Sandbox ==<br />
<br />
This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right <br />
<br />
=== HDMI Audio ===<br />
<br />
The UX31A contains the following PCI souncard:<br />
<br />
$ lspci -nnn -k | grep -i audio<br />
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)<br />
<br />
This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.<br />
<br />
You will need the snd-hda-hdmi module:<br />
<br />
$ lsmod | grep hda<br />
snd_hda_codec_hdmi 21095 1 <br />
snd_hda_codec_realtek 49734 1 <br />
snd_hda_intel 22373 2 <br />
snd_hda_codec 71565 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel<br />
snd_pcm 60543 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel<br />
snd_page_alloc 5921 2 snd_pcm,snd_hda_intel<br />
snd_hwdep 5061 1 snd_hda_codec<br />
snd 48443 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel<br />
<br />
=== UDEV ===<br />
Here is how udev sees plugging in the HDMI cable:<br />
<br />
$ udevadm monitor<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
KERNEL[96692.710767] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
UDEV [96692.712940] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
<br />
=== Pulseaudio ===<br />
<br />
To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
<br />
Pulseaudio sees the soundcard as follows:<br />
<br />
$ pacmd list-cards<br />
Welcome to PulseAudio! Use "help" for usage information.<br />
>>> 1 card(s) available.<br />
index: 0<br />
name: <alsa_card.pci-0000_00_1b.0><br />
driver: <module-alsa-card.c><br />
owner module: 4<br />
properties:<br />
alsa.card = "0"<br />
alsa.card_name = "HDA Intel PCH"<br />
alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"<br />
alsa.driver_name = "snd_hda_intel"<br />
device.bus_path = "pci-0000:00:1b.0"<br />
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"<br />
device.bus = "pci"<br />
device.vendor.id = "8086"<br />
device.vendor.name = "Intel Corporation"<br />
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"<br />
device.form_factor = "internal"<br />
device.string = "0"<br />
device.description = "Built-in Audio"<br />
module-udev-detect.discovered = "1"<br />
device.icon_name = "audio-card-pci"<br />
profiles:<br />
output:analog-stereo: Analog Stereo Output (priority 6000)<br />
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)<br />
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)<br />
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)<br />
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)<br />
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)<br />
input:analog-stereo: Analog Stereo Input (priority 60)<br />
off: Off (priority 0)<br />
active profile: <output:hdmi-stereo><br />
sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)<br />
sources:<br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)<br />
ports:<br />
analog-output-speaker: Speakers (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-output-headphones: Headphones (priority 9000, available: no)<br />
properties:<br />
<br />
analog-input: Analog Input (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-input-microphone: Microphone (priority 8700, available: unknown)<br />
properties:<br />
<br />
hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)<br />
properties:<br />
<br />
The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).<br />
<br />
To change the profile, one can use the pactl command:<br />
<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:analog-stereo><br />
$ pactl set-card-profile 0 output:hdmi-stereo<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:hdmi-stereo><br />
<br />
== Terminal commands for Function Keys ==<br />
<br />
Would it be useful to add to this table<br />
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A#Function_keys <br><br />
one more column with suggested terminal commands for the functions needing shortcuts? <br><br />
I found them extremely useful in openbox, but not always easy to find.<br />
Examples:<br />
<br />
Fn+F1 pm-suspend <br><br />
... <br><br />
Fn+F3 asus-kbd-backlight down <br><br />
Fn-F4 asus-kbd-backlight up <br><br />
... <br><br />
Fn+F10 amixer sset Master toggle <br><br />
Fn+F11 amixer sset Master 2dB- <br><br />
Fn+F12 amixer sset Master 2dB+ <br><br />
... <br><br />
<br><br />
<br />
[My first attempt at contributing to this Arch wiki]</div>Latgarfhttps://wiki.archlinux.org/index.php?title=Talk:ASUS_Zenbook_Prime_UX31A&diff=264408Talk:ASUS Zenbook Prime UX31A2013-06-27T03:13:09Z<p>Latgarf: /* Terminal commands for Function Keys */ new section</p>
<hr />
<div>== Clean up ==<br />
I removed a lot of unnecessary information that only complicates things. For installation instructions simply look at the official [[Installation Guide]]. It is not needed to duplicate those information here. Legacy information are not needed. Who would run a new laptop with an old kernel? Since the newest kernels fix many problems we can remove these from this wiki page. [[User:Drenninghoff|Drenninghoff]] ([[User talk:Drenninghoff|talk]])<br />
<br />
== Other function keys ==<br />
I am writing from an UX31A with kernel 3.5.3-1-ARCH, and my function keys are '''not''' working out-of-the-box (except volume and display out). Is there any kernel module which is not mentioned in the text or is this information simply wrong?<br />
<br />
Additionally the following info box says that since a ''newer'' kernel version a patch is no longer needed. A version that I don't need anyhow, because everything is supposed to work out-of-the-box. Seems a little bit contradictious...<br />
<br />
*"Working" means that you can see keycodes with xev when function keys are pressed. It does not means that — for example — when you press fn+f3 it will diminish keyboard luminosity : for that you must link the keycode to the functionality. I have the same kernel version than you and I can confirm you no longer needs the fix : All the keys except screen backlight are working. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 21:26, 31 August 2012 (UTC)<br />
<br />
* Ah, I see! Thanks for the explanation. [[User:Mqt|Mqt]] ([[User talk:Mqt|talk]]) 21:42, 31 August 2012 (UTC)<br />
<br />
== Installation section ==<br />
<br />
The additional information about encrypted partition is nice, but I think installation instructions should be more modular and better accomodate the different installation scenarios : standalone arch without encryption, arch with encryption, dual boot install keeping the original windows install...<br />
<br />
So I think that all the additional steps about encryption should be clearly flagged at optional. [[User:Bzhb|Bzhb]] ([[User talk:Bzhb|talk]]) 10:12, 1 September 2012 (UTC)<br />
<br />
I completely agree [[User:Nihathrael|Nihathrael]] ([[User talk:Nihathrael|talk]]) 21:27, 14 September 2012 (UTC)<br />
<br />
== HDMI Audio Sandbox ==<br />
<br />
This is a sandbox for an HDMI Pulseaudio from the commandline module I'll move into the article once I have it right <br />
<br />
=== HDMI Audio ===<br />
<br />
The UX31A contains the following PCI souncard:<br />
<br />
$ lspci -nnn -k | grep -i audio<br />
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)<br />
<br />
This device is capable of outputting both analog stereo (used to power the speaker and headphones) which uses the snd-audio-code-realtek module, and digital audio through the mini-hdmi port on the right side of the machine.<br />
<br />
You will need the snd-hda-hdmi module:<br />
<br />
$ lsmod | grep hda<br />
snd_hda_codec_hdmi 21095 1 <br />
snd_hda_codec_realtek 49734 1 <br />
snd_hda_intel 22373 2 <br />
snd_hda_codec 71565 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_intel<br />
snd_pcm 60543 3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel<br />
snd_page_alloc 5921 2 snd_pcm,snd_hda_intel<br />
snd_hwdep 5061 1 snd_hda_codec<br />
snd 48443 11 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec,snd_hda_intel<br />
<br />
=== UDEV ===<br />
Here is how udev sees plugging in the HDMI cable:<br />
<br />
$ udevadm monitor<br />
monitor will print the received events for:<br />
UDEV - the event which udev sends out after rule processing<br />
KERNEL - the kernel uevent<br />
<br />
KERNEL[96692.710767] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
UDEV [96692.712940] change /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)<br />
<br />
=== Pulseaudio ===<br />
<br />
To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
<br />
Pulseaudio sees the soundcard as follows:<br />
<br />
$ pacmd list-cards<br />
Welcome to PulseAudio! Use "help" for usage information.<br />
>>> 1 card(s) available.<br />
index: 0<br />
name: <alsa_card.pci-0000_00_1b.0><br />
driver: <module-alsa-card.c><br />
owner module: 4<br />
properties:<br />
alsa.card = "0"<br />
alsa.card_name = "HDA Intel PCH"<br />
alsa.long_card_name = "HDA Intel PCH at 0xf7d18000 irq 47"<br />
alsa.driver_name = "snd_hda_intel"<br />
device.bus_path = "pci-0000:00:1b.0"<br />
sysfs.path = "/devices/pci0000:00/0000:00:1b.0/sound/card0"<br />
device.bus = "pci"<br />
device.vendor.id = "8086"<br />
device.vendor.name = "Intel Corporation"<br />
device.product.name = "7 Series/C210 Series Chipset Family High Definition Audio Controller"<br />
device.form_factor = "internal"<br />
device.string = "0"<br />
device.description = "Built-in Audio"<br />
module-udev-detect.discovered = "1"<br />
device.icon_name = "audio-card-pci"<br />
profiles:<br />
output:analog-stereo: Analog Stereo Output (priority 6000)<br />
output:analog-stereo+input:analog-stereo: Analog Stereo Duplex (priority 6060)<br />
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5400)<br />
output:hdmi-stereo+input:analog-stereo: Digital Stereo (HDMI) Output + Analog Stereo Input (priority 5460)<br />
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 300)<br />
output:hdmi-surround+input:analog-stereo: Digital Surround 5.1 (HDMI) Output + Analog Stereo Input (priority 360)<br />
input:analog-stereo: Analog Stereo Input (priority 60)<br />
off: Off (priority 0)<br />
active profile: <output:hdmi-stereo><br />
sinks:To flip from analog (speakers/headphones) to digital (HDMI output), it is necessary to set the card's Pulseaudio profile. <br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo/#18: Built-in Audio Digital Stereo (HDMI)<br />
sources:<br />
alsa_output.pci-0000_00_1b.0.hdmi-stereo.monitor/#19: Monitor of Built-in Audio Digital Stereo (HDMI)<br />
ports:<br />
analog-output-speaker: Speakers (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-output-headphones: Headphones (priority 9000, available: no)<br />
properties:<br />
<br />
analog-input: Analog Input (priority 10000, available: unknown)<br />
properties:<br />
<br />
analog-input-microphone: Microphone (priority 8700, available: unknown)<br />
properties:<br />
<br />
hdmi-output-0: HDMI / DisplayPort (priority 5900, available: no)<br />
properties:<br />
<br />
The two important pieces of information here are the card's number ("index: 0") and the profiles for analog and HDMI digital stereo (output:analog-stereo and output:hdmi-stereo).<br />
<br />
To change the profile, one can use the pactl command:<br />
<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:analog-stereo><br />
$ pactl set-card-profile 0 output:hdmi-stereo<br />
$ pacmd list-cards | grep "active profile"<br />
active profile: <output:hdmi-stereo><br />
<br />
== Terminal commands for Function Keys ==<br />
<br />
Would it be useful to add to this table<br />
https://wiki.archlinux.org/index.php/ASUS_Zenbook_Prime_UX31A#Function_keys <br />
one more column with suggested terminal commands for the functions needing shortcuts?<br />
I found them extremely useful in openbox, but not always easy to find.<br />
Examples:<br />
<br />
Fn+F1 pm-suspend<br />
...<br />
Fn+F3 asus-kbd-backlight down<br />
Fn-F4 asus-kbd-backlight up<br />
...<br />
Fn+F10 amixer sset Master toggle<br />
Fn+F11 amixer sset Master 2dB-<br />
Fn+F12 amixer sset Master 2dB+<br />
...<br />
<br />
[My first attempt at contributing to this Arch wiki]</div>Latgarf