https://wiki.archlinux.org/api.php?action=feedcontributions&user=DonJaime&feedformat=atomArchWiki - User contributions [en]2024-03-28T19:59:49ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Power_management&diff=655106Power management2021-03-16T11:27:21Z<p>DonJaime: Undo revision 655039 by DonJaime (talk) Sorry</p>
<hr />
<div>[[Category:Power management]]<br />
[[es:Power management]]<br />
[[ja:電源管理]]<br />
[[zh-hans:Power management]]<br />
{{Related articles start}}<br />
{{Related|Power management/Suspend and hibernate}}<br />
{{Related|Display Power Management Signaling}}<br />
{{Related|CPU frequency scaling}}<br />
{{Related|Hybrid graphics}}<br />
{{Related|Kernel modules}}<br />
{{Related|sysctl}}<br />
{{Related|udev}}<br />
{{Related articles end}}<br />
[[Wikipedia:Power management|Power management]] is a feature that turns off the power or switches system's components to a low-power state when inactive.<br />
<br />
In Arch Linux, power management consists of two main parts:<br />
<br />
# Configuration of the Linux kernel, which interacts with the hardware.<br />
#* [[Kernel parameters]]<br />
#* [[Kernel modules]]<br />
#* [[udev]] rules<br />
# Configuration of userspace tools, which interact with the kernel and react to its events. Many userspace tools also allow to modify kernel configuration in a "user-friendly" way. See [[#Userspace tools]] for the options.<br />
<br />
== Userspace tools ==<br />
<br />
Using these tools can replace setting a lot of settings by hand. Only run '''one''' of these tools to avoid possible conflicts as they all work more or less similarly. Have a look at the [[:Category:Power management|power management category]] to get an overview on what power management options exist in Arch Linux.<br />
<br />
These are the more popular scripts and tools designed to help power saving:<br />
<br />
=== Console ===<br />
<br />
* {{App|[[acpid]]| A daemon for delivering ACPI power management events with netlink support.|https://sourceforge.net/projects/acpid2/|{{Pkg|acpid}}}}<br />
* {{App|[[Laptop Mode Tools]]|Utility to configure laptop power saving settings, considered by many to be the de facto utility for power saving though may take a bit of configuration.|https://github.com/rickysarraf/laptop-mode-tools|{{AUR|laptop-mode-tools}}}}<br />
* {{App|libsmbios|Library and tools for interacting with Dell SMBIOS tables.|https://github.com/dell/libsmbios|{{Pkg|libsmbios}}}}<br />
* {{App|[[powertop]]|A tool to diagnose issues with power consumption and power management to help set power saving settings.|https://01.org/powertop/|{{Pkg|powertop}}}}<br />
* {{App|[[systemd]]|A system and service manager.|https://freedesktop.org/wiki/Software/systemd/|{{Pkg|systemd}}}}<br />
* {{App|[[TLP]]|Advanced power management for Linux.|http://linrunner.de/tlp|{{Pkg|tlp}}}}<br />
<br />
=== Graphical ===<br />
<br />
* {{App|batterymon-clone|Simple battery monitor tray icon.|https://github.com/jareksed/batterymon-clone|{{AUR|batterymon-clone}}}}<br />
* {{App|batsignal|Lightweight battery monitor that uses libnotify to warn of low battery levels.|https://github.com/electrickite/batsignal|{{AUR|batsignal}}}}<br />
* {{App|cbatticon|Lightweight and fast battery icon that sits in your system tray.|https://github.com/valr/cbatticon|{{Pkg|cbatticon}}}}<br />
* {{App|GNOME Power Statistics|System power information and statistics for GNOME.|https://gitlab.gnome.org/GNOME/gnome-power-manager|{{Pkg|gnome-power-manager}}}}<br />
* {{App|KDE Power Devil|Power management module for Plasma.|https://invent.kde.org/plasma/powerdevil|{{Pkg|powerdevil}}}}<br />
* {{App|LXQt Power Management|Power management module for LXQt.|https://github.com/lxqt/lxqt-powermanagement|{{Pkg|lxqt-powermanagement}}}}<br />
* {{App|MATE Power Management|Power management tool for MATE.|https://github.com/mate-desktop/mate-power-manager|{{Pkg|mate-power-manager}}}}<br />
* {{App|MATE Power Statistics|System power information and statistics for MATE.|https://github.com/mate-desktop/mate-power-manager|{{Pkg|mate-power-manager}}}}<br />
* {{App|powerkit|Desktop independent power manager.|https://github.com/rodlie/powerkit|{{AUR|powerkit}}}}<br />
* {{App|Xfce Power Manager|Power manager for Xfce.|https://docs.xfce.org/xfce/xfce4-power-manager/start|{{Pkg|xfce4-power-manager}}}}<br />
* {{App|vattery|Battery monitoring application written in Vala that will display the status of a laptop battery in a system tray.|https://www.jezra.net/projects/vattery.html|{{AUR|vattery}}}}<br />
<br />
== Power management with systemd ==<br />
<br />
=== ACPI events ===<br />
<br />
''systemd'' handles some power-related [[Wikipedia:Advanced_Configuration_and_Power_Interface|ACPI]] events, whose actions can be configured in {{ic|/etc/systemd/logind.conf}} or {{ic|/etc/systemd/logind.conf.d/*.conf}} — see {{man|5|logind.conf}}. On systems with no dedicated power manager, this may replace the [[acpid]] daemon which is usually used to react to these ACPI events.<br />
<br />
The specified action for each event can be one of {{ic|ignore}}, {{ic|poweroff}}, {{ic|reboot}}, {{ic|halt}}, {{ic|suspend}}, {{ic|hibernate}}, {{ic|hybrid-sleep}}, {{ic|suspend-then-hibernate}}, {{ic|lock}} or {{ic|kexec}}. In case of hibernation and suspension, they must be properly [[Power management/Suspend and hibernate|set up]]. If an event is not configured, ''systemd'' will use a default action.<br />
<br />
{| class="wikitable sortable" border=1<br />
!Event handler<br />
!Description<br />
!Default action<br />
|-<br />
|{{ic|HandlePowerKey}}<br />
|Triggered when the power key/button is pressed.<br />
|{{ic|poweroff}}<br />
|-<br />
|{{ic|HandleSuspendKey}}<br />
|Triggered when the suspend key/button is pressed.<br />
|{{ic|suspend}}<br />
|-<br />
|{{ic|HandleHibernateKey}}<br />
|Triggered when the hibernate key/button is pressed.<br />
|{{ic|hibernate}}<br />
|-<br />
|{{ic|HandleLidSwitch}}<br />
|Triggered when the lid is closed, except in the cases below.<br />
|{{ic|suspend}}<br />
|-<br />
|{{ic|HandleLidSwitchDocked}}<br />
|Triggered when the lid is closed if the system is inserted in a docking station, or more than one display is connected.<br />
|{{ic|ignore}}<br />
|-<br />
|{{ic|HandleLidSwitchExternalPower}}<br />
|Triggered when the lid is closed if the system is connected to external power.<br />
|action set for {{ic|HandleLidSwitch}}<br />
|}<br />
<br />
To apply any changes, signal {{ic|systemd-logind}} with {{ic|HUP}}:<br />
<br />
# systemctl kill -s HUP systemd-logind<br />
<br />
{{Note|''systemd'' cannot handle AC and Battery ACPI events, so if you use [[Laptop Mode Tools]] or other similar tools [[acpid]] is still required.}}<br />
<br />
==== Power managers ====<br />
<br />
Some [[desktop environment]]s include power managers which [https://www.freedesktop.org/wiki/Software/systemd/inhibit/ inhibit] (temporarily turn off) some or all of the ''systemd'' ACPI settings. If such a power manager is running, then the actions for ACPI events can be configured in the power manager alone. Changes to {{ic|/etc/systemd/logind.conf}} or {{ic|/etc/systemd/logind.conf.d/*.conf}} need be made only if you wish to configure behaviour for a particular event that is not inhibited by the power manager. <br />
<br />
Note that if the power manager does not inhibit ''systemd'' for the appropriate events you can end up with a situation where ''systemd'' suspends your system and then when the system is woken up the other power manager suspends it again. As of December 2016, the power managers of [[KDE]], [[GNOME]], [[Xfce]] and [[MATE]] issue the necessary ''inhibited'' commands. If the ''inhibited'' commands are not being issued, such as when using [[acpid]] or others to handle ACPI events, set the {{ic|Handle}} options to {{ic|ignore}}. See also {{man|1|systemd-inhibit}}.<br />
<br />
==== xss-lock ====<br />
<br />
{{pkg|xss-lock}} subscribes to the systemd-events {{ic|suspend}}, {{ic|hibernate}}, {{ic|lock-session}}, and {{ic|unlock-session}} with appropriate actions (run locker and wait for user to unlock or kill locker). ''xss-lock'' also reacts to [[DPMS]] events and runs or kills the locker in response.<br />
<br />
Start xss-lock in your [[autostart]], for example<br />
<br />
xss-lock -- i3lock -n -i ''background_image.png'' &<br />
<br />
=== Suspend and hibernate ===<br />
<br />
''systemd'' provides commands to suspend to RAM or hibernate using the kernel's native suspend/resume functionality. There are also mechanisms to add hooks to customize pre- and post-suspend actions.<br />
<br />
{{ic|systemctl suspend}} should work out of the box, for {{ic|systemctl hibernate}} to work on your system you need to follow the instructions at [[Suspend and hibernate#Hibernation]].<br />
<br />
There are also two modes combining suspend and hibernate:<br />
<br />
* {{ic|systemctl hybrid-sleep}} suspends the system both to RAM and disk, so a complete power loss does not result in lost data. This mode is also called [[Power management/Suspend and hibernate|suspend to both]].<br />
* {{ic|systemctl suspend-then-hibernate}} initially suspends the system to RAM and if it is not interrupted within the delay specified by {{ic|HibernateDelaySec}} in {{man|5|systemd-sleep.conf}}, then the system will be woken using an RTC alarm and hibernated.<br />
<br />
{{Note|''systemd'' can also use other suspend backends (such as [[Uswsusp]]), in addition to the default ''kernel'' backend, in order to put the computer to sleep or hibernate. See [[Uswsusp#With systemd]] for an example.}}<br />
<br />
==== Hybrid-sleep on suspend or hibernation request ====<br />
<br />
It is possible to configure systemd to always do a ''hybrid-sleep'' even on a ''suspend'' or ''hibernation'' request.<br />
<br />
The default ''suspend'' and ''hibernation'' action can be configured in the {{ic|/etc/systemd/sleep.conf}} file. To set both actions to ''hybrid-sleep'':<br />
<br />
{{hc|/etc/systemd/sleep.conf|2=<br />
[Sleep]<br />
# suspend=hybrid-sleep<br />
SuspendMode=suspend<br />
SuspendState=disk<br />
# hibernate=hybrid-sleep<br />
HibernateMode=suspend<br />
HibernateState=disk<br />
}}<br />
<br />
See the {{man|5|sleep.conf.d}} manual page for details and the [https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-system-suspend-and-hibernation linux kernel documentation on power states].<br />
<br />
=== Sleep hooks ===<br />
<br />
==== Suspend/resume service files ====<br />
<br />
Service files can be hooked into ''suspend.target'', ''hibernate.target'', ''sleep.target'', ''hybrid-sleep.target'' and ''suspend-then-hibernate.target'' to execute actions before or after suspend/hibernate. Separate files should be created for user actions and root/system actions. [[Enable]] the {{ic|suspend@''user''}} and {{ic|resume@''user''}} services to have them started at boot. Examples:<br />
<br />
{{hc|/etc/systemd/system/suspend@.service|2=<br />
[Unit]<br />
Description=User suspend actions<br />
Before=sleep.target<br />
<br />
[Service]<br />
User=%I<br />
Type=forking<br />
Environment=DISPLAY=:0<br />
ExecStartPre= -/usr/bin/pkill -u %u unison ; /usr/local/bin/music.sh stop<br />
ExecStart=/usr/bin/sflock<br />
ExecStartPost=/usr/bin/sleep 1<br />
<br />
[Install]<br />
WantedBy=sleep.target<br />
}}<br />
<br />
{{hc|/etc/systemd/system/resume@.service|2=<br />
[Unit]<br />
Description=User resume actions<br />
After=suspend.target<br />
<br />
[Service]<br />
User=%I<br />
Type=simple<br />
ExecStart=/usr/local/bin/ssh-connect.sh<br />
<br />
[Install]<br />
WantedBy=suspend.target}}<br />
<br />
{{Note|As screen lockers may return before the screen is "locked", the screen may flash on resuming from suspend. Adding a small delay via {{ic|1=ExecStartPost=/usr/bin/sleep 1}} helps prevent this.}}<br />
<br />
For root/system actions ([[enable]] the {{ic|root-resume}} and {{ic|root-suspend}} services to have them started at boot):<br />
<br />
{{hc|/etc/systemd/system/root-suspend.service|2=<br />
[Unit]<br />
Description=Local system suspend actions<br />
Before=sleep.target<br />
<br />
[Service]<br />
Type=simple<br />
ExecStart=-/usr/bin/pkill sshfs<br />
<br />
[Install]<br />
WantedBy=sleep.target}}<br />
<br />
{{hc|/etc/systemd/system/root-resume.service|2=<br />
[Unit]<br />
Description=Local system resume actions<br />
After=suspend.target<br />
<br />
[Service]<br />
Type=simple<br />
ExecStart=/usr/bin/systemctl restart mnt-media.automount<br />
<br />
[Install]<br />
WantedBy=suspend.target}}<br />
<br />
{{Tip|A couple of handy hints about these service files (more in {{man|5|systemd.service}}):<br />
<br />
* If {{ic|1=<nowiki>Type=oneshot</nowiki>}} then you can use multiple {{ic|1=<nowiki>ExecStart=</nowiki>}} lines. Otherwise only one {{ic|ExecStart}} line is allowed. You can add more commands with either {{ic|ExecStartPre}} or by separating commands with a semicolon (see the first example above; note the spaces before and after the semicolon, as they are ''required'').<br />
* A command prefixed with {{ic|-}} will cause a non-zero exit status to be ignored and treated as a successful command. <br />
* The best place to find errors when troubleshooting these service files is of course with [[journalctl]].<br />
}}<br />
<br />
==== Combined Suspend/resume service file ====<br />
<br />
With the combined suspend/resume service file, a single hook does all the work for different phases (sleep/resume) and for different targets (suspend/hibernate/hybrid-sleep).<br />
<br />
Example and explanation:<br />
<br />
{{hc|/etc/systemd/system/wicd-sleep.service|2=<nowiki><br />
[Unit]<br />
Description=Wicd sleep hook<br />
Before=sleep.target<br />
StopWhenUnneeded=yes<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=yes<br />
ExecStart=-/usr/share/wicd/daemon/suspend.py<br />
ExecStop=-/usr/share/wicd/daemon/autoconnect.py<br />
<br />
[Install]<br />
WantedBy=sleep.target<br />
</nowiki>}}<br />
<br />
* {{ic|1=<nowiki>RemainAfterExit=yes</nowiki>}}: After started, the service is considered active until it is explicitly stopped.<br />
* {{ic|1=<nowiki>StopWhenUnneeded=yes</nowiki>}}: When active, the service will be stopped if no other active service requires it. In this specific example, it will be stopped after ''sleep.target'' is stopped.<br />
* Because ''sleep.target'' is pulled in by ''suspend.target'', ''hibernate.target'' and ''hybrid-sleep.target'' and because ''sleep.target'' itself is a ''StopWhenUnneeded'' service, the hook is guaranteed to start/stop properly for different tasks.<br />
<br />
===== Generic service template =====<br />
<br />
In this example, we create a [http://0pointer.net/blog/projects/instances.html template service] which we can then use to hook any existing systemd service to power events:[https://narkive.com/mYzxSIDN.6]<br />
<br />
{{hc|/etc/systemd/system/sleep@.service|2=<br />
[Unit]<br />
Description=%I sleep hook<br />
Before=sleep.target<br />
StopWhenUnneeded=yes<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=yes<br />
ExecStart=-/usr/bin/systemctl stop %i<br />
ExecStop=-/usr/bin/systemctl start %i<br />
<br />
[Install]<br />
WantedBy=sleep.target}}<br />
<br />
Then [[enable]] an instance of this template by specifying the basename of an existing systemd service after the @:<br />
<br />
# systemctl enable sleep@'''''service-file-basename'''''.service<br />
<br />
See {{man|5|systemd.unit|DESCRIPTION}} for more details on templates.<br />
<br />
{{Tip|Templates are not limited to systemd services and can be used with other programs/ See [https://fedoramagazine.org/systemd-template-unit-files/] for some examples.}}<br />
<br />
==== Hooks in /usr/lib/systemd/system-sleep ====<br />
<br />
''systemd'' runs all executables in {{ic|/usr/lib/systemd/system-sleep/}}, passing two arguments to each of them:<br />
<br />
* Argument 1: either {{ic|pre}} or {{ic|post}}, depending on whether the machine is going to sleep or waking up<br />
* Argument 2: {{ic|suspend}}, {{ic|hibernate}} or {{ic|hybrid-sleep}}, depending on which is being invoked<br />
<br />
''systemd'' will run these scripts concurrently and not one after another.<br />
<br />
The output of any custom script will be logged by ''systemd-suspend.service'', ''systemd-hibernate.service'' or ''systemd-hybrid-sleep.service''. You can see its output in ''systemd''<nowiki>'</nowiki>s [[journalctl]]:<br />
<br />
# journalctl -b -u systemd-suspend.service<br />
<br />
{{Note|You can also use ''sleep.target'', ''suspend.target'', ''hibernate.target'' or ''hybrid-sleep.target'' to hook units into the sleep state logic instead of using custom scripts.}}<br />
<br />
An example of a custom sleep script:<br />
<br />
{{hc|/usr/lib/systemd/system-sleep/example.sh|<br />
#!/bin/sh<br />
case $1/$2 in<br />
pre/*)<br />
echo "Going to $2..."<br />
;;<br />
post/*)<br />
echo "Waking up from $2..."<br />
;;<br />
esac<br />
}}<br />
<br />
Do not forget to make your script executable:<br />
<br />
# chmod a+x /usr/lib/systemd/system-sleep/example.sh<br />
<br />
See {{man|7|systemd.special}} and {{man|8|systemd-sleep}} for more details.<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Delayed lid switch action ====<br />
<br />
When performing lid switches in short succession, ''logind'' will delay the suspend action for up to 90s to detect possible docks. [https://lists.freedesktop.org/archives/systemd-devel/2015-January/027131.html] This delay was made configurable with systemd v220:[https://github.com/systemd/systemd/commit/9d10cbee89ca7f82d29b9cb27bef11e23e3803ba]<br />
<br />
{{hc|/etc/systemd/logind.conf|2=<br />
...<br />
HoldoffTimeoutSec=30s<br />
...<br />
}}<br />
<br />
==== Suspend from corresponding laptop Fn key not working ====<br />
<br />
If, regardless of the setting in logind.conf, the sleep button does not work (pressing it does not even produce a message in syslog), then logind is probably not watching the keyboard device. [https://lists.freedesktop.org/archives/systemd-devel/2015-February/028325.html] Do:<br />
<br />
# journalctl --grep="Watching system buttons"<br />
<br />
You might see something like this:<br />
<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event2 (Power Button)<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event3 (Sleep Button)<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event4 (Video Bus)<br />
<br />
Notice no keyboard device. Now obtain ATTRS{name} for the parent keyboard device [http://systemd-devel.freedesktop.narkive.com/Rbi3rjNN/patch-1-2-logind-add-support-for-tps65217-power-button] :<br />
<br />
{{hc|# udevadm info -a /dev/input/by-path/*-kbd|2=<br />
...<br />
KERNEL=="event0"<br />
...<br />
ATTRS{name}=="AT Translated Set 2 keyboard"<br />
}}<br />
<br />
Now write a custom udev rule to add the "power-switch" tag:<br />
<br />
{{hc|/etc/udev/rules.d/70-power-switch-my.rules|<nowiki><br />
ACTION=="remove", GOTO="power_switch_my_end"<br />
SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="AT Translated Set 2 keyboard", TAG+="power-switch"<br />
LABEL="power_switch_my_end"<br />
</nowiki>}}<br />
<br />
{{Style|Explicit {{ic|systemctl}} commands should not be provided.}}<br />
<br />
Restart services and reload rules:<br />
<br />
# systemctl restart systemd-udevd.service<br />
# udevadm trigger<br />
# systemctl restart systemd-logind.service<br />
<br />
Now you should see {{ic|Watching system buttons on /dev/input/event0}} in syslog.<br />
<br />
== Power saving ==<br />
<br />
{{Note|See [[Laptop#Power management]] for power management specific to laptops, such as battery monitoring.}}<br />
<br />
This section is a reference for creating custom scripts and power saving settings such as by udev rules. Make sure that the settings are not managed by some [[#Userspace tools|other utility]] to avoid conflicts.<br />
<br />
Almost all of the features listed here are worth using whether or not the computer is on AC or battery power. Most have negligible performance impact and are just not enabled by default because of commonly broken hardware/drivers. Reducing power usage means reducing heat, which can even lead to higher performance on a modern Intel or AMD CPU, thanks to [[Wikipedia:Intel Turbo Boost|dynamic overclocking]].<br />
<br />
=== Processors with Intel HWP (Intel Hardware P-state) support ===<br />
<br />
{{Merge|CPU frequency scaling|More context in the main article.}}<br />
<br />
The available energy preferences of a HWP supported processor are {{ic|default performance balance_performance balance_power power}}.<br />
<br />
This can be validated by {{ic|$ cat /sys/devices/system/cpu/cpufreq/policy?/energy_performance_available_preferences}}<br />
<br />
To conserve more energy, you can config by creating the following file:<br />
<br />
{{hc|/etc/tmpfiles.d/energy_performance_preference.conf|<br />
w /sys/devices/system/cpu/cpufreq/policy?/energy_performance_preference - - - - balance_power<br />
}}<br />
<br />
See the {{man|8|systemd-tmpfiles}} and {{man|5|tmpfiles.d}} man pages for details.<br />
<br />
=== Audio ===<br />
<br />
==== Kernel ====<br />
By default, audio power saving is turned off by most drivers. It can be enabled by setting the {{ic|power_save}} parameter; a time (in seconds) to go into idle mode. To idle the audio card after one second, create the following file for Intel soundcards.<br />
<br />
{{hc|/etc/modprobe.d/audio_powersave.conf|2=<br />
options snd_hda_intel power_save=1<br />
}}<br />
<br />
Alternatively, use the following for ac97:<br />
<br />
options snd_ac97_codec power_save=1<br />
<br />
{{Note|<br />
* To retrieve the manufacturer and the corresponding kernel driver which is used for your sound card, run {{ic|lspci -k}}.<br />
* Toggling the audio card's power state can cause a popping sound or noticeable latency on some broken hardware.<br />
}}<br />
<br />
It is also possible to further reduce the audio power requirements by disabling the HDMI audio output, which can done by [[blacklisting]] the appropriate kernel modules (e.g. {{ic|snd_hda_codec_hdmi}} in case of Intel hardware).<br />
<br />
==== PulseAudio ====<br />
By default, PulseAudio suspends any audio sources that have become idle for too long. When using an external USB microphone, recordings may start with a pop sound. As a workaround, comment out the following line in {{ic|/etc/pulse/default.pa}}:<br />
<br />
load-module module-suspend-on-idle<br />
<br />
Afterwards, restart PulseAudio with {{ic|systemctl restart --user pulseaudio}}.<br />
<br />
=== Backlight ===<br />
<br />
See [[Backlight]].<br />
<br />
=== Bluetooth ===<br />
<br />
{{expansion|reason=The device should likely be disabled with hciconfig first.}}<br />
<br />
To disable bluetooth completely, [[blacklist]] the {{ic|btusb}} and {{ic|bluetooth}} modules.<br />
<br />
To turn off bluetooth only temporarily, use ''rfkill'':<br />
<br />
# rfkill block bluetooth<br />
<br />
Or with udev rule:<br />
<br />
{{hc|/etc/udev/rules.d/50-bluetooth.rules|<nowiki><br />
# disable bluetooth<br />
SUBSYSTEM=="rfkill", ATTR{type}=="bluetooth", ATTR{state}="0"<br />
</nowiki>}}<br />
<br />
=== Web camera ===<br />
<br />
If you will not use integrated web camera then [[blacklist]] the {{ic|uvcvideo}} module.<br />
<br />
=== Kernel parameters ===<br />
<br />
This section uses configs in {{ic|/etc/sysctl.d/}}, which is ''"a drop-in directory for kernel sysctl parameters."'' See [http://0pointer.de/blog/projects/the-new-configuration-files The New Configuration Files] and more specifically {{man|5|sysctl.d}} for more information.<br />
<br />
==== Disabling NMI watchdog ====<br />
<br />
{{Expansion|This or {{ic|nowatchdog}} as can be seen in [[Improving performance#Watchdogs]]}}<br />
<br />
The [[Wikipedia:Non-maskable interrupt|NMI]] watchdog is a debugging feature to catch hardware hangs that cause a kernel panic. On some systems it can generate a lot of interrupts, causing a noticeable increase in power usage:<br />
<br />
{{hc|/etc/sysctl.d/disable_watchdog.conf|2=<br />
kernel.nmi_watchdog = 0<br />
}}<br />
<br />
or add {{ic|1=nmi_watchdog=0}} to the [[kernel line]] to disable it completely from early boot.<br />
<br />
==== Writeback Time ====<br />
<br />
Increasing the virtual memory dirty writeback time helps to aggregate disk I/O together, thus reducing spanned disk writes, and increasing power saving. To set the value to 60 seconds (default is 5 seconds):<br />
<br />
{{hc|/etc/sysctl.d/dirty.conf|2=<br />
vm.dirty_writeback_centisecs = 6000<br />
}}<br />
<br />
To do the same for journal commits on supported filesystems (e.g. ext4, btrfs...), use {{ic|1=commit=60}} as a option in [[fstab]].<br />
<br />
Note that this value is modified as a side effect of the Laptop Mode setting below.<br />
See also [[sysctl#Virtual memory]] for other parameters affecting I/O performance and power saving.<br />
<br />
==== Laptop Mode ====<br />
<br />
See the [https://www.kernel.org/doc/html/latest/admin-guide/laptops/laptop-mode.html kernel documentation] on the laptop mode 'knob.' ''"A sensible value for the knob is 5 seconds."''<br />
<br />
{{hc|/etc/sysctl.d/laptop.conf|2=<br />
vm.laptop_mode = 5<br />
}}<br />
<br />
{{Note|This setting is mainly relevant to spinning-disk drives.}}<br />
<br />
=== Network interfaces ===<br />
<br />
[[Wake-on-LAN]] can be a useful feature, but if you are not making use of it then it is simply draining extra power waiting for a magic packet while in suspend. You can adapt the [[Wake-on-LAN#udev]] rule to disable the feature for all ethernet interfaces.<br />
To enable powersaving with {{Pkg|iw}} on all wireless interfaces:<br />
<br />
{{hc|/etc/udev/rules.d/'''81'''-wifi-powersave.rules|2=<br />
ACTION=="add", SUBSYSTEM=="net", KERNEL=="wl*", RUN+="/usr/bin/iw dev $name set power_save on"}}<br />
<br />
The name of the configuration file is important. With the use of [[Network configuration#Change interface name|persistent device names]] in systemd, the above network rule, named lexicographically '''after''' {{ic|80-net-setup-link.rules}}, is applied after the device is renamed with a persistent name e.g. {{ic|wlan0}} renamed {{ic|wlp3s0}}.<br />
Be aware that the {{ic|RUN}} command is executed after all rules have been processed and must anyway use the persistent name, available in {{ic|$name}} for the matched device.<br />
<br />
==== Intel wireless cards (iwlwifi) ====<br />
<br />
Additional power saving functions of Intel wireless cards with {{ic|iwlwifi}} driver can be enabled by passing the correct parameters to the kernel module. Making them persistent can be achieved by adding the lines below to the {{ic|/etc/modprobe.d/iwlwifi.conf}} file:<br />
<br />
options iwlwifi power_save=1<br />
<br />
This option will probably increase your median latency:<br />
<br />
options iwlwifi uapsd_disable=0<br />
<br />
On kernels < 5.4 you can use this option, but it will probably decrease your maximum throughput:<br />
<br />
options iwlwifi d0i3_disable=0<br />
<br />
Depending on your wireless card one of these two options will apply.<br />
<br />
options iwlmvm power_scheme=3<br />
<br />
options iwldvm force_cam=0<br />
<br />
You can check which one is relevant by checking which of these modules is running using<br />
<br />
# lsmod | grep '^iwl.vm'<br />
<br />
Keep in mind that these power saving options are experimental and can cause an unstable system.<br />
<br />
=== Bus power management ===<br />
<br />
==== Active State Power Management ====<br />
<br />
If the computer is believed not to support [[Wikipedia:Active State Power Management|ASPM]] it will be disabled on boot:<br />
<br />
# lspci -vv | grep 'ASPM.*abled;'<br />
<br />
ASPM is handled by the BIOS, if ASPM is disabled it will be because [https://wireless.wiki.kernel.org/en/users/documentation/ASPM]:<br />
<br />
# The BIOS disabled it for some reason (for conflicts?).<br />
# PCIE requires ASPM but L0s are optional (so L0s might be disabled and only L1 enabled).<br />
# The BIOS might not have been programmed for it.<br />
# The BIOS is buggy.<br />
<br />
If believing the computer has support for ASPM it can be forced on for the kernel to handle with the {{ic|1=pcie_aspm=force}} [[kernel parameter]].<br />
<br />
{{Warning|<br />
* Forcing on ASPM can cause a freeze/panic, so make sure you have a way to undo the option if it does not work.<br />
* On systems that do not support it forcing on ASPM can even increase power consumption.<br />
* This forces ASPM in kernel while it can still remain disabled in hardware and not work. To check whether this is the case the {{ic|dmesg {{!}} grep ASPM}} command can be used and if that is the case, hardware-specific Wiki article should be consulted.<br />
}}<br />
<br />
To adjust to {{ic|powersave}} do (the following command will not work unless enabled):<br />
<br />
# echo powersave > /sys/module/pcie_aspm/parameters/policy<br />
<br />
By default it looks like this:<br />
<br />
{{hc|$ cat /sys/module/pcie_aspm/parameters/policy|<br />
[default] performance powersave powersupersave<br />
}}<br />
<br />
==== PCI Runtime Power Management ====<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|2=<br />
SUBSYSTEM=="pci", ATTR{power/control}="auto"<br />
}}<br />
<br />
The rule above powers all unused devices down, but some devices will not wake up again.<br />
To allow runtime power management only for devices that are known to work, use simple matching against vendor and device IDs (use {{ic|lspci -nn}} to get these values):<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|<nowiki><br />
# whitelist for pci autosuspend<br />
SUBSYSTEM=="pci", ATTR{vendor}=="0x1234", ATTR{device}=="0x1234", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
Alternatively, to blacklist devices that are not working with PCI runtime power management and enable it for all other devices:<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|<nowiki><br />
# blacklist for pci runtime power management<br />
SUBSYSTEM=="pci", ATTR{vendor}=="0x1234", ATTR{device}=="0x1234", ATTR{power/control}="on", GOTO="pci_pm_end"<br />
<br />
SUBSYSTEM=="pci", ATTR{power/control}="auto"<br />
LABEL="pci_pm_end"<br />
</nowiki>}}<br />
<br />
==== USB autosuspend ====<br />
<br />
The Linux kernel can automatically suspend USB devices when they are not in use. This can sometimes save quite a bit of power, however some USB devices are not compatible with USB power saving and start to misbehave (common for USB mice/keyboards). [[udev]] rules based on whitelist or blacklist filtering can help to mitigate the problem.<br />
<br />
The most simple and likely useless example is enabling autosuspend for all USB devices:<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
To allow autosuspend only for devices that are known to work, use simple matching against vendor and product IDs (use ''lsusb'' to get these values):<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
# whitelist for usb autosuspend<br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{idVendor}=="05c6", ATTR{idProduct}=="9205", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
Alternatively, to blacklist devices that are not working with USB autosuspend and enable it for all other devices:<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
# blacklist for usb autosuspend<br />
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="9205", GOTO="power_usb_rules_end"<br />
<br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="auto"<br />
LABEL="power_usb_rules_end"<br />
</nowiki>}}<br />
<br />
The default autosuspend idle delay time is controlled by the {{ic|autosuspend}} parameter of the {{ic|usbcore}} built-in [[kernel module]]. To set the delay to 5 seconds instead of the default 2 seconds, add the following [[kernel parameter]] for your bootloader.<br />
<br />
{{bc|1=usbcore.autosuspend=5}}<br />
<br />
Similarly to {{ic|power/control}}, the delay time can be fine-tuned per device by setting the {{ic|power/autosuspend}} attribute.<br />
<br />
See the [https://www.kernel.org/doc/html/latest/driver-api/usb/power-management.html Linux kernel documentation] for more information on USB power management.<br />
<br />
==== SATA Active Link Power Management ====<br />
<br />
{{Warning|SATA Active Link Power Management can lead to data loss on some devices. Do not enable this setting unless you have frequent backups.}}<br />
<br />
{{Out of date|Phrases like "new setting" and "will become a default setting" are outdated. Also should be more formal. See [[Help:Style#Language register]].}}<br />
<br />
Since Linux 4.15 there is a [https://hansdegoede.livejournal.com/18412.html new setting] called {{ic|med_power_with_dipm}} that matches the behaviour of Windows IRST driver settings and should not cause data loss with recent SSD/HDD drives. The power saving can be significant, ranging [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebb82e3c79d2a956366d0848304a53648bd6350b from 1.0 to 1.5 Watts (when idle)]. It will become a default setting for Intel based laptops in Linux 4.16 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebb82e3c79d2a956366d0848304a53648bd6350b].<br />
<br />
The current setting can be read from {{ic|/sys/class/scsi_host/host*/link_power_management_policy}} as follows:<br />
<br />
$ cat /sys/class/scsi_host/host*/link_power_management_policy<br />
<br />
{| class="wikitable"<br />
|+ Available ALPM settings<br />
! Setting<br />
! Description<br />
! Power saving<br />
|-<br />
| max_performance<br />
| current default<br />
| None<br />
|-<br />
| medium_power<br />
| -<br />
| ~1.0 Watts<br />
|-<br />
| med_power_with_dipm<br />
| recommended setting<br />
| ~1.5 Watts<br />
|-<br />
| min_power<br />
| '''WARNING: possible data loss'''<br />
| ~1.5 Watts<br />
|}<br />
<br />
{{hc|/etc/udev/rules.d/hd_power_save.rules|2=<br />
ACTION=="add", SUBSYSTEM=="scsi_host", KERNEL=="host*", ATTR{link_power_management_policy}="med_power_with_dipm"<br />
}}<br />
<br />
{{Note|This adds latency when accessing a drive that has been idle, so it is one of the few settings that may be worth toggling based on whether you are on AC power.}}<br />
<br />
=== Hard disk drive ===<br />
<br />
See [[hdparm#Power management configuration]] for drive parameters that can be set.<br />
<br />
Power saving is not effective when too many programs are frequently writing to the disk. Tracking all programs, and how and when they write to disk is the way to limit disk usage. Use {{Pkg|iotop}} to see which programs use the disk frequently. See [[Improving performance#Storage devices]] for other tips.<br />
<br />
Also little things like setting the [[Fstab#atime options|noatime]] option can help. If enough RAM is available, consider disabling or limiting [[swappiness]] as it has the possibility to limit a good number of disk writes.<br />
<br />
=== CD-ROM or DVD drive ===<br />
<br />
See [[Udisks#Devices do not remain unmounted (udisks)]].<br />
<br />
== Tools and scripts ==<br />
<br />
{{Style|Merged from [[Power saving]], needs reorganization to fit into this page.}}<br />
<br />
=== Using a script and an udev rule ===<br />
<br />
Since systemd users can suspend and hibernate through {{ic|systemctl suspend}} or {{ic|systemctl hibernate}} and handle acpi events with {{ic|/etc/systemd/logind.conf}}, it might be interesting to remove ''pm-utils'' and [[acpid]]. There is just one thing systemd cannot do (as of systemd-204): power management depending on whether the system is running on AC or battery. To fill this gap, you can create a single [[udev]] rule that runs a script when the AC adapter is plugged and unplugged:<br />
<br />
{{hc|/etc/udev/rules.d/powersave.rules|2=<nowiki><br />
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/path/to/your/script true"<br />
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/path/to/your/script false"<br />
</nowiki>}}<br />
<br />
{{Note|You can use the same script that ''pm-powersave'' uses. You just have to make it executable and place it somewhere else (for example {{ic|/usr/local/bin/}}).}}<br />
<br />
Examples of powersave scripts:<br />
<br />
* [https://github.com/supplantr/ftw ftw], package: {{AUR|ftw-git}}<br />
* [https://github.com/Unia/powersave powersave]<br />
* [https://github.com/quequotion/pantheon-bzr-qq/blob/master/EXTRAS/indicator-powersave/throttle throttle], from {{AUR|indicator-powersave}}<br />
<br />
The above udev rule should work as expected, but if your power settings are not updated after a suspend or hibernate cycle, you should add a script in {{ic|/usr/lib/systemd/system-sleep/}} with the following contents:<br />
<br />
{{hc|/usr/lib/systemd/system-sleep/00powersave|<nowiki><br />
#!/bin/sh<br />
<br />
case $1 in<br />
pre) /path/to/your/script false ;;<br />
post) <br />
if cat /sys/class/power_supply/AC0/online | grep 0 > /dev/null 2>&1<br />
then<br />
/path/to/your/script true <br />
else<br />
/path/to/your/script false<br />
fi<br />
;;<br />
esac<br />
exit 0<br />
</nowiki>}}<br />
<br />
Do not forget to make it executable!<br />
<br />
{{Note|Be aware that AC0 may be different for your laptop, change it if that is the case.}}<br />
<br />
=== Print power settings ===<br />
<br />
This script prints power settings and a variety of other properties for USB and PCI devices. Note that root permissions are needed to see all settings.<br />
<br />
{{bc|<nowiki><br />
#!/bin/bash<br />
<br />
for i in $(find /sys/devices -name "bMaxPower")<br />
do<br />
busdir=${i%/*}<br />
busnum=$(<$busdir/busnum)<br />
devnum=$(<$busdir/devnum)<br />
title=$(lsusb -s $busnum:$devnum)<br />
<br />
printf "\n\n+++ %s\n -%s\n" "$title" "$busdir"<br />
<br />
for ff in $(find $busdir/power -type f ! -empty 2>/dev/null)<br />
do<br />
v=$(cat $ff 2>/dev/null|tr -d "\n")<br />
[[ ${#v} -gt 0 ]] && echo -e " ${ff##*/}=$v";<br />
v=;<br />
done | sort -g;<br />
done;<br />
<br />
printf "\n\n\n+++ %s\n" "Kernel Modules"<br />
for mod in $(lspci -k | sed -n '/in use:/s,^.*: ,,p' | sort -u)<br />
do<br />
echo "+ $mod";<br />
systool -v -m $mod 2> /dev/null | sed -n "/Parameters:/,/^$/p";<br />
done<br />
</nowiki>}}<br />
<br />
== See also ==<br />
<br />
* [http://www.thinkwiki.org/wiki/How_to_reduce_power_consumption ThinkWiki:How to reduce power consumption]<br />
* [http://ivanvojtko.blogspot.sk/2016/04/how-to-get-longer-battery-life-on-linux.html How to get longer battery life on Linux]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Power_management&diff=655039Power management2021-03-15T18:11:59Z<p>DonJaime: /* Kernel parameters */ correct sysctl property to disable watchdog</p>
<hr />
<div>[[Category:Power management]]<br />
[[es:Power management]]<br />
[[ja:電源管理]]<br />
[[zh-hans:Power management]]<br />
{{Related articles start}}<br />
{{Related|Power management/Suspend and hibernate}}<br />
{{Related|Display Power Management Signaling}}<br />
{{Related|CPU frequency scaling}}<br />
{{Related|Hybrid graphics}}<br />
{{Related|Kernel modules}}<br />
{{Related|sysctl}}<br />
{{Related|udev}}<br />
{{Related articles end}}<br />
[[Wikipedia:Power management|Power management]] is a feature that turns off the power or switches system's components to a low-power state when inactive.<br />
<br />
In Arch Linux, power management consists of two main parts:<br />
<br />
# Configuration of the Linux kernel, which interacts with the hardware.<br />
#* [[Kernel parameters]]<br />
#* [[Kernel modules]]<br />
#* [[udev]] rules<br />
# Configuration of userspace tools, which interact with the kernel and react to its events. Many userspace tools also allow to modify kernel configuration in a "user-friendly" way. See [[#Userspace tools]] for the options.<br />
<br />
== Userspace tools ==<br />
<br />
Using these tools can replace setting a lot of settings by hand. Only run '''one''' of these tools to avoid possible conflicts as they all work more or less similarly. Have a look at the [[:Category:Power management|power management category]] to get an overview on what power management options exist in Arch Linux.<br />
<br />
These are the more popular scripts and tools designed to help power saving:<br />
<br />
=== Console ===<br />
<br />
* {{App|[[acpid]]| A daemon for delivering ACPI power management events with netlink support.|https://sourceforge.net/projects/acpid2/|{{Pkg|acpid}}}}<br />
* {{App|[[Laptop Mode Tools]]|Utility to configure laptop power saving settings, considered by many to be the de facto utility for power saving though may take a bit of configuration.|https://github.com/rickysarraf/laptop-mode-tools|{{AUR|laptop-mode-tools}}}}<br />
* {{App|libsmbios|Library and tools for interacting with Dell SMBIOS tables.|https://github.com/dell/libsmbios|{{Pkg|libsmbios}}}}<br />
* {{App|[[powertop]]|A tool to diagnose issues with power consumption and power management to help set power saving settings.|https://01.org/powertop/|{{Pkg|powertop}}}}<br />
* {{App|[[systemd]]|A system and service manager.|https://freedesktop.org/wiki/Software/systemd/|{{Pkg|systemd}}}}<br />
* {{App|[[TLP]]|Advanced power management for Linux.|http://linrunner.de/tlp|{{Pkg|tlp}}}}<br />
<br />
=== Graphical ===<br />
<br />
* {{App|batterymon-clone|Simple battery monitor tray icon.|https://github.com/jareksed/batterymon-clone|{{AUR|batterymon-clone}}}}<br />
* {{App|batsignal|Lightweight battery monitor that uses libnotify to warn of low battery levels.|https://github.com/electrickite/batsignal|{{AUR|batsignal}}}}<br />
* {{App|cbatticon|Lightweight and fast battery icon that sits in your system tray.|https://github.com/valr/cbatticon|{{Pkg|cbatticon}}}}<br />
* {{App|GNOME Power Statistics|System power information and statistics for GNOME.|https://gitlab.gnome.org/GNOME/gnome-power-manager|{{Pkg|gnome-power-manager}}}}<br />
* {{App|KDE Power Devil|Power management module for Plasma.|https://invent.kde.org/plasma/powerdevil|{{Pkg|powerdevil}}}}<br />
* {{App|LXQt Power Management|Power management module for LXQt.|https://github.com/lxqt/lxqt-powermanagement|{{Pkg|lxqt-powermanagement}}}}<br />
* {{App|MATE Power Management|Power management tool for MATE.|https://github.com/mate-desktop/mate-power-manager|{{Pkg|mate-power-manager}}}}<br />
* {{App|MATE Power Statistics|System power information and statistics for MATE.|https://github.com/mate-desktop/mate-power-manager|{{Pkg|mate-power-manager}}}}<br />
* {{App|powerkit|Desktop independent power manager.|https://github.com/rodlie/powerkit|{{AUR|powerkit}}}}<br />
* {{App|Xfce Power Manager|Power manager for Xfce.|https://docs.xfce.org/xfce/xfce4-power-manager/start|{{Pkg|xfce4-power-manager}}}}<br />
* {{App|vattery|Battery monitoring application written in Vala that will display the status of a laptop battery in a system tray.|https://www.jezra.net/projects/vattery.html|{{AUR|vattery}}}}<br />
<br />
== Power management with systemd ==<br />
<br />
=== ACPI events ===<br />
<br />
''systemd'' handles some power-related [[Wikipedia:Advanced_Configuration_and_Power_Interface|ACPI]] events, whose actions can be configured in {{ic|/etc/systemd/logind.conf}} or {{ic|/etc/systemd/logind.conf.d/*.conf}} — see {{man|5|logind.conf}}. On systems with no dedicated power manager, this may replace the [[acpid]] daemon which is usually used to react to these ACPI events.<br />
<br />
The specified action for each event can be one of {{ic|ignore}}, {{ic|poweroff}}, {{ic|reboot}}, {{ic|halt}}, {{ic|suspend}}, {{ic|hibernate}}, {{ic|hybrid-sleep}}, {{ic|suspend-then-hibernate}}, {{ic|lock}} or {{ic|kexec}}. In case of hibernation and suspension, they must be properly [[Power management/Suspend and hibernate|set up]]. If an event is not configured, ''systemd'' will use a default action.<br />
<br />
{| class="wikitable sortable" border=1<br />
!Event handler<br />
!Description<br />
!Default action<br />
|-<br />
|{{ic|HandlePowerKey}}<br />
|Triggered when the power key/button is pressed.<br />
|{{ic|poweroff}}<br />
|-<br />
|{{ic|HandleSuspendKey}}<br />
|Triggered when the suspend key/button is pressed.<br />
|{{ic|suspend}}<br />
|-<br />
|{{ic|HandleHibernateKey}}<br />
|Triggered when the hibernate key/button is pressed.<br />
|{{ic|hibernate}}<br />
|-<br />
|{{ic|HandleLidSwitch}}<br />
|Triggered when the lid is closed, except in the cases below.<br />
|{{ic|suspend}}<br />
|-<br />
|{{ic|HandleLidSwitchDocked}}<br />
|Triggered when the lid is closed if the system is inserted in a docking station, or more than one display is connected.<br />
|{{ic|ignore}}<br />
|-<br />
|{{ic|HandleLidSwitchExternalPower}}<br />
|Triggered when the lid is closed if the system is connected to external power.<br />
|action set for {{ic|HandleLidSwitch}}<br />
|}<br />
<br />
To apply any changes, signal {{ic|systemd-logind}} with {{ic|HUP}}:<br />
<br />
# systemctl kill -s HUP systemd-logind<br />
<br />
{{Note|''systemd'' cannot handle AC and Battery ACPI events, so if you use [[Laptop Mode Tools]] or other similar tools [[acpid]] is still required.}}<br />
<br />
==== Power managers ====<br />
<br />
Some [[desktop environment]]s include power managers which [https://www.freedesktop.org/wiki/Software/systemd/inhibit/ inhibit] (temporarily turn off) some or all of the ''systemd'' ACPI settings. If such a power manager is running, then the actions for ACPI events can be configured in the power manager alone. Changes to {{ic|/etc/systemd/logind.conf}} or {{ic|/etc/systemd/logind.conf.d/*.conf}} need be made only if you wish to configure behaviour for a particular event that is not inhibited by the power manager. <br />
<br />
Note that if the power manager does not inhibit ''systemd'' for the appropriate events you can end up with a situation where ''systemd'' suspends your system and then when the system is woken up the other power manager suspends it again. As of December 2016, the power managers of [[KDE]], [[GNOME]], [[Xfce]] and [[MATE]] issue the necessary ''inhibited'' commands. If the ''inhibited'' commands are not being issued, such as when using [[acpid]] or others to handle ACPI events, set the {{ic|Handle}} options to {{ic|ignore}}. See also {{man|1|systemd-inhibit}}.<br />
<br />
==== xss-lock ====<br />
<br />
{{pkg|xss-lock}} subscribes to the systemd-events {{ic|suspend}}, {{ic|hibernate}}, {{ic|lock-session}}, and {{ic|unlock-session}} with appropriate actions (run locker and wait for user to unlock or kill locker). ''xss-lock'' also reacts to [[DPMS]] events and runs or kills the locker in response.<br />
<br />
Start xss-lock in your [[autostart]], for example<br />
<br />
xss-lock -- i3lock -n -i ''background_image.png'' &<br />
<br />
=== Suspend and hibernate ===<br />
<br />
''systemd'' provides commands to suspend to RAM or hibernate using the kernel's native suspend/resume functionality. There are also mechanisms to add hooks to customize pre- and post-suspend actions.<br />
<br />
{{ic|systemctl suspend}} should work out of the box, for {{ic|systemctl hibernate}} to work on your system you need to follow the instructions at [[Suspend and hibernate#Hibernation]].<br />
<br />
There are also two modes combining suspend and hibernate:<br />
<br />
* {{ic|systemctl hybrid-sleep}} suspends the system both to RAM and disk, so a complete power loss does not result in lost data. This mode is also called [[Power management/Suspend and hibernate|suspend to both]].<br />
* {{ic|systemctl suspend-then-hibernate}} initially suspends the system to RAM and if it is not interrupted within the delay specified by {{ic|HibernateDelaySec}} in {{man|5|systemd-sleep.conf}}, then the system will be woken using an RTC alarm and hibernated.<br />
<br />
{{Note|''systemd'' can also use other suspend backends (such as [[Uswsusp]]), in addition to the default ''kernel'' backend, in order to put the computer to sleep or hibernate. See [[Uswsusp#With systemd]] for an example.}}<br />
<br />
==== Hybrid-sleep on suspend or hibernation request ====<br />
<br />
It is possible to configure systemd to always do a ''hybrid-sleep'' even on a ''suspend'' or ''hibernation'' request.<br />
<br />
The default ''suspend'' and ''hibernation'' action can be configured in the {{ic|/etc/systemd/sleep.conf}} file. To set both actions to ''hybrid-sleep'':<br />
<br />
{{hc|/etc/systemd/sleep.conf|2=<br />
[Sleep]<br />
# suspend=hybrid-sleep<br />
SuspendMode=suspend<br />
SuspendState=disk<br />
# hibernate=hybrid-sleep<br />
HibernateMode=suspend<br />
HibernateState=disk<br />
}}<br />
<br />
See the {{man|5|sleep.conf.d}} manual page for details and the [https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html#basic-sysfs-interfaces-for-system-suspend-and-hibernation linux kernel documentation on power states].<br />
<br />
=== Sleep hooks ===<br />
<br />
==== Suspend/resume service files ====<br />
<br />
Service files can be hooked into ''suspend.target'', ''hibernate.target'', ''sleep.target'', ''hybrid-sleep.target'' and ''suspend-then-hibernate.target'' to execute actions before or after suspend/hibernate. Separate files should be created for user actions and root/system actions. [[Enable]] the {{ic|suspend@''user''}} and {{ic|resume@''user''}} services to have them started at boot. Examples:<br />
<br />
{{hc|/etc/systemd/system/suspend@.service|2=<br />
[Unit]<br />
Description=User suspend actions<br />
Before=sleep.target<br />
<br />
[Service]<br />
User=%I<br />
Type=forking<br />
Environment=DISPLAY=:0<br />
ExecStartPre= -/usr/bin/pkill -u %u unison ; /usr/local/bin/music.sh stop<br />
ExecStart=/usr/bin/sflock<br />
ExecStartPost=/usr/bin/sleep 1<br />
<br />
[Install]<br />
WantedBy=sleep.target<br />
}}<br />
<br />
{{hc|/etc/systemd/system/resume@.service|2=<br />
[Unit]<br />
Description=User resume actions<br />
After=suspend.target<br />
<br />
[Service]<br />
User=%I<br />
Type=simple<br />
ExecStart=/usr/local/bin/ssh-connect.sh<br />
<br />
[Install]<br />
WantedBy=suspend.target}}<br />
<br />
{{Note|As screen lockers may return before the screen is "locked", the screen may flash on resuming from suspend. Adding a small delay via {{ic|1=ExecStartPost=/usr/bin/sleep 1}} helps prevent this.}}<br />
<br />
For root/system actions ([[enable]] the {{ic|root-resume}} and {{ic|root-suspend}} services to have them started at boot):<br />
<br />
{{hc|/etc/systemd/system/root-suspend.service|2=<br />
[Unit]<br />
Description=Local system suspend actions<br />
Before=sleep.target<br />
<br />
[Service]<br />
Type=simple<br />
ExecStart=-/usr/bin/pkill sshfs<br />
<br />
[Install]<br />
WantedBy=sleep.target}}<br />
<br />
{{hc|/etc/systemd/system/root-resume.service|2=<br />
[Unit]<br />
Description=Local system resume actions<br />
After=suspend.target<br />
<br />
[Service]<br />
Type=simple<br />
ExecStart=/usr/bin/systemctl restart mnt-media.automount<br />
<br />
[Install]<br />
WantedBy=suspend.target}}<br />
<br />
{{Tip|A couple of handy hints about these service files (more in {{man|5|systemd.service}}):<br />
<br />
* If {{ic|1=<nowiki>Type=oneshot</nowiki>}} then you can use multiple {{ic|1=<nowiki>ExecStart=</nowiki>}} lines. Otherwise only one {{ic|ExecStart}} line is allowed. You can add more commands with either {{ic|ExecStartPre}} or by separating commands with a semicolon (see the first example above; note the spaces before and after the semicolon, as they are ''required'').<br />
* A command prefixed with {{ic|-}} will cause a non-zero exit status to be ignored and treated as a successful command. <br />
* The best place to find errors when troubleshooting these service files is of course with [[journalctl]].<br />
}}<br />
<br />
==== Combined Suspend/resume service file ====<br />
<br />
With the combined suspend/resume service file, a single hook does all the work for different phases (sleep/resume) and for different targets (suspend/hibernate/hybrid-sleep).<br />
<br />
Example and explanation:<br />
<br />
{{hc|/etc/systemd/system/wicd-sleep.service|2=<nowiki><br />
[Unit]<br />
Description=Wicd sleep hook<br />
Before=sleep.target<br />
StopWhenUnneeded=yes<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=yes<br />
ExecStart=-/usr/share/wicd/daemon/suspend.py<br />
ExecStop=-/usr/share/wicd/daemon/autoconnect.py<br />
<br />
[Install]<br />
WantedBy=sleep.target<br />
</nowiki>}}<br />
<br />
* {{ic|1=<nowiki>RemainAfterExit=yes</nowiki>}}: After started, the service is considered active until it is explicitly stopped.<br />
* {{ic|1=<nowiki>StopWhenUnneeded=yes</nowiki>}}: When active, the service will be stopped if no other active service requires it. In this specific example, it will be stopped after ''sleep.target'' is stopped.<br />
* Because ''sleep.target'' is pulled in by ''suspend.target'', ''hibernate.target'' and ''hybrid-sleep.target'' and because ''sleep.target'' itself is a ''StopWhenUnneeded'' service, the hook is guaranteed to start/stop properly for different tasks.<br />
<br />
===== Generic service template =====<br />
<br />
In this example, we create a [http://0pointer.net/blog/projects/instances.html template service] which we can then use to hook any existing systemd service to power events:[https://narkive.com/mYzxSIDN.6]<br />
<br />
{{hc|/etc/systemd/system/sleep@.service|2=<br />
[Unit]<br />
Description=%I sleep hook<br />
Before=sleep.target<br />
StopWhenUnneeded=yes<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=yes<br />
ExecStart=-/usr/bin/systemctl stop %i<br />
ExecStop=-/usr/bin/systemctl start %i<br />
<br />
[Install]<br />
WantedBy=sleep.target}}<br />
<br />
Then [[enable]] an instance of this template by specifying the basename of an existing systemd service after the @:<br />
<br />
# systemctl enable sleep@'''''service-file-basename'''''.service<br />
<br />
See {{man|5|systemd.unit|DESCRIPTION}} for more details on templates.<br />
<br />
{{Tip|Templates are not limited to systemd services and can be used with other programs/ See [https://fedoramagazine.org/systemd-template-unit-files/] for some examples.}}<br />
<br />
==== Hooks in /usr/lib/systemd/system-sleep ====<br />
<br />
''systemd'' runs all executables in {{ic|/usr/lib/systemd/system-sleep/}}, passing two arguments to each of them:<br />
<br />
* Argument 1: either {{ic|pre}} or {{ic|post}}, depending on whether the machine is going to sleep or waking up<br />
* Argument 2: {{ic|suspend}}, {{ic|hibernate}} or {{ic|hybrid-sleep}}, depending on which is being invoked<br />
<br />
''systemd'' will run these scripts concurrently and not one after another.<br />
<br />
The output of any custom script will be logged by ''systemd-suspend.service'', ''systemd-hibernate.service'' or ''systemd-hybrid-sleep.service''. You can see its output in ''systemd''<nowiki>'</nowiki>s [[journalctl]]:<br />
<br />
# journalctl -b -u systemd-suspend.service<br />
<br />
{{Note|You can also use ''sleep.target'', ''suspend.target'', ''hibernate.target'' or ''hybrid-sleep.target'' to hook units into the sleep state logic instead of using custom scripts.}}<br />
<br />
An example of a custom sleep script:<br />
<br />
{{hc|/usr/lib/systemd/system-sleep/example.sh|<br />
#!/bin/sh<br />
case $1/$2 in<br />
pre/*)<br />
echo "Going to $2..."<br />
;;<br />
post/*)<br />
echo "Waking up from $2..."<br />
;;<br />
esac<br />
}}<br />
<br />
Do not forget to make your script executable:<br />
<br />
# chmod a+x /usr/lib/systemd/system-sleep/example.sh<br />
<br />
See {{man|7|systemd.special}} and {{man|8|systemd-sleep}} for more details.<br />
<br />
=== Troubleshooting ===<br />
<br />
==== Delayed lid switch action ====<br />
<br />
When performing lid switches in short succession, ''logind'' will delay the suspend action for up to 90s to detect possible docks. [https://lists.freedesktop.org/archives/systemd-devel/2015-January/027131.html] This delay was made configurable with systemd v220:[https://github.com/systemd/systemd/commit/9d10cbee89ca7f82d29b9cb27bef11e23e3803ba]<br />
<br />
{{hc|/etc/systemd/logind.conf|2=<br />
...<br />
HoldoffTimeoutSec=30s<br />
...<br />
}}<br />
<br />
==== Suspend from corresponding laptop Fn key not working ====<br />
<br />
If, regardless of the setting in logind.conf, the sleep button does not work (pressing it does not even produce a message in syslog), then logind is probably not watching the keyboard device. [https://lists.freedesktop.org/archives/systemd-devel/2015-February/028325.html] Do:<br />
<br />
# journalctl --grep="Watching system buttons"<br />
<br />
You might see something like this:<br />
<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event2 (Power Button)<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event3 (Sleep Button)<br />
May 25 21:28:19 vmarch.lan systemd-logind[210]: Watching system buttons on /dev/input/event4 (Video Bus)<br />
<br />
Notice no keyboard device. Now obtain ATTRS{name} for the parent keyboard device [http://systemd-devel.freedesktop.narkive.com/Rbi3rjNN/patch-1-2-logind-add-support-for-tps65217-power-button] :<br />
<br />
{{hc|# udevadm info -a /dev/input/by-path/*-kbd|2=<br />
...<br />
KERNEL=="event0"<br />
...<br />
ATTRS{name}=="AT Translated Set 2 keyboard"<br />
}}<br />
<br />
Now write a custom udev rule to add the "power-switch" tag:<br />
<br />
{{hc|/etc/udev/rules.d/70-power-switch-my.rules|<nowiki><br />
ACTION=="remove", GOTO="power_switch_my_end"<br />
SUBSYSTEM=="input", KERNEL=="event*", ATTRS{name}=="AT Translated Set 2 keyboard", TAG+="power-switch"<br />
LABEL="power_switch_my_end"<br />
</nowiki>}}<br />
<br />
{{Style|Explicit {{ic|systemctl}} commands should not be provided.}}<br />
<br />
Restart services and reload rules:<br />
<br />
# systemctl restart systemd-udevd.service<br />
# udevadm trigger<br />
# systemctl restart systemd-logind.service<br />
<br />
Now you should see {{ic|Watching system buttons on /dev/input/event0}} in syslog.<br />
<br />
== Power saving ==<br />
<br />
{{Note|See [[Laptop#Power management]] for power management specific to laptops, such as battery monitoring.}}<br />
<br />
This section is a reference for creating custom scripts and power saving settings such as by udev rules. Make sure that the settings are not managed by some [[#Userspace tools|other utility]] to avoid conflicts.<br />
<br />
Almost all of the features listed here are worth using whether or not the computer is on AC or battery power. Most have negligible performance impact and are just not enabled by default because of commonly broken hardware/drivers. Reducing power usage means reducing heat, which can even lead to higher performance on a modern Intel or AMD CPU, thanks to [[Wikipedia:Intel Turbo Boost|dynamic overclocking]].<br />
<br />
=== Processors with Intel HWP (Intel Hardware P-state) support ===<br />
<br />
{{Merge|CPU frequency scaling|More context in the main article.}}<br />
<br />
The available energy preferences of a HWP supported processor are {{ic|default performance balance_performance balance_power power}}.<br />
<br />
This can be validated by {{ic|$ cat /sys/devices/system/cpu/cpufreq/policy?/energy_performance_available_preferences}}<br />
<br />
To conserve more energy, you can config by creating the following file:<br />
<br />
{{hc|/etc/tmpfiles.d/energy_performance_preference.conf|<br />
w /sys/devices/system/cpu/cpufreq/policy?/energy_performance_preference - - - - balance_power<br />
}}<br />
<br />
See the {{man|8|systemd-tmpfiles}} and {{man|5|tmpfiles.d}} man pages for details.<br />
<br />
=== Audio ===<br />
<br />
==== Kernel ====<br />
By default, audio power saving is turned off by most drivers. It can be enabled by setting the {{ic|power_save}} parameter; a time (in seconds) to go into idle mode. To idle the audio card after one second, create the following file for Intel soundcards.<br />
<br />
{{hc|/etc/modprobe.d/audio_powersave.conf|2=<br />
options snd_hda_intel power_save=1<br />
}}<br />
<br />
Alternatively, use the following for ac97:<br />
<br />
options snd_ac97_codec power_save=1<br />
<br />
{{Note|<br />
* To retrieve the manufacturer and the corresponding kernel driver which is used for your sound card, run {{ic|lspci -k}}.<br />
* Toggling the audio card's power state can cause a popping sound or noticeable latency on some broken hardware.<br />
}}<br />
<br />
It is also possible to further reduce the audio power requirements by disabling the HDMI audio output, which can done by [[blacklisting]] the appropriate kernel modules (e.g. {{ic|snd_hda_codec_hdmi}} in case of Intel hardware).<br />
<br />
==== PulseAudio ====<br />
By default, PulseAudio suspends any audio sources that have become idle for too long. When using an external USB microphone, recordings may start with a pop sound. As a workaround, comment out the following line in {{ic|/etc/pulse/default.pa}}:<br />
<br />
load-module module-suspend-on-idle<br />
<br />
Afterwards, restart PulseAudio with {{ic|systemctl restart --user pulseaudio}}.<br />
<br />
=== Backlight ===<br />
<br />
See [[Backlight]].<br />
<br />
=== Bluetooth ===<br />
<br />
{{expansion|reason=The device should likely be disabled with hciconfig first.}}<br />
<br />
To disable bluetooth completely, [[blacklist]] the {{ic|btusb}} and {{ic|bluetooth}} modules.<br />
<br />
To turn off bluetooth only temporarily, use ''rfkill'':<br />
<br />
# rfkill block bluetooth<br />
<br />
Or with udev rule:<br />
<br />
{{hc|/etc/udev/rules.d/50-bluetooth.rules|<nowiki><br />
# disable bluetooth<br />
SUBSYSTEM=="rfkill", ATTR{type}=="bluetooth", ATTR{state}="0"<br />
</nowiki>}}<br />
<br />
=== Web camera ===<br />
<br />
If you will not use integrated web camera then [[blacklist]] the {{ic|uvcvideo}} module.<br />
<br />
=== Kernel parameters ===<br />
<br />
This section uses configs in {{ic|/etc/sysctl.d/}}, which is ''"a drop-in directory for kernel sysctl parameters."'' See [http://0pointer.de/blog/projects/the-new-configuration-files The New Configuration Files] and more specifically {{man|5|sysctl.d}} for more information.<br />
<br />
==== Disabling NMI watchdog ====<br />
<br />
{{Expansion|This or {{ic|nowatchdog}} as can be seen in [[Improving performance#Watchdogs]]}}<br />
<br />
The [[Wikipedia:Non-maskable interrupt|NMI]] watchdog is a debugging feature to catch hardware hangs that cause a kernel panic. On some systems it can generate a lot of interrupts, causing a noticeable increase in power usage:<br />
<br />
{{hc|/etc/sysctl.d/disable_watchdog.conf|2=<br />
kernel.watchdog = 0<br />
}}<br />
<br />
or add {{ic|1=nmi_watchdog=0}} to the [[kernel line]] to disable it completely from early boot.<br />
<br />
==== Writeback Time ====<br />
<br />
Increasing the virtual memory dirty writeback time helps to aggregate disk I/O together, thus reducing spanned disk writes, and increasing power saving. To set the value to 60 seconds (default is 5 seconds):<br />
<br />
{{hc|/etc/sysctl.d/dirty.conf|2=<br />
vm.dirty_writeback_centisecs = 6000<br />
}}<br />
<br />
To do the same for journal commits on supported filesystems (e.g. ext4, btrfs...), use {{ic|1=commit=60}} as a option in [[fstab]].<br />
<br />
Note that this value is modified as a side effect of the Laptop Mode setting below.<br />
See also [[sysctl#Virtual memory]] for other parameters affecting I/O performance and power saving.<br />
<br />
==== Laptop Mode ====<br />
<br />
See the [https://www.kernel.org/doc/html/latest/admin-guide/laptops/laptop-mode.html kernel documentation] on the laptop mode 'knob.' ''"A sensible value for the knob is 5 seconds."''<br />
<br />
{{hc|/etc/sysctl.d/laptop.conf|2=<br />
vm.laptop_mode = 5<br />
}}<br />
<br />
{{Note|This setting is mainly relevant to spinning-disk drives.}}<br />
<br />
=== Network interfaces ===<br />
<br />
[[Wake-on-LAN]] can be a useful feature, but if you are not making use of it then it is simply draining extra power waiting for a magic packet while in suspend. You can adapt the [[Wake-on-LAN#udev]] rule to disable the feature for all ethernet interfaces.<br />
To enable powersaving with {{Pkg|iw}} on all wireless interfaces:<br />
<br />
{{hc|/etc/udev/rules.d/'''81'''-wifi-powersave.rules|2=<br />
ACTION=="add", SUBSYSTEM=="net", KERNEL=="wl*", RUN+="/usr/bin/iw dev $name set power_save on"}}<br />
<br />
The name of the configuration file is important. With the use of [[Network configuration#Change interface name|persistent device names]] in systemd, the above network rule, named lexicographically '''after''' {{ic|80-net-setup-link.rules}}, is applied after the device is renamed with a persistent name e.g. {{ic|wlan0}} renamed {{ic|wlp3s0}}.<br />
Be aware that the {{ic|RUN}} command is executed after all rules have been processed and must anyway use the persistent name, available in {{ic|$name}} for the matched device.<br />
<br />
==== Intel wireless cards (iwlwifi) ====<br />
<br />
Additional power saving functions of Intel wireless cards with {{ic|iwlwifi}} driver can be enabled by passing the correct parameters to the kernel module. Making them persistent can be achieved by adding the lines below to the {{ic|/etc/modprobe.d/iwlwifi.conf}} file:<br />
<br />
options iwlwifi power_save=1<br />
<br />
This option will probably increase your median latency:<br />
<br />
options iwlwifi uapsd_disable=0<br />
<br />
On kernels < 5.4 you can use this option, but it will probably decrease your maximum throughput:<br />
<br />
options iwlwifi d0i3_disable=0<br />
<br />
Depending on your wireless card one of these two options will apply.<br />
<br />
options iwlmvm power_scheme=3<br />
<br />
options iwldvm force_cam=0<br />
<br />
You can check which one is relevant by checking which of these modules is running using<br />
<br />
# lsmod | grep '^iwl.vm'<br />
<br />
Keep in mind that these power saving options are experimental and can cause an unstable system.<br />
<br />
=== Bus power management ===<br />
<br />
==== Active State Power Management ====<br />
<br />
If the computer is believed not to support [[Wikipedia:Active State Power Management|ASPM]] it will be disabled on boot:<br />
<br />
# lspci -vv | grep 'ASPM.*abled;'<br />
<br />
ASPM is handled by the BIOS, if ASPM is disabled it will be because [https://wireless.wiki.kernel.org/en/users/documentation/ASPM]:<br />
<br />
# The BIOS disabled it for some reason (for conflicts?).<br />
# PCIE requires ASPM but L0s are optional (so L0s might be disabled and only L1 enabled).<br />
# The BIOS might not have been programmed for it.<br />
# The BIOS is buggy.<br />
<br />
If believing the computer has support for ASPM it can be forced on for the kernel to handle with the {{ic|1=pcie_aspm=force}} [[kernel parameter]].<br />
<br />
{{Warning|<br />
* Forcing on ASPM can cause a freeze/panic, so make sure you have a way to undo the option if it does not work.<br />
* On systems that do not support it forcing on ASPM can even increase power consumption.<br />
* This forces ASPM in kernel while it can still remain disabled in hardware and not work. To check whether this is the case the {{ic|dmesg {{!}} grep ASPM}} command can be used and if that is the case, hardware-specific Wiki article should be consulted.<br />
}}<br />
<br />
To adjust to {{ic|powersave}} do (the following command will not work unless enabled):<br />
<br />
# echo powersave > /sys/module/pcie_aspm/parameters/policy<br />
<br />
By default it looks like this:<br />
<br />
{{hc|$ cat /sys/module/pcie_aspm/parameters/policy|<br />
[default] performance powersave powersupersave<br />
}}<br />
<br />
==== PCI Runtime Power Management ====<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|2=<br />
SUBSYSTEM=="pci", ATTR{power/control}="auto"<br />
}}<br />
<br />
The rule above powers all unused devices down, but some devices will not wake up again.<br />
To allow runtime power management only for devices that are known to work, use simple matching against vendor and device IDs (use {{ic|lspci -nn}} to get these values):<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|<nowiki><br />
# whitelist for pci autosuspend<br />
SUBSYSTEM=="pci", ATTR{vendor}=="0x1234", ATTR{device}=="0x1234", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
Alternatively, to blacklist devices that are not working with PCI runtime power management and enable it for all other devices:<br />
<br />
{{hc|/etc/udev/rules.d/pci_pm.rules|<nowiki><br />
# blacklist for pci runtime power management<br />
SUBSYSTEM=="pci", ATTR{vendor}=="0x1234", ATTR{device}=="0x1234", ATTR{power/control}="on", GOTO="pci_pm_end"<br />
<br />
SUBSYSTEM=="pci", ATTR{power/control}="auto"<br />
LABEL="pci_pm_end"<br />
</nowiki>}}<br />
<br />
==== USB autosuspend ====<br />
<br />
The Linux kernel can automatically suspend USB devices when they are not in use. This can sometimes save quite a bit of power, however some USB devices are not compatible with USB power saving and start to misbehave (common for USB mice/keyboards). [[udev]] rules based on whitelist or blacklist filtering can help to mitigate the problem.<br />
<br />
The most simple and likely useless example is enabling autosuspend for all USB devices:<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
To allow autosuspend only for devices that are known to work, use simple matching against vendor and product IDs (use ''lsusb'' to get these values):<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
# whitelist for usb autosuspend<br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{idVendor}=="05c6", ATTR{idProduct}=="9205", ATTR{power/control}="auto"<br />
</nowiki>}}<br />
<br />
Alternatively, to blacklist devices that are not working with USB autosuspend and enable it for all other devices:<br />
<br />
{{hc|/etc/udev/rules.d/50-usb_power_save.rules|<nowiki><br />
# blacklist for usb autosuspend<br />
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="9205", GOTO="power_usb_rules_end"<br />
<br />
ACTION=="add", SUBSYSTEM=="usb", TEST=="power/control", ATTR{power/control}="auto"<br />
LABEL="power_usb_rules_end"<br />
</nowiki>}}<br />
<br />
The default autosuspend idle delay time is controlled by the {{ic|autosuspend}} parameter of the {{ic|usbcore}} built-in [[kernel module]]. To set the delay to 5 seconds instead of the default 2 seconds, add the following [[kernel parameter]] for your bootloader.<br />
<br />
{{bc|1=usbcore.autosuspend=5}}<br />
<br />
Similarly to {{ic|power/control}}, the delay time can be fine-tuned per device by setting the {{ic|power/autosuspend}} attribute.<br />
<br />
See the [https://www.kernel.org/doc/html/latest/driver-api/usb/power-management.html Linux kernel documentation] for more information on USB power management.<br />
<br />
==== SATA Active Link Power Management ====<br />
<br />
{{Warning|SATA Active Link Power Management can lead to data loss on some devices. Do not enable this setting unless you have frequent backups.}}<br />
<br />
{{Out of date|Phrases like "new setting" and "will become a default setting" are outdated. Also should be more formal. See [[Help:Style#Language register]].}}<br />
<br />
Since Linux 4.15 there is a [https://hansdegoede.livejournal.com/18412.html new setting] called {{ic|med_power_with_dipm}} that matches the behaviour of Windows IRST driver settings and should not cause data loss with recent SSD/HDD drives. The power saving can be significant, ranging [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebb82e3c79d2a956366d0848304a53648bd6350b from 1.0 to 1.5 Watts (when idle)]. It will become a default setting for Intel based laptops in Linux 4.16 [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ebb82e3c79d2a956366d0848304a53648bd6350b].<br />
<br />
The current setting can be read from {{ic|/sys/class/scsi_host/host*/link_power_management_policy}} as follows:<br />
<br />
$ cat /sys/class/scsi_host/host*/link_power_management_policy<br />
<br />
{| class="wikitable"<br />
|+ Available ALPM settings<br />
! Setting<br />
! Description<br />
! Power saving<br />
|-<br />
| max_performance<br />
| current default<br />
| None<br />
|-<br />
| medium_power<br />
| -<br />
| ~1.0 Watts<br />
|-<br />
| med_power_with_dipm<br />
| recommended setting<br />
| ~1.5 Watts<br />
|-<br />
| min_power<br />
| '''WARNING: possible data loss'''<br />
| ~1.5 Watts<br />
|}<br />
<br />
{{hc|/etc/udev/rules.d/hd_power_save.rules|2=<br />
ACTION=="add", SUBSYSTEM=="scsi_host", KERNEL=="host*", ATTR{link_power_management_policy}="med_power_with_dipm"<br />
}}<br />
<br />
{{Note|This adds latency when accessing a drive that has been idle, so it is one of the few settings that may be worth toggling based on whether you are on AC power.}}<br />
<br />
=== Hard disk drive ===<br />
<br />
See [[hdparm#Power management configuration]] for drive parameters that can be set.<br />
<br />
Power saving is not effective when too many programs are frequently writing to the disk. Tracking all programs, and how and when they write to disk is the way to limit disk usage. Use {{Pkg|iotop}} to see which programs use the disk frequently. See [[Improving performance#Storage devices]] for other tips.<br />
<br />
Also little things like setting the [[Fstab#atime options|noatime]] option can help. If enough RAM is available, consider disabling or limiting [[swappiness]] as it has the possibility to limit a good number of disk writes.<br />
<br />
=== CD-ROM or DVD drive ===<br />
<br />
See [[Udisks#Devices do not remain unmounted (udisks)]].<br />
<br />
== Tools and scripts ==<br />
<br />
{{Style|Merged from [[Power saving]], needs reorganization to fit into this page.}}<br />
<br />
=== Using a script and an udev rule ===<br />
<br />
Since systemd users can suspend and hibernate through {{ic|systemctl suspend}} or {{ic|systemctl hibernate}} and handle acpi events with {{ic|/etc/systemd/logind.conf}}, it might be interesting to remove ''pm-utils'' and [[acpid]]. There is just one thing systemd cannot do (as of systemd-204): power management depending on whether the system is running on AC or battery. To fill this gap, you can create a single [[udev]] rule that runs a script when the AC adapter is plugged and unplugged:<br />
<br />
{{hc|/etc/udev/rules.d/powersave.rules|2=<nowiki><br />
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/path/to/your/script true"<br />
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/path/to/your/script false"<br />
</nowiki>}}<br />
<br />
{{Note|You can use the same script that ''pm-powersave'' uses. You just have to make it executable and place it somewhere else (for example {{ic|/usr/local/bin/}}).}}<br />
<br />
Examples of powersave scripts:<br />
<br />
* [https://github.com/supplantr/ftw ftw], package: {{AUR|ftw-git}}<br />
* [https://github.com/Unia/powersave powersave]<br />
* [https://github.com/quequotion/pantheon-bzr-qq/blob/master/EXTRAS/indicator-powersave/throttle throttle], from {{AUR|indicator-powersave}}<br />
<br />
The above udev rule should work as expected, but if your power settings are not updated after a suspend or hibernate cycle, you should add a script in {{ic|/usr/lib/systemd/system-sleep/}} with the following contents:<br />
<br />
{{hc|/usr/lib/systemd/system-sleep/00powersave|<nowiki><br />
#!/bin/sh<br />
<br />
case $1 in<br />
pre) /path/to/your/script false ;;<br />
post) <br />
if cat /sys/class/power_supply/AC0/online | grep 0 > /dev/null 2>&1<br />
then<br />
/path/to/your/script true <br />
else<br />
/path/to/your/script false<br />
fi<br />
;;<br />
esac<br />
exit 0<br />
</nowiki>}}<br />
<br />
Do not forget to make it executable!<br />
<br />
{{Note|Be aware that AC0 may be different for your laptop, change it if that is the case.}}<br />
<br />
=== Print power settings ===<br />
<br />
This script prints power settings and a variety of other properties for USB and PCI devices. Note that root permissions are needed to see all settings.<br />
<br />
{{bc|<nowiki><br />
#!/bin/bash<br />
<br />
for i in $(find /sys/devices -name "bMaxPower")<br />
do<br />
busdir=${i%/*}<br />
busnum=$(<$busdir/busnum)<br />
devnum=$(<$busdir/devnum)<br />
title=$(lsusb -s $busnum:$devnum)<br />
<br />
printf "\n\n+++ %s\n -%s\n" "$title" "$busdir"<br />
<br />
for ff in $(find $busdir/power -type f ! -empty 2>/dev/null)<br />
do<br />
v=$(cat $ff 2>/dev/null|tr -d "\n")<br />
[[ ${#v} -gt 0 ]] && echo -e " ${ff##*/}=$v";<br />
v=;<br />
done | sort -g;<br />
done;<br />
<br />
printf "\n\n\n+++ %s\n" "Kernel Modules"<br />
for mod in $(lspci -k | sed -n '/in use:/s,^.*: ,,p' | sort -u)<br />
do<br />
echo "+ $mod";<br />
systool -v -m $mod 2> /dev/null | sed -n "/Parameters:/,/^$/p";<br />
done<br />
</nowiki>}}<br />
<br />
== See also ==<br />
<br />
* [http://www.thinkwiki.org/wiki/How_to_reduce_power_consumption ThinkWiki:How to reduce power consumption]<br />
* [http://ivanvojtko.blogspot.sk/2016/04/how-to-get-longer-battery-life-on-linux.html How to get longer battery life on Linux]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=654855Dell XPS 13 (9343)2021-03-14T10:59:29Z<p>DonJaime: /* Troubleshooting */ More obsessively correct BIOS version information in EFISTUB section</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9343)]]<br />
{{Laptop style|Hardware table needs more content and PCI/USB IDs, missing function key table}}<br />
{{Note|This page refers to the ''early'' 2015 model of XPS 13. For the ''late'' 2015 model, see [[Dell XPS 13 (9350)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
! Hardware !! PCI/USB ID !! Working?<br />
|-<br />
| Video || || {{Yes}}<br />
|-<br />
| Wireless || || {{Yes}}<br />
|-<br />
| Bluetooth || || {{Yes}}<br />
|-<br />
| Audio || || {{Yes}}<br />
|-<br />
| Touchpad || || {{Yes}}<br />
|-<br />
| Webcam || || {{Yes}}<br />
|-<br />
| SD-card reader || || {{Yes}}<br />
|}<br />
{{Related articles start}}<br />
{{Related|Dell XPS 13 (9333)}}<br />
{{Related|Dell XPS 13 (9350)}}<br />
{{Related|Dell XPS 13 (9360)}}<br />
{{Related|Dell XPS 13 (9370)}}<br />
{{Related|Dell XPS 13 2-in-1 (9365)}}<br />
{{Related articles end}}<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[https://bartongeorge.io/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/]. 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 Linux on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]] and [[UEFI]] pages. 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 (released July 2015), 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 or QHD+) and '''Wi-Fi adapter''' differences (Dell DW1560 or Intel 7265).<br />
<br />
Users with QHD+ displays should use a DE/WM that properly supports [[HiDPI]].<br />
<br />
Regarding the Wi-Fi adapter, both cards work in Arch Linux. If the Intel one works out-of-the-box thanks to mainline kernel support, the Dell DW1560 instead requires a proprietary kernel module that is not well-supported; further details are reported in the proper below section.<br />
<br />
There are no exclusive hardware differences between the ''Developer Edition'' and the standard Windows edition, so this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
The latest BIOS update is [https://www.dell.com/support/Home/us/en/19/Drivers/DriversDetails?driverId=W5C0W A20] and it was released on 8th October 2019. With version 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.<br />
<br />
BIOS upgrade is easy, thanks to the EFI implementation: place the update binary (the just downloaded {{ic|.exe}} file) in the EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, press {{ic|F12}} key in order to enter in the Boot Menu and then choose ''BIOS Update''.<br />
<br />
=== Screen and Keyboard Backlight ===<br />
Backlight and its control work out-of-the-box:<br />
* The [[Backlight#Save and restore functionality|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 Function keys ({{ic|Fn-F11}} and {{ic|Fn-F12}} for screen backlight and {{ic|Fn-F10}} for keyboard backlight) work without any operation, as well.<br />
<br />
{{Note|By default, the keyboard backlight automatically turns off after 60 seconds of inactivity. You can change the default behaviour by editing the related ''sysfs'' entry {{ic|1=/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout}}.}}<br />
<br />
==== Dynamic Backlight/Brightness Control (DBC) ====<br />
You may notice that the screen looks dimmer than you expect or the screen overall brightness changes constantly. This behaviour is not a symptom of any monitor issue but a technology called '''Dynamic Backlight/Brightness Control (DBC)''', designed to save energy according to the content displayed on the screen.<br />
<br />
{{Tip|You can check this feature on this [https://tylerwatt12.com/dc/ website].}}<br />
<br />
{{Warning|This feature is ''automatic'' and ''not-controllable''. According to official Dell [http://www.dell.com/support/article/us/en/19/sln304876/xps-9343-9350-9360-and-9365-2-in-1-lcd-brightness-issues source], only the '''QHD+ models''' have a chance to disable it via a firmware update.}}<br />
<br />
=== SSD ===<br />
This laptop series comes with a SSD as storage device, connected via SATA. This technology needs some configuration in order to achieve the best operative conditions. See [[Solid State Drives]] for further information.<br />
<br />
=== Wi-Fi ===<br />
Most configurations sport the Dell DW1560 802.11ac adapter (based on the Broadcom BCM4352 chip) which requires {{Pkg|broadcom-wl}} or {{Pkg|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, instead they use an Intel Wireless 7265 card which is supported by the mainline kernel.<br />
<br />
{{Note|This card is widely available as an after-market purchase for those wishing to replace the Broadcom adapter in their laptop. This wireless adapter, other than an enviable driver support for both Wi-Fi and Bluetooth that makes installation easier, compared to the Broadcom card, it has a 2-3 times wider reception range and a much higher throughput, making it an worthwhile upgrade. Other cards are also available. The Intel Wireless 8265 is known to work}}<br />
<br />
=== Bluetooth ===<br />
{{Note|For users with Intel wireless adapter with both Wi-Fi and Bluetooth, the Bluetooth 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 ([https://web.archive.org/web/20200928012524/http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), so you need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use Bluetooth.<br />
<br />
Alternatively, you can retrieve the firmware directly from the [https://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] by 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 is 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 perform [[#BIOS updates]] 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 itself to determine in which mode the sound chipset should be initialized in at boot.<br />
<br />
==== HDA mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''older than 4.4''' and again starting '''from version 4.11.5''', the sound card will be initialized in HDA mode.<br />
<br />
{{Note|To use HDA mode on excluded kernels, re-compile them with the option {{ic|1=CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y}}. This will force HDA mode on.}}<br />
<br />
===== Setting the default sound card =====<br />
By default, ALSA does not 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|If you are dual-booting with Windows, you will have to do a cold boot twice before to have sound working in Linux and vice-versa.}}<br />
<br />
{{Note|This is not necessary in I2S mode.}}<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''from 4.4 to 4.11.4''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0[http://www.spinics.net/lists/linux-acpi/msg57457.html] or newer. (I2S support was broken in mainline kernel 4.5, and fixed in Arch kernel 4.5.2 and mainline 4.8[https://bugs.archlinux.org/task/48936][https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?id=a395bdd6b24b692adbce0df6510ec9f2af57573e]).<br />
<br />
===== Enabling the microphone =====<br />
{{Note|The microphone appears to be enabled by default as of official Arch Linux 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 the {{ic|Mic}} item. Follow the instructions below in order to achieve the goal:<br />
* open {{ic|alsamixer}} (an utility included in 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|Cycling the '''Port''' (from ''Main Microphone'' to ''Headset Microphone (unplugged)'', and back) of the '''Input Devices''' tab in the {{ic|pavucontrol}} application, has the same effect of the above instructions.}}<br />
<br />
===== Using Jack =====<br />
By default Jack recognises four capture ports and is unusable because the transport is broken into short fragments with breaks between them. Limit input to two channels with {{ic|-i2}} on the command line or the corresponding option in {{pkg|qjackctl}}'s advanced settings.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS, the touchpad should work out-of-the-box with either the synaptics or libinput drivers. The second is recommended over the former.<br />
<br />
==== Synaptics driver ====<br />
For more advanced settings with the Synaptics driver, see [[Touchpad Synaptics#Buttonless touchpads (aka ClickPads)|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 />
Refer to the specific [[libinput]] page for more details.<br />
<br />
For further configurable options (e.g. NaturalScrolling, MiddleEmulation), see {{man|1|libinput}}.<br />
<br />
=== Powersaving ===<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 />
You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour by yourself.<br />
<br />
{{Note|1=&nbsp;<br />
* With kernel 4.6+, frame-buffer compression ('''FBC''') is enabled by default, so {{ic|i915.enable_fbc}} is no longer needed.<br />
* Panel self refresh ('''PSR''') causes the display to flicker, so it has been disabled by default as of kernel 4.9 [https://bugs.freedesktop.org/show_bug.cgi?id=95176].<br />
* {{ic|1=i915.lvds_downclock=1}} for '''LVDS downclock''' is no longer needed. According to IRC #intel-gfx, ''"[...] there is a new auto-downclock for eDP panels in recent kernels and it is enabled by default if available, [...]"''.<br />
* {{ic|1=i915.enable_rc6=7}} is useless on Broadwell ('''Gen8''') systems because 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 />
=== Calibrated ICC profile ===<br />
<br />
==== QHD+ model ====<br />
{{Warning|This profile is only for QHD+ model. Do not use it if you have the FHD one.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the colour attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document. The following ICC profile is made with dispcalGUI ( {{pkg|displaycal}}) ArgyllCMS ( {{pkg|argyllcms}}) and a spectrophotometer for absolute colour accuracy; even if it is possible to achieve better results by calibrating your own monitor by yourself, in general this profile is definitively 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 for at least 30 minutes prior to start the calibration.<br />
<br />
* [https://mega.nz/#!nkNVQDCI!YYcS32HLWk1Aqry30dmOrt0wrfH9W_VczNesHQEpG_U QHD+, D65, Gamma 2.2, max luminance].<br />
<br />
=== Disable the touchscreen ===<br />
This is an optional step and was tested 07.2019 using Gnome and Wayland. Find out which device it is:<br />
libinput list-devices<br />
Scroll to find the right section (Something like ELAN Touchscreen) and find the line "Kernel: /dev/input/event#". (in my case 6) Use the event# for the next command: <br />
udevadm info -a -p /sys/class/input/event#<br />
Find an attribute that is most probably unique/distinct. (I used: ATTRS{name}=="ELAN Touchscreen" )<br />
Use this in a newly created file: /etc/udev/rules.d/99-disable_touchscreen.rules<br />
KERNEL=="event*", ATTRS{name}=="ELAN Touchscreen", ENV{LIBINPUT_IGNORE_DEVICE}="1"<br />
Then check if it worked: <br />
udevadm test /sys/class/input/event6<br />
and search for: <br />
LIBINPUT_IGNORE_DEVICE=1<br />
If this line is there (most probably within the last 3 lines) reboot and your touchscreen should be disabled. <br />
<br />
== Troubleshooting ==<br />
<br />
=== EFISTUB does not boot ===<br />
Update the BIOS. In more recent versions (A19 at the latest) it works.<br />
Older versions of the BIOS do not pass any boot parameters to the kernel and you have to use a UEFI [[boot loader]] instead. [[systemd-boot]] will work with current kernels.<br />
Alternatively, packaging the command line, microcode and initramfs with the kernel into a single EFI will also work. This can then be added as an entry into the boot manager. See this [https://github.com/xdever/arch-efiboot example], doing so using {{ic|objcopy}}. Similarly, creating a signed EFI using {{AUR|cryptboot}} and {{AUR|sbupdate-git}} will also work.<br />
<br />
=== Random kernel hangs at boot ===<br />
See [https://bugzilla.kernel.org/show_bug.cgi?id=105251 here]. This issue seems to affect only touchscreen model owners. The fix consists in removing "keyboard" from the HOOKS array in /etc/mkinitcpio.conf. If you need the keyboard at boot, edit the MODULES array as follow MODULES="atkbd usbhid hid-generic". You will have to run {{ic|mkinitcpio -p linux}} as root afterwards.<br />
<br />
=== Sometimes the system fails to resume from suspend after closing and reopening the LID ===<br />
Even if it has been reported as fixed upstream according to [https://bugzilla.kernel.org/show_bug.cgi?id=86241 this kernel.org bug report], users still suffer of this problem (reported for both FullHD model with kernel 4.20.12 and the QHD+ model with kernel 4.18.6).<br />
<br />
One more, following a comment in the abovementioned bug report, you can work it around by blacklisting ''mei'' modules:<br />
<br />
cat << EOF | sudo tee /etc/modprobe.d/blacklist.suspend-bug.conf<br />
<br />
blacklist mei<br />
blacklist mei_me<br />
EOF<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#AccelMethod|switch your Intel graphics acceleration from SNA to UXA]]. Switching to UXA, however, will result in worse performance. Switching to xf86-video-modesetting (Glamor acceleration) should not decrease performance considerably,however it is still not known if will fix the resume issue.<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 />
=== Wireless switch/rfkill issues with KDE ===<br />
As from kernel version 4.4 the rfkill switch works. The KDE plasma-nm (NetworkManager) widget does not indicate that wlan is active after it has been reactivated, but still connects correctly. The KDE system tray bluetooth widget usually disappears if the switch disables bluetooth, and fails to reappear when it is reactivated. You can work around this by setting the switch not to switch bluetooth in the BIOS setup. With kernel version < 4.13.11 and/or plasma-desktop < 5.11 the mouse pointer may freeze first time that the rfkill switch is used. To unfreeze it, switch to another virtual console and back.<br />
<br />
=== DE can't connect Bluetooth devices ===<br />
If the Bluetooth GUI can't connect the device, try to use {{ic|bluetoothctl}} to connect manually.<br />
<br />
=== Sound doesn't work after upgrading to kernel 4.4+ ===<br />
You need to do two cold boots ('''NOT''' a simple reboot, shut it down and turn it back on again) to make sound working again.<br />
<br />
Refer to the [[#HDA mode]] 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 Linux bug report].<br />
<br />
=== Loud cracks/noise during boot or audio playback ===<br />
Some users have reported the above sound problems, as described [https://bbs.archlinux.org/viewtopic.php?id=208496 here] for example.<br />
<br />
[[Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback|Disabling audio powersafe]] may work for people using the '''HDA''' audio mode.<br />
<br />
However, it is still unknown how to solve this issue for the '''I2S''' audio mode.<br />
<br />
For further reference, see the corresponding [https://bugzilla.kernel.org/show_bug.cgi?id=112611 kernel bug entry].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
Update {{pkg|xf86-video-intel}} to latest version. This should fix the issue.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
* [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop//xps-13-9343-laptop_Service%20Manual_en-us.pdf Service Manual for Dell XPS 13 (9343)]<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=654760Dell XPS 13 (9343)2021-03-13T12:40:33Z<p>DonJaime: /* EFISTUB does not boot */ EFISTUB does now boot with an updated BIOS</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9343)]]<br />
{{Laptop style|Hardware table needs more content and PCI/USB IDs, missing function key table}}<br />
{{Note|This page refers to the ''early'' 2015 model of XPS 13. For the ''late'' 2015 model, see [[Dell XPS 13 (9350)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
! Hardware !! PCI/USB ID !! Working?<br />
|-<br />
| Video || || {{Yes}}<br />
|-<br />
| Wireless || || {{Yes}}<br />
|-<br />
| Bluetooth || || {{Yes}}<br />
|-<br />
| Audio || || {{Yes}}<br />
|-<br />
| Touchpad || || {{Yes}}<br />
|-<br />
| Webcam || || {{Yes}}<br />
|-<br />
| SD-card reader || || {{Yes}}<br />
|}<br />
{{Related articles start}}<br />
{{Related|Dell XPS 13 (9333)}}<br />
{{Related|Dell XPS 13 (9350)}}<br />
{{Related|Dell XPS 13 (9360)}}<br />
{{Related|Dell XPS 13 (9370)}}<br />
{{Related|Dell XPS 13 2-in-1 (9365)}}<br />
{{Related articles end}}<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[https://bartongeorge.io/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/]. 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 Linux on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]] and [[UEFI]] pages. 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 (released July 2015), 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 or QHD+) and '''Wi-Fi adapter''' differences (Dell DW1560 or Intel 7265).<br />
<br />
Users with QHD+ displays should use a DE/WM that properly supports [[HiDPI]].<br />
<br />
Regarding the Wi-Fi adapter, both cards work in Arch Linux. If the Intel one works out-of-the-box thanks to mainline kernel support, the Dell DW1560 instead requires a proprietary kernel module that is not well-supported; further details are reported in the proper below section.<br />
<br />
There are no exclusive hardware differences between the ''Developer Edition'' and the standard Windows edition, so this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
The latest BIOS update is [https://www.dell.com/support/Home/us/en/19/Drivers/DriversDetails?driverId=W5C0W A20] and it was released on 8th October 2019. With version 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.<br />
<br />
BIOS upgrade is easy, thanks to the EFI implementation: place the update binary (the just downloaded {{ic|.exe}} file) in the EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, press {{ic|F12}} key in order to enter in the Boot Menu and then choose ''BIOS Update''.<br />
<br />
=== Screen and Keyboard Backlight ===<br />
Backlight and its control work out-of-the-box:<br />
* The [[Backlight#Save and restore functionality|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 Function keys ({{ic|Fn-F11}} and {{ic|Fn-F12}} for screen backlight and {{ic|Fn-F10}} for keyboard backlight) work without any operation, as well.<br />
<br />
{{Note|By default, the keyboard backlight automatically turns off after 60 seconds of inactivity. You can change the default behaviour by editing the related ''sysfs'' entry {{ic|1=/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout}}.}}<br />
<br />
==== Dynamic Backlight/Brightness Control (DBC) ====<br />
You may notice that the screen looks dimmer than you expect or the screen overall brightness changes constantly. This behaviour is not a symptom of any monitor issue but a technology called '''Dynamic Backlight/Brightness Control (DBC)''', designed to save energy according to the content displayed on the screen.<br />
<br />
{{Tip|You can check this feature on this [https://tylerwatt12.com/dc/ website].}}<br />
<br />
{{Warning|This feature is ''automatic'' and ''not-controllable''. According to official Dell [http://www.dell.com/support/article/us/en/19/sln304876/xps-9343-9350-9360-and-9365-2-in-1-lcd-brightness-issues source], only the '''QHD+ models''' have a chance to disable it via a firmware update.}}<br />
<br />
=== SSD ===<br />
This laptop series comes with a SSD as storage device, connected via SATA. This technology needs some configuration in order to achieve the best operative conditions. See [[Solid State Drives]] for further information.<br />
<br />
=== Wi-Fi ===<br />
Most configurations sport the Dell DW1560 802.11ac adapter (based on the Broadcom BCM4352 chip) which requires {{Pkg|broadcom-wl}} or {{Pkg|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, instead they use an Intel Wireless 7265 card which is supported by the mainline kernel.<br />
<br />
{{Note|This card is widely available as an after-market purchase for those wishing to replace the Broadcom adapter in their laptop. This wireless adapter, other than an enviable driver support for both Wi-Fi and Bluetooth that makes installation easier, compared to the Broadcom card, it has a 2-3 times wider reception range and a much higher throughput, making it an worthwhile upgrade. Other cards are also available. The Intel Wireless 8265 is known to work}}<br />
<br />
=== Bluetooth ===<br />
{{Note|For users with Intel wireless adapter with both Wi-Fi and Bluetooth, the Bluetooth 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 ([https://web.archive.org/web/20200928012524/http://tech.sybreon.com/2015/03/15/xps13-9343-ubuntu-linux/ source]), so you need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use Bluetooth.<br />
<br />
Alternatively, you can retrieve the firmware directly from the [https://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] by 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 is 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 perform [[#BIOS updates]] 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 itself to determine in which mode the sound chipset should be initialized in at boot.<br />
<br />
==== HDA mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''older than 4.4''' and again starting '''from version 4.11.5''', the sound card will be initialized in HDA mode.<br />
<br />
{{Note|To use HDA mode on excluded kernels, re-compile them with the option {{ic|1=CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y}}. This will force HDA mode on.}}<br />
<br />
===== Setting the default sound card =====<br />
By default, ALSA does not 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|If you are dual-booting with Windows, you will have to do a cold boot twice before to have sound working in Linux and vice-versa.}}<br />
<br />
{{Note|This is not necessary in I2S mode.}}<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''from 4.4 to 4.11.4''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0[http://www.spinics.net/lists/linux-acpi/msg57457.html] or newer. (I2S support was broken in mainline kernel 4.5, and fixed in Arch kernel 4.5.2 and mainline 4.8[https://bugs.archlinux.org/task/48936][https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?id=a395bdd6b24b692adbce0df6510ec9f2af57573e]).<br />
<br />
===== Enabling the microphone =====<br />
{{Note|The microphone appears to be enabled by default as of official Arch Linux 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 the {{ic|Mic}} item. Follow the instructions below in order to achieve the goal:<br />
* open {{ic|alsamixer}} (an utility included in 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|Cycling the '''Port''' (from ''Main Microphone'' to ''Headset Microphone (unplugged)'', and back) of the '''Input Devices''' tab in the {{ic|pavucontrol}} application, has the same effect of the above instructions.}}<br />
<br />
===== Using Jack =====<br />
By default Jack recognises four capture ports and is unusable because the transport is broken into short fragments with breaks between them. Limit input to two channels with {{ic|-i2}} on the command line or the corresponding option in {{pkg|qjackctl}}'s advanced settings.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS, the touchpad should work out-of-the-box with either the synaptics or libinput drivers. The second is recommended over the former.<br />
<br />
==== Synaptics driver ====<br />
For more advanced settings with the Synaptics driver, see [[Touchpad Synaptics#Buttonless touchpads (aka ClickPads)|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 />
Refer to the specific [[libinput]] page for more details.<br />
<br />
For further configurable options (e.g. NaturalScrolling, MiddleEmulation), see {{man|1|libinput}}.<br />
<br />
=== Powersaving ===<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 />
You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour by yourself.<br />
<br />
{{Note|1=&nbsp;<br />
* With kernel 4.6+, frame-buffer compression ('''FBC''') is enabled by default, so {{ic|i915.enable_fbc}} is no longer needed.<br />
* Panel self refresh ('''PSR''') causes the display to flicker, so it has been disabled by default as of kernel 4.9 [https://bugs.freedesktop.org/show_bug.cgi?id=95176].<br />
* {{ic|1=i915.lvds_downclock=1}} for '''LVDS downclock''' is no longer needed. According to IRC #intel-gfx, ''"[...] there is a new auto-downclock for eDP panels in recent kernels and it is enabled by default if available, [...]"''.<br />
* {{ic|1=i915.enable_rc6=7}} is useless on Broadwell ('''Gen8''') systems because 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 />
=== Calibrated ICC profile ===<br />
<br />
==== QHD+ model ====<br />
{{Warning|This profile is only for QHD+ model. Do not use it if you have the FHD one.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the colour attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document. The following ICC profile is made with dispcalGUI ( {{pkg|displaycal}}) ArgyllCMS ( {{pkg|argyllcms}}) and a spectrophotometer for absolute colour accuracy; even if it is possible to achieve better results by calibrating your own monitor by yourself, in general this profile is definitively 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 for at least 30 minutes prior to start the calibration.<br />
<br />
* [https://mega.nz/#!nkNVQDCI!YYcS32HLWk1Aqry30dmOrt0wrfH9W_VczNesHQEpG_U QHD+, D65, Gamma 2.2, max luminance].<br />
<br />
=== Disable the touchscreen ===<br />
This is an optional step and was tested 07.2019 using Gnome and Wayland. Find out which device it is:<br />
libinput list-devices<br />
Scroll to find the right section (Something like ELAN Touchscreen) and find the line "Kernel: /dev/input/event#". (in my case 6) Use the event# for the next command: <br />
udevadm info -a -p /sys/class/input/event#<br />
Find an attribute that is most probably unique/distinct. (I used: ATTRS{name}=="ELAN Touchscreen" )<br />
Use this in a newly created file: /etc/udev/rules.d/99-disable_touchscreen.rules<br />
KERNEL=="event*", ATTRS{name}=="ELAN Touchscreen", ENV{LIBINPUT_IGNORE_DEVICE}="1"<br />
Then check if it worked: <br />
udevadm test /sys/class/input/event6<br />
and search for: <br />
LIBINPUT_IGNORE_DEVICE=1<br />
If this line is there (most probably within the last 3 lines) reboot and your touchscreen should be disabled. <br />
<br />
== Troubleshooting ==<br />
<br />
=== EFISTUB does not boot ===<br />
Update the BIOS. Version A20 works.<br />
Older versions of the BIOS do not pass any boot parameters to the kernel and you have to use a UEFI [[boot loader]] instead. [[systemd-boot]] will work with current kernels.<br />
Alternatively, packaging the command line, microcode and initramfs with the kernel into a single EFI will also work. This can then be added as an entry into the boot manager. See this [https://github.com/xdever/arch-efiboot example], doing so using {{ic|objcopy}}. Similarly, creating a signed EFI using {{AUR|cryptboot}} and {{AUR|sbupdate-git}} will also work.<br />
<br />
=== Random kernel hangs at boot ===<br />
See [https://bugzilla.kernel.org/show_bug.cgi?id=105251 here]. This issue seems to affect only touchscreen model owners. The fix consists in removing "keyboard" from the HOOKS array in /etc/mkinitcpio.conf. If you need the keyboard at boot, edit the MODULES array as follow MODULES="atkbd usbhid hid-generic". You will have to run {{ic|mkinitcpio -p linux}} as root afterwards.<br />
<br />
=== Sometimes the system fails to resume from suspend after closing and reopening the LID ===<br />
Even if it has been reported as fixed upstream according to [https://bugzilla.kernel.org/show_bug.cgi?id=86241 this kernel.org bug report], users still suffer of this problem (reported for both FullHD model with kernel 4.20.12 and the QHD+ model with kernel 4.18.6).<br />
<br />
One more, following a comment in the abovementioned bug report, you can work it around by blacklisting ''mei'' modules:<br />
<br />
cat << EOF | sudo tee /etc/modprobe.d/blacklist.suspend-bug.conf<br />
<br />
blacklist mei<br />
blacklist mei_me<br />
EOF<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#AccelMethod|switch your Intel graphics acceleration from SNA to UXA]]. Switching to UXA, however, will result in worse performance. Switching to xf86-video-modesetting (Glamor acceleration) should not decrease performance considerably,however it is still not known if will fix the resume issue.<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 />
=== Wireless switch/rfkill issues with KDE ===<br />
As from kernel version 4.4 the rfkill switch works. The KDE plasma-nm (NetworkManager) widget does not indicate that wlan is active after it has been reactivated, but still connects correctly. The KDE system tray bluetooth widget usually disappears if the switch disables bluetooth, and fails to reappear when it is reactivated. You can work around this by setting the switch not to switch bluetooth in the BIOS setup. With kernel version < 4.13.11 and/or plasma-desktop < 5.11 the mouse pointer may freeze first time that the rfkill switch is used. To unfreeze it, switch to another virtual console and back.<br />
<br />
=== DE can't connect Bluetooth devices ===<br />
If the Bluetooth GUI can't connect the device, try to use {{ic|bluetoothctl}} to connect manually.<br />
<br />
=== Sound doesn't work after upgrading to kernel 4.4+ ===<br />
You need to do two cold boots ('''NOT''' a simple reboot, shut it down and turn it back on again) to make sound working again.<br />
<br />
Refer to the [[#HDA mode]] 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 Linux bug report].<br />
<br />
=== Loud cracks/noise during boot or audio playback ===<br />
Some users have reported the above sound problems, as described [https://bbs.archlinux.org/viewtopic.php?id=208496 here] for example.<br />
<br />
[[Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback|Disabling audio powersafe]] may work for people using the '''HDA''' audio mode.<br />
<br />
However, it is still unknown how to solve this issue for the '''I2S''' audio mode.<br />
<br />
For further reference, see the corresponding [https://bugzilla.kernel.org/show_bug.cgi?id=112611 kernel bug entry].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
Update {{pkg|xf86-video-intel}} to latest version. This should fix the issue.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
* [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop//xps-13-9343-laptop_Service%20Manual_en-us.pdf Service Manual for Dell XPS 13 (9343)]<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Migrating_between_architectures&diff=506805Talk:Migrating between architectures2018-01-10T09:26:19Z<p>DonJaime: /* Third method? */ new section</p>
<hr />
<div>== LiveCD method doesn't work ==<br />
<br />
The LiveCD migration method from i686 -> x86_64 doesn't work, the instructions are incomplete. It took me half a day to get my system working again.<br />
<br />
Here are the issues I ran into:<br />
<br />
* There's not enough space on the livecd ramdisk to do a full system update if there are large installed packages (e.g. eclipse, ghc etc). I had to delete the pacman cache from time to time to prevent the disk from filling up.<br />
* After system update, the init ramdisk has to be regenerated with mkinitcpio otherwise the updated system won't boot with the new kernel. To run mkinitcpio, you have to first chroot (look up chroot on arch wiki).<br />
* The script from the article uses pacman -Qqet to discover the installed packages, however this won't list libraries. To do a full update I had to change that to pacman -Qq.<br />
* The update script doesn't update dependencies in the correct order, so it has to be run twice. This seems to be the same issue as Dooglus describes below.<br />
* /etc/makepkg.conf has to be updated to match the new architecture.<br />
* It would be a good idea to save the output of the script into a log file, that was helpful for me to find packages that were not upgraded (some from AUR and others with lib32 dependency problems). Make sure to pipe stderr also, for example:<br />
<br />
migrate 2>&1 | tee migrate.log<br />
<br />
I'm not sure what the policies are for updating the wiki page and I probably wouldn't be able to describe all the steps that were necessary to get my system up and running again, but I hope the points above will help others who run into the same issues. <br />
<br />
{{Unsigned|06:24, 16 March 2012|Lajos}}<br />
<br />
== Couldn't install lib32-glibc ==<br />
<br />
The article says "Alternatively, if migrating to 64 bits, now is the time to install the lib32-glibc fallback". But when I tried to install lib32-glibc I got errors about conflicting files. I didn't keep a record of the exact error message, but glibc and lib32-glibc both have these 2 files in them, so I guess that was the cause of the error:<br />
<br />
/lib/ld-linux.so.2<br />
/usr/include/gnu/stubs-32.h<br />
<br />
See https://www.archlinux.org/packages/core/i686/glibc/files/ and https://www.archlinux.org/packages/multilib/x86_64/lib32-glibc/files/ for the file lists - the article suggests installing lib32-glibc before upgrading glibc. --[[User:Dooglus|Dooglus]] 20:40, 9 November 2011 (EST)<br />
<br />
:first: <br />
:if the following lines are in your {{ic|/etc/pacman.conf}} you can install lib32-glibc:<br />
<br />
[multilib]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
:second: <br />
:if you have problems with existing file use the '''-f''' (force) flag<br />
:after the migration every thing has changed, (deps, files..) - so it doesn't matter any way<br />
<br />
:{{Unsigned|15:56, 19 March 2012|Djrf}}<br />
<br />
== Errors Upgrading pacman, etc. ==<br />
<br />
I followed the instructions for method two (installing from a running system) to upgrade from 32 bit to 64 bit. It went well until it came to reinstalling pacman and friends, then I saw a bunch of errors:<br />
<br />
[root@chris chris]# pacman -S pacman glibc libfetch libarchive openssl acl attr \<br />
xz-utils bzip2 zlib readline bash ncurses expat<br />
warning: pacman-3.5.4-4 is up to date -- reinstalling<br />
warning: glibc-2.14.1-1 is up to date -- reinstalling<br />
warning: libfetch-2.33-3 is up to date -- reinstalling<br />
warning: libarchive-2.8.5-2 is up to date -- reinstalling<br />
warning: openssl-1.0.0.e-1 is up to date -- reinstalling<br />
warning: acl-2.2.51-1 is up to date -- reinstalling<br />
warning: attr-2.4.46-1 is up to date -- reinstalling<br />
warning: xz-5.0.3-1 is up to date -- reinstalling<br />
warning: bzip2-1.0.6-3 is up to date -- reinstalling<br />
warning: zlib-1.2.5-4 is up to date -- reinstalling<br />
warning: readline-6.2.001-3 is up to date -- reinstalling<br />
warning: bash-4.2.010-2 is up to date -- reinstalling<br />
warning: ncurses-5.9-2 is up to date -- reinstalling<br />
warning: expat-2.0.1-7 is up to date -- reinstalling<br />
resolving dependencies...<br />
looking for inter-conflicts...<br />
<br />
Targets (14): glibc-2.14.1-1 ncurses-5.9-2 readline-6.2.001-3 bash-4.2.010-2 \<br />
zlib-1.2.5-4 bzip2-1.0.6-3 xz-5.0.3-1 attr-2.4.46-1 acl-2.2.51-1 \<br />
openssl-1.0.0.e-1 expat-2.0.1-7 libarchive-2.8.5-2 libfetch-2.33-3 \<br />
pacman-3.5.4-4<br />
<br />
Total Download Size: 0.00 MB<br />
Total Installed Size: 67.17 MB<br />
<br />
Proceed with installation? [Y/n] y<br />
call to execv failed (No such file or directory)<br />
error: command failed to execute correctly<br />
call to execv failed (No such file or directory)<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew<br />
[root@chris chris]# <br />
<br />
I don't know if they are 'expected' errors, or if they're a problem. I carried on with the<br />
<br />
# pacman -S $(pacman -Qq)<br />
<br />
command, which also produced some errors. I won't paste the whole output, since it is rather large, but some of the more serious looking errors were:<br />
<br />
Proceed with installation? [Y/n] y<br />
/tmp/alpm_nhTnAm/.INSTALL: line 6: sbin/init: No such file or directory<br />
usr/sbin/locale-gen: line 16: /bin/rm: No such file or directory<br />
Generating locales...<br />
usr/sbin/locale-gen: line 33: /bin/sed: No such file or directory<br />
.UTF-8usr/sbin/locale-gen: line 35: /bin/sed: No such file or directory<br />
...usr/sbin/locale-gen: line 38: /bin/sed: No such file or directory<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
error: command failed to execute correctly<br />
/tmp/alpm_pnGmoW/.INSTALL: line 16: bin/grep: No such file or directory<br />
groupadd: group 'optical' already exists<br />
<br />
After that I ran both commands again, in the same order, and this time they both completed without errors, and my system appears to be fine as far as I can tell.<br />
<br />
I don't know if the errors produced the first time through needed fixing, or if my solution (re-running both commands) is a good solution, but maybe someone who knows could update the article accordingly, either saying not to worry about the errors, or saying what how to fix them. --[[User:Dooglus|Dooglus]] 20:18, 9 November 2011 (EST)<br />
<br />
=== "Install Pacman" ===<br />
<br />
The step:<br />
<br />
pactree -l pacman | pacman -S -<br />
<br />
had some errors for glibc and other packages like <br />
<br />
error: command failed to execute correctly<br />
<br />
After installing the new pacman, I installed the packages:<br />
gettext<br />
texinfo<br />
gzip - used but glibc to generate locales<br />
<br />
And reinstalled pacman, this time it worked fine.<br />
(I also installed some packages like grep, sudo, and such)<br />
<br />
Continued the guide normally. {{Unsigned|09:10, 31 July 2013|Olivervbk}}<br />
<br />
== "Install Remaining Packages" ==<br />
<br />
Just went through this installation, thought I'd note that I had to the alternative step in "Download new packages" (using comm to remove AUR packages). When I did the install remaining package step, you need to include that to edit the pacman -Qq output as well or it won't run. I'm new to wiki editing so don't know if I should just go and do that myself, but I thought I'd point that out for anybody freakin out.<br />
{{Unsigned|19:28, 1 August 2012|Jemofthewest}}<br />
<br />
:Hi Jemofthewest, if you have just gone through this process then I’d encourage you to update the page as best you can. You’re probably a lot more familiar with the process than me (and probably most other people reading this). [[User:Vadmium|Vadmium]] ([[User talk:Vadmium|talk]]) 12:38, 19 August 2012 (UTC).<br />
<br />
<br />
I've had some troubles with this step. To install the lib32-glibc fallback, I had to add the multilib repo. With this I've had new packages that were not downloaded and after rebooting, I no longer had network. I could solve by re-installing some packages that allowed me to use dhclient, wget and such, but I think it's a good idea to put a note to re-run the download command after adding the multilib repo. And make sure you have connection before commencing the update. [[User:Renatolond|Renatolond]] ([[User talk:Renatolond|talk]]) 15:54, 21 January 2015 (UTC)<br />
<br />
== Install from running system works ==<br />
<br />
Just wanted to say that as of July, 21th, 2014, following the guide works ok for i686 -> x86_64. Thanks. {{Unsigned|14:32, 21 July 2014|Cgo}}<br />
<br />
:Worked perfectly for me as well today - [[User:Warddr|Warddr]] ([[User talk:Warddr|talk]]) 22:51, 12 August 2014 (UTC)<br />
<br />
:worked here also perfectly at my ''ThinkPad x200'' with 4gb ram :3 --[[User:Therojam|Therojam]] ([[User talk:Therojam|talk]]) 15:23, 24 May 2015 (UTC)<br />
Worked for me too! Had to generate locale manually afterwords (sudo locale-gen). At one point X (nvidia) didn't start but after the last full reinstall command it did. Going to console mode was key here. (ctrl+alt+F2) -- swanson, 8 march 2016<br />
<br />
== Install from running system doesn't work ==<br />
Af of September, 6th, 2017 the method No 2 doesn't work for me. On reinstalling pacman stem I stumbled upon dependency break (not remember what package exactly) so I was forced to pactree -l|pacman -Sdd and after reinstalling all packages I'm not able to boot due to udisks-part-id process being terminated by signal SYS<br />
[EDIT:]<br />
Either reinstalling systemd or generating locale helped.<br />
--[[User:Speranskiy|Speranskiy]] ([[User talk:Speranskiy|talk]]) 06:56, 6 September 2017 (UTC)<br />
<br />
== Third method? ==<br />
<br />
I've used this method to migrate from i686 to x86_64 and back again. Include it in the page?<br />
<br />
{{bc|<br />
# if necessary, edit /etc/pacman.conf to remove any repositories that don't support the new architecture<br />
# save lists of explicitly installed packages and optional dependencies<br />
<br />
pacman -Qneq > /root/pacman-explicit<br />
pacman -Qmeq > /root/pacman-aur-explicit<br />
pacman -Qndttq > /root/pacman-optdeps<br />
pacman -Qmdttq > /root/pacman-aur-optdeps<br />
<br />
# hollow out system. Confirm that you want to remove the hold packages.<br />
<br />
pacman -Rdd $(pacman -Qq)<br />
<br />
# reboot from install medium<br />
# mount /, /boot, /usr as appropriate, as for initial installation<br />
<br />
# forget who we used to trust<br />
<br />
mv /mnt/etc/pacman.d/gnupg /mnt/etc/pacman.d/gnupg~<br />
# or see https://archlinux32.org/download/ on transitioning if moving to i686 from x86_64<br />
<br />
# lobotomise pacman. Removing /mnt/var/log/pacman.log is optional and a matter of taste<br />
<br />
rm -r /mnt/var/cache/pacman /mnt/var/lib/pacman [/mnt/var/log/pacman.log]<br />
<br />
# restore saved config files<br />
<br />
for F in $(find /mnt -name "*.pacsave") ; do mv "$F" "${F%.pacsave}" ; done<br />
<br />
# use your old pacman config for reinstallation<br />
<br />
mv /etc/pacman.conf /etc/pacman.conf~<br />
cp /mnt/etc/pacman.conf /etc/pacman.conf<br />
<br />
# install explicitly installed packages and their dependencies (init ramdisk should be automatically regenerated)<br />
<br />
pacstrap /mnt $(< /mnt/root/pacman-explicit )<br />
<br />
# do whatever is needed to make sure your booloader will work, or replace it<br />
# reboot into restored basic system, or arch-chroot /mnt, and install optional dependencies<br />
<br />
pacman -S --asdeps $(< /root/pacman-optdeps )<br />
<br />
# Merge or replace makepkg.conf with makepkg.conf.pacnew to correct architecture, then restore any aur packages.<br />
}}<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 09:26, 10 January 2018 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=495714Dell XPS 13 (9343)2017-11-08T16:25:59Z<p>DonJaime: /* rfkill issues with KDE */ Update for recent KDE widget quirks</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9343)]]<br />
{{Note|This page refers to the ''early'' 2015 model of XPS 13. For the ''late'' 2015 model, see [[Dell XPS 13 (9350)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| Video || {{G|Working}}<br />
|-<br />
| Backlight control || {{G|Working}}<br />
|-<br />
| Wi-Fi || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Wireless switch || {{Y|Working ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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[https://bartongeorge.io/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/]. 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 Linux on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]] and [[UEFI]] pages. 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 (released July 2015), 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 or QHD+) and '''Wi-Fi adapter''' differences (Dell DW1560 or Intel 7265).<br />
<br />
Users with QHD+ displays should use a DE/WM that properly supports [[HiDPI]].<br />
<br />
Regarding the Wi-Fi adapter, both cards work in Arch Linux. If the Intel one works out-of-the-box thanks to mainline kernel support, the Dell DW1560 instead requires a proprietary kernel module that is not well-supported; further details are reported in the proper below section.<br />
<br />
There are no exclusive hardware differences between the ''Developer Edition'' and the standard Windows edition, so this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
The latest BIOS update is [http://www.dell.com/support/Home/us/en/19/Drivers/DriversDetails?driverId=5K69V A13] and was released on 28th August 2017. With version 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.<br />
<br />
BIOS upgrade is easy, thanks to the EFI implementation: place the update binary in the EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, press {{ic|F12}} key in order to enter in the Boot Menu and then choose ''BIOS Update''.<br />
<br />
=== Backlight ===<br />
Backlight and its control work 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 Function keys ({{ic|Fn-F10}} to {{ic|Fn-F12}}) works without any operation, as well.<br />
<br />
{{Note|By default, the keyboard backlight automatically turns off after 60 seconds of inactivity. You can change the default behaviour by editing the related ''sysfs'' entry {{ic|1=/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout}}.}}<br />
<br />
=== SSD ===<br />
This laptop series comes with a SSD as storage device, connected via SATA. This technology needs some configuration in order to achieve the best operative conditions. See [[Solid State Drives]] for further information.<br />
<br />
=== Wi-Fi ===<br />
Most configurations sport the Dell DW1560 802.11ac adapter (based on the Broadcom BCM4352 chip) which requires {{AUR|broadcom-wl}} or {{Pkg|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, instead they use an Intel Wireless 7265 card which is supported by the mainline kernel.<br />
<br />
{{Note|This card is widely available as an after-market purchase for those wishing to replace the Broadcom adapter in their laptop. This wireless adapter, other than an enviable driver support for both Wi-Fi and Bluetooth that makes installation easier, compared to the Broadcom card, it has a 2-3 times wider reception range and a much higher throughput, making it an worthwhile upgrade you should decide to do.}}<br />
<br />
=== Bluetooth ===<br />
{{Note|For uers with Intel wireless adapter with both Wi-Fi and Bluetooth, the Bluetooth 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 need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use Bluetooth.<br />
<br />
Alternatively, you can retrieve the firmware directly from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] by 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 is 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 perform [[#BIOS updates]] 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 itself to determine in which mode the sound chipset should be initialized in at boot.<br />
<br />
==== HDA mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''older than 4.4''' and again starting '''from version 4.11.5''', the sound card will be initialized in HDA mode.<br />
<br />
{{Note|To use HDA mode on excluded kernels, re-compile them with the option {{ic|1=CONFIG_ACPI_REV_OVERRIDE_POSSIBLE=y}}. This will force HDA mode on.}}<br />
<br />
===== Setting the default sound card =====<br />
By default, ALSA does not 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|If you are dual-booting with Windows, you will have to do a cold boot twice before to have sound working in Linux and vice-versa.}}<br />
<br />
{{Note|This is not necessary in I2S mode.}}<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and official Arch Linux kernels '''from 4.4 to 4.11.4''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0[http://www.spinics.net/lists/linux-acpi/msg57457.html] or newer. (I2S support was broken in mainline kernel 4.5, and fixed in Arch kernel 4.5.2 and mainline 4.8[https://bugs.archlinux.org/task/48936][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 official Arch Linux 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 the {{ic|Mic}} item. Follow the instructions below in order to achieve the goal:<br />
* open {{ic|alsamixer}} (an utility included in 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|Cycling the '''Port''' (from ''Main Microphone'' to ''Headset Microphone (unplugged)'', and back) of the '''Input Devices''' tab in the {{ic|pavucontrol}} application, has the same effect of the above instructions.}}<br />
<br />
===== Using Jack =====<br />
By default Jack recognises four capture ports and is unusable because the transport is broken into short fragments with breaks between them. Limit input to two channels with {{ic|-i2}} on the command line or the corresponding option in {{pkg|qjackctl}}'s advanced settings.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS, the touchpad should work out-of-the-box with either the synaptics or libinput drivers. The second is recommended over the former.<br />
<br />
==== Synaptics driver ====<br />
For more advanced settings with the Synaptics driver, see [[Touchpad Synaptics#Buttonless touchpads (aka ClickPads)|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 />
Refer to the specific [[libinput]] page for more details.<br />
<br />
For further configurable options (e.g. NaturalScrolling, MiddleEmulation), see {{man|1|libinput}}.<br />
<br />
=== Powersaving ===<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 />
You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour by yourself.<br />
<br />
{{Note|1=&nbsp;<br />
* With kernel 4.6+, frame-buffer compression ('''FBC''') is enabled by default, so {{ic|i915.enable_fbc}} is no longer needed.<br />
* Panel self refresh ('''PSR''') causes the display to flicker, so it has been disabled by default as of kernel 4.9 [https://bugs.freedesktop.org/show_bug.cgi?id=95176].<br />
* {{ic|1=i915.lvds_downclock=1}} for '''LVDS downclock''' is no longer needed. According to IRC #intel-gfx, ''"[...] there is a new auto-downclock for eDP panels in recent kernels and it is enabled by default if available, [...]"''.<br />
* {{ic|1=i915.enable_rc6=7}} is useless on Broadwell ('''Gen8''') systems because 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 />
=== Calibrated ICC profile ===<br />
<br />
==== QHD+ model ====<br />
{{Warning|This profile is only for QHD+ model. Do not use it if you have the FHD one.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the colour attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document. The following ICC profile is made with dispcalGUI ( {{pkg|displaycal}}) ArgyllCMS ( {{pkg|argyllcms}}) and a spectrophotometer for absolute colour accuracy; even if it is possible to achieve better results by calibrating your own monitor by yourself, in general this profile is definitively 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 for at least 30 minutes prior to start the calibration.<br />
<br />
* [https://mega.nz/#!nkNVQDCI!YYcS32HLWk1Aqry30dmOrt0wrfH9W_VczNesHQEpG_U QHD+, D65, Gamma 2.2, max luminance].<br />
<br />
== Troubleshooting ==<br />
<br />
=== DE can't connect Bluetooth devices ===<br />
If the Bluetooth GUI can't connect the device, try to use {{ic|bluetoothctl}} to connect manually.<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
Update {{pkg|xf86-video-intel}} to latest version. 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 worse performance. Switching to xf86-video-modesetting (Glamor acceleration) should not decrease performance considerably,however it is still not known if will fix the resume issue.<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 KDE ===<br />
As from kernel version 4.4 the rfkill switch works. The KDE plasma-nm (NetworkManager) widget does not indicate that wlan is active after it has been reactivated, but still connects correctly. The KDE system tray bluetooth widget usually disappears if the switch disables bluetooth, and fails to reappear when it is reactivated. You can work around this by setting the switch not to switch bluetooth in the BIOS setup. With kernel version < 4.13.11 and/or plasma-desktop < 5.11 the mouse pointer may freeze first time that the rfkill switch is used. To unfreeze it, switch to another virtual console and back.<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 affect only touchscreen model owners. The fix consists in removing "keyboard" from the HOOKS array in /etc/mkinitcpio.conf. If you need the keyboard at boot, edit the MODULES array as follow MODULES="atkbd usbhid hid-generic". 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 ('''NOT''' a simple reboot, shut it down and turn it back on again) to make sound working again.<br />
<br />
Refer to the [[#HDA mode]] 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 Linux bug report].<br />
<br />
=== Loud cracks/noise during boot or audio playback ===<br />
Some users have reported the above sound problems, as described [https://bbs.archlinux.org/viewtopic.php?id=208496 here] for example.<br />
<br />
[[Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback|Disabling audio powersafe]] may work for people using the '''HDA''' audio mode.<br />
<br />
However, it is still unknown how to solve this issue for the '''I2S''' audio mode.<br />
<br />
For further reference, see the corresponding [https://bugzilla.kernel.org/show_bug.cgi?id=112611 kernel bug entry].<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
* [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop//xps-13-9343-laptop_Service%20Manual_en-us.pdf Service Manual for Dell XPS 13 (9343)]<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=474334Dell XPS 13 (9343)2017-04-16T10:05:58Z<p>DonJaime: /* Audio */ Instructions for making Jack usable</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9343)]]<br />
{{Note|This page refers to the ''early'' 2015 model of XPS 13. For the ''late'' 2015 model, see [[Dell XPS 13 (9350)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| Video || {{G|Working}}<br />
|-<br />
| Backlight control || {{G|Working}}<br />
|-<br />
| Wi-Fi || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Wireless switch || {{Y|Working ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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[https://bartongeorge.io/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/]. 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 Linux 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 and this means Installation Media newer than 2015.08.01 (release date: 2015-08-01) should all be able to boot this machine without problems.<br />
<br />
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 or QHD+) and '''Wi-Fi adapter''' differences (Dell DW1560 or Intel 7265).<br />
<br />
For users with QHD+ display, they need to use a DE/WM that properly supports [[HiDPI]].<br />
Regarding the Wi-Fi adapter, both cards work in Arch Linux; while the Intel 7265 has mainline kernel support, hence it will work out-of-the-box, the Dell DW1560 instead requires a proprietary kernel module that is not well-supported; further details are in the proper below section.<br />
<br />
There are no exclusive hardware differences between the ''Developer Edition'' and the ''classical edition'' (the one with Windows) of this laptop that means this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
Best practice is to install and use software on the latest BIOS version and this laptop makes no difference.<br />
<br />
The latest BIOS update is [http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=MYXCY&fileId=3598184217 A11] and was released on 2017-02-02. 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.<br />
<br />
BIOS upgrade is easy, thanks to the EFI implementation: store the update binary on the EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, press {{ic|F12}} key in order to enter in the Boot Menu and then choose ''BIOS Update''.<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 Function 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 technology needs some configuration in order to achieve the best operative conditions. See [[Solid State Drives]] for information.<br />
<br />
=== Wi-Fi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (based on the Broadcom BCM4352 chip) which requires {{AUR|broadcom-wl}} or {{Pkg|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 they use an Intel Wireless 7265 card, which is supported by the mainline kernel. This card is widely available as an after-market purchase for those wishing to replace the Broadcom adapter in their laptop. This wireless adapter, other than an enviable driver support, for both Wi-Fi and Bluetooth, that makes installation easier, compared to the Broadcom card, it has a 2-3 times wider reception range and a much higher throughput [citation needed], making it an worthwhile upgrade should you decide to do so.<br />
<br />
=== Bluetooth ===<br />
{{Note|users with Intel wireless adapter with both Wi-Fi and Bluetooth, the Bluetooth 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 need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use Bluetooth.<br />
<br />
Alternatively, you can retrieve the firmware directly from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] by 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 is 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 official Arch Linux 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 by using that kernel.<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 official Arch Linux kernel '''4.4 or newer''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0[http://www.spinics.net/lists/linux-acpi/msg57457.html] or newer.<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 official Arch Linux kernel 4.5.2+[https://bugs.archlinux.org/task/48936]; anyhow, a better fix[https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?h=topic/intel&id=a395bdd6b24b692adbce0df6510ec9f2af57573e] is included in kernel 4.8.}}<br />
<br />
===== Enabling the microphone =====<br />
{{Note|The microphone appears to be enabled by default as of official Arch Linux 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|Cycling the '''Port''' (from ''Main Microphone'' to ''Headset Microphone (unplugged)'', and back) of the '''Input Devices''' tab in the {{ic|pavucontrol}} application, has the same effect of the above instructions.}}<br />
<br />
===== Using Jack =====<br />
By default Jack recognises four capture ports and is unusable because the transport is broken into short fragments with breaks between them. Limit input to two channels with {{ic|-i2}} on the command line or the corresponding option in {{pkg|qjackctl}}'s advanced settings.<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 />
You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour by yourself.<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}} parameters are no longer needed. Kernel 4.6.2+ is recommended as older kernels may cause the display to flicker.<br />
* Soon panel self-refresh (PSR) will be disabled again. [https://patchwork.freedesktop.org/patch/127188/] Commit 2ee7dc497e348eecbb82adbb1ea9e9a7e29fe921 (drm/i915: disable PSR by default on HSW/BDW) landed on 2016-12-14 and is marked for inclusion in the stable kernel. Kernel 4.9 is already ''affected''. This is the reference bug [https://bugs.freedesktop.org/show_bug.cgi?id=95176].<br />
* {{ic|1=i915.lvds_downclock=1}} for LVDS downclock is no longer needed. According to IRC #intel-gfx, "there is a new auto-downclock for eDP panels in recent kernels and it is enabled by default if available, so do not 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+ hardwares.[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 ===<br />
<br />
==== QHD+ model ====<br />
<br />
{{Warning|This profile is only for QHD+ model. Do not use it if you have the FHD one.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the colour attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document. The following ICC profile is made with dispcalGUI ( {{pkg|displaycal}}), ArgyllCMS ( {{pkg|argyllcms}}) and a spectrophotometer for absolute colour accuracy; even if it is possible to achieve better results by calibrating your own monitor by yourself, in general this profile is definitively 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 for at least 30 minutes prior to start 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 KDE ===<br />
With recent kernel versions (as from 4.4) the rfkill switch works. Under the KDE desktop, the first time that the rfkill switch is used, the mouse pointer freezes. To unfreeze it, switch to another virtual console and back.<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 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 stock Linux 4.4 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 Linux 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]. [[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 />
=== Display freezes while manipulating external displays with Xrandr / random blanking ===<br />
{{ic|xrandr}} commands (for eg. [[HiDPI#Multiple displays]]) can result in display freezes with no clear journalctl or Xorg error logs.<br />
Reported to occur for QHD models running kernel version 4.3.x and up [https://wiki.gentoo.org/wiki/Dell_XPS_13_9343#GPU_hang.2Ffreeze4_with_external_display] [[Intel graphics#Skylake support]]. Setting [[kernel parameter]] {{ic|i915.preliminary_hw_support&#61;0}} can reduce or remove this issue.<br />
<br />
If you are experiencing freezes in GNOME on Login and/or after, be sure you have latest BIOS installed and disabled the C state feature.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
* [http://downloads.dell.com/Manuals/all-products/esuprt_laptop/esuprt_xps_laptop//xps-13-9343-laptop_Service%20Manual_en-us.pdf Service Manual for Dell XPS 13 (9343)]<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=468015Dell XPS 13 (9343)2017-02-09T19:51:43Z<p>DonJaime: /* BIOS updates */ Update for BIOS version A11</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9343)]]<br />
{{Note|This page refers to the ''early'' 2015 model of XPS 13. For the ''late'' 2015 model, see [[Dell XPS 13 (9350)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status'''<br />
|-<br />
| Video || {{G|Working}}<br />
|-<br />
| Backlight control || {{G|Working}}<br />
|-<br />
| Wi-Fi || {{G|Working}}<br />
|-<br />
| Bluetooth || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| Touchpad || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Wireless switch || {{Y|Working ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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[https://bartongeorge.io/2015/04/09/4th-gen-dell-xps-13-developer-edition-available/]. 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 Linux 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 and this means Installation Media newer than 2015.08.01 (release date: 2015-08-01) should all be able to boot this machine without problems.<br />
<br />
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 or QHD+) and '''Wi-Fi adapter''' differences (Dell DW1560 or Intel 7265).<br />
<br />
For users with QHD+ display, they need to use a DE/WM that properly supports [[HiDPI]].<br />
Regarding the Wi-Fi adapter, both cards work in Arch Linux; while the Intel 7265 has mainline kernel support, hence it will work out-of-the-box, the Dell DW1560 instead requires a proprietary kernel module that is not well-supported; further details are in the proper below section.<br />
<br />
There are no exclusive hardware differences between the ''Developer Edition'' and the ''classical edition'' (the one with Windows) of this laptop that means this guide is equally applicable to both models.<br />
<br />
== Configuration ==<br />
<br />
=== BIOS updates ===<br />
Best practice is to install and use software on the latest BIOS version and this laptop makes no difference.<br />
<br />
The latest BIOS update is [http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=MYXCY&fileId=3598184217 A11] and was released on 2017-02-02. 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.<br />
<br />
BIOS upgrade is easy, thanks to the EFI implementation: store the update binary on the EFI partition ({{ic|/boot/EFI}}) or on a USB flash drive, reboot, press {{ic|F12}} key in order to enter in the Boot Menu and then choose ''BIOS Update''.<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 Function 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 />
=== Wi-Fi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (based on the Broadcom BCM4352 chip) 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 they use an Intel Wireless 7265 card, which is supported by the mainline kernel. This card is widely available as an after-market purchase for those wishing to replace the Broadcom adapter in their laptop. This wireless adapter, other than an enviable driver support, for both Wi-Fi and Bluetooth, that makes installation easier, compared to the Broadcom card, it has a 2-3 times wider reception range and a much higher throughput [citation needed], making it an worthwhile upgrade should you decide to do so.<br />
<br />
=== Bluetooth ===<br />
{{Note|users with Intel wireless adapter with both Wi-Fi and Bluetooth, the Bluetooth 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 need to install {{AUR|bcm20702a1-firmware}} and reboot if you want to use Bluetooth.<br />
<br />
Alternatively, you can retrieve the firmware directly from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver] by 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 is 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 official Arch Linux 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 by using that kernel.<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 official Arch Linux kernel '''4.4 or newer''', the sound card will be initialized in I2S mode. I2S support requires {{pkg|alsa-lib}} 1.1.0[http://www.spinics.net/lists/linux-acpi/msg57457.html] or newer.<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 official Arch Linux kernel 4.5.2+[https://bugs.archlinux.org/task/48936]; anyhow, a better fix[https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?h=topic/intel&id=a395bdd6b24b692adbce0df6510ec9f2af57573e] is included in kernel 4.8.}}<br />
<br />
===== Enabling the microphone =====<br />
{{Note|The microphone appears to be enabled by default as of official Arch Linux 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|Cycling the '''Port''' (from ''Main Microphone'' to ''Headset Microphone (unplugged)'', and back) of the '''Input Devices''' tab in the {{ic|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 />
You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour by yourself.<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}} parameters are no longer needed. Kernel 4.6.2+ is recommended as older kernels may cause the display to flicker.<br />
* Soon panel self-refresh (PSR) will be disabled again. [https://patchwork.freedesktop.org/patch/127188/] Commit 2ee7dc497e348eecbb82adbb1ea9e9a7e29fe921 (drm/i915: disable PSR by default on HSW/BDW) landed on 2016-12-14 and is marked for inclusion in the stable kernel. Kernel 4.9 is already ''affected''. This is the reference bug [https://bugs.freedesktop.org/show_bug.cgi?id=95176].<br />
* {{ic|1=i915.lvds_downclock=1}} for LVDS downclock is no longer needed. According to IRC #intel-gfx, "there is a new auto-downclock for eDP panels in recent kernels and it is enabled by default if available, so do not 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+ hardwares.[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 ===<br />
<br />
==== QHD+ model ====<br />
<br />
{{Warning|This profile is only for QHD+ model. Do not use it if you have the FHD one.}}<br />
<br />
An [[ICC profiles|ICC profile]] is a binary file which contains precise data regarding the colour attributes of the monitor. It allows you to produce consistent and repeatable results for graphic and document. The following ICC profile is made with dispcalGUI ( {{pkg|displaycal}}), ArgyllCMS ( {{pkg|argyllcms}}) and a spectrophotometer for absolute colour accuracy; even if it is possible to achieve better results by calibrating your own monitor by yourself, in general this profile is definitively 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 for at least 30 minutes prior to start 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 KDE ===<br />
With recent kernel versions (as from 4.4) the rfkill switch works. Under the KDE desktop, the first time that the rfkill switch is used, the mouse pointer freezes. To unfreeze it, switch to another virtual console and back.<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 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 stock Linux 4.4 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 Linux 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 />
=== Display freezes while manipulating external displays with Xrandr / random blanking ===<br />
{{ic|xrandr}} commands (for eg. [[HiDPI#Multiple_displays]]) can result in display freezes with no clear journalctl or Xorg error logs.<br />
Reported to occur for QHD models running kernel version 4.3.x and up [https://wiki.gentoo.org/wiki/Dell_XPS_13_9343#GPU_hang.2Ffreeze4_with_external_display] [https://wiki.archlinux.org/index.php/Intel_graphics#Skylake_support]. Setting [[kernel parameter]] {{ic|i915.preliminary_hw_support&#61;0}} can reduce or remove this issue.<br />
<br />
If you are experiencing freezes in GNOME on Login and/or after, be sure you have latest BIOS installed and disabled the C state feature.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=456154Dell XPS 13 (9343)2016-11-06T11:46:33Z<p>DonJaime: Correct revision 456153 by DonJaime (talk)</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 ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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 />
Dell does no longer show bios versions higher than A07 on their site. You can download BIOS version A08 and A09 from here:<br />
* [https://mega.nz/#!20U2VRBI!FRam__6wjlOjRejd0Oy4Wtof6wdkTkyUUBBz8oTtOno BIOS A08] md5sum: d1df9447f119ce5cb90ebea875a22cd9<br />
* [https://please.insert/link BIOS A09] md5sum: please-insert-link<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 KDE ===<br />
With recent kernel versions (as from 4.4) the rfkill switch works. Under the KDE desktop, the first time that the rfkill switch is used, the mouse pointer freezes. To unfreeze it, switch to another virtual console and back.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=456153Dell XPS 13 (9343)2016-11-06T11:43:11Z<p>DonJaime: /* rfkill issues with kde */ Update to reflect the fact that 1. the switch works and 2. the problem is not confined to Broadcom</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 ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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 />
Dell does no longer show bios versions higher than A07 on their site. You can download BIOS version A08 and A09 from here:<br />
* [https://mega.nz/#!20U2VRBI!FRam__6wjlOjRejd0Oy4Wtof6wdkTkyUUBBz8oTtOno BIOS A08] md5sum: d1df9447f119ce5cb90ebea875a22cd9<br />
* [https://please.insert/link BIOS A09] md5sum: please-insert-link<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 kde ===<br />
With recent kernel versions (as from 4.4) the rfkill switch works. Under the KDE desktop, the first time that the rfkill switch is used, the mouse pointer freezes. To unfreeze it, switch to another virtual console and back.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=456152Dell XPS 13 (9343)2016-11-06T11:41:07Z<p>DonJaime: Adapt link to corrected title</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 ([[#rfkill_issues_with_KDE|Some issues with kde]])}}<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 />
Dell does no longer show bios versions higher than A07 on their site. You can download BIOS version A08 and A09 from here:<br />
* [https://mega.nz/#!20U2VRBI!FRam__6wjlOjRejd0Oy4Wtof6wdkTkyUUBBz8oTtOno BIOS A08] md5sum: d1df9447f119ce5cb90ebea875a22cd9<br />
* [https://please.insert/link BIOS A09] md5sum: please-insert-link<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=456151Dell XPS 13 (9343)2016-11-06T11:39:30Z<p>DonJaime: /* rfkill issues with kde */ Update to reflect the fact that 1. the switch works and 2. the KDE problem is not confined to Broadcom</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 />
Dell does no longer show bios versions higher than A07 on their site. You can download BIOS version A08 and A09 from here:<br />
* [https://mega.nz/#!20U2VRBI!FRam__6wjlOjRejd0Oy4Wtof6wdkTkyUUBBz8oTtOno BIOS A08] md5sum: d1df9447f119ce5cb90ebea875a22cd9<br />
* [https://please.insert/link BIOS A09] md5sum: please-insert-link<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 KDE ===<br />
With recent kernel versions (as from 4.4) the rfkill switch works. Under the KDE desktop, the mouse pointer freezes the first time that the rfkill switch is used. To unfreeze it, switch to another virtual console and back.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=448573Dell XPS 13 (9343)2016-08-29T09:44:36Z<p>DonJaime: /* Bluetooth */ Change to maintained AUR package for bluetooth firmware</p>
<hr />
<div>B[[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)]].}}<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=KTW00 BIOS update A08] was released on 2016-08-24. 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 />
=== 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 />
=== Random hangs after login with external monitor ===<br />
<br />
Very often, three-quarters of times, if I boot up the machine with an external monitor connected (I use a miniDP to HDMI cable), the computer hangs after I login in through graphical display manager. i.e. in my case, using GDM to login in into gnome desktop, after I enter the password, cursor disappears and system becomes totally unresponsive; the only way to "continue" is to force a reboot by pressing the power button.<br />
I don't know if it was only a problem of mine due to a strange hardware/software combination but, anyway and fortunately, it seems fixed ''starting from May 2016'', likely thanks to a kernel bug fix. This mean {{ic|kernel-lts}} users may still suffer of this issue.<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 />
== 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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=424968Dell XPS 13 (9343)2016-03-10T08:05:02Z<p>DonJaime: /* Bluetooth */ Refer to AUR package for bluetooth firmware</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)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<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|bt-dw1560-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 />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and Arch kernel 4.4 or newer, the sound card will be initialized in I2S mode.<br />
{{Note|I2S regressed: in 4.5-rc6 and 4.5-rc7 'aplay -l' doesn't even show broadwell-rt286 anymore. Expect a regression when 4.5 hits stable.}}<br />
<br />
I2S support in Linux is quite nascent and wasn't up to par with HDA support until recently, so a quirk flag was enabled in the mainline kernel that would force HDA mode on.[http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039] This flag has been disabled in the stock Arch kernel as of 4.4.[https://bugs.archlinux.org/task/47710] Also note that I2S support is known to be broken with older versions of alsalib.[http://www.spinics.net/lists/linux-acpi/msg57457.html]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<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]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. 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 />
=== High quality ICC monitor profiles ===<br />
An 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. Since every monitor is different it is possible to achieve better results calibrating your own monitor, but if you don't have a colorimeter or a spectrophotometer you will get far better results with the following XYZ LUT + MATRIX profiles made with a ~3500 patches testchart instead of the canned ones. If you previously didn't install a canned profile you will notice a night and day difference in color accuracy. Do not use a profile made for the QHD+ version with the FHD one and vice versa.<br />
The profiles 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 />
{{Note|You should disable Dynamic Brightness Control to accurately calibrate the QHD+ display: https://github.com/advancingu/XPS13Linux/issues/2}}<br />
<br />
* FHD, D65, Gamma 2.2, max luminance: coming soon (I will get my hands on the FHD monitor in February.) However, it may not be possible to accurately calibrate the FHD display due to the dynamic contrast behaviour of the panel which cannot be disabled.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
For kernel >= 4.4, the touchpad description is "DLL0665:01 06CB:76AD Touchpad".<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seems to have been fixed, and freezes happen significantly less often. However, heavy flickering may still occur with external monitors.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As of kernel version 4.3.3 it still causes occasional flickering but no longer so mch as to be unusable.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<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 [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<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). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<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. See the Audio section above for more information.<br />
<br />
It is reported that recompiling the kernel with the CONFIG_ACPI_REV_OVERRIDE_POSSIBLE option will re-enable the microphone. See the [https://bbs.archlinux.org/viewtopic.php?id=208674 BBS thread] and [https://bugs.archlinux.org/task/47989 bug report] for information.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=419942Dell XPS 13 (9343)2016-02-10T13:58:32Z<p>DonJaime: /* rfkill issues with Broadcom wireless */ UPdate for kernel 4.4</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)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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 />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and Arch kernel 4.4 or newer, the sound card will be initialized in I2S mode.<br />
<br />
I2S support in Linux is quite nascent and wasn't up to par with HDA support until recently, so a quirk flag was enabled in the mainline kernel that would force HDA mode on.[http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039] This flag has been disabled in the stock Arch kernel as of 4.4.[https://bugs.archlinux.org/task/47710] Also note that I2S support is known to be broken with older versions of alsalib.[http://www.spinics.net/lists/linux-acpi/msg57457.html]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<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]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. 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 />
=== High quality ICC monitor profiles ===<br />
An 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. Since every monitor is different it is possible to achieve better results calibrating your own monitor, but if you don't have a colorimeter or a spectrophotometer you will get far better results with the following XYZ LUT + MATRIX profiles made with a ~3500 patches testchart instead of the canned ones. If you previously didn't install a canned profile you will notice a night and day difference in color accuracy. Do not use a profile made for the QHD+ version with the FHD one and vice versa.<br />
The profiles 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 />
{{Note|You should disable Dynamic Brightness Control to accurately calibrate the QHD+ display: https://github.com/advancingu/XPS13Linux/issues/2}}<br />
<br />
* FHD, D65, Gamma 2.2, max luminance: coming soon (I will get my hands on the FHD monitor in February.) However, it may not be possible to accurately calibrate the FHD display due to the dynamic contrast behaviour of the panel which cannot be disabled.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seems to have been fixed, and freezes happen significantly less often. However, heavy flickering may still occur with external monitors.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As of kernel version 4.3.3 it still causes occasional flickering but no longer so mch as to be unusable.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<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 [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<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). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<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. See the Audio section above for more information.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=419940Dell XPS 13 (9343)2016-02-10T13:54:16Z<p>DonJaime: /* EFISTUB does not boot */ Still there in A07...</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)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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 />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
With BIOS A02+ and Arch kernel 4.4 or newer, the sound card will be initialized in I2S mode.<br />
<br />
I2S support in Linux is quite nascent and wasn't up to par with HDA support until recently, so a quirk flag was enabled in the mainline kernel that would force HDA mode on.[http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039] This flag has been disabled in the stock Arch kernel as of 4.4.[https://bugs.archlinux.org/task/47710] Also note that I2S support is known to be broken with older versions of alsalib.[http://www.spinics.net/lists/linux-acpi/msg57457.html]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<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]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. 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 />
=== High quality ICC monitor profiles ===<br />
An 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. Since every monitor is different it is possible to achieve better results calibrating your own monitor, but if you don't have a colorimeter or a spectrophotometer you will get far better results with the following XYZ LUT + MATRIX profiles made with a ~3500 patches testchart instead of the canned ones. If you previously didn't install a canned profile you will notice a night and day difference in color accuracy. Do not use a profile made for the QHD+ version with the FHD one and vice versa.<br />
The profiles 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 />
{{Note|You should disable Dynamic Brightness Control to accurately calibrate the QHD+ display: https://github.com/advancingu/XPS13Linux/issues/2}}<br />
<br />
* FHD, D65, Gamma 2.2, max luminance: coming soon (I will get my hands on the FHD monitor in February.) However, it may not be possible to accurately calibrate the FHD display due to the dynamic contrast behaviour of the panel which cannot be disabled.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seems to have been fixed, and freezes happen significantly less often. However, heavy flickering may still occur with external monitors.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As of kernel version 4.3.3 it still causes occasional flickering but no longer so mch as to be unusable.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<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 />
The wireless switch key (to the right of the "Brightness up" key) switches the wireless card on/off at the hardware level, but the Broadcom driver does 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 [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<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). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<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. See the Audio section above for more information.<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=416838Talk:Dell XPS 13 (9343)2016-01-23T12:47:11Z<p>DonJaime: /* Powersaving */</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 />
<s>== wifi during installation ==</s><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 />
::Closing this discussion. This is a general point that should maybe be mentioned in the Beginner's Guide, but not here.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:44, 23 January 2016 (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 />
Enabling Tearfree in the xorg config seems to help somewhat.<br />
[[User:Mnhagan01|Mnhagan01]] ([[User talk:Mnhagan01|talk]]) 14:34, 5 November 2015 (UTC)<br />
<br />
Flickering and freezes have improved by kernel 4.3.3. I've edited the page to reflect this.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:30, 14 January 2016 (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 />
:If you aren't quick enough with the enter key, releasing it can wake the computer up. Try '''sleep 1s; xset dpms force off''' and if that works you can delete this section. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:37, 14 January 2016 (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 />
:[http://paste.debian.net/319130/ There is a test patch for palm detection] [[User:Dx2|Dx2]] ([[User talk:Dx2|talk]]) 11:05, 3 November 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 />
== 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?<br />
<br />
:I'm planning on buying one of these, I'll update the page with any problems I run into. There's some discussion on the Dell forums about linux support [http://en.community.dell.com/techcenter/os-applications/f/4613/t/19659067 here], seems like everything was working for them except WiFi. [[User:Xymostech|Xymostech]] ([[User talk:Xymostech|talk]]) 01:37, 5 November 2015 (UTC)<br />
<br />
A new section or page should be made for the late 2013 xps 13 (9350). Most of this information for the earlier version do not apply. Wifi for dell xps 13 skylake is using a dw1802a chip which is a broadcom 4350. 4350 is in mainline kernel support from 4.4 onwards. There is a patch that can be applied to kernel and user must extract the 4350 driver from 4.4 branch. Besides that, the skylake intel video can enter X only if i915.preliminary_hw_support=1 in kernel boot command. There is something very wrong with the video though. There are two things that aren't working OOB besides wifi. Brightness keys f11, f12 are not registered as keys by xbindkeys -k and they do not work. Video played crashes X along with random but frequent screen flickering. [[User:Frank604|Frank604]] ([[User talk:Frank604|talk]]) 17:56, 13 November 2015 (UTC)<br />
<br />
== UXA vs. SNA and Suspend Issue ==<br />
<br />
The wiki suggests switching the Intel Graphics Acceleration from UXA to SNA "... [i]f you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend [...]." I myself encountered an issue using XFCE + LightDM where, after resuming from suspend and successfully unlocking the screen, the screen would fade to black and become unresponsive. Switching to UXA removed the issue and made suspend/resume reliable.<br />
<br />
Clearly this is a workaround; UXA performance is pretty bad (with compositing, XFCE's alt-tab takes about 2 seconds to respond on my setup). Does anyone have more information about how SNA could affect a DE's suspend/resume routine? Ubuntu users have reported a similar bug [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437807 here], and it appears that the issue doesn't affect Unity DE. Can anyone using Unity under Arch confirm that?<br />
<br />
: SNA is simply less tested (and therefore less reliable) than UXA. Consider filing an upstream bug report, but first, see if any of these match your issue: https://bugs.freedesktop.org/buglist.cgi?quicksearch=sna%20suspend [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 21:17, 27 October 2015 (UTC)<br />
<br />
== Unsetting CONFIG_ACPI_REV_OVERRIDE_POSSIBLE ==<br />
<br />
https://bugs.archlinux.org/task/47710<br />
Since version 4.4 Linux has working I2S audio for the XPS 13 2015, so we can finally unset this ugly workaround with kernel versions >= 4.4. Fedora Rawhide already disabled it.</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=416837Talk:Dell XPS 13 (9343)2016-01-23T12:44:23Z<p>DonJaime: /* wifi during installation */ Closing</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 />
<s>== wifi during installation ==</s><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 />
::Closing this discussion. This is a general point that should maybe be mentioned in the Beginner's Guide, but not here.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:44, 23 January 2016 (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 />
Enabling Tearfree in the xorg config seems to help somewhat.<br />
[[User:Mnhagan01|Mnhagan01]] ([[User talk:Mnhagan01|talk]]) 14:34, 5 November 2015 (UTC)<br />
<br />
FLickering and freezes seem to be thing of the past with kernel 4.3.3. I've edited the page to reflect this.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:30, 14 January 2016 (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 />
:If you aren't quick enough with the enter key, releasing it can wake the computer up. Try '''sleep 1s; xset dpms force off''' and if that works you can delete this section. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:37, 14 January 2016 (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 />
:[http://paste.debian.net/319130/ There is a test patch for palm detection] [[User:Dx2|Dx2]] ([[User talk:Dx2|talk]]) 11:05, 3 November 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 />
== 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?<br />
<br />
:I'm planning on buying one of these, I'll update the page with any problems I run into. There's some discussion on the Dell forums about linux support [http://en.community.dell.com/techcenter/os-applications/f/4613/t/19659067 here], seems like everything was working for them except WiFi. [[User:Xymostech|Xymostech]] ([[User talk:Xymostech|talk]]) 01:37, 5 November 2015 (UTC)<br />
<br />
A new section or page should be made for the late 2013 xps 13 (9350). Most of this information for the earlier version do not apply. Wifi for dell xps 13 skylake is using a dw1802a chip which is a broadcom 4350. 4350 is in mainline kernel support from 4.4 onwards. There is a patch that can be applied to kernel and user must extract the 4350 driver from 4.4 branch. Besides that, the skylake intel video can enter X only if i915.preliminary_hw_support=1 in kernel boot command. There is something very wrong with the video though. There are two things that aren't working OOB besides wifi. Brightness keys f11, f12 are not registered as keys by xbindkeys -k and they do not work. Video played crashes X along with random but frequent screen flickering. [[User:Frank604|Frank604]] ([[User talk:Frank604|talk]]) 17:56, 13 November 2015 (UTC)<br />
<br />
== UXA vs. SNA and Suspend Issue ==<br />
<br />
The wiki suggests switching the Intel Graphics Acceleration from UXA to SNA "... [i]f you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend [...]." I myself encountered an issue using XFCE + LightDM where, after resuming from suspend and successfully unlocking the screen, the screen would fade to black and become unresponsive. Switching to UXA removed the issue and made suspend/resume reliable.<br />
<br />
Clearly this is a workaround; UXA performance is pretty bad (with compositing, XFCE's alt-tab takes about 2 seconds to respond on my setup). Does anyone have more information about how SNA could affect a DE's suspend/resume routine? Ubuntu users have reported a similar bug [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437807 here], and it appears that the issue doesn't affect Unity DE. Can anyone using Unity under Arch confirm that?<br />
<br />
: SNA is simply less tested (and therefore less reliable) than UXA. Consider filing an upstream bug report, but first, see if any of these match your issue: https://bugs.freedesktop.org/buglist.cgi?quicksearch=sna%20suspend [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 21:17, 27 October 2015 (UTC)<br />
<br />
== Unsetting CONFIG_ACPI_REV_OVERRIDE_POSSIBLE ==<br />
<br />
https://bugs.archlinux.org/task/47710<br />
Since version 4.4 Linux has working I2S audio for the XPS 13 2015, so we can finally unset this ugly workaround with kernel versions >= 4.4. Fedora Rawhide already disabled it.</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=416834Dell XPS 13 (9343)2016-01-23T12:39:06Z<p>DonJaime: /* Powersaving */ Correct good news about flickers and freezes with i915 kernel parameters</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)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<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]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. 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 />
=== High quality ICC monitor profiles ===<br />
An 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. Since every monitor is different it is possible to achieve better results calibrating your own monitor, but if you don't have a colorimeter or a spectrophotometer you will get far better results with the following XYZ LUT + MATRIX profiles made with a ~3500 patches testchart instead of the canned ones. If you previously didn't install a canned profile you will notice a night and day difference in color accuracy. Do not use a profile made for the QHD+ version with the FHD one and vice versa.<br />
The profiles 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. The monitor has been turned on for at least 30 minutes before commencing the calibration.<br />
<br />
* QHD+, D65, Gamma 2.2, max luminance: https://mega.nz/#!LpMGUJCD!cqGOyY-BCHL3znTZI-kwwagLWD0gnaarKTurdzRH1Qo<br />
<br />
{{Note|You should disbale Dynamic Brightness Control to accurately calibrate the QHD+ display: https://github.com/advancingu/XPS13Linux/issues/2}}<br />
{{Note|This profile has been made with DBC on, so I will upload another profile with DBC off}}<br />
<br />
* FHD, D65, Gamma 2.2, max luminance: coming soon (I will get my hands on the FHD monitor in February)<br />
<br />
{{Note|It may not be possible to accurately calibrate the FHD display due to the dynamic contrast behaviour of the panel which cannot be disabled}}<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seems to have been fixed, and freezes happen significantly less often.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As of kernel version 4.3.3 it still causes occasional flickering but no longer so mch as to be unusable.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<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.<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 />
The wireless switch key (to the right of the "Brightness up" key) switches the wireless card on/off at the hardware level, but the Broadcom driver does 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 A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<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). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=415354Talk:Dell XPS 13 (9343)2016-01-14T13:37:19Z<p>DonJaime: /* LCD backlight */</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 />
Enabling Tearfree in the xorg config seems to help somewhat.<br />
[[User:Mnhagan01|Mnhagan01]] ([[User talk:Mnhagan01|talk]]) 14:34, 5 November 2015 (UTC)<br />
<br />
FLickering and freezes seem to be thing of the past with kernel 4.3.3. I've edited the page to reflect this.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:30, 14 January 2016 (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 />
:If you aren't quick enough with the enter key, releasing it can wake the computer up. Try '''sleep 1s; xset dpms force off''' and if that works you can delete this section. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:37, 14 January 2016 (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 />
:[http://paste.debian.net/319130/ There is a test patch for palm detection] [[User:Dx2|Dx2]] ([[User talk:Dx2|talk]]) 11:05, 3 November 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 />
== 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?<br />
<br />
:I'm planning on buying one of these, I'll update the page with any problems I run into. There's some discussion on the Dell forums about linux support [http://en.community.dell.com/techcenter/os-applications/f/4613/t/19659067 here], seems like everything was working for them except WiFi. [[User:Xymostech|Xymostech]] ([[User talk:Xymostech|talk]]) 01:37, 5 November 2015 (UTC)<br />
<br />
A new section or page should be made for the late 2013 xps 13 (9350). Most of this information for the earlier version do not apply. Wifi for dell xps 13 skylake is using a dw1802a chip which is a broadcom 4350. 4350 is in mainline kernel support from 4.4 onwards. There is a patch that can be applied to kernel and user must extract the 4350 driver from 4.4 branch. Besides that, the skylake intel video can enter X only if i915.preliminary_hw_support=1 in kernel boot command. There is something very wrong with the video though. There are two things that aren't working OOB besides wifi. Brightness keys f11, f12 are not registered as keys by xbindkeys -k and they do not work. Video played crashes X along with random but frequent screen flickering. [[User:Frank604|Frank604]] ([[User talk:Frank604|talk]]) 17:56, 13 November 2015 (UTC)<br />
<br />
== UXA vs. SNA and Suspend Issue ==<br />
<br />
The wiki suggests switching the Intel Graphics Acceleration from UXA to SNA "... [i]f you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend [...]." I myself encountered an issue using XFCE + LightDM where, after resuming from suspend and successfully unlocking the screen, the screen would fade to black and become unresponsive. Switching to UXA removed the issue and made suspend/resume reliable.<br />
<br />
Clearly this is a workaround; UXA performance is pretty bad (with compositing, XFCE's alt-tab takes about 2 seconds to respond on my setup). Does anyone have more information about how SNA could affect a DE's suspend/resume routine? Ubuntu users have reported a similar bug [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437807 here], and it appears that the issue doesn't affect Unity DE. Can anyone using Unity under Arch confirm that?<br />
<br />
: SNA is simply less tested (and therefore less reliable) than UXA. Consider filing an upstream bug report, but first, see if any of these match your issue: https://bugs.freedesktop.org/buglist.cgi?quicksearch=sna%20suspend [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 21:17, 27 October 2015 (UTC)<br />
<br />
== Unsetting CONFIG_ACPI_REV_OVERRIDE_POSSIBLE ==<br />
<br />
https://bugs.archlinux.org/task/47710<br />
Since version 4.4 Linux has working I2S audio for the XPS 13 2015, so we can finally unset this ugly workaround with kernel versions >= 4.4. Fedora Rawhide already disabled it.</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=415353Talk:Dell XPS 13 (9343)2016-01-14T13:36:51Z<p>DonJaime: /* LCD backlight */</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 />
Enabling Tearfree in the xorg config seems to help somewhat.<br />
[[User:Mnhagan01|Mnhagan01]] ([[User talk:Mnhagan01|talk]]) 14:34, 5 November 2015 (UTC)<br />
<br />
FLickering and freezes seem to be thing of the past with kernel 4.3.3. I've edited the page to reflect this.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:30, 14 January 2016 (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 />
:If you aren't quick enough with the enter key, releasing it can wake the computer up. Try '''sleep 1s; xset dpms force off''' and if that works you can delete this section.<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 />
:[http://paste.debian.net/319130/ There is a test patch for palm detection] [[User:Dx2|Dx2]] ([[User talk:Dx2|talk]]) 11:05, 3 November 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 />
== 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?<br />
<br />
:I'm planning on buying one of these, I'll update the page with any problems I run into. There's some discussion on the Dell forums about linux support [http://en.community.dell.com/techcenter/os-applications/f/4613/t/19659067 here], seems like everything was working for them except WiFi. [[User:Xymostech|Xymostech]] ([[User talk:Xymostech|talk]]) 01:37, 5 November 2015 (UTC)<br />
<br />
A new section or page should be made for the late 2013 xps 13 (9350). Most of this information for the earlier version do not apply. Wifi for dell xps 13 skylake is using a dw1802a chip which is a broadcom 4350. 4350 is in mainline kernel support from 4.4 onwards. There is a patch that can be applied to kernel and user must extract the 4350 driver from 4.4 branch. Besides that, the skylake intel video can enter X only if i915.preliminary_hw_support=1 in kernel boot command. There is something very wrong with the video though. There are two things that aren't working OOB besides wifi. Brightness keys f11, f12 are not registered as keys by xbindkeys -k and they do not work. Video played crashes X along with random but frequent screen flickering. [[User:Frank604|Frank604]] ([[User talk:Frank604|talk]]) 17:56, 13 November 2015 (UTC)<br />
<br />
== UXA vs. SNA and Suspend Issue ==<br />
<br />
The wiki suggests switching the Intel Graphics Acceleration from UXA to SNA "... [i]f you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend [...]." I myself encountered an issue using XFCE + LightDM where, after resuming from suspend and successfully unlocking the screen, the screen would fade to black and become unresponsive. Switching to UXA removed the issue and made suspend/resume reliable.<br />
<br />
Clearly this is a workaround; UXA performance is pretty bad (with compositing, XFCE's alt-tab takes about 2 seconds to respond on my setup). Does anyone have more information about how SNA could affect a DE's suspend/resume routine? Ubuntu users have reported a similar bug [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437807 here], and it appears that the issue doesn't affect Unity DE. Can anyone using Unity under Arch confirm that?<br />
<br />
: SNA is simply less tested (and therefore less reliable) than UXA. Consider filing an upstream bug report, but first, see if any of these match your issue: https://bugs.freedesktop.org/buglist.cgi?quicksearch=sna%20suspend [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 21:17, 27 October 2015 (UTC)<br />
<br />
== Unsetting CONFIG_ACPI_REV_OVERRIDE_POSSIBLE ==<br />
<br />
https://bugs.archlinux.org/task/47710<br />
Since version 4.4 Linux has working I2S audio for the XPS 13 2015, so we can finally unset this ugly workaround with kernel versions >= 4.4. Fedora Rawhide already disabled it.</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=415352Talk:Dell XPS 13 (9343)2016-01-14T13:30:25Z<p>DonJaime: /* Powersaving */</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 />
Enabling Tearfree in the xorg config seems to help somewhat.<br />
[[User:Mnhagan01|Mnhagan01]] ([[User talk:Mnhagan01|talk]]) 14:34, 5 November 2015 (UTC)<br />
<br />
FLickering and freezes seem to be thing of the past with kernel 4.3.3. I've edited the page to reflect this.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:30, 14 January 2016 (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 />
:[http://paste.debian.net/319130/ There is a test patch for palm detection] [[User:Dx2|Dx2]] ([[User talk:Dx2|talk]]) 11:05, 3 November 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 />
== 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?<br />
<br />
:I'm planning on buying one of these, I'll update the page with any problems I run into. There's some discussion on the Dell forums about linux support [http://en.community.dell.com/techcenter/os-applications/f/4613/t/19659067 here], seems like everything was working for them except WiFi. [[User:Xymostech|Xymostech]] ([[User talk:Xymostech|talk]]) 01:37, 5 November 2015 (UTC)<br />
<br />
A new section or page should be made for the late 2013 xps 13 (9350). Most of this information for the earlier version do not apply. Wifi for dell xps 13 skylake is using a dw1802a chip which is a broadcom 4350. 4350 is in mainline kernel support from 4.4 onwards. There is a patch that can be applied to kernel and user must extract the 4350 driver from 4.4 branch. Besides that, the skylake intel video can enter X only if i915.preliminary_hw_support=1 in kernel boot command. There is something very wrong with the video though. There are two things that aren't working OOB besides wifi. Brightness keys f11, f12 are not registered as keys by xbindkeys -k and they do not work. Video played crashes X along with random but frequent screen flickering. [[User:Frank604|Frank604]] ([[User talk:Frank604|talk]]) 17:56, 13 November 2015 (UTC)<br />
<br />
== UXA vs. SNA and Suspend Issue ==<br />
<br />
The wiki suggests switching the Intel Graphics Acceleration from UXA to SNA "... [i]f you encounter some artifacts and/or an unusable graphical environment after resuming from a suspend [...]." I myself encountered an issue using XFCE + LightDM where, after resuming from suspend and successfully unlocking the screen, the screen would fade to black and become unresponsive. Switching to UXA removed the issue and made suspend/resume reliable.<br />
<br />
Clearly this is a workaround; UXA performance is pretty bad (with compositing, XFCE's alt-tab takes about 2 seconds to respond on my setup). Does anyone have more information about how SNA could affect a DE's suspend/resume routine? Ubuntu users have reported a similar bug [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1437807 here], and it appears that the issue doesn't affect Unity DE. Can anyone using Unity under Arch confirm that?<br />
<br />
: SNA is simply less tested (and therefore less reliable) than UXA. Consider filing an upstream bug report, but first, see if any of these match your issue: https://bugs.freedesktop.org/buglist.cgi?quicksearch=sna%20suspend [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 21:17, 27 October 2015 (UTC)<br />
<br />
== Unsetting CONFIG_ACPI_REV_OVERRIDE_POSSIBLE ==<br />
<br />
https://bugs.archlinux.org/task/47710<br />
Since version 4.4 Linux has working I2S audio for the XPS 13 2015, so we can finally unset this ugly workaround with kernel versions >= 4.4. Fedora Rawhide already disabled it.</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=415351Dell XPS 13 (9343)2016-01-14T13:23:14Z<p>DonJaime: /* Powersaving */ note improvements in kernel support for power saving parameters</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)]].}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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/04/Drivers/DriversDetails?driverId=28M21 BIOS update A07] was released on 2015-11-26. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card, see {{AUR|linux-firmware-git-iwlwifi}}.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
==== ALSA configuration ====<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]]. In the current case, both cards use the {{ic|snd_hda_intel}} module. 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 />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
At least since kernel 4.3.3 the flickering and/or freezes caused by {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} seem to have been fixed.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W. As from kernel version 4.3.3 it no longer causes flickering.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<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.<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 />
The wireless switch key (to the right of the "Brightness up" key) switches the wireless card on/off at the hardware level, but the Broadcom driver does 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 A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
=== Repeating keys issue === <br />
BIOS A07 should fix this.<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). Obviously you will have to run:<br />
<br />
# mkinitcpio -p linux<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>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=397104Dell XPS 13 (9343)2015-09-01T19:28:20Z<p>DonJaime: Fix in-page link</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| Wireless switch || {{Y|Works, but is [[#rfkill_issues_with_Broadcom_wireless|problematic]] with Broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== rfkill issues with Broadcom wireless ===<br />
<br />
The wireless switch key (to the right of the "Brightness up" key) switches the wireless card on/off at the hardware level, but the Broadcom driver does 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 />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397073Talk:Dell XPS 13 (9343)2015-09-01T14:04:39Z<p>DonJaime: /* Frequent temporary System freezes with linux-4.1 */ Delete closed discussion</p>
<hr />
<div>== 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 />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397072Talk:Dell XPS 13 (9343)2015-09-01T14:04:12Z<p>DonJaime: /* BIOS */ Deleted closed discussion</p>
<hr />
<div>== 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 />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397071Talk:Dell XPS 13 (9343)2015-09-01T14:03:52Z<p>DonJaime: /* Touchpad */ Deleted closed discussion</p>
<hr />
<div>== 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 />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397070Talk:Dell XPS 13 (9343)2015-09-01T14:03:30Z<p>DonJaime: /* PulseAudio flat-volumes section */ Deleted closed discussion</p>
<hr />
<div>== 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397069Talk:Dell XPS 13 (9343)2015-09-01T14:03:00Z<p>DonJaime: /* linux-mainline 4.1 */ Deleted closed discussion</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=397066Dell XPS 13 (9343)2015-09-01T13:54:45Z<p>DonJaime: Put rfkill switch in support table</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<br />
|-<br />
| rfkill switch || {{Y|Works, but [[#WiFi_and_the_rfkill_Switch|glitch]] with broadcom WiFi}} || rfkill<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<br />
<br />
==== WiFi and the rfkill Switch ====<br />
<br />
At least with the broadcom card, the rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable "Wireless Switch" control in the firmware setup.<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=397064Dell XPS 13 (9343)2015-09-01T13:45:09Z<p>DonJaime: /* WiFi */ Describe rfkill switch flakiness and workaround</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} 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 adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<br />
<br />
==== WiFi and the rfkill Switch ====<br />
<br />
At least with the broadcom card, the rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable "Wireless Switch" control in the firmware setup.<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=397061Talk:Dell XPS 13 (9343)2015-09-01T13:40:34Z<p>DonJaime: /* Rfkill switch */</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== <s>linux-mainline 4.1</s> ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 2015 (UTC)<br />
<br />
: Mainline kernel is no longer recommended on the page, and libinput is. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:13, 27 August 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== <s>Rfkill switch</s> ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)<br />
<br />
: No response. Closing here and putting it on the page. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:40, 1 September 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394117Talk:Dell XPS 13 (9343)2015-08-27T15:14:04Z<p>DonJaime: /* linux-mainline 4.1 */ Suggest closing</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== <s>linux-mainline 4.1</s> ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 2015 (UTC)<br />
<br />
: Mainline kernel is no longer recommended on the page, and libinput is. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:13, 27 August 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== Rfkill switch ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394114Talk:Dell XPS 13 (9343)2015-08-27T15:10:28Z<p>DonJaime: /* Frequent temporary System freezes with linux-4.1 */</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== <s>Frequent temporary System freezes with linux-4.1</s> ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
::: i915.enable_fbc=1 is mentioned on the page as causing freezes. Suggest closing this discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 15:10, 27 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== Rfkill switch ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=394107Dell XPS 13 (9343)2015-08-27T14:39:21Z<p>DonJaime: /* WiFi */ Workaround for wireless breakage on kernel upgrade</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} to be installed. See the [[Broadcom wireless]] page for more details.<br />
<br />
{{Tip|'''Surviving Kernel Upgrades:''' If you use {{AUR|broadcom-wl}}, kernel upgrades may break wireless from time to time. Using {{AUR|broadcom-wl-dkms}} helps avoid this.}}<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
Additionally, [[powertop]] may also be employed to tweak the performance and monitor power consumption.<br />
<br />
{{Note|<br />
* Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.<br />
* {{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").<br />
}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Multiboot_USB_drive&diff=394104Multiboot USB drive2015-08-27T14:19:34Z<p>DonJaime: /* Tails */ remove option when iso not on removable media</p>
<hr />
<div>[[Category:Boot process]]<br />
[[de:Multiboot USB Stick]]<br />
{{Related articles start}}<br />
{{Related|GRUB}}<br />
{{Related|Syslinux}}<br />
{{Related|Archiso}}<br />
{{Related articles end}}<br />
{{Move|Multiboot disk images|See discussion|section=Scope and title}}<br />
A multiboot USB flash drive allows booting multiple ISO files from a single device. The ISO files can be copied to the drive and booted directly without unpacking them first. There are multiple methods available, but they may not work for all ISO images.<br />
<br />
== Using GRUB and loopback devices ==<br />
<br />
{{Poor writing|multiple [[Help:Style|style]] issues}}<br />
<br />
advantages:<br />
* only a single partition required<br />
* all ISO files are found in one directory<br />
* adding and removing ISO files is simple<br />
<br />
disadvantages:<br />
* not all ISO images are compatible<br />
* the original boot menu for the ISO file is not shown<br />
* it can be difficult to find a working boot entry<br />
<br />
=== Preparation ===<br />
<br />
{{Expansion|How much extra space is needed for the bootloader?}}<br />
<br />
Create at least one partition and a filesystem supported by [[GRUB]] on the USB drive. See [[Partitioning]] and [[File systems#Create a filesystem]]. Choose the size based on the total size of the ISO files that you want to store on the drive, and plan for extra space for the bootloader.<br />
<br />
=== Installing GRUB ===<br />
<br />
Mount the filesystem located on the USB drive:<br />
<br />
# mount /dev/sdXY /mnt<br />
<br />
Create the directory /boot:<br />
<br />
# mkdir /mnt/boot<br />
<br />
Install grub on the USB drive:<br />
<br />
# grub-install --target=i386-pc --recheck --boot-directory=/mnt/boot /dev/sdX<br />
<br />
In case you want to boot ISOs in UEFI mode, you have to install grub for the UEFI target:<br />
<br />
# grub-install --target x86_64-efi --efi-directory /mnt --boot-directory=/mnt/boot --removable<br />
<br />
For UEFI, the partition has to be the first one in an MBR partition table and formatted with FAT32.<br />
<br />
=== Configuring GRUB ===<br />
<br />
For the purpose of multiboot USB drive it is easier to edit {{ic|grub.cfg}} by hand instead of generating it. Alternatively, make the following changes in {{ic|/etc/grub.d/40_custom}} or {{ic|/mnt/boot/grub/custom.cfg}} and generate {{ic|/mnt/boot/grub/grub.cfg}} using [[GRUB#Generating main configuration file|grub-mkconfig]].<br />
<br />
As it is recommend to use a [[Persistent block device naming|persistent name]] instead of {{ic|/dev/sd''xY''}} to identify the partition on the USB drive where the image files are located, define a variable for convenience to hold the value. If the ISO images are on the same partition as grub, use the following to read the UUID at boot time:<br />
<br />
{{hc|/mnt/boot/grub/grub.cfg|2=<br />
# path to the partition holding ISO images (using UUID)<br />
probe -u $root --set=rootuuid<br />
set imgdevpath="/dev/disk/by-uuid/$rootuuid"<br />
}}<br />
<br />
Or specify the UUID explicitly:<br />
<br />
{{hc|/mnt/boot/grub/grub.cfg|2=<br />
# path to the partition holding ISO images (using UUID)<br />
set imgdevpath="/dev/disk/by-uuid/''UUID_value''"<br />
}}<br />
<br />
Alternatively, use the device label instead of UUID:<br />
<br />
{{hc|/mnt/boot/grub/grub.cfg|2=<br />
# path to the partition holding ISO images (using labels)<br />
set imgdevpath="/dev/disk/by-label/''label_value''"<br />
}}<br />
<br />
The necessary UUID or label can be found using {{ic|lsblk -f}}. Do not use the same label as the Arch ISO for the USB device, otherwise the boot process will fail.<br />
<br />
To complete the configuration, a boot entry for each ISO image has to be added below this header, see the next section for examples.<br />
<br />
=== Boot entries ===<br />
<br />
{{Poor writing|The only boxes used should be code blocks, otherwise the section will be unreadable. Anything else should be plain text.}}<br />
<br />
It is assumed that the ISO images are stored in the {{ic|boot/iso/}} directory on the same filesystem where GRUB is installed. Otherwise it would be necessary to prefix the path to ISO file with device identification when using the {{ic|loopback}} command, for example {{ic|loopback loop '''(hd1,2)'''$isofile}}. As this identification of devices is not [[Persistent block device naming|persistent]], it is not used in the examples in this section.<br />
<br />
One can use persistent block device naming like this:<br />
{{bc|1=<br />
# define globally (i.e outside any menuentry)<br />
insmod search_fs_uuid<br />
search --no-floppy --set='''isopart''' --fs-uuid d6de9100-1981-11e5-9fb9-74867a652f05 # your iso fs uuid here<br />
# later use inside each menuentry instead<br />
loopback loop '''($isopart)'''$isofile<br />
}}<br />
<br />
{{Tip| For a list of kernel parameters, see https://www.kernel.org/doc/Documentation/kernel-parameters.txt (still incomplete)}}<br />
<br />
==== Alt Linux ====<br />
<br />
* Initramfs framework: ???<br />
* Live framework: ???<br />
* Init system: ???<br />
<br />
{{bc|1=<br />
menuentry "[loopback]altlinux-7.0.5-simply-x86_64-install-dvd5.iso" {<br />
set gfxpayload=keep<br />
insmod gzio<br />
insmod part_msdos<br />
insmod ext2<br />
insmod xfs<br />
set bootpart=uuid:df46d821-e7f9-4e35-bbd2-728bdce8d89a<br />
set isodir=/boot/iso<br />
set isofile=altlinux-7.0.5-simply-x86_64-install-dvd5.iso<br />
loopback loop (${root})${isodir}/${isofile}<br />
linux (loop)/syslinux/alt0/vmlinuz automatic=method:disk,${bootpart},directory:${isodir}/${isofile} ramdisk_size=183210 changedisk lang=ru_RU splash noeject xdriver=auto quiet=1 showopts<br />
initrd (loop)/syslinux/alt0/full.cz<br />
}<br />
}}<br />
<br />
==== Arch Linux ====<br />
<br />
{{Tip|If you want to boot into a 32-bit system, replace {{ic|x86_64}} with {{ic|i686}}.}}<br />
<br />
===== monthly release =====<br />
<br />
* Initramfs framework: [[mkinitcpio]] (cmdline: [https://projects.archlinux.org/mkinitcpio.git/tree/man/mkinitcpio.8.txt#n212])<br />
* Live framework: [[archiso]] (cmdline: [https://projects.archlinux.org/archiso.git/tree/docs/README.bootparams])<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry '[loopback]archlinux-2014.12.01-dual.iso' {<br />
set isofile='/boot/iso/archlinux-2014.12.01-dual.iso'<br />
loopback loop $isofile<br />
linux (loop)/arch/boot/'''x86_64'''/vmlinuz archisodevice=/dev/loop0 img_dev=$imgdevpath img_loop=$isofile<br />
initrd (loop)/arch/boot/'''x86_64'''/archiso.img<br />
}<br />
}}<br />
<br />
===== archboot =====<br />
<br />
* Initramfs framework: [[mkinitcpio]] (cmdline: [https://projects.archlinux.org/mkinitcpio.git/tree/man/mkinitcpio.8.txt#n212])<br />
* Live framework: [[archboot]] (cmdline: none? ''RFD'')<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry '[loopback]archlinux-2014.11-1-archboot' {<br />
set isofile='/boot/iso/archlinux-2014.11-1-archboot.iso'<br />
loopback loop $isofile<br />
linux (loop)/boot/vmlinuz_'''x86_64''' iso_loop_dev=$imgdevpath iso_loop_path=$isofile<br />
initrd (loop)/boot/initramfs_'''x86_64'''.img<br />
}<br />
}}<br />
<br />
==== CentOS ====<br />
<br />
===== Stock installation medium =====<br />
<br />
* Initramfs framework: [https://fedoraproject.org/wiki/Dracut Dracut] (cmdline: [https://git.kernel.org/cgit/boot/dracut/dracut.git/tree/dracut.cmdline.7.asc])<br />
* Installation program: [https://fedoraproject.org/wiki/Anaconda Anaconda] (cmdline: [https://github.com/rhinstaller/anaconda/blob/master/docs/boot-options.rst])<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry "[loopback]CentOS-7.0-1406-x86_64-'''DVD'''" {<br />
set isofile='/boot/iso/CentOS-7.0-1406-x86_64-'''DVD'''.iso'<br />
loopback loop $isofile<br />
linux (loop)/isolinux/vmlinuz noeject inst.stage2=hd:'''/dev/sdb2''':/$isofile<br />
initrd (loop)/isolinux/initrd.img<br />
}<br />
}}<br />
<br />
{{tip|The boot parameter of second stage install image location {{ic|1=/dev/sdb2}} which is used by Anaconda, is similar to [[fstab]]'s first field (fs_spec), could be replaced with one of:<br />
* {{ic|1=/dev/sd'''''xY'''''}}<br />
* {{ic|1=LABEL=MYUSBSTICK}}<br />
* {{ic|1=UUID=00000000-0000-0000-0000-0000deadbeef}}<br />
<br />
For example, {{ic|1=linux (loop)/isolinux/vmlinuz noeject inst.stage2=hd:'''LABEL=MYUSBSTICK''':/$isofile}}<br />
}}<br />
<br />
===== Desktop live medium =====<br />
<br />
* Initramfs framework: [https://fedoraproject.org/wiki/Dracut Dracut] (cmdline: [https://git.kernel.org/cgit/boot/dracut/dracut.git/tree/dracut.cmdline.7.asc])<br />
* Live framework: fedora [https://fedoraproject.org/wiki/FedoraLiveCD livecd-tools] (cmdline: none)<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry '[loopback]CentOS-7.0-1406-x86_64-GnomeLive' {<br />
set isofile='/boot/iso/CentOS-7.0-1406-x86_64-GnomeLive.iso'<br />
loopback loop $isofile<br />
linux (loop)/isolinux/vmlinuz0 root=live:CDLABEL=CentOS-7-live-GNOME-x86_64 iso-scan/filename=$isofile rd.live.image<br />
initrd (loop)/isolinux/initrd0.img<br />
}<br />
}}<br />
<br />
==== Clonezilla Live ====<br />
{{tip|1=Since 2014.01.05[https://projects.archlinux.org/archiso.git/commit/?id=5cd02c704046cdb6974f6b10f0cac366eeebec0e], the Arch Linux monthly release contains clonezilla.}}<br />
<br />
* Initramfs framework: [https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/ initramfs-tools] (cmdline: ''RFD'')<br />
* Live framework: [http://live.debian.net/ Debian Live] (cmdline: [http://manpages.debian.org/cgi-bin/man.cgi?query=live-boot&apropos=0&sektion=7&manpath=Debian+unstable+sid&format=html&locale=en])<br />
* Init system: [https://savannah.nongnu.org/projects/sysvinit sysvinit] (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry "[loopback]clonezilla-live-2.2.3-25-amd64" {<br />
set isofile="/boot/iso/clonezilla-live-2.2.3-25-amd64.iso"<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz findiso=$isofile boot=live union=aufs config noprompt ip=frommedia toram=filesystem.squashfs<br />
initrd (loop)/live/initrd.img<br />
}<br />
}}<br />
<br />
==== Debian ====<br />
<br />
===== Stock install medium =====<br />
<br />
* Initramfs framework: [https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/ initramfs-tools] (cmdline: ''RFD'')<br />
* Installation program: [https://wiki.debian.org/DebianInstaller#Development debian-installer] (cmdline: ''exists but missing online documentation'')<br />
* Init system: [https://savannah.nongnu.org/projects/sysvinit sysvinit] (cmdline: ''RFD'')<br />
<br />
{{tip|To install debian from any stock install medium on a non-optical medium (e.g. usb stick, HDD), it's necessary to use a different initramfs instead of the default one on the installation medium which is located at {{ic|(loop)/install.amd/initrd.gz}}. If you boot with the default one, the installer will unable to find or mount the proper iso image for installation.<br />
<br />
Please download the initramfs for hard disk installation from [https://mirrors.kernel.org/debian/dists/stable/main/installer-amd64/current/images/hd-media/initrd.gz an official mirror site], put it in the same directory with the image file and give it a suitable name ({{ic|debian-7.8.0-amd64-DVD-1.hdd.initrd.gz}} in this example).}}<br />
<br />
{{bc|1=<br />
menuentry '[loopback]debian-7.8.0-amd64-DVD-1' {<br />
set isofile='/boot/iso/debian-7.8.0-amd64-DVD-1.iso'<br />
set initrdfile='/boot/iso/debian-7.8.0-amd64-DVD-1.hdd.initrd.gz'<br />
loopback loop $isofile<br />
linux (loop)/install.amd/vmlinuz vga=791 iso-scan/ask_second_pass=true iso-scan/filename=$isofile<br />
initrd $initrdfile<br />
}<br />
}}<br />
<br />
===== Live install medium =====<br />
<br />
* Initramfs framework: [https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/ initramfs-tools] (cmdline: ''RFD'')<br />
* Live framework: [http://live.debian.net/ Debian Live] (cmdline: [http://manpages.debian.org/cgi-bin/man.cgi?query=live-boot&apropos=0&sektion=7&manpath=Debian+unstable+sid&format=html&locale=en])<br />
* Init system: [https://savannah.nongnu.org/projects/sysvinit sysvinit] (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry '[loopback]debian-live-7.8.0-amd64-xfce-desktop' {<br />
set isofile='/boot/iso/debian-live-7.8.0-amd64-xfce-desktop.iso'<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz boot=live config fromiso='''/dev/sdb2'''/$isofile<br />
initrd (loop)/live/initrd.img<br />
}<br />
}}<br />
<br />
{{note|It's also OK to use {{ic|1=findiso=$isofile}} instead of the longer {{ic|1=fromiso=/dev/disk/by-.../.../$isofile}}. Anyway, using {{ic|1=fromiso=}} instead of {{ic|1=findiso=}} may speed up the initialization progress because it avoids unnecessary mounting.}}<br />
<br />
==== Elementary OS ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: upstart (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry '[loopback]elementaryos-freya-amd64.20150411' {<br />
set isofile='/boot/iso/elementaryos-freya-amd64.20150411.iso'<br />
loopback loop $isofile<br />
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile locale='''en_US.UTF-8'''<br />
initrd (loop)/casper/initrd.lz<br />
}<br />
}}<br />
<br />
==== Fedora ====<br />
<br />
===== Stock installation medium =====<br />
<br />
* Initramfs framework: [https://fedoraproject.org/wiki/Dracut Dracut] (cmdline: [https://git.kernel.org/cgit/boot/dracut/dracut.git/tree/dracut.cmdline.7.asc])<br />
* Installation program: [https://fedoraproject.org/wiki/Anaconda Anaconda] (cmdline: [https://github.com/rhinstaller/anaconda/blob/master/docs/boot-options.rst])<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry '[loopback]Fedora-20-x86_64-DVD' {<br />
set isofile='/boot/iso/Fedora-20-x86_64-DVD.iso'<br />
loopback loop $isofile<br />
linux (loop)/isolinux/vmlinuz noeject inst.stage2=hd:'''/dev/sdb2''':/$isofile<br />
initrd (loop)/isolinux/initrd.img<br />
}<br />
}}<br />
<br />
===== Workstation live medium =====<br />
<br />
* Initramfs framework: [https://fedoraproject.org/wiki/Dracut Dracut] (cmdline: [https://git.kernel.org/cgit/boot/dracut/dracut.git/tree/dracut.cmdline.7.asc])<br />
* Live framework: fedora [https://fedoraproject.org/wiki/FedoraLiveCD livecd-tools] (cmdline: none)<br />
* Init system: [[systemd]] (cmdline: [http://www.freedesktop.org/software/systemd/man/kernel-command-line.html])<br />
<br />
{{bc|1=<br />
menuentry '[loopback]Fedora-Live-Workstation-x86_64-21-5' {<br />
set isofile='/boot/iso/Fedora-Live-Desktop-x86_64-21-5.iso'<br />
loopback loop $isofile<br />
linux (loop)/isolinux/vmlinuz0 root=live:CDLABEL=Fedora-Live-WS-x86_64-21-5 iso-scan/filename=$isofile rd.live.image<br />
initrd (loop)/isolinux/initrd0.img<br />
}<br />
}}<br />
<br />
==== Gentoo ====<br />
===== Desktop LiveDVD =====<br />
<br />
* Initramfs framework: [https://wiki.gentoo.org/wiki/Genkernel genkernel] (cmdline: [https://gitweb.gentoo.org/proj/genkernel.git/tree/doc/genkernel.8.txt#n393])<br />
* Live framework: [https://gitweb.gentoo.org/proj/livecd-tools.git/ livecd-tools] (cmdline: ''RFD'')<br />
* Init system: [https://wiki.gentoo.org/wiki/Project:OpenRC OpenRC] (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry "[loopback]livedvd-amd64-multilib-20140826" {<br />
set isofile="/boot/iso/livedvd-amd64-multilib-20140826.iso"<br />
loopback loop $isofile<br />
linux (loop)/isolinux/gentoo root=/dev/ram0 init=/linuxrc aufs looptype=squashfs loop=/image.squashfs cdroot isoboot=$isofile vga='''791''' splash=silent,theme:default console=tty0<br />
initrd (loop)/isolinux/gentoo.igz <br />
}<br />
}}<br />
<br />
{{Tip|This should also works for minimal medium.}}<br />
<br />
==== GParted Live ====<br />
<br />
* Initramfs framework: [https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/ initramfs-tools] (cmdline: ''RFD'')<br />
* Live framework: [http://live.debian.net/ Debian Live] (cmdline: [http://manpages.debian.org/cgi-bin/man.cgi?query=live-boot&apropos=0&sektion=7&manpath=Debian+unstable+sid&format=html&locale=en])<br />
* Init system: [https://savannah.nongnu.org/projects/sysvinit sysvinit] (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry "[loopback]gparted-live-0.22.0-2-'''amd64'''" {<br />
set isofile="/boot/iso/gparted-live-0.22.0-2-'''amd64'''.iso"<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz boot=live union=overlay username=user config components quiet noswap noeject toram=filesystem.squashfs ip= nosplash findiso=$isofile<br />
initrd (loop)/live/initrd.img<br />
}<br />
}}<br />
<br />
==== Kali Linux ====<br />
<br />
* Initramfs framework: [https://anonscm.debian.org/cgit/kernel/initramfs-tools.git/ initramfs-tools] (cmdline: ''RFD'')<br />
* Live framework: [http://live.debian.net/ Debian Live] (cmdline: [http://manpages.debian.org/cgi-bin/man.cgi?query=live-boot&apropos=0&sektion=7&manpath=Debian+unstable+sid&format=html&locale=en])<br />
* Init system: [https://savannah.nongnu.org/projects/sysvinit sysvinit] (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry "[loopback]kali-linux-1.0.7-'''amd64'''" {<br />
set isofile='/boot/iso/kali-linux-1.0.7-'''amd64'''.iso'<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz boot=live findiso=$isofile noconfig=sudo username=root hostname=kali<br />
initrd (loop)/live/initrd.img<br />
}<br />
}}<br />
<br />
==== Linux Mint ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: ''RFD''<br />
<br />
{{bc|1=<br />
menuentry "[loopback]linuxmint-201403-cinnamon-dvd-'''32'''bit" {<br />
set isofile="/boot/iso/linuxmint-201403-cinnamon-dvd-'''32'''bit.iso"<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz isofrom='''/dev/sdb2'''/iso/$isofile boot=live live-config live-media-path=/live quiet splash noeject noprompt<br />
initrd (loop)/live/initrd.img<br />
}<br />
}}<br />
<br />
==== openSUSE ====<br />
<br />
===== Stock installation medium =====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: Kiwi? ''RFD''<br />
* Init system: ''RFD''<br />
<br />
{{bc|1=<br />
menuentry '[loopback]openSUSE-13.1-DVD-x86_64' {<br />
set isofile='/boot/iso/openSUSE-13.1-DVD-x86_64.iso'<br />
loopback loop $isofile<br />
linux (loop)/boot/x86_64/loader/linux install=hd:$isofile<br />
initrd (loop)/boot/x86_64/loader/initrd<br />
}<br />
}}<br />
<br />
===== Desktop Live medium =====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: Kiwi? ''RFD''<br />
* Init system: ''RFD''<br />
<br />
{{bc|1=<br />
menuentry '[loopback]openSUSE-13.1-KDE-Live-x86_64' {<br />
set isofile='/boot/iso/openSUSE-13.1-KDE-Live-x86_64.iso'<br />
loopback loop $isofile<br />
linux (loop)/boot/x86_64/loader/linux isofrom_device=$imgdevpath isofrom_system=$isofile LANG='''en_US.UTF-8'''<br />
initrd (loop)/boot/x86_64/loader/initrd<br />
}<br />
}}<br />
<br />
==== Parabola GNU/Linux-libre ====<br />
<br />
{{Tip|If you want to boot into a 32-bit system, replace {{ic|x86_64}} with {{ic|i686}}.}}<br />
<br />
{{bc|1=<br />
menuentry '[loopback]parabola-2015.07.01-dual.iso' {<br />
set isofile='/boot/iso/parabola-2015.07.01-dual.iso'<br />
loopback loop $isofile<br />
linux (loop)/parabola/boot/'''x86_64'''/vmlinuz parabolaisolabel=PARA_'''201507''' img_dev=$imgdevpath img_loop=$isofile earlymodules=loop<br />
initrd (loop)/parabola/boot/'''x86_64'''/parabolaiso.img<br />
}<br />
}}<br />
<br />
{{Tip| The label string after {{ic|1=parabolaisolabel=}} needs to be edited when a newer release is used.}}<br />
<br />
==== Sabayon ====<br />
<br />
* Initramfs framework: genkernel? ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: openrc? ''RFD''<br />
<br />
{{bc|1=<br />
menuentry '[loopback]Sabayon_Linux_14.05_amd64_KDE' {<br />
set isofile='/boot/iso/Sabayon_Linux_14.05_amd64_KDE.iso'<br />
loopback loop $isofile<br />
linux (loop)/boot/sabayon root=/dev/ram0 aufs cdroot locale='''en_US''' loop=/livecd.squashfs looptype=squashfs isoboot=$isofile<br />
initrd (loop)/boot/sabayon.igz<br />
}<br />
}}<br />
<br />
==== Slackware Linux ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: ''RFD''<br />
<br />
{{bc|1=<br />
menuentry '[loopback]slackware64-14.1-install-dvd' {<br />
set isofile='/boot/iso/slackware64-14.1-install-dvd.iso'<br />
loopback loop $isofile<br />
linux (loop)/kernels/huge.s/bzImage printk.time=0<br />
initrd (loop)/isolinux/initrd.img<br />
}<br />
}}<br />
<br />
==== SystemRescueCD ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: ''RFD''<br />
<br />
{{note|Replace {{ic|64}} with {{ic|32}} if you want to boot into a 32-bit system.}}<br />
{{bc|1=<br />
menuentry '[loopback]systemrescuecd-x86-4.5.2' {<br />
set isofile='/boot/iso/systemrescuecd-x86-4.5.2.iso'<br />
loopback loop $isofile<br />
linux (loop)/isolinux/rescue'''64''' isoloop=$isofile<br />
initrd (loop)/isolinux/initram.igz<br />
}<br />
}}<br />
<br />
==== Ubuntu ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework or installation program: ''RFD''<br />
* Init system: upstart (cmdline: ''RFD'')<br />
<br />
{{bc|1=<br />
menuentry '[loopback]ubuntu-14.04.1-desktop-amd64' {<br />
set isofile='/boot/iso/ubuntu-14.04.1-desktop-amd64.iso'<br />
loopback loop $isofile<br />
linux (loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=$isofile locale='''en_US.UTF-8'''<br />
initrd (loop)/casper/initrd.lz<br />
}<br />
}}<br />
<br />
==== Slitaz ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework: ''RFD''<br />
* Init system: ''RFD''<br />
<br />
First, download slitaz iso, then extract somewhere (in this case, /live/slitaz-4.0 on /dev/sda3)<br />
<br />
{{bc|1=<br />
menuentry 'slitaz-4.0 core' {<br />
set dir='/live/slitaz-4.0'<br />
set root=(hd0,msdos3)<br />
set lang='pt_BR'<br />
set kmap='br-abnt2'<br />
linux ($root)/$dir/bzImage lang=$lang kmap=$kmap rw root=/dev/null vga=normal autologin<br />
initrd ($root)/$dir/rootfs4.gz ($root)/$dir/rootfs3.gz ($root)/$dir/rootfs2.gz ($root)/$dir/rootfs1.gz<br />
}<br />
}}<br />
<br />
==== Slax ====<br />
<br />
* Initramfs framework: ''RFD''<br />
* Live framework: ''RFD''<br />
* Init system: ''RFD''<br />
<br />
First, download Slax zip (for USB), then extract somewhere (in this case, /live/slax on /dev/sda3)<br />
<br />
{{bc|1=<br />
menuentry 'slax' {<br />
set dir=/live/slax<br />
set root=(hd0,msdos3)<br />
linux $dir/boot/vmlinuz from=$dir vga=normal load_ramdisk=1 prompt_ramdisk=0 printk.time=0 slax.flags=perch,xmode<br />
initrd $dir/boot/initrfs.img<br />
}<br />
}}<br />
<br />
==== Tails ====<br />
<br />
* Initramfs framework: ''Unknown''<br />
* Live framework: ''Unknown''<br />
* Init system: ''Unknown''<br />
<br />
Simply download and verify integrity of the Tails iso.<br />
<br />
{{bc|1=<br />
menuentry "[loopback]tails-i386-1.5.iso" {<br />
set isofile='/boot/iso/tails-i386-1.5.iso'<br />
loopback loop $isofile<br />
linux (loop)/live/vmlinuz2 boot=live config findiso=${isofile} live-media=removable apparmor=1 security=apparmor nopersistent noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 noautologin module=Tails<br />
initrd (loop)/live/initrd2.img<br />
}<br />
}}<br />
<br />
{{Warning|Emergency memory erasure does not seem to work when booting this way.}}<br />
<br />
Remove the {{ic|1=live-media=removable}} option if the iso file is not on removable media.<br />
<br />
== Using Syslinux and memdisk ==<br />
<br />
Using the [http://www.syslinux.org/wiki/index.php/MEMDISK memdisk] module, the ISO image is loaded into memory, and its bootloader is loaded. Make sure that the system that will boot this USB drive has sufficient amount of memory for the image file and running operating system.<br />
<br />
=== Preparation ===<br />
<br />
Make sure that the USB drive is properly [[Partitioning|partitioned]] and that there is a partition with [[file system]] supported by Syslinux, for example fat32 or ext4. Then install Syslinux to this partition, see [[Syslinux#Installation]].<br />
<br />
=== Install the memdisk module ===<br />
<br />
The memdisk module was not installed during Syslinux installation, it has to be installed manually. Mount the partition where Syslinux is installed to {{ic|/mnt/}} and copy the memdisk module to the same directory where Syslinux is installed:<br />
<br />
# cp /usr/lib/syslinux/bios/memdisk /mnt/boot/syslinux/<br />
<br />
=== Configuration ===<br />
<br />
After copying the ISO files on the USB drive, edit the [[Syslinux#Configuration|Syslinux configuration file]] and create menu entries for the ISO images. The basic entry looks like this:<br />
<br />
{{hc|boot/syslinux/syslinux.cfg|<br />
LABEL ''some_label''<br />
LINUX memdisk<br />
INITRD ''/path/to/image.iso''<br />
APPEND iso<br />
}}<br />
<br />
See [http://www.syslinux.org/wiki/index.php/MEMDISK memdisk on Syslinux wiki] for more configuration options.<br />
<br />
=== Caveat for 32-bit systems ===<br />
<br />
When booting a 32-bit system from an image larger than 128MiB, it is necessary to increase the maximum memory usage of vmalloc. This is done by adding {{ic|1=vmalloc=''value''M}} to the kernel parameters, where {{ic|''value''}} is larger than the size of the ISO image in MiB.[http://www.syslinux.org/wiki/index.php/MEMDISK#-_memdiskfind_in_combination_with_phram_and_mtdblock]<br />
<br />
For example when booting the 32-bit system from the [https://www.archlinux.org/download/ Arch installation ISO], press the {{ic|Tab}} key over the {{ic|Boot Arch Linux (i686)}} entry and add {{ic|1=vmalloc=768M}} at the end. Skipping this step will result in the following error during boot:<br />
<br />
modprobe: ERROR: could not insert 'phram': Input/output error<br />
<br />
== See also ==<br />
<br />
* GRUB:<br />
** https://help.ubuntu.com/community/Grub2/ISOBoot/Examples<br />
** https://help.ubuntu.com/community/Grub2/ISOBoot<br />
* Syslinux:<br />
** [http://www.syslinux.org/wiki/index.php/Boot_an_Iso_image Boot an ISO image]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394070Talk:Dell XPS 13 (9343)2015-08-27T10:42:51Z<p>DonJaime: /* Rfkill switch */ sign. *sigh*</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== Rfkill switch ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
<br />
2. Does this match other users' experience with broadcom?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:42, 27 August 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394069Talk:Dell XPS 13 (9343)2015-08-27T10:42:10Z<p>DonJaime: /* Rfkill switch */ new section</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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 />
== Rfkill switch ==<br />
<br />
There is a suggestion on the page to disable the rfkill switch if WLAN doesn't work properly. In function of the answers to the following questions, I would add the rfkill switch to the device table at the top and include the following further down:<br />
<br />
"The rfkill switch key (to the right of 'Brightness up') works at the hardware level -- the wireless card is switched off -- but the wifi card driver does not react to it properly: it does not realise the card is off, and only sees a lost connection. Then it fails to recover when the key is used to switch the card back on. You can get it to work again by switching wifi off and on again in the NetworkManager applet or by {{ic|echo}}ing 0 and then 1 into {{ic|/sys/class/rfkill/rfkill0/state}}. Alternatively, you can disable ""Wireless Switch" control in the firmware setup."<br />
<br />
Questions:<br />
<br />
1. Are there problems with the rfkill switch with an intel wifi card?<br />
2. Does this match other users' experience with broadcom?</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394068Talk:Dell XPS 13 (9343)2015-08-27T10:25:15Z<p>DonJaime: Put strikeout tags from my last edits in the right place. Sorry about the noise.</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== <s>Touchpad</s> ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
== <s>BIOS</s> ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:24, 27 August 2015 (UTC)<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394067Talk:Dell XPS 13 (9343)2015-08-27T10:18:03Z<p>DonJaime: /* Touchpad */</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
<s><br />
== Touchpad ==<br />
</s><br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
: We could close this discussion now, I think. [[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 10:17, 27 August 2015 (UTC)<br />
<br />
<s><br />
<br />
== BIOS ==<br />
</s><br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion.<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394066Talk:Dell XPS 13 (9343)2015-08-27T10:14:18Z<p>DonJaime: /* BIOS */</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== Touchpad ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
<s><br />
== BIOS ==<br />
</s><br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: nuff said. Closing discussion.<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394065Talk:Dell XPS 13 (9343)2015-08-27T10:12:01Z<p>DonJaime: Undo revision 394064 by DonJaime (talk)</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== Touchpad ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
== BIOS ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=394064Talk:Dell XPS 13 (9343)2015-08-27T10:10:49Z<p>DonJaime: /* BIOS */ Closed discussion</p>
<hr />
<div>== 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 />
== <s>PulseAudio flat-volumes section</s> ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
::: As Soren121 mentioned, please see the guidelines in [[:Category:Laptops]]. Closing. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 14:45, 12 August 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== Touchpad ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
<s>== BIOS ==</s><br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
: Nothing more to be said. Closing discussion.<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=390942Talk:Dell XPS 13 (9343)2015-08-12T13:43:09Z<p>DonJaime: /* Powersaving */</p>
<hr />
<div>== 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 />
== PulseAudio flat-volumes section ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== Touchpad ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
<br />
== BIOS ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)<br />
<br />
== Frequent temporary System freezes with linux-4.1 ==<br />
<br />
When running Linux-4.1 (mainline) I get frequent full system freezes, most notable whilst typing. This was happening without kernel parameters but even with the recommended ones here, it was still happening. Have reverted to 3.19 and no issues.<br />
<br />
Freezes are accompanied by the following (example)<br />
<br />
traps: polkitd[626] general protection ip:7f2d76f74582 sp:7ffc896c87b0 error:0 in libmozjs-17.0.so[7f2d76e3c000+3a8000]<br />
<br />
System is running Manjaro Cinnamon, but was also happening with the official XFCE release.<br />
:Add nosmap to the kernel cmdline. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 15:10, 4 August 2015 (UTC)<br />
<br />
:I've tried nosmap as boot param and it still froze. On 4.1.3 with kernel parameters ''pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7 i915.enable_ips=0 nosmap''. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 12:42, 5 August 2015 (UTC)<br />
<br />
::i915.enable_fbc=1 is known to cause issues with the rather low DVMT preallocated memory. You could try setting that to 0 and give it another try. Maybe that helps.\<br />
<br />
:After a few days on 4.1.3 with just i915.enable_ips=0 for the display flicker issue, it seems to be stable. I'm using an aftermarket intel wireless card. --[[User:Adlpz|Adlpz]] ([[User talk:Adlpz|talk]]) 10:42, 10 August 2015 (UTC)<br />
<br />
== On adding bug/regression info ==<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)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=390938Dell XPS 13 (9343)2015-08-12T13:39:57Z<p>DonJaime: /* EFISTUB does not boot */ Detail the problem, clarify the status of systemd-boot, and link to it.</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} to be installed. See the [[Broadcom wireless]] page for more details.<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
{{Tip|Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.}}<br />
{{Tip|{{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== Audio channel balance issues (PulseAudio) ===<br />
The official pulseaudio package is missing a [[udev]] rule, which makes the system fallback to a generic audio profile. (Source?)<br />
<br />
This in turn results in a faulty mixing of audio channels, producing an rather odd sounding volume spectrum when using headphones in combination with equally balanced left and right audio channels.<br />
<br />
It sounds as if the left and right channel partially nullify each other.<br />
<br />
The easiest way to fix this issue is to add a ''udev'' rule, setting the right profile yourself.<br />
{{hc|/lib/udev/rules.d/91-pulseaudio-xps13.rules|<nowiki><br />
# Dell XPS 13 (9343) Audio Profile Picker UDEV Rule<br />
SUBSYSTEM!="sound", GOTO="pulseaudio_end"<br />
ACTION!="change", GOTO="pulseaudio_end"<br />
KERNEL!="card*", GOTO="pulseaudio_end"<br />
SUBSYSTEMS=="usb", GOTO="pulseaudio_end"<br />
<br />
# Dell XPS 13 (9343)<br />
ATTRS{subsystem_vendor}=="0x8086", ATTRS{subsystem_device}=="0x9ca0", ENV{PULSE_PROFILE_SET}="force-speaker-and-int-mic.conf"<br />
<br />
LABEL="pulseaudio_end"<br />
</nowiki>}}<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
As of version A05, the BIOS does not pass any boot parameters to the kernel. Use a [[Boot_loaders#UEFI-only boot loaders|UEFI boot loader]] instead.<br />
[[systemd-boot]] works with current kernels.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=390936Dell XPS 13 (9343)2015-08-12T13:23:06Z<p>DonJaime: /* WiFi */ Remove inaccurate warning about Broadcom channel limitations. (I'm currently on channel 11.)</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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=YMRTD BIOS update A05] was released on 2015-07-31. 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 />
=== WiFi ===<br />
Most configurations feature the Dell DW1560 802.11ac adapter (Broadcom BCM4352), which requires {{AUR|broadcom-wl}} or {{AUR|broadcom-wl-dkms}} to be installed. See the [[Broadcom wireless]] page for more details.<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
MatchProduct "DLL0665:01 06CB:76AD UNKNOWN"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
{{Tip|Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.}}<br />
{{Tip|{{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== Audio channel balance issues (PulseAudio) ===<br />
The official pulseaudio package is missing a [[udev]] rule, which makes the system fallback to a generic audio profile. (Source?)<br />
<br />
This in turn results in a faulty mixing of audio channels, producing an rather odd sounding volume spectrum when using headphones in combination with equally balanced left and right audio channels.<br />
<br />
It sounds as if the left and right channel partially nullify each other.<br />
<br />
The easiest way to fix this issue is to add a ''udev'' rule, setting the right profile yourself.<br />
{{hc|/lib/udev/rules.d/91-pulseaudio-xps13.rules|<nowiki><br />
# Dell XPS 13 (9343) Audio Profile Picker UDEV Rule<br />
SUBSYSTEM!="sound", GOTO="pulseaudio_end"<br />
ACTION!="change", GOTO="pulseaudio_end"<br />
KERNEL!="card*", GOTO="pulseaudio_end"<br />
SUBSYSTEMS=="usb", GOTO="pulseaudio_end"<br />
<br />
# Dell XPS 13 (9343)<br />
ATTRS{subsystem_vendor}=="0x8086", ATTRS{subsystem_device}=="0x9ca0", ENV{PULSE_PROFILE_SET}="force-speaker-and-int-mic.conf"<br />
<br />
LABEL="pulseaudio_end"<br />
</nowiki>}}<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
Until this bug is fixed, revert to mesa and mesa-libgl (10.5.7).<br />
<br />
=== EFISTUB does not boot ===<br />
Use [[Boot_loaders#UEFI-only boot loaders]] instead.<br />
Tested with systemd-boot.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Multiboot_USB_drive&diff=390285Talk:Multiboot USB drive2015-08-07T13:33:45Z<p>DonJaime: /* Scope and title */</p>
<hr />
<div>== Redirect to avoid duplication? ==<br />
<br />
Everything seems to be already covered on [[GRUB]] page: [[GRUB#Installation]], [[GRUB#Generating main configuration file]], [[GRUB#Booting ISO9660 image file directly via GRUB]]... (it is obvious that GRUB can be installed on USB drive)<br />
<br />
Maybe we can just redirect to [[GRUB#Booting ISO9660 image file directly via GRUB]] to avoid duplication?<br />
<br />
-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 15:42, 10 September 2014 (UTC)<br />
<br />
:What about compacting the article instead by keeping the general idea and the steps in the procedure while replacing the duplicated parts with links, and then merging the result into [[USB_flash_installation_media#Using_a_multiboot_USB_drive]], which is this article's only backlink? -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:49, 11 September 2014 (UTC)<br />
<br />
::Moving [[GRUB#Booting ISO9660 image file directly via GRUB]] could also be considered, but "Multiboot USB drive" is too generic title for this. It all depends if similar setups (even without booting ISO images) are possible with other boot loaders, e.g. [[syslinux]]. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 11:56, 11 September 2014 (UTC)<br />
<br />
:::Do you mean "moving" it to a separate article or into [[USB_flash_installation_media#Using_a_multiboot_USB_drive]]? In either case, as you point out splitting [[GRUB#Booting ISO9660 image file directly via GRUB]] would require more research about other boot loaders to justify having it in a separate article from [[GRUB]], I'm not sure how long would that take to be implemented...<br />
:::If our immediate goal is only removing the duplicated content, my solution seems more readily feasible.<br />
:::-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 14:06, 12 September 2014 (UTC)<br />
<br />
::::As there was another method to be added (Syslinux + memdisk), I have merged the [[GRUB#Booting ISO9660 image file directly via GRUB]] section here. Aside from the obvious style issues, there is also [[USB_flash_installation_media#Loading_the_installation_media_from_RAM]] (see also the [https://bbs.archlinux.org/viewtopic.php?id=135266 preceding forum thread]), which is surprisingly presented as Windows-only method. If it was a Linux method, I would have already merged it here, but now I'm not so sure. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:49, 13 September 2014 (UTC)<br />
<br />
:::::Well done with the merge. About [[USB_flash_installation_media#Loading_the_installation_media_from_RAM]] I'm not sure either, if you want you can consider flagging it with Template:Merge to attract more opinions here. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 04:23, 14 September 2014 (UTC)<br />
<br />
::::::OK, marked as suggested, closing. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:50, 14 September 2014 (UTC)<br />
<br />
:::::::Re-opening, this discussion is still needed as a reference for [[#Scope and title]], but let's continue discussing there. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:06, 21 September 2014 (UTC)<br />
<br />
:To clarify what this article was meant to be: My intention was to make an article specifically about how to boot multiple ISO files from one usb drive. I agree that the title is too generic as is. Whilst a lot of the content here might seem simple and already found elsewhere, configuring the various boot menuentries is difficult, and not documented on any other page. The boot menuentries are poorly documented on the homepages of clonezilla, ubuntu, and so on. Therefore maintaining a list of these entries on the wiki seems to be a good idea. I have now added 3 entries beyond the one for the archiso. This list does not really fit on any of the existing pages. It is entirely possible to achieve a similar result using syslinux, which could be added later. <br />
: -- [[User:Teateawhy|Teateawhy]] ([[User talk:Teateawhy|talk]]) 15:52, 12 September 2014 (UTC)<br />
<br />
::Ahem... What about [[GRUB#Booting_ISO9660_image_file_directly_via_GRUB]] as we linked from our posts above? :) -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:57, 13 September 2014 (UTC)<br />
<br />
== Scope and title ==<br />
<br />
If I may, I have some comments about this article.<br />
<br />
First, the "introduction" (the first section of the article right after the title):<br />
<br />
<center>''A multiboot USB flash drive allows booting multiple ISO files from a single device''</center><br />
<br />
A multiboot (USB flash) drive can manage the booting options in different ways. I mean, it is not limited just to booting "ISO images as-is". This is ''one'' valid method, with pros and cons.<br />
<br />
Considering the name of the article (and the current relations / links to/from it), I would tend to think that limiting this article to this "full ISO images approach only" would be at least inaccurate. It should at least mention that there are other approaches available, with other pros and cons.<br />
<br />
Alternatively, the name (title) of the wiki article should be modified so to reflect the specific approach being described. The disadvantage of such alternative is that it might leave the impression that this is "the" ("best", "only") way to have a multiboot (USB flash) drive.<br />
<br />
I understand the initial intention of [[User:Teateawhy|Teateawhy]] about the scope of the article. By reading the links to/from this article and the current title, IMHO some adjustments are needed, hence my above comments.<br />
<br />
Now, regarding parts of the current content...<br />
* At this date (2014Sep), MEMDISK works on BIOS only, not UEFI (UEFI not being supported by these bootloaders using this "ISO mapping" approach is mentioned under [[Multiboot_USB_drive#Using_GRUB_and_loopback_devices]] but not under [[Multiboot_USB_drive#Using_Syslinux_and_memdisk]].<br />
* The MEMDISK method is not limited to Syslinux. Bootloaders that are capable of loading a Linux kernel (on BIOS hardware) should be able to load MEMDISK too.<br />
* There are other bootloaders also capable of mapping (ISO) images (e.g. grub4dos).<br />
* Syslinux is mentioned in conjunction with MEMDISK, but someone could claim that using Syslinux by itself on a multiboot USB flash drive might be better than mapping entire ISO images (depending on pros and cons or each method). Additionally, Syslinux (and others) can support UEFI.<br />
<br />
Of course, adding all this info in detail to this (one) article might make the scope of it "too wide" to be actually useful/clear.<br />
<br />
So, it is fine to provide information about making a multiboot USB flash drive by "simply throwing ISO images" on the drive, but I also think that the title of the article and the links to/from it should be "more accurate", specially reflecting that other possibilities exist (instead of mapping whole ISO images) and mentioning pros and cons (more RAM needed, time to load the mapped image, consecutive blocks, used space in the USB drive...). [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 21:40, 14 September 2014 (UTC)<br />
<br />
:Hi, thank you for your observations. This article has clearly large margins for improvement, including changing the title itself and the sections that link to it from other articles. I agree with all of your points, your contribution would be very welcome; if you have a better title to propose, please let us know here. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 03:00, 15 September 2014 (UTC)<br />
<br />
::About suggesting an alternative title... <br />
<br />
::The procedures described here are mostly valid for different storage media. Indeed, a typical use-case is on a USB flash drive, but you could do the same on non-flash drives, and on non-USB drives, whether removable or not.<br />
<br />
::Additionally, the content describes different variations of only one particular approach: mapping images. Although the method is typically used with ISO images, you could do the same with other types (e.g. HDD and superfloppy) of bootable images.<br />
<br />
::It seems that two words, "multiboot" and "image(s)", are essential to the article. I also think that, either together or by themselves, they give enough information so to attract potential interested readers. IMHO, words such as "USB", "flash" and "drive" are not really needed for the title, and they can be (and in fact are) mentioned in the content as typical use-cases of this multiboot method.<br />
<br />
::So, perhaps something about "Multiboot images" (or "Multibooting images") could be appropriate? Optionally add the "ISO" term too; although, these methods are not exclusively used with ISO images.<br />
<br />
::Once the scope and the title are refined, it would be helpful for users to have a hint about the existence of other methods (instead of mapping images), mentioning some of the generic pros and cons. Then (a) future new article(s) about such other multiboot methods could be linked to/from this (renamed) page. [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 14:14, 16 September 2014 (UTC)<br />
<br />
:::Good reasoning. What about "Multibooting disk images" as an improvement? Just "images" sounds too ambiguous to me, and "disk images" seems to be the correct term according to [[Wikipedia:Disk image]]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:46, 17 September 2014 (UTC)<br />
<br />
::::"Multiboot disk images" sounds reasonable. Just for the record, although many users don't care / remember / know, in this context the generic term "dis'''k'''" includes the "disc" optical media (ISO images). Now, "only" the content needs some improvements :). [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 13:12, 17 September 2014 (UTC)<br />
<br />
:::::Um... sorry but coming back here after a few days, I think I'm less convinced by the (current and intended) scope of this article, which is/would become too heterogeneous. I'd consider merging the GRUB section back to [[GRUB]] instead (or maybe even better in a GRUB/Subpage), and then, if you wanted (@Ady), you could rename this article as "MEMDISK" and expand it on how to load and use MEMDISK with some bootloaders; this would probably also make it easier to merge [[USB_flash_installation_media#Loading_the_installation_media_from_RAM]] here, and we could easily add a link to the new GRUB subpage in [[USB_flash_installation_media#Using_a_multiboot_USB_drive]]. I'm also re-opening [[#Redirect to avoid duplication?]] because it's related. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:05, 21 September 2014 (UTC)<br />
<br />
::::::Whichever the case, ATM the suggested title ("Multiboot disk images") seems (to me) more accurate than the current title ("Multiboot USB drive") according to the current content. "Multiboot disk images" also matches what seems to be the scope that [[User:Teateawhy]] intended for this page.<br />
<br />
::::::WRT merging / moving (part of) the content into other pages, I might have a slightly different view on the matter (or perhaps it is not so different?). [[GRUB]] is capable of dealing with many different scenarios. For the content / scope of a wiki article, I would tend to focus on what a user wants / needs / thinks, instead of concentrating on "every single thing that GRUB can do".<br />
<br />
::::::One user might be thinking about a very simple and generic task ("boot my newly installed OS, which I attempt to test with the very-basic features and nothing fancy").<br />
<br />
::::::Another user might want to have LVM, encryption, RAID, with several OSes... And yet another user wants a portable device with several "rescue" tools, or several OSes so to show to friends on their own hardware.<br />
<br />
::::::Writing every single scenario related to bootloaders (or to GRUB) under one single article would make it more complex for users to focus on their respective interests / tasks. IMHO, having different articles focusing on the task (i.e. what each user is thinking about) rather than focusing on a certain name/tool or certain software such as "everything GRUB", is more useful for users.<br />
<br />
::::::You can always have links from [[GRUB]] and from other alternative bootloaders' wiki pages to the "task-oriented" articles. Of course, the in-common information regarding GRUB shall not be repeated, but just mention the relevant info / steps so to achieve the goal/task. So the question becomes, how much "in-common" information (or details / steps) can and should be moved back to [[GRUB]]? Would/should this page be just a list of entries for different OSes, leaving the "HowTos" for each bootloader's wiki pages? Then you can decide how to name this page. [[User:Ady|Ady]] ([[User talk:Ady|talk]]) 16:45, 21 September 2014 (UTC)<br />
<br />
::::'Multiboot' is misleading. This page presents very useful information about how to boot from a disk image file. 'Booting from a disk image file' would be an appropriate findable title, as would 'Booting from disk image files.' I'm not sure which style the arch wiki prefers.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 13:32, 7 August 2015 (UTC)<br />
<br />
== Tails ==<br />
<br />
Can anyone add [https://tails.boum.org/ Tails]? [http://www.preining.info/blog/2015/05/usb-stick-update-tails-debian-gparted-sysrescd/ This] might be useful. [[User:Fturco|Fturco]] ([[User talk:Fturco|talk]]) 19:43, 2 July 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=389487Dell XPS 13 (9343)2015-07-31T22:06:07Z<p>DonJaime: /* BIOS updates */ Remove misinformation introduced in my last edit.</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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 />
{{Warning|Stay clear of kernel 4.2+ for now, as it introduces an regression that causes the touchpad I2C driver initialization to fail, rendering the touchpad useless.}}<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=YMRTD BIOS update A05] was released on 2015-07-31. 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 {{ic|/boot/efi}}) or on a USB flash drive and choose it from BIOS Update in the F12 boot menu.<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}} to be installed. See the [[Broadcom wireless]] page for more details.<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
{{Tip|Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.}}<br />
{{Tip|{{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== Audio channel balance issues (PulseAudio) ===<br />
The official pulseaudio package is missing a [[udev]] rule, which makes the system fallback to a generic audio profile. (Source?)<br />
<br />
This in turn results in a faulty mixing of audio channels, producing an rather odd sounding volume spectrum when using headphones in combination with equally balanced left and right audio channels.<br />
<br />
It sounds as if the left and right channel partially nullify each other.<br />
<br />
The easiest way to fix this issue is to add a ''udev'' rule, setting the right profile yourself.<br />
{{hc|/lib/udev/rules.d/91-pulseaudio-xps13.rules|<nowiki><br />
# Dell XPS 13 (9343) Audio Profile Picker UDEV Rule<br />
SUBSYSTEM!="sound", GOTO="pulseaudio_end"<br />
ACTION!="change", GOTO="pulseaudio_end"<br />
KERNEL!="card*", GOTO="pulseaudio_end"<br />
SUBSYSTEMS=="usb", GOTO="pulseaudio_end"<br />
<br />
# Dell XPS 13 (9343)<br />
ATTRS{subsystem_vendor}=="0x8086", ATTRS{subsystem_device}=="0x9ca0", ENV{PULSE_PROFILE_SET}="force-speaker-and-int-mic.conf"<br />
<br />
LABEL="pulseaudio_end"<br />
</nowiki>}}<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
So far the only proper fix I was able to find has been reverting to the an older build of mesa and mesa-libgl (10.5.7).<br />
<br />
I will update this troubleshooting entry once I've bisected the repository and found the commit causing this issue.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Talk:Dell_XPS_13_(9343)&diff=389485Talk:Dell XPS 13 (9343)2015-07-31T21:56:36Z<p>DonJaime: /* BIOS */</p>
<hr />
<div>== 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 />
== PulseAudio flat-volumes section ==<br />
<br />
I don't agree with the inclusion of the flat-volumes tip on this page, but I don't want to just delete it unilaterally, so I thought I'd ask what others think here. The [[:Category:Laptops]] page has fairly strict instructions to only include information that is specific to the laptop, and any info that is more generic should be moved to another page. There are a few exceptions made on this page already, like the Gnome mouse plugin tip, but those are generally included because it's not obvious where the problem lies. The 'flat-volumes' tip applies generally to PulseAudio and isn't specific to any hardware. An Arch user should be able to find the info on their own. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 17:35, 17 June 2015 (UTC)<br />
: I agree completely. [[User:Pancakes|Pancakes]] ([[User talk:Pancakes|talk]]) 08:22, 19 June 2015 (UTC)<br />
:: Okay, thanks. Section removed. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 08:48, 30 June 2015 (UTC)<br />
: You claim that the Gnome-Mouse plugin tip of mine is allowed to live because the source of the problem isn't obvious, yet at the same time you say the source of the problem with borked audio is obvious and easy to find for an "Arch user". Given the variety and many layers of audio protocols in use on Linux I would say that audio problems are anything but easy to diagnose and that newcomers would benefit greatly from having said reference link available. In my opinion, this is just another way of serving Arch's motto of keep it simple. Why hide known solutions? [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 13:49, 30 June 2015 (UTC)<br />
:: The Gnome mouse plugin tip is present because it creates an incompatibility with the touchpad section instructions, which makes it relevant to this page, whereas the flat-volumes tip has no relationship with the hardware in this laptop. It doesn't present an incompatibility to anything listed on this page or otherwise cause issues; it's simply an default setting in Pulse that some may find undesirable. It may seem silly but we have to draw the line somewhere, and as I've mentioned, we're given rather specific advice to keep only the things that relate to this laptop. But as for your other arguments, I would argue that since you have to manually install Pulse on Arch, the source of that flat-volumes behavior would be obvious, especially because none of the other sound subsystems have application-level behavior. In regards to Arch's motto, that's one interpretation, but I think that keeping this page short and on-topic also embodies the motto. [[User:Soren121|Soren121]] ([[User talk:Soren121|talk]]) 14:30, 30 June 2015 (UTC)<br />
<br />
== linux-mainline 4.1 ==<br />
<br />
I notice this page has changed recently to recommend people install linux-mainline 4.1 kernel so I tried it today but I get terrible graphic glitches compared to linux-xps13-alt which does not have those glitches and seems to work otherwise as well. In both cases I am using xf86-video-intel-git.<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 03:21, 19 June 2015 (UTC)<br />
: What kind of graphical glitches are you talking about? Mind pasting us your kernel cmdline along with a more detailed description of what those glitches look like? I've been running linux-mainline for a while now and have no graphical glitches. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:02, 30 June 2015 (UTC)<br />
:: After your comment here I checked my cmdline and found I had i915.enable_rc6=4 for some odd reason. I've corrected that to i915.enable_rc6=7 and it seems there are no glitches now. Thanks for responding. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:16, 1 July 2015 (UTC)<br />
::: No problem, I'm glad you were able to resolve your issue. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:22, 1 July 2015 (UTC)<br />
:::: While you're here, the touchpad is still problematic with phantom touches etc. On 4.1 which do you think works best, synaptics, or libinput? [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 10:37, 1 July 2015 (UTC)<br />
::::: I've been messing around with both of these already and found synaptics to be the better choice on the long run (YMMV). libinput randomly stops working after extended use, forcing me to reboot to get it back into a working state, which, given that I do my daily work on this device, is unacceptable. As for your reported ghost touches, the only time I've encountered something that could be considered a ghost touch was when I was typing a whole bunch of code and touched the damn thing with my palm. But this is a known problem with the broken palm detection in i2c mode (in combination with the synaptics driver). So, long story short... you either use libinput with working palm detection but random complete blackouts, or stick with synaptics but accept the broken palm detection (for now). Another thing I've noticed is that the mouse pointer acceleration goes wonky when using libinput, which makes it difficult to do accurate clicks when required. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:43, 1 July 2015 (UTC)<br />
:::::: Yes, I used the term "ghost touches" for want of a better description, but I do mean palm detection. I'm also a software developer and I worked 9 hours straight today within a few gnome-terminals using libinput on mainline 4.1rc8 + GNOME3 and found it works quite well. Better for me than synaptics so I am sticking with it. Note with both synaptics and libinput I get a better result if I ignore the wiki here and don't blacklist the psmouse module nor do I disable the gnome settings mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:29, 2 July 2015 (UTC)<br />
::::::: The psmouse thing is something I never quite understood either way, I have ignored that one as well and never had issues. Disabling the gnome mouse settings though is somewhat of a must for synaptics driver users as the default settings the gnome settings daemon enforces render the touchpad more or less useless. In your case of using libinput though, leaving this enabled is perfectly fine, as the default settings for libinput are way less crippling than the ones for synaptics. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 11:50, 2 July 2015 (UTC)<br />
:::::::: That's not my experience at all with synaptics. On all the kernels I have tried I find the settings without the mouse plugin to be hopeless. With the mouse plugin things work fine, 2 finger tap for right mouse, 3 finger tap for paste, etc (same as libinput by default). Can't get it to work properly if I disable the mouse plugin. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 11:57, 2 July 2015 (UTC)<br />
::::::::: I've decided to give libinput another go as I was curious about your reported successes with it. And what shall I say? You were right. After copying your every move, whitelisting psmouse, re-enabling the mouse config plugin and getting rid of the xorg.conf configuration entirely (only using it to enable the driver) - everything started working out of the box. So yes... libinput is the better choice at the moment, and I think that the XPS13 main page should be updated to reflect this finding. The only thing that isn't working as it should so far is the gnome mouse config plugin, as all of its touchpad settings have no influence on the libinput driver. This however is an issue with the gnome config daemon and not the touchpad driver itself. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 10:38, 10 July 2015 (UTC)<br />
:::::::::: I am using linux-mainline 4.1rc7-1 with libinput 0.18.0-1 and gnome settings work for me. Two finger scroll is selected but greyed out. Both Tap to Click, and Natural Scrolling can be selected on/off and both do change the setting. Selecting all these 3 settings on is the sensible configuration of course(!). I have been using testing/libinput 0.19.0-1 for the last few days as there are subtle improvements. I will compile up the testing/linux 4.1.2-1 kernel today. Unfortunately we need to manually add the mic fix patch to the released 4.1 kernel as per my post https://bbs.archlinux.org/viewtopic.php?id=199350 which is very disappointing. I use Google Hangouts and Skype extensively so the mic is essential for me. [[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 22:14, 10 July 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 />
== Touchpad ==<br />
<br />
With no configuration except disabling psmouse, my touchpad doesn't freeze and has a soft right button. Is that just KDE being nice to me or has something else been fixed?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
The three soft-button configuration is useful for anyone with a clickpad. Should it be moved to the [[Touchpad Synaptics]] page?<br />
<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 12:08, 30 July 2015 (UTC)<br />
<br />
: Yes KDE is being nice to you and yes the three button config is a key-essential (for me at least it is), so why not let other people benefit from it as well I guess. I can't configure any settings for the touchpad at all using the Gnome-variant configuration dialog, so on that one (or its many derivatives) you will have to configure things yourself in xorg config files (which isn't too bad either way, as I don't believe anyone will ever change the touchpad config anyway) until someone actually fixes the mouse-configuration tools to work with our touchpad.<br />
<br />
[[User:Bulletmark|Bulletmark]] ([[User talk:Bulletmark|talk]]) 14:08, 30 July 2015 (UTC)<br />
<br />
: I'm using GNOME and since kernel 4.1.1 and libinput 0.19+ the touchpad works perfectly for me with no special configuration at all. No xorg conf file, I have not blacklisted psmouse, and I have not disabled the gnome settings daemon. There are 3 settings in the gnome touchpad settings display to select and they all work. They are Tap to click, Two finger scroll, and Natural Scrolling. Libinput is selected by xorg by default and, unlike synaptics, has basic palm detection. Two finger tap gives right click, 3 finger tap gives middle click (e.g. paste). I think the wiki is out of date here. Best setup, at least with GNOME, is just to leave everything default and check the 3 options on in the settings.<br />
<br />
:: Sadly, the xorg configuration is still required for a bunch of gnome derivatives like Cinnamon. [[User:Coldbird|Coldbird]] ([[User talk:Coldbird|talk]]) 14:49, 30 July 2015 (UTC)<br />
<br />
I've tidied up the clickpad section on the synaptics page and linked to it from here for palm detection and soft button config.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 16:43, 31 July 2015 (UTC)<br />
<br />
<br />
== BIOS ==<br />
<br />
Seems newer models ship with BIOS 05 which can't be found on the Dell page at the moment --[[User:Piratenpanda|Piratenpanda]] ([[User talk:Piratenpanda|talk]]) 18:18, 31 July 2015 (UTC)<br />
<br />
I've updated the BIOS Update section to point to BIOS A05.<br />
[[User:DonJaime|DonJaime]] ([[User talk:DonJaime|talk]]) 21:56, 31 July 2015 (UTC)</div>DonJaimehttps://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9343)&diff=389484Dell XPS 13 (9343)2015-07-31T21:54:54Z<p>DonJaime: /* BIOS updates */ Update to latest update. Attempt at more clarity in instructions.</p>
<hr />
<div>[[Category:Dell]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || wl ''or'' iwlwifi<br />
|-<br />
| Bluetooth || {{G|Works after installing firmware}}|| btbcm<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Works after configuration}} || hid_multitouch<br />
|-<br />
| Webcam || {{G|Working}} || linux-uvc<br />
|-<br />
| Card Reader || {{G|Working}} || rtsx_usb<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 the XPS 13 line, and 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]], [[Beginners' 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 />
{{Warning|Stay clear of kernel 4.2+ for now, as it introduces an regression that causes the touchpad I2C driver initialization to fail, rendering the touchpad useless.}}<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=YMRTD BIOS update A05] was released on 2015-07-31. 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 in your EFI partition ({{ic|/boot/efi}} or {{ic|/boot/efi}}) or on a USB flash drive and choose it from BIOS Update in the F12 boot menu or F2 BIOS Setup during bootup to update.<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}} to be installed. See the [[Broadcom wireless]] page for more details.<br />
<br />
Some higher-end models do not use the Dell-branded adapter but instead use an Intel Wireless 7265, which is supported by the mainline kernel. This card is generally available as an aftermarket purchase for those wishing to replace the Broadcom wireless in their laptop. Compared to the Broadcom card, the Intel card has a 2-3 times wider reception range and way higher throughput, making it an worthwhile upgrade should you decide to do so. Note that the Intel 7265 card exists as both a WLAN standalone and WLAN/Bluetooth combo card; both work, so it's your decision if you are willing to pay extra to get Bluetooth support or not.<br />
<br />
{{Tip|'''Intel users:''' Intel Linux driver maintainer Emmanuel Grumbach maintains a [https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git fork of the linux-firmware repository] which contains bleeding edge firmware that provides improved throughput and connection stability for the Intel 7265 card.}}<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 have to retrieve it from the [http://catalog.update.microsoft.com/v7/site/ScopedViewRedirect.aspx?updateid=87a7756f-1451-45da-ba8a-55f8aa29dfee Windows driver]. 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 [https://en.wikipedia.org/wiki/Intel_High_Definition_Audio HDA standard] and the [https://en.wikipedia.org/wiki/I%C2%B2S I2S standard]. The embedded controller in the XPS 13 uses the [https://en.wikipedia.org/wiki/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+, the kernel will automatically use the sound card in HDA mode.<br />
<br />
Microphone support was finally fixed in the mainline kernel in 4.1.3. All older kernel versions require patches to fix it. To fix it on kernels 4.1.0-4.1.2, apply the patch [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=831bfdf9520e389357cfeee42a6174a73ce7bdb7 available here]. To fix it on kernels older than 4.1, apply this patchset: [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=e1e62b98ebddc3234f3259019d3236f66fc667f8 1], [https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec 2].<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.<br />
<br />
==== I2S mode ====<br />
I2S support in Linux is still quite nascent, and some important features, notably jack detection, are not due to land until kernel 4.2 or later. [http://www.spinics.net/lists/linux-acpi/msg57126.html] As a result, I2S support is currently disabled in favor of HDA mode. An ACPI REV quirk mode was merged in for 4.2 that will force HDA mode on until I2S support is ready. [http://thread.gmane.org/gmane.linux.acpi.devel/75464/focus=75466][https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=18d78b64fddc11eb336f01e46ad3303a3f55d039]<br />
<br />
In I2S mode, the dual-boot workaround is not necessary.<br />
<br />
=== Touchpad ===<br />
With the latest BIOS patch, most of the touchpad functions should work, although [[Touchpad Synaptics#Using_the_driver.27s_automatic_palm_detection|palm detection]] does not work in i2c mode yet. For advanced settings with {{pkg|xf86-input-synaptics}}, the ''psmouse'' kernel module must be [[Kernel modules#Blacklisting|blacklisted]] first.<br />
<br />
The touchpad may freeze if two fingers are detected on the pad. This can be fixed by setting {{ic|1=synclient Clickpad=1}}<br />
<br />
If your desktop does not provide useful default settings for the clickpad (no right or middle button emulation, for example) or you want more control than your desktop environments settings provide, see [[Touchpad Synaptics#Buttonless_touchpads_.28aka_ClickPads.29|Touchpad Synaptics]]<br />
<br />
If you need working palm detection, 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-synaptics.conf|<nowiki><br />
Section "InputClass"<br />
Identifier "touchpad"<br />
Driver "libinput"<br />
Option "Tapping" "on"<br />
Option "AccelSpeed" "1"<br />
EndSection<br />
</nowiki>}}<br />
<br />
=== Powersaving ===<br />
<br />
With kernel 4.1 and {{pkg|tlp}}, the idle power usage is reduced to ~3.5 W with the following [[kernel parameters]]:<br />
<br />
pcie_aspm=force i915.enable_fbc=1 i915.enable_rc6=7<br />
<br />
However, there have been reports (as of July 2015) of {{ic|<nowiki>i915.enable_fbc=1</nowiki>}} causing flickering and/or freezes.<br />
<br />
{{Tip|Enabling PSR support, via {{ic|<nowiki>i915.enable_psr=1</nowiki>}}, will further reduce idle power usage to ~2.6 W; however, this currently causes flickering.}}<br />
{{Tip|{{ic|<nowiki>i915.lvds_downclock=1</nowiki>}} for lvds_downclock is no longer needed. From the MacBook page: "there's a new auto-downclock for eDP panels in recent kernels and it's enabled by default if available, so don't use - recommendation from irc #intel-gfx").}}<br />
<br />
== Troubleshooting ==<br />
<br />
=== Loss of horizontal sync when switching TTYs ===<br />
See [[Intel graphics#Loss of horizontal sync when switching TTYs]].<br />
<br />
=== Pink & green artifacts in video or webcam output ===<br />
See [[Intel graphics#Pink & green artifacts in video or webcam output]].<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.<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 />
If your WiFi connection drops constantly, try [[disabling]] [[NetworkManager]] (if you have it installed) and fall back to using {{ic|wifi-menu}}.<br />
<br />
=== Audio channel balance issues (PulseAudio) ===<br />
The official pulseaudio package is missing a [[udev]] rule, which makes the system fallback to a generic audio profile. (Source?)<br />
<br />
This in turn results in a faulty mixing of audio channels, producing an rather odd sounding volume spectrum when using headphones in combination with equally balanced left and right audio channels.<br />
<br />
It sounds as if the left and right channel partially nullify each other.<br />
<br />
The easiest way to fix this issue is to add a ''udev'' rule, setting the right profile yourself.<br />
{{hc|/lib/udev/rules.d/91-pulseaudio-xps13.rules|<nowiki><br />
# Dell XPS 13 (9343) Audio Profile Picker UDEV Rule<br />
SUBSYSTEM!="sound", GOTO="pulseaudio_end"<br />
ACTION!="change", GOTO="pulseaudio_end"<br />
KERNEL!="card*", GOTO="pulseaudio_end"<br />
SUBSYSTEMS=="usb", GOTO="pulseaudio_end"<br />
<br />
# Dell XPS 13 (9343)<br />
ATTRS{subsystem_vendor}=="0x8086", ATTRS{subsystem_device}=="0x9ca0", ENV{PULSE_PROFILE_SET}="force-speaker-and-int-mic.conf"<br />
<br />
LABEL="pulseaudio_end"<br />
</nowiki>}}<br />
<br />
=== DRM GPU Render Ring Hang when using OpenGL ===<br />
With the latest update of mesa and mesa-libgl (10.6.2 at the time of writing) a new regression has been introduced, causing OpenGL applications to trigger a Render Ring Hang after a while, effectively forcing the GPU to reinitialize and crash all applications that were part of the affected Render Ring.<br />
<br />
So far the only proper fix I was able to find has been reverting to the an older build of mesa and mesa-libgl (10.5.7).<br />
<br />
I will update this troubleshooting entry once I've bisected the repository and found the commit causing this issue.<br />
<br />
== See also ==<br />
<br />
General:<br />
* [https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/ Linux support for the Dell XPS 13 9343 (2015 model)]<br />
* [https://lkml.org/lkml/2015/3/12/149 <nowiki>[PATCH]</nowiki> ACPI: Adjust the return value of _REV on x86]<br />
* [https://lkml.org/lkml/2015/3/16/472 Re: <nowiki>[PATCH]</nowiki> Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.]<br />
* [https://github.com/mpalourdio/xps13 Collection of links and different configurations]<br />
<br />
Project Sputnik:<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/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/04/09/4th-gen-dell-xps-13-developer-edition-available/ 4th gen Dell XPS 13 developer edition available!]<br />
<br />
Packages for XPS 13:<br />
* [https://aur.archlinux.org/packages/linux-xps13-alt/ altercation's custom XPS 13 2015 kernel with sound+mic patches & clickpad patch]</div>DonJaime