https://wiki.archlinux.org/api.php?action=feedcontributions&user=Gtklocker&feedformat=atomArchWiki - User contributions [en]2024-03-29T14:33:54ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=565538Dell XPS 15 (9570)2019-02-02T12:26:02Z<p>Gtklocker: /* Graphics */ Remove uvcvideo blacklist which is a webcam module</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{G|Working}}<br />
|-<br />
| [[#Hibernate|Hibernate]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Modify}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo deep|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
{{Warning|Some users have reported a problem where the CPUs get stuck in a high power state after resuming from S3 (deep) suspension [https://www.reddit.com/r/Dell/comments/91313h/xps_15_9570_c_state_bug_after_s3_sleep_and_modern/].}}<br />
<br />
<br />
== Hibernate ==<br />
<br />
Works out of the Box see [[Power management/Suspend and hibernate]]<br />
<br />
== Graphics ==<br />
<br />
The nouveau module is known to cause kernel panics and freezes on this model. One way to mitigate this is by adding {{ic|nomodeset}} to the kernel options, however it's best if you completely disable it.<br />
<br />
{{hc|/etc/modprobe.d/blacklist.conf|<br />
blacklist nouveau<br />
blacklist rivafb<br />
blacklist nvidiafb<br />
blacklist rivatv<br />
blacklist nv}}<br />
<br />
And make sure the discrete GPU powers off by default on boot.<br />
<br />
{{hc|/etc/tmpfiles.d/nvidia_pm.conf|<br />
w /sys/bus/pci/devices/0000:01:00.0/power/control - - - - auto}}<br />
<br />
Integrated graphics works well out of the box.<br />
<br />
=== Optimus Nvidia ===<br />
<br />
Works but additional configuration is needed. (see *[https://github.com/Bumblebee-Project/bbswitch/issues/140#issuecomment-394180574])<br />
* If tlp is installed, add the graphic card to '''RUNTIME_PM_BLACKLIST'''<br />
* Uninstall or disable bbswitch<br />
* Install bumblebee and set '''PMMethod=none''' in nvidia section<br />
* Install nvidia driver<br />
* Reboot<br />
<br />
Note: This is just one configuration that worked. There are more configurations that might work just as well or even better. Sometimes nvidia driver can not be unloaded because some process is still using it.<br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389]).<br />
<br />
=== nvidia-xrun ===<br />
<br />
The {{AUR|nvidia-xrun}} package will not work because it relies on bbswitch, that is broken. The {{AUR|nvidia-xrun-pm}} package provides an alternative version that works with this card. After installing the package a service can be enabled to automatically bring the card down during boot:<br />
<br />
systemctl enable nvidia-xrun-pm<br />
<br />
==Thunderbolt docks==<br />
<br />
===TB16===<br />
TB16 works fine if either Thunderbolt security is disabled in the BIOS or using {{Pkg|bolt}} to temporarily authorize or permanently enroll Thunderbolt devices with Thunderbolt security activated.<br />
<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].<br />
<br />
== Tips and Tricks ==<br />
<br />
===Systemd doesn't wait for Network===<br />
<br />
Few months ago systemd added "after= .. .. network.target" in /usr/lib/systemd/system/systemd-user-sessions.service<br />
<br />
This causes systemd to wait for network connection at boot, you can modify this file to remove network.target but it will be overwritten on systemd update. A better workaround is to add /etc/systemd/system/systemd-user-sessions.service with network.target removed.<br />
<br />
{{hc|/etc/systemd/system/systemd-user-sessions.service|2= <br />
# This file is part of systemd.<br />
#<br />
# systemd is free software; you can redistribute it and/or modify it<br />
# under the terms of the GNU Lesser General Public License as published by<br />
# the Free Software Foundation; either version 2.1 of the License, or<br />
# (at your option) any later version.<br />
<br />
[Unit]<br />
Description=Permit User Sessions<br />
Documentation=man:systemd-user-sessions.service(8)<br />
After=remote-fs.target nss-user-lookup.target<br />
<br />
[Service]<br />
Type=oneshot<br />
RemainAfterExit=yes<br />
ExecStart=/usr/lib/systemd/systemd-user-sessions start<br />
ExecStop=/usr/lib/systemd/systemd-user-sessions stop }}</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=555682Dell XPS 15 (9570)2018-11-18T11:20:48Z<p>Gtklocker: Talk about how to disable dGPU without bbswitch or proprietary drivers</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{G|Working}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Modify}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo deep|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
The nouveau module is known to cause kernel panics and freezes on this model. One way to mitigate this is by adding {{ic|nomodeset}} to the kernel options, however it's best if you completely disable it.<br />
<br />
{{hc|/etc/modprobe.d/blacklist.conf|<br />
blacklist nouveau<br />
blacklist rivafb<br />
blacklist nvidiafb<br />
blacklist rivatv<br />
blacklist nv<br />
blacklist uvcvideo}}<br />
<br />
And make sure the discrete GPU powers off by default on boot.<br />
<br />
{{hc|/etc/tmpfiles.d/nvidia_pm.conf|<br />
w /sys/bus/pci/devices/0000:01:00.0/power/control - - - - auto}}<br />
<br />
Integrated graphics works well out of the box.<br />
<br />
=== Optimus Nvidia ===<br />
<br />
Works but additional configuration is needed. (see *[https://github.com/Bumblebee-Project/bbswitch/issues/140#issuecomment-394180574])<br />
* Add pcie_port_pm=on to kernel options<br />
* If tlp is installed, add the graphic card to '''RUNTIME_PM_BLACKLIST'''<br />
* Uninstall or disable bbswitch<br />
* Install bumblebee and set '''PMMethod=none''' in nvidia section<br />
* Install nvidia driver<br />
* Reboot<br />
<br />
Note: This is just one configuration that worked. There are more configurations that might work just as well or even better. Sometimes nvidia driver can not be unloaded because some process is still using it. However even if the driver is loaded power saving still works.<br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547837Dell XPS 15 (9570)2018-10-15T17:14:17Z<p>Gtklocker: Bluetooth works</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{G|Working}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo deep|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547836Dell XPS 15 (9570)2018-10-15T17:10:48Z<p>Gtklocker: /* Suspend */ fix mistake in command sequence</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{G|Working}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo deep|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547835Dell XPS 15 (9570)2018-10-15T17:10:15Z<p>Gtklocker: Suspend does work</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{G|Working}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo s2idle|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547478Dell XPS 15 (9570)2018-10-13T15:52:11Z<p>Gtklocker: /* Suspend */ fix typo</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{Y|Buggy}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo s2idle|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the change permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547475Dell XPS 15 (9570)2018-10-13T15:49:09Z<p>Gtklocker: Fix suspend link on functionality table</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend|Suspend]] || {{Y|Buggy}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo s2idle|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the changed permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547472Dell XPS 15 (9570)2018-10-13T15:46:07Z<p>Gtklocker: EFI firmware updates do work (fwupd)</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend_and_Hibernate|Suspend]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#EFI_firmware_updates|EFI firmware updates]] || {{G|Working}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo s2idle|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the changed permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])<br />
<br />
== EFI firmware updates ==<br />
<br />
This device is supported by [[Fwupd]].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Dell_XPS_15_(9570)&diff=547463Dell XPS 15 (9570)2018-10-13T15:41:22Z<p>Gtklocker: Add suspend section</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 15 (9570)]]<br />
{{Note|This page far from completed. Some not mentioned items could be same as [[XPS 15 9560]]}}<br />
<br />
{| class="wikitable" style="float: right;"<br />
| '''Device/Functionality''' || '''Status'''<br />
|-<br />
| [[#Suspend_and_Hibernate|Suspend]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Suspend_and_Hibernate|Hibernate]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Graphics|Integrated Graphics]] || {{G|Working}}<br />
|-<br />
| [[#Graphics|Discrete Nvidia Graphics]] || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Wifi]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|Bluetooth]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#Wifi_and_Bluetooth|rfkill]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Audio || {{G|Working}}<br />
|-<br />
| [[#Touchpad|Touchpad]]{{Broken section link}} || {{G|Working}}<br />
|-<br />
| Webcam || {{G|Working}}<br />
|-<br />
| Card Reader || {{G|Working}}<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}}<br />
|-<br />
| [[#Power_Saving|Power Management]]{{Broken section link}} || {{Y|Buggy}}<br />
|-<br />
| [[#UEFI|EFI firmware updates]]{{Broken section link}} || {{Grey|Not tested}}<br />
|-<br />
| [[#Fingerprint_reader|Fingerprint reader]]{{Broken section link}} || {{R|Not working}}<br />
|}<br />
<br />
== Suspend ==<br />
<br />
By default, the very inefficient s2idle suspend variant is incorrectly selected. This is probably due to the BIOS. The much more efficient deep variant should be selected instead:<br />
<br />
$ cat /sys/power/mem_sleep <br />
[s2idle] deep<br />
$ echo s2idle|sudo tee /sys/power/mem_sleep<br />
$ cat /sys/power/mem_sleep <br />
s2idle [deep]<br />
<br />
To make the changed permanent add {{ic|1=mem_sleep_default=deep}} to your kernel parameters.<br />
<br />
Read more regarding the sleep variants on the kernel documentation [https://www.kernel.org/doc/html/v4.18/admin-guide/pm/sleep-states.html].<br />
<br />
== Graphics ==<br />
<br />
Integrated graphics works well out of the box. <br />
<br />
=== bbswitch ===<br />
<br />
Discrete (GeForce GTX 1050 Ti) graphics card do not work well with bbswich. It won't power on/off (see *[https://bbs.archlinux.org/viewtopic.php?id=238389])</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=IRC_channels&diff=122767IRC channels2010-11-27T12:40:46Z<p>Gtklocker: /* International IRC Channels */</p>
<hr />
<div>[[Category:Website Resources]]<br />
{{i18n|IRC Channels}}<br />
== Official IRC Channels ==<br />
You can find official Arch-related discussion on the following Internet Relay Chat (IRC) channels, located at the '''[irc://irc.freenode.net irc.freenode.net]''' IRC network:<br />
{|<br />
|-<br />
| '''#archlinux'''<br />
| The main discussion channel, mostly in English<br />
|-<br />
| '''#archlinux64'''<br />
| x86_64 specific discussion channel, mostly in English<br />
|-<br />
| '''#archlinux-bugs'''<br />
| Bug-centric discussion<br />
|-<br />
| '''#archlinux-offtopic'''<br />
| Random offtopic discussions.<br />
|-<br />
| '''#archlinux-pacman'''<br />
| Pacman development and discussion<br />
|-<br />
| '''#archlinux-multilib'''<br />
| Arch Linux Multilib Project discussion and packaging<br />
|}<br />
<br />
== International IRC Channels ==<br />
International discussions are available at the following channels, also located at the '''[irc://irc.freenode.net irc.freenode.net]''' IRC network:<br />
<br />
{|<br />
|-<br />
| '''#archlinux-br'''<br />
| Discussion (Brazilian)<br />
|-<br />
| '''#archlinux-cr'''<br />
| Discussion (Costa Rica)<br />
|-<br />
| '''#arch-cn'''<br />
| Discussion (Chinese), on '''[irc://irc.oftc.net irc.oftc.net]'''<br />
|-<br />
| '''#archlinux.de'''<br />
| Discussion (German)<br />
|-<br />
| '''#archlinux.dk'''<br />
| Discussion (Danish)<br />
|-<br />
| '''#archlinux-greece'''<br />
| Discussion (Greek)<br />
|-<br />
| '''#archlinux-es'''<br />
| Discussion (Spanish)<br />
|-<br />
| '''#archlinux-fr'''<br />
| Discussion (French)<br />
|-<br />
| '''#archlinux-gaelic'''<br />
| Discussion (Gaelic)<br />
|-<br />
| '''#archlinux.hu'''<br />
| Discussion (Hungarian)<br />
|-<br />
| '''#archlinux-ir'''<br />
| Discussion (Persian)<br />
|-<br />
| '''#archlinux.it'''<br />
| Discussion (Italian)<br />
|-<br />
| '''#archlinux.pl'''<br />
| Discussion (Polish)<br />
|-<br />
| '''#archlinux.ro'''<br />
| Discussion (Romanian)<br />
|-<br />
| '''#archlinux-rs'''<br />
| Discussion (Serbian)<br />
|-<br />
| '''#archlinux.se'''<br />
| Discussion (Swedish)<br />
|-<br />
| '''#archlinux.tr'''<br />
| Discussion (Turkish)<br />
|-<br />
| '''#archlinux-il'''<br />
| Discussion (Hebrew)<br />
|-<br />
| '''#archlinux.fi'''<br />
| Discussion (Finnish)<br />
|}<br />
<br />
== Related Pages ==<br />
* [[Arch Around the World]]<br />
* [[International Communities]]<br />
* [[IRC_Channel]]</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Midori&diff=114695Midori2010-08-22T12:19:14Z<p>Gtklocker: </p>
<hr />
<div>This is the Midori unofficial wiki page.<br />
<br />
== What is Midori? ==<br />
Midori is a very powerful GTK+2 browser based on webkit, which aims to be simple, fast and snappy. Yet it's not very popular but it's really powerful.<br />
<br />
== How can I install it? ==<br />
The installation is pretty simple. As for many other packages you'll just need to do:<br />
pacman -S midori</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Midori&diff=114694Midori2010-08-22T12:02:25Z<p>Gtklocker: </p>
<hr />
<div>This is the Midori unofficial wiki page.<br />
<br />
== What is Midori? ==<br />
Midori is a very powerful GTK+2 browser based on webkit, which aims to be simple, fast and snappy. Yet it's not very popular but it's really powerful.</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=Midori&diff=114693Midori2010-08-22T12:01:14Z<p>Gtklocker: Created page with "This is the Midori unofficial wiki page. == What is Midori? == Midori is a very powerful GTK+2 browser based on webkit, which aims to be simple, fast and snappy. Yet it's not v..."</p>
<hr />
<div>This is the Midori unofficial wiki page.<br />
<br />
<br />
== What is Midori? ==<br />
Midori is a very powerful GTK+2 browser based on webkit, which aims to be simple, fast and snappy. Yet it's not very popular but it's really powerful.</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=ATI&diff=109417ATI2010-06-23T21:45:29Z<p>Gtklocker: /* Powersaving */</p>
<hr />
<div>[[Category: Graphics (English)]]<br />
[[Category: X Server (English)]]<br />
[[Category: HOWTOs (English)]]<br />
{{i18n|ATI}}<br />
{{Article summary start}}<br />
{{Article summary text|An overview of open source ATI/AMD video card drivers.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI Catalyst}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|NVIDIA}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
Owners of '''ATI''' video cards have a choice between ATI's proprietary driver ({{Package AUR|catalyst}}) and open source alternatives ({{Package Official|xf86-video-ati}} or {{Package Official|xf86-video-radeonhd}}).<br />
<br />
Currently, the performance of the open source drivers are not ''on par'' with the proprietary driver in terms of 3D performance and lack certain features, such as reliable TV-out support. They do, however, offer better dual-head support (<tt>xf86-video-ati</tt>), excellent 2D acceleration, and provide sufficient 3D acceleration for OpenGL-accelerated [[window manager]]s, such as [[Compiz]] or KWin. Currently, [http://www.archlinux.org/news/439/ the ATI Catalyst package is available in the AUR].<br />
<br />
If unsure, try the open source drivers first; they will suit most needs and are generally less problematic and flexible. (See the [http://www.x.org/wiki/RadeonFeature feature matrix] for details.) For an overview of ATI's proprietary "Catalyst" video card driver, see [[ATI Catalyst]]; this article covers the open source drivers.<br />
<br />
==Naming conventions==<br />
ATI's [[Wikipedia:Radeon|Radeon]] brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both ''product'' names (e.g. HD 4850, X1900) and ''code'' or ''core'' names (e.g. RV770, R580). Traditionally, a ''product series'' will correspond to a ''core series'' (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series &ndash; including the RV515, RV530, R520, and R580 cores).<br />
<br />
For a table of core and product series, see [[Wikipedia:Comparison of AMD graphics processing units]].<br />
<br />
== Differences between open source drivers ==<br />
<br />
<div style="width: 50%; float: left"><br />
===<tt>xf86-video-ati</tt> (radeon)===<br />
*Works with Radeon chipsets up to HD 4xxx (latest R700 chipsets) as well as HD 5xxx (latest R800 chipsets). <br />
*Radeons up to the X1xxx series are fully supported, stable, and full 2D and 3D acceleration are provided. <br />
*Radeons from HD 2xxx to X4xxx have full 2D acceleration and functional 3D acceleration, but are not supported by all the features that the proprietary driver provides (for example, powersaving is still in a testing phase). <br />
*Supports DRI1, RandR 1.2/1.3, EXA acceleration and [[KMS|kernel mode-setting]]/DRI2 (with the latest Linux kernel, libdrm and Mesa versions).<br />
*All cards from HD 5xxx (R800) and newer are supported, but for now, with 2D support only.<br />
*'''HDMI''' support will soon be implemented in '''xf86-video-ati''' over AtomBIOS.<br />
</div><br />
<br />
<div style="width: 50%; float: right"><br />
===<tt>xf86-video-radeonhd</tt> (radeonhd)===<br />
*Driver for ATI R500 chipsets (Radeon X1000 series) and '''newer'''. <br />
*Written by Novell with specifications provided to the public by AMD. <br />
*Supports RandR 1.2 and is under heavy development. It does also support HDMI with sound (if your hardware is so equipped, except RV730 based chip sets).<br />
</div><br />
<br />
<div style="clear: both"></div> <!-- prevent overlapping paragraphs --><br />
<br />
Generally, '''xf86-video-ati''' seems to offer more consistent performance as compared to '''xf86-video-radeonhd''' and is more actively developed, so it should be your first choice, no matter which ATI card you own. xf86-video-radeonhd should be used as a "fallback" driver in case you encounter errors with xf86-video-ati and it '''should not be used''' as a primary driver - radeonhd's development has been unofficially halted. In case you need to use a driver for newer ATI cards, you should prefer the proprietary '''catalyst''' driver.<br />
<br />
{{Note|xf86-video-ati is recognized as "'''radeon'''" by Xorg (in xorg.conf) and xf86-video-radeonhd as "'''radeonhd'''". }}<br />
<br />
== Installation and configuration ==<br />
<br />
=== Installation ===<br />
{{Note| If you have previously installed the proprietary driver, make sure to remove <code>catalyst</code> and '''reboot'''.}}<br />
<br />
To install <code>xf86-video-ati</code> :<br />
pacman -S xf86-video-ati libgl ati-dri<br />
<br />
To install <code>xf86-video-radeonhd</code> : <br />
pacman -S xf86-video-radeonhd libgl ati-dri<br />
<br />
{{Note|All cards from HD3xxx (R600) and newer need to install additional firmware files from [[AUR]]: [[http://aur.archlinux.org/packages.php?ID=33016 radeon_ucode]]}}<br />
{{Note|The GIT versions of these drivers can be found on [[AUR]].}}<br />
<br />
=== Configuration ===<br />
You now have the choice between creating an xorg.conf, or attempting to use the recently enabled '''Xorg''' autodetection. <br />
<br />
==== Running Xorg without xorg.conf ====<br />
In most cases, Xorg can '''autodetect''' your hardware settings. The Xorg.conf configuration file in /etc/X11 is optional since Xorg-server 1.5.x.<br />
<br />
Always make sure you have '''mesa''', the group '''xorg''' and the group '''xorg-input-drivers''' installed:<br />
pacman -S xorg-input-drivers mesa xorg<br />
<br />
{{Note| With KMS (Kernel Mode Setting) enabled, '''xorg.conf may not be needed at all.''' For more info on Radeon Kernel mode-setting, read [[#Kernel mode-setting (KMS)]].}}<br />
<br />
==== Running Xorg with expanded xorg.conf ====<br />
{{Note| '''/etc/X11/xorg.conf''' no longer requires sections for all input devices because Udev can configure some/all via hotplugging. (Ensure '''xorg-input-drivers''' are installed.)}}<br />
<br />
In case you want manual configuration, edit your [[xorg.conf]], and add or make sure you have the following in their given sections:<br />
Section "Module"<br />
Load "glx"<br />
Load "dri"<br />
Load "drm"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-ati</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeon"<br />
EndSection<br />
<br />
Device section for <code>xf86-video-radeonhd</code> :<br />
Section "Device"<br />
Identifier "name" # your alias<br />
Driver "radeonhd"<br />
Option "AccelMethod" "exa" # to enable 2D and Xv acceleration on R6xx/R7xx - default AccelMethod shadowfb<br />
Option "DRI" "on" # to enable 2D and Xv acceleration on R6xx/R7xx - default DRI disabled<br />
EndSection<br />
<br />
{{Note|Try below for smooth performance,over Option "DRI", for RS780M/MN [Radeon HD 3200] using the radeonhd driver(as of 3rd May 2009)}}<br />
<br />
This section (DRI) is not needed (thus deprecated), but use it if you encounter DRI related problems.<br />
Section "DRI"<br />
Group "video"<br />
Mode 0666<br />
EndSection<br />
<br />
Adding '''only''' the '''Device''' Section in the xorg.conf should fit most cases. Using that Section, you can enable features and tweak the driver's performance or behaviour.<br />
<br />
When using the opensource drivers, ensure <code>catalyst</code> is ''not'' installed -- '''ati-dri''' is being used instead. Otherwise, the wrong <code>libGL.so</code> will be installed, which will cause direct rendering to fail.<br />
<br />
== Kernel mode-setting (KMS) ==<br />
<br />
[[KMS]] enables native resolution in the framebuffer and allows for instant console (tty) switching. KMS also enables newer technologies (such as DRI2) which will help reduce artifacts and increase 3D performance, even kernel space power-saving. <br />
<br />
KMS for ATI video cards requires the [[Xorg]] free video user space driver {{Package Official|xf86-video-ati}} version 6.12.4 or later. <br />
<br />
=== Enabling experimental KMS ===<br />
<br />
Since kernel26 v.2.6.33, KMS is '''enabled''' by default for ATI cards. <br />
<br />
==== Early KMS start ====<br />
<br />
''This method will start KMS as early as possible in the [[boot process]] (when the [[initramfs]] is loaded).''<br />
<br />
# Remove all {{Codeline|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader configuration file ({{Filename|/boot/grub/menu.lst}} for [[GRUB]] users). Using other framebuffer drivers (such as <tt>[[uvesafb]]</tt> or <tt>radeonfb</tt>) will conflict with KMS. Remove any framebuffer related modules from {{Filename|/etc/mkinitcpio.conf}}. {{Codeline|<nowiki>video=</nowiki>}} can now be used in conjunction with KMS.<br />
# Add {{Codeline|radeon}} to MODULES array in {{Filename|/etc/mkinitcpio.conf}}. Depending on motherboard chipset, it may be necessary to add {{Codeline|intel_agp}} before the {{Codeline|radeon}} module. Previously, the {{Codeline|fbcon}} module also needed to be listed to be able to switch to the console after X has started, but is now compiled into the default kernel.<br />
#* ''Following is probably not true since Linux 2.6.33, at least author didn't run into any problems:'' For newer ATI cards ('''R6xx''' and '''newer''') extra microcode is currently needed. Grab [http://aur.archlinux.org/packages.php?ID=33016 radeon_ucode] and [http://aur.archlinux.org/packages.php?ID=31708 radeon-initrd] from AUR, '''build''' and '''install''' them and add {{Codeline|radeon}} to HOOKS array in {{Filename|/etc/mkinitcpio.conf}}.<br />
# Re-generate your initramfs: <pre># mkinitcpio -p kernel26</pre><br />
# Add {{Codeline|<nowiki>radeon.modeset=1</nowiki>}} to the kernel options in the bootloader configuration file to enable KMS.<br />
# '''Reboot''' the system.<br />
<br />
==== Late start ====<br />
<br />
''With this choice, KMS will be enabled when modules are loaded during the [[boot process]].''<br />
<br />
# Remove all {{Codeline|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader configuration file ({{Filename|/boot/grub/menu.lst}} for [[GRUB]] users). Using other framebuffer drivers (such as <tt>[[uvesafb]]</tt> or <tt>radeonfb</tt>) will conflict with KMS. Remove any framebuffer related modules from {{Filename|/etc/mkinitcpio.conf}}. {{Codeline|<nowiki>video=</nowiki>}} can now be used in conjunction with KMS.<br />
# Add {{Codeline|radeon}} to MODULES array in {{Filename|/etc/rc.conf}}. Depending on motherboard chipset, it may be necessary to add {{Codeline|intel_agp}} before the {{Codeline|radeon}} module. Previously, the {{Codeline|fbcon}} module also needed to be listed to be able to switch to the console after X has started, but is now compiled into the default kernel.<br />
# '''Reboot''' the system.<br />
<br />
{{Tip|Some users have reported faster [[udev]] module loading by adding {{Codeline|<nowiki>options radeon modeset=1</nowiki>}} to {{Filename|/etc/modprobe.d/modprobe.conf}}.}}<br />
<br />
=== Troubleshooting KMS ===<br />
<br />
=== Generic problem solution ===<br />
<br />
If your card often crashes when loading the '''radeon''' module, starting your login manager, entering desktop or crashes when you start 3D apps like glxgears you can try if the kernel boot option "pci=nomsi" solves your problems. See https://bugzilla.kernel.org/show_bug.cgi?id=15626 for X200m cards.<br />
<br />
==== Disable KMS ====<br />
<br />
Users should consider disabling kernel mode-setting if encountering kernel panics, distorted framebuffer on boot, no GPU signal, [[Xorg]] refusing to start, Xorg falling back to Mesa software rasterizer (no 3D acceleration) or 'POWER OFF' problem (kernel 2.6.33-2)at shutdown.<br />
<br />
# Add {{Codeline|<nowiki>radeon.modeset=0</nowiki>}} (or {{Codeline|nomodeset}}, if this does not work) to the kernel options line in the bootloader configuration file ({{Filename|/boot/grub/menu.lst}} for [[GRUB]] users). That should work. If you want to remove KMS support from the initramfs, follow the next two steps.<br />
# If {{Codeline|radeon}} was added to the MODULES array in {{Filename|mkinitcpio.conf}} to enable ''early start'', remove it.<br />
# Rebuild the [[initramfs]] with <pre># mkinitcpio -p kernel26</pre><br />
<br />
{{Warning|Catalyst users will likely need to blacklist the {{Codeline|radeon}} module by adding {{Codeline|'''!'''radeon}} to the MODULES array in {{Filename|/etc/rc.conf}}.}}<br />
<br />
Alternatively, module options can be specified in a file within the {{Filename|/etc/modprobe.d}} directory. If using the '''radeon''' module ({{Codeline|<nowiki>lsmod | grep radeon</nowiki>}}) disable KMS by creating a file containing the above code:<br />
<br />
{{File|name=/etc/modprobe.d/radeon.conf|content=options radeon modeset=0}}<br />
<br />
==== Renaming {{Filename|xorg.conf}} ====<br />
<br />
Renaming {{Filename|/etc/X11/xorg.conf}}, which may include options that conflict with KMS, will force Xorg to autodetect hardware with sane defaults. After renaming, '''restart''' Xorg.<br />
<br />
== Performance tuning ==<br />
The following options apply to Section "'''Device'''" in /etc/X11/'''xorg.conf'''.<br />
<br />
=== Tuning performance with xf86-video-ati ===<br />
By design, xf86-video-ati runs at AGP 1x speed. It is generally safe to modify this. If you notice hangs, try reducing the value or removing the line entirely (you can use values 1, 2, 4, 8).<br />
Option "AGPMode" "4"<br />
<br />
'''ColorTiling''' is completely safe to enable and supposedly is enabled by default. People have noticed a performance increase when enabled via xorg.conf.<br />
Option "ColorTiling" "on"<br />
<br />
'''Acceleration architecture'''; this will work only on '''newer''' cards. If you enable this and then can't get back into X, remove it.<br />
Option "AccelMethod" "EXA"<br />
<br />
'''Page Flip''' is generally safe to enable. This would mostly be used on older cards, as enabling this would disable EXA. With recent drivers can be used together with EXA.<br />
Option "EnablePageFlip" "on" <br />
<br />
'''AGPFastWrite''' will enable fast writes for AGP cards. This one can be problematic, so be prepared to remove it if you can't get into X.<br />
Option "AGPFastWrite" "yes"<br />
<br />
'''EXAVSync ''' option attempts to avoid tearing by stalling the engine until the display controller has passed the destination region. It reduces tearing at the cost of performance and has been know to cause instability on some chips.<br />
Really useful when enabling Xv overlay on videos on a 3D accelerated desktop. It is not necessary when KMS (thus DRI2 acceleration) is enabled.<br />
<br />
Option "EXAVSync" "yes"<br />
<br />
See an example Device Section in xorg.conf:<br />
<pre><br />
Section "Device"<br />
Identifier "My Graphics Card"<br />
Driver "radeon"<br />
Option "DRI" "on" <br />
Option "DynamicPM" "on" # Dynamic powersaving.<br />
Option "ClockGating" "on" # Assisting option for powersaving.<br />
Option "AccelMethod" "EXA" # EXA should fit most cases.<br />
Option "EXAVSync" "on" # EXAVSync is explained above.<br />
Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.<br />
Option "ScalerWidth" "2048" # That should fix some very rare bugs.<br />
Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.<br />
Option "RenderAccel" "on" # Optional. It should be enabled by default.<br />
Option "AccelDFS" "on" #Optional. See the man page.<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
</pre><br />
<br />
<br />
'''See the manpage for more configuration options.'''<br />
<code>man radeon</code><br />
<br />
A fine tool to try is [http://aur.archlinux.org/packages.php?do_Details=1&ID=2994 driconf]. It will allow you to modify several settings, like vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).<br />
<br />
=== Tuning performance with xf86-video-radeonhd ===<br />
TODO<br />
<br />
== Powersaving ==<br />
<br />
The powersaving part is totally different with and without KMS.<br />
<br />
=== With KMS enabled ===<br />
<br />
With the radeon driver powersaving isn't enabled by default. And considering that the stock kernel don't offer sysfs option for doing it, you can try two things:<br />
<br />
1. Try adding radeon.dynpm=1 to the kernel parameters (if using the stock kernel).<br />
<br />
2. Use the [radeon] repo:<br />
<br />
# For x86_64<br />
[radeon]<br />
Server = http://gtklocker.tiven.org/radeon-repo/x86_64/<br />
<br />
# For i686<br />
[radeon]<br />
Server = http://gtklocker.tiven.org/radeon-repo/i686/<br />
<br />
And try adjusting /sys/class/drm/card0/device/power_profile. There are three profiles available: low, high, dynpm.<br />
<br />
Low will always force the GPU to run at low levels. High will force it to run at full power, and dynpm will select between low and high depending on the GPU usage.<br />
<br />
You can try a profile with <br />
echo profile > /sys/class/drm/card0/device/power_profile<br />
and when you find something that fits your needs, you can add it to /etc/rc.local, so it's executed at system startup and it becomes permanent.<br />
<br />
=== Without KMS ===<br />
<br />
In your xorg.conf file, add 2 lines to "Device" Section:<br />
Option "DynamicPM" "on"<br />
Option "ClockGating" "on"<br />
<br />
If the two options are enabled successfully, you will see following lines in /var/log/Xorg.0.log:<br />
<br />
(**) RADEON(0): Option "ClockGating" "on"<br />
(**) RADEON(0): Option "DynamicPM" "on"<br />
<br />
Static power management enable success<br />
(II) RADEON(0): Dynamic Clock Gating Enabled<br />
(II) RADEON(0): Dynamic Power Management Enabled<br />
<br />
If you desire low power cost, you can add an extra line to "Device" Section of xorg.conf:<br />
Option "ForceLowPowerMode" "on"<br />
<br />
== TV out ==<br />
Since August 2007, there is TV-out support for all Radeons with integrated TV-out.<br />
<br />
It is somewhat limited for now, it doesn't always autodetect the output correctly and only NTSC mode works.<br />
<br />
First, check that you have an S-video output: <code>xrandr</code> should give you something like<br />
Screen 0: minimum 320x200, current 1024x768, maximum 1280x1200<br />
...<br />
S-video disconnected (normal left inverted right x axis y axis)<br />
<br />
Now we should tell Xorg that it is actually connected (it ''is'', right?)<br />
xrandr --output S-video --set load_detection 1<br />
<br />
Setting tv standard to use:<br />
xrandr --output S-video --set tv_standard ntsc<br />
<br />
Adding a mode for it (currently it supports only 800x600):<br />
xrandr --addmode S-video 800x600<br />
<br />
I'll go for a clone mode:<br />
xrandr --output S-video --same-as VGA-0<br />
<br />
So far so good. Now let's try to see what we have:<br />
xrandr --output S-video --mode 800x600<br />
<br />
At this point you should see a 800x600 version of your desktop on your TV.<br />
<br />
To disable the output, do<br />
xrandr --output S-video --off<br />
<br />
Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.<br />
<br />
To send the output to the TV, I do<br />
xvattr -a XV_CRTC -v 1<br />
<br />
{{Note| you need to install '''xvattr''' from [[AUR]] to execute this command.}}<br />
<br />
To switch back to my monitor, I change this to <code>0</code>. <code>-1</code> is used for automatic switching in dualhead setups.<br />
<br />
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg config file.<br />
<br />
== HDMI with sound ==<br />
Given that your hardware supports it, and you have installed '''xf86-video-radeonhd''' (note: The driver '''xf86-video-ati''' will soon get HDMI support.) you can insert the following into xorg.conf to enable HDMI with sound:<br />
Section "Device"<br />
# ...<br />
Option "Audio" "on"<br />
Option "HDMI" "all"<br />
EndSection<br />
<br />
Restart X when you have done this, try to see if there is sound transmitted to TV via HDMI cable.<br />
# Connect your PC to the TV via HDMI cable (duh).<br />
# Use xrandr to get picture to the TV. Ex: <code>xrandr --output DVI-D_1 --mode 1280x768 --right-of PANEL</code>. Simply typing <code>xrandr</code> will give you a list of your valid outputs.<br />
# Run <code>aplay -l</code> to get the list of your sound devices. Find HDMI and note the card number and corresponding device number. Example of what you want to see: <code>card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]</code><br />
# Try sending sound to this device: <code>aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav</code>. Be sure to change plughw:z,y to match your hardware number found with last command. You should be able to hear the test sound from your TV.<br />
<br />
=== Note on RV730 and RV710 ===<br />
<br />
'''xf86-video-radeonhd''' does not support yet audio through HDMI for these chipsets, but work is in progress.<br />
<br />
== Troubleshooting ==<br />
<br />
=== I encounter artifacts when logging into my DE or WM ===<br />
<br />
If you encounter artifacts, first try starting X without {{Filename|/etc/X11/xorg.conf}}. Recent versions of Xorg are capable of reliable auto-detection and auto-configuration for most use cases. Outdated or improperly configured {{Filename|xorg.conf}} files are known to cause trouble.<br />
<br />
In order to run without a configuration tile, it is recommended that the <tt>xorg-input-drivers</tt> package group be installed.<br />
<br />
Artifacts may also be related to [[kernel mode setting]]. Consider [[#Disable KMS|disabling KMS]].<br />
<br />
=== I have switched from catalyst to radeonhd or radeon and some things don't work ===<br />
<br />
First of all, don't panic. Uninstall catalyst, install xf86-video-radeonhd or xf86-video-ati and then '''''reboot'''''.<br />
<br />
Make sure you are not using the xorg.conf generated by catalyst. Your original should have been backed up and you can recall it:<br />
cp /etc/X11/xorg.conf.original-0 /etc/X11/xorg.conf<br />
<br />
Otherwise, stop your graphical server if running, and in a tty, type as root:<br />
Xorg -configure<br />
mv xorg.conf.new /etc/X11/xorg.conf<br />
and make sure you put the required options.<br />
<br />
If it still doesn't solve your problem, know that apparently catalyst has the bad idea to replace Xorg files with symbolic links pointing to its own files. The easiest at this point is to uninstall all catalyst stuff (just to be on the safe side) and then to reinstall xorg, libgl, ati-dri and xf86-video-radeonhd or xf86-video-ati.<br />
<br />
If it still doesn't work, then have a look into the forum, your problem might be a configuration issue.<br />
<br />
{{Note| When you switch to '''xf86-video-ati''' or '''xf86-video-radeonhd''', remember that you can login without xorg.conf as well (without problems in most cases), since Xorg can autodetect your settings. So '''xorg.conf''' is optional.}}<br />
<br />
=== I have installed a free driver and my card is painfully slow ===<br />
<br />
Some cards can be installed by default trying to use [[ATI#AMD/Ati cards and kernel mode-setting (KMS)|KMS]]. You can check whether this is your case running:<br />
dmesg | egrep "drm|radeon"<br />
<br />
This command might show something ''like'' this, meaning it is trying to default to KMS:<br />
[drm] radeon default to kernel modesetting.<br />
...<br />
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL<br />
<br />
If your card is not supported by KMS (anything older than r100), then you can [[ATI#Disable KMS|disable KMS]]. This should fix the problem.<br />
<br />
If you're getting and error message in dmesg like this:<br />
platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin<br />
r600_cp: Failed to load firmware "radeon/R600_rlc.bin"<br />
[drm:r600_startup] *ERROR* Failed to load firmware!<br />
radeon 0000:01:00.0: disabling GPU acceleration<br />
Install linux-firmware (currently in testing) or linux-firmware-git from [http://aur.archlinux.org/packages.php?ID=37306 AUR].</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=User:Gtklocker&diff=108447User:Gtklocker2010-06-10T09:08:22Z<p>Gtklocker: Created page with '''I'll start putting content on this :)'''</p>
<hr />
<div>''I'll start putting content on this :)''</div>Gtklockerhttps://wiki.archlinux.org/index.php?title=User:Flamelab&diff=108446User:Flamelab2010-06-10T09:06:26Z<p>Gtklocker: /* Using xinitrc */</p>
<hr />
<div>'''''KDE 4.5 DRAFT!<br />
'''''<br />
<br />
<br />
<br />
[[Category:Desktop environments (English)]]<br />
[[Category:HOWTOs (English)]]<br />
{{i18n|KDE}}<br />
{{Article summary start}}<br />
{{Article summary text|KDE is a full featured desktop environment known for its well integrated applications, like Konqueror, Dolphin, Plasma, KWrite and Konsole.}}<br />
{{Article summary end}}<br />
==KDE 4.5 Arch Linux Notes==<br />
<br />
'''KDE 4.5''' Software Compilation is the current major release of KDE that includes a number of improvements and bug fixes. The new Arch package set for KDE makes it possible to only install those applications you like.''<br />
<br />
Important features in short:<br />
* '''Split packages'''; for more Information see [[KDE_Packages|KDE Packages]] and [[DeveloperWiki:Splitting_KDE|Splitting KDE]].<br />
* Qt uses the '''Gstreamer backend''' for Phonon by default. Other backends like '''phonon-xine''' can be installed optionally.<br />
* Meta packages ensure a smooth upgrade and emulate the old monolith packages for those who prefer them.<br />
<br />
Important hints for upgraders:<br />
* Check if your mirror is '''up to date'''.<br />
* pacman will ask you to replace '''all''' kde packages with kde-meta packages.<br />
* '''Do not force an update'''. If pacman complains about conflicts please '''file a bug report'''.<br />
* You can remove the meta packages and the sub packages you do not need after the update.<br />
* If you do not like split packages just keep using the kde-meta packages.<br />
<br />
:Information about upstream changes are be available [http://kde.org/announcements/4.5 here]<br />
<br />
==Installing KDE 4.5 Software Compilation==<br />
<br />
=== Installing full KDE SC ===<br />
<br />
To install the entire KDE set, first '''fully upgrade your system''':<br />
<br />
pacman -Syu<br />
<br />
and then:<br />
<br />
pacman -S kde<br />
<br />
{{Warning| In case you encounter dependency problems regarding '''Qt/kdelibs/phonon''' while '''upgrading''' KDE, [http://wiki.archlinux.org/index.php/KDE#Arch_linux_specific_packaging_issues follow this section.] }}<br />
<br />
If you need language files:<br />
<br />
pacman -S kde-l10n-yourlanguagehere<br />
<br />
e.g. kde-l10n-'''de''', for the German language.<br />
<br />
{{Note| KDE 4.x is '''modular'''; you can install your preferred KDE applications without having to install an entire set of packages. See [[KDE Packages]] for more information.}}<br />
<br />
=== Minimal Install ===<br />
<br />
If you want to have a minimal installation of the KDE SC, here is an example:<br />
<br />
pacman -S kdebase-workspace kdebase-konsole<br />
<br />
== Starting KDE ==<br />
<br />
Starting KDE depends on your preferences. Basically there are two ways of starting KDE. Using '''KDM''' or '''xinitrc'''.<br />
<br />
=== Using KDM (KDE Display Manager)===<br />
''It is highly recommended to get familiar with the [http://wiki.archlinux.org/index.php/Display_Manager full article] concerning display managers, before you make any changes. See also [[KDM]] Wiki page.''<br />
<br />
==== Starting KDM as a daemon ====<br />
Add "'''kdm'''" (without the quotes) to deamons array in '''{{Filename|/etc/rc.conf}}'''<br />
<br />
DAEMONS=(dbus hal syslog-ng network netfs crond ... '''kdm''')<br />
<br />
==== Starting KDM through /etc/inittab [''preferable''] ==== <br />
<br />
Edit '''{{Filename|/etc/inittab}}''' and comment out:<br />
#id:3:initdefault:<br />
<br />
[...]<br />
<br />
#x:5:respawn:/usr/bin/xdm -nodaemon<br />
<br />
Then uncomment:<br />
<br />
id:5:initdefault:<br />
<br />
[...]<br />
<br />
x:5:respawn:/usr/bin/kdm -nodaemon<br />
<br />
{{Note| In both methods KDM loads Xorg automatically.}}<br />
<br />
===Using xinitrc===<br />
''The meaning and usage of '''xinitrc''' is very well described [http://wiki.archlinux.org/index.php/Xinitrc here].<br />
<br />
Edit '''{{Filename|/home/}}'''{{Filename|''your-username''}}'''{{Filename|/.xinitrc}}'''. Then uncomment:<br />
exec startkde <br />
After a reboot or/and login, each execution of Xorg ('''startx''' or '''xinit''') will start KDE automatically.<br />
<br />
'''Warning''': By doing this you won't have restart/shutdown functions on your KDE menu.<br />
<br />
{{Note| If you want to start Xorg at boot, please read [[Start X at boot]] article.}}<br />
<br />
==Configuring==<br />
<br />
{{Note| Configuring KDE is primarily done in ''''System Settings''''. There are also a few other options available for the desktop with 'Desktop Settings' when you right click the desktop.}}<br />
<br />
For other personalization options not covered below such as activities, different wallpapers on one cube, etc please refer to the [[Plasma]] wiki page.<br />
<br />
===Personalization===<br />
<br />
How to set up the KDE desktop to your personal style; use different Plasma themes, window decorations and icon themes. <br />
<br />
====What is Plasma?====<br />
<br />
[[Plasma]] is a desktop integration technology that provides many functions from displaying the wallpaper to adding widgets to the desktop.<br />
<br />
=====Plasma themes=====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=76&PHPSESSID=bba0ae5354c7818b519687ebf5badf0e Plasma themes] can be installed through the Desktop Settings control panel. If you like to have them installed system-wide, themes can be found in both the official repositories and [http://aur.archlinux.org/packages.php?O=0&K=plasmatheme&do_Search=Go AUR].<br />
<br />
====Window Decorations====<br />
<br />
[http://kde-look.org/index.php?xcontentmode=75 Window decorations] can be changed in the '''System Settings > Application Appearance > Style''' control panel and some are available on [http://aur.archlinux.org/packages.php?O=0&K=kdestyle&do_Search=Go&PP=25&SO=d&SB=v AUR].<br />
<br />
====KDE 4 Theme Integration with GTK Applications====<br />
<br />
<br />
To better integrate GTK and KDE 4 themes, you can use '''QtCurve'''.<br />
<br />
pacman -S qtcurve-gtk2 qtcurve-kde4<br />
<br />
Or you can download a GTK theme that matches your version of KDE [http://kde-look.org/content/show.php?content=103741 here]. This theme comes closer to the original Oxygen and is updated frequently.<br />
<br />
=====Automatic procedure=====<br />
<br />
To change the GTK theme to QtCurve or something else a few applications are available:<br />
<br />
pacman -S lxappearance<br />
pacman -S gtk-theme-switch2<br />
pacman -S gtk-chtheme<br />
<br />
Then change the theme of your choice in the respective application:<br />
<br />
lxappearance<br />
gtk-theme-switch2<br />
gtk-chtheme<br />
<br />
=====Manual procedure=====<br />
<br />
To manually change the GTK theme to QtCurve, you need to create the file {{Filename|~/.gtkrc-2.0-kde4}} with the following content:<br />
<br />
include "/usr/share/themes/QtCurve/gtk-2.0/gtkrc"<br />
include "/etc/gtk-2.0/gtkrc"<br />
<br />
style "user-font"<br />
{<br />
font_name="Sans Serif"<br />
}<br />
widget_class "*" style "user-font"<br />
<br />
gtk-theme-name="QtCurve"<br />
<br />
Then you need to create the symbolic link {{Filename|~/.gtkrc-2.0}}:<br />
<br />
ln -s .gtkrc-2.0-kde4 .gtkrc-2.0<br />
<br />
If you want also specify a font, you can add (and adapt) the following line to the file:<br />
<br />
gtk-font-name="Sans Serif 9"<br />
<br />
=====Icons=====<br />
<br />
If you're using Oxygen icons and want a consistent look in GTK open/save dialogs, you can install an [http://aur.archlinux.org/packages.php?O=0&K=oxygenrefit2-icon-theme&do_Search=Go oxygenrefit2] icon theme from AUR and set it as your GTK icon theme. Add the theme to the {{Filename|~/.gtkrc-2.0}} file or you can use lxappearance and set it.<br />
<br />
gtk-icon-theme-name="OxygenRefit2"<br />
<br />
There are also a couple GTK themes built on the [http://aur.archlinux.org/packages.php?ID=24329 gtk-kde42-oxygen-theme Oxygen style] that can also do this.<br />
<br />
====Icon Themes====<br />
<br />
Not many full system icons themes are available for KDE 4. You can open up '''System Settings > Application Appearance > Icons''' and browse for new ones or install them manually. Many of them can be found on [http://www.kde-look.org/ kde-look.org].<br />
<br />
=====Arch Linux Logo Icon in Kicker menu=====<br />
<br />
Right-Click on the Kicker menu button, press "'''Application launcher settings'''" and then press the icon on the '''right'''. Then you may choose Arch Linux icon or any other icon that will replace the default one.<br />
<br />
====Plasmoids====<br />
<br />
KDE 4 supports plasmoids (aka plasma applets, and widgets). These are also available in the [http://aur.archlinux.org/packages.php?O=0&K=plasmoid&do_Search=Go&PP=25&SO=d&SB=v repositories] or you can find more on [http://www.kde-look.org/ kde-look.org].<br />
<br />
====Fonts====<br />
<br />
If you have personally set up how your [[Fonts]] render, be aware that System Settings may alter their appearance. When you go '''System Settings > Application Appearance > Fonts''' System Settings will likely alter your font configuration file ({{Filename|fonts.conf}}). There is no way to prevent this but if you set the values to match your {{Filename|fonts.conf}} file the expected font rendering will return (it will require you to restart your application or in a few cases for you to have to restart your desktop). Note too that Gnomes' Font Preferences will also do this if you use both desktop environments.<br />
<br />
=== Networking/Printing ===<br />
<br />
NetworkManager support has been added in KDE 4.5 SC. See [[Networkmanager#KDE4|NetworkManager]] for more information.<br />
<br />
===Samba/Windows support===<br />
<br />
If you want to have access to Windows services:<br />
<br />
pacman -S samba<br />
<br />
You may then configure your Samba shares through <br />
<br />
System Settings > Sharing > Samba<br />
<br />
<br />
===Powersaving===<br />
<br />
KDE has integrated Powersaving service called "'''Powerdevil Power Management'''" that may adjust the powersaving profile of the system or/and the brightness of the screen (if supported).<br />
<br />
==== How to enable generic powersaving ====<br />
<br />
Navigate to Systemsettings > Power Management<br />
In Profile Management, in "When AC adaptor is plugged in" (or the battery<br />
option) choose "Powersave"<br />
In "Edit Profiles" > "Powersave", tick the "Enable System power saving", and<br />
then press apply.<br />
<br />
==== How to enable Cpufreq based powersaving ====<br />
<br />
Since KDE 4.5, [http://lists.kde.org/?l=kde-devel&m=126800277431817&w=2 Powerdevil doesn't hangle CPU power schemes through Cpufreq]. CPU is being used by using the hardware or/and kernel "'''ondemand'''" governor power scheme and that's the official way to have the system's power management handled. That may not be suitable for everyone.<br />
<br />
Cpufreq is accessible through the '''Solid Device Framework''', though.<br />
<br />
So in order to do that, follow these steps:<br />
<br />
1. You need to create a script for every Cpufreq governor you want to be used. In this example, you will now create a script to enable the powersaving governor.<br />
<br />
Create a script in /usr/bin<br />
<br />
# touch /usr/bin/kde-cpufreq-powersave<br />
<br />
Add these in the script<br />
<br />
#!/bin/bash<br />
solid-powermanagement set cpufreq powersave<br />
<br />
Make it executable<br />
<br />
# chmod +x /usr/bin/kde-cpufreq-powersave<br />
<br />
2. Install cpufrequtils<br />
<br />
pacman -S cpufrequtils<br />
<br />
and make sure you have your CPU's cpufreq module loaded. For more information on this, visit [[Cpufreq|this article]].<br />
<br />
3. Then, in '''System Settings > Power Management''', go to "Edit Profiles" > "Powersave", and make sure that "Enable System power saving" is enabled.<br />
<br />
After that, press the file dialog button next to the phrase "When loading profile execute" and choose the script you have just created. Now, each time you choose the Powersaving profile through Powerdevil, Cpufreq will force the powersaving governor.<br />
<br />
You can do the same for other profiles and governors.<br />
<br />
==System Administration==<br />
<br />
=== How to set keyboard layout in order switch language inputs ? ===<br />
<br />
In order to do that, navigate to <br />
<br />
System Settings > Input Devices > Keyboard<br />
<br />
There you may choose your keyboard model at first.<br />
<br />
{{Note| It is preferable that, if you use Evdev, that means Xorg automatic configuration for keyboards, you should choose "Evdev-managed keyboard".}}<br />
<br />
In the "'''Layouts'''" tab, you choose the languages you may want to use by pressing the "Add Layout" button and therefore the variant and the language.<br />
<br />
In the "'''Advanced'''" tab, you can choose the keyboard combination you want in order to change the layouts in the "Key(s) to change layout" sub-menu.<br />
<br />
=== How to terminate Xorg-server through KDE system settings ? ===<br />
<br />
Navigate to <br />
<br />
System Settings > Input Devices > Keyboard > Advanced (tab) > "Key Sequence to terminate X server" submenu<br />
<br />
and tick the box.<br />
<br />
===Akonadi and external MySQL-Server===<br />
<br />
As of December 2009, akonadi's configuration panel''' does not offer the option to connect to an external MySQL-server via TCP'''. You can however enable this via its configuration file (it's located within ${HOME}/.config/akonadi, the file is called akonadiserverrc). After you've stopped akonadi from the command line (with ''akonadictl stop'') Open the file with your favorite editor, and edit it like so:<br />
<br />
[QMYSQL]<br />
Name=${DBNAME}<br />
User=${USER}<br />
Password=${YOUR_PASSWORD_FOR_THE_USER}<br />
Options=<br />
ServerPath=/usr/sbin/mysqld<br />
StartServer=false<br />
Host=${THE_IP_WHERE_MYSQL_RUNS}<br />
Port=3306<br />
<br />
(of course, substitute your values for variables here)<br />
<br />
Test your setup from the command line (''akonadictl start''). If it starts, you succeeded and akonadi will now connect to MySQL via TCP. stop it once more, and go to system settings -> akonadi configuration (on the "Advanced" tab) and click "start" on the "Akonadi Server configuration" tab to restart akonadi. Alternatively, restart KDE.<br />
<br />
==Desktop Search and Semantic Desktop==<br />
<br />
===Nepomuk===<br />
<br />
From Wikipedia:<br />
''<br />
:NEPOMUK-KDE is featured as one of the newer technologies in KDE 4. It uses the RDF store Soprano and, on a technical level, :allows associating metadata to various items present on a normal user's desktop such as files, bookmarks, e-mails, and :calendar entries. Metadata can be arbitrary RDF; as of KDE 4, tagging is the most user-visible metadata application.'' <br />
<br />
Nepomuk is enabled by default. Nepomuk can be turned on and off in<br />
<br />
System Settings > Desktop Search<br />
<br />
Visit [http://en.wikipedia.org/wiki/NEPOMUK_(framework) this Wikipedia article] for more information.<br />
See [http://lwn.net/Articles/358148/ here], [http://www.well.com/~doctorow/metacrap.htm here] and [http://tech.slashdot.org/article.pl?sid=08/12/16/1546219 here] for additional information.<br />
<br />
===Strigi Search===<br />
<br />
KDE4 has '''Strigi''' for file indexing. It is located under '''Desktop Search''', like Nepomuk. It can be turned on only if Nepomuk is turned on as well.<br />
<br />
Strigi indexes your files and helps you find them easily after by just pressing <br />
<br />
{{Keypress|Alt}} + {{Keypress|F2}}<br />
<br />
and typing what you want to find.<br />
<br />
'''Nepomuk/Strigi''' search is also integrated into ''Dolphin''. By default, Dolphin has a search bar on top-right where you may type what you want to be found from Strigi's index. <br />
<br />
{{Note | Strigi has implications for resource usage on your computer - CPU, memory, disk access, disk space, battery life. If Strigi is too resource-hungry for you, you can turn it off in "'''System Settings > Desktop Search'''". }}<br />
<br />
Strigi index folders can be configured in "Advanced" tab.<br />
<br />
==KDM (KDE Desktop Manager)==<br />
<br />
===KDM Xserver file===<br />
An example configuration for KDM can be found at '''/usr/share/config/kdm/kdmrc'''. See '''/usr/share/doc/HTML/en/kdm/kdmrc-ref.docbook''' for all options.<br />
<br />
===Configure KDM as root===<br />
<br />
You cannot configure KDM settings when launching System Settings as user. In order to do that, press<br />
<br />
{{Keypress|Alt}} + {{Keypress|F2}}<br />
<br />
and type<br />
<br />
kdesu systemsettings<br />
<br />
In the pop-up kdesu window, enter your root password and wait for System Settings to be launched.<br />
<br />
{{Note| Since you have launched it as root, be careful when changing your settings. All settings configuration in root-launched System Settings are saved under /root/.kde4 and not under ~/.kde4 (your home location).}}<br />
<br />
In the System Settings window, go to Security.<br />
<br />
==Phonon==<br />
<br />
===What is Phonon ?===<br />
<br />
''Phonon is the multimedia API for KDE 4. Phonon was created to allow KDE 4 to be independent of any single multimedia framework such as GStreamer or xine and to provide a stable API for KDE 4's lifetime. It was done for various reasons: to create a simple KDE/Qt style multimedia API, to better support native multimedia frameworks on Windows and Mac OS X, and to fix problems of frameworks becoming unmaintained or having API or ABI instability.<br />
''<br />
<br />
from Wikipedia.<br />
<br />
===Which backend should I choose ?===<br />
<br />
KDE4 on Arch Linux has '''Gstreamer''' backend for Phonon. But there are more backends as well. You could use Xine ( [http://www.archlinux.org/packages/?q=phonon phonon-xine] ) or VLC ( [http://aur.archlinux.org/packages.php?ID=29113 phonon-vlc-svn] ).<br />
<br />
==Troubleshooting==<br />
<br />
===KHotkeys issue===<br />
<br />
Ιf '''khotkeys''' does not work, make sure you have a fully updated system first.<br />
<br />
You can also create ~/.kde4/Autostart/reloadkhotkeys.sh with contents <br />
#!/bin/bash<br />
(sleep 3 && qdbus org.kde.kded /modules/khotkeys reread_configuration) &<br />
and then do a<br />
chmod u+x ~/.kde4/Autostart/reloadkhotkeys.sh<br />
then logout & login.<br />
<br />
===Enabling thumbnails under Konqueror and Dolphin file managers===<br />
<br />
For thumbnails of videos in konqueror and dolphin:<br />
<br />
pacman -S kdemultimedia-mplayerthumbs<br />
<br />
===First login on KDE is slow===<br />
<br />
The first login takes a while; no need to worry. KDE is creating all the proper configuration files under '''~/.kde4''' in order to start.<br />
<br />
===I encounter problems with automounting (or) KDE behaves strangely for no apparent reason===<br />
<br />
====Possible HAL problem====<br />
<br />
=====HAL not installed/not running=====<br />
<br />
It is possible that you have not installed HAL yet.<br />
<br />
Install HAL<br />
<br />
pacman -S hal<br />
<br />
if it is not already installed and then add it to the DAEMONS array in '''/etc/rc.conf''' for full media functionality.<br />
<br />
=====Consolekit session not running=====<br />
<br />
'''ck-launch-session''' command attaches a consolekit session to the X session that is going to run, and it is needed by '''HAL'''.<br />
<br />
If you are starting KDE with '''startx''' try adding <code>ck-launch-session</code> to the '''.xinitrc''',<br />
as so:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
# exec gnome-session<br />
exec ck-launch-session startkde<br />
# exec startxfce4<br />
# ...or the Window Manager of your choice<br />
<br />
This is done automatically with KDM. <br />
{{Tip|This should also clear up any power (i.e. suspend to RAM/Disk) issues you may also be having.}}<br />
<br />
==== Possible previous KDE4 faulty settings ====<br />
<br />
It may be possible that some previous KDE4 settings in {{Filename|~/.kde4}} may be configured in a wrong way (by an application, by the user etc). If you cannot find any way to solve the problem by editing/configuring/deleting/adding settings in {{Filename|~/.kde4}}, [[KDE#I_want_a_fresh_installation_of_KDE_for_my_system._What_should_I_do_.3F|'''delete''']] the whole directory or just {{Filename|~/.kde4/share/config}} and restart KDE.<br />
<br />
=== Suspend to Disk/Ram not working ===<br />
<br />
If suspend to disk/ram does not work the be sure hal is running, also make sure you are in the power group (remember to logout)<br />
<br />
Also, if you are starting KDE with startx try adding ck-launch-session to the .xinitrc,<br />
as so:<br />
<br />
#!/bin/sh<br />
#<br />
# ~/.xinitrc<br />
#<br />
# Executed by startx (run your window manager from here)<br />
# exec gnome-session<br />
exec ck-launch-session startkde<br />
# exec startxfce4<br />
# ...or the Window Manager of your choice<br />
<br />
This is done automatically with kdm.<br />
<br />
===GPG and SSH===<br />
To disable gpg-agent and/or ssh-agent in KDE sessions, edit <code>/etc/kde/env/agent-startup.sh</code> and <code>/etc/kde/shutdown/agent-shutdown.sh</code>.<br />
<br />
=== Graphics' related issues ===<br />
<br />
==== Low 2D desktop performance (or) Artifacts appear when on 2D ====<br />
<br />
===== Possible driver problem =====<br />
<br />
Make sure you have the proper driver for your card installed, so that your desktop is at least 2D accelerated. Follow these articles for more information: [[ATI]], [[NVIDIA]], [[Intel]] for more information, in order to make sure that everything is all right. <br />
<br />
The open source ATI and Intel drivers and the proprietary Nvidia driver should provide the best 2D acceleration.<br />
<br />
==== Konsole is slow in applications like vim ====<br />
This is a problem that is caused by slow glyph rendering. You can solve this by switching to a scalable font like Bitstream Vera Sans Mono.<br />
<br />
==== Low 3D desktop performance====<br />
<br />
KDE begins with desktop effects enabled. Older cards may be insufficient for 3D desktop acceleration. You can disable desktop effects in <br />
<br />
System Settings > Desktop <br />
<br />
or you can toggle desktop effects with <br />
{{Keypress|Alt}} + {{Keypress|Shift}} + {{Keypress|F12}}<br />
<br />
<br />
{{Note| You may encounter such problems with 3D desktop performance even when using a more powerful graphics card, but using catalyst proprietary driver (fglrx). This driver is known for having issues with 3D acceleration. Visit [[ATI|the ATi Wiki page]] for more troubleshooting.}}<br />
<br />
===Sound problems under KDE===<br />
====ALSA related problems====<br />
<br />
{{Note| First make sure you have '''alsa-lib''' and '''alsa-utils''' installed.}}<br />
<br />
====="Falling back to default" messages when trying to listen to any sound in KDE=====<br />
<br />
When you encounter such messages:<br />
<br />
:The audio playback device ''<name-of-the-sound-device>'' does not work.<br />
:Falling back to default<br />
<br />
Go to<br />
<br />
System Settings > Audio & Video<br />
<br />
and set the device named "'''default'''" above all the other devices in each box you see.<br />
<br />
=====I cannot play mp3 files when having Gstreamer backend in Qt Phonon=====<br />
<br />
That can be solved by installing gstreamer0.10-plugins<br />
<br />
pacman -S gstreamer0.10-plugins<br />
<br />
You can also change the backend used by Phonon, by installing the phonon-xine<br />
<br />
pacman -S phonon-xine<br />
<br />
if you encounter problems that are not solved after installing gstreamer plugins. Then choose Xine in<br />
<br />
System Settings > Audio & Video > Backend (tab)<br />
<br />
(it may have been autoselected after installing phonon-xine)<br />
<br />
=====Amarok "waits" before playing any track=====<br />
<br />
If you have encountered this error, the problem is backend specific. In order to solve this problem, change Amarok's backend from '''gstreamer''' to '''xine'''.<br />
<br />
====OSS4 related problems====<br />
<br />
=====I have OSS4 installed, but I have problems with Kmix etc=====<br />
<br />
You should use the Xine Phonon backend which is suitable for use along with OSS4.<br />
<br />
=== Arch linux specific packaging issues ===<br />
<br />
Due to some changes on the packages or pacman problems, there could be some problems during upgrading. Please read the sections below, if you have a problem.<br />
<br />
==== Qt updating problem during upgrading from KDE SC 4.3 (or previous version) to KDE SC 4.5 ====<br />
<br />
If you encounter this error message during upgrading:<br />
<br />
error: failed to prepare transaction (could not satisfy dependencies)<br />
:: kdelibs: requires phonon<br />
<br />
First, you need to update Qt, which doesn't provide phonon anymore. <br />
<br />
So in that case:<br />
<br />
pacman -Syy '''--asdeps qt'''<br />
<br />
pacman -Su<br />
<br />
==== Kdepim meta-package is blocking the upgrade. ====<br />
<br />
Due to changes to the KDE meta-packages, there could be a problem with '''kde-meta-kdepim''' meta-package. So, in that case<br />
<br />
pacman -Syy '''--asdeps kdepim-runtime'''<br />
pacman -Su<br />
<br />
===I wanted a minimal installation of KDE. After I installed some packages and logged in KDE, there are no panels===<br />
<br />
If you wanted a minimal installation of KDE, logged in, heard the login sound but nothing else happened, you may not have installed the Plasma binaries. These are included in<br />
<br />
kdebase-workspace<br />
<br />
Install this package and restart Xorg.<br />
<br />
===I want a fresh installation of KDE for my system. What should I do ?===<br />
<br />
If you really want that, just rename the settings directory of KDE (just in case you'll need a backup later):<br />
<br />
mv ~/.kde4 ~/.kde4-backup<br />
<br />
===Plasma desktop behaves strangely but I do not know what to do===<br />
<br />
Plasma issues are caused mainly by unstable '''plasmoids''' or '''plasma themes'''. First, find which was the last plasmoid or plasma theme you had installed and disable it or even remove it. <br />
<br />
If you cannot find which the problem is, but you do not want all the KDE settings to be lost, do:<br />
<br />
rm -r ~/.kde4/share/config/plasma*<br />
<br />
This command will '''delete all plasma configs''' of your user and when you will relogin into KDE, you will have the '''default''' settings back.<br />
<br />
===Couldn't find MIME type application/octet-stream===<br />
"'''Couldn't find MIME type application/octet-stream'''" can be shown as an alert from KDE after it's updated. <br />
<br />
Can be solved when you create new mime type in KDE Control Center named ''''octet-stream'''' in category ''''application'''' and with the same text (octet-stream) in the description.<br />
<br />
Check contents of '''octet-stream.desktop''' located in {{Filename|~/.kde/share/mimelnk/application}}. Check to see that there is a line that reads '''Hidden=false'''. If Hidden=true you will still get the error message.<br />
<br />
===I encounter a serious lag with bitmap fonts on Konsole===<br />
<br />
That's an issue reported while using KDE 4.x and Nvidia proprietary driver. It's about to be fixed in future Nvidia driver release.<br />
<br />
==Other KDE projects==<br />
===The Chakra Project===<br />
<br />
{{Warning| Chakra Project may soon '''split''' from Arch's main system. You should be informed on Chakra Project's news and devs' decisions on [http://chakra-project.org/ Chakra Project website].}}<br />
<br />
====Split KDE packages====<br />
[http://chakra-project.org/ The Chakra Project] is a community-based modular version of KDE 4 and Live CD project, which includes a number of UI enhancements for KDE 4.x. Visit [http://chakra-project.org/wiki/index.php/Main_Page the Chakra Project Wiki main page] for more information.<br />
<br />
====Chakra Project Arch Live CD====<br />
<br />
The Chakra Project also provides a full featured Live CD, which has the latest stable KDEmod4 packages included.<br />
You may visit [http://chakra-project.org/download-iso.html the Chakra Project Live CD webpage] in order to find more information.<br />
<br />
====Passing from KDEmod to [extra]'s KDE====<br />
<br />
{{Note|You do have instructions for passing from '''[extra]''''s KDE4 to KDEmod4 [http://chakra-project.org/download-kdemod.html here]. }}<br />
<br />
Both flavours of KDE provide the same Desktop Environment, so if you install the one or the other, in the same upstream version, there should not be any problem regarding plasmoids, themes, styles or any KDE related application.<br />
<br />
So, if you want, for any reason, to pass from KDEmod to '''[extra]''''s KDE, do:<br />
<br />
pacman -Rd kdemod<br />
<br />
OR<br />
<br />
pacman -Rd kdemod-uninstall<br />
<br />
and it should be removed, but with the '''-d''' argument, the KDE dependent packages '''are not''' uninstalled, but only the Desktop Environment. But, if you want to '''completelly''' remove any KDEmod specific application/plasmoid/style etc too, do<br />
<br />
pacman -Rcns kdemod<br />
<br />
and then make sure that everything has been uninstalled:<br />
<br />
pacman -Q | grep kde<br />
<br />
{{Note| If you want to use the same KDE specific settings from the previous KDEmod installation, move or rename ~/'''.kdemod4''' to ~/'''.kde4''' }}<br />
<br />
After this, you may have KDEmod uninstalled.<br />
<br />
Then, follow [[KDE#Installing_KDE_4.5|this]].<br />
<br />
===KDE unstable===<br />
====KDEmod testing/unstable====<br />
<br />
You may visit [http://chakra-project.org/repos.html this webpage] and see which repos can you add in''' pacman.conf''' in order to test the KDEmod unstable packages.<br />
<br />
====KDE unstable (snapshot)====<br />
<br />
===== Unofficial kde-unstable =====<br />
<br />
The member '''ProgDan''' has created a repo where he uploads the testing KDE packages when a new '''upstream snapshot''' is out. You may visit [http://bbs.archlinux.org/viewtopic.php?id=76245 this topic] for more information.<br />
<br />
===== Semi-official kde-unstable =====<br />
<br />
When KDE is reaching beta or RC milestone, KDE "unstable" packages are uploaded to the [kde-unstable] repo. <br />
<br />
You may add it by adding:<br />
<br />
[kde-unstable]<br />
Include = /etc/pacman.d/mirrorlist<br />
<br />
in '''{{Filename|/etc/pacman.conf}}'''<br />
<br />
They stay there until KDE is declared stable and passes to [extra].<br />
<br />
Make sure [http://wiki.archlinux.org/index.php/KDE#Distro_and_Upstream_bug_report you make bug reports] if you find any issues.<br />
<br />
Read [http://wiki.archlinux.org/index.php/DeveloperWiki:KDE#Users this section] in the wiki as well.<br />
<br />
===KDE Legacy===<br />
<br />
====Downgrading to KDEmod3 from KDE 4====<br />
For those people who decide that KDE 4 is still not yet "ready" for them, there is a website about how to downgrade to a version of KDE 3.5 called '''kdemod3''':<br />
* [http://chakra-project.org/download-kdemod3.html KDEmod3]<br />
<br />
'''Warning''': There have been issues reported regarding Libjpeg7, that caused KDEmod3 to behave strangely. In order to solve that, install [http://aur.archlinux.org/packages.php?ID=28427 libjpeg6] [http://aur.archlinux.org/packages.php?ID=33795 libpng12 from AUR]. The libs '''libjpeg6''' and '''libpng12''' can be safely installed along side the current libraries. More info [http://chakra-project.org/bbs/viewtopic.php?id=1097 here]<br />
<br />
{{Warning| KDE 3 is no longer maintained and supported by the KDE developers. KDEmod3 is no longer maintained by the Chakra Projects developers. Use it on your own risk, regarding any bugs, performance issues or security risks.}}<br />
<br />
==== Unofficial community repository for KDEmod3 ====<br />
<br />
[http://bbs.archlinux.org/viewtopic.php?id=97612 In this thread] you may find info on a rebuild of the unsupported KDEmod3.<br />
<br />
==Bugs==<br />
===Common bugs===<br />
If you think you found something that seems like bug, please see [[Common_Issues]] and regarding that: KDE 4 config files are usually located at <br />
<br />
~/.kde4/share/config/<br />
<br />
and for app-specific configs <br />
<br />
~/.kde4/share/apps/<br />
<br />
===Distro and Upstream bug report===<br />
It is preferrable that if you find a minor or serious bug, you should visit [http://bugs.archlinux.org the Arch Bug Tracker] or/and [http://bugs.kde.org KDE Bug Tracker] in order to report that. Make sure that you be clear on what you want to report.<br />
<br />
If you have any issue and you write about in on the Arch forums, first make sure that you have '''FULLY''' updated your system using a good sync mirror (check [https://www.archlinux.de/?page=MirrorStatus here]) or try '''reflector'''.<br />
<br />
==External Links==<br />
* [http://www.kde.org KDE Homepage]<br />
* [http://bugs.kde.org KDE Bug Tracker]<br />
* [http://bugs.archlinux.org Arch Linux Bug Tracker]<br />
* [http://websvn.kde.org KDE WebSVN]</div>Gtklocker