https://wiki.archlinux.org/api.php?action=feedcontributions&user=DooMMasteR&feedformat=atomArchWiki - User contributions [en]2024-03-29T11:41:23ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Dell_XPS_13_(9360)&diff=466878Dell XPS 13 (9360)2017-01-27T07:59:06Z<p>DooMMasteR: /* Wireless */ issue description</p>
<hr />
<div>[[Category:Dell]]<br />
[[ja:Dell XPS 13 (9360)]]<br />
{| class="wikitable" style="float: right;"<br />
| '''Device''' || '''Status''' || '''Modules'''<br />
|-<br />
| Video || {{G|Working}} || i915<br />
|-<br />
| Wireless || {{G|Working}} || ath10k<br />
|-<br />
| Bluetooth || {{G|Working}}|| btusb<br />
|-<br />
| Audio || {{G|Working}} || snd_hda_intel<br />
|-<br />
| Touchpad || {{G|Working}} || ?<br />
|-<br />
| Webcam || {{G|Working}} || uvcvideo<br />
|-<br />
| USB-C / Thunderbolt 3 || {{G|Working}} || ?<br />
|-<br />
| Wireless switch || {{G|Working}} || intel_hid<br />
|-<br />
| Function/Multimedia Keys || {{G|Working}} || ?<br />
|}<br />
<br />
The Dell XPS 13 Late 2016 (9360) is the fourth-generation model of the XPS 13 line. The laptop is available since October in both a standard edition with Windows installed as well as a Developer Edition with Ubuntu installed. There is no hardware difference between them. Just like the older versions ([[Dell XPS 13 (9333)]], [[Dell XPS 13 (9343)]]), [[Dell XPS 13 (9350)]]) it is available in different hardware configurations. This fourth gen model includes Intel's Kaby Lake CPU and configurable with up to 16GB LPDDR 1866 MHz RAM and a 1TB PCI SSD. It will now also be available in Rose Gold. Prior to previous information it won't be available with LPDDR 2133 MHz RAM.<br />
<br />
The installation process for Arch on the XPS 13 does not differ from any other PC. For installation help, please see the [[Installation guide]] and [[UEFI]]. This page covers the current status of hardware support on Arch, as well as post-installation recommendations.<br />
<br />
As of kernel 4.5, the Intel Kaby Lake architecture is supported.<br />
<br />
<br />
== Content adaptive brightness control ==<br />
In the XPS 13 the display panels (both FHD and QHD+) come with adaptive brightness embedded in the panel firmware, this "content adaptive brightness control" (usually referred to as CABC or DBC) will adjust the screen brightness depending on the content displayed on the screen and will generally be found undesirable, especially for Linux users who are likely to be switching between dark and light screen content. Dell has issued a fix for this however it is only available to run in Windows and for the QHD+ model of the laptop so this precaution should be taken before installing Linux, the FHD model of the XPS 13 (9360) cannot be fixed. This is not a problem with the panel but rather a problem with the way the panels are configured for the XPS 13, as the same panel exists in the Dell's Latitude 13 7000 series (e7370) FHD model but with CABC disabled. The fix is available directly from [http://www.dell.com/support/home/de/de/debsdt1/Drivers/DriversDetails?driverId=20JWV&fileId=3574543510&osCode=WT64A&productCode=xps-13-9360-laptop&languageCode=ge&categoryId=AP Dell].<br />
<br />
== NVM Express SSD ==<br />
=== NVME Power Saving Patch ===<br />
Andy Lutomirski has released version 4 of his patchset which fixes powersaving for NVME devices in linux. Currently, this patch is not merged into mainline yet. Until it lands in mainline kernel use the AUR package below. <br />
{{App|Linux-nvme|Mainline linux kernel patched with Andy's patch for NVME powersaving APST.|https://github.com/damige/linux-nvme|{{AUR|linux-nvme}}}} (check out [http://linuxnvme.damige.net/] for compiled packages)<br />
<br />
== Video ==<br />
The video should work with the {{ic|i915}} driver of the current {{Pkg|linux}} kernel. Consult [[Intel graphics]] for a detailed installation and configuration guide as well as for [[Intel graphics#Troubleshooting|Troubleshooting]].<br />
<br />
=== Blank screen issue after booting ===<br />
If using "late start" [[KMS]] (the default) and the screen goes blank when loading modules, it may help to add {{ic|i915}} and {{ic|intel_agp}} to the initramfs or using a special [[kernel parameter]]. Consult [[Intel graphics#Blank screen during boot, when "Loading modules"]] for more information about the kernel paramter way and have a look at [[Kernel mode setting#Early KMS start]] for a guide on how to setup the modules for the initramfs.<br />
<br />
== Wireless ==<br />
<br />
The Killer 1535 Wirless Adapter is functional and the ath10k firmware is included in recent linux kernel versions. The connection speed reported by iw is limited to 1-6Mbits/s. However this is just the output being wrong. The real connection speed is not limited to this value.<br />
<br />
Some users are experiencing issues, where the connection is dropped under heavy load but reconnects within a brief moment. This might not be noticed during browsing at all but becomes apparent in online games. There is no know solution so far.<br />
<br />
== Bluetooth ==<br />
<br />
After following the instructions given at [[Bluetooth]] tethering of internet connections via phone works immediately.<br />
<br />
<br />
== Thunderbolt 3 / USB 3.1 ==<br />
<br />
The USB-C port supports Thunderbolt 3, Displayport-over-USB-C and USB power delivery as well as USB 3.1.<br />
<br />
=== Ethernet repeatedly disconnects/reconnects with Dell USB-C adapter (DA200) ===<br />
<br />
Use of a power management package (such as [[TLP]]) may cause the ethernet adapter to repeatedly disconnect and reconnect. If this happens, disable/blacklist USB autosuspend for the ethernet adapter. (On my laptop, this is the device <tt>Bus 004 Device 007: ID 0bda:8153 Realtek Semiconductor Corp</tt> in the output of <tt>lsusb</tt>.)<br />
<br />
Also disabling or reducing power of wifi may help: http://en.community.dell.com/support-forums/network-internet-wireless/f/3324/t/19995423<br />
<br />
== SATA controller ==<br />
When the SATA-controller is set to {{ic|RAID On}} in Bios, the hard disk (at least the SSD) is not recognized. Set to {{ic|Off}} or {{ic|AHCI}} ({{ic|AHCI}} is recommended) before attempting to install Arch.<br />
<br />
== Touchpad ==<br />
The touchpad has no explicit buttons. The buttons are built into the pads surface. There is a small line printed on the pad separating left from right click button. The pad has a '''middle button''' built in! (works with libinput without any configuration): To issue a middle click, simply press on the middle area right between the virtual left and click buttons - so on the small printed separator line.<br />
<br />
=== Remove psmouse errors from dmesg ===<br />
<br />
If {{ic|<nowiki>dmesg | grep -i psmouse</nowiki>}} returns an error, but your touchpad still works, then it might be a good idea to disable {{ic|psmouse}}. First create a config file:<br />
<br />
# nano /etc/modprobe.d/modprobe.conf<br />
<br />
blacklist psmouse<br />
<br />
Then add this file to {{ic|/etc/mkinitcpio.conf}}:<br />
<br />
...<br />
FILES="/etc/modprobe.d/modprobe.conf"<br />
...<br />
<br />
Rebuild your initial ramdisk image (see [[Mkinitcpio#Image creation and activation]]).<br />
<br />
== Touchscreen ==<br />
The touchscreen works without additional configuration. The bug resulting in a disabled touchscreen after resume was fixed with kernel 4.8.5.<br />
<br />
=== Gestures ===<br />
Refer to [[libinput#Gestures]] for information about the current development state and available methods.<br />
<br />
== Keyboard Backlight ==<br />
By default, the keyboard backlight turns off after 10 seconds of inactivity. Some users might find this too short and annoying.<br />
The delay can be increased (or decreased) by editing this file:<br />
/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/stop_timeout<br />
<br />
You can also change the brightness (0-2) by editing the following file. This is identical to pressing F10 on your keyboard:<br />
/sys/devices/platform/dell-laptop/leds/dell\:\:kbd_backlight/brightness<br />
<br />
== Firmware Updates ==<br />
Dell provides firmware updates via {{aur|fwupd}}. See [[Flashing BIOS from Linux#fwupd]]. Please note if you have used a bind mount partition for /boot, you will not be able to use the fwupd utility; Instead format a USB as FAT32 and put the bios update .exe on. Reboot into the one-time-boot menu and update the BIOS flash through there.<br />
<br />
<br />
== Troubleshooting ==<br />
<br />
=== EFISTUB does not boot ===<br />
The BIOS does not pass any boot parameters to the kernel. Use a UEFI [[boot loader]] instead.<br />
<br />
=== Not waking from suspend ===<br />
Update the BIOS to 1.0.7 to patch this issue.<br />
<br />
=== Power Drain after waking from standby ===<br />
<br />
Some users recognised ~2W more power consumption after waking up from standby. Go to the UEFI Firmware Settings (tap the F2 key when the Dell logo appears) and uncheck the 'Enable Thunderbolt Boot Support'. You may use {{Pkg|powertop}} or {{AUR|powerstat-git}} to reproduce and check this behaviour yourself. <br />
<br />
=== Popping Sound on headphones/external speakers ===<br />
Have a look at [[Advanced_Linux_Sound_Architecture/Troubleshooting#Pops_when_starting_and_stopping_playback]] and [[Advanced_Linux_Sound_Architecture/Troubleshooting#Popping_sound_after_resuming_from_suspension]].<br />
<br />
=== Coil Whine ===<br />
<br />
Unfortunately Dell still did not fix this issue and the sound for my model was very loud. The issue seems to be connected to the graphic card. For some users, it is possible to reduce it a lot by activating frame buffer compression "enable_fbc=1" [[Intel graphics#Module-based Powersaving Options]]. The coil whine will then start again under heavy graphic load. For the touchscreen model, this may be very often, due to the high resolution screen. In a similar vein, the display can be run at a lower resolution, again reducing the load on the graphics card.</div>DooMMasteRhttps://wiki.archlinux.org/index.php?title=File_systems&diff=368997File systems2015-04-08T11:16:42Z<p>DooMMasteR: http://en.wikipedia.org/wiki/ExFAT#File_and_cluster_pre-allocation</p>
<hr />
<div>[[Category:File systems]]<br />
[[es:File Systems]]<br />
[[It:File Systems]]<br />
[[ja:ファイルシステム]]<br />
[[pl:File Systems]]<br />
[[zh-cn:File Systems]]<br />
{{Related articles start}}<br />
{{Related|Mount}}<br />
{{Related|Partitioning}}<br />
{{Related articles end}}<br />
<br />
From [[Wikipedia:File system|Wikipedia]]:<br />
:''A file system (or filesystem) is a means to organize data expected to be retained after a program terminates by providing procedures to store, retrieve and update data, as well as manage the available space on the device(s) which contain it. A file system organizes data in an efficient manner and is tuned to the specific characteristics of the device.''<br />
<br />
Individual drive partitions can be setup using one of the many different available filesystems. Each has its own advantages, disadvantages, and unique idiosyncrasies. A brief overview of supported filesystems follows; the links are to wikipedia pages that provide much more information.<br />
<br />
Before being formatted, a drive should be [[Partitioning|partitioned]].<br />
<br />
== Types of file systems ==<br />
<br />
* [[Btrfs]] — Also known as "Better FS", is a '''new filesystem with powerful features similar to Sun/Oracle's excellent ZFS'''. These include snapshots, multi-disk striping and mirroring (software RAID without mdadm), checksums, incremental backup, and on-the-fly compression that can give a significant performance boost as well as save space. Although it has been merged into the mainline kernel, as of April 2014, Btrfs is not considered stable, with an experimental status. Btrfs appears to be the future of GNU/Linux filesystems and is offered as a root filesystem option in all major distribution installers.<br />
* '''exFAT''' — '''Microsoft file system optimized for flash drives'''. Like NTFS, exFAT can pre-allocate disk space for a file by just marking arbitrary space on disk as 'allocated'.<br />
* [[Wikipedia:ext2|ext2]] — '''Second Extended Filesystem''' is an established, mature GNU/Linux filesystem that is very stable. A drawback is that it does not have journaling support or barriers. Lack of journaling can result in data loss in the event of a power failure or system crash. It may also be '''not''' convenient for root ({{ic|/}}) and {{ic|/home}} partitions because file-system checks can take a long time. An ext2 filesystem can be [[Convert_ext2_to_ext3|converted to ext3]].<br />
* [[ext3]] — '''Third Extended Filesystem''' is essentially the ext2 system with journaling support and write barriers. It is backward compatible with ext2, well tested, and extremely stable.<br />
* [[ext4]] — '''Fourth Extended Filesystem''' is a newer filesystem that is also compatible with ext2 and ext3. It provides support for volumes with sizes up to 1 exabyte (i.e. 1,048,576 terabytes) and files sizes up to 16 terabytes. It increases the 32,000 subdirectory limit in ext3 to 64,000. It also offers online defragmentation capability.<br />
* [[F2FS]] — '''Flash-Friendly File System''' is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel. The motivation for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which have been widely being used in computer systems ranging from mobile devices to servers.<br />
* [[JFS]] — IBM's '''Journaled File System''' was the first filesystem to offer journaling. It had many years of development in the IBM AIX® operating system before being ported to GNU/Linux. JFS makes the smallest demand on CPU resources of any GNU/Linux filesystem. It is very fast at formatting, mounting, and filesystem checks (fsck). JFS offers very good all-around performance especially in conjunction with the deadline I/O scheduler. It is not as widely supported as the ext series or ReiserFS, but still very mature and stable.<br />
* [[Wikipedia:NILFS|NILFS2]] — '''New Implementation of a Log-structured File System''' was developed by NTT. It records all data in a continuous log-like format that is only appended to and never overwritten. It is designed to reduce seek times and minimize the type of data loss that occurs after a crash with conventional Linux filesystems.<br />
* [[NTFS]] — '''File system used by Windows'''. NTFS has several technical improvements over FAT and HPFS (High Performance File System), such as improved support for metadata, and the use of advanced data structures to improve performance, reliability, and disk space utilization, plus additional extensions, such as security access control lists (ACL) and file system journaling.<br />
* [[Reiser4]] — '''Successor to the ReiserFS file system''', developed from scratch by Namesys and sponsored by DARPA as well as Linspire, it uses B*-trees in conjunction with the dancing tree balancing approach, in which underpopulated nodes will not be merged until a flush to disk except under memory pressure or when a transaction completes. Such a system also allows Reiser4 to create files and directories without having to waste time and space through fixed blocks.<br />
* [[Wikipedia:ReiserFS|ReiserFS]] — '''Hans Reiser's high-performance journaling FS (v3)''' uses a very interesting method of data throughput based on an unconventional and creative algorithm. ReiserFS is touted as very fast, especially when dealing with many small files. ReiserFS is fast at formatting, yet comparatively slow at mounting. Quite mature and stable. ReiserFSv3 is not being actively developed at this time. Generally regarded as a good choice for {{ic|/var}}.<br />
* [[Wikipedia:File Allocation Table#VFAT|VFAT]] — '''Virtual File Allocation Table''' is technically simple and supported by virtually all existing operating systems. This makes it a useful format for solid-state memory cards and a convenient way to share data between operating systems. VFAT supports long file names.<br />
* [[XFS]] — '''Early journaling filesystem originally developed by Silicon Graphics''' for the IRIX operating system and ported to GNU/Linux. It provides very fast throughput on large files and filesystems and is very fast at formatting and mounting. Comparative benchmark testing has shown it to be slower when dealing with many small files. XFS is very mature and offers online defragmentation capability.<br />
* [[ZFS]] — '''Combined file system and logical volume manager designed by Sun Microsystems'''. The features of ZFS include protection against data corruption, support for high storage capacities, integration of the concepts of filesystem and volume management, snapshots and copy-on-write clones, continuous integrity checking and automatic repair, RAID-Z and native NFSv4 ACLs.<br />
<br />
=== Journaling ===<br />
<br />
All the above filesystems with the exception of ext2, FAT16/32, use [[Wikipedia:Journaling_file_system|journaling]]. Journaling provides fault-resilience by logging changes before they are committed to the filesystem. In the event of a system crash or power failure, such file systems are faster to bring back online and less likely to become corrupted. The logging takes place in a dedicated area of the filesystem.<br />
<br />
Not all journaling techniques are the same. Only ext3 and ext4 offer data-mode journaling, which logs both data and meta-data. Data-mode journaling comes with a speed penalty and is not enabled by default. The other filesystems provide ordered-mode journaling, which only logs meta-data. While all journaling will return a filesystem to a valid state after a crash, data-mode journaling offers the greatest protection against corruption and data loss. There is a compromise in system performance, however, because data-mode journaling does two write operations: first to the journal and then to the disk. The trade-off between system speed and data safety should be considered when choosing the filesystem type.<br />
<br />
=== Arch Linux support ===<br />
<br />
* {{App|btrfs-progs|[[Btrfs]] support.|http://btrfs.wiki.kernel.org/|{{Pkg|btrfs-progs}}}}<br />
* {{App|dosfstools|VFAT support.|http://www.daniel-baumann.ch/software/dosfstools/|{{Pkg|dosfstools}}}}<br />
* {{App|exfat-utils|exFAT support.|http://code.google.com/p/exfat/|{{Pkg|exfat-utils}}}}<br />
* {{App|f2fs-tools|[[F2fs|F2FS]] support.|https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git|{{Pkg|f2fs-tools}}}}<br />
* {{App|e2fsprogs|ext2, [[ext3]], [[ext4]] support.|http://e2fsprogs.sourceforge.net|{{Pkg|e2fsprogs}}}}<br />
* {{App|jfsutils|[[JFS]] support.|http://jfs.sourceforge.net|{{Pkg|jfsutils}}}}<br />
* {{App|nilfs-utils|NILFS support.|http://nilfs.sourceforge.net/|{{Pkg|nilfs-utils}}}}<br />
* {{App|ntfs-3g|[[NTFS]] support.|http://www.tuxera.com/community/ntfs-3g-download/|{{Pkg|ntfs-3g}}}}<br />
* {{App|reiser4progs|[[Reiser4|ReiserFSv4]] support.|http://sourceforge.net/projects/reiser4/|{{AUR|reiser4progs}}}}<br />
* {{App|reiserfsprogs|ReiserFSv3 support.|https://www.kernel.org/|{{Pkg|reiserfsprogs}}}}<br />
* {{App|xfsprogs|[[XFS]] support.|http://oss.sgi.com/projects/xfs/|{{Pkg|xfsprogs}}}}<br />
* {{App|zfs|[[ZFS]] support.|http://zfsonlinux.org/|{{AUR|zfs-git}}}}<br />
<br />
=== FUSE-based file systems ===<br />
<br />
[[Wikipedia:Filesystem in Userspace|Filesystem in Userspace]] (FUSE) is a mechanism for Unix-like operating systems that lets non-privileged users create their own file systems without editing kernel code. This is achieved by running file system code in ''user space'', while the FUSE kernel module provides only a "bridge" to the actual kernel interfaces.<br />
<br />
Some notable FUSE-based file systems:<br />
<br />
{{Poor writing|Some descriptions are really poor, also some packages may not meet the "notable" requirement.}}<br />
<br />
* {{App|acd-fuse|Mount Amazon cloud drives.|https://github.com/handyman5/acd_fuse|{{AUR|acdfuse-git}}}}<br />
* {{App|adbfs-git|Mount an Android device filesystem.|http://collectskin.com/adbfs/|{{AUR|adbfs-git}}}}<br />
* {{App|cddfs|Mount audio CDs.|http://castet.matthieu.free.fr/|{{AUR|cddfs}}}}<br />
* {{App|fuse-exfat|exFAT mount support.|http://code.google.com/p/exfat/|{{Pkg|fuse-exfat}}}}<br />
* {{App|fuseiso|Mount an ISO as a regular user.|http://sourceforge.net/projects/fuseiso/|{{Pkg|fuseiso}}}}<br />
* {{App|wiifuse|Mount a Gamecube or Wii DVD disc image read-only.|http://wiibrew.org/wiki/Wiifuse|{{AUR|wiifuse}}}}<br />
* {{App|xbfuse-git|Mount an Xbox (360) ISO.|http://multimedia.cx/xbfuse/|{{AUR|xbfuse-git}}}}<br />
* {{App|xmlfs|Mount XML files as directory tree.|https://github.com/halhen/xmlfs|{{AUR|xmlfs}}}}<br />
* {{App|zfs-fuse|[[ZFS_on_FUSE|ZFS support via FUSE]].|http://zfs-fuse.net/|{{AUR|zfs-fuse}}}}<br />
<br />
See [[Wikipedia:Filesystem in Userspace#Example uses]] for more.<br />
<br />
== Create a filesystem ==<br />
<br />
{{Note|<br />
* If you want to change the partition layout, see [[Partitioning]].<br />
* If you want to create a swap partition, see [[Swap]].<br />
}}<br />
<br />
Before starting, you need to know which name Linux gave to your device. Hard drives and USB sticks show up as {{ic|/dev/sd''x''}}, where ''x'' is a lowercase letter, while partitions show up as {{ic|/dev/sd''xY''}}, where ''Y'' is a number.<br />
<br />
Usually filesystems are created on a partition, but they can also be created inside of logical containers like [[LVM]], [[RAID]], or [[dm-crypt]].<br />
<br />
To create a new filesystem on a partition, the existing filesystem located on the partition must not be mounted.<br />
<br />
If the partition you want to format contains a mounted filesystem, it will show up in the ''MOUNTPOINT'' column of lsblk.<br />
<br />
$ lsblk<br />
<br />
To unmount it, you can use ''umount'' on the directory where the filesystem was mounted to:<br />
<br />
# umount /mountpoint<br />
<br />
To create a new file system of type ext4 on a partition do:<br />
<br />
{{Warning|After creating a new filesystem, data previously stored on this partition can likely not be recovered. Make a backup of any data you want to keep.}}<br />
<br />
# mkfs.ext4 /dev/''partition''<br />
<br />
Alternatively, you can use {{ic|mkfs}} which is just a unified front-end for the different {{ic|mkfs.''fstype''}} tools.<br />
<br />
# mkfs -t ext4 /dev/''partition''<br />
<br />
== See also ==<br />
<br />
* [[wikipedia:Comparison of file systems]]</div>DooMMasteR