https://wiki.archlinux.org/api.php?action=feedcontributions&user=Alexjj&feedformat=atomArchWiki - User contributions [en]2024-03-28T10:07:35ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=User:Alexjj&diff=456628User:Alexjj2016-11-12T14:45:49Z<p>Alexjj: fixed link formatting</p>
<hr />
<div>Hi. I'm Alex Johnstone.<br />
<br />
My [[Special:Contributions/Alexjj|contributions]].<br />
<br />
My [https://alexjj.com homepage].</div>Alexjjhttps://wiki.archlinux.org/index.php?title=User:Alexjj&diff=456626User:Alexjj2016-11-12T14:44:57Z<p>Alexjj: Created user page for me.</p>
<hr />
<div>Hi. I'm Alex Johnstone.<br />
<br />
My [[Special:Contributions/Alexjj|contributions]].<br />
<br />
My [[https://alexjj.com|homepage]].</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9350)&diff=456625Talk:Dell XPS 13 (9350)2016-11-12T14:32:13Z<p>Alexjj: /* XPS pages renaming */ agreeing</p>
<hr />
<div>Added a section for kernel specific configurations.<br />
<br />
== <s> SATA controller </s> ==<br />
Potentially useful blog post?: https://samnicholls.net/2016/01/14/how-to-switch-sata-raid-to-ahci-windows-10-xps-13/ (disclaimer: it's mine) on getting around the SATA controller issue for those who need to dual boot, works on my 9350 but ymmv. [[User:Samstudio8|Samstudio8]] ([[User talk:Samstudio8|talk]]) 04:11, 14 January 2016 (UTC)<br />
<br />
: I described your suggested solutions in the main article. Feel free to correct any mistakes. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 10:10, 15 July 2016 (UTC)<br />
<br />
== Release of 4.4 in testing ==<br />
<br />
I made a slew of edits and some clean up related to the release of 4.4 in testing. Let me know if you see any issues. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:24, 20 January 2016 (UTC)<br />
<br />
== BIOS update 1.1.9 ==<br />
<br />
Since the BIOS update, I get some errors, with stack dump during suspend/resume.<br />
<br />
[ 0.448742] ------------[ cut here ]------------<br />
[ 0.448744] WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page+0x5e1/0x780()<br />
[ 0.448745] x86/mm: Found insecure W+X mapping at address ffff880000000000/0xffff880000000000<br />
[ 0.448746] Modules linked in:<br />
[ 0.448748] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-3-ARCH #1<br />
[ 0.448749] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 0.448750] 0000000000000000 00000000271d54da ffff8802771afd48 ffffffff812c8a99<br />
[ 0.448752] ffff8802771afd90 ffff8802771afd80 ffffffff810771c2 ffff8802771afe90<br />
[ 0.448754] 8000000000000163 0000000000000004 0000000000000000 0000000000000000<br />
[ 0.448755] Call Trace:<br />
[ 0.448758] [<ffffffff812c8a99>] dump_stack+0x4b/0x72<br />
[ 0.448760] [<ffffffff810771c2>] warn_slowpath_common+0x82/0xc0<br />
[ 0.448762] [<ffffffff8107725c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 0.448763] [<ffffffff8106c4c1>] note_page+0x5e1/0x780<br />
[ 0.448765] [<ffffffff8106c967>] ptdump_walk_pgd_level_core+0x307/0x450<br />
[ 0.448766] [<ffffffff8106cae7>] ptdump_walk_pgd_level_checkwx+0x17/0x20<br />
[ 0.448768] [<ffffffff8106278f>] mark_rodata_ro+0xef/0x100<br />
[ 0.448770] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448771] [<ffffffff8158636d>] kernel_init+0x1d/0xe0<br />
[ 0.448773] [<ffffffff8159290f>] ret_from_fork+0x3f/0x70<br />
[ 0.448774] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448775] ---[ end trace b1a5026ad8272458 ]---<br />
<br />
[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:48, 20 January 2016 (UTC)<br />
<br />
Since latest kernel update (4.4.1-2-ARCH), I do not get the above error anymore. I'm still using 1.1.9 at the moment. Instead I get the following error:<br />
<br />
<pre><br />
[ 1370.376263] ------------[ cut here ]------------<br />
[ 1370.376281] WARNING: CPU: 1 PID: 140 at drivers/ata/libata-eh.c:4143 ata_scsi_port_error_handler+0x731/0x770 [libata]()<br />
[ 1370.376356] Modules linked in: fuse ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6t_rpfilter snd_hda_codec_hdmi ip6table_raw joydev input_leds ip6_tables mousedev iptable_filter dell_led dell_laptop intel_rapl x86_pkg_temp_thermal intel_powerclamp led_class serio_raw atkbd kvm_intel dcdbas libps2 dell_wmi hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core sparse_keymap kvm nls_cp437 snd_hda_codec_realtek snd_hda_codec_generic vfat irqbypass fat crct10dif_pclmul crc32_pclmul aesni_intel snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core aes_x86_64 lrw gf128mul snd_soc_sst_ipc glue_helper snd_soc_sst_dsp ablk_helper cryptd snd_soc_core snd_compress snd_pcm_dmaengine<br />
[ 1370.376448] ac97_bus dw_dmac_core pcspkr snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_timer snd rtsx_pci_ms brcmutil i2c_i801 soundcore cfg80211 memstick uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common shpchp videodev mei_me btusb btrtl usbhid media mei idma64 processor_thermal_device intel_soc_dts_iosf iosf_mbi intel_lpss_pci fan thermal wmi i2c_hid hid battery hci_uart btbcm btqca btintel bluetooth i8042 rfkill serio crc16 pinctrl_sunrisepoint pinctrl_intel intel_lpss_acpi evdev acpi_als intel_lpss kfifo_buf industrialio mac_hid int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel tpm_tis acpi_pad tpm ac fjes processor sch_fq_codel coretemp msr ip_tables x_tables rtsx_pci_sdmmc mmc_core xhci_pci ahci xhci_hcd libahci<br />
[ 1370.376474] libata rtsx_pci scsi_mod usbcore usb_common crc32c_generic crc32c_intel btrfs xor raid6_pq i915 video button intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvme<br />
[ 1370.376480] CPU: 1 PID: 140 Comm: scsi_eh_2 Tainted: G W 4.4.1-2-ARCH #1<br />
[ 1370.376482] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 1370.376488] 0000000000000000 000000009b4c41e3 ffff880274f23d60 ffffffff812c7f39<br />
[ 1370.376494] 0000000000000000 ffff880274f23d98 ffffffff810765b2 ffff880274de0000<br />
[ 1370.376499] ffff880274f23e08 ffff880274de0000 ffff880274f23e60 ffff880274f23e80<br />
[ 1370.376501] Call Trace:<br />
[ 1370.376508] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 1370.376516] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 1370.376523] [<ffffffff810766fa>] warn_slowpath_null+0x1a/0x20<br />
[ 1370.376533] [<ffffffffa03944b1>] ata_scsi_port_error_handler+0x731/0x770 [libata]<br />
[ 1370.376546] [<ffffffffa038ed1d>] ? ata_scsi_cmd_error_handler+0x11d/0x160 [libata]<br />
[ 1370.376557] [<ffffffffa0394590>] ata_scsi_error+0xa0/0xe0 [libata]<br />
[ 1370.376568] [<ffffffffa0339246>] scsi_error_handler+0xb6/0x550 [scsi_mod]<br />
[ 1370.376575] [<ffffffff8158d93a>] ? __schedule+0x3aa/0xa70<br />
[ 1370.376586] [<ffffffffa0339190>] ? scsi_eh_get_sense+0x170/0x170 [scsi_mod]<br />
[ 1370.376591] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 1370.376597] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376602] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 1370.376608] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376611] ---[ end trace d11264a1acf26f7c ]---<br />
</pre><br />
<br />
I do not see any other errors. It's an ATA error, and I am still preloading "nvme" in my MODULES= mkinitcpio configuration at the moment.[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:03, 12 February 2016 (UTC)<br />
<br />
I can second that exact same error with 4.4.1-2-ARCH. After reading through http://en.community.dell.com/support-forums/laptop/f/3518/t/19586456 I'm starting to begin wondering if its a general hardware problem with the mainboard/powerboard. Does anyone with an XPS 9350 NOT have any of this issues with a working suspend? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 09:47, 12 February 2016 (UTC)<br />
<br />
== BIOS 1.2.3 ==<br />
<br />
With BIOS update 1.2.3 I get the following ACPI errors:<br />
<br />
[ 240.210541] INFO: task kworker/0:2:64 blocked for more than 120 seconds.<br />
[ 240.210552] Not tainted 4.4.1-1-ARCH #1<br />
[ 240.210555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br />
[ 240.210561] kworker/0:2 D ffff880275b13b58 0 64 2 0x00000000<br />
[ 240.210580] Workqueue: kacpid acpi_os_execute_deferred<br />
[ 240.210585] ffff880275b13b58 ffffffff8137774a ffffffff81810500 ffff880275b9ac40<br />
[ 240.210591] ffff880275b14000 ffff880271451700 ffff880275b9ac40 ffff880276966820<br />
[ 240.210597] ffff88007628b050 ffff880275b13b70 ffffffff8158e03c 7fffffffffffffff<br />
[ 240.210603] Call Trace:<br />
[ 240.210612] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210622] [<ffffffff8158e03c>] schedule+0x3c/0x90<br />
[ 240.210629] [<ffffffff81590ab3>] schedule_timeout+0x1b3/0x240<br />
[ 240.210633] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210642] [<ffffffff8136c0c6>] ? acpi_ns_search_one_scope+0x25/0x45<br />
[ 240.210649] [<ffffffff8136c235>] ? acpi_ns_search_and_enter+0x14f/0x1ab<br />
[ 240.210656] [<ffffffff8158fd34>] __down_timeout+0x74/0xd0<br />
[ 240.210662] [<ffffffff810bdb87>] ? down_timeout+0x37/0x60<br />
[ 240.210666] [<ffffffff810bdb9c>] down_timeout+0x4c/0x60<br />
[ 240.210673] [<ffffffff813478bf>] acpi_os_wait_semaphore+0x4c/0x67<br />
[ 240.210679] [<ffffffff81367243>] acpi_ex_system_wait_mutex+0x3c/0x4d<br />
[ 240.210686] [<ffffffff81359b28>] acpi_ds_begin_method_execution+0x13f/0x1d8<br />
[ 240.210693] [<ffffffff81359db4>] acpi_ds_call_control_method+0x54/0x17b<br />
[ 240.210698] [<ffffffff8136f3ab>] acpi_ps_parse_aml+0xaf/0x26f<br />
[ 240.210703] [<ffffffff8136fc11>] acpi_ps_execute_method+0x14b/0x186<br />
[ 240.210710] [<ffffffff8136a151>] acpi_ns_evaluate+0x1bb/0x247<br />
[ 240.210717] [<ffffffff8135d6f9>] acpi_ev_asynch_execute_gpe_method+0xa0/0x105<br />
[ 240.210723] [<ffffffff81346bce>] acpi_os_execute_deferred+0x14/0x20<br />
[ 240.210731] [<ffffffff8108e21b>] process_one_work+0x14b/0x440<br />
[ 240.210737] [<ffffffff8108e558>] worker_thread+0x48/0x4a0<br />
[ 240.210744] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210750] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210755] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 240.210761] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 240.210766] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 240.210771] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
<br />
This probably stems from a malfunctioning in the 1.2.3 Bios:<br />
<br />
[ 2.927769] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.927774] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927782] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927791] acpi PNP0C0B:00: Failed to change power state to D0<br />
[ 2.931194] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)<br />
[ 2.934430] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.934434] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934439] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934445] acpi PNP0C0B:00: Setting initial power state<br />
[ 2.936690] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)<br />
[ 2.937857] idma64 idma64.0: Found Intel integrated DMA 64-bit<br />
[ 2.951059] acpi PNP0C0B:00: Cannot transition from (unknown) to D3hot<br />
[ 2.951481] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)<br />
[ 2.951616] idma64 idma64.1: Found Intel integrated DMA 64-bit<br />
[ 2.957772] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.957776] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957781] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957787] acpi PNP0C0B:01: Failed to change power state to D0<br />
[ 2.964451] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.964455] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964460] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964498] acpi PNP0C0B:01: Setting initial power state<br />
[ 2.969276] mei_me 0000:00:16.0: enabling device (0000 -> 0002)<br />
[ 2.981024] acpi PNP0C0B:01: Cannot transition from (unknown) to D3hot<br />
[ 2.987767] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.987772] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987778] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987784] acpi PNP0C0B:02: Failed to change power state to D0<br />
[ 2.990676] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4<br />
[ 2.994441] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.994447] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994455] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994464] acpi PNP0C0B:02: Setting initial power state<br />
[ 3.001025] usb 1-3: new full-speed USB device number 3 using xhci_hcd<br />
[ 3.007691] acpi PNP0C0B:02: Cannot transition from (unknown) to D3hot<br />
[ 3.014415] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.014420] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014426] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014436] acpi PNP0C0B:03: Failed to change power state to D0<br />
[ 3.018400] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150930/utaddress-254)<br />
[ 3.018409] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver<br />
[ 3.021070] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.021074] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021080] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021086] acpi PNP0C0B:03: Setting initial power state<br />
<br />
<br />
Additionally I still get the intel gpu drm error that was present in 4.3:<br />
<br />
[ 8200.818355] WARNING: CPU: 0 PID: 663 at drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]()<br />
[ 8200.818357] WARN_ON(!wm_changed)<br />
[ 8200.818359] Modules linked in:<br />
[ 8200.818361] ...<br />
[ 8200.818462] intel_gtt<br />
[ 8200.818466] CPU: 0 PID: 663 Comm: Xorg Tainted: G W 4.4.1-1-ARCH #1<br />
[ 8200.818468] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.2.3 01/08/2016<br />
[ 8200.818470] 0000000000000000 00000000c1d62b7d ffff88007631f750 ffffffff812c7f39<br />
[ 8200.818474] ffff88007631f798 ffff88007631f788 ffffffff810765b2 ffff880276862000<br />
[ 8200.818477] ffff88007631f8bc ffff880276867000 0000000000000000 ffff88007631f828<br />
[ 8200.818480] Call Trace:<br />
[ 8200.818486] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 8200.818491] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 8200.818495] [<ffffffff8107664c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 8200.818505] [<ffffffffa00f1f37>] skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]<br />
[ 8200.818515] [<ffffffffa00f219a>] skl_update_wm+0x25a/0x750 [i915]<br />
[ 8200.818526] [<ffffffffa00f64de>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 8200.818539] [<ffffffffa015ed70>] haswell_crtc_enable+0x370/0x870 [i915]<br />
[ 8200.818553] [<ffffffffa015a992>] intel_atomic_commit+0x492/0x1430 [i915]<br />
[ 8200.818561] [<ffffffffa003339e>] ? drm_atomic_check_only+0x18e/0x590 [drm]<br />
[ 8200.818567] [<ffffffffa00337d7>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 8200.818572] [<ffffffffa00a3fb6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 8200.818580] [<ffffffffa0021ea2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 8200.818589] [<ffffffffa0026d92>] drm_mode_setcrtc+0x3d2/0x4f0 [drm]<br />
[ 8200.818595] [<ffffffffa00187b2>] drm_ioctl+0x152/0x540 [drm]<br />
[ 8200.818603] [<ffffffffa00269c0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 8200.818613] [<ffffffff811f0b68>] do_vfs_ioctl+0x298/0x480<br />
[ 8200.818620] [<ffffffff810824e1>] ? __set_task_blocked+0x41/0xa0<br />
[ 8200.818627] [<ffffffff811fabe7>] ? __fget+0x77/0xb0<br />
[ 8200.818630] [<ffffffff811f0dc9>] SyS_ioctl+0x79/0x90<br />
[ 8200.818634] [<ffffffff81084fde>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 8200.818637] [<ffffffff81591b2e>] entry_SYSCALL_64_fastpath+0x12/0x71<br />
[ 8200.818640] ---[ end trace 0e9f223c58ecdab8 ]---<br />
<br />
Everything, including the graphics works fine, however I am having trouble to rewake up the system when the laptop lid was closed.<br />
If just the display is turning off, it always comes back. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:45, 3 February 2016 (UTC)<br />
<br />
<br />
As of this morning, BIOS 1.2.3 and latest Linux kernel 4.4.2.1-ARCH, I have no more issue with suspend/wake up. By that, I mean that I do not see the libata crash anymore on suspend/wakeup. In fact, I do not see any crashes at all. It's looking all normal. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 01:01, 23 February 2016 (UTC)<br />
<br />
Nope, for me BIOS 1.2.3 with 4.4.5-1-ARCH is even worse. I can not poweroff, suspend or shutdown.--[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 10:05, 16 March 2016 (UTC)<br />
<br />
I'm using the same BIOS/Kernel as you. I do see the ACPI error (namespace failure you report, but nothing else). Could it be the graphic card power management, instead? I have absolutely nothing on my kernel line (all defaults). I do load intel-ucode, and my current microcode version 0x6a. I'm not sure which version of the graphics chip you have, but the failure in intel_pm (power management of the i915) may be mitigated by "disabling" power management: have you tried putting your graphic card on always "on" power (basically disable PM):<br />
<br />
echo on | sudo tee /sys/bus/pci/drivers/i915/0000:00:02.0/power/control <br />
<br />
Hopefully, that will help you. Note that it's bus number 0000:00:02.0 on my machine, but it maybe different on yours (so you may have to inspect the /sys/bus/pci/driver/i915 tree). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 10:48, 16 March 2016 (UTC)<br />
<br />
Thanks Bouh, unfortunately I already have the /power/control set to 'on'. As you, I have nothing on my kernel options but intel-ucode, no power manager, etc. Do you have any kernel modules blacklisted, such as dell_* ? I currently don't have, but maybe should? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:32, 16 March 2016 (UTC)<br />
<br />
No modules blacklisted, appart from the insignificant...:<br />
<br />
{{hc|cat /etc/modprobe.d/*|<br />
blacklist pcspkr<br />
blacklist psmouse<br />
}}<br />
<br />
I'm using thermald + my own power-management scripts. I'm thinking we may have different hardware. I moved on to kernel 4.5, still no issues to report (appart from the missing ACPI namespaces). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 04:31, 17 March 2016 (UTC)<br />
<br />
== PulseAudio modifying gain settings ==<br />
After talking to the pulseaudio mailing list, one user, gave me the workaround. This is his answer below:<br />
<br />
It's weird that a mic boost would affect headphone output. One<br />
explanation would be that the mic signal is fed directly to the<br />
headphones, but in that case increasing the boost should increase the<br />
noise, not decrease it. I guess it's a hardware or driver bug.<br />
<br />
To work around this, you can remove the [Element Headphone Mic Boost]<br />
sections from these two files:<br />
<br />
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf<br />
/usr/share/pulseuadio/alsa-mixer/paths/analog-input-headphone-mic.conf<br />
<br />
After that PulseAudio won't touch the boost volume any more.<br />
<br />
Whenever pulseaudio is updated, the package manager will remove your<br />
modifications, so you have to redo the modifications. That's still<br />
better than having to reset the mixer after every reboot...<br />
<br />
I guess this really needs to be provided as a patched {{Pkg|pulseaudio}} package. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:09, 25 January 2016 (UTC)<br />
<br />
== HiDPI ==<br />
This is not really mentioned in the 2016 model page, but I did have some very very small icons and fonts. What I had to do was create a file and fill it with something like this:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 338 190 # In millimeters<br />
EndSection<br />
}}<br />
<br />
This made my DPI settings similar to what they are in the Windows (240 DPI) that came with the XPS. [[User:Renatolond|Renatolond]]<br />
<br />
Out of curiosity, which desktop environment are you using? I am using a stock gnome-shell and it sets the scaling factor automatically. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:34, 19 February 2016 (UTC)<br />
<br />
I'm using Plasma via SDDM, but I think the problem begins before, because in CLI without any env the fonts are very small as well. --[[User:Renatolond|Renatolond]] ([[User talk:Renatolond|talk]]) 16:49, 19 February 2016 (UTC)<br />
<br />
In CLI, the setting mentioned above have no effect, don't they? Check this out if you want to change this: https://wiki.archlinux.org/index.php/Fonts#Console_fonts [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:16, 1 March 2016 (UTC)<br />
<br />
What model are you using?? The actual display size should be 294 by 165 according to dell specification. By the way, I also need to set <code>Xft.dpi: 166</code> in .Xresources. [[User:Jiaan|Jiaan]] ([[User talk:Jiaan|talk]]) 23 Sep 2016<br />
<br />
== Thunderbolt and XPS 15/13 ==<br />
I don't actually have a 13, but it seems the XPS 15 has somewhat similar hardware, at least as far as thunderbolt/USB-C is concerned. On my machine USB-C does not work without a PCI-e rescan, and the second you use the USB-C port the machine will no longer sleep with ACPI bugs on dmesg.<br />
<br />
Is it crazy to just create a XPS 15 (2016) and Precision 5510 (which afaict is the same machine with higher-end processor options) page which just redirects here?<br />
{{unsigned|04:18, 29 March 2016|BlueMatt}}<br />
<br />
Hi, I got exactly the same problem on my XPS 13.<br />
If I boot with USB-C adapter connected it is detectecd, if I not connects it during the boot process I need to do a rescan but if I disconnect it for the second time I got the same issue your are talking about.<br />
What is your USB-C device type your are trying to make it work? is it the Dell Multi Adatper (USB, VGA, HDMI, Ethernet)? For this one I am only able to make the Ethernet working, the HDMI is detected, my external monitor correctly detected but no signal is received on this side...<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 14:56, 29 March 2016 (UTC)<br />
<br />
For reference, here are my related dmesg:<br />
{{hc|dmesg|2=<br />
<br />
[ 997.082343] Call Trace:<br />
[ 997.082355] [<ffffffff812d8b11>] dump_stack+0x63/0x82<br />
[ 997.082360] [<ffffffff81076de2>] warn_slowpath_common+0x82/0xc0<br />
[ 997.082364] [<ffffffff81076e7c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 997.082377] [<ffffffffa00f94f7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
[ 997.082390] [<ffffffffa00f968e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
[ 997.082407] [<ffffffffa018413f>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
[ 997.082420] [<ffffffffa00fcd9e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 997.082439] [<ffffffffa01679a1>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
[ 997.082457] [<ffffffffa01632b7>] intel_atomic_commit+0x737/0x1870 [i915]<br />
[ 997.082466] [<ffffffffa0032581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
[ 997.082473] [<ffffffffa0032a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 997.082478] [<ffffffffa00a28c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 997.082489] [<ffffffffa00211b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 997.082498] [<ffffffffa00262c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
[ 997.082506] [<ffffffffa0017892>] drm_ioctl+0x152/0x540 [drm]<br />
[ 997.082514] [<ffffffffa0025ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 997.082518] [<ffffffff811eac5c>] ? __vfs_write+0xcc/0x100<br />
[ 997.082522] [<ffffffff811fdbb1>] do_vfs_ioctl+0xa1/0x5b0<br />
[ 997.082526] [<ffffffff81082d81>] ? __set_task_blocked+0x41/0xa0<br />
[ 997.082530] [<ffffffff81207fc7>] ? __fget+0x77/0xb0<br />
[ 997.082534] [<ffffffff811fe139>] SyS_ioctl+0x79/0x90<br />
[ 997.082537] [<ffffffff810858ce>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 997.082541] [<ffffffff815ab32e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
[ 997.082544] ---[ end trace 5285a5658ce7e2d8 ]---<br />
<br />
}}<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 15:37, 29 March 2016 (UTC)<br />
<br />
You may want to read http://ubuntuforums.org/showthread.php?t=2301071. Lots of people talking about USB-C and Thunderbolt 3. Seems display adapters work for most people with some effort, not sure about Thunderbolt 3 (which puts the USB-C port in PCIe mode), but USB-C seems pretty consistently broken in the same ways as above (I've tried it with a male A <-> C adapter and several devices, as well as my Nexus 5X which is native C). [[User:BlueMatt|BlueMatt]] ([[User talk:BlueMatt|talk]]) 18:46, 29 March 2016 (UTC)<br />
:Thanks BlueMatt, I read it carefuly, and I saw the PCI rescan workaround, for me it is only working the first time then I got an issue where it will never been detected anymore and I need a system restart.<br />
EDIT: Regarding VGA, everything is working well when connected, when it is disconnected if the laptop is put in sleep mode it hangs, no way to wake it up, power button led remains lighted but nothing on the screen.[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 10:14, 30 March 2016 (UTC) <br />
:For HDMI monitor is detected but no signal is sent so the monitor stays black, for Ethernet working if I boot the laptop with the adapter connected or if I do a rescan when I connect the adapter after the boot, but only one time...<br />
Perhaps a good idea to add a section into the Wiki page speaking about USB-C issue/workaround? [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 21:03, 29 March 2016 (UTC)<br />
<br />
:@BlueMatt: Regarding your question of separate articles: Exactly. It is great how this article develops, even better if contributions help users of similar/related models. Please see the extra section I created earlier as a ''suggestion'' ([[Dell XPS 13 (2016)#Diverting models]]) to account for any stub model differences that may be. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 10:10, 4 April 2016 (UTC)<br />
<br />
:@Belette: If you look at the Bias 1.2.3 section in this discussion, the slowpath bug is caused by a Linux kernel bug that in the meantime was fixed but reopened again ([https://bugs.freedesktop.org/show_bug.cgi?id=89055]). Hopefully it will be stable in 4.5.<br />
:@BlueMatt: I love that the Arch Wiki is so detailed about special models - hence I think it really depends on how similar the XPS 12, 13 and 15 models are. I have not seen any reports on how the XPS 12 works at all, only 13 and 15. Hence, I'm positive with regard to keeping separate articles until we know how similar they really are. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 07:45, 5 April 2016 (UTC)<br />
<br />
::You are welcome to add the info you have to [[Dell_XPS_13_%282016%29#XPS_12]] for now and to create an XPS12 article stub on your userpage. Open a question on the BBS, if you look for [https://wiki.archlinux.org/index.php?title=Dell_XPS_12_%282016%29&oldid=429570 info]. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:51, 5 April 2016 (UTC)<br />
<br />
== Touchpad multi-gesture ==<br />
I don't see anything specifically related to multi-gesture (zoom, pinch...) on the touchpad in the Dell XPS 13 page.<br />
<br />
I have installed xf86-input-libinput as suggested and both my touchpad and touch screen are working perfecty but I am missing multigesture..<br />
Using this tips: https://bbs.archlinux.org/viewtopic.php?pid=1617669#p1617669 [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 08:28, 7 April 2016 (UTC)<br />
<br />
== <s>Now with official Linux support</s> ==<br />
<br />
I got an email informing me that the XPS 13 2016 model is now supported by Dell, as the 4.4 kernel with the required Broadcom drivers is available in Ubuntu 16.04 LTS. However I can't find information about this on the dell site, and [http://www.dell.com/us/business/p/xps-13-linux/pd] mentioned "This product is currently unavailable". -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:14, 16 May 2016 (UTC)<br />
<br />
:[https://wiki.archlinux.org/index.php?title=Dell_XPS_13_%282016%29&diff=435552&oldid=429579], thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:43, 12 June 2016 (UTC)<br />
<br />
== EFISTUB booting ==<br />
<br />
I tried to get this laptop to boot the Linux kernel directly, via [[EFISTUB]], but none of the boot entries I created with <code>efibootmgr</code> worked. The exact same command did work, however, from the UEFI Shell v2, as well as from [[systemd-boot]]. So I suspect that this system’s UEFI implementation doesn’t properly support passing parameters to a boot entry. For booting, you either need an UEFI boot loader (like [[systemd-boot]]), or you need to link the command line into the image, as in [https://bentley.link/secureboot/#combine-the-kernel-initramfs-and-boot-options this article]. —[[User:LucasWerkmeister|LucasWerkmeister]] ([[User talk:LucasWerkmeister|talk]]) 11:16, 12 June 2016 (UTC)<br />
<br />
== Screen stuttering ==<br />
<br />
I am experiencing quite a lot of screen stuttering. Though I have chrome running in the background, half of my memory is still free and therefore should not cause problems even for an integrated GPU. The stuttering occurs independent from the application I use: e.g. my graphical terminal (gnome-terminal) is affected as well. Temperatures seem to be fine at about 50 to 60 °C and I load the latest intel microcode through my boot loader (systemd-boot). My X11 config file looks like this:<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|2=<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "sna" # UXA is an alternative<br />
Option "TearFree" "true" # SNA only, not needed for DRI3<br />
EndSection<br />
}}<br />
Googling the issue did not return viable results since most of them concern tearing, which I do not encounter, or recommend setting the {{ic|TearFree}} option to {{ic|true}} which I hava already done. I am using {{ic|mesa 12.0.1-2}}, {{ic|xf86-video-intel 1:2.99.917+676+g26f8ab5-1}}, {{ic|linux 4.6.4-1}} and {{ic|linux-firmware 20160516.80d463b-1}} with the above {{ic|xorg.conf.d/20-intel.conf}} config file. I assume it to be related to at least one of the packages. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 14:46, 28 July 2016 (UTC)<br />
<br />
== Kaby Lake Model ==<br />
<br />
Due out 4th October with intel's latest. A developer edition is coming too, bit later maybe 10th I think. <br />
Late 2016 model... [[Dell XPS 13 (4th Gen)]]<br />
<br />
== XPS pages renaming ==<br />
<br />
I suggest to rename archwiki pages in order to respect the '''hardware product code''', because '''year''' differentiation is wrong ''e.g. third and fourth generation are both dated 2015'', while '''generation''' is not easy to correspond to the hardware since Dell also use product code ''e.g. in the support page''.<br />
archwiki pages become:<br />
* Dell XPS 13 (2015) ------> Dell XPS 13 (9343)<br />
* Dell XPS 13 (2016) ------> Dell XPS 13 (9350)<br />
* Dell XPS 13 (4th Gen) ---> Dell XPS 13 (9360)<br />
--[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 09:18, 12 November 2016 (UTC)<br />
<br />
Agreed!<br />
[[User:Alexjj|Alexjj]] ([[User talk:Alexjj|talk]]) 14:31, 12 November 2016 (UTC)</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9350)&diff=451843Dell XPS 13 (9350)2016-09-24T23:54:17Z<p>Alexjj: added link to 4th gen</p>
<hr />
<div>[[Category:Dell]]<br />
{{Note|This page refers to the early 2016 model of XPS 13. For the late 2016 model see [[Dell XPS 13 (4th Gen)]].}}<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Works after configuration}} || i915<br />
|-<br />
| Wireless || {{G|Works after configuration}} || brcmfmac<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || ?<br />
|-<br />
| Webcam || {{G|Working}} || uvcvideo<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_pci<br />
|-<br />
| Wireless switch || {{G|Working}} || intel_hid<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}} || ?<br />
|}<br />
<br />
<br />
<br />
The Dell XPS 13 2016 (9350) is the third-generation model of the XPS 13 line. The laptop is available in both a standard edition with Windows installed as well as a Developer Edition which only differs in that it comes with Ubuntu installed as well as the Broadcom WiFi card replaced with an Intel WiFi card. Just like the older versions ([[Dell XPS 13]] and [[Dell XPS 13 (2015)]]) it can be bought in different hardware configurations.<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.3, the Intel Skylake architecture is supported.<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 (9350) 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/19/Drivers/DriversDetails?driverId=PWD5K&fileId=3505631210&osCode=WT64A&productCode=xps-13-9350-laptop&languageCode=EN&categoryId=AP&dgc=BA&cid=299605&lid=5718620&acd=123092226602942957c94940922&ven3=120619725550599228 Dell].<br />
<br />
== BIOS ==<br />
=== USB not found ===<br />
It may happen that the Arch Linux USB won't be recognized. You have to disable secure boot (Secure Boot > Disable) and then enable the legacy (General > Advanced Boot Options > Enable Legacy Option ROMs).<br />
<br />
=== No UEFI system found ===<br />
Sometimes the BIOS UEFI does not respect the efivars. In this case you have manually add your efi file in BIOS boot options by going to General > Boot Sequence > Add Boot Option.<br />
<br />
=== Updates ===<br />
[http://downloads.dell.com/FOLDER03769593M/1/XPS_9350_1.4.4.exe BIOS update 1.4.4] was released on 2016-06-30. Store the update binary on your EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, and choose BIOS Update in the F12 boot menu.<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 />
In the event of devices not working correctly, ensure that you have updated to the latest BIOS (above) and Thunderbolt firmware (below).<br />
<br />
[http://downloads.dell.com/FOLDER03798029M/1/Intel_TBT3_FW_UPDATE_NVM16_A04_2.16.01.003.exe Thunderbolt 3 Firmware Update 2.16.01.003, A04] was released on 2016-08-10. Unlike the BIOS update, this is a graphical application which must be run in a modern Windows environment (MS-DOS will not suffice).<br />
<br />
Hotplug support for this port requires a [https://bugzilla.kernel.org/show_bug.cgi?id=115121 bug fix] which landed in kernel version 4.7. It also requires the kernel to be built with <tt>CONFIG_PCI_HOTPLUG=y</tt>.<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 />
=== Dual booting Linux and Windows ===<br />
In order to boot into Windows properly without getting an {{ic|INACCESSIBLE_BOOT_DEVICE}} error with disabled {{ic|RAID}} you must configure Windows to use the {{ic|AHCI}}-speaking SATA storage controller, assuming you used {{ic|AHCI}} for installing Linux. The driver is effectively disabled even though it is installed. Either of the following methods were reported to activate the drivers without reinstallation (your mileage may vary):<br />
<br />
* [http://www.tenforums.com/drivers-hardware/15006-attn-ssd-owners-enabling-ahci-mode-after-windows-10-installation.html booting into safe mode and back]<br />
* [https://samnicholls.net/2016/01/14/how-to-switch-sata-raid-to-ahci-windows-10-xps-13/ Selecting {{ic|Microsoft Storage Spaces Controller}} in Windows Device Manager]<br />
* [http://www.tenforums.com/tutorials/22631-ahci-enable-windows-8-windows-10-after-installation.html Modifying registry entries]<br />
* [http://superuser.com/questions/471102/change-from-ide-to-ahci-after-installing-windows-8/471108#471108 Modifying other registry entries]<br />
<br />
Consult the [https://support.microsoft.com/en-us/kb/2795397 microsoft support] page for additional information. Be aware that some manufactures propagate reinstalling Windows to be the only solution, which it is not.<br />
<br />
== NVM Express SSD ==<br />
=== Cannot find root device ===<br />
The location of the {{ic|nvme}} module for [[wikipedia:NVM_Express|"NVM Express"]] SSD has changed between {{Pkg|linux}} kernel version 4.3 and 4.4. If you experience "cannot find root device" on boot, it may be due to the [https://bugs.archlinux.org/task/47761 {{ic|nvme}} module not being present in {{ic|initramfs}}]. In this case, the following may resolve your issue.<br />
<br />
Edit your {{ic|/etc/mkinitcpio.conf}} file:<br />
...<br />
MODULES="... nvme"<br />
...<br />
<br />
Then update the bootloader.<br />
<br />
# mkinitcpio -p linux<br />
<br />
where {{ic|linux}} is the name of the image loaded on boot. If you installed {{AUR|linux-mainline}} then change that to {{ic|linux-mainline}}.<br />
<br />
=== Note on Mount Options ===<br />
<br />
Using the {{ic|discard}} mount option for your filesystem is not recommended, as mentioned in [[Solid_State_Drives#Continuous TRIM|this warning]] and [https://bbs.archlinux.org/viewtopic.php?pid=1593544#p1593544 the forum]. See also [[Solid State Drives/NVMe#Discards]] for further information.<br />
<br />
=== NVME Power Saving Patch ===<br />
<br />
As of August 30, 2016 Andy Lutomirski has released version 2 of his 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 package 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}}}}<br />
<br />
== Wireless ==<br />
<br />
For the non-developer edition, the built-in Broadcom BCM4350 is now supported in the current {{Pkg|linux}} kernel (as of version 4.4.1-1). The wireless module {{ic|brcmfmac}} also needs the firmware {{ic|brcmfmac4350-pcie.bin}} from the related {{Pkg|linux-firmware}} package.<br />
<br />
The Broadcom adapter does not report its regulatory country and so, by default, the global settings for channels and frequencies will be set. See [[Wireless network configuration#Respecting the regulatory domain]] for more information about how this can be changed.<br />
<br />
== Bluetooth ==<br />
<br />
=== Intel WiFi ===<br />
If your WiFi card supports Bluetooth, then the BT interface should be available out-of-the-box, as the required firmware is included in {{pkg|linux-firmware}}.<br />
<br />
=== Broadcom Wifi ===<br />
Bluetooth should work right away. Load the module {{ic|btusb}} and {{ic|bluetooth}} if it was not already and [[start]]/[[enable]] {{ic|bluetooth.service}}. Refer to [[Bluetooth]] for more information and configuration options.<br />
<br />
==== Wireless headset: strange bluetooth behavior ====<br />
<br />
If your Bluetooth behaves weird, such as being able to connect but not to listen through it, etc. You probably need the firmware.<br />
<br />
The Broadcom Bluetooth firmware is not available in the kernel (the same as for the 2015 model [http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), therefore you will have to retrieve it from a Windows [http://downloads.dell.com/FOLDER03272920M/1/9350_Network_Driver_XMJK7_WN32_12.0.1.720_A00.EXE .exe]. You need to extract the {{ic|.exe}} file with {{Pkg|p7zip}} and then convert it to a {{ic|.hcd}} file with ''hex2hcd'' from {{Pkg|bluez-utils}}:<br />
<br />
$ 7z x 9350_Network_Driver_XMJK7_WN32_12.0.1.720_A00.EXE<br />
$ cp Win32/BCM4350C5_003.006.007.0095.1703.hex ./<br />
$ hex2hcd BCM4350C5_003.006.007.0095.1703.hex<br />
# mv BCM4350C5_003.006.007.0095.1703.hcd /lib/firmware/brcm/BCM-0a5c-6412.hcd<br />
<br />
After reboot, the firmware should be available for your Bluetooth interface.<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 />
=== 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 paramter 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 />
=== Linux kernel 4.3 or earlier ===<br />
<br />
If you are using an older kernel 4.3 or earlier, you also require the kernel parameter {{ic|i915.preliminary_hw_support&#61;1}}, see [[Intel graphics#Skylake support]]. (For later kernels 4.3+ or {{AUR|linux-bcm4350}} the parameter is unnecessary.)<br />
<br />
=== Linux kernel 4.5 or earlier ===<br />
<br />
If you have the newer i7-6560 CPU with Iris 540 graphics, the GPU hangs every few minutes with kernel versions before 4.6. This is probably due to this bug https://bugs.freedesktop.org/show_bug.cgi?id=94161 and can be countered by either disabling DRI in your Xorg configuration:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "DRI" "false"<br />
EndSection<br />
}}<br />
<br />
or by adding {{ic|1=i915.enable_rc6=0}} to the kernel boot parameters.<br />
<br />
== Touchpad ==<br />
Only key-presses work out of the box. Installing {{pkg|xf86-input-libinput}} is sufficient for proper mouse support plus it also handles the touchscreen - see [[libinput]] for configuration. Features such as tap-to-click are usually adjustable within the [[desktop environment]].<br />
<br />
Alternatively you may want to install {{pkg|xf86-input-synaptics}} as driver but "it is on maintenance mode and {{pkg|xf86-input-libinput}} must be preferred over" (installation note from the package itself). Plus it may lack the ability to be easily adjustable within your [[desktop environment]] (see [[Dell Studio XPS 13]]). Restarting the X server might be required.<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 />
=== Gestures ===<br />
<br />
Refer to [[libinput#Gestures]] for information about the current development state and available methods.<br />
<br />
== Sound ==<br />
<br />
=== Hissing/Crackling noises when using headphones ===<br />
<br />
Some people reported white hissing/crackling noises when using headphones. To get rid of them you can run {{ic|alsamixer}} from {{Pkg|alsa-utils}}.<br />
Select your soundcard with F6 and set the headset-gain to 22 (3rd lever from the left) or use the {{ic|amixer}} command:<br />
<br />
$ amixer -c 0 cset 'numid=10' 1<br />
numid=10,iface=MIXER,name='Headphone Mic Boost Volume'<br />
; type=INTEGER,access=rw---R--,values=2,min=0,max=3,step=0<br />
: values=1,1<br />
| dBscale-min=0.00dB,step=10.00dB,mute=0<br />
<br />
Unfortunately [[PulseAudio]] will override the above setting every time you log in/out of your environment (or every time the PulseAudio service is restarted), even if the {{ic|alsa-restore.service}} is enabled at [[start]] up.<br />
<br />
To work around this issue, edit {{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-input-headphone-mic.conf}} and comment out the section {{ic|[Element Headphone Mic Boost]}}:<br />
<br />
---<br />
#[Element Headphone Mic Boost]<br />
#required-any = any<br />
#switch = select<br />
#volume = merge<br />
#override-map.1 = all<br />
#override-map.2 = all-left,all-right<br />
---<br />
<br />
Similarly in {{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf}}, comment out the same section:<br />
<br />
---<br />
#[Element Headphone Mic Boost]<br />
#switch = off<br />
#volume = off<br />
---<br />
<br />
This will prevent PulseAudio to fiddle with the gain setting at all.<br />
<br />
{{Note|Unfortunately, you must make the same modifications every time the PulseAudio package is updated. Additionally, this will entirely disable the internal microphone.}}<br />
<br />
=== Loud popping-noises when sound was not playing ===<br />
<br />
Also people noticed loud popping-noises when sound was not playing.<br />
You can turn off the sound_power_save in through e.g. {{ic|tlp}} <br />
<br />
# nano /etc/default/tlp<br />
...<br />
SOUND_POWER_SAVE_ON_BAT = 0 <br />
...<br />
<br />
== Microphone ==<br />
{{Note| Not all hardware has the "Digital" channel}}<br />
For ALSA, increase "Digital" channel for microphone to work.<br />
<br />
== CPU slowdown after resume from suspend ==<br />
If you are experiencing a very slow computer after resume from suspend, you may be subject to a bug where your CPU frequency is capped to a very low value. Use {{ic|cpupower frequency-info}} to check. If so, please read [https://bbs.archlinux.org/viewtopic.php?pid=1558948#p1558948 this forum thread] for debug information, and a workaround.<br />
<br />
== Diverting models == <br />
<br />
=== XPS 12 ===<br />
{{Expansion|The XPS 12 features a detachable keyboard.}}<br />
<br />
=== Dell XPS 15 ===<br />
Despite the similarities between the two devices they have quite different solutions for various problems, refer to [[Dell XPS 15]] for more information.<br />
<br />
=== Dell XPS 13 (2015) ===<br />
Information about the predecessor is available at [[Dell XPS 13 (2015)]].<br />
<br />
== lspci and lsusb == <br />
<br />
{{Expansion|Output from ''lspci'' and ''lsusb'' for '''one''' model might be helpful. Different models' hardware (e.g. XPS 12 keyboard, XPS 15 screen) that are susceptible to need different instructions should be pointed out separately (not via a full second hardware output). Alternatively these could be added to [[Laptop/Dell#XPS]]|Talk:Dell XPS 13 (2016)#Thunderbolt and XPS 15.2F13}}<br />
<br />
The <tt>lspci</tt> and <tt>lsusb</tt> below were take from the following system:<br />
<br />
[ 0.000000] DMI: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.3.3 03/01/2016<br />
<br />
on kernel:<br />
<br />
Linux marv 4.5.4-1-ARCH #1 SMP PREEMPT Wed May 11 22:21:28 CEST 2016 x86_64 GNU/Linux<br />
<br />
<br />
=== lspci ===<br />
<br />
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)<br />
00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated Graphics (rev 07)<br />
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)<br />
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)<br />
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)<br />
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)<br />
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)<br />
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)<br />
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)<br />
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)<br />
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)<br />
00:1d.0 PCI bridge: Intel Corporation Device 9d18 (rev f1)<br />
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)<br />
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)<br />
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)<br />
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)<br />
3a:00.0 Network controller: Broadcom Corporation BCM4350 802.11ac Wireless Network Adapter (rev 08)<br />
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)<br />
3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)<br />
<br />
[https://gist.github.com/mgalgs/a903e3528f48aa25b5c0b9ae9c09a07f Full output from sudo lspci -v]<br />
<br />
After plugging in a USB-C hub, a number of new PCI devices appear:<br />
<br />
01:00.0 PCI bridge: Intel Corporation Device 1576<br />
02:00.0 PCI bridge: Intel Corporation Device 1576<br />
02:01.0 PCI bridge: Intel Corporation Device 1576<br />
02:02.0 PCI bridge: Intel Corporation Device 1576<br />
39:00.0 USB controller: Intel Corporation Device 15b5<br />
<br />
=== lsusb ===<br />
<br />
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 001 Device 004: ID 0c45:670c Microdia <br />
Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. <br />
Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. <br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
<br />
[https://gist.github.com/mgalgs/15fb0d19795f700d60f061f67dddbefc Full output from sudo lsusb -v]<br />
<br />
== See also ==<br />
<br />
* [https://bbs.archlinux.org/viewtopic.php?pid=1579113 Arch Forum thread for XPS 13]<br />
* [http://www.dell.com/support/home/us/en/19/product-support/product/xps-13-9350-laptop/drivers Dell XPS 13 9350 driver and firmware updates]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9350)&diff=451842Dell XPS 13 (9350)2016-09-24T23:53:19Z<p>Alexjj: Adde</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Works after configuration}} || i915<br />
|-<br />
| Wireless || {{G|Works after configuration}} || brcmfmac<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || ?<br />
|-<br />
| Webcam || {{G|Working}} || uvcvideo<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_pci<br />
|-<br />
| Wireless switch || {{G|Working}} || intel_hid<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}} || ?<br />
|}<br />
<br />
{{Note|This page refers to the early 2016 model of XPS 13. For the late 2016 model see [[Dell XPS 13 (4th Gen)]].}}<br />
<br />
The Dell XPS 13 2016 (9350) is the third-generation model of the XPS 13 line. The laptop is available in both a standard edition with Windows installed as well as a Developer Edition which only differs in that it comes with Ubuntu installed as well as the Broadcom WiFi card replaced with an Intel WiFi card. Just like the older versions ([[Dell XPS 13]] and [[Dell XPS 13 (2015)]]) it can be bought in different hardware configurations.<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.3, the Intel Skylake architecture is supported.<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 (9350) 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/19/Drivers/DriversDetails?driverId=PWD5K&fileId=3505631210&osCode=WT64A&productCode=xps-13-9350-laptop&languageCode=EN&categoryId=AP&dgc=BA&cid=299605&lid=5718620&acd=123092226602942957c94940922&ven3=120619725550599228 Dell].<br />
<br />
== BIOS ==<br />
=== USB not found ===<br />
It may happen that the Arch Linux USB won't be recognized. You have to disable secure boot (Secure Boot > Disable) and then enable the legacy (General > Advanced Boot Options > Enable Legacy Option ROMs).<br />
<br />
=== No UEFI system found ===<br />
Sometimes the BIOS UEFI does not respect the efivars. In this case you have manually add your efi file in BIOS boot options by going to General > Boot Sequence > Add Boot Option.<br />
<br />
=== Updates ===<br />
[http://downloads.dell.com/FOLDER03769593M/1/XPS_9350_1.4.4.exe BIOS update 1.4.4] was released on 2016-06-30. Store the update binary on your EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, and choose BIOS Update in the F12 boot menu.<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 />
In the event of devices not working correctly, ensure that you have updated to the latest BIOS (above) and Thunderbolt firmware (below).<br />
<br />
[http://downloads.dell.com/FOLDER03798029M/1/Intel_TBT3_FW_UPDATE_NVM16_A04_2.16.01.003.exe Thunderbolt 3 Firmware Update 2.16.01.003, A04] was released on 2016-08-10. Unlike the BIOS update, this is a graphical application which must be run in a modern Windows environment (MS-DOS will not suffice).<br />
<br />
Hotplug support for this port requires a [https://bugzilla.kernel.org/show_bug.cgi?id=115121 bug fix] which landed in kernel version 4.7. It also requires the kernel to be built with <tt>CONFIG_PCI_HOTPLUG=y</tt>.<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 />
=== Dual booting Linux and Windows ===<br />
In order to boot into Windows properly without getting an {{ic|INACCESSIBLE_BOOT_DEVICE}} error with disabled {{ic|RAID}} you must configure Windows to use the {{ic|AHCI}}-speaking SATA storage controller, assuming you used {{ic|AHCI}} for installing Linux. The driver is effectively disabled even though it is installed. Either of the following methods were reported to activate the drivers without reinstallation (your mileage may vary):<br />
<br />
* [http://www.tenforums.com/drivers-hardware/15006-attn-ssd-owners-enabling-ahci-mode-after-windows-10-installation.html booting into safe mode and back]<br />
* [https://samnicholls.net/2016/01/14/how-to-switch-sata-raid-to-ahci-windows-10-xps-13/ Selecting {{ic|Microsoft Storage Spaces Controller}} in Windows Device Manager]<br />
* [http://www.tenforums.com/tutorials/22631-ahci-enable-windows-8-windows-10-after-installation.html Modifying registry entries]<br />
* [http://superuser.com/questions/471102/change-from-ide-to-ahci-after-installing-windows-8/471108#471108 Modifying other registry entries]<br />
<br />
Consult the [https://support.microsoft.com/en-us/kb/2795397 microsoft support] page for additional information. Be aware that some manufactures propagate reinstalling Windows to be the only solution, which it is not.<br />
<br />
== NVM Express SSD ==<br />
=== Cannot find root device ===<br />
The location of the {{ic|nvme}} module for [[wikipedia:NVM_Express|"NVM Express"]] SSD has changed between {{Pkg|linux}} kernel version 4.3 and 4.4. If you experience "cannot find root device" on boot, it may be due to the [https://bugs.archlinux.org/task/47761 {{ic|nvme}} module not being present in {{ic|initramfs}}]. In this case, the following may resolve your issue.<br />
<br />
Edit your {{ic|/etc/mkinitcpio.conf}} file:<br />
...<br />
MODULES="... nvme"<br />
...<br />
<br />
Then update the bootloader.<br />
<br />
# mkinitcpio -p linux<br />
<br />
where {{ic|linux}} is the name of the image loaded on boot. If you installed {{AUR|linux-mainline}} then change that to {{ic|linux-mainline}}.<br />
<br />
=== Note on Mount Options ===<br />
<br />
Using the {{ic|discard}} mount option for your filesystem is not recommended, as mentioned in [[Solid_State_Drives#Continuous TRIM|this warning]] and [https://bbs.archlinux.org/viewtopic.php?pid=1593544#p1593544 the forum]. See also [[Solid State Drives/NVMe#Discards]] for further information.<br />
<br />
=== NVME Power Saving Patch ===<br />
<br />
As of August 30, 2016 Andy Lutomirski has released version 2 of his 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 package 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}}}}<br />
<br />
== Wireless ==<br />
<br />
For the non-developer edition, the built-in Broadcom BCM4350 is now supported in the current {{Pkg|linux}} kernel (as of version 4.4.1-1). The wireless module {{ic|brcmfmac}} also needs the firmware {{ic|brcmfmac4350-pcie.bin}} from the related {{Pkg|linux-firmware}} package.<br />
<br />
The Broadcom adapter does not report its regulatory country and so, by default, the global settings for channels and frequencies will be set. See [[Wireless network configuration#Respecting the regulatory domain]] for more information about how this can be changed.<br />
<br />
== Bluetooth ==<br />
<br />
=== Intel WiFi ===<br />
If your WiFi card supports Bluetooth, then the BT interface should be available out-of-the-box, as the required firmware is included in {{pkg|linux-firmware}}.<br />
<br />
=== Broadcom Wifi ===<br />
Bluetooth should work right away. Load the module {{ic|btusb}} and {{ic|bluetooth}} if it was not already and [[start]]/[[enable]] {{ic|bluetooth.service}}. Refer to [[Bluetooth]] for more information and configuration options.<br />
<br />
==== Wireless headset: strange bluetooth behavior ====<br />
<br />
If your Bluetooth behaves weird, such as being able to connect but not to listen through it, etc. You probably need the firmware.<br />
<br />
The Broadcom Bluetooth firmware is not available in the kernel (the same as for the 2015 model [http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), therefore you will have to retrieve it from a Windows [http://downloads.dell.com/FOLDER03272920M/1/9350_Network_Driver_XMJK7_WN32_12.0.1.720_A00.EXE .exe]. You need to extract the {{ic|.exe}} file with {{Pkg|p7zip}} and then convert it to a {{ic|.hcd}} file with ''hex2hcd'' from {{Pkg|bluez-utils}}:<br />
<br />
$ 7z x 9350_Network_Driver_XMJK7_WN32_12.0.1.720_A00.EXE<br />
$ cp Win32/BCM4350C5_003.006.007.0095.1703.hex ./<br />
$ hex2hcd BCM4350C5_003.006.007.0095.1703.hex<br />
# mv BCM4350C5_003.006.007.0095.1703.hcd /lib/firmware/brcm/BCM-0a5c-6412.hcd<br />
<br />
After reboot, the firmware should be available for your Bluetooth interface.<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 />
=== 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 paramter 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 />
=== Linux kernel 4.3 or earlier ===<br />
<br />
If you are using an older kernel 4.3 or earlier, you also require the kernel parameter {{ic|i915.preliminary_hw_support&#61;1}}, see [[Intel graphics#Skylake support]]. (For later kernels 4.3+ or {{AUR|linux-bcm4350}} the parameter is unnecessary.)<br />
<br />
=== Linux kernel 4.5 or earlier ===<br />
<br />
If you have the newer i7-6560 CPU with Iris 540 graphics, the GPU hangs every few minutes with kernel versions before 4.6. This is probably due to this bug https://bugs.freedesktop.org/show_bug.cgi?id=94161 and can be countered by either disabling DRI in your Xorg configuration:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "DRI" "false"<br />
EndSection<br />
}}<br />
<br />
or by adding {{ic|1=i915.enable_rc6=0}} to the kernel boot parameters.<br />
<br />
== Touchpad ==<br />
Only key-presses work out of the box. Installing {{pkg|xf86-input-libinput}} is sufficient for proper mouse support plus it also handles the touchscreen - see [[libinput]] for configuration. Features such as tap-to-click are usually adjustable within the [[desktop environment]].<br />
<br />
Alternatively you may want to install {{pkg|xf86-input-synaptics}} as driver but "it is on maintenance mode and {{pkg|xf86-input-libinput}} must be preferred over" (installation note from the package itself). Plus it may lack the ability to be easily adjustable within your [[desktop environment]] (see [[Dell Studio XPS 13]]). Restarting the X server might be required.<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 />
=== Gestures ===<br />
<br />
Refer to [[libinput#Gestures]] for information about the current development state and available methods.<br />
<br />
== Sound ==<br />
<br />
=== Hissing/Crackling noises when using headphones ===<br />
<br />
Some people reported white hissing/crackling noises when using headphones. To get rid of them you can run {{ic|alsamixer}} from {{Pkg|alsa-utils}}.<br />
Select your soundcard with F6 and set the headset-gain to 22 (3rd lever from the left) or use the {{ic|amixer}} command:<br />
<br />
$ amixer -c 0 cset 'numid=10' 1<br />
numid=10,iface=MIXER,name='Headphone Mic Boost Volume'<br />
; type=INTEGER,access=rw---R--,values=2,min=0,max=3,step=0<br />
: values=1,1<br />
| dBscale-min=0.00dB,step=10.00dB,mute=0<br />
<br />
Unfortunately [[PulseAudio]] will override the above setting every time you log in/out of your environment (or every time the PulseAudio service is restarted), even if the {{ic|alsa-restore.service}} is enabled at [[start]] up.<br />
<br />
To work around this issue, edit {{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-input-headphone-mic.conf}} and comment out the section {{ic|[Element Headphone Mic Boost]}}:<br />
<br />
---<br />
#[Element Headphone Mic Boost]<br />
#required-any = any<br />
#switch = select<br />
#volume = merge<br />
#override-map.1 = all<br />
#override-map.2 = all-left,all-right<br />
---<br />
<br />
Similarly in {{ic|/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf}}, comment out the same section:<br />
<br />
---<br />
#[Element Headphone Mic Boost]<br />
#switch = off<br />
#volume = off<br />
---<br />
<br />
This will prevent PulseAudio to fiddle with the gain setting at all.<br />
<br />
{{Note|Unfortunately, you must make the same modifications every time the PulseAudio package is updated. Additionally, this will entirely disable the internal microphone.}}<br />
<br />
=== Loud popping-noises when sound was not playing ===<br />
<br />
Also people noticed loud popping-noises when sound was not playing.<br />
You can turn off the sound_power_save in through e.g. {{ic|tlp}} <br />
<br />
# nano /etc/default/tlp<br />
...<br />
SOUND_POWER_SAVE_ON_BAT = 0 <br />
...<br />
<br />
== Microphone ==<br />
{{Note| Not all hardware has the "Digital" channel}}<br />
For ALSA, increase "Digital" channel for microphone to work.<br />
<br />
== CPU slowdown after resume from suspend ==<br />
If you are experiencing a very slow computer after resume from suspend, you may be subject to a bug where your CPU frequency is capped to a very low value. Use {{ic|cpupower frequency-info}} to check. If so, please read [https://bbs.archlinux.org/viewtopic.php?pid=1558948#p1558948 this forum thread] for debug information, and a workaround.<br />
<br />
== Diverting models == <br />
<br />
=== XPS 12 ===<br />
{{Expansion|The XPS 12 features a detachable keyboard.}}<br />
<br />
=== Dell XPS 15 ===<br />
Despite the similarities between the two devices they have quite different solutions for various problems, refer to [[Dell XPS 15]] for more information.<br />
<br />
=== Dell XPS 13 (2015) ===<br />
Information about the predecessor is available at [[Dell XPS 13 (2015)]].<br />
<br />
== lspci and lsusb == <br />
<br />
{{Expansion|Output from ''lspci'' and ''lsusb'' for '''one''' model might be helpful. Different models' hardware (e.g. XPS 12 keyboard, XPS 15 screen) that are susceptible to need different instructions should be pointed out separately (not via a full second hardware output). Alternatively these could be added to [[Laptop/Dell#XPS]]|Talk:Dell XPS 13 (2016)#Thunderbolt and XPS 15.2F13}}<br />
<br />
The <tt>lspci</tt> and <tt>lsusb</tt> below were take from the following system:<br />
<br />
[ 0.000000] DMI: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.3.3 03/01/2016<br />
<br />
on kernel:<br />
<br />
Linux marv 4.5.4-1-ARCH #1 SMP PREEMPT Wed May 11 22:21:28 CEST 2016 x86_64 GNU/Linux<br />
<br />
<br />
=== lspci ===<br />
<br />
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)<br />
00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated Graphics (rev 07)<br />
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)<br />
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)<br />
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)<br />
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)<br />
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)<br />
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)<br />
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)<br />
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)<br />
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)<br />
00:1d.0 PCI bridge: Intel Corporation Device 9d18 (rev f1)<br />
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)<br />
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)<br />
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)<br />
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)<br />
3a:00.0 Network controller: Broadcom Corporation BCM4350 802.11ac Wireless Network Adapter (rev 08)<br />
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)<br />
3c:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller (rev 01)<br />
<br />
[https://gist.github.com/mgalgs/a903e3528f48aa25b5c0b9ae9c09a07f Full output from sudo lspci -v]<br />
<br />
After plugging in a USB-C hub, a number of new PCI devices appear:<br />
<br />
01:00.0 PCI bridge: Intel Corporation Device 1576<br />
02:00.0 PCI bridge: Intel Corporation Device 1576<br />
02:01.0 PCI bridge: Intel Corporation Device 1576<br />
02:02.0 PCI bridge: Intel Corporation Device 1576<br />
39:00.0 USB controller: Intel Corporation Device 15b5<br />
<br />
=== lsusb ===<br />
<br />
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub<br />
Bus 001 Device 004: ID 0c45:670c Microdia <br />
Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. <br />
Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. <br />
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br />
<br />
[https://gist.github.com/mgalgs/15fb0d19795f700d60f061f67dddbefc Full output from sudo lsusb -v]<br />
<br />
== See also ==<br />
<br />
* [https://bbs.archlinux.org/viewtopic.php?pid=1579113 Arch Forum thread for XPS 13]<br />
* [http://www.dell.com/support/home/us/en/19/product-support/product/xps-13-9350-laptop/drivers Dell XPS 13 9350 driver and firmware updates]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=451841Dell XPS 13 (9343)2016-09-24T23:52:22Z<p>Alexjj: added link to 4th gen</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (2015)]]<br />
{{Note|This page refers to the early 2015 model of XPS 13. For the late 2015 model, see [[Dell XPS 13 (2016)]], and late 2016 model see [[Dell XPS 13 (4th Gen)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| Video || {{G|Working}}<br />
|-<br />
| Backlight control || {{G|Working}}<br />
|-<br />
| Wireless || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{G|Works after configuration}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Wireless switch || {{Y|Works (Broadcom WiFi has some [[#rfkill_issues_with_Broadcom_wireless|issues]])}}<br />
|}<br />
<br />
The [http://www.dell.com/us/p/xps-13-9343-laptop/pd 2015 Dell XPS 13 (9343)] is the second-generation model of Dell's XPS 13 line. Like its predecessor, it has official Linux support courtesy of Dell's Project Sputnik team. They target Ubuntu 14.04 LTS, but the improvements and support from the Sputnik team are generally applicable to all distros.<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.1.3, a patched kernel is no longer necessary. However, some manual configuration is still recommended to get the best experience.<br />
<br />
== Model differences ==<br />
Although the XPS 13 is sold in a variety of configurations in most markets, those wanting to run Linux should pay special attention to display options (FHD/QHD+) and WiFi adapter differences (Dell DW1560 vs. Intel 7265). For users with the QHD+ model, you'll need to use a DE/WM that properly supports [[HiDPI]]. Regarding the WiFi adapter choices, both cards do work in Arch, but the Dell DW1560 requires a proprietary kernel module that is not well-supported, whereas the Intel 7265 is supported by the mainline kernel.<br />
<br />
There are no exclusive hardware differences between the Developer Edition and the Windows edition of this laptop; this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
[http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=MNWHN&fileId=3564153400 BIOS update A09] was released on 2016-08-30. With A02 or newer, almost everything should work out of the box, and the kernel boot parameters that were used in conjunction with earlier BIOS versions are no longer necessary. Store the update binary on your EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, and choose BIOS Update in the F12 boot menu.<br />
<br />
=== Backlight ===<br />
Works out-of-the-box:<br />
* The [[Backlight#systemd-backlight_service|systemd-backlight.service]] takes care of both eDP panel and keyboard backlight (and any other external device) status, saving at shutdown and restoring their values at boot.<br />
* hardware keys ({{ic|Fn-F10}} to {{ic|Fn-F12}}) works without any operation, as well.<br />
<br />
=== SSD ===<br />
This laptop series comes with a SSD as storage device; this section aims to remind you that this technology needs some configuration in order to achieve the best operative conditions. See [[Solid State Drives]] for information.<br />
<br />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} (in this case, remember to install {{ic|linux-headers}} too; even if it is listed as an optional dependency) to be installed. See the [[Broadcom wireless]] page for more details and/or assistance.<br />
<br />
Some higher-end models do not use the Dell-branded Broadcom adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is widely available as an aftermarket purchase for those wishing to replace the Broadcom adapter in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and a much higher throughput, making it an worthwhile upgrade should you decide to do so.<br />
<br />
=== Bluetooth ===<br />
{{Note|'''Intel WiFi users:''' If your WiFi card supports Bluetooth, then the BT interface should be available out-of-the-box, as the required firmware is included in {{pkg|linux-firmware}}.}}<br />
<br />
The Broadcom Bluetooth firmware is not available in the kernel ([http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), so you will need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use bluetooth.<br />
<br />
Alternatively, you can retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] yourself. You need to extract the {{ic|.cab}} file with {{Pkg|cabextract}} and then convert it to a {{ic|.hcd}} file with ''hex2hcd'' from {{Pkg|bluez-utils}}:<br />
<br />
$ cabextract 20662520_6c535fbfa9dca0d07ab069e8918896086e2af0a7.cab<br />
$ hex2hcd BCM20702A1_001.002.014.1443.1572.hex<br />
# mv BCM20702A1_001.002.014.1443.1572.hcd /lib/firmware/brcm/BCM20702A1-0a5c-216f.hcd<br />
# ln -rs /lib/firmware/brcm/BCM20702A1-0a5c-216f.hcd /lib/firmware/brcm/BCM20702A0-0a5c-216f.hcd<br />
<br />
After reboot, the firmware should be available for your Bluetooth interface.<br />
<br />
=== Audio ===<br />
{{Note|Proper audio support is dependent on having the latest BIOS update. If you have not yet updated to BIOS A02 or newer, please do that first.}}<br />
<br />
The sound chipset in this laptop, a Realtek ALC3263, is described as "dual-mode", meaning it supports both the [[wikipedia:Intel_High_Definition_Audio|HDA standard]] and the [[wikipedia:I²S|I2S standard]]. The embedded controller in the XPS 13 uses the [[wikipedia:Advanced_Configuration_and_Power_Interface|ACPI]] _REV value provided by the OS you use to determine which mode the sound chipset should be initialized in at boot.<br />
<br />
==== HDA mode ====<br />
With BIOS A02+ and Arch kernel '''4.3 or older''', the sound card will be initialized in HDA mode.<br />
<br />
To use HDA mode on newer kernels, compile your kernel with the option {{ic|1=CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y}}. This will force HDA mode on; you will not be able to use I2S mode.<br />
<br />
===== Setting the default sound card =====<br />
By default, ALSA doesn't output sound to the PCH card but to the HDMI card. This can be changed by following [[ALSA#Set the default sound card]]. To set the proper order, create the following {{ic|.conf}} file in {{ic|/etc/modprobe.d/}} [https://bbs.archlinux.org/viewtopic.php?pid=1446773#p1446773]:<br />
<br />
{{hc|/etc/modprobe.d/alsa-base.conf|2=<br />
options snd_hda_intel index=1,0<br />
}}<br />
<br />
Note that if you are dual-booting with Windows, you will have to do a cold boot twice before HDA sound will work in Linux and vice-versa. This is not necessary in I2S mode.<br />
<br />
==== I2S mode ==== <br />
With BIOS A02+ and Arch kernel '''4.4 or newer''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0 or newer.[http://www.spinics.net/lists/linux-acpi/msg57457.html]<br />
<br />
{{Note|1=Kernels 4.5-4.7 require the options {{ic|1=CONFIG_DW_DMAC=y}} and {{ic|1=SND_SOC_INTEL_BROADWELL_MACH=m}} to be statically compiled[https://bugzilla.redhat.com/show_bug.cgi?id=1308792#c21]; otherwise, the sound card will not be recognized. This has been resolved in Arch kernel 4.5.2+[https://bugs.archlinux.org/task/48936]; meanwhile, a better fix is forthcoming in kernel 4.8.[https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?h=topic/intel&id=a395bdd6b24b692adbce0df6510ec9f2af57573e]}}<br />
<br />
===== Enabling the microphone =====<br />
{{Note|The microphone appears to be enabled by default as of Arch kernel 4.5.3, so these instructions may be unnecessary.[https://bugs.archlinux.org/task/47989#comment146876]}}<br />
<br />
In I2S mode, the built-in microphone is muted by default. To enable it you have to unmute {{ic|Mic}} item; follow the instructions below in order to achieve the goal:<br />
* open {{ic|alsamixer}} (an utility included into the {{pkg|alsa-utils}} package)<br />
* press {{ic|F6}} and select the '''''broadwell-rt286''''' sound card<br />
* press {{ic|F4}} to switch to the ''Capture view'' and ensure that '''ADC0''' has the ''CAPTURE'' label. If it doesn't, toggle over to it with your arrow keys and press the spacebar to turn it on ''CAPTURE''<br />
* finally, toggle over to the '''Mic''' item and raise the volume to 100.<br />
<br />
{{Note|Switching the '''port''' (from Main Microphone and Headset Microphone (unplugged)) of the only {{ic|Input Devices}} tab entry in the `pavucontrol` application, has the same effect of the above instructions.}}<br />
<br />
=== Touchpad ===<br />
With the latest BIOS, the touchpad should work out-of-the-box with either the synaptics or libinput drivers.<br />
<br />
==== Synaptics driver ====<br />
For more advanced settings with the Synaptics driver, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]].<br />
<br />
If the touchpad freezes when you use more than one finger, try enabling Clickpad mode with {{ic|1=synclient Clickpad=1}}.<br />
<br />
==== Libinput driver ====<br />
For better multi-touch support, you can use {{pkg|xf86-input-libinput}}. The libinput driver supports nearly all button layouts out of the box with few additional settings. <br />
<br />
{{hc|/etc/X11/xorg.conf.d/50-libinput.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD Touchpad"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
Refer to {{ic|man libinput}} for more configurable options (e.g. NaturalScrolling, MiddleEmulation.)<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.6.5 and {{pkg|tlp}}, the idle power usage can reach ~2.3 W with the [[kernel parameter]] {{ic|1=pcie_aspm=force}} enabled.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak performance and monitor power consumption.<br />
<br />
{{Note|1=&nbsp;<br />
* With kernel 4.6+, frame-buffer compression (FBC) and panel self-refresh (PSR) are enabled by default, so {{ic|i915.enable_fbc}} and {{ic|i915.enable_psr}} are no longer needed. Kernel 4.6.2+ is recommended as older kernels may cause the display to flicker.<br />
* {{ic|1=i915.lvds_downclock=1}} for LVDS downclock is no longer needed. According to irc #intel-gfx, "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use."<br />
* {{ic|1=i915.enable_rc6=7}} is useless on Broadwell/gen8 systems. The deeper GPU power states that this option enables (RC6p and RC6pp) do not exist on gen7+ hardware.[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/i915_drv.h#n2862][https://lists.freedesktop.org/archives/intel-gfx/2012-June/018383.html]<br />
}}<br />
<br />
=== Calibrated ICC profile for QHD+ models ===<br />
{{Warning|This profile is only for QHD+ models. Do not use it if you have the FHD model of the XPS 13.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the color attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document editing and publishing. The following ICC profiles are made with DispcalGUI, ArgyllCMS and a spectrophotometer for absolute color accuracy. It is possible to achieve better results by calibrating your own monitor, but generally this profile will be an improvement over the stock profile.<br />
<br />
This profile has been made with the spectrophotometer's high resolution spectral mode, with white and black level drift compensation, the high quality ArgyllCMS switch and 3440 patches. Dynamic Brightness Control has been disabled and the monitor has been turned on at least 30 minutes before commencing the calibration.<br />
<br />
* [https://mega.nz/#!nkNVQDCI!YYcS32HLWk1Aqry30dmOrt0wrfH9W_VczNesHQEpG_U QHD+, D65, Gamma 2.2, max luminance].<br />
<br />
== Troubleshooting ==<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
<br />
{{Out of date|kept for users of other distros until the fix is released upstream.}}<br />
<br />
Update {{pkg|xf86-video-intel}} if you haven't already; this should fix the issue.<br />
<br />
=== Graphical artifacting/instability after S3 resume ===<br />
If you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend, you may want to [[Intel_graphics#SNA_issues|switch your Intel graphics acceleration from SNA to UXA]]. Switching to UXA, however, will result in decreased performance. Switching to xf86-video-modesetting (glamor acceleration) should not decrease performance much, however it is still not known if will fix resume.<br />
<br />
=== Connection issues with Broadcom wireless ===<br />
If {{ic|wifi-menu}} and {{ic|iwlist scan}} fail after driver installation and reboot, try disabling "Wireless Switch" control in the BIOS.<br />
<br />
=== rfkill issues with Broadcom wireless ===<br />
With kernel 4.4 and Broadcom WiFi card, the wireless switch has no effect except freezing the pointer in the KDE desktop. To unfreeze it, switch to another virtual console and back.<br />
<br />
With lower kernel versions, it switches the wireless card on/off at the hardware level, but the Broadcom driver does not not react to it properly: it does not realise the card is off, and only sees a lost connection. It then fails to recover when the card is switched back on. You can work-around this issue by switching WiFi off and on again in the NetworkManager applet or by setting {{ic|/sys/class/rfkill/rfkill0/state}} to 0 and then 1. Alternatively, you can disable the "Wireless Switch" control in the firmware setup.<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A07, the BIOS does not pass any boot parameters to the kernel. Use a UEFI [[boot loader]] instead. [[systemd-boot]] will work with current kernels.<br />
<br />
=== Random kernel hangs at boot ===<br />
See [https://bugzilla.kernel.org/show_bug.cgi?id=105251 here]. This issue seems to only affect those with touchscreens. The fix consists in removing "keyboard" from the HOOKS in /etc/mkinitcpio.conf and instead using MODULES="atkbd.ko usbhid hid-generic" (if you need the keyboard hook). You will have to run {{ic|mkinitcpio -p linux}} as root afterwards.<br />
<br />
=== Sound doesn't work after upgrading to kernel 4.4+ ===<br />
You need to do two cold boots (''don't'' reboot; shutdown and turn back on again) to make sound work again. This is necessary because I2S support was enabled in the Arch 4.4 stock kernel, and the XPS 13's embedded controller requires two cold boots to recognize changes in the sound chipset mode. <br />
<br />
Refer to the Audio section above for more info, as well as the [https://bbs.archlinux.org/viewtopic.php?id=208674 BBS thread] and [https://bugs.archlinux.org/task/47989 Arch bug report].<br />
<br />
=== Loud cracks/noise during boot or audio playback ===<br />
Some users have reported above sound outputs, as described e.g. in [https://bbs.archlinux.org/viewtopic.php?id=208496 this BBS thread]. [https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback Disabling audio powersafe] may work for people using the '''HDA''' audio mode. However, it is still unknown how to solve this issue for the '''I2S''' audio mode. For further reference, see the corresponding [https://bugzilla.kernel.org/show_bug.cgi?id=112611 kernel bug record].<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<br />
* [http://bartongeorge.net/2015/08/28/recent-fixes-for-xps-13-developer-edition/ Recent Fixes for XPS 13 developer edition]<br />
* [http://bartongeorge.net/2015/02/23/update-2-dell-xps-13-laptop-developer-edition-sputnik-gen-4/ Update 2: Dell XPS 13 laptop, developer edition – Sputnik Gen 4]<br />
* [http://bartongeorge.net/2015/02/05/update-dell-xps-13-laptop-developer-edition-sputnik-gen-4/ Update: Dell XPS 13 laptop, developer edition – Sputnik Gen 4]<br />
* [http://bartongeorge.net/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9360)&diff=451341Dell XPS 13 (9360)2016-09-21T05:32:03Z<p>Alexjj: spell fourth correctly.</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{B|Not released yet}} || ?<br />
|-<br />
| Wireless || {{B|Not released yet}} || ?<br />
|-<br />
| Bluetooth || {{B|Not released yet}}|| ?<br />
|-<br />
| Audio || {{B|Not released yet}} || ?<br />
|-<br />
| Touchpad || {{B|Not released yet}} || ?<br />
|-<br />
| Webcam || {{B|Not released yet}} || ?<br />
|-<br />
| USB-C / Thunderbolt 3 || {{B|Not released yet}} || ?<br />
|-<br />
| Wireless switch || {{B|Not released yet}} || ?<br />
|-<br />
| Function/Multimedia Keys || {{B|Not released yet}} || ?<br />
|}<br />
<br />
<br />
<br />
<br />
The Dell XPS 13 Late 2016 (model number?) is the fourth-generation model of the XPS 13 line. The laptop will be available early October in both a standard edition with Windows installed as well as a Developer Edition with Ubuntu installed, hardware differences not known yet. Just like the older versions ([[Dell XPS 13]], [[Dell XPS 13 (2015)]]), [[Dell XPS 13 (2016)]]) it will be available in different hardware configurations. This fourth gen model includes Intel's Kaby Lake CPU and configurable with up to 16GB RAM and a 1TB PCI SSD. It will now also be available in Rose Gold.<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.</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9360)&diff=451340Dell XPS 13 (9360)2016-09-21T05:31:20Z<p>Alexjj: Started 4th gen page</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{B|Not released yet}} || ?<br />
|-<br />
| Wireless || {{B|Not released yet}} || ?<br />
|-<br />
| Bluetooth || {{B|Not released yet}}|| ?<br />
|-<br />
| Audio || {{B|Not released yet}} || ?<br />
|-<br />
| Touchpad || {{B|Not released yet}} || ?<br />
|-<br />
| Webcam || {{B|Not released yet}} || ?<br />
|-<br />
| USB-C / Thunderbolt 3 || {{B|Not released yet}} || ?<br />
|-<br />
| Wireless switch || {{B|Not released yet}} || ?<br />
|-<br />
| Function/Multimedia Keys || {{B|Not released yet}} || ?<br />
|}<br />
<br />
<br />
<br />
<br />
The Dell XPS 13 Late 2016 (model number?) is the forth-generation model of the XPS 13 line. The laptop will be available early October in both a standard edition with Windows installed as well as a Developer Edition with Ubuntu installed, hardware differences not known yet. Just like the older versions ([[Dell XPS 13]], [[Dell XPS 13 (2015)]]), [[Dell XPS 13 (2016)]]) it will be available in different hardware configurations. This forth gen model includes Intel's Kaby Lake CPU and configurable with up to 16GB RAM and a 1TB PCI SSD. It will now also be available in Rose Gold.<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.</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9350)&diff=451339Talk:Dell XPS 13 (9350)2016-09-21T05:21:31Z<p>Alexjj: Just made the new 4th gen page</p>
<hr />
<div>Added a section for kernel specific configurations.<br />
<br />
== <s> SATA controller </s> ==<br />
Potentially useful blog post?: https://samnicholls.net/2016/01/14/how-to-switch-sata-raid-to-ahci-windows-10-xps-13/ (disclaimer: it's mine) on getting around the SATA controller issue for those who need to dual boot, works on my 9350 but ymmv. [[User:Samstudio8|Samstudio8]] ([[User talk:Samstudio8|talk]]) 04:11, 14 January 2016 (UTC)<br />
<br />
: I described your suggested solutions in the main article. Feel free to correct any mistakes. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 10:10, 15 July 2016 (UTC)<br />
<br />
== Release of 4.4 in testing ==<br />
<br />
I made a slew of edits and some clean up related to the release of 4.4 in testing. Let me know if you see any issues. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:24, 20 January 2016 (UTC)<br />
<br />
== BIOS update 1.1.9 ==<br />
<br />
Since the BIOS update, I get some errors, with stack dump during suspend/resume.<br />
<br />
[ 0.448742] ------------[ cut here ]------------<br />
[ 0.448744] WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page+0x5e1/0x780()<br />
[ 0.448745] x86/mm: Found insecure W+X mapping at address ffff880000000000/0xffff880000000000<br />
[ 0.448746] Modules linked in:<br />
[ 0.448748] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-3-ARCH #1<br />
[ 0.448749] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 0.448750] 0000000000000000 00000000271d54da ffff8802771afd48 ffffffff812c8a99<br />
[ 0.448752] ffff8802771afd90 ffff8802771afd80 ffffffff810771c2 ffff8802771afe90<br />
[ 0.448754] 8000000000000163 0000000000000004 0000000000000000 0000000000000000<br />
[ 0.448755] Call Trace:<br />
[ 0.448758] [<ffffffff812c8a99>] dump_stack+0x4b/0x72<br />
[ 0.448760] [<ffffffff810771c2>] warn_slowpath_common+0x82/0xc0<br />
[ 0.448762] [<ffffffff8107725c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 0.448763] [<ffffffff8106c4c1>] note_page+0x5e1/0x780<br />
[ 0.448765] [<ffffffff8106c967>] ptdump_walk_pgd_level_core+0x307/0x450<br />
[ 0.448766] [<ffffffff8106cae7>] ptdump_walk_pgd_level_checkwx+0x17/0x20<br />
[ 0.448768] [<ffffffff8106278f>] mark_rodata_ro+0xef/0x100<br />
[ 0.448770] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448771] [<ffffffff8158636d>] kernel_init+0x1d/0xe0<br />
[ 0.448773] [<ffffffff8159290f>] ret_from_fork+0x3f/0x70<br />
[ 0.448774] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448775] ---[ end trace b1a5026ad8272458 ]---<br />
<br />
[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:48, 20 January 2016 (UTC)<br />
<br />
Since latest kernel update (4.4.1-2-ARCH), I do not get the above error anymore. I'm still using 1.1.9 at the moment. Instead I get the following error:<br />
<br />
<pre><br />
[ 1370.376263] ------------[ cut here ]------------<br />
[ 1370.376281] WARNING: CPU: 1 PID: 140 at drivers/ata/libata-eh.c:4143 ata_scsi_port_error_handler+0x731/0x770 [libata]()<br />
[ 1370.376356] Modules linked in: fuse ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6t_rpfilter snd_hda_codec_hdmi ip6table_raw joydev input_leds ip6_tables mousedev iptable_filter dell_led dell_laptop intel_rapl x86_pkg_temp_thermal intel_powerclamp led_class serio_raw atkbd kvm_intel dcdbas libps2 dell_wmi hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core sparse_keymap kvm nls_cp437 snd_hda_codec_realtek snd_hda_codec_generic vfat irqbypass fat crct10dif_pclmul crc32_pclmul aesni_intel snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core aes_x86_64 lrw gf128mul snd_soc_sst_ipc glue_helper snd_soc_sst_dsp ablk_helper cryptd snd_soc_core snd_compress snd_pcm_dmaengine<br />
[ 1370.376448] ac97_bus dw_dmac_core pcspkr snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_timer snd rtsx_pci_ms brcmutil i2c_i801 soundcore cfg80211 memstick uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common shpchp videodev mei_me btusb btrtl usbhid media mei idma64 processor_thermal_device intel_soc_dts_iosf iosf_mbi intel_lpss_pci fan thermal wmi i2c_hid hid battery hci_uart btbcm btqca btintel bluetooth i8042 rfkill serio crc16 pinctrl_sunrisepoint pinctrl_intel intel_lpss_acpi evdev acpi_als intel_lpss kfifo_buf industrialio mac_hid int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel tpm_tis acpi_pad tpm ac fjes processor sch_fq_codel coretemp msr ip_tables x_tables rtsx_pci_sdmmc mmc_core xhci_pci ahci xhci_hcd libahci<br />
[ 1370.376474] libata rtsx_pci scsi_mod usbcore usb_common crc32c_generic crc32c_intel btrfs xor raid6_pq i915 video button intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvme<br />
[ 1370.376480] CPU: 1 PID: 140 Comm: scsi_eh_2 Tainted: G W 4.4.1-2-ARCH #1<br />
[ 1370.376482] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 1370.376488] 0000000000000000 000000009b4c41e3 ffff880274f23d60 ffffffff812c7f39<br />
[ 1370.376494] 0000000000000000 ffff880274f23d98 ffffffff810765b2 ffff880274de0000<br />
[ 1370.376499] ffff880274f23e08 ffff880274de0000 ffff880274f23e60 ffff880274f23e80<br />
[ 1370.376501] Call Trace:<br />
[ 1370.376508] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 1370.376516] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 1370.376523] [<ffffffff810766fa>] warn_slowpath_null+0x1a/0x20<br />
[ 1370.376533] [<ffffffffa03944b1>] ata_scsi_port_error_handler+0x731/0x770 [libata]<br />
[ 1370.376546] [<ffffffffa038ed1d>] ? ata_scsi_cmd_error_handler+0x11d/0x160 [libata]<br />
[ 1370.376557] [<ffffffffa0394590>] ata_scsi_error+0xa0/0xe0 [libata]<br />
[ 1370.376568] [<ffffffffa0339246>] scsi_error_handler+0xb6/0x550 [scsi_mod]<br />
[ 1370.376575] [<ffffffff8158d93a>] ? __schedule+0x3aa/0xa70<br />
[ 1370.376586] [<ffffffffa0339190>] ? scsi_eh_get_sense+0x170/0x170 [scsi_mod]<br />
[ 1370.376591] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 1370.376597] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376602] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 1370.376608] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376611] ---[ end trace d11264a1acf26f7c ]---<br />
</pre><br />
<br />
I do not see any other errors. It's an ATA error, and I am still preloading "nvme" in my MODULES= mkinitcpio configuration at the moment.[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:03, 12 February 2016 (UTC)<br />
<br />
I can second that exact same error with 4.4.1-2-ARCH. After reading through http://en.community.dell.com/support-forums/laptop/f/3518/t/19586456 I'm starting to begin wondering if its a general hardware problem with the mainboard/powerboard. Does anyone with an XPS 9350 NOT have any of this issues with a working suspend? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 09:47, 12 February 2016 (UTC)<br />
<br />
== BIOS 1.2.3 ==<br />
<br />
With BIOS update 1.2.3 I get the following ACPI errors:<br />
<br />
[ 240.210541] INFO: task kworker/0:2:64 blocked for more than 120 seconds.<br />
[ 240.210552] Not tainted 4.4.1-1-ARCH #1<br />
[ 240.210555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br />
[ 240.210561] kworker/0:2 D ffff880275b13b58 0 64 2 0x00000000<br />
[ 240.210580] Workqueue: kacpid acpi_os_execute_deferred<br />
[ 240.210585] ffff880275b13b58 ffffffff8137774a ffffffff81810500 ffff880275b9ac40<br />
[ 240.210591] ffff880275b14000 ffff880271451700 ffff880275b9ac40 ffff880276966820<br />
[ 240.210597] ffff88007628b050 ffff880275b13b70 ffffffff8158e03c 7fffffffffffffff<br />
[ 240.210603] Call Trace:<br />
[ 240.210612] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210622] [<ffffffff8158e03c>] schedule+0x3c/0x90<br />
[ 240.210629] [<ffffffff81590ab3>] schedule_timeout+0x1b3/0x240<br />
[ 240.210633] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210642] [<ffffffff8136c0c6>] ? acpi_ns_search_one_scope+0x25/0x45<br />
[ 240.210649] [<ffffffff8136c235>] ? acpi_ns_search_and_enter+0x14f/0x1ab<br />
[ 240.210656] [<ffffffff8158fd34>] __down_timeout+0x74/0xd0<br />
[ 240.210662] [<ffffffff810bdb87>] ? down_timeout+0x37/0x60<br />
[ 240.210666] [<ffffffff810bdb9c>] down_timeout+0x4c/0x60<br />
[ 240.210673] [<ffffffff813478bf>] acpi_os_wait_semaphore+0x4c/0x67<br />
[ 240.210679] [<ffffffff81367243>] acpi_ex_system_wait_mutex+0x3c/0x4d<br />
[ 240.210686] [<ffffffff81359b28>] acpi_ds_begin_method_execution+0x13f/0x1d8<br />
[ 240.210693] [<ffffffff81359db4>] acpi_ds_call_control_method+0x54/0x17b<br />
[ 240.210698] [<ffffffff8136f3ab>] acpi_ps_parse_aml+0xaf/0x26f<br />
[ 240.210703] [<ffffffff8136fc11>] acpi_ps_execute_method+0x14b/0x186<br />
[ 240.210710] [<ffffffff8136a151>] acpi_ns_evaluate+0x1bb/0x247<br />
[ 240.210717] [<ffffffff8135d6f9>] acpi_ev_asynch_execute_gpe_method+0xa0/0x105<br />
[ 240.210723] [<ffffffff81346bce>] acpi_os_execute_deferred+0x14/0x20<br />
[ 240.210731] [<ffffffff8108e21b>] process_one_work+0x14b/0x440<br />
[ 240.210737] [<ffffffff8108e558>] worker_thread+0x48/0x4a0<br />
[ 240.210744] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210750] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210755] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 240.210761] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 240.210766] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 240.210771] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
<br />
This probably stems from a malfunctioning in the 1.2.3 Bios:<br />
<br />
[ 2.927769] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.927774] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927782] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927791] acpi PNP0C0B:00: Failed to change power state to D0<br />
[ 2.931194] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)<br />
[ 2.934430] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.934434] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934439] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934445] acpi PNP0C0B:00: Setting initial power state<br />
[ 2.936690] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)<br />
[ 2.937857] idma64 idma64.0: Found Intel integrated DMA 64-bit<br />
[ 2.951059] acpi PNP0C0B:00: Cannot transition from (unknown) to D3hot<br />
[ 2.951481] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)<br />
[ 2.951616] idma64 idma64.1: Found Intel integrated DMA 64-bit<br />
[ 2.957772] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.957776] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957781] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957787] acpi PNP0C0B:01: Failed to change power state to D0<br />
[ 2.964451] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.964455] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964460] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964498] acpi PNP0C0B:01: Setting initial power state<br />
[ 2.969276] mei_me 0000:00:16.0: enabling device (0000 -> 0002)<br />
[ 2.981024] acpi PNP0C0B:01: Cannot transition from (unknown) to D3hot<br />
[ 2.987767] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.987772] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987778] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987784] acpi PNP0C0B:02: Failed to change power state to D0<br />
[ 2.990676] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4<br />
[ 2.994441] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.994447] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994455] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994464] acpi PNP0C0B:02: Setting initial power state<br />
[ 3.001025] usb 1-3: new full-speed USB device number 3 using xhci_hcd<br />
[ 3.007691] acpi PNP0C0B:02: Cannot transition from (unknown) to D3hot<br />
[ 3.014415] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.014420] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014426] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014436] acpi PNP0C0B:03: Failed to change power state to D0<br />
[ 3.018400] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150930/utaddress-254)<br />
[ 3.018409] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver<br />
[ 3.021070] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.021074] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021080] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021086] acpi PNP0C0B:03: Setting initial power state<br />
<br />
<br />
Additionally I still get the intel gpu drm error that was present in 4.3:<br />
<br />
[ 8200.818355] WARNING: CPU: 0 PID: 663 at drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]()<br />
[ 8200.818357] WARN_ON(!wm_changed)<br />
[ 8200.818359] Modules linked in:<br />
[ 8200.818361] ...<br />
[ 8200.818462] intel_gtt<br />
[ 8200.818466] CPU: 0 PID: 663 Comm: Xorg Tainted: G W 4.4.1-1-ARCH #1<br />
[ 8200.818468] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.2.3 01/08/2016<br />
[ 8200.818470] 0000000000000000 00000000c1d62b7d ffff88007631f750 ffffffff812c7f39<br />
[ 8200.818474] ffff88007631f798 ffff88007631f788 ffffffff810765b2 ffff880276862000<br />
[ 8200.818477] ffff88007631f8bc ffff880276867000 0000000000000000 ffff88007631f828<br />
[ 8200.818480] Call Trace:<br />
[ 8200.818486] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 8200.818491] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 8200.818495] [<ffffffff8107664c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 8200.818505] [<ffffffffa00f1f37>] skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]<br />
[ 8200.818515] [<ffffffffa00f219a>] skl_update_wm+0x25a/0x750 [i915]<br />
[ 8200.818526] [<ffffffffa00f64de>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 8200.818539] [<ffffffffa015ed70>] haswell_crtc_enable+0x370/0x870 [i915]<br />
[ 8200.818553] [<ffffffffa015a992>] intel_atomic_commit+0x492/0x1430 [i915]<br />
[ 8200.818561] [<ffffffffa003339e>] ? drm_atomic_check_only+0x18e/0x590 [drm]<br />
[ 8200.818567] [<ffffffffa00337d7>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 8200.818572] [<ffffffffa00a3fb6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 8200.818580] [<ffffffffa0021ea2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 8200.818589] [<ffffffffa0026d92>] drm_mode_setcrtc+0x3d2/0x4f0 [drm]<br />
[ 8200.818595] [<ffffffffa00187b2>] drm_ioctl+0x152/0x540 [drm]<br />
[ 8200.818603] [<ffffffffa00269c0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 8200.818613] [<ffffffff811f0b68>] do_vfs_ioctl+0x298/0x480<br />
[ 8200.818620] [<ffffffff810824e1>] ? __set_task_blocked+0x41/0xa0<br />
[ 8200.818627] [<ffffffff811fabe7>] ? __fget+0x77/0xb0<br />
[ 8200.818630] [<ffffffff811f0dc9>] SyS_ioctl+0x79/0x90<br />
[ 8200.818634] [<ffffffff81084fde>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 8200.818637] [<ffffffff81591b2e>] entry_SYSCALL_64_fastpath+0x12/0x71<br />
[ 8200.818640] ---[ end trace 0e9f223c58ecdab8 ]---<br />
<br />
Everything, including the graphics works fine, however I am having trouble to rewake up the system when the laptop lid was closed.<br />
If just the display is turning off, it always comes back. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:45, 3 February 2016 (UTC)<br />
<br />
<br />
As of this morning, BIOS 1.2.3 and latest Linux kernel 4.4.2.1-ARCH, I have no more issue with suspend/wake up. By that, I mean that I do not see the libata crash anymore on suspend/wakeup. In fact, I do not see any crashes at all. It's looking all normal. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 01:01, 23 February 2016 (UTC)<br />
<br />
Nope, for me BIOS 1.2.3 with 4.4.5-1-ARCH is even worse. I can not poweroff, suspend or shutdown.--[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 10:05, 16 March 2016 (UTC)<br />
<br />
I'm using the same BIOS/Kernel as you. I do see the ACPI error (namespace failure you report, but nothing else). Could it be the graphic card power management, instead? I have absolutely nothing on my kernel line (all defaults). I do load intel-ucode, and my current microcode version 0x6a. I'm not sure which version of the graphics chip you have, but the failure in intel_pm (power management of the i915) may be mitigated by "disabling" power management: have you tried putting your graphic card on always "on" power (basically disable PM):<br />
<br />
echo on | sudo tee /sys/bus/pci/drivers/i915/0000:00:02.0/power/control <br />
<br />
Hopefully, that will help you. Note that it's bus number 0000:00:02.0 on my machine, but it maybe different on yours (so you may have to inspect the /sys/bus/pci/driver/i915 tree). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 10:48, 16 March 2016 (UTC)<br />
<br />
Thanks Bouh, unfortunately I already have the /power/control set to 'on'. As you, I have nothing on my kernel options but intel-ucode, no power manager, etc. Do you have any kernel modules blacklisted, such as dell_* ? I currently don't have, but maybe should? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:32, 16 March 2016 (UTC)<br />
<br />
No modules blacklisted, appart from the insignificant...:<br />
<br />
{{hc|cat /etc/modprobe.d/*|<br />
blacklist pcspkr<br />
blacklist psmouse<br />
}}<br />
<br />
I'm using thermald + my own power-management scripts. I'm thinking we may have different hardware. I moved on to kernel 4.5, still no issues to report (appart from the missing ACPI namespaces). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 04:31, 17 March 2016 (UTC)<br />
<br />
== PulseAudio modifying gain settings ==<br />
After talking to the pulseaudio mailing list, one user, gave me the workaround. This is his answer below:<br />
<br />
It's weird that a mic boost would affect headphone output. One<br />
explanation would be that the mic signal is fed directly to the<br />
headphones, but in that case increasing the boost should increase the<br />
noise, not decrease it. I guess it's a hardware or driver bug.<br />
<br />
To work around this, you can remove the [Element Headphone Mic Boost]<br />
sections from these two files:<br />
<br />
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf<br />
/usr/share/pulseuadio/alsa-mixer/paths/analog-input-headphone-mic.conf<br />
<br />
After that PulseAudio won't touch the boost volume any more.<br />
<br />
Whenever pulseaudio is updated, the package manager will remove your<br />
modifications, so you have to redo the modifications. That's still<br />
better than having to reset the mixer after every reboot...<br />
<br />
I guess this really needs to be provided as a patched {{Pkg|pulseaudio}} package. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:09, 25 January 2016 (UTC)<br />
<br />
== HiDPI ==<br />
This is not really mentioned in the 2016 model page, but I did have some very very small icons and fonts. What I had to do was create a file and fill it with something like this:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 338 190 # In millimeters<br />
EndSection<br />
}}<br />
<br />
This made my DPI settings similar to what they are in the Windows (240 DPI) that came with the XPS. [[User:Renatolond|Renatolond]]<br />
<br />
Out of curiosity, which desktop environment are you using? I am using a stock gnome-shell and it sets the scaling factor automatically. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:34, 19 February 2016 (UTC)<br />
<br />
I'm using Plasma via SDDM, but I think the problem begins before, because in CLI without any env the fonts are very small as well. --[[User:Renatolond|Renatolond]] ([[User talk:Renatolond|talk]]) 16:49, 19 February 2016 (UTC)<br />
<br />
In CLI, the setting mentioned above have no effect, don't they? Check this out if you want to change this: https://wiki.archlinux.org/index.php/Fonts#Console_fonts [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:16, 1 March 2016 (UTC)<br />
<br />
== Thunderbolt and XPS 15/13 ==<br />
I don't actually have a 13, but it seems the XPS 15 has somewhat similar hardware, at least as far as thunderbolt/USB-C is concerned. On my machine USB-C does not work without a PCI-e rescan, and the second you use the USB-C port the machine will no longer sleep with ACPI bugs on dmesg.<br />
<br />
Is it crazy to just create a XPS 15 (2016) and Precision 5510 (which afaict is the same machine with higher-end processor options) page which just redirects here?<br />
{{unsigned|04:18, 29 March 2016|BlueMatt}}<br />
<br />
Hi, I got exactly the same problem on my XPS 13.<br />
If I boot with USB-C adapter connected it is detectecd, if I not connects it during the boot process I need to do a rescan but if I disconnect it for the second time I got the same issue your are talking about.<br />
What is your USB-C device type your are trying to make it work? is it the Dell Multi Adatper (USB, VGA, HDMI, Ethernet)? For this one I am only able to make the Ethernet working, the HDMI is detected, my external monitor correctly detected but no signal is received on this side...<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 14:56, 29 March 2016 (UTC)<br />
<br />
For reference, here are my related dmesg:<br />
{{hc|dmesg|2=<br />
<br />
[ 997.082343] Call Trace:<br />
[ 997.082355] [<ffffffff812d8b11>] dump_stack+0x63/0x82<br />
[ 997.082360] [<ffffffff81076de2>] warn_slowpath_common+0x82/0xc0<br />
[ 997.082364] [<ffffffff81076e7c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 997.082377] [<ffffffffa00f94f7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
[ 997.082390] [<ffffffffa00f968e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
[ 997.082407] [<ffffffffa018413f>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
[ 997.082420] [<ffffffffa00fcd9e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 997.082439] [<ffffffffa01679a1>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
[ 997.082457] [<ffffffffa01632b7>] intel_atomic_commit+0x737/0x1870 [i915]<br />
[ 997.082466] [<ffffffffa0032581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
[ 997.082473] [<ffffffffa0032a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 997.082478] [<ffffffffa00a28c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 997.082489] [<ffffffffa00211b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 997.082498] [<ffffffffa00262c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
[ 997.082506] [<ffffffffa0017892>] drm_ioctl+0x152/0x540 [drm]<br />
[ 997.082514] [<ffffffffa0025ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 997.082518] [<ffffffff811eac5c>] ? __vfs_write+0xcc/0x100<br />
[ 997.082522] [<ffffffff811fdbb1>] do_vfs_ioctl+0xa1/0x5b0<br />
[ 997.082526] [<ffffffff81082d81>] ? __set_task_blocked+0x41/0xa0<br />
[ 997.082530] [<ffffffff81207fc7>] ? __fget+0x77/0xb0<br />
[ 997.082534] [<ffffffff811fe139>] SyS_ioctl+0x79/0x90<br />
[ 997.082537] [<ffffffff810858ce>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 997.082541] [<ffffffff815ab32e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
[ 997.082544] ---[ end trace 5285a5658ce7e2d8 ]---<br />
<br />
}}<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 15:37, 29 March 2016 (UTC)<br />
<br />
You may want to read http://ubuntuforums.org/showthread.php?t=2301071. Lots of people talking about USB-C and Thunderbolt 3. Seems display adapters work for most people with some effort, not sure about Thunderbolt 3 (which puts the USB-C port in PCIe mode), but USB-C seems pretty consistently broken in the same ways as above (I've tried it with a male A <-> C adapter and several devices, as well as my Nexus 5X which is native C). [[User:BlueMatt|BlueMatt]] ([[User talk:BlueMatt|talk]]) 18:46, 29 March 2016 (UTC)<br />
:Thanks BlueMatt, I read it carefuly, and I saw the PCI rescan workaround, for me it is only working the first time then I got an issue where it will never been detected anymore and I need a system restart.<br />
EDIT: Regarding VGA, everything is working well when connected, when it is disconnected if the laptop is put in sleep mode it hangs, no way to wake it up, power button led remains lighted but nothing on the screen.[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 10:14, 30 March 2016 (UTC) <br />
:For HDMI monitor is detected but no signal is sent so the monitor stays black, for Ethernet working if I boot the laptop with the adapter connected or if I do a rescan when I connect the adapter after the boot, but only one time...<br />
Perhaps a good idea to add a section into the Wiki page speaking about USB-C issue/workaround? [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 21:03, 29 March 2016 (UTC)<br />
<br />
:@BlueMatt: Regarding your question of separate articles: Exactly. It is great how this article develops, even better if contributions help users of similar/related models. Please see the extra section I created earlier as a ''suggestion'' ([[Dell XPS 13 (2016)#Diverting models]]) to account for any stub model differences that may be. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 10:10, 4 April 2016 (UTC)<br />
<br />
:@Belette: If you look at the Bias 1.2.3 section in this discussion, the slowpath bug is caused by a Linux kernel bug that in the meantime was fixed but reopened again ([https://bugs.freedesktop.org/show_bug.cgi?id=89055]). Hopefully it will be stable in 4.5.<br />
:@BlueMatt: I love that the Arch Wiki is so detailed about special models - hence I think it really depends on how similar the XPS 12, 13 and 15 models are. I have not seen any reports on how the XPS 12 works at all, only 13 and 15. Hence, I'm positive with regard to keeping separate articles until we know how similar they really are. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 07:45, 5 April 2016 (UTC)<br />
<br />
::You are welcome to add the info you have to [[Dell_XPS_13_%282016%29#XPS_12]] for now and to create an XPS12 article stub on your userpage. Open a question on the BBS, if you look for [https://wiki.archlinux.org/index.php?title=Dell_XPS_12_%282016%29&oldid=429570 info]. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:51, 5 April 2016 (UTC)<br />
<br />
== Touchpad multi-gesture ==<br />
I don't see anything specifically related to multi-gesture (zoom, pinch...) on the touchpad in the Dell XPS 13 page.<br />
<br />
I have installed xf86-input-libinput as suggested and both my touchpad and touch screen are working perfecty but I am missing multigesture..<br />
Using this tips: https://bbs.archlinux.org/viewtopic.php?pid=1617669#p1617669 [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 08:28, 7 April 2016 (UTC)<br />
<br />
== <s>Now with official Linux support</s> ==<br />
<br />
I got an email informing me that the XPS 13 2016 model is now supported by Dell, as the 4.4 kernel with the required Broadcom drivers is available in Ubuntu 16.04 LTS. However I can't find information about this on the dell site, and [http://www.dell.com/us/business/p/xps-13-linux/pd] mentioned "This product is currently unavailable". -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:14, 16 May 2016 (UTC)<br />
<br />
:[https://wiki.archlinux.org/index.php?title=Dell_XPS_13_%282016%29&diff=435552&oldid=429579], thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:43, 12 June 2016 (UTC)<br />
<br />
== EFISTUB booting ==<br />
<br />
I tried to get this laptop to boot the Linux kernel directly, via [[EFISTUB]], but none of the boot entries I created with <code>efibootmgr</code> worked. The exact same command did work, however, from the UEFI Shell v2, as well as from [[systemd-boot]]. So I suspect that this system’s UEFI implementation doesn’t properly support passing parameters to a boot entry. For booting, you either need an UEFI boot loader (like [[systemd-boot]]), or you need to link the command line into the image, as in [https://bentley.link/secureboot/#combine-the-kernel-initramfs-and-boot-options this article]. —[[User:LucasWerkmeister|LucasWerkmeister]] ([[User talk:LucasWerkmeister|talk]]) 11:16, 12 June 2016 (UTC)<br />
<br />
== Screen stuttering ==<br />
<br />
I am experiencing quite a lot of screen stuttering. Though I have chrome running in the background, half of my memory is still free and therefore should not cause problems even for an integrated GPU. The stuttering occurs independent from the application I use: e.g. my graphical terminal (gnome-terminal) is affected as well. Temperatures seem to be fine at about 50 to 60 °C and I load the latest intel microcode through my boot loader (systemd-boot). My X11 config file looks like this:<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|2=<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "sna" # UXA is an alternative<br />
Option "TearFree" "true" # SNA only, not needed for DRI3<br />
EndSection<br />
}}<br />
Googling the issue did not return viable results since most of them concern tearing, which I do not encounter, or recommend setting the {{ic|TearFree}} option to {{ic|true}} which I hava already done. I am using {{ic|mesa 12.0.1-2}}, {{ic|xf86-video-intel 1:2.99.917+676+g26f8ab5-1}}, {{ic|linux 4.6.4-1}} and {{ic|linux-firmware 20160516.80d463b-1}} with the above {{ic|xorg.conf.d/20-intel.conf}} config file. I assume it to be related to at least one of the packages. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 14:46, 28 July 2016 (UTC)<br />
<br />
== Kaby Lake Model ==<br />
<br />
Due out 4th October with intel's latest. A developer edition is coming too, bit later maybe 10th I think. <br />
Late 2016 model... [[Dell XPS 13 (4th Gen)]]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9350)&diff=451338Talk:Dell XPS 13 (9350)2016-09-21T05:19:19Z<p>Alexjj: New model incoming</p>
<hr />
<div>Added a section for kernel specific configurations.<br />
<br />
== <s> SATA controller </s> ==<br />
Potentially useful blog post?: https://samnicholls.net/2016/01/14/how-to-switch-sata-raid-to-ahci-windows-10-xps-13/ (disclaimer: it's mine) on getting around the SATA controller issue for those who need to dual boot, works on my 9350 but ymmv. [[User:Samstudio8|Samstudio8]] ([[User talk:Samstudio8|talk]]) 04:11, 14 January 2016 (UTC)<br />
<br />
: I described your suggested solutions in the main article. Feel free to correct any mistakes. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 10:10, 15 July 2016 (UTC)<br />
<br />
== Release of 4.4 in testing ==<br />
<br />
I made a slew of edits and some clean up related to the release of 4.4 in testing. Let me know if you see any issues. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:24, 20 January 2016 (UTC)<br />
<br />
== BIOS update 1.1.9 ==<br />
<br />
Since the BIOS update, I get some errors, with stack dump during suspend/resume.<br />
<br />
[ 0.448742] ------------[ cut here ]------------<br />
[ 0.448744] WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:225 note_page+0x5e1/0x780()<br />
[ 0.448745] x86/mm: Found insecure W+X mapping at address ffff880000000000/0xffff880000000000<br />
[ 0.448746] Modules linked in:<br />
[ 0.448748] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-3-ARCH #1<br />
[ 0.448749] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 0.448750] 0000000000000000 00000000271d54da ffff8802771afd48 ffffffff812c8a99<br />
[ 0.448752] ffff8802771afd90 ffff8802771afd80 ffffffff810771c2 ffff8802771afe90<br />
[ 0.448754] 8000000000000163 0000000000000004 0000000000000000 0000000000000000<br />
[ 0.448755] Call Trace:<br />
[ 0.448758] [<ffffffff812c8a99>] dump_stack+0x4b/0x72<br />
[ 0.448760] [<ffffffff810771c2>] warn_slowpath_common+0x82/0xc0<br />
[ 0.448762] [<ffffffff8107725c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 0.448763] [<ffffffff8106c4c1>] note_page+0x5e1/0x780<br />
[ 0.448765] [<ffffffff8106c967>] ptdump_walk_pgd_level_core+0x307/0x450<br />
[ 0.448766] [<ffffffff8106cae7>] ptdump_walk_pgd_level_checkwx+0x17/0x20<br />
[ 0.448768] [<ffffffff8106278f>] mark_rodata_ro+0xef/0x100<br />
[ 0.448770] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448771] [<ffffffff8158636d>] kernel_init+0x1d/0xe0<br />
[ 0.448773] [<ffffffff8159290f>] ret_from_fork+0x3f/0x70<br />
[ 0.448774] [<ffffffff81586350>] ? rest_init+0x90/0x90<br />
[ 0.448775] ---[ end trace b1a5026ad8272458 ]---<br />
<br />
[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 07:48, 20 January 2016 (UTC)<br />
<br />
Since latest kernel update (4.4.1-2-ARCH), I do not get the above error anymore. I'm still using 1.1.9 at the moment. Instead I get the following error:<br />
<br />
<pre><br />
[ 1370.376263] ------------[ cut here ]------------<br />
[ 1370.376281] WARNING: CPU: 1 PID: 140 at drivers/ata/libata-eh.c:4143 ata_scsi_port_error_handler+0x731/0x770 [libata]()<br />
[ 1370.376356] Modules linked in: fuse ipt_REJECT nf_reject_ipv4 ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6t_rpfilter snd_hda_codec_hdmi ip6table_raw joydev input_leds ip6_tables mousedev iptable_filter dell_led dell_laptop intel_rapl x86_pkg_temp_thermal intel_powerclamp led_class serio_raw atkbd kvm_intel dcdbas libps2 dell_wmi hid_multitouch nls_iso8859_1 i2c_designware_platform i2c_designware_core sparse_keymap kvm nls_cp437 snd_hda_codec_realtek snd_hda_codec_generic vfat irqbypass fat crct10dif_pclmul crc32_pclmul aesni_intel snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core aes_x86_64 lrw gf128mul snd_soc_sst_ipc glue_helper snd_soc_sst_dsp ablk_helper cryptd snd_soc_core snd_compress snd_pcm_dmaengine<br />
[ 1370.376448] ac97_bus dw_dmac_core pcspkr snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_timer snd rtsx_pci_ms brcmutil i2c_i801 soundcore cfg80211 memstick uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common shpchp videodev mei_me btusb btrtl usbhid media mei idma64 processor_thermal_device intel_soc_dts_iosf iosf_mbi intel_lpss_pci fan thermal wmi i2c_hid hid battery hci_uart btbcm btqca btintel bluetooth i8042 rfkill serio crc16 pinctrl_sunrisepoint pinctrl_intel intel_lpss_acpi evdev acpi_als intel_lpss kfifo_buf industrialio mac_hid int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel tpm_tis acpi_pad tpm ac fjes processor sch_fq_codel coretemp msr ip_tables x_tables rtsx_pci_sdmmc mmc_core xhci_pci ahci xhci_hcd libahci<br />
[ 1370.376474] libata rtsx_pci scsi_mod usbcore usb_common crc32c_generic crc32c_intel btrfs xor raid6_pq i915 video button intel_gtt i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvme<br />
[ 1370.376480] CPU: 1 PID: 140 Comm: scsi_eh_2 Tainted: G W 4.4.1-2-ARCH #1<br />
[ 1370.376482] Hardware name: Dell Inc. XPS 13 9350/0V33HM, BIOS 1.1.9 12/18/2015<br />
[ 1370.376488] 0000000000000000 000000009b4c41e3 ffff880274f23d60 ffffffff812c7f39<br />
[ 1370.376494] 0000000000000000 ffff880274f23d98 ffffffff810765b2 ffff880274de0000<br />
[ 1370.376499] ffff880274f23e08 ffff880274de0000 ffff880274f23e60 ffff880274f23e80<br />
[ 1370.376501] Call Trace:<br />
[ 1370.376508] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 1370.376516] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 1370.376523] [<ffffffff810766fa>] warn_slowpath_null+0x1a/0x20<br />
[ 1370.376533] [<ffffffffa03944b1>] ata_scsi_port_error_handler+0x731/0x770 [libata]<br />
[ 1370.376546] [<ffffffffa038ed1d>] ? ata_scsi_cmd_error_handler+0x11d/0x160 [libata]<br />
[ 1370.376557] [<ffffffffa0394590>] ata_scsi_error+0xa0/0xe0 [libata]<br />
[ 1370.376568] [<ffffffffa0339246>] scsi_error_handler+0xb6/0x550 [scsi_mod]<br />
[ 1370.376575] [<ffffffff8158d93a>] ? __schedule+0x3aa/0xa70<br />
[ 1370.376586] [<ffffffffa0339190>] ? scsi_eh_get_sense+0x170/0x170 [scsi_mod]<br />
[ 1370.376591] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 1370.376597] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376602] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 1370.376608] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 1370.376611] ---[ end trace d11264a1acf26f7c ]---<br />
</pre><br />
<br />
I do not see any other errors. It's an ATA error, and I am still preloading "nvme" in my MODULES= mkinitcpio configuration at the moment.[[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:03, 12 February 2016 (UTC)<br />
<br />
I can second that exact same error with 4.4.1-2-ARCH. After reading through http://en.community.dell.com/support-forums/laptop/f/3518/t/19586456 I'm starting to begin wondering if its a general hardware problem with the mainboard/powerboard. Does anyone with an XPS 9350 NOT have any of this issues with a working suspend? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 09:47, 12 February 2016 (UTC)<br />
<br />
== BIOS 1.2.3 ==<br />
<br />
With BIOS update 1.2.3 I get the following ACPI errors:<br />
<br />
[ 240.210541] INFO: task kworker/0:2:64 blocked for more than 120 seconds.<br />
[ 240.210552] Not tainted 4.4.1-1-ARCH #1<br />
[ 240.210555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.<br />
[ 240.210561] kworker/0:2 D ffff880275b13b58 0 64 2 0x00000000<br />
[ 240.210580] Workqueue: kacpid acpi_os_execute_deferred<br />
[ 240.210585] ffff880275b13b58 ffffffff8137774a ffffffff81810500 ffff880275b9ac40<br />
[ 240.210591] ffff880275b14000 ffff880271451700 ffff880275b9ac40 ffff880276966820<br />
[ 240.210597] ffff88007628b050 ffff880275b13b70 ffffffff8158e03c 7fffffffffffffff<br />
[ 240.210603] Call Trace:<br />
[ 240.210612] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210622] [<ffffffff8158e03c>] schedule+0x3c/0x90<br />
[ 240.210629] [<ffffffff81590ab3>] schedule_timeout+0x1b3/0x240<br />
[ 240.210633] [<ffffffff8137774a>] ? acpi_ut_repair_name+0x2a/0x74<br />
[ 240.210642] [<ffffffff8136c0c6>] ? acpi_ns_search_one_scope+0x25/0x45<br />
[ 240.210649] [<ffffffff8136c235>] ? acpi_ns_search_and_enter+0x14f/0x1ab<br />
[ 240.210656] [<ffffffff8158fd34>] __down_timeout+0x74/0xd0<br />
[ 240.210662] [<ffffffff810bdb87>] ? down_timeout+0x37/0x60<br />
[ 240.210666] [<ffffffff810bdb9c>] down_timeout+0x4c/0x60<br />
[ 240.210673] [<ffffffff813478bf>] acpi_os_wait_semaphore+0x4c/0x67<br />
[ 240.210679] [<ffffffff81367243>] acpi_ex_system_wait_mutex+0x3c/0x4d<br />
[ 240.210686] [<ffffffff81359b28>] acpi_ds_begin_method_execution+0x13f/0x1d8<br />
[ 240.210693] [<ffffffff81359db4>] acpi_ds_call_control_method+0x54/0x17b<br />
[ 240.210698] [<ffffffff8136f3ab>] acpi_ps_parse_aml+0xaf/0x26f<br />
[ 240.210703] [<ffffffff8136fc11>] acpi_ps_execute_method+0x14b/0x186<br />
[ 240.210710] [<ffffffff8136a151>] acpi_ns_evaluate+0x1bb/0x247<br />
[ 240.210717] [<ffffffff8135d6f9>] acpi_ev_asynch_execute_gpe_method+0xa0/0x105<br />
[ 240.210723] [<ffffffff81346bce>] acpi_os_execute_deferred+0x14/0x20<br />
[ 240.210731] [<ffffffff8108e21b>] process_one_work+0x14b/0x440<br />
[ 240.210737] [<ffffffff8108e558>] worker_thread+0x48/0x4a0<br />
[ 240.210744] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210750] [<ffffffff8108e510>] ? process_one_work+0x440/0x440<br />
[ 240.210755] [<ffffffff81093ff8>] kthread+0xd8/0xf0<br />
[ 240.210761] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
[ 240.210766] [<ffffffff81591e8f>] ret_from_fork+0x3f/0x70<br />
[ 240.210771] [<ffffffff81093f20>] ? kthread_worker_fn+0x170/0x170<br />
<br />
This probably stems from a malfunctioning in the 1.2.3 Bios:<br />
<br />
[ 2.927769] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.927774] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927782] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.927791] acpi PNP0C0B:00: Failed to change power state to D0<br />
[ 2.931194] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)<br />
[ 2.934430] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.934434] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934439] ACPI Error: Method parse/execution failed [\_TZ.FN00._ON] (Node ffff8802780deed8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.934445] acpi PNP0C0B:00: Setting initial power state<br />
[ 2.936690] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)<br />
[ 2.937857] idma64 idma64.0: Found Intel integrated DMA 64-bit<br />
[ 2.951059] acpi PNP0C0B:00: Cannot transition from (unknown) to D3hot<br />
[ 2.951481] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)<br />
[ 2.951616] idma64 idma64.1: Found Intel integrated DMA 64-bit<br />
[ 2.957772] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.957776] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957781] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.957787] acpi PNP0C0B:01: Failed to change power state to D0<br />
[ 2.964451] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.964455] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964460] ACPI Error: Method parse/execution failed [\_TZ.FN01._ON] (Node ffff88027810f028), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.964498] acpi PNP0C0B:01: Setting initial power state<br />
[ 2.969276] mei_me 0000:00:16.0: enabling device (0000 -> 0002)<br />
[ 2.981024] acpi PNP0C0B:01: Cannot transition from (unknown) to D3hot<br />
[ 2.987767] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.987772] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987778] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.987784] acpi PNP0C0B:02: Failed to change power state to D0<br />
[ 2.990676] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4<br />
[ 2.994441] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 2.994447] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994455] ACPI Error: Method parse/execution failed [\_TZ.FN02._ON] (Node ffff88027810f168), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 2.994464] acpi PNP0C0B:02: Setting initial power state<br />
[ 3.001025] usb 1-3: new full-speed USB device number 3 using xhci_hcd<br />
[ 3.007691] acpi PNP0C0B:02: Cannot transition from (unknown) to D3hot<br />
[ 3.014415] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.014420] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014426] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.014436] acpi PNP0C0B:03: Failed to change power state to D0<br />
[ 3.018400] ACPI Warning: SystemIO range 0x000000000000F040-0x000000000000F05F conflicts with OpRegion 0x000000000000F040-0x000000000000F04F (\_SB_.PCI0.SBUS.SMBI) (20150930/utaddress-254)<br />
[ 3.018409] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver<br />
[ 3.021070] ACPI Error: [\_SB_.PCI0.LPCB.H_EC.ECAV] Namespace lookup failure, AE_NOT_FOUND (20150930/psargs-359)<br />
[ 3.021074] ACPI Error: Method parse/execution failed [\_TZ.FNCL] (Node ffff88027810f4d8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021080] ACPI Error: Method parse/execution failed [\_TZ.FN03._ON] (Node ffff88027810f2a8), AE_NOT_FOUND (20150930/psparse-542)<br />
[ 3.021086] acpi PNP0C0B:03: Setting initial power state<br />
<br />
<br />
Additionally I still get the intel gpu drm error that was present in 4.3:<br />
<br />
[ 8200.818355] WARNING: CPU: 0 PID: 663 at drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]()<br />
[ 8200.818357] WARN_ON(!wm_changed)<br />
[ 8200.818359] Modules linked in:<br />
[ 8200.818361] ...<br />
[ 8200.818462] intel_gtt<br />
[ 8200.818466] CPU: 0 PID: 663 Comm: Xorg Tainted: G W 4.4.1-1-ARCH #1<br />
[ 8200.818468] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.2.3 01/08/2016<br />
[ 8200.818470] 0000000000000000 00000000c1d62b7d ffff88007631f750 ffffffff812c7f39<br />
[ 8200.818474] ffff88007631f798 ffff88007631f788 ffffffff810765b2 ffff880276862000<br />
[ 8200.818477] ffff88007631f8bc ffff880276867000 0000000000000000 ffff88007631f828<br />
[ 8200.818480] Call Trace:<br />
[ 8200.818486] [<ffffffff812c7f39>] dump_stack+0x4b/0x72<br />
[ 8200.818491] [<ffffffff810765b2>] warn_slowpath_common+0x82/0xc0<br />
[ 8200.818495] [<ffffffff8107664c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 8200.818505] [<ffffffffa00f1f37>] skl_update_other_pipe_wm+0x1e7/0x1f0 [i915]<br />
[ 8200.818515] [<ffffffffa00f219a>] skl_update_wm+0x25a/0x750 [i915]<br />
[ 8200.818526] [<ffffffffa00f64de>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 8200.818539] [<ffffffffa015ed70>] haswell_crtc_enable+0x370/0x870 [i915]<br />
[ 8200.818553] [<ffffffffa015a992>] intel_atomic_commit+0x492/0x1430 [i915]<br />
[ 8200.818561] [<ffffffffa003339e>] ? drm_atomic_check_only+0x18e/0x590 [drm]<br />
[ 8200.818567] [<ffffffffa00337d7>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 8200.818572] [<ffffffffa00a3fb6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 8200.818580] [<ffffffffa0021ea2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 8200.818589] [<ffffffffa0026d92>] drm_mode_setcrtc+0x3d2/0x4f0 [drm]<br />
[ 8200.818595] [<ffffffffa00187b2>] drm_ioctl+0x152/0x540 [drm]<br />
[ 8200.818603] [<ffffffffa00269c0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 8200.818613] [<ffffffff811f0b68>] do_vfs_ioctl+0x298/0x480<br />
[ 8200.818620] [<ffffffff810824e1>] ? __set_task_blocked+0x41/0xa0<br />
[ 8200.818627] [<ffffffff811fabe7>] ? __fget+0x77/0xb0<br />
[ 8200.818630] [<ffffffff811f0dc9>] SyS_ioctl+0x79/0x90<br />
[ 8200.818634] [<ffffffff81084fde>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 8200.818637] [<ffffffff81591b2e>] entry_SYSCALL_64_fastpath+0x12/0x71<br />
[ 8200.818640] ---[ end trace 0e9f223c58ecdab8 ]---<br />
<br />
Everything, including the graphics works fine, however I am having trouble to rewake up the system when the laptop lid was closed.<br />
If just the display is turning off, it always comes back. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:45, 3 February 2016 (UTC)<br />
<br />
<br />
As of this morning, BIOS 1.2.3 and latest Linux kernel 4.4.2.1-ARCH, I have no more issue with suspend/wake up. By that, I mean that I do not see the libata crash anymore on suspend/wakeup. In fact, I do not see any crashes at all. It's looking all normal. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 01:01, 23 February 2016 (UTC)<br />
<br />
Nope, for me BIOS 1.2.3 with 4.4.5-1-ARCH is even worse. I can not poweroff, suspend or shutdown.--[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 10:05, 16 March 2016 (UTC)<br />
<br />
I'm using the same BIOS/Kernel as you. I do see the ACPI error (namespace failure you report, but nothing else). Could it be the graphic card power management, instead? I have absolutely nothing on my kernel line (all defaults). I do load intel-ucode, and my current microcode version 0x6a. I'm not sure which version of the graphics chip you have, but the failure in intel_pm (power management of the i915) may be mitigated by "disabling" power management: have you tried putting your graphic card on always "on" power (basically disable PM):<br />
<br />
echo on | sudo tee /sys/bus/pci/drivers/i915/0000:00:02.0/power/control <br />
<br />
Hopefully, that will help you. Note that it's bus number 0000:00:02.0 on my machine, but it maybe different on yours (so you may have to inspect the /sys/bus/pci/driver/i915 tree). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 10:48, 16 March 2016 (UTC)<br />
<br />
Thanks Bouh, unfortunately I already have the /power/control set to 'on'. As you, I have nothing on my kernel options but intel-ucode, no power manager, etc. Do you have any kernel modules blacklisted, such as dell_* ? I currently don't have, but maybe should? --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 12:32, 16 March 2016 (UTC)<br />
<br />
No modules blacklisted, appart from the insignificant...:<br />
<br />
{{hc|cat /etc/modprobe.d/*|<br />
blacklist pcspkr<br />
blacklist psmouse<br />
}}<br />
<br />
I'm using thermald + my own power-management scripts. I'm thinking we may have different hardware. I moved on to kernel 4.5, still no issues to report (appart from the missing ACPI namespaces). [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 04:31, 17 March 2016 (UTC)<br />
<br />
== PulseAudio modifying gain settings ==<br />
After talking to the pulseaudio mailing list, one user, gave me the workaround. This is his answer below:<br />
<br />
It's weird that a mic boost would affect headphone output. One<br />
explanation would be that the mic signal is fed directly to the<br />
headphones, but in that case increasing the boost should increase the<br />
noise, not decrease it. I guess it's a hardware or driver bug.<br />
<br />
To work around this, you can remove the [Element Headphone Mic Boost]<br />
sections from these two files:<br />
<br />
/usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf<br />
/usr/share/pulseuadio/alsa-mixer/paths/analog-input-headphone-mic.conf<br />
<br />
After that PulseAudio won't touch the boost volume any more.<br />
<br />
Whenever pulseaudio is updated, the package manager will remove your<br />
modifications, so you have to redo the modifications. That's still<br />
better than having to reset the mixer after every reboot...<br />
<br />
I guess this really needs to be provided as a patched {{Pkg|pulseaudio}} package. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 06:09, 25 January 2016 (UTC)<br />
<br />
== HiDPI ==<br />
This is not really mentioned in the 2016 model page, but I did have some very very small icons and fonts. What I had to do was create a file and fill it with something like this:<br />
<br />
{{hc|/etc/X11/xorg.conf.d/90-monitor.conf|2=<br />
Section "Monitor"<br />
Identifier "<default monitor>"<br />
DisplaySize 338 190 # In millimeters<br />
EndSection<br />
}}<br />
<br />
This made my DPI settings similar to what they are in the Windows (240 DPI) that came with the XPS. [[User:Renatolond|Renatolond]]<br />
<br />
Out of curiosity, which desktop environment are you using? I am using a stock gnome-shell and it sets the scaling factor automatically. [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:34, 19 February 2016 (UTC)<br />
<br />
I'm using Plasma via SDDM, but I think the problem begins before, because in CLI without any env the fonts are very small as well. --[[User:Renatolond|Renatolond]] ([[User talk:Renatolond|talk]]) 16:49, 19 February 2016 (UTC)<br />
<br />
In CLI, the setting mentioned above have no effect, don't they? Check this out if you want to change this: https://wiki.archlinux.org/index.php/Fonts#Console_fonts [[User:Bouh|Bouh]] ([[User talk:Bouh|talk]]) 15:16, 1 March 2016 (UTC)<br />
<br />
== Thunderbolt and XPS 15/13 ==<br />
I don't actually have a 13, but it seems the XPS 15 has somewhat similar hardware, at least as far as thunderbolt/USB-C is concerned. On my machine USB-C does not work without a PCI-e rescan, and the second you use the USB-C port the machine will no longer sleep with ACPI bugs on dmesg.<br />
<br />
Is it crazy to just create a XPS 15 (2016) and Precision 5510 (which afaict is the same machine with higher-end processor options) page which just redirects here?<br />
{{unsigned|04:18, 29 March 2016|BlueMatt}}<br />
<br />
Hi, I got exactly the same problem on my XPS 13.<br />
If I boot with USB-C adapter connected it is detectecd, if I not connects it during the boot process I need to do a rescan but if I disconnect it for the second time I got the same issue your are talking about.<br />
What is your USB-C device type your are trying to make it work? is it the Dell Multi Adatper (USB, VGA, HDMI, Ethernet)? For this one I am only able to make the Ethernet working, the HDMI is detected, my external monitor correctly detected but no signal is received on this side...<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 14:56, 29 March 2016 (UTC)<br />
<br />
For reference, here are my related dmesg:<br />
{{hc|dmesg|2=<br />
<br />
[ 997.082343] Call Trace:<br />
[ 997.082355] [<ffffffff812d8b11>] dump_stack+0x63/0x82<br />
[ 997.082360] [<ffffffff81076de2>] warn_slowpath_common+0x82/0xc0<br />
[ 997.082364] [<ffffffff81076e7c>] warn_slowpath_fmt+0x5c/0x80<br />
[ 997.082377] [<ffffffffa00f94f7>] skl_update_other_pipe_wm+0x177/0x180 [i915]<br />
[ 997.082390] [<ffffffffa00f968e>] skl_update_wm+0x18e/0x5f0 [i915]<br />
[ 997.082407] [<ffffffffa018413f>] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915]<br />
[ 997.082420] [<ffffffffa00fcd9e>] intel_update_watermarks+0x1e/0x30 [i915]<br />
[ 997.082439] [<ffffffffa01679a1>] haswell_crtc_enable+0x321/0x8c0 [i915]<br />
[ 997.082457] [<ffffffffa01632b7>] intel_atomic_commit+0x737/0x1870 [i915]<br />
[ 997.082466] [<ffffffffa0032581>] ? drm_atomic_check_only+0x181/0x600 [drm]<br />
[ 997.082473] [<ffffffffa0032a37>] drm_atomic_commit+0x37/0x60 [drm]<br />
[ 997.082478] [<ffffffffa00a28c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]<br />
[ 997.082489] [<ffffffffa00211b2>] drm_mode_set_config_internal+0x62/0x100 [drm]<br />
[ 997.082498] [<ffffffffa00262c0>] drm_mode_setcrtc+0x3e0/0x500 [drm]<br />
[ 997.082506] [<ffffffffa0017892>] drm_ioctl+0x152/0x540 [drm]<br />
[ 997.082514] [<ffffffffa0025ee0>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]<br />
[ 997.082518] [<ffffffff811eac5c>] ? __vfs_write+0xcc/0x100<br />
[ 997.082522] [<ffffffff811fdbb1>] do_vfs_ioctl+0xa1/0x5b0<br />
[ 997.082526] [<ffffffff81082d81>] ? __set_task_blocked+0x41/0xa0<br />
[ 997.082530] [<ffffffff81207fc7>] ? __fget+0x77/0xb0<br />
[ 997.082534] [<ffffffff811fe139>] SyS_ioctl+0x79/0x90<br />
[ 997.082537] [<ffffffff810858ce>] ? SyS_rt_sigprocmask+0x8e/0xc0<br />
[ 997.082541] [<ffffffff815ab32e>] entry_SYSCALL_64_fastpath+0x12/0x6d<br />
[ 997.082544] ---[ end trace 5285a5658ce7e2d8 ]---<br />
<br />
}}<br />
[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 15:37, 29 March 2016 (UTC)<br />
<br />
You may want to read http://ubuntuforums.org/showthread.php?t=2301071. Lots of people talking about USB-C and Thunderbolt 3. Seems display adapters work for most people with some effort, not sure about Thunderbolt 3 (which puts the USB-C port in PCIe mode), but USB-C seems pretty consistently broken in the same ways as above (I've tried it with a male A <-> C adapter and several devices, as well as my Nexus 5X which is native C). [[User:BlueMatt|BlueMatt]] ([[User talk:BlueMatt|talk]]) 18:46, 29 March 2016 (UTC)<br />
:Thanks BlueMatt, I read it carefuly, and I saw the PCI rescan workaround, for me it is only working the first time then I got an issue where it will never been detected anymore and I need a system restart.<br />
EDIT: Regarding VGA, everything is working well when connected, when it is disconnected if the laptop is put in sleep mode it hangs, no way to wake it up, power button led remains lighted but nothing on the screen.[[User:Belette|Belette]] ([[User talk:Belette|talk]]) 10:14, 30 March 2016 (UTC) <br />
:For HDMI monitor is detected but no signal is sent so the monitor stays black, for Ethernet working if I boot the laptop with the adapter connected or if I do a rescan when I connect the adapter after the boot, but only one time...<br />
Perhaps a good idea to add a section into the Wiki page speaking about USB-C issue/workaround? [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 21:03, 29 March 2016 (UTC)<br />
<br />
:@BlueMatt: Regarding your question of separate articles: Exactly. It is great how this article develops, even better if contributions help users of similar/related models. Please see the extra section I created earlier as a ''suggestion'' ([[Dell XPS 13 (2016)#Diverting models]]) to account for any stub model differences that may be. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 10:10, 4 April 2016 (UTC)<br />
<br />
:@Belette: If you look at the Bias 1.2.3 section in this discussion, the slowpath bug is caused by a Linux kernel bug that in the meantime was fixed but reopened again ([https://bugs.freedesktop.org/show_bug.cgi?id=89055]). Hopefully it will be stable in 4.5.<br />
:@BlueMatt: I love that the Arch Wiki is so detailed about special models - hence I think it really depends on how similar the XPS 12, 13 and 15 models are. I have not seen any reports on how the XPS 12 works at all, only 13 and 15. Hence, I'm positive with regard to keeping separate articles until we know how similar they really are. --[[User:Tommyfankhauser|Tommyfankhauser]] ([[User talk:Tommyfankhauser|talk]]) 07:45, 5 April 2016 (UTC)<br />
<br />
::You are welcome to add the info you have to [[Dell_XPS_13_%282016%29#XPS_12]] for now and to create an XPS12 article stub on your userpage. Open a question on the BBS, if you look for [https://wiki.archlinux.org/index.php?title=Dell_XPS_12_%282016%29&oldid=429570 info]. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 12:51, 5 April 2016 (UTC)<br />
<br />
== Touchpad multi-gesture ==<br />
I don't see anything specifically related to multi-gesture (zoom, pinch...) on the touchpad in the Dell XPS 13 page.<br />
<br />
I have installed xf86-input-libinput as suggested and both my touchpad and touch screen are working perfecty but I am missing multigesture..<br />
Using this tips: https://bbs.archlinux.org/viewtopic.php?pid=1617669#p1617669 [[User:Belette|Belette]] ([[User talk:Belette|talk]]) 08:28, 7 April 2016 (UTC)<br />
<br />
== <s>Now with official Linux support</s> ==<br />
<br />
I got an email informing me that the XPS 13 2016 model is now supported by Dell, as the 4.4 kernel with the required Broadcom drivers is available in Ubuntu 16.04 LTS. However I can't find information about this on the dell site, and [http://www.dell.com/us/business/p/xps-13-linux/pd] mentioned "This product is currently unavailable". -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 22:14, 16 May 2016 (UTC)<br />
<br />
:[https://wiki.archlinux.org/index.php?title=Dell_XPS_13_%282016%29&diff=435552&oldid=429579], thanks -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 11:43, 12 June 2016 (UTC)<br />
<br />
== EFISTUB booting ==<br />
<br />
I tried to get this laptop to boot the Linux kernel directly, via [[EFISTUB]], but none of the boot entries I created with <code>efibootmgr</code> worked. The exact same command did work, however, from the UEFI Shell v2, as well as from [[systemd-boot]]. So I suspect that this system’s UEFI implementation doesn’t properly support passing parameters to a boot entry. For booting, you either need an UEFI boot loader (like [[systemd-boot]]), or you need to link the command line into the image, as in [https://bentley.link/secureboot/#combine-the-kernel-initramfs-and-boot-options this article]. —[[User:LucasWerkmeister|LucasWerkmeister]] ([[User talk:LucasWerkmeister|talk]]) 11:16, 12 June 2016 (UTC)<br />
<br />
== Screen stuttering ==<br />
<br />
I am experiencing quite a lot of screen stuttering. Though I have chrome running in the background, half of my memory is still free and therefore should not cause problems even for an integrated GPU. The stuttering occurs independent from the application I use: e.g. my graphical terminal (gnome-terminal) is affected as well. Temperatures seem to be fine at about 50 to 60 °C and I load the latest intel microcode through my boot loader (systemd-boot). My X11 config file looks like this:<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|2=<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "sna" # UXA is an alternative<br />
Option "TearFree" "true" # SNA only, not needed for DRI3<br />
EndSection<br />
}}<br />
Googling the issue did not return viable results since most of them concern tearing, which I do not encounter, or recommend setting the {{ic|TearFree}} option to {{ic|true}} which I hava already done. I am using {{ic|mesa 12.0.1-2}}, {{ic|xf86-video-intel 1:2.99.917+676+g26f8ab5-1}}, {{ic|linux 4.6.4-1}} and {{ic|linux-firmware 20160516.80d463b-1}} with the above {{ic|xorg.conf.d/20-intel.conf}} config file. I assume it to be related to at least one of the packages. -- [[User:Edh|Edh]] ([[User talk:Edh|talk]]) 14:46, 28 July 2016 (UTC)<br />
<br />
== Kaby Lake Model ==<br />
<br />
Due out 4th October with intel's latest. A developer edition is coming too, bit later maybe 10th I think. <br />
Late 2016 model...what's the wiki address for this going to be? Dell XPS 13 (4th Gen)</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Samba&diff=439598Samba2016-07-03T07:08:50Z<p>Alexjj: Added smbtree tool for listing shares. It's helpful to see exactly what the sharenames looks like to the computer.</p>
<hr />
<div>[[Category:Network sharing]]<br />
[[cs:Samba]]<br />
[[da:Samba]]<br />
[[de:Samba]]<br />
[[es:Samba]]<br />
[[fr:Samba]]<br />
[[it:Samba]]<br />
[[ja:Samba]]<br />
[[ru:Samba]]<br />
[[sr:Samba]]<br />
[[tr:Samba]]<br />
[[zh-CN:Samba]]<br />
[[zh-TW:Samba]]<br />
{{Related articles start}}<br />
{{Related|Active Directory Integration}}<br />
{{Related|Samba/Active Directory domain controller}}<br />
{{Related|NFS}}<br />
{{Related articles end}}<br />
<br />
'''Samba''' is a re-implementation of the [[wikipedia:Server_Message_Block|SMB]] networking protocol. It facilitates file and printer sharing among Linux and Windows systems as an alternative to [[NFS]]. Some users say that Samba is easily configured and that operation is very straight-forward. However, many new users run into problems with its complexity and non-intuitive mechanism. This article provides instructions for users on how to setup Samba. It is strongly suggested that the user sticks close to the following directions.<br />
<br />
== Server configuration ==<br />
<br />
To share files with Samba, [[install]] the {{Pkg|samba}} package.<br />
<br />
The Samba server is configured in {{ic|/etc/samba/smb.conf.default}}. Copy the default Samba configuration file to {{ic|/etc/samba/smb.conf}}:<br />
# cp /etc/samba/smb.conf.default /etc/samba/smb.conf<br />
Otherwise, smbd will fail to start.<br />
<br />
=== Creating a share ===<br />
<br />
Edit {{ic|/etc/samba/smb.conf}}, scroll down to the '''Share Definitions''' section. The default configuration automatically creates a share for each user's home directory. However, users cannot actually log in unless they add a users wildcard.<br />
{{hc|/etc/samba/smb.conf|2=<br />
...<br />
[homes]<br />
comment = Home Directories<br />
browseable = no<br />
writable = yes<br />
valid users = %S<br />
}}<br />
<br />
It also creates a share for printers by default. There are a number of commented sample configurations included. More information about available options for shared resources can be found in {{ic|man smb.conf}}. [http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html There] is also an on-line version available.<br />
<br />
On Windows side, be sure to change {{ic|smb.conf}} to the in-use Windows Workgroup (default: {{ic|WORKGROUP}}).<br />
<br />
=== Starting services ===<br />
<br />
To provide basic file sharing through SMB [[start/enable]] {{ic|smbd.service}} and/or {{ic|nmbd.service}} services. See [http://www.samba.org/samba/docs/man/manpages-3/smbd.8.html smbd] and [http://www.samba.org/samba/docs/man/manpages-3/nmbd.8.html nmbd] manpages for details, as the {{ic|nmbd.service}} service may not always be required.<br />
<br />
{{Tip|Instead of having the service running since boot, you can enable {{ic|smbd.socket}} so the daemon is started on the first incoming connection. Do not forget to disable {{ic|smbd.service}}.}}<br />
<br />
=== Creating usershare path ===<br />
{{Note|This is an optional feature. Skip this section if you do not need it.}}<br />
<br />
"Usershare" is a feature that gives non-root users the capability to add, modify, and delete their own share definitions. <br />
<br />
This creates the usershare directory in {{ic|/var/lib/samba}}:<br />
<br />
# mkdir -p /var/lib/samba/usershare<br />
<br />
This makes the group sambashare:<br />
<br />
# groupadd -r sambashare<br />
<br />
This changes the owner of the directory and group you just created to root:<br />
<br />
# chown root:sambashare /var/lib/samba/usershare<br />
<br />
This changes the permissions of the usershare directory so that users in the group sambashare can read, write and execute files:<br />
<br />
# chmod 1770 /var/lib/samba/usershare<br />
<br />
Set the following variables in {{ic|smb.conf}} configuration file: <br />
<br />
{{hc|/etc/samba/smb.conf|2=<br />
...<br />
[global]<br />
usershare path = /var/lib/samba/usershare<br />
usershare max shares = 100<br />
usershare allow guests = yes<br />
usershare owner only = yes<br />
...<br />
}}<br />
<br />
Add your user to the ''sambashare'' group. Replace {{ic|''your_username''}} with the name of your user:<br />
<br />
# gpasswd sambashare -a ''your_username''<br />
<br />
Restart {{ic|smbd.service}} and {{ic|nmbd.service}} services.<br />
<br />
Log out and log back in. You should now be able to configure your samba share using GUI. For example, in [[Thunar]] you can right click on any directory and share it on the network. If you want to share pathes inside your home directory you must make it listable for the group others.<br />
<br />
=== Adding a user ===<br />
<br />
Samba requires a Linux user account - you may use an existing user account or create a [[Users and groups#User management|new one]].<br />
<br />
Although the user name is shared with Linux system, Samba uses a password separate from that of the Linux user accounts. Replace {{ic|samba_user}} with the chosen Samba user account:<br />
<br />
# smbpasswd -a ''samba_user''<br />
<br />
{{Note|Depending on the [https://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html#SERVERROLE server role], existing [[File permissions and attributes]] may need to be altered for the Samba user account.}}<br />
{{Note|If you want the new user only to be allowed to remotely access the file server shares through Samba, you can restrict other login options - disabling shell ({{ic|usermod --shell /usr/bin/nologin --lock username}}), disabling SSH logons (/etc/ssh/sshd_conf, option {{ic|AllowUsers}}), etc... Also see [[Security]] for hardening your system.}}<br />
<br />
=== Changing Samba user's password ===<br />
<br />
To change a user's password, use {{ic|smbpasswd}}:<br />
<br />
# smbpasswd ''samba_user''<br />
<br />
=== Required ports ===<br />
<br />
If you are using a [[firewall]], do not forget to open required ports (usually 137-139 + 445). For a complete list please check [https://wiki.samba.org/index.php/Samba_port_usage Samba port usage].<br />
<br />
=== Sample configuration ===<br />
See {{ic|man smb.conf}} for details and explanation of configuration options. There is also an [http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html online version] available.<br />
<br />
{{hc|/etc/samba/smb.conf|<nowiki><br />
[global]<br />
deadtime = 60 ; This is useful to stop a server's resources being exhausted by a large number of inactive connections<br />
disable netbios = yes ; Disable netbios announcing<br />
dns proxy = no ; nmbd spawns a second copy of itself to do the DNS name lookup requests on 'yes'<br />
hosts allow = 192.168.1. 127. 10. ; This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service<br />
invalid users = root ; This is a list of users that should not be allowed to login to this service<br />
security = user ; Use as standalone file server<br />
map to guest = Bad User ; Means user logins with an invalid password are rejected, or allow guest login and mapped into the guest account<br />
max connections = 100 ; Number of simultaneous connections to a service to be limited<br />
workgroup = WORKGROUP ; Workgroup the server will appear to be in when queried by clients<br />
<br />
; Uncomment the following lines to disable printer support<br />
;load printers = no<br />
;printing = bsd<br />
;printcap name = /dev/null<br />
;disable spoolss = yes<br />
<br />
; Default permissions for all shares <br />
inherit owner = yes ; Take the ownership of the parent directory when creating files/folders<br />
create mask = 0664 ; Create file mask<br />
directory mask = 0775 ; Create director mask<br />
force create mode = 0664 ; Force create file mask<br />
force directory mode = 0775 ; Force create directory mask<br />
<br />
; Private Share<br />
[private] ; translate into: \\server\private<br />
comment = My Private Share ; Seen next to a share when a client queries the server<br />
path = /path/to/data ; Directory to which the user of the service is to be given access<br />
read only = no ; An inverted synonym to writeable.<br />
valid users = user1 user2 @group1 @group2; restrict a service to a particular set of users and/or groups<br />
<br />
; Public Share<br />
;[public]<br />
; comment = My Public Share<br />
; path = /path/to/public<br />
; read only = yes<br />
; guest ok = yes; No password required to connect to the service<br />
</nowiki>}}<br />
<br />
Restart the {{ic|smbd}} service to apply configuration changes.<br />
{{note|Connected clients may need to reconnect before configuration changes take effect.}}<br />
<br />
=== Validate configuration ===<br />
The command {{ic|testparm}} validates the configuration of {{ic|smb.conf}}:<br />
<br />
# testparm -s<br />
<br />
== Client configuration ==<br />
<br />
For a lightweight method (without support for listing public shares, etc.), only install {{Pkg|cifs-utils}} to provide {{ic|/usr/bin/mount.cifs}}.<br />
<br />
Install {{Pkg|smbclient}} for an ftp-like command line interface. See {{ic|man smbclient}} for commonly used commands.<br />
<br />
Depending on the [[desktop environment]], GUI methods may be available. See [[#File manager configuration]] for use with a file manager.<br />
<br />
{{Note|After installing {{Pkg|cifs-utils}} or {{Pkg|smbclient}}, load the {{ic|cifs}} [[kernel module]] or reboot to prevent mount fails.}}<br />
<br />
=== List Public Shares ===<br />
The following command lists public shares on a server:<br />
<br />
$ smbclient -L ''hostname'' -U%<br />
<br />
Alternatively, running smbtree will show a tree diagram of all the shares. This isn't advisable on a network with a lot of computers, but can be helpful for diagnosing if you have the correct sharename.<br />
<br />
$ smbtree -b -N<br />
<br />
Where the options are:<br />
<br />
-b, --broadcast Use broadcast instead of using the master browser <br />
-N, --no-pass Don't ask for a password<br />
<br />
=== WINS host names ===<br />
<br />
The {{pkg|smbclient}} package provides a driver to resolve host names using WINS. To enable it, add “wins” to the “hosts” line in /etc/nsswitch.conf.<br />
<br />
=== Manual mounting ===<br />
<br />
Create a mount point for the share:<br />
<br />
# mkdir /mnt/''mountpoint''<br />
<br />
Mount the share using {{ic|mount.cifs}} as {{ic|type}}. Not all the options listed below are needed or desirable:<br />
{{bc|1=<br />
# mount -t cifs //''SERVER''/''sharename'' /mnt/''mountpoint'' -o user=''username'',password=''password'',uid=''username'',gid=''group'',workgroup=''workgroup'',ip=''serverip'',iocharset=''utf8''<br />
}}<br />
<br />
To allow users to mount it as long as the mount point resides in a directory controllable by the user; i.e. the user's home, append the {{ic|users}} mount option.<br />
<br />
{{Note|The option is user'''s''' (plural). For other filesystem types handled by mount, this option is usually ''user''; sans the "'''s'''".}}<br />
{{Warning|Using {{ic|uid}} and/or {{ic|gid}} as mount options may cause I/O errors, it's recommended to set/check the [[File permissions and attributes]] instead.}}<br />
<br />
''SERVER''<br />
: The server name.<br />
<br />
''sharename''<br />
: The shared directory.<br />
<br />
''mountpoint''<br />
: The local directory where the share will be mounted.<br />
<br />
{{ic|<nowiki>-o [options]</nowiki>}}<br />
: See {{ic|man mount.cifs}} for more information.<br />
<br />
{{Note|<br />
* The output "mount error(13): Permission denied", might be due to a bug in mount.cifs. See the following bug report. https://bugs.archlinux.org/task/43015#comment130771<br />
Try specifying the option <nowiki>"sec=ntlmv2"</nowiki> as workaround.<br />
* Abstain from using a trailing {{ic|/}}. {{ic|//''SERVER''/''sharename'''''/'''}} will not work.<br />
* If your mount does not work stable, stutters or freezes, try to enable different SMB protocol version with {{ic|1=vers=}} option. For example, {{ic|1=vers=2.0}} for Windows Vista mount.<br />
* If having timeouts on a mounted network share with cifs on a shutdown, see [[WPA supplicant#Problem with mounted network shares (cifs) and shutdown (Date: 1st Oct. 2015)]].<br />
}}<br />
<br />
===== Storing Share Passwords =====<br />
Storing passwords in a world readable file is not recommended. A safer method is to create a credentials file:<br />
{{hc|/path/to/credentials/share|2=<br />
username=''myuser''<br />
password=''mypass''<br />
}}<br />
Replace {{ic|<nowiki>username=myuser,password=mypass</nowiki>}} with {{ic|<nowiki>credentials=/path/to/credentials/share</nowiki>}}.<br />
<br />
The credential file should explicitly readable/writeable to root:<br />
# chmod 600 /path/to/credentials/share<br />
<br />
=== Automatic mounting ===<br />
{{Note|You may need to [[enable]] {{ic|systemd-networkd-wait-online.service}} or {{ic| NetworkManager-wait-online.service}} (depending on your setup) to proper enable booting on start-up.}}<br />
<br />
==== As mount entry ====<br />
<br />
This is an simple example of a {{ic|cifs}} [[fstab|mount entry]] that requires authentication:<br />
{{hc|/etc/fstab|2=<br />
//''SERVER''/''sharename'' /mnt/''mountpoint'' cifs username=''myuser'',password=''mypass'' 0 0<br />
}}<br />
<br />
{{Note|Space in sharename should be replaced by {{ic|\040}} (ASCII code for space in octal). For example, {{ic|//''SERVER''/share name}} on the command line should be {{ic|//''SERVER''/share\040name}} in {{ic|/etc/fstab}}.}}<br />
<br />
To speed up the service on boot, add the {{ic|1=x-systemd.automount}} option to the entry:<br />
{{hc|/etc/fstab|2=<br />
//''SERVER''/''SHARENAME'' /mnt/''mountpoint'' cifs credentials=''/path/to/smbcredentials/share'',x-systemd.automount 0 0<br />
}}<br />
<br />
==== As systemd unit ====<br />
Create a new {{ic|.mount}} file inside {{ic|/etc/systemd/system}}, e.g. {{ic|mnt-myshare.mount}}.<br />
<br />
{{ic|1=Requires=}} replace (if needed) with your [[:Category:Network_configuration|Network configuration]].<br />
<br />
{{ic|1=What=}} path to share<br />
<br />
{{ic|1=Where=}} path to mount the share<br />
<br />
{{ic|1=Options=}} share mounting options<br />
<br />
{{hc|/etc/systemd/system/mnt-myshare.mount|<nowiki><br />
[Unit]<br />
Description=Mount Share at boot<br />
Requires=systemd-networkd.service<br />
After=network-online.target<br />
Wants=network-online.target<br />
<br />
[Mount]<br />
What=//server/share<br />
Where=/mnt/myshare<br />
Options=credentials=/etc/samba/creds/myshare,iocharset=utf8,rw,x-systemd.automount<br />
Type=cifs<br />
TimeoutSec=30<br />
<br />
[Install]<br />
WantedBy=multi-user.target<br />
</nowiki>}}<br />
<br />
To use {{ic|mnt-myshare.mount}}, [[start]] the unit and [[enable]] it to run on system boot.<br />
<br />
==== smbnetfs ====<br />
<br />
{{Note|1=smbnetfs needs an intact Samba server setup.<br />
See above on how to do that.}}<br />
<br />
First, check if you can see all the shares you are interested in mounting:<br />
$ smbtree -U ''remote_user''<br />
<br />
If that does not work, find and modify the following line<br />
in {{ic|/etc/samba/smb.conf}} accordingly:<br />
<br />
domain master = auto<br />
<br />
Now [[restart]] {{ic|smbd.service}} and {{ic|nmbd.service}}.<br />
<br />
If everything works as expected, [[pacman#Installing specific packages|install]] {{Pkg|smbnetfs}} from the official repositories.<br />
<br />
Then, add the following line to {{ic|/etc/fuse.conf}}:<br />
<br />
user_allow_other<br />
<br />
Now copy the directory {{ic|/etc/smbnetfs/.smb}} to your home directory:<br />
<br />
$ cp -a /etc/smbnetfs/.smb ~<br />
<br />
Then create a link to {{ic|smb.conf}}:<br />
<br />
$ ln -sf /etc/samba/smb.conf ~/.smb/smb.conf<br />
<br />
If a username and a password are required to access some of the shared folders, edit {{ic|~/.smb/smbnetfs.auth}}<br />
to include one or more entries like this:<br />
<br />
{{hc|~/.smb/smbnetfs.auth|<br />
auth "hostname" "username" "password"<br />
}}<br />
<br />
It is also possible to add entries for specific hosts to be mounted by smbnetfs, if necessary.<br />
More details can be found in {{ic|~/.smb/smbnetfs.conf}}.<br />
<br />
If you are using the Dolphin or Nautilus file managers, you may want to add the following to {{ic|~/.smb/smbnetfs.conf}} to avoid "Disk full" errors as smbnetfs by default will report 0 bytes of free space:<br />
{{hc|~/.smb/smbnetfs.conf|<br />
free_space_size 1073741824<br />
}}<br />
<br />
When you are done with the configuration, you need to run<br />
$ chmod 600 ~/.smb/smbnetfs.*<br />
Otherwise, smbnetfs complains about 'insecure config file permissions'.<br />
<br />
Finally, to mount your Samba network neighbourhood to a directory of your choice, call<br />
$ smbnetfs ''mount_point''<br />
<br />
===== Daemon =====<br />
<br />
The Arch Linux package also maintains an additional system-wide operation mode for smbnetfs. To enable it, you need to make the<br />
said modifications in the directoy {{ic|/etc/smbnetfs/.smb}}.<br />
<br />
Then, you can start and/or enable the {{ic|smbnetfs}} [[daemon]] as usual. The system-wide mount point is at {{ic|/mnt/smbnet/}}.<br />
<br />
==== autofs ====<br />
<br />
See [[Autofs]] for information on the kernel-based automounter for Linux.<br />
<br />
=== File manager configuration ===<br />
<br />
==== GNOME Files, Nemo, Caja, Thunar and PCManFM ====<br />
<br />
In order to access samba shares through GNOME Files, Nemo, Caja, Thunar or PCManFM, install the {{Pkg|gvfs-smb}} package, available in the [[official repositories]].<br />
<br />
Press {{ic|Ctrl+l}} and enter {{ic|smb://''servername''/''share''}} in the location bar to access your share.<br />
<br />
The mounted share is likely to be present at {{ic|/run/user/''your_UID''/gvfs}} or {{ic|~/.gvfs}} in the filesystem.<br />
<br />
==== KDE ====<br />
<br />
KDE, has the ability to browse Samba shares built in. Therefore do not need any additional packages. However, for a GUI in the KDE System Settings, install the {{Pkg|kdenetwork-filesharing}} package from the official repositories.<br />
<br />
If when navigating with Dolphin you get a "Time Out" Error, you should uncomment and edit this line in smb.conf:{{bc|1=name resolve order = lmhosts bcast host wins}}<br />
as shown in this [http://ubuntuforums.org/showthread.php?t=1605499 page].<br />
<br />
==== Other graphical environments ====<br />
<br />
There are a number of useful programs, but they may need to have packages created for them. This can be done with the Arch package build system. The good thing about these others is that they do not require a particular environment to be installed to support them, and so they bring along less baggage.<br />
<br />
* {{Pkg|pyneighborhood}} is available in the official repositories.<br />
* LinNeighborhood, RUmba, xffm-samba plugin for Xffm are not available in the official repositories or the AUR. As they are not officially (or even unofficially supported), they may be obsolete and may not work at all.<br />
<br />
== Tips and tricks ==<br />
=== Block certain file extensions on Samba share ===<br />
{{Note|Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned.}}<br />
Samba offers an option to block files with certain patterns, like file extensions. This option can be used to prevent dissemination of viruses or to dissuade users from wasting space with certain files. More information about this option can be found in {{ic|man smb.conf}}.<br />
<br />
{{hc|/etc/samba/smb.conf|2=<br />
...<br />
[myshare]<br />
comment = Private<br />
path = /mnt/data<br />
read only = no<br />
veto files = /*.exe/*.com/*.dll/*.bat/*.vbs/*.tmp/*.mp3/*.avi/*.mp4/*.wmv/*.wma/<br />
}}<br />
<br />
=== Discovering network shares ===<br />
If nothing is known about other systems on the local network, and automated tools such as [[#smbnetfs|smbnetfs]] are not available, the following methods allow one to manually probe for Samba shares.<br />
<br />
1. First, install {{Pkg|nmap}} and {{Pkg|smbclient}} using [[pacman]]:<br />
# pacman -S nmap smbclient<br />
<br />
2. {{ic|nmap}} checks which ports are open:<br />
# nmap -p 139 -sT 192.168.1.*<br />
<br />
In this case, a scan on the 192.168.1.* IP address range and port 139 has been performed, resulting in:<br />
{{hc<br />
|$ nmap -sT 192.168.1.*<br />
|Starting nmap 3.78 ( http://www.insecure.org/nmap/ ) at 2005-02-15 11:45 PHT<br />
Interesting ports on 192.168.1.1:<br />
(The 1661 ports scanned but not shown below are in state: closed)<br />
PORT STATE SERVICE<br />
'''139/tcp open netbios-ssn'''<br />
5000/tcp open UPnP<br />
<br />
Interesting ports on 192.168.1.5:<br />
(The 1662 ports scanned but not shown below are in state: closed)<br />
PORT STATE SERVICE<br />
6000/tcp open X11<br />
<br />
Nmap run completed -- 256 IP addresses (2 hosts up) scanned in 7.255 seconds<br />
}}<br />
<br />
The first result is another system; the second happens to be the client from where this scan was performed.<br />
<br />
3. Now that systems with port 139 open are revealed, use {{ic|nmblookup}} to check for NetBIOS names: <br />
{{hc<br />
|$ nmblookup -A 192.168.1.1<br />
|Looking up status of 192.168.1.1<br />
PUTER <00> - B <ACTIVE><br />
HOMENET <00> - <GROUP> B <ACTIVE><br />
PUTER <03> - B <ACTIVE><br />
'''PUTER <20> - B <ACTIVE>'''<br />
HOMENET <1e> - <GROUP> B <ACTIVE><br />
USERNAME <03> - B <ACTIVE><br />
HOMENET <1d> - B <ACTIVE><br />
MSBROWSE <01> - <GROUP> B <ACTIVE><br />
}}<br />
<br />
Regardless of the output, look for '''<20>''', which shows the host with open services.<br />
<br />
4. Use {{ic|smbclient}} to list which services are shared on ''PUTER''. If prompted for a password, pressing enter should still display the list:<br />
{{hc<br />
|$ smbclient -L \\PUTER<br />
|<nowiki><br />
Sharename Type Comment<br />
--------- ---- -------<br />
MY_MUSIC Disk<br />
SHAREDDOCS Disk<br />
PRINTER$ Disk<br />
PRINTER Printer<br />
IPC$ IPC Remote Inter Process Communication<br />
<br />
Server Comment<br />
--------- -------<br />
PUTER<br />
<br />
Workgroup Master<br />
--------- -------<br />
HOMENET PUTER<br />
</nowiki>}}<br />
<br />
=== Remote control of Windows computer ===<br />
Samba offers a set of tools for communication with Windows. These can be handy if access to a Windows computer through remote desktop is not an option, as shown by some examples.<br />
<br />
Send shutdown command with a comment:<br />
<br />
$ net rpc shutdown -C "comment" -I IPADDRESS -U USERNAME%PASSWORD<br />
A forced shutdown instead can be invoked by changing -C with comment to a single -f. For a restart, only add -r, followed by a -C or -f.<br />
<br />
Stop and start services:<br />
<br />
$ net rpc service stop SERVICENAME -I IPADDRESS -U USERNAME%PASSWORD<br />
<br />
To see all possible net rpc command:<br />
<br />
$ net rpc<br />
<br />
===Share files without a username and password===<br />
Edit {{ic|/etc/samba/smb.conf}} and add the following line:<br />
{{bc|<nowiki>map to guest = Bad User</nowiki>}}<br />
<br />
After this line:<br />
{{bc|<nowiki>security = user</nowiki>}}<br />
<br />
Restrict the shares data to a specific interface replace:<br />
{{bc|<nowiki>; interfaces = 192.168.12.2/24 192.168.13.2/24</nowiki>}}<br />
<br />
with:<br />
<br />
{{bc|<nowiki><br />
interfaces = lo eth0<br />
bind interfaces only = true</nowiki>}}<br />
<br />
Optionally edit the account that access the shares, edit the following line:<br />
{{bc|<nowiki>; guest account = nobody</nowiki>}}<br />
<br />
For example:<br />
{{bc|<nowiki> guest account = pcguest</nowiki>}}<br />
<br />
And do something in the likes of:<br />
{{bc|<nowiki># useradd -c "Guest User" -d /dev/null -s /bin/false pcguest</nowiki>}}<br />
<br />
Then setup a "" password for user pcguest.<br />
<br />
The last step is to create share directory (for write access make writable = yes):<br />
<br />
{{bc|<nowiki><br />
[Public Share]<br />
path = /path/to/public/share<br />
available = yes<br />
browsable = yes<br />
public = yes<br />
writable = no<br />
</nowiki>}}<br />
<br />
{{note|Make sure the guest also has permission to visit /path, /path/to and /path/to/public, according to [http://unix.stackexchange.com/questions/13858/do-the-parent-directorys-permissions-matter-when-accessing-a-subdirectory http://unix.stackexchange.com/questions/13858/do-the-parent-directorys-permissions-matter-when-accessing-a-subdirectory]}}<br />
<br />
==== Sample Passwordless Configuration ====<br />
This is the configuration I use with samba 4 for easy passwordless filesharing with family on a home network. Change any options needed to suit your network (workgroup and interface). I'm restricting it to the static IP I have on my ethernet interface, just delete that line if you do not care which interface is used.<br />
{{hc|/etc/samba/smb.conf|<nowiki><br />
[global]<br />
<br />
workgroup = WORKGROUP<br />
<br />
server string = Media Server<br />
<br />
security = user<br />
map to guest = Bad User<br />
<br />
log file = /var/log/samba/%m.log<br />
<br />
max log size = 50<br />
<br />
<br />
interfaces = 192.168.2.194/24<br />
<br />
<br />
dns proxy = no <br />
<br />
<br />
[media]<br />
path = /shares<br />
public = yes<br />
only guest = yes<br />
writable = yes<br />
<br />
[storage]<br />
path = /media/storage<br />
public = yes<br />
only guest = yes<br />
writable = yes<br />
</nowiki>}}<br />
<br />
=== Build Samba without CUPS ===<br />
<br />
Just build without cups installed. From the [https://wiki.samba.org/index.php/Samba_as_a_print_server Samba Wiki]:<br />
<blockquote>Samba has built-in support [for CUPS] and defaults to CUPS if the development package (aka header files and libraries) could be found at compile time.</blockquote><br />
<br />
Of course, modifications to the PKGBUILD will also be necessary: libcups will have to be removed from the depends and makedepends arrays and other references to cups and printing will need to be deleted. In the case of the 4.1.9-1 PKGBUILD, 'other references' includes lines 169, 170 and 236:<br />
{{bc|<br />
mkdir -p ${pkgdir}/usr/lib/cups/backend<br />
ln -sf /usr/bin/smbspool ${pkgdir}/usr/lib/cups/backend/smb<br />
install -d -m1777 ${pkgdir}/var/spool/samba<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Failed to start Samba SMB/CIFS server ===<br />
<br />
Check if the permissions are set correctly for {{ic|/var/cache/samba/}} and restart the {{ic|smbd.service}} or {{ic|smbd.socket}}:<br />
# chmod 0755 /var/cache/samba/msg<br />
<br />
=== Unable to overwrite files, permissions errors ===<br />
Possible solutions:<br />
*Append the mount option {{ic|nodfs}} to the {{ic|/etc/fstab}} [[#Add_Share_to_.2Fetc.2Ffstab|entry]].<br />
*Add {{ic|<nowiki>msdfs root = no</nowiki>}} to the {{ic|[global]}} section of the server's {{ic|/etc/samba/smb.conf}}.<br />
<br />
=== Windows clients keep asking for password even if Samba shares are created with guest permissions ===<br />
Set {{ic|map to guest}} inside the {{ic|global}} section of {{ic|/etc/samba/smb.conf}}:<br />
map to guest = Bad User<br />
<br />
=== Windows 7 connectivity problems - mount error(12): cannot allocate memory ===<br />
<br />
A known Windows 7 bug that causes "mount error(12): cannot allocate memory" on an otherwise perfect cifs share on the Linux end can be fixed by setting a few registry keys on the Windows box as follows:<br />
<br />
*{{ic|HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache}} (set to {{ic|1}})<br />
*{{ic|HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size}} (set to {{ic|3}})<br />
<br />
Alternatively, start Command Prompt in Admin Mode and execute the following:<br />
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v "LargeSystemCache" /t REG_DWORD /d 1 /f<br />
reg add "HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" /v "Size" /t REG_DWORD /d 3 /f<br />
<br />
Do one of the following for the settings to take effect:<br />
* Restart Windows<br />
* Restart the Server service via services.msc<br />
* From the Command Prompt run: 'net stop lanmanserver' and 'net start lanmanserver' - The server may automatically restart after stopping it.<br />
<br />
{{Note|Googling will reveal another tweak recommending users to add a key modifying the "IRPStackSize" size. This is incorrect for fixing this issue under Windows 7. Do not attempt it.}}<br />
<br />
[http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017 Original article].<br />
<br />
=== Trouble accessing a password-protected share from Windows ===<br />
<br />
{{Note|This needs to be added to the '''local smb.conf''', not to the server's smb.conf}}<br />
<br />
For trouble accessing a password protected share from Windows, try adding this to {{ic|/etc/samba/smb.conf}}:[http://blogs.computerworld.com/networking_nightmare_ii_adding_linux]<br />
<br />
[global]<br />
# lanman fix<br />
client lanman auth = yes<br />
client ntlmv2 auth = no<br />
<br />
=== Getting a dialog box up takes a long time ===<br />
<br />
I had a problem that it took ~30 seconds to get a password dialog box up when trying to connect from both Windows XP/Windows 7. Analyzing the error.log on the server I saw:<br />
<br />
[2009/11/11 06:20:12, 0] printing/print_cups.c:cups_connect(103)<br />
Unable to connect to CUPS server localhost:631 - Interrupted system call<br />
<br />
This keeps samba from asking cups and also from complaining about /etc/printcap missing:<br />
<br />
printing = bsd<br />
printcap name = /dev/null<br />
<br />
=== Error: Failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL ===<br />
<br />
If you are a home user and using samba purely for file sharing from a server or NAS, you are probably not interested in sharing printers through it. If so, you can prevent this error from occurring by adding the following lines to your {{ic|/etc/samba/smb.conf}}:<br />
{{bc|<nowiki><br />
load printers = No<br />
printing = bsd<br />
printcap name = /dev/null<br />
disable spoolss = Yes<br />
</nowiki>}}<br />
[[Restart]] the samba service, {{ic|smbd.service}}, and then check your logs:<br />
{{bc|cat /var/log/samba/smbd.log}}<br />
and the error should now no longer be appearing.<br />
<br />
=== Sharing a folder fails ===<br />
<br />
It means that while you are sharing a folder from ''Dolphin'' (file manager) and everything seems ok at first, after restarting ''Dolphin'' the share icon is gone from the shared folder, and also some output like this in terminal (''Konsole'') output:<br />
<br />
‘net usershare’ returned error 255: net usershare: usershares are currently disabled<br />
<br />
To fix it, enable usershare as described in [[#Creating usershare path]].<br />
<br />
=== "Browsing" network fails with "Failed to retrieve share list from server" ===<br />
And you are using a firewall (iptables) because you do not trust your local (school, university, hotel) local network. This may be due to the following: When the smbclient is browsing the local network it sends out a broadcast request on udp port 137. The servers on the network then reply to your client but as the source address of this reply is different from the destination address iptables saw when sending the request for the listing out, iptables will not recognize the reply as being "ESTABLISHED" or "RELATED", and hence the packet is dropped. A possible solution is to add:{{bc|<br />
iptables -t raw -A OUTPUT -p udp -m udp --dport 137 -j CT --helper netbios-ns<br />
}}<br />
to your iptables setup.<br />
<br />
=== You are not the owner of the folder ===<br />
<br />
Simply try to reboot the system.<br />
<br />
=== protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE ===<br />
<br />
The client probably does not have access to shares. Make sure clients' IP address is in {{ic|1=hosts allow =}} line in {{ic|/etc/samba/smb.conf}}.<br />
<br />
=== Connection to SERVER failed: (Error NT_STATUS_UNSUCCESSFUL) ===<br />
<br />
You are probably passing wrong server name to {{ic|smbclient}}. To find out the server name, run {{ic|hostnamectl}} on the server and look at "Transient hostname" line<br />
<br />
=== Connection to SERVER failed: (Error NT_STATUS_CONNECTION_REFUSED) ===<br />
<br />
Make sure that the server has started. The shared directories should exist and be accessible.<br />
<br />
== See also ==<br />
<br />
* [http://www.samba.org/samba/docs/SambaIntro.html Samba: An Introduction]<br />
* [http://www.samba.org/ Official Samba site]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=405373Talk:Dell XPS 13 (9343)2015-10-18T00:06:16Z<p>Alexjj: /* Late 2015 model with Skylake CPU */</p>
<hr />
<div>== Read this first ==<br />
<br />
If you are adding information about a bug/regression, PLEASE include a source link to a bug tracker, forum, etc. so that others can update this wiki page when the issue is resolved. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 20:30, 10 August 2015 (UTC)<br />
<br />
== wifi during installation ==<br />
<br />
I'm going to install Arch Linux on my new XPS 9343!<br />
Prior to begin, I want to solve a question: because wireless chipset works only after installing a package from AUR (reading main wiki page), how can I make wireless working in the setup environment ???<br />
<br />
[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 11:52, 29 May 2015 (UTC)<br />
<br />
: First off, the wiki talk page isn't the best place to ask for help-- you should be asking this question in the forums. I'll answer it anyway, though. Ideally you'd use a USB Ethernet adapter, but if you don't have one, you should download the appropriate kernel headers package and the broadcom-wl pkgbuild on another computer, and then copy them onto your XPS with a flash drive after you're finished installing Arch. When you install Arch, make sure you also install the `base-devel` group so that you can build AUR packages.<br />
<br />
:[[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 12:10, 29 May 2015 (UTC)<br />
<br />
:: thank you! and yes, usually I use our forum, but I thought that this place should be better due to very high particular topic... forum is too broad. I don't have an USB-ethernet adapter, so this must be the way. However I haven't understand exactly the trick: I build the needed package using another pc and I transfer it in the XPS, well. When I have to install it?<br />
<br />
::I think this must be added as first section in the wiki page<br />
<br />
::[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 13:41, 29 May 2015 (UTC)<br />
<br />
== FHD/QHD+ ==<br />
<br />
This wiki states that linux buyers "should pay special attention to display configuration options (FHD/QHD+)" but then there is nothing mentioned about these options anywhere else.<br />
<br />
Sorry, but can I ask what special attention should I pay? Do both screen options work fine in Linux?<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 13:28, 1 June 2015 (UTC)<br />
<br />
:They both work fine, but [[HiDPI]] support is a necessity for the QHD+ screen, whereas you can get away with just changing text size on the FHD. HiDPI is still uneven on Linux; Gnome 3 currently has the best HiDPI support, while KDE 5's is a work-in-progress. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 13:45, 1 June 2015 (UTC)<br />
<br />
::Perhaps add your comment to the main page? I use GNOME 3 BTW and knew that. I don't really see the point of getting the QHD+ display and just scaling most things up. It also is glossy instead of matte, chews more battery, and causes slightly more heat. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 13:53, 1 June 2015 (UTC)<br />
<br />
:::Done. I agree with your points; that's exactly why I got the FHD model myself. The only configuration I had to do was increase the text scaling in Gnome to 1.25. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 06:45, 2 June 2015 (UTC)<br />
<br />
== Intel wifi option? ==<br />
<br />
The page says:<br />
<br />
"The Intel module has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so."<br />
<br />
I guess replacing the factory Broadcom card would void the warranty though? Is opening the case and replacing the card difficult? Perhaps comments about these could be added.<br />
<br />
BTW. I am about to get a i5+8GB+256GB+broadcom wifi+FHD model delivered and will clobber the windows install with Arch. Hence my interest in this wiki page. I will contribute feedback when I do the install.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 04:36, 3 June 2015 (UTC)<br />
<br />
:As far as I know, if you replace the WiFi card, the rest of the laptop is still covered by the warranty. Dell is pretty good about user-serviceability; they even provide [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop/xps-13-9343-laptop_Service%20Manual_en-us.pdf the service manual] (PDF) for free. They will not, however, cover any damage that you may cause while working inside your laptop. It's quite easy to replace the WiFi card, but you do need a Torx T5 screwdriver and a plastic spudger to remove the bottom half of the case, and most people don't have those lying around. As for including instructions in the wiki, disassembling the laptop has no relevance to its support in Arch, so I don't think that would belong here. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:06, 3 June 2015 (UTC)<br />
:For the technical part of swapping things out [[User:Soren121|Soren121]] has got you covered pretty well already. Even if you have those tools though (I did the modification and am in fact the person that put up the information on the page, so yes, I had the tools ready), getting the bottom off can be a bit troublesome to say the least. For some parts you do have to apply a bit more force than you would think is good for the device, but don't worry, it's pretty sturdy and can handle it should you ever decide to go through with the modification. Once the bottom is removed its a matter of removing the single screw that holds the WiFi card in place, unplugging the two antenna-wires from the module, followed by, obviously, putting the new module in place and reversing the steps. The antenna wires are color-coded, and so are the replacement WiFi modules, so you should have no problem matching the antenna wires. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:11, 30 June 2015 (UTC)<br />
<br />
== VirtualBox freezing workaround ==<br />
<br />
I just added a edit to provide a solution for the Broadwell related VirtualBox Virtual Machine startup freezing issues. However I'm not entirely sure if I placed this tip too well... while it does affect the Dell XPS 13 (as it obviously is a Broadwell based device), this issue does span over multiple device making me believe it might be better placed in the VirtualBox page than this one.<br />
<br />
So, what do you guys think? Place it on the VirtualBox page or leave it here?<br />
<br />
If we do move it to the VirtualBox page, should a reference link remain on the Dell XPS 13 (2015) page or should we treat this the same way we did the PulseAudio flat volumes issue? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 08:26, 7 July 2015 (UTC)<br />
<br />
: I vote to move it to the VirtualBox page and remove it from this page. First off, VirtualBox is not a commonly-installed system service or application. You could reasonably expect most Linux desktop users to have Pulse installed (unless they're still scared of it), but not so with VirtualBox. Second, like you said, it affects all Broadwell machines, so it shouldn't just be kept here if at all. For example, originally I had only listed the Broadwell TTY switching bug here on this page. Later on, I noticed in the forums that people with the X1 Carbon, among other machines, were linking to this page for help. I moved that section to [[Intel graphics]] after that, because I realized they shouldn't have to hunt down the page for a device they don't have just to get help. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 16:22, 7 July 2015 (UTC)<br />
<br />
:: The Intel bug was fixed from April, we're July now, so it can be safely deleted. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:47, 7 July 2015 (UTC)<br />
<br />
::: True. My concern was that a lot of people using other distros reference the XPS 13 wiki page here, because it's one of the more complete XPS 13 Linux help pages available. The bug was fixed upstream but they still haven't released an update with it yet. I know Ubuntu and Arch backported the patch but many others haven't. Personally, I would prefer to wait and remove it when upstream releases that update. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:55, 7 July 2015 (UTC)<br />
<br />
:: I've moved the VirtualBox freeze troubleshooting section to the VirtualBox page now. Everything's clean and nice on the XPS 13 page again. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 05:10, 9 July 2015 (UTC)<br />
<br />
== Powersaving ==<br />
<br />
Since kernel 4.1.2-2 is now in the stable repositories, can the proposed kernel parameters in the Powersaving section be used without the linux-mainline kernel? The section doesn't say which exact changes or patches in the kernel are needed to make this work. I would just try it out but I am unsure how to confirm if it is actually working.<br />
<br />
[[User:FlorianH|FlorianH]] ([[User talk:FlorianH|talk]]) 11:37, 16 July 2015 (UTC)<br />
<br />
:It should work fine with the standard 4.1 Arch kernel. The linux-mainline package doesn't include any extra patches. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:16, 23 July 2015 (UTC)<br />
<br />
I had fairly frequent freezes which went away when I got rid of i915.enable_fbc=1. Is this just my system or is it worth mentioning?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:56, 30 July 2015 (UTC)<br />
<br />
:It's not just you. I had to remove that option as well as the screen would flicker like crazy if I didn't. I guess it might be worthwhile mentioning on the page. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 12:11, 30 July 2015 (UTC)<br />
<br />
:It seems that the flicker we experience with the i915.enable_fbc=1 isn't actually a bug but rather an issue with the DVMT pre-allocated memory for the GPU. I've captured an error message in dmesg right after a flicker occured stating that this is the most likely issue. Sadly, our BIOS doesn't allow the configuration of the DVMT pre-allocated memory size, so we are stuck with the 64MB it preallocates by default. I did however find a tutorial on the x86 hackintosh community forums on how to manually change the BIOS saved settings for DVMT on the Dell XPS 13 9343 using the EFI shell (see here: http://www.tonymacx86.com/yosemite-laptop-support/162062-guide-intel-hd-graphics-5500-os-x-yosemite-10-10-3-a.html). I assume that if we changed this value to an higher setting, then the Framebuffer compression algorithm wouldn't run out of memory while doing its job anymore, avoiding the flicker entirely. Someone care to try this? I can't quite afford messing (up) with my setup over the week as I use my XPS 13 as my actual work machine. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:30, 3 August 2015 (UTC)<br />
<br />
::No-one else seems to be keen on low-level EFI-hacking. DVMT is meant to be *dynamic*. Rather than a problem with the pre-allocated memory, couldn't it be a problem with the pre-allocated/dynamically-allocated ratio chosen by the driver? [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:43, 12 August 2015 (UTC)<br />
<br />
A note says that "Enabling PSR support ... will further reduce idle power usage to ~2.6 W ..."; we should provide the '''basic''' power usage, prior to enabling this feature, so a user can ''evaluate'' if use it or not... should result in: "this feature allow you to reduce power usage from X to Y watts"; unfortunately now I can't do it on my own<br />
<br />
--[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 08:41, 20 August 2015 (UTC)<br />
<br />
== NetworkManager ==<br />
<br />
The sentence in [[Dell_XPS_13_(2015)#Connection_issues_with_Broadcom_wireless]]:<br />
:"If your WiFi connection drops constantly, try disabling NetworkManager (if you have it installed) and fall back to using wifi-menu."<br />
makes no sense as NetworkManager and netctl both use [[wpa_supplicant]] to negotiate a wireless connection. Unless someone can make an exact relation between NetworkManager and this hardware, this sentence should be removed. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:13, 3 September 2015 (UTC)<br />
:: Removed. If anyone has an objection, feel free to discuss. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:12, 30 September 2015 (UTC)<br />
<br />
== LCD backlight ==<br />
<br />
I'm experiencing problems where the backlights turn on again one second after I run '''xset dpms force off'''. However, I do not feel confident enough that this is a hardware problem to bring this up as an issue in the article. Can anybody replicate or tell me that I'm doing it wrong?<br />
[[User:Aron|Aron]] ([[User talk:Aron|talk]]) 15:01, 17 September 2015 (UTC)<br />
<br />
== The render ring hang report ==<br />
<br />
This section has no sources and the problem it describes is not reproducible. I haven't been able to find bug reports on the Mesa or kernel trackers that matches the description, nor have I experienced such an issue on my own XPS 13 with the latest Mesa drivers. Unless someone is able to provide a source/proof of the issue, I'd like to propose that we remove this section. Without knowing what the problem is, we won't know if the issue has been resolved (or if it even was an issue in the first place!) [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:03, 30 September 2015 (UTC)<br />
<br />
:Sounds like a good idea; also, the version of Mesa mentioned in the section is almost 3 months old at this point and there have been a fair few bug-fix releases since then. [[User:Bryn|Bryn]] ([[User talk:Bryn|talk]]) 22:45, 1 October 2015 (UTC)<br />
<br />
:: Also an excellent point. I'll remove it in a few days if no one raises an objection. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 22:52, 1 October 2015 (UTC)<br />
<br />
:: Removed. If you have an objection, again, feel free to discuss. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 03:43, 11 October 2015 (UTC)<br />
<br />
== Touchpad with palm detection ==<br />
<br />
I'd like to share with you a new configuration for touchpad pointed out by Barton George:<br />
http://bartongeorge.net/2015/09/30/alternate-touchpad-configuration-for-xps-9343-developer-edition-running-ubuntu-15-04/<br />
touchpad with palm detection using "libinput"<br />
I haven't tried it!<br />
<br />
--[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 10:31, 7 October 2015 (UTC)<br />
<br />
:The Touchpad section of this wiki page has had instructions for using libinput for months now! :) And yes, it does work. The only drawback is that it is less configurable than the synaptics driver. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:00, 7 October 2015 (UTC)<br />
<br />
:: Yes, I read it! I noticed a quiet different .conf file and this is a reason why I posted the link. --[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 13:15, 8 October 2015 (UTC)<br />
<br />
== Audio issues with Realtek ALC3263 ==<br />
I've experienced severe audio problems using 4.2.3-1 (and at least 4.2.2) and BIOS updated to A05. Sound worked for some undefined period of time and then speakers (or headphones) started producing crackling sounds and eventually sound became very distorted. dmesg output when this started:<br />
<br />
snd_hda_intel IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
...<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
<br />
IRQ timing line showed up shortly after sound device was used and spurious response lines showed up when crackling started. This was clearly a driver problem and I tested different snd_hda_intel options, with no good results. Eventually I decided to enable more verbose debugging for sound devices and I built a custom kernel using current rc with arch default config (4.3.0-rc5-ARCH). When I booted into it I never experienced sound issues again. --[[User:Lknix|Lknix]] ([[User talk:Lknix|talk]]) 19:54, 13 October 2015 (UTC)<br />
<br />
== Call for testing ==<br />
I managed to find an Arch specific issue: https://bugzilla.kernel.org/show_bug.cgi?id=105251#c9<br />
Can you please download the Arch Live CD from https://www.archlinux.org/download/, flash it to an usb drive using dd, then boot it using EFI at least 20 times (the crash is much more difficult to reproduce with the live CD) and write about it? If you cannot manage to reproduce it within 20 boots you probably aren't being afflicted.<br />
<br />
afflicted (QHD+, Intel Wifi, i7-5600U)[[User:Darkbasic|darkbasic (http&#58;//www.linuxsystems.it/)]] ([[User talk:Darkbasic|talk]]) 14:52, 12 October 2015 (UTC)<br />
<br />
== Late 2015 model with Skylake CPU ==<br />
<br />
At beginning of October Dell refreshed the XPS line with skylake CPU. Firstly, should the wiki page/information on the previous model should be re-named to Early 2015? Secondly, anyone bought and tested the latest model with Linux? New model includes Thunderbolt 3 and USB 3.1 as that's part of intel skylake now. Perhaps that'll mean Linux support through intel code?</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=405372Talk:Dell XPS 13 (9343)2015-10-18T00:00:23Z<p>Alexjj: Started topic on the late 2015 model refresh</p>
<hr />
<div>== Read this first ==<br />
<br />
If you are adding information about a bug/regression, PLEASE include a source link to a bug tracker, forum, etc. so that others can update this wiki page when the issue is resolved. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 20:30, 10 August 2015 (UTC)<br />
<br />
== wifi during installation ==<br />
<br />
I'm going to install Arch Linux on my new XPS 9343!<br />
Prior to begin, I want to solve a question: because wireless chipset works only after installing a package from AUR (reading main wiki page), how can I make wireless working in the setup environment ???<br />
<br />
[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 11:52, 29 May 2015 (UTC)<br />
<br />
: First off, the wiki talk page isn't the best place to ask for help-- you should be asking this question in the forums. I'll answer it anyway, though. Ideally you'd use a USB Ethernet adapter, but if you don't have one, you should download the appropriate kernel headers package and the broadcom-wl pkgbuild on another computer, and then copy them onto your XPS with a flash drive after you're finished installing Arch. When you install Arch, make sure you also install the `base-devel` group so that you can build AUR packages.<br />
<br />
:[[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 12:10, 29 May 2015 (UTC)<br />
<br />
:: thank you! and yes, usually I use our forum, but I thought that this place should be better due to very high particular topic... forum is too broad. I don't have an USB-ethernet adapter, so this must be the way. However I haven't understand exactly the trick: I build the needed package using another pc and I transfer it in the XPS, well. When I have to install it?<br />
<br />
::I think this must be added as first section in the wiki page<br />
<br />
::[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 13:41, 29 May 2015 (UTC)<br />
<br />
== FHD/QHD+ ==<br />
<br />
This wiki states that linux buyers "should pay special attention to display configuration options (FHD/QHD+)" but then there is nothing mentioned about these options anywhere else.<br />
<br />
Sorry, but can I ask what special attention should I pay? Do both screen options work fine in Linux?<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 13:28, 1 June 2015 (UTC)<br />
<br />
:They both work fine, but [[HiDPI]] support is a necessity for the QHD+ screen, whereas you can get away with just changing text size on the FHD. HiDPI is still uneven on Linux; Gnome 3 currently has the best HiDPI support, while KDE 5's is a work-in-progress. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 13:45, 1 June 2015 (UTC)<br />
<br />
::Perhaps add your comment to the main page? I use GNOME 3 BTW and knew that. I don't really see the point of getting the QHD+ display and just scaling most things up. It also is glossy instead of matte, chews more battery, and causes slightly more heat. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 13:53, 1 June 2015 (UTC)<br />
<br />
:::Done. I agree with your points; that's exactly why I got the FHD model myself. The only configuration I had to do was increase the text scaling in Gnome to 1.25. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 06:45, 2 June 2015 (UTC)<br />
<br />
== Intel wifi option? ==<br />
<br />
The page says:<br />
<br />
"The Intel module has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so."<br />
<br />
I guess replacing the factory Broadcom card would void the warranty though? Is opening the case and replacing the card difficult? Perhaps comments about these could be added.<br />
<br />
BTW. I am about to get a i5+8GB+256GB+broadcom wifi+FHD model delivered and will clobber the windows install with Arch. Hence my interest in this wiki page. I will contribute feedback when I do the install.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 04:36, 3 June 2015 (UTC)<br />
<br />
:As far as I know, if you replace the WiFi card, the rest of the laptop is still covered by the warranty. Dell is pretty good about user-serviceability; they even provide [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop/xps-13-9343-laptop_Service%20Manual_en-us.pdf the service manual] (PDF) for free. They will not, however, cover any damage that you may cause while working inside your laptop. It's quite easy to replace the WiFi card, but you do need a Torx T5 screwdriver and a plastic spudger to remove the bottom half of the case, and most people don't have those lying around. As for including instructions in the wiki, disassembling the laptop has no relevance to its support in Arch, so I don't think that would belong here. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:06, 3 June 2015 (UTC)<br />
:For the technical part of swapping things out [[User:Soren121|Soren121]] has got you covered pretty well already. Even if you have those tools though (I did the modification and am in fact the person that put up the information on the page, so yes, I had the tools ready), getting the bottom off can be a bit troublesome to say the least. For some parts you do have to apply a bit more force than you would think is good for the device, but don't worry, it's pretty sturdy and can handle it should you ever decide to go through with the modification. Once the bottom is removed its a matter of removing the single screw that holds the WiFi card in place, unplugging the two antenna-wires from the module, followed by, obviously, putting the new module in place and reversing the steps. The antenna wires are color-coded, and so are the replacement WiFi modules, so you should have no problem matching the antenna wires. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:11, 30 June 2015 (UTC)<br />
<br />
== VirtualBox freezing workaround ==<br />
<br />
I just added a edit to provide a solution for the Broadwell related VirtualBox Virtual Machine startup freezing issues. However I'm not entirely sure if I placed this tip too well... while it does affect the Dell XPS 13 (as it obviously is a Broadwell based device), this issue does span over multiple device making me believe it might be better placed in the VirtualBox page than this one.<br />
<br />
So, what do you guys think? Place it on the VirtualBox page or leave it here?<br />
<br />
If we do move it to the VirtualBox page, should a reference link remain on the Dell XPS 13 (2015) page or should we treat this the same way we did the PulseAudio flat volumes issue? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 08:26, 7 July 2015 (UTC)<br />
<br />
: I vote to move it to the VirtualBox page and remove it from this page. First off, VirtualBox is not a commonly-installed system service or application. You could reasonably expect most Linux desktop users to have Pulse installed (unless they're still scared of it), but not so with VirtualBox. Second, like you said, it affects all Broadwell machines, so it shouldn't just be kept here if at all. For example, originally I had only listed the Broadwell TTY switching bug here on this page. Later on, I noticed in the forums that people with the X1 Carbon, among other machines, were linking to this page for help. I moved that section to [[Intel graphics]] after that, because I realized they shouldn't have to hunt down the page for a device they don't have just to get help. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 16:22, 7 July 2015 (UTC)<br />
<br />
:: The Intel bug was fixed from April, we're July now, so it can be safely deleted. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:47, 7 July 2015 (UTC)<br />
<br />
::: True. My concern was that a lot of people using other distros reference the XPS 13 wiki page here, because it's one of the more complete XPS 13 Linux help pages available. The bug was fixed upstream but they still haven't released an update with it yet. I know Ubuntu and Arch backported the patch but many others haven't. Personally, I would prefer to wait and remove it when upstream releases that update. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:55, 7 July 2015 (UTC)<br />
<br />
:: I've moved the VirtualBox freeze troubleshooting section to the VirtualBox page now. Everything's clean and nice on the XPS 13 page again. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 05:10, 9 July 2015 (UTC)<br />
<br />
== Powersaving ==<br />
<br />
Since kernel 4.1.2-2 is now in the stable repositories, can the proposed kernel parameters in the Powersaving section be used without the linux-mainline kernel? The section doesn't say which exact changes or patches in the kernel are needed to make this work. I would just try it out but I am unsure how to confirm if it is actually working.<br />
<br />
[[User:FlorianH|FlorianH]] ([[User talk:FlorianH|talk]]) 11:37, 16 July 2015 (UTC)<br />
<br />
:It should work fine with the standard 4.1 Arch kernel. The linux-mainline package doesn't include any extra patches. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:16, 23 July 2015 (UTC)<br />
<br />
I had fairly frequent freezes which went away when I got rid of i915.enable_fbc=1. Is this just my system or is it worth mentioning?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:56, 30 July 2015 (UTC)<br />
<br />
:It's not just you. I had to remove that option as well as the screen would flicker like crazy if I didn't. I guess it might be worthwhile mentioning on the page. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 12:11, 30 July 2015 (UTC)<br />
<br />
:It seems that the flicker we experience with the i915.enable_fbc=1 isn't actually a bug but rather an issue with the DVMT pre-allocated memory for the GPU. I've captured an error message in dmesg right after a flicker occured stating that this is the most likely issue. Sadly, our BIOS doesn't allow the configuration of the DVMT pre-allocated memory size, so we are stuck with the 64MB it preallocates by default. I did however find a tutorial on the x86 hackintosh community forums on how to manually change the BIOS saved settings for DVMT on the Dell XPS 13 9343 using the EFI shell (see here: http://www.tonymacx86.com/yosemite-laptop-support/162062-guide-intel-hd-graphics-5500-os-x-yosemite-10-10-3-a.html). I assume that if we changed this value to an higher setting, then the Framebuffer compression algorithm wouldn't run out of memory while doing its job anymore, avoiding the flicker entirely. Someone care to try this? I can't quite afford messing (up) with my setup over the week as I use my XPS 13 as my actual work machine. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:30, 3 August 2015 (UTC)<br />
<br />
::No-one else seems to be keen on low-level EFI-hacking. DVMT is meant to be *dynamic*. Rather than a problem with the pre-allocated memory, couldn't it be a problem with the pre-allocated/dynamically-allocated ratio chosen by the driver? [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:43, 12 August 2015 (UTC)<br />
<br />
A note says that "Enabling PSR support ... will further reduce idle power usage to ~2.6 W ..."; we should provide the '''basic''' power usage, prior to enabling this feature, so a user can ''evaluate'' if use it or not... should result in: "this feature allow you to reduce power usage from X to Y watts"; unfortunately now I can't do it on my own<br />
<br />
--[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 08:41, 20 August 2015 (UTC)<br />
<br />
== NetworkManager ==<br />
<br />
The sentence in [[Dell_XPS_13_(2015)#Connection_issues_with_Broadcom_wireless]]:<br />
:"If your WiFi connection drops constantly, try disabling NetworkManager (if you have it installed) and fall back to using wifi-menu."<br />
makes no sense as NetworkManager and netctl both use [[wpa_supplicant]] to negotiate a wireless connection. Unless someone can make an exact relation between NetworkManager and this hardware, this sentence should be removed. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 06:13, 3 September 2015 (UTC)<br />
:: Removed. If anyone has an objection, feel free to discuss. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:12, 30 September 2015 (UTC)<br />
<br />
== LCD backlight ==<br />
<br />
I'm experiencing problems where the backlights turn on again one second after I run '''xset dpms force off'''. However, I do not feel confident enough that this is a hardware problem to bring this up as an issue in the article. Can anybody replicate or tell me that I'm doing it wrong?<br />
[[User:Aron|Aron]] ([[User talk:Aron|talk]]) 15:01, 17 September 2015 (UTC)<br />
<br />
== The render ring hang report ==<br />
<br />
This section has no sources and the problem it describes is not reproducible. I haven't been able to find bug reports on the Mesa or kernel trackers that matches the description, nor have I experienced such an issue on my own XPS 13 with the latest Mesa drivers. Unless someone is able to provide a source/proof of the issue, I'd like to propose that we remove this section. Without knowing what the problem is, we won't know if the issue has been resolved (or if it even was an issue in the first place!) [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 05:03, 30 September 2015 (UTC)<br />
<br />
:Sounds like a good idea; also, the version of Mesa mentioned in the section is almost 3 months old at this point and there have been a fair few bug-fix releases since then. [[User:Bryn|Bryn]] ([[User talk:Bryn|talk]]) 22:45, 1 October 2015 (UTC)<br />
<br />
:: Also an excellent point. I'll remove it in a few days if no one raises an objection. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 22:52, 1 October 2015 (UTC)<br />
<br />
:: Removed. If you have an objection, again, feel free to discuss. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 03:43, 11 October 2015 (UTC)<br />
<br />
== Touchpad with palm detection ==<br />
<br />
I'd like to share with you a new configuration for touchpad pointed out by Barton George:<br />
http://bartongeorge.net/2015/09/30/alternate-touchpad-configuration-for-xps-9343-developer-edition-running-ubuntu-15-04/<br />
touchpad with palm detection using "libinput"<br />
I haven't tried it!<br />
<br />
--[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 10:31, 7 October 2015 (UTC)<br />
<br />
:The Touchpad section of this wiki page has had instructions for using libinput for months now! :) And yes, it does work. The only drawback is that it is less configurable than the synaptics driver. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:00, 7 October 2015 (UTC)<br />
<br />
:: Yes, I read it! I noticed a quiet different .conf file and this is a reason why I posted the link. --[[User:NTia89|nTia89]] ([[User talk:NTia89|talk]]) 13:15, 8 October 2015 (UTC)<br />
<br />
== Audio issues with Realtek ALC3263 ==<br />
I've experienced severe audio problems using 4.2.3-1 (and at least 4.2.2) and BIOS updated to A05. Sound worked for some undefined period of time and then speakers (or headphones) started producing crackling sounds and eventually sound became very distorted. dmesg output when this started:<br />
<br />
snd_hda_intel IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
...<br />
snd_hda_intel 0000:00:1b.0: spurious response 0x0:0x0, last cmd=0x1470700<br />
<br />
IRQ timing line showed up shortly after sound device was used and spurious response lines showed up when crackling started. This was clearly a driver problem and I tested different snd_hda_intel options, with no good results. Eventually I decided to enable more verbose debugging for sound devices and I built a custom kernel using current rc with arch default config (4.3.0-rc5-ARCH). When I booted into it I never experienced sound issues again. --[[User:Lknix|Lknix]] ([[User talk:Lknix|talk]]) 19:54, 13 October 2015 (UTC)<br />
<br />
== Call for testing ==<br />
I managed to find an Arch specific issue: https://bugzilla.kernel.org/show_bug.cgi?id=105251#c9<br />
Can you please download the Arch Live CD from https://www.archlinux.org/download/, flash it to an usb drive using dd, then boot it using EFI at least 20 times (the crash is much more difficult to reproduce with the live CD) and write about it? If you cannot manage to reproduce it within 20 boots you probably aren't being afflicted.<br />
<br />
afflicted (QHD+, Intel Wifi, i7-5600U)[[User:Darkbasic|darkbasic (http&#58;//www.linuxsystems.it/)]] ([[User talk:Darkbasic|talk]]) 14:52, 12 October 2015 (UTC)<br />
<br />
== Late 2015 model with Skylake CPU ==<br />
<br />
At beginning of October Dell refreshed the XPS line with skylake CPU. Firstly, should the wiki page/information on the previous model should be re-named to Early 2015? Secondly, anyone bought and tested the latest model with Linux?</div>Alexjjhttps://wiki.archlinux.org/index.php?title=User:Adamlau/HandBrakeCLI&diff=402503User:Adamlau/HandBrakeCLI2015-10-01T04:09:22Z<p>Alexjj: added link to handbrake's own wiki which details the usage of the tool</p>
<hr />
<div>[[Category:Multimedia]]<br />
[http://handbrake.fr/ HandBrakeCLI] is command-line driven interface to a collection of built-in libraries which enables the decoding, encoding and conversion of audio and video streams to [[Wikipedia:MPEG-4_Part_14|MP4]] (M4V) and [[Wikipedia:Matroska|MKV]] container formats with an emphasis on [[Wikipedia:H.264/MPEG-4_AVC|H.264/MPEG-4 AVC]] encoding through [http://www.videolan.org/developers/x264.html x264].<br />
<br />
== Package installation ==<br />
[[pacman|Install]] {{Pkg|handbrake-cli}} from the [[Official repositories]].<br />
<br />
== Encoding examples ==<br />
{{Accuracy|Single-pass and Two-pass sections are the same?}}<br />
<br />
=== Single-pass x264 (very high-quality) ===<br />
{{bc|1=<br />
HandBrakeCLI -i X-Men.First.Class.2011.vob -o X-Men.First.Class.2011.mkv -E lame -B 160k -6 stereo -R 48000 -e x264 -x b_adapt=2:bframes=8:direct=auto:fast_pskip=0:deblock=-1,-1:psy-rd=1,0.15:me=umh:me_range=24:partitions=all:ref=16:subq=10:trellis=2:rc_lookahead=60:frameref=15:threads=auto -s1 -S 2250 -2 -v2<br />
}}<br />
<br />
=== Two-pass x264 (very high-quality) ===<br />
{{bc|1=<br />
HandBrakeCLI -i X-Men.First.Class.2011.vob -o X-Men.First.Class.2011.mkv -E lame -B 160k -6 stereo -R 48000 -e x264 -x b_adapt=2:bframes=8:direct=auto:fast_pskip=0:deblock=-1,-1:psy-rd=1,0.15:me=umh:me_range=24:partitions=all:ref=16:subq=10:trellis=2:rc_lookahead=60:frameref=15:threads=auto -s1 -S 2250 -2 -v2<br />
}}<br />
<br />
ULTRAFAST TESTING<br />
<br />
{{bc|1=<br />
HandBrakeCLI -i Hostel.II.vob -o Hostel.II.mkv -E lame -B 128k -6 dpl2 -R 48000 -e x264 -x ref=1:bframes=0:cabac=0:8x8dct=0:weightp=0:me=dia:subq=0:rc-lookahead=0:mbtree=0:analyse=none:trellis=0:aq-mode=0:scenecut=0:no-deblock=1:threads=auto -s1 -S 750 -v<br />
}}<br />
<br />
== Adding subtitles ==<br />
{{Expansion|TODO.}}<br />
<br />
== See also ==<br />
<br />
* [https://trac.handbrake.fr/wiki/CLIGuide Official CLI Guide]</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:Apple_Keyboard&diff=278640Talk:Apple Keyboard2013-10-14T07:53:40Z<p>Alexjj: added a question as the wiki entry does not work for me</p>
<hr />
<div>I've put echo 2 > /sys/module/hid_apple/parameters/fnmode in a modprobe conf but it complains about the line starting with echo...any suggestiongs?</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Raspberry_Pi&diff=276514Raspberry Pi2013-09-24T12:22:41Z<p>Alexjj: Added raspberry pi camera setup info</p>
<hr />
<div>[[Category:Getting and installing Arch]]<br />
[[cs:Raspberry Pi]]<br />
[[ru:Raspberry Pi]]<br />
{{Article summary start}}<br />
{{Article summary text|Raspberry Pi (RPi) is a minimalist computer built for the [[Wikipedia:ARMv6|ARMv6 architecture]]. [http://www.raspberrypi.org/ More information about this project] and [http://uk.farnell.com/raspberry-pi technical specification].}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Beginners' Guide}}<br />
<br />
[http://elinux.org/RPiconfig RPi Config] - Excellent source of info relating to under-the-hood tweaks.<br />
<br />
[http://elinux.org/RPI_vcgencmd_usage RPi vcgencmd usage] - Overview of firmware command vcgencmd.<br />
{{Article summary end}}<br />
<br />
== Article Preface ==<br />
This article is not meant to be an exhaustive setup guide and assumes that the reader has setup an Arch system before. Arch newbies are encouraged to read the [[Beginners' Guide]] if unsure how to preform standard tasks such as creating users, managing the system, etc.<br />
<br />
{{Note|Support for the ARM architecture is provided on http://archlinuxarm.org not through posts to the official Arch Linux Forum. Any posts related to ARM specific issues will be promptly closed per the [https://wiki.archlinux.org/index.php/Forum_Etiquette#Arch_Linux_Distribution_Support_ONLY Arch Linux Distribution Support ONLY] policy.}}<br />
<br />
== Installing Arch Linux ARM ==<br />
<br />
See the [http://archlinuxarm.org/platforms/armv6/raspberry-pi#qt-platform_tabs-ui-tabs2 archlinuxarm documentation].<br />
<br />
== Audio ==<br />
{{Note| The requisite module '''snd-bcm2835''' should be autoloaded by default.}}<br />
<br />
Install the needed packages:<br />
pacman -S alsa-utils alsa-firmware alsa-lib alsa-plugins<br />
<br />
Optionally adjust the default volume using `alsamixer` and ensure that the sole source "PCM" is not muted (denoted by double MM if muted).<br />
<br />
Select an audio source for output:<br />
amixer cset numid=3 x<br />
<br />
Where 'x' corresponds to:<br />
*0 for Auto<br />
*1 for Analog out<br />
*3 for HDMI<br />
<br />
=== Caveats for HDMI Audio ===<br />
Some applications require a setting in {{ic|/boot/config.txt}} to force audio over HDMI:<br />
hdmi_drive=2<br />
<br />
== Onboard Hardware Sensors ==<br />
=== Temperature ===<br />
Temperatures sensors for the board itself are including as part of the '''raspberrypi-firmware-tools''' package. The RPi offers a sensor on the BCM2835 SoC (CPU/GPU):<br />
<br />
/opt/vc/bin/vcgencmd measure_temp<br />
temp=49.8'C<br />
<br />
Alternatively, simply read from the filesystem:<br />
% cat /sys/class/thermal/thermal_zone0/temp <br />
49768<br />
<br />
=== Voltage ===<br />
Four different voltages can be monitored via {{ic|/opt/vc/bin/vcgencmd}} as well:<br />
<br />
% /opt/vc/bin/vcgencmd measure_volts <id><br />
<br />
*core for core voltage<br />
*sdram_c for sdram Core voltage<br />
*sdram_i for sdram I/O voltage<br />
*sdram_p for sdram PHY voltage<br />
<br />
=== Lightweight Monitoring Suite ===<br />
{{AUR|Monitorix}} has specific support for the RPi since v3.2.0. Screenshots available [[http://www.monitorix.org/screenshots.html here]].<br />
<br />
== Overclocking/Underclocking ==<br />
The RPi can be overclocked by editing {{ic|/boot/config.txt}}, for example:<br />
<br />
arm_freq=800<br />
arm_freq_min=100<br />
core_freq=300<br />
core_freq_min=75<br />
sdram_freq=400<br />
over_voltage=0<br />
<br />
The optional xxx_min lines define the min usage of their respective settings. When the system is not under load, the values will drop down to those specified. Consult the [http://elinux.org/RPiconfig#Overclocking Overclocking] article on elinux for additional options and examples.<br />
<br />
A reboot is needed for new settings to take effect.<br />
<br />
{{Note|The overclocked setting for CPU clock applies only when the governor throttles up the CPU, i.e. under load.}}<br />
<br />
Users may query the current frequency of the CPU via this command:<br />
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq<br />
<br />
== Serial Console ==<br />
Edit the default /boot/cmdline.txt<br />
<br />
Change loglevel to 5 to see boot messages<br />
loglevel=5<br />
<br />
Change speed from 115200 to 38400<br />
console=ttyAMA0,38400 kgdboc=ttyAMA0,38400<br />
<br />
Start getty service<br />
systemctl start getty@ttyAMA0<br />
<br />
Enable on boot<br />
systemctl enable getty@ttyAMA0.service<br />
<br />
Creating the proper service link:<br />
ln -s /usr/lib/systemd/system/serial-getty@.service /etc/systemd/system/getty.target.wants/serial-getty@ttyAMA0.service<br />
<br />
Then connect :)<br />
screen /dev/ttyUSB0 38400<br />
<br />
== Video ==<br />
pacman -S xf86-video-fbdev<br />
<br />
Adjustments are likely required to correct proper overscan/underscan and are easily achieved in {{ic|boot/config.txt}} in which many tweaks are set. To fix, simply uncomment the corresponding lines and setup per the commented instructions:<br />
<br />
# uncomment the following to adjust overscan. Use positive numbers if console<br />
# goes off screen, and negative if there is too much border<br />
#overscan_left=16<br />
overscan_right=8<br />
overscan_top=-16<br />
overscan_bottom=-16<br />
<br />
Users wishing to use the analog video out should consult [https://raw.github.com/Evilpaul/RPi-config/master/config.txt this] config file which contains options for non-NTSC outputs.<br />
<br />
A reboot is needed for new settings to take effect.<br />
<br />
== Raspberry Pi Camera module ==<br />
The commands for the camera module are including as part of the '''raspberrypi-firmware-tools''' package - which is installed by default. You can then use:<br />
/opt/vc/bin/raspistill<br />
/opt/vc/bin/raspivid<br />
<br />
You need to append to /boot/config.txt:<br />
<br />
start_file=start_x.elf<br />
fixup_file=fixup_x.dat<br />
<br />
Optionally<br />
disable_camera_led=1</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:MATE&diff=252105Talk:MATE2013-03-27T16:03:49Z<p>Alexjj: /* MATE conflicts */</p>
<hr />
<div>==Notice: cleaning GNOME related articles==<br />
Hello MATE community,<br />
<br />
Some preparation is ongoing to clean up the GNOME related articles in our WiKi, specifically these two:<br />
<br />
:https://wiki.archlinux.org/index.php/Gnome<br />
:https://wiki.archlinux.org/index.php/Gnome_Tips<br />
<br />
Part of this cleaning effort will be to remove all outdated (GNOME 2.xx related) information in order to keep both these articles current and relevant. It has been pointed out to me that some of this information may be of value to the MATE community.<br />
<br />
I'm hereby asking if anybody here might be willing to look over both articles and see if anything is of value to the MATE articles, I wouldn't want to drop information that might help you out or be useful.--[[User:Stefanwilkens|stefanwilkens]] 13:10, 20 January 2012 (EST)<br />
<br />
==Starting MATE==<br />
Needs more information here from others, I only use gdm-old so I have no idea how mate-display-manager or plain old gdm behaves. -- [[User:Tea|Tea]] 15:00, 24 August 2011<br />
<br />
<br />
==MATE conflicts==<br />
<br />
What are these statements saying:<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
The first line says you get conflicts. The second line (the Note) says many MATE packages do NOT conflict. Which is it? -- [[User:alexjj|alexjj]] 16:00, 27 March 2013</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:MATE&diff=252104Talk:MATE2013-03-27T16:03:35Z<p>Alexjj: </p>
<hr />
<div>==Notice: cleaning GNOME related articles==<br />
Hello MATE community,<br />
<br />
Some preparation is ongoing to clean up the GNOME related articles in our WiKi, specifically these two:<br />
<br />
:https://wiki.archlinux.org/index.php/Gnome<br />
:https://wiki.archlinux.org/index.php/Gnome_Tips<br />
<br />
Part of this cleaning effort will be to remove all outdated (GNOME 2.xx related) information in order to keep both these articles current and relevant. It has been pointed out to me that some of this information may be of value to the MATE community.<br />
<br />
I'm hereby asking if anybody here might be willing to look over both articles and see if anything is of value to the MATE articles, I wouldn't want to drop information that might help you out or be useful.--[[User:Stefanwilkens|stefanwilkens]] 13:10, 20 January 2012 (EST)<br />
<br />
==Starting MATE==<br />
Needs more information here from others, I only use gdm-old so I have no idea how mate-display-manager or plain old gdm behaves. -- [[User:Tea|Tea]] 15:00, 24 August 2011<br />
<br />
<br />
==MATE conflicts==<br />
<br />
What are these statements saying:<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
The first line says you get conflicts. The second line (the Note) says many MATE packages do NOT conflict. Which is it? -- -- [[User:alexjj|alexjj]] 16:00, 27 March 2013</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:MATE&diff=252103Talk:MATE2013-03-27T16:02:35Z<p>Alexjj: </p>
<hr />
<div>==Notice: cleaning GNOME related articles==<br />
Hello MATE community,<br />
<br />
Some preparation is ongoing to clean up the GNOME related articles in our WiKi, specifically these two:<br />
<br />
:https://wiki.archlinux.org/index.php/Gnome<br />
:https://wiki.archlinux.org/index.php/Gnome_Tips<br />
<br />
Part of this cleaning effort will be to remove all outdated (GNOME 2.xx related) information in order to keep both these articles current and relevant. It has been pointed out to me that some of this information may be of value to the MATE community.<br />
<br />
I'm hereby asking if anybody here might be willing to look over both articles and see if anything is of value to the MATE articles, I wouldn't want to drop information that might help you out or be useful.--[[User:Stefanwilkens|stefanwilkens]] 13:10, 20 January 2012 (EST)<br />
<br />
==Starting MATE==<br />
Needs more information here from others, I only use gdm-old so I have no idea how mate-display-manager or plain old gdm behaves. -- [[User:Tea|Tea]] 15:00, 24 August 2011<br />
<br />
<br />
==MATE conflicts==<br />
<br />
What are these statements saying:<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
The first line says you get conflicts. The second line (the Note) says many MATE packages do NOT conflict. Which is it?</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Talk:MATE&diff=252101Talk:MATE2013-03-27T16:01:18Z<p>Alexjj: </p>
<hr />
<div>==Notice: cleaning GNOME related articles==<br />
Hello MATE community,<br />
<br />
Some preparation is ongoing to clean up the GNOME related articles in our WiKi, specifically these two:<br />
<br />
:https://wiki.archlinux.org/index.php/Gnome<br />
:https://wiki.archlinux.org/index.php/Gnome_Tips<br />
<br />
Part of this cleaning effort will be to remove all outdated (GNOME 2.xx related) information in order to keep both these articles current and relevant. It has been pointed out to me that some of this information may be of value to the MATE community.<br />
<br />
I'm hereby asking if anybody here might be willing to look over both articles and see if anything is of value to the MATE articles, I wouldn't want to drop information that might help you out or be useful.--[[User:Stefanwilkens|stefanwilkens]] 13:10, 20 January 2012 (EST)<br />
<br />
==Starting MATE==<br />
Needs more information here from others, I only use gdm-old so I have no idea how mate-display-manager or plain old gdm behaves. -- [[User:Tea|Tea]] 15:00, 24 August 2011<br />
<br />
<br />
===MATE conflicts===<br />
<br />
What are these statements saying:<br />
<br />
You are very likely to get file conflicts when installing. Simply rename the offending files or install with the {{ic|--force}} flag. You will also require [[dbus]].<br />
{{note|Currently, many MATE packages do not provide, conflict with or replace any GNOME packages.}}<br />
<br />
The first line says you get conflicts. The second line (the Note) says many MATE packages do NOT conflict. Which is it?</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Picom&diff=251127Picom2013-03-18T14:12:01Z<p>Alexjj: /* Usage */</p>
<hr />
<div>[[Category:X Server]]<br />
[[Category:Eye candy]]<br />
{{Article summary start}}<br />
{{Article summary text|Introduces chjj's fork of xcompmgr (fork of fork indeed).}}<br />
{{Article summary end}}<br />
<br />
[https://github.com/chjj/compton Compton] is a fork of xcompmgr-dana by chjj, where xcompmgr-dana is a fork of xcompmgr by Dana. It is therefore, like xcompmgr, a standalone composite manager and can be used as a companion to lightweight [[Window Manager|window managers]] which don't do composition on themselves.<br />
<br />
This fork fixed many bugs, and is very usable by this time of writing.<br />
<br />
== Installation ==<br />
Install the {{AUR|compton-git}} package, available in the [[AUR]].<br />
<br />
== Usage ==<br />
To start manually, just run:<br />
$ compton<br />
<br />
To use fancy shadows, you can run<br />
$ compton -c<br />
Additionally, -C can be used to avoid shadows on panels and docks, and -G can be used to avoid shadows on drag-and-drop objects (you probably want this).<br />
<br />
If you want it started automatically, put this in [[xprofile]]:<br />
<br />
compton -cGb<br />
<br />
where -b means to daemonize after composite manager registered.<br />
<br />
An example of a more customised command:<br />
compton -cCGfF -o 0.38 -O 200 -I 200 -t 0.02 -l 0.02 -r 3.2 -D2 -m 0.88<br />
<br />
You can also put your configuration in a file {{ic|~/.config/compton.conf}} or {{ic|~/.compton.conf}}.<br />
<br />
A sample configuration file.<br />
<br />
{{hc|~/.compton.conf|2=<br />
# Shadow<br />
shadow = true; # Enabled client-side shadows on windows.<br />
no-dock-shadow = true; # Avoid drawing shadows on dock/panel windows.<br />
no-dnd-shadow = true; # Don't draw shadows on DND windows.<br />
clear-shadow = true; # Zero the part of the shadow's mask behind the window (experimental).<br />
shadow-radius = 7; # The blur radius for shadows. (default 12)<br />
shadow-offset-x = -7; # The left offset for shadows. (default -15)<br />
shadow-offset-y = -7; # The top offset for shadows. (default -15)<br />
# shadow-opacity = 0.7; # The translucency for shadows. (default .75)<br />
# shadow-red = 0.0; # Red color value of shadow. (0.0 - 1.0, defaults to 0)<br />
# shadow-green = 0.0; # Green color value of shadow. (0.0 - 1.0, defaults to 0)<br />
# shadow-blue = 0.0; # Blue color value of shadow. (0.0 - 1.0, defaults to 0)<br />
shadow-exclude = [ "n:e:Notification" ]; # Exclude conditions for shadows.<br />
# shadow-exclude = "n:e:Notification";<br />
shadow-ignore-shaped = true;<br />
<br />
# Opacity<br />
menu-opacity = 0.9; # The opacity for menus. (default 1.0)<br />
inactive-opacity = 0.9; # Opacity of inactive windows. (0.1 - 1.0)<br />
#frame-opacity = 0.8; # Opacity of window titlebars and borders. (0.1 - 1.0)<br />
inactive-opacity-override = true; # Inactive opacity set by 'inactive-opacity' overrides value of _NET_WM_OPACITY.<br />
<br />
# Fading<br />
fading = true; # Fade windows during opacity changes.<br />
# fade-delta = 30; # The time between steps in a fade in milliseconds. (default 10).<br />
fade-in-step = 0.03; # Opacity change between steps while fading in. (default 0.028).<br />
fade-out-step = 0.03; # Opacity change between steps while fading out. (default 0.03).<br />
# no-fading-openclose = true; # Fade windows in/out when opening/closing.<br />
<br />
# Other<br />
#inactive-dim = 0.5; # Dim inactive windows. (0.0 - 1.0, defaults to 0).<br />
mark-wmwin-focused = true; # Try to detect WM windows and mark them as active.<br />
mark-ovredir-focused = true;<br />
detect-rounded-corners = true;<br />
<br />
# Window type settings<br />
wintypes:<br />
{<br />
tooltip = { fade = true; shadow = false; opacity = 0.75; };<br />
};<br />
}}<br />
<br />
To run compton with config file:<br />
<br />
$ compton --config ~/.compton.conf<br />
<br />
To automatically start compton put following in any of your [[Startup files]]:<br />
<br />
compton --config ~/.compton.conf -b<br />
<br />
== Transparency ==<br />
Besides what is provided in xcompmgr, compton introduces two new auto-transparency options:<br />
<br />
-i opacity<br />
Specifies inactive window transparency. (0.1 - 1.0)<br />
-e opacity<br />
Specifies window frame transparency. (0.1 - 1.0)<br />
<br />
Try them out on your own.<br />
<br />
=== Problem with slock ===<br />
<br />
Note that inactive window transparency (-i option) will make all inactive window became transparent, and if you use {{Pkg|slock}} it may not be a good result. Try this in config file instead:<br />
<br />
inactive-dim = 0.2;<br />
<br />
This will work with slock better.<br />
<br />
== Multihead ==<br />
<br />
If you use a [[multihead]] configuration without Xinerama, which means you start a X server with more than one screen, then compton will start on only one screen by default. You can start on all screen by starting multiple compton on all screens with -d. For example, if you have 4 monitors then you can start compton by:<br />
<br />
seq 0 3 | xargs -l1 -I@ compton -b -d :0.@</div>Alexjjhttps://wiki.archlinux.org/index.php?title=Beginners%27_guide&diff=250948Beginners' guide2013-03-16T17:21:10Z<p>Alexjj: /* Wired */</p>
<hr />
<div><noinclude><br />
[[Category:Getting and installing Arch]]<br />
[[Category:About Arch]]<br />
[[da:Beginners' Guide/Installation]]<br />
[[es:Beginners' Guide/Installation]]<br />
[[hr:Beginners' Guide/Installation]]<br />
[[hu:Beginners' Guide/Installation]]<br />
[[it:Beginners' Guide/Installation]]<br />
[[ja:Beginners' Guide/Installation]]<br />
[[ko:Beginners' Guide/Installation]]<br />
[[nl:Beginners' Guide/Installatie]]<br />
[[pl:Beginners' Guide/Installation]]<br />
[[pt:Beginners' Guide/Installation]]<br />
[[ro:Ghidul începătorilor/Instalare]]<br />
[[ru:Beginners' Guide/Installation]]<br />
[[sr:Beginners' Guide/Installation]]<br />
[[zh-CN:Beginners' Guide/Installation]]<br />
[[zh-TW:Beginners' Guide/Installation]]<br />
{{Tip|This is part of a multi-page article for The Beginners' Guide. '''[[Beginners' Guide|Click here]]''' if you would rather read the guide in its entirety.}}<br />
</noinclude><br />
== Installation ==<br />
<br />
You are now presented with a shell prompt, automatically logged in as root.<br />
<br />
=== Change the language ===<br />
<br />
{{Tip|These are optional for the majority of users. Useful only if you plan on writing in your own language in any of the configuration files, if you use diacritical marks in the Wi-Fi password, or if you would like to receive system messages (e.g. possible errors) in your own language.}}<br />
<br />
By default, the keyboard layout is set to {{ic|us}}. If you have a non-[[Wikipedia:File:KB United States-NoAltGr.svg|US]] keyboard layout, run:<br />
<br />
# loadkeys ''layout''<br />
<br />
...where ''layout'' can be {{ic|fr}}, {{ic|uk}}, {{ic|be-latin1}}, etc. See [[KEYMAP#Keyboard layouts|here]] for a comprehensive list.<br />
<br />
The font should also be changed, because most languages use more glyphs than the 26 letter [[Wikipedia:English alphabet|English alphabet]]. Otherwise some foreign characters may show up as white squares or as other symbols. Note that the name is case-sensitive, so please type it ''exactly'' as you see it:<br />
<br />
# setfont Lat2-Terminus16<br />
<br />
By default, the language is set to English (US). If you would like to change the language for the install process ''(German, in this example)'', remove the {{ic|#}} in front of the [http://www.greendesktiny.com/support/knowledgebase_detail.php?ref=EUH-483 locale] you want from {{ic|/etc/locale.gen}}, along with English (US). Please choose the {{ic|UTF-8}} entry.<br />
<br />
Use {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.<br />
<br />
{{hc|# nano /etc/locale.gen|<br />
en_US.UTF-8 UTF-8<br />
de_DE.UTF-8 UTF-8}}<br />
<br />
# locale-gen<br />
# export LANG=de_DE.UTF-8<br />
<br />
Remember, {{Keypress|LAlt+LShift}} activates and deactivates the keymap.<br />
<br />
=== Establish an internet connection ===<br />
<br />
{{Warning|udev no longer assigns network interface names according to the wlanX and ethX naming scheme. If you're coming from a different distribution or are reinstalling Arch and not aware of the new interface naming style, please do not assume that your wireless interface is named wlan0, or that your wired interface is named eth0. You can use the "ip" utility to discover the names of your interfaces.}}<br />
<br />
From systemd-197's release and onward, udev now assigns predictable, stable network interface names that deviate from the legacy incremental naming scheme (wlan0, wlan1, etc.). These interface names are guaranteed to be persistent across reboots, which solves the problem of the lack of predictability of network interface name assignment. For more information about why this was necessary, read http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames .<br />
<br />
The {{ic|dhcpcd}} network daemon is started automatically at boot and it will attempt to start a wired connection, if available. Try pinging a website to see if it was successful. And since Google is always on...<br />
<br />
{{hc|# ping -c 3 www.google.com|2=<br />
PING www.l.google.com (74.125.132.105) 56(84) bytes of data.<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=1 ttl=50 time=17.0 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=2 ttl=50 time=18.2 ms<br />
64 bytes from wb-in-f105.1e100.net (74.125.132.105): icmp_req=3 ttl=50 time=16.6 ms<br />
<br />
--- www.l.google.com ping statistics ---<br />
3 packets transmitted, 3 received, 0% packet loss, time 2003ms<br />
rtt min/avg/max/mdev = 16.660/17.320/18.254/0.678 ms}}<br />
<br />
If you get a {{ic|ping: unknown host}} error, first check if there is any problem with your cable (or if you have enough wireless signal), otherwise you will need to set up the network manually, as explained below.<br />
<br />
Otherwise, move on to [[#Prepare the storage drive|Prepare the storage drive]].<br />
<br />
==== Wired ====<br />
<br />
Follow this procedure if you need to set up a wired connection via a static IP address.<br />
<br />
First, identify the name of your ethernet interface. <br />
<br />
{{hc|# ip link|<br />
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT <br />
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br />
2: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000<br />
link/ether 00:11:25:31:69:20 brd ff:ff:ff:ff:ff:ff<br />
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000<br />
link/ether 01:02:03:04:05:06 brd ff:ff:ff:ff:ff:ff}}<br />
<br />
In this case, the ethernet interface is enp2s0f0. If you're unsure, your ethernet interface is likely to start with the letter "e", and unlikely to be "lo" or start with the letter "w". You can also use iwconfig and see which interfaces are not wireless:<br />
<br />
{{hc|# iwconfig|2=<br />
enp2s0f0 no wireless extensions.<br />
wlp3s0 IEEE 802.11bgn ESSID:"NETGEAR97" <br />
Mode:Managed Frequency:2.427 GHz Access Point: 2C:B0:5D:9C:72:BF <br />
Bit Rate=65 Mb/s Tx-Power=16 dBm <br />
Retry long limit:7 RTS thr:off Fragment thr:off<br />
Power Management:on<br />
Link Quality=61/70 Signal level=-49 dBm <br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:430 Missed beacon:0<br />
lo no wireless extensions.}}<br />
<br />
In this example, neither enp2s0f0 nor the loopback device have wireless extensions, meaning enp2s0f0 is our ethernet interface.<br />
<br />
You also need to know these settings:<br />
<br />
* Static IP address.<br />
* Subnet mask.<br />
* Gateway's IP address.<br />
* Name servers' (DNS) IP addresses.<br />
* Domain name (unless you're on a local LAN, in which case you can make it up).<br />
<br />
Activate the connected Ethernet interface (e.g. {{ic|enp2s0f0}}):<br />
<br />
# ip link set enp2s0f0 up<br />
<br />
Add the address:<br />
<br />
# ip addr add <ip address>/<subnetmask> dev <interface><br />
<br />
For example:<br />
<br />
# ip addr add 192.168.1.2/24 dev enp2s0f0<br />
<br />
For more options, run {{ic|man ip}}.<br />
<br />
Add your gateway like this, substituting your own gateway's IP address:<br />
<br />
# ip route add default via <ip address><br />
<br />
For example:<br />
<br />
# ip route add default via 192.168.1.1<br />
<br />
Edit {{ic|resolv.conf}}, substituting your name servers' IP addresses and your local domain name:<br />
<br />
{{hc|# nano /etc/resolv.conf|<br />
nameserver 61.23.173.5<br />
nameserver 61.95.849.8<br />
search example.com}}<br />
<br />
{{Note|Currently, you may include a maximum of 3 {{ic|nameserver}} lines.}}<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Network Configuration]] page.<br />
<br />
==== Wireless ====<br />
<br />
Follow this procedure if you need wireless connectivity (Wi-Fi) during the installation process.<br />
<br />
If you're coming from another distribution, or if this is your first time installing Arch Linux since the deprecation of the old interface naming scheme, you might be surprised to learn that the first wireless interface is not named "wlan0". In fact, none of the interfaces are automatically prefixed with "wlan" any longer. Don't panic; simply execute {{ic|iwconfig}} to discover the name of your wireless interface.<br />
<br />
The wireless drivers and utilities are now available to you in the live environment of the installation media. A good knowledge of your wireless hardware will be of key importance to successful configuration. Note that the following quick-start procedure ''executed at this point in the installation'' will initialize your wireless hardware for use ''in the live environment of the installation media''. These steps (or some other form of wireless management) '''must be repeated from the actual installed system after booting into it'''.<br />
<br />
Also note that these steps are optional if wireless connectivity is unnecessary at this point in the installation; wireless functionality may always be established later.<br />
<br />
{{Note|The following examples use {{ic|wlp3s0}} for the interface and {{ic|linksys}} for the ESSID. Remember to change these values according to your setup.}}<br />
<br />
The basic procedure will be:<br />
<br />
* Identify the wireless interface:<br />
<br />
# lspci | grep -i net<br />
<br />
Or, if using a USB adapter:<br />
<br />
# lsusb<br />
<br />
* Ensure udev has loaded the driver, and that the driver has created a usable wireless kernel interface with {{ic|iwconfig}}:<br />
<br />
{{Note|If you do not see output similar to this, then your wireless driver has not been loaded. If this is the case, you must load the driver yourself. Please see [[Wireless Setup]] for more detailed information.}}<br />
<br />
{{hc|# iwconfig|2=<br />
enp2s0f0 no wireless extensions.<br />
wlp3s0 IEEE 802.11bgn ESSID:"NETGEAR97" <br />
Mode:Managed Frequency:2.427 GHz Access Point: 2C:B0:5D:9C:72:BF <br />
Bit Rate=65 Mb/s Tx-Power=16 dBm <br />
Retry long limit:7 RTS thr:off Fragment thr:off<br />
Power Management:on<br />
Link Quality=61/70 Signal level=-49 dBm <br />
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0<br />
Tx excessive retries:0 Invalid misc:430 Missed beacon:0<br />
lo no wireless extensions.}}<br />
<br />
In this example, {{ic|wlp3s0}} is the available wireless interface.<br />
<br />
* Bring the interface up with:<br />
<br />
# ip link set wlp3s0 up<br />
<br />
A small percentage of wireless chipsets also require firmware, in addition to a corresponding driver. If the wireless chipset requires firmware, you are likely to receive this error when bringing the interface up:<br />
<br />
{{hc|# ip link set wlp3s0 up|<br />
SIOCSIFFLAGS: No such file or directory}}<br />
<br />
If unsure, invoke {{ic|dmesg}} to query the kernel log for a firmware request from the wireless chipset.<br />
<br />
Example output from an Intel chipset which requires and has requested firmware from the kernel at boot:<br />
<br />
{{hc|# dmesg <nowiki>|</nowiki> grep firmware|<br />
firmware: requesting iwlwifi-5000-1.ucode}}<br />
<br />
If there is no output, it may be concluded that the system's wireless chipset does not require firmware.<br />
<br />
{{Warning|Wireless chipset firmware packages (for cards which require them) are pre-installed under {{ic|/usr/lib/firmware}} in the live environment (on CD/USB stick) '''but must be explicitly installed to your actual system to provide wireless functionality after you reboot into it!''' Package installation is covered later in this guide. Ensure installation of both your wireless module and firmware before rebooting! See [[Wireless Setup]] if you are unsure about the requirement of corresponding firmware installation for your particular chipset. }}<br />
<br />
Next, use {{Pkg|netcfg}}'s {{ic|wifi-menu}} to connect to a network. Replace ''wlp3s0" with the name of your interface:<br />
<br />
# wifi-menu wlp3s0<br />
<br />
{{Warning|At the moment, netcfg's wifi-menu, when executed without arguments, will look for "wlan0". Execute wifi-menu with your interface as the argument in order to use it. See [[Network Configuration#Get_current_device_names]]}}<br />
<br />
You should now have a working network connection. If you do not, check the detailed [[Wireless Setup]] page.<br />
<br />
==== xDSL (PPPoE), analog modem or ISDN ====<br />
<br />
If you have a router in bridge mode, run:<br />
<br />
# pppoe-setup<br />
<br />
* Type in the username that the ISP provided you with.<br />
* Press {{Keypress|Enter}} for "eth0".<br />
* Press {{Keypress|Enter}} for "no", so that it stays up continuously.<br />
* Type {{ic|server}} (since this is usually the case).<br />
* Press {{Keypress|1}} for a firewall.<br />
* Type in the password that the ISP provided you with.<br />
* Press {{Keypress|Y}} at the end.<br />
<br />
To use these settings and connect to your ISP, run:<br />
<br />
# pppoe-start<br />
<br />
You may also need to adjust your {{ic|resolv.conf}}:<br />
<br />
# echo nameserver 8.8.8.8 > /etc/resolv.conf<br />
<br />
If you have a dial-up or ISDN connection, see [[Direct Modem Connection]].<br />
<br />
==== Behind a proxy server ====<br />
<br />
If you are behind a proxy server, you will need to export the {{ic|http_proxy}} and {{ic|ftp_proxy}} environment variables. See [[Proxy settings]] for more information.<br />
<br />
=== Prepare the storage drive ===<br />
<br />
{{Warning|Partitioning can destroy data. You are '''strongly''' cautioned and advised to backup any critical data before proceeding.}}<br />
<br />
Absolute beginners are encouraged to use a graphical partitioning tool. [http://gparted.sourceforge.net/download.php GParted] is a good example, and is [http://gparted.sourceforge.net/livecd.php provided as a "live" CD]. It is also included on live CDs of most Linux distributions such as [[Wikipedia:Ubuntu (operating system)|Ubuntu]] and [[Wikipedia:Linux Mint|Linux Mint]]. A drive should first be [[partitioning|partitioned]] and the partitions should be formatted with a [[File Systems|file system]] before rebooting.<br />
<br />
See [[Swap]] for details if you wish to set up a swap partition or file now. A swap file is easier to resize than a partition and can be created at any point after installation, but cannot be used with a BTRFS filesystem.<br />
<br />
If you have already done so, proceed to [[#Mount the partitions|Mount the partitions]].<br />
<br />
Otherwise, see the following example.<br />
<br />
==== Example ====<br />
<br />
The Arch Linux install media includes the following partitioning tools: {{ic|fdisk}}, {{ic|gdisk}}, {{ic|cfdisk}}, {{ic|cgdisk}}, {{ic|parted}}.<br />
<br />
{{Box BLUE|Notes regarding [[UEFI]] boot:|<br />
* If you have a UEFI motherboard, you will need to create an extra [[Unified Extensible Firmware Interface#Create an UEFI System Partition in Linux|UEFI System Partition]].<br />
* It is recommended to always use GPT for UEFI boot, as some UEFI firmwares do not allow UEFI-MBR boot.}}<br />
<br />
{{Box BLUE|Notes regarding [[GPT]] partitioning:|<br />
* If you are not dual booting with Windows, then it is advisable to use GPT instead of MBR. Read [[GPT]] for a list of advantages.<br />
* If you have a BIOS motherboard (or plan on booting in BIOS compatibility mode) and you want to setup GRUB on a GPT-partitioned drive, you will need to create an extra [[GRUB2#GUID Partition Table (GPT) specific instructions|BIOS Boot Partition]]. Syslinux doesn't need one.<br />
* Some BIOS systems may have issues with GPT. See http://mjg59.dreamwidth.org/8035.html and http://rodsbooks.com/gdisk/bios.html for more info and possible workarounds.}}<br />
<br />
{{Note|If you are installing to a USB flash key, see [[Installing Arch Linux on a USB key]].}}<br />
<br />
The example system will contain a 15 GB root partition, and a [[Partitioning#/home|home]] partition for the remaining space. Choose either [[MBR]] or [[GPT]]. Do not choose both!<br />
<br />
It should be emphasized that partitioning is a personal choice and that this example is only for illustrative purposes. See [[Partitioning]].<br />
<br />
{| class="wikitable"<br />
|-<br />
| rowspan="2" | '''MBR'''<br />
| rowspan="2"| {{ic|cfdisk&nbsp;/dev/sda}}<br />
| '''Root:'''<br />
<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – type in "15360" – {{Keypress|Enter}} for Beginning – {{Keypress|Enter}} for Bootable.<br />
|-<br />
|<br />
'''Home:'''<br />
<br />
* Press the down arrow to move to the free space area.<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for Primary – {{Keypress|Enter}} to use the rest of the drive (or you could type in the desired size).<br />
|-<br />
| rowspan="2" | '''GPT'''<br />
| rowspan="2"| {{ic|cgdisk&nbsp;/dev/sda}}<br />
| '''Root:'''<br />
<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for the first sector (2048) – type in "15G" – {{Keypress|Enter}} for the default hex code (8300) – {{Keypress|Enter}} for a blank partition name.<br />
|-<br />
| '''Home:'''<br />
<br />
* Press the down arrow a couple of times to move to the larger free space area.<br />
* Choose New (or press {{Keypress|N}}) – {{Keypress|Enter}} for the first sector – {{Keypress|Enter}} to use the rest of the drive (or you could type in the desired size; for example "30G") – {{Keypress|Enter}} for the default hex code (8300) – {{Keypress|Enter}} for a blank partition name.<br />
|}<br />
<br />
If you chose MBR, here's how it should look like:<br />
<br />
Name Flags Part Type FS Type [Label] Size (MB)<br />
-----------------------------------------------------------------------<br />
sda1 Boot Primary Linux 15360<br />
sda2 Primary Linux 133000*<br />
<br />
If you chose GPT, here's how it should look like: <br />
<br />
Part. # Size Partition Type Partition Name<br />
----------------------------------------------------------------<br />
1007.0 KiB free space<br />
1 15.0 GiB Linux filesystem<br />
2 123.45 GiB Linux filesystem<br />
<br />
Double check and make sure that you are happy with the partition sizes as well as the partition table layout before continuing.<br />
<br />
If you would like to start over, you can simply select Quit (or press {{Keypress|Q}}) to exit without saving changes and then restart cfdisk (or cgdisk).<br />
<br />
If you are satisfied, choose Write (or press {{Keypress|Shift+W}}) to finalize and to write the partition table to the drive. Type "yes" and choose Quit (or press {{Keypress|Q}}) to exit without making any more changes.<br />
<br />
Simply partitioning is not enough; the partitions also need a [[File Systems|filesystem]]. To format the partitions with an ext4 filesystem:<br />
<br />
{{Warning|Double check and triple check that it's actually {{ic|/dev/sda1}} and {{ic|/dev/sda2}} that you want to format.}}<br />
<br />
# mkfs.ext4 /dev/sda1<br />
# mkfs.ext4 /dev/sda2<br />
<br />
If you have made a partition dedicated to swap (code 82), don't forget to format and activate it with:<br />
<br />
# mkswap /dev/sda''X''<br />
# swapon /dev/sda''X''<br />
<br />
=== Mount the partitions ===<br />
<br />
Each partition is identified with a number suffix. For example, {{ic|sda1}} specifies the first partition of the first drive, while {{ic|sda}} designates the entire drive.<br />
<br />
To display the current partition layout:<br />
<br />
# lsblk /dev/sda<br />
<br />
{{Note|Do not mount more than one partition to the same directory. And pay attention, because the mounting order is important.}}<br />
<br />
First, mount the root partition on {{ic|/mnt}}. Following the example when using {{ic|cfdisk}} above (yours may be different), it would be:<br />
<br />
# mount /dev/sda1 /mnt<br />
<br />
Then mount the home partition and any other separate partition ({{ic|/boot}}, {{ic|/var}}, etc), if you have any:<br />
<br />
# mkdir /mnt/home<br />
# mount /dev/sda2 /mnt/home<br />
<br />
In case you have a UEFI motherboard, mount the UEFI partition:<br />
<br />
# mkdir -p /mnt/boot/efi<br />
# mount /dev/sda''X'' /mnt/boot/efi<br />
<br />
=== Select a mirror ===<br />
<br />
Before installing, you may want to edit the {{ic|mirrorlist}} file and place your preferred mirror first. A copy of this file will be installed on your new system by {{ic|pacstrap}} as well, so it's worth getting it right.<br />
<br />
{{hc|# nano /etc/pacman.d/mirrorlist|<br />
##<br />
## Arch Linux repository mirrorlist<br />
## Sorted by mirror score from mirror status page<br />
## Generated on 2012-MM-DD<br />
##<br />
<br />
<nowiki>Server = http://mirror.example.xyz/archlinux/$repo/os/$arch</nowiki><br />
...}}<br />
<br />
* {{Keypress|Alt+6}} to copy a {{ic|Server}} line.<br />
* {{Keypress|PageUp}} key to scroll up.<br />
* {{Keypress|Ctrl+U}} to paste it at the top of the list.<br />
* {{Keypress|Ctrl+X}} to exit, and when prompted to save changes, press {{Keypress|Y}} and {{Keypress|Enter}} to use the same filename.<br />
<br />
If you want, you can make it the ''only'' mirror available by getting rid of everything else (using {{Keypress|Ctrl+K}}), but it's usually a good idea to have a few more, in case the first one goes offline.<br />
<br />
{{Tip|<br />
* Use the [https://www.archlinux.org/mirrorlist/ Mirrorlist Generator] to get an updated list for your country. HTTP mirrors are faster than FTP, because of something called [[Wikipedia:Keepalive|keepalive]]. With FTP, pacman has to send out a signal each time it downloads a package, resulting in a brief pause. For other ways to generate a mirror list, see [[Mirrors#Sorting mirrors|Sorting mirrors]] and [[Reflector]].<br />
* [https://archlinux.org/mirrors/status/ Arch Linux MirrorStatus] reports various aspects about the mirrors such as network problems with mirrors, data collection problems, the last time mirrors have been synced, etc.}}<br />
<br />
{{Note|<br />
* Whenever in the future you change your list of mirrors, always remember to force pacman to refresh all package lists with {{ic|pacman -Syy}}. This is considered to be good practice and will avoid possible headaches. See [[Mirrors]] for more information.<br />
* If you're using an older installation medium, your mirrorlist might be outdated, which might lead to problems when updating Arch Linux (see {{Bug|22510}}). Therefore it is advised to obtain the latest mirror information as described above.<br />
* Some issues have been reported in the [https://bbs.archlinux.org/ Arch Linux forums] regarding network problems that prevent pacman from updating/synchronizing repositories (see [https://bbs.archlinux.org/viewtopic.php?id&#61;68944] and [https://bbs.archlinux.org/viewtopic.php?id&#61;65728]). When installing Arch Linux natively, these issues have been resolved by replacing the default pacman file downloader with an alternative (see [[Improve Pacman Performance]] for more details). When installing Arch Linux as a guest OS in [[VirtualBox]], this issue has also been addressed by using "Host interface" instead of "NAT" in the machine properties.}}<br />
<br />
=== Install the base system ===<br />
<br />
The base system is installed using the [https://github.com/falconindy/arch-install-scripts/blob/master/pacstrap.in pacstrap] script.<br />
<br />
The {{ic|-i}} switch can be omitted if you wish to install every package from the ''base'' and ''base-devel'' groups without prompting.<br />
<br />
# pacstrap -i /mnt base base-devel<br />
<br />
{{Note|If pacman fails to verify your packages, check the system time with {{ic|cal}}. If the system date is invalid (e.g. it shows year 2010), signing keys will be considered expired (or invalid), signature checks on packages will fail and installation will be interrupted. Make sure to correct the system time, either by doing so manually or with the {{Pkg|ntp}} client, and retry running the pacstrap command. Refer to [[Time]] page for more information on correcting system time.}}<br />
<br />
{{Note| If pacman complains about invalid signatures during the pacstrap phase (''error: failed to commit transaction (invalid or corrupted package)'') run the following command below.}}<br />
# pacman-key --init && pacman-key --populate archlinux <br />
<br />
* {{Grp|base}}: Software packages from the [core] repo to provide the minimal base environment.<br />
<br />
* {{Grp|base-devel}}: Extra tools from [core] such as {{ic|make}}, and {{ic|automake}}. Most beginners should choose to install it, as it will likely be needed to expand the system. The ''base-devel'' group will be required to install software from the [[Arch User Repository]].<br />
<br />
This will give you a basic Arch system. Other packages can be installed later using [[pacman]].<br />
<br />
=== Generate an fstab ===<br />
<br />
Generate an [[fstab]] file with the following command. UUIDs will be used because they have certain advantages (see [[fstab#Identifying filesystems]]). If you would prefer to use labels instead, replace the {{ic|-U}} option with {{ic|-L}}.<br />
<br />
{{Note|If you encounter errors running genfstab or later in the install process, do '''not''' run genfstab again; just edit the fstab file.}}<br />
<br />
# genfstab -U -p /mnt >> /mnt/etc/fstab<br />
# nano /mnt/etc/fstab<br />
<br />
{{Warning|The fstab file should always be checked after generating it. If you made an EFI system partition earlier, then {{ic|genfstab}} has incorrectly added options to your EFI system partition. This will in fact ''prevent'' your computer from booting from that drive, so you need to remove all options for the EFI partition except for {{ic|noatime}}. For the other partitions that use it, be sure to replace {{ic|1="codepage=cp437"}} with {{ic|1="codepage=437"}} or else when you next reboot, any mounts with this option will fail and systemd will halt and drop into recovery mode. This should be fixed by linux 3.8}}<br />
<br />
A few considerations:<br />
<br />
* Only the root ({{ic|/}}) partition needs {{ic|1}} for the last field. Everything else should have either {{ic|2}} or {{ic|0}} (see [[fstab#Field definitions]]).<br />
<br />
=== Chroot and configure the base system ===<br />
<br />
Next, we [[chroot]] into our newly installed system:<br />
<br />
# arch-chroot /mnt<br />
<br />
{{Note|Use {{ic|arch-chroot /mnt /bin/bash}} to chroot into a bash shell.}}<br />
At this stage of the installation, you will configure the primary configuration files of your Arch Linux base system. These can either be created if they do not exist, or edited if you wish to change the defaults.<br />
<br />
Closely following and understanding these steps is of key importance to ensure a properly configured system.<br />
<br />
==== Locale ====<br />
<br />
Locales are used by '''glibc''' and other locale-aware programs or libraries for rendering text, correctly displaying regional monetary values, time and date formats, alphabetic idiosyncrasies, and other locale-specific standards.<br />
<br />
There are two files that need editing: {{ic|locale.gen}} and {{ic|locale.conf}}.<br />
<br />
* The {{ic|locale.gen}} file is empty by default (everything is commented out) and you need to remove the {{ic|#}} in front of the line(s) you want. You may uncomment more lines than just English (US), as long as you choose their {{ic|UTF-8}} encoding:<br />
<br />
{{hc|# nano /etc/locale.gen|<br />
en_US.UTF-8 UTF-8<br />
de_DE.UTF-8 UTF-8}}<br />
<br />
# locale-gen<br />
<br />
This will run on every '''glibc''' upgrade, generating all the locales specified in {{ic|/etc/locale.gen}}.<br />
<br />
* The {{ic|locale.conf}} file doesn't exist by default. Setting only {{ic|LANG}} should be enough. It will act as the default value for all other variables.<br />
<br />
# echo LANG=en_US.UTF-8 > /etc/locale.conf<br />
# export LANG=en_US.UTF-8<br />
<br />
{{Note|If you set some other language than English at the beginning of the install, the above commands would be something like:<br />
# echo LANG<nowiki>=</nowiki>de_DE.UTF-8 > /etc/locale.conf<br />
# export LANG<nowiki>=</nowiki>de_DE.UTF-8<br />
}}<br />
<br />
To use other {{ic|LC_*}} variables, first run {{ic|locale}} to see the available options. An advanced example can be found [[Locale#Setting_system-wide_locale|here]].<br />
<br />
{{Warning|Using the {{ic|LC_ALL}} variable is strongly discouraged because it overrides everything.}}<br />
<br />
==== Console font and keymap ====<br />
<br />
If you set a keymap at [[#Change_the_language|the beginning]] of the install process, load it now, as well, because the environment has changed. For example:<br />
<br />
# loadkeys ''de-latin1''<br />
# setfont Lat2-Terminus16<br />
<br />
To make them available after reboot, edit {{ic|vconsole.conf}}:<br />
<br />
{{hc|# nano /etc/vconsole.conf|2=<br />
KEYMAP=de-latin1<br />
FONT=Lat2-Terminus16<br />
}}<br />
<br />
* {{ic|KEYMAP}} – Please note that this setting is only valid for your TTYs, not any graphical window managers or Xorg.<br />
<br />
* {{ic|FONT}} – Available alternate console fonts reside in {{ic|/usr/share/kbd/consolefonts/}}. The default (blank) is safe, but some foreign characters may show up as white squares or as other symbols. It's recommended that you change it to {{ic|Lat2-Terminus16}}, because according to {{ic|/usr/share/kbd/consolefonts/README.Lat2-Terminus16}}, it claims to support "about 110 language sets".<br />
<br />
* Possible option {{ic|FONT_MAP}} – Defines the console map to load at boot. Read {{ic|man setfont}}. Removing it or leaving it blank is safe.<br />
<br />
See [[Fonts#Console_fonts|Console fonts]] and {{ic|man vconsole.conf}} for more information.<br />
<br />
==== Time zone ====<br />
<br />
Available time zones and subzones can be found in the {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} directories.<br />
<br />
To view the available <Zone>, check the directory {{ic|/usr/share/zoneinfo/}}:<br />
<br />
# ls /usr/share/zoneinfo/<br />
<br />
Similarly, you can check the contents of directories belonging to a <SubZone>:<br />
<br />
# ls /usr/share/zoneinfo/Europe<br />
<br />
Create a symbolic link {{ic|/etc/localtime}} to your zone file {{ic|/usr/share/zoneinfo/<Zone>/<SubZone>}} using this command:<br />
<br />
# ln -s /usr/share/zoneinfo/<Zone>/<SubZone> /etc/localtime<br />
<br />
'''Example:'''<br />
<br />
# ln -s /usr/share/zoneinfo/Europe/Minsk /etc/localtime<br />
<br />
==== Hardware clock ====<br />
<br />
Set the hardware clock mode uniformly between your operating systems. Otherwise, they may overwrite the hardware clock and cause time shifts.<br />
<br />
You can generate {{ic|/etc/adjtime}} automatically by using one of the following commands:<br />
<br />
* '''UTC''' (recommended)<br />
<br />
: {{Note|Using [[Wikipedia:Coordinated Universal Time|UTC]] for the hardware clock does not mean that software will display time in UTC.}}<br />
<br />
: {{bc|# hwclock --systohc --utc}}<br />
<br />
To synchronize your "UTC" time over the internet, see [[Network Time Protocol daemon|NTPd]].<br />
<br />
* '''localtime''' (discouraged; used by default in Windows)<br />
<br />
: {{Warning|Using ''localtime'' may lead to several known and unfixable bugs. However, there are no plans to drop support for ''localtime''.}}<br />
<br />
: {{bc|# hwclock --systohc --localtime}}<br />
<br />
If you have (or planning on having) a dual boot setup with Windows:<br />
<br />
* Recommended: Set both Arch Linux and Windows to use UTC. A quick [[Time#UTC in Windows|registry fix]] is needed. Also, be sure to prevent Windows from synchronizing the time on-line, because the hardware clock will default back to ''localtime''. <br />
<br />
* Not recommended: Set Arch Linux to ''localtime'' and disable any time-related services, like [[Network Time Protocol daemon|NTPd]] . This will let Windows take care of hardware clock corrections and you will need to remember to boot into Windows at least two times a year (in Spring and Autumn) when [[Wikipedia:Daylight saving time|DST]] kicks in. So please don't ask on the forums why the clock is one hour behind or ahead if you usually go for days or weeks without booting into Windows.<br />
<br />
==== Kernel modules ====<br />
<br />
{{Tip|This is just an example, you do not need to set it. All needed modules are automatically loaded by udev, so you will rarely need to add something here. Only add modules that you know are missing.}}<br />
<br />
For kernel modules to load during boot, place a {{ic|*.conf}} file in {{ic|/etc/modules-load.d/}}, with a name based on the program that uses them.<br />
<br />
{{hc|# nano /etc/modules-load.d/virtio-net.conf|<br />
# Load 'virtio-net.ko' at boot.<br />
<br />
virtio-net}}<br />
<br />
If there are more modules to load per {{ic|*.conf}}, the module names can be separated by newlines. A good example are the [[VirtualBox#Arch Linux guests|VirtualBox Guest Additions]].<br />
<br />
Empty lines and lines starting with {{ic|#}} or {{ic|;}} are ignored.<br />
<br />
==== Hostname ====<br />
<br />
Set the [[Wikipedia:hostname|hostname]] to your liking (e.g. ''arch''):<br />
<br />
# echo ''myhostname'' > /etc/hostname<br />
<br />
{{Note|There is no need to edit {{ic|/etc/hosts}}.}}<br />
<br />
=== Configure the network ===<br />
<br />
You need to configure the network again, but this time for your newly installed environment. The procedure and prerequisites are very similar to the one described [[#Establish an internet connection|above]], except we are going to make it persistent and automatically run at boot.<br />
<br />
{{Note|For more in-depth information on network configration, visit [[Network Configuration]] and [[Wireless Setup]].}}<br />
<br />
==== Wired ====<br />
<br />
; Dynamic IP<br />
<br />
{{Warning|A bug has been noted in the install ISO, in which the name your interface has during installation differs from the one it will have upon reboot. See [https://bugs.archlinux.org/task/33923 Bug #33923] for more details.<br />
Until this bug is fixed, you can use the following script to find the name your interface will have after boot:<br />
for i in /sys/class/net/*; do<br />
echo "&#61;&#61;$i"<br />
udevadm test-builtin net_id "$i";<br />
echo<br />
done 2>/dev/null<br />
}}<br />
<br />
If you only use a single fixed wired network connection, you do not need a network management service and can simply enable the {{ic|dhcpcd}} service. Where <interface> is your wired interface:<br />
# systemctl enable dhcpcd@<interface>.service<br />
<br />
Alternatively, you can use {{Pkg|netcfg}}'s {{ic|net-auto-wired}}, which gracefully handles dynamic connections to new networks:<br />
<br />
Install {{Pkg|ifplugd}}, which is required for {{ic|net-auto-wired}}:<br />
# pacman -S ifplugd<br />
<br />
Edit {{ic|/etc/conf.d/netcfg}} and modify the network interface name, most likely it is not eth0. You can find out more about the naming in the warning above.<br />
{{hc|nano /etc/conf.d/netcfg|2=<br />
WIRED_INTERFACE="<interface>"}}<br />
<br />
Copy a sample profile from {{ic|/etc/network.d/examples}} to {{ic|/etc/network.d}}:<br />
# cd /etc/network.d<br />
# cp examples/ethernet-dhcp .<br />
<br />
Edit the profile as needed (modify {{ic|INTERFACE}}):<br />
# nano ethernet-dhcp<br />
<br />
Enable the {{ic|net-auto-wired}} service.<br />
# systemctl enable net-auto-wired.service<br />
<br />
; Static IP<br />
<br />
Copy a sample profile from {{ic|/etc/network.d/examples}} to {{ic|/etc/network.d}}:<br />
# cd /etc/network.d<br />
# cp examples/ethernet-static .<br />
<br />
Edit the profile as needed (modify {{ic|INTERFACE}}, {{ic|ADDR}}, {{ic|GATEWAY}} and {{ic|DNS}}):<br />
# nano ethernet-static<br />
<br />
Edit {{ic|/etc/conf.d/netcfg}} and add the new network profile to the {{ic|NETWORKS}} array:<br />
{{hc|nano /etc/conf.d/netcfg|<br />
2=NETWORKS=(ethernet-static)}}<br />
<br />
Enable the {{ic|netcfg}} service:<br />
# systemctl enable netcfg.service<br />
<br />
==== Wireless ====<br />
<br />
You will need to install additional programs to be able to configure and manage wireless network profiles for [[netcfg]].<br />
<br />
[[NetworkManager]] and [[Wicd]] are other popular alternatives.<br />
<br />
* Install the required packages:<br />
<br />
# pacman -S wireless_tools wpa_supplicant wpa_actiond dialog<br />
<br />
If your wireless adapter requires a firmware (as described in the above [[#Wireless|Establish an internet connection]] section and also [[Wireless Setup#Drivers and firmware|here]]), install the package containing your firmware. For example:<br />
<br />
# pacman -S zd1211-firmware<br />
<br />
See [[Wireless Setup]] and [[WPA supplicant]] for more info.<br />
<br />
* After finishing the rest of this installation and rebooting, you can connect to the network with {{ic|wifi-menu <interface>}} (where {{ic|<interface>}} is the interface of your wireless chipset), which will generate a profile file in {{ic|/etc/network.d}} named after the SSID. There are also templates available in {{ic|/etc/network.d/examples/}} for manual configuration.<br />
<br />
# wifi-menu <interface><br />
<br />
{{Warning|If you're using {{ic|wifi-menu}}, this must be done *after* your reboot when you're no longer chrooted. The process spawned by this command will conflict with the one you have running outside of the chroot. Alternatively, you could just configure a network profile manually using the templates previously mentioned so that you don't have to worry about using {{ic|wifi-menu}} at all.}}<br />
<br />
* Enable the {{ic|net-auto-wireless}} service, which will connect to known networks and gracefully handle roaming and disconnects:<br />
<br />
# systemctl enable net-auto-wireless.service<br />
<br />
{{Note|[[Netcfg]] also provides {{ic|net-auto-wired}}, which can be used in conjunction with {{ic|net-auto-wireless}}.}}<br />
<br />
* Make sure that the correct wireless interface (e.g. {{ic|wlp3s0}}) is set in {{ic|/etc/conf.d/netcfg}}:<br />
<br />
{{hc|# nano /etc/conf.d/netcfg|2=<br />
WIRELESS_INTERFACE="wlp3s0"}}<br />
<br />
It is also possible to define a list of network profiles that should be automatically connected, using the {{ic|AUTO_PROFILES}} variable in {{ic|/etc/conf.d/netcfg}}. If {{ic|AUTO_PROFILES}} is not set, all known wireless networks will be tried.<br />
<br />
==== xDSL (PPPoE), analog modem or ISDN ====<br />
<br />
For xDSL, dial-up and ISDN connections, see [[Direct Modem Connection]].<br />
<br />
=== Configure pacman ===<br />
<br />
Pacman is the Arch Linux '''pac'''kage '''man'''ager. It is highly recommended to study and learn how to use it. Read {{ic|man pacman}}, have a look at the [[pacman]] and [[Pacman - An Introduction]] articles, or check out the [[Pacman Rosetta]] article for a comparison to other popular package managers.<br />
<br />
For repository selections and pacman options, edit {{ic|pacman.conf}}:<br />
# nano /etc/pacman.conf<br />
<br />
Most people will want to use {{ic|[core]}}, {{ic|[extra]}} and {{ic|[community]}}.<br />
<br />
If you installed Arch Linux x86_64, it's recommended that you enable the {{ic|[multilib]}} repository, as well (to be able to run both 32 bit and 64 bit applications):<br />
<br />
{{Note|When choosing repos, be sure to uncomment both the {{ic|[''repo_name'']}} header lines, as well as the lines below. Failure to do so will result in the selected repository being omitted! This is a very common error. A correct example for the multilib repository is found below.}}<br />
<br />
[multilib]<br />
SigLevel = PackageRequired<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
You will then need to update the package list by running {{ic|pacman}} with the {{ic|-Sy}} switch. Failing to do so will generate "warning: database file for 'multilib' does not exist" error when next using pacman.<br />
<br />
See [[Official Repositories]] for more information, including details about the purpose of each repository.<br />
<br />
For software unavailable directly through pacman, see [[Arch User Repository]].<br />
<br />
=== Create an initial ramdisk environment ===<br />
<br />
{{Tip|Most users can skip this step and use the defaults provided in {{ic|mkinitcpio.conf}}. The initramfs image (from the {{ic|/boot}} folder) has already been generated based on this file when the {{Pkg|linux}} package (the Linux kernel) was installed earlier with {{ic|pacstrap}}.}}<br />
<br />
Here you need to set the right [[Mkinitcpio#HOOKS|hooks]] if the root is on a USB drive, if you use RAID, LVM, or if {{ic|/usr}} is on a separate partition.<br />
<br />
Edit {{ic|/etc/mkinitcpio.conf}} as needed and re-generate the initramfs image with:<br />
<br />
# mkinitcpio -p linux<br />
<br />
{{Note|Arch VPS installations on QEMU (e.g. when using {{ic|virt-manager}}) may need {{ic|virtio}} modules in {{ic|mkinitcpio.conf}} to be able to boot.<br />
<br />
{{hc|# nano /etc/mkinitcpio.conf|2=<br />
MODULES="virtio virtio_blk virtio_pci virtio_net"}}}}<br />
<br />
=== Set the root password ===<br />
<br />
Set the root password with:<br />
<br />
# passwd<br />
<br />
=== Install and configure a bootloader ===<br />
<br />
==== For BIOS motherboards ====<br />
<br />
For BIOS systems, there are three bootloaders - Syslinux, GRUB, and [[LILO]]. Choose the bootloader as per your convenience. Below only Syslinux and GRUB are explained. <br />
<br />
* Syslinux is (currently) limited to loading only files from the partition where it was installed. Its configuration file is considered to be easier to understand. An example configuration can be found [https://bbs.archlinux.org/viewtopic.php?pid=1109328#p1109328 here].<br />
<br />
* GRUB is more feature-rich and supports more complex scenarios. Its configuration file(s) is more similar to a scripting language, which may be difficult for beginners to manually write. It is recommended that they automatically generate one.<br />
<br />
{{Note|Some BIOS systems may have issues with GPT. See http://mjg59.dreamwidth.org/8035.html and http://rodsbooks.com/gdisk/bios.html for more info and possible workarounds.}}<br />
<br />
===== Syslinux =====<br />
<br />
Install the {{Pkg|syslinux}} package and then use the {{ic|syslinux-install_update}} script to automatically ''install'' the files ({{ic|-i}}), mark the partition ''active'' by setting the boot flag ({{ic|-a}}), and install the ''MBR'' boot code ({{ic|-m}}):<br />
<br />
{{Note|If you have partitioned the drive as GPT, install {{Pkg|gptfdisk}} package, as well ({{ic|pacman -S gptfdisk}}), because it contains {{ic|sgdisk}}, which will be used to set the GPT-specific boot flag.}}<br />
<br />
# pacman -S syslinux<br />
# syslinux-install_update -i -a -m<br />
<br />
Configure {{ic|syslinux.cfg}} to point to the right root partition. This step is vital. If it points to the wrong partition, Arch Linux will not boot. Change {{ic|/dev/sda3}} to reflect your root partition ''(if you partitioned your drive as in [[#Prepare the storage drive|the example]], your root partition is sda1)''. Do the same for the fallback entry.<br />
<br />
{{hc|# nano /boot/syslinux/syslinux.cfg|2=<br />
...<br />
LABEL arch<br />
...<br />
APPEND root=/dev/sda3 ro<br />
...}}<br />
<br />
For more information on configuring and using Syslinux, see [[Syslinux]].<br />
<br />
===== GRUB =====<br />
<br />
Install the {{Pkg|grub-bios}} package and then run {{ic|grub-install /dev/sda}}:<br />
<br />
{{Note|Change {{ic|/dev/sda}} to reflect the drive you installed Arch on. Do not append a partition number (do not use {{ic|sda''X''}}).}}<br />
<br />
{{Note|For GPT-partitioned drives on BIOS motherboards, GRUB needs a "[[GRUB2#GUID Partition Table (GPT) specific instructions|BIOS Boot Partition]]".}}<br />
<br />
# pacman -S grub-bios<br />
# grub-install --target=i386-pc --recheck /dev/sda<br />
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br />
<br />
While using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} ({{ic|pacman -S os-prober}}) before running the next command.}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
For more information on configuring and using GRUB, see [[GRUB2]].<br />
<br />
==== For UEFI motherboards ====<br />
<br />
For UEFI boot, the drive needs to be GPT-partitioned, and a UEFI System Partition (512 MiB or higher, FAT32, type {{ic|EF00}}) must be present and mounted on {{ic|/boot/efi}}. If you have followed this guide from the beginning, you've already done all of these.<br />
<br />
While there are other [[UEFI Bootloaders|UEFI bootloaders]] available, using EFISTUB is recommended. Below are instructions for setting up EFISTUB and GRUB (of course you choose only one of them).<br />
<br />
{{Note|Syslinux does not yet support UEFI.}}<br />
<br />
===== EFISTUB =====<br />
<br />
The Linux kernel can act as its own bootloader using EFISTUB. This is the UEFI boot method recommended by developers and simpler compared to {{ic|grub-efi-x86_64}}. The steps below set up rEFInd (a fork of rEFIt) to provide a menu for EFISTUB kernels, as well as for booting other UEFI bootloaders. You can also use [[UEFI Bootloaders#Using gummiboot|gummiboot]] instead of rEFInd, however, gummiboot requires kernel 3.8 which is still in testing. Both rEFInd and gummiboot can detect Windows UEFI bootloader in case of dual-boot.<br />
<br />
1. Boot in UEFI mode and load {{ic|efivars}} kernel module before chrooting:<br />
<br />
# modprobe efivars # before chrooting<br />
<br />
2. Mount the UEFISYS partition at {{ic|/mnt/boot/efi}}, chroot and [[UEFI_Bootloaders#Setting_up_EFISTUB|copy the kernel and initramfs files]] as described below.<br />
<br />
* Create {{ic|/boot/efi/EFI/arch/}} directory.<br />
<br />
* Copy {{ic|/boot/vmlinuz-linux}} to {{ic|/boot/efi/EFI/arch/vmlinuz-arch.efi}}. The {{ic|.efi}} file extension is very important as some UEFI firmwares refuse to launch a file without this extension. '''Important:''' Remember that the file is called vmlinu'''z''', but not vmlinu'''x'''.<br />
<br />
* Copy {{ic|/boot/initramfs-linux.img}} to {{ic|/boot/efi/EFI/arch/initramfs-arch.img}}.<br />
<br />
* Copy {{ic|/boot/initramfs-linux-fallback.img}} to {{ic|/boot/efi/EFI/arch/initramfs-arch-fallback.img}}.<br />
<br />
Every time the kernel and initramfs files are updated in {{ic|/boot}}, they need to be updated in {{ic|/boot/efi/EFI/arch}}. This can be automated [[UEFI_Bootloaders#Systemd|using systemd]].<br />
<br />
3. In this guide you set up a bootloader GUI called rEFInd. Alternative bootloaders can be found on the page [[UEFI Bootloaders#Booting EFISTUB]].<br />
For the recommended rEFInd bootloader install the following packages:<br />
# pacman -S refind-efi efibootmgr<br />
<br />
4. Install rEFInd to the UEFISYS partition (summarized from [[UEFI Bootloaders#Using rEFInd]]):<br />
<br />
# mkdir -p /boot/efi/EFI/refind<br />
# cp /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/refind_x64.efi<br />
# cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/refind.conf<br />
# cp -r /usr/share/refind/icons /boot/efi/EFI/refind/icons<br />
<br />
5. Create a {{ic|refind_linux.conf}} file with the kernel parameters to be used by rEFInd:<br />
<br />
{{hc|# nano /boot/efi/EFI/arch/refind_linux.conf|2=<br />
"Boot to X" "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=graphical.target"<br />
"Boot to console" "root=/dev/sdaX ro rootfstype=ext4 systemd.unit=multi-user.target"}}<br />
<br />
{{Note|{{ic|refind_linux.conf}} is copied in the directory {{ic|/boot/efi/EFI/arch/}} where the initramfs and the kernel have been copied to in step 2. }}<br />
{{Note|In {{ic|refind_linux.conf}}, sdaX refers to your root file system, not your boot partition, if you created them separately. }}<br />
<br />
6. Add rEFInd to UEFI boot menu using [[UEFI#efibootmgr|efibootmgr]]. <br />
<br />
{{Warning|Using {{ic|efibootmgr}} on Apple Macs may brick the firmware and may need reflash of the motherboard ROM. For Macs, use {{AUR|mactel-boot}}, or "bless" from within Mac OS X.}}<br />
<br />
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'<br />
<br />
{{Note|In the above command, X and Y denote the drive and partition of the UEFISYS partition. For example, in {{ic|/dev/sdc5}}, X is "c" and Y is "5".}}<br />
<br />
7. (Optional) As a fallback, in case {{ic|efibootmgr}} created boot entry does not work, copy {{ic|refind_x64.efi}} to {{ic|/boot/efi/EFI/boot/bootx64.efi}} as follows:<br />
<br />
# cp -r /boot/efi/EFI/refind/* /boot/efi/EFI/boot/<br />
# mv /boot/efi/EFI/boot/refind_x64.efi /boot/efi/EFI/boot/bootx64.efi<br />
<br />
===== GRUB =====<br />
<br />
{{Note|In case you have a system with 32-bit EFI, like pre-2008 Macs, install {{ic|grub-efi-i386}} instead, and use {{ic|1=--target=i386-efi}}.}}<br />
<br />
# pacman -S grub-efi-x86_64 efibootmgr<br />
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck<br />
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br />
<br />
The next command creates a menu entry for GRUB in the UEFI boot menu. However, as of {{Pkg|grub-efi-x86_64}} version 2.00, {{ic|grub-install}} tries to create a menu entry, so running {{ic|efibootmgr}} may not be necessary. See [[UEFI#efibootmgr]] for more info.<br />
<br />
# efibootmgr -c -g -d /dev/sdX -p Y -w -L "Arch Linux (GRUB)" -l '\EFI\arch_grub\grubx64.efi'<br />
<br />
Next, while using a manually created {{ic|grub.cfg}} is absolutely fine, it's recommended that beginners automatically generate one:<br />
<br />
{{Tip|To automatically search for other operating systems on your computer, install {{Pkg|os-prober}} ({{ic|pacman -S os-prober}}) before running the next command.}}<br />
<br />
# grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
For more information on configuring and using GRUB, see [[GRUB]].<br />
<br />
=== Unmount the partitions and reboot ===<br />
<br />
Exit from the chroot environment:<br />
<br />
# exit<br />
<br />
Since the partitions are mounted under {{ic|/mnt}}, we use the following command to unmount them:<br />
<br />
# umount /mnt/{boot,home,}<br />
<br />
Reboot the computer:<br />
<br />
# reboot<br />
<br />
{{Tip|Be sure to remove the installation media, otherwise you will boot back into it.}}<noinclude><br />
{{Beginners' Guide navigation}}</noinclude></div>Alexjj