https://wiki.archlinux.org/api.php?action=feedcontributions&user=Nfs&feedformat=atomArchWiki - User contributions [en]2024-03-29T07:17:49ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=USB_flash_installation_medium&diff=498085USB flash installation medium2017-11-23T23:07:33Z<p>Nfs: /* In GNU/Linux */ removed the instruction to create the MBR or GPT which appeared after Mark the partition as active (or "bootable"). This must be done first!</p>
<hr />
<div>[[Category:Getting and installing Arch]]<br />
[[ar:USB flash installation media]]<br />
[[bg:USB flash installation media]]<br />
[[de:Installation von einem USB-Stick]]<br />
[[es:USB flash installation media]]<br />
[[fr:Créer une clef USB avec l'ISO Arch Linux]]<br />
[[it:USB flash installation media]]<br />
[[ja:USB インストールメディア]]<br />
[[ro:Instalare prin USB]]<br />
[[ru:USB flash installation media]]<br />
[[tr:USB ile kurulum]]<br />
[[zh-hans:USB flash installation media]]<br />
[[zh-hant:USB flash installation media]]<br />
{{Related articles start}}<br />
{{Related|CD Burning}}<br />
{{Related|Archiso}}<br />
{{Related|Multiboot USB drive}}<br />
{{Related articles end}}<br />
<br />
This page discusses various multi-platform methods on how to create an Arch Linux Installer USB drive (also referred to as ''"flash drive", "USB stick", "USB key"'', etc) for booting in BIOS and UEFI systems. The result will be a LiveUSB (LiveCD-like) system that can be used for installing Arch Linux, system maintenance or for recovery purposes, and that, because of the nature of [[Wikipedia:SquashFS|SquashFS]], will discard all changes once the computer shuts down.<br />
<br />
If you would like to run a full install of Arch Linux from a USB drive (i.e. with persistent settings), see [[Installing Arch Linux on a USB key]]. If you would like to use your bootable Arch Linux USB stick as a rescue USB, see [[Change root]].<br />
<br />
== BIOS and UEFI bootable USB ==<br />
<br />
=== Using dd ===<br />
{{Note|This method is recommended due to its simplicity. If it does not work, switch to the alternative method [[#Using manual formatting]] below.}}<br />
<br />
{{Warning|This will irrevocably destroy all data on {{ic|/dev/'''sdx'''}}. To restore the USB drive as an empty, usable storage device after using the Arch ISO image, the iso9660 filesystem signature needs to be removed by running {{ic|wipefs --all /dev/'''sdx'''}} as root, before [[repartition]]ing and [[reformat]]ing the USB drive.}}<br />
<br />
==== In GNU/Linux ====<br />
<br />
{{Tip|Find out the name of your USB drive with {{ic|lsblk}}. Make sure that it is '''not''' mounted.}}<br />
<br />
Run the following command, replacing {{ic|/dev/'''sdx'''}} with your drive, e.g. {{ic|/dev/sdb}}. (Do '''not''' append a partition number, so do '''not''' use something like {{ic|/dev/sdb'''1'''}})<br />
<br />
# dd bs=4M if=/path/to/archlinux.iso of=/dev/'''sdx''' status=progress && sync<br />
<br />
Wait for the command ''sync'' to complete before unplugging the USB drive to ensure the data was written completely.<br />
<br />
See [[Core utilities#dd]] for more information about {{ic|dd}}.<br />
<br />
==== In Windows ====<br />
<br />
===== Using Rufus ===== <br />
[https://rufus.akeo.ie/ Rufus] is a multi-purpose USB iso writer. Simply select the Arch Linux ISO, the USB drive you want to create the bootable Arch Linux onto and click start.<br />
<br />
Since Rufus does not care if the drive is properly formatted or not and provides a GUI it may be the easiest and most robust tool to use.<br />
<br />
{{Note| Be sure to select '''DD''' mode or the image will be transferred incorrectly.}}<br />
<br />
===== Using USBwriter =====<br />
<br />
This method does not require any workaround and is as straightforward as {{ic|dd}} under Linux. Just download the Arch Linux ISO, and with local administrator rights use the [http://sourceforge.net/p/usbwriter/wiki/Documentation/ USBwriter] utility to write to your USB flash memory.<br />
<br />
===== Using win32diskimager =====<br />
<br />
[https://sourceforge.net/projects/win32diskimager/ win32diskimager] is another graphical USB iso writing tool for Windows. Simply select your iso image and the target USB drive letter (you may have to format it first to assign it a drive letter), and click Write. <br />
<br />
===== Using Cygwin =====<br />
<br />
Make sure your [http://www.cygwin.com/ Cygwin] installation contains the {{ic|dd}} package.<br />
<br />
{{Tip|If you do not want to install Cygwin, you can download {{ic|dd}} for Windows from [http://www.chrysocome.net/dd here]. See the next section for more information.}}<br />
<br />
Place your image file in your home directory:<br />
<br />
C:\cygwin\home\John\<br />
<br />
Run cygwin as administrator (required for cygwin to access hardware). To write to your USB drive use the following command:<br />
<br />
dd if=image.iso of=\\.\'''x''': bs=4M<br />
<br />
where image.iso is the path to the iso image file within the {{ic|cygwin}} directory and {{ic|\\.\'''x''':}} is your USB flash drive where {{ic|'''x'''}} is the windows designated letter, e.g. {{ic|\\.\d:}}.<br />
<br />
On Cygwin 6.0, find out the correct partition with:<br />
<br />
cat /proc/partitions<br />
<br />
and write the ISO image with the information from the output. Example:<br />
<br />
{{Warning|This will irrevocably delete all files on your USB flash drive, so make sure you do not have any important files on the flash drive before doing this.}}<br />
<br />
dd if=image.iso of=/dev/sdb bs=4M<br />
<br />
===== dd for Windows =====<br />
<br />
A GPL licensed dd version for Windows is available at http://www.chrysocome.net/dd. The advantage of this over Cygwin is a smaller download. Use it as shown in instructions for Cygwin above.<br />
<br />
To begin, download the latest version of dd for Windows. Once downloaded, extract the archive's contents into Downloads or elsewhere.<br />
<br />
Now, launch your {{ic|command prompt}} as an administrator. Next, change directory ({{ic|cd}}) into the Downloads directory.<br />
<br />
If your Arch Linux ISO is elsewhere you may need to state the full path, for convenience you may wish to put the Arch Linux ISO into the same folder as the dd executable. The basic format of the command will look like this.<br />
<br />
# dd if=''archlinux-2017-XX-YY-x86_64.iso'' od=\\.\''x'': bs=4M<br />
<br />
{{Note|The Windows drive letters are linked to a partition. To allow selecting the entire disk, ''dd for Windows'' provides the {{ic|od}} parameter, which is used in the commands above. Note however that this parameter is specific to ''dd for Windows'' and cannot be found in other implementations of ''dd''.}}<br />
<br />
{{Warning|Because the {{ic|od}} is used, all partitions on the selected disk will be destroyed. Be absolutely sure that you are directing dd to the correct drive before executing.}}<br />
<br />
Simply replace the various null spots (indicated by an "x") with the correct date and correct drive letter. Here is a complete example.<br />
<br />
# dd if=ISOs\archlinux-2017.04.01-x86_64.iso od=\\.\d: bs=4M<br />
<br />
{{Accuracy|The following note may be invalid, the [http://www.chrysocome.net/dd upstream documentation] does not mention anything related to ''PhysicalDrive''.}}<br />
<br />
{{Note|Alternatively, replace the drive letter with {{ic|\\.\PhysicalDrive''X''}}, where {{ic|''X''}} is the physical drive number (starts from 0). Example:<br />
{{bc|1=# dd if=ISOs\archlinux-2017.04.01-x86_64.iso of=\\.\PhysicalDrive1 bs=4M}}<br />
You can find out the physical drive number by typing {{ic|wmic diskdrive list brief}} at the command prompt or with {{ic|dd --list}}<br />
Any Explorer window must be closed or dd will report an error.}}<br />
<br />
==== In macOS ====<br />
<br />
First, you need to identify the USB device. Open {{ic|/Applications/Utilities/Terminal}} and list all storage devices with the command:<br />
<br />
$ diskutil list<br />
<br />
Your USB device will appear as something like {{ic|/dev/disk2 (external, physical)}}. Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.<br />
<br />
A USB device is normally auto-mounted in macOS, and you have to unmount (not eject) it before block-writing to it with {{ic|dd}}. In Terminal, do:<br />
<br />
$ diskutil unmountDisk /dev/diskX<br />
<br />
Now copy the ISO image file to the device. The {{ic|dd}} command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:<br />
<br />
$ sudo dd if=path/to/arch.iso of=/dev/'''r'''diskX bs=1m<br />
<br />
After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.<br />
<br />
=== Using manual formatting===<br />
<br />
==== In GNU/Linux ====<br />
<br />
This method is more complicated than writing the image directly with {{ic|dd}}, but it does keep the flash drive usable for data storage (that is, the ISO is installed in a specific partition within the already [[Partitioning|partitioned device]] without altering other partitions).<br />
<br />
{{Note|Here, we will denote the targeted partition as {{ic|/dev/sd'''Xn'''}}. In any of the following commands, adjust '''X''' and '''n''' according to your system.}}<br />
<br />
* Make sure that the {{Pkg|syslinux}} package is installed on the system. <br />
<br />
* If not done yet, create the partition table and/or partition on the device before continuing. The partition {{ic|/dev/sd'''Xn'''}} must be formatted to FAT32.<br />
<br />
* Mount the ISO image, mount the FAT32 filesystem located in the USB flash device, and copy the contents of the ISO image to it. Then unmount the ISO image, but keep the FAT32 partition mounted (this will be used in subsequent steps). Eg:<br />
# mkdir -p /mnt/{iso,usb}<br />
# mount -o loop archlinux-2017.04.01-x86_64.iso /mnt/iso<br />
# mount /dev/sd'''Xn''' /mnt/usb<br />
# cp -a /mnt/iso/* /mnt/usb<br />
# sync<br />
# umount /mnt/iso<br />
<br />
* {{Note|The following step is not required when using [[Archboot]] instead of [[Archiso]].}} To boot either a label or an [[UUID]] to select the partition to boot from is required. By default the label {{ic|ARCH_2017'''XX'''}} (with the appropriate release month) is used. Thus, the partition’s label has to be set accordingly, for example using ''gparted''. Alternatively, you can change this behaviour by altering the lines ending by {{ic|1=archisolabel=ARCH_2017'''XX'''}} in the file {{ic|/mnt/usb/arch/boot/syslinux/archiso_sys.cfg}} (for BIOS boot), and in {{ic|/mnt/usb/loader/entries/archiso-x86_64.conf}} (for UEFI boot). To use an UUID instead, replace those portions of lines with {{ic|1=archiso''device''=/dev/disk/by-uuid/'''YOUR-UUID'''}}. The UUID can be retrieved with {{ic|1=blkid -o value -s UUID /dev/sd'''Xn'''}}.<br />
<br />
{{Warning|Mismatching labels or wrong UUID prevents booting from the created medium.}}<br />
<br />
* Syslinux is already preinstalled in ''/mnt/usb/arch/boot/syslinux''. Install it completely to that folder by following [[Syslinux#Manual install]]. Instructions are reproduced here for convenience.<br />
** Overwrite the existing Syslinux modules ({{ic|*.c32}} files) present in the USB (from the ISO) with the ones from the syslinux package (found in ''/usr/lib/syslinux/bios''). This is necessary to avoid boot failure because of a possible version mismatch.<br />
# cp /usr/lib/syslinux/bios/*.c32 /mnt/usb/arch/boot/syslinux<br />
** Run:<br />
# extlinux --install /mnt/usb/arch/boot/syslinux<br />
** Unmount the partition ({{ic|umount /mnt/usb}}).<br />
<br />
* Mark the partition as active (or “bootable”).<br />
<br />
==== In Windows ====<br />
<br />
{{Note|<br />
* For manual formatting, do not use any '''Bootable USB Creator utility''' for creating the UEFI bootable USB. For manual formatting, do not use ''dd for Windows'' to dd the ISO to the USB drive either.<br />
<br />
* In the below commands, '''X:''' is assumed to be the USB flash drive in Windows.<br />
<br />
* Windows uses backward slash {{ic|\}} as path-separator, so the same is used in the below commands.<br />
<br />
* All commands should be run in Windows command prompt '''as administrator'''.<br />
<br />
* {{ic|>}} denotes the Windows command prompt.<br />
}}<br />
<br />
* Partition and format the USB drive using [http://rufus.akeo.ie/ Rufus USB partitioner]. Select partition scheme option as '''MBR for BIOS and UEFI''' and File system as '''FAT32'''. Uncheck "Create a bootable disk using ISO image" and "Create extended label and icon files" options.<br />
<br />
* Change the '''Volume Label''' of the USB flash drive {{ic|X:}} to match the LABEL mentioned in the {{ic|1=archisolabel=}} part in {{ic|<ISO>\loader\entries\archiso-x86_64.conf}}. This step is required for Official ISO ([[Archiso]]) but not required for [[Archboot]]. This step can be also performed using Rufus, during the prior "partition and format" step.<br />
<br />
* Extract the ISO (similar to extracting ZIP archive) to the USB flash drive (using [http://7-zip.org/ 7-Zip]. <br />
<br />
* Download official Syslinux 6.xx binaries (zip file) from https://www.kernel.org/pub/linux/utils/boot/syslinux/ and extract it. The version of Syslinux should be the same version used in the ISO image.<br />
<br />
* Run the following command (in Windows cmd prompt, as admin):<br />
<br />
{{Note|Use {{ic|X:\boot\syslinux\}} for Archboot iso.}}<br />
<br />
> cd bios\<br />
> for /r %Y in (*.c32) do copy "%Y" "X:\arch\boot\syslinux\" /y<br />
> copy mbr\*.bin X:\arch\boot\syslinux\ /y<br />
<br />
* Install Syslinux to the USB by running (use {{ic|win64\syslinux64.exe}} for x64 Windows):<br />
<br />
{{Note|Use {{ic|-d /boot/syslinux}} for Archboot iso.}}<br />
<br />
> cd bios\<br />
> win32\syslinux.exe -d /arch/boot/syslinux -i -a -m X:<br />
<br />
{{Note|<br />
* The above step installs Syslinux's {{ic|ldlinux.sys}} to the VBR of the USB partition, sets the partition as "active/boot" in the MBR partition table and writes the MBR boot code to the 1st 440-byte boot code region of the USB.<br />
<br />
* The {{ic|-d}} switch expects a path with forward slash path-separator like in *unix systems.<br />
}}<br />
<br />
== Other methods for BIOS systems ==<br />
<br />
=== In GNU/Linux ===<br />
<br />
==== Using a multiboot USB drive ====<br />
This allows booting multiple ISOs from a single USB device, including the archiso. Updating an existing USB drive to a more recent ISO is simpler than for most other methods. See [[Multiboot USB drive]].<br />
<br />
==== Using GNOME Disk Utility ====<br />
Linux distributions running GNOME can easily make a live CD through {{Pkg|nautilus}} and {{Pkg|gnome-disk-utility}}. Simply right-click on the .iso file, and select "Open With Disk Image Writer." When GNOME Disk Utility opens, specify the flash drive from the "Destination" drop-down menu and click "Start Restoring."<br />
<br />
==== Making a USB-ZIP drive ====<br />
For some old BIOS systems, only booting from USB-ZIP drives is supported. This method allows you to still boot from a USB-HDD drive.<br />
{{Warning|This will destroy all information on your USB flash drive!}}<br />
<br />
* Download {{Pkg|syslinux}} and {{Pkg|mtools}} from the official repositories.<br />
* Find your usb drive with {{ic|lsblk}}.<br />
* Type {{ic|mkdiskimage -4 /dev/sd'''x''' 0 64 32}} (replace x with the letter of your drive). This will take a while.<br />
From here continue with the manual formatting method. The partition will be /dev/sd'''x'''4 due to the way ZIP drives work.<br />
<br />
{{Note|Do not format the drive as FAT32; keep it as FAT16.}}<br />
<br />
==== Using UNetbootin ====<br />
UNetbootin can be used on any Linux distribution or Windows to copy your iso to a USB device. However, Unetbootin overwrites syslinux.cfg, so it creates a USB device that does not boot properly. For this reason, '''Unetbootin is not recommended''' -- please use {{ic|dd}} or one of the other methods discussed in this topic.<br />
{{Warning|UNetbootin writes over the default {{ic|syslinux.cfg}}; this must be restored before the USB device will boot properly.}}<br />
<br />
Edit {{ic|syslinux.cfg}}:<br />
<br />
{{hc|sysconfig.cfg|2=<br />
default menu.c32<br />
prompt 0<br />
menu title Archlinux Installer<br />
timeout 100<br />
<br />
label unetbootindefault<br />
menu label Archlinux_x86_64<br />
kernel /arch/boot/x86_64/vmlinuz<br />
append initrd=/arch/boot/x86_64/archiso.img archisodevice=/dev/sd'''x1''' ../../<br />
}}<br />
<br />
In {{ic|/dev/sd'''x1'''}} you must replace '''x''' with the first free letter after the last letter in use on the system where you are installing Arch Linux (e.g. if you have two hard drives, use {{ic|c}}.). You can make this change during the first phase of boot by pressing {{ic|Tab}} when the menu is shown.<br />
<br />
=== In Windows ===<br />
<br />
==== Win32 Disk Imager ====<br />
<br />
{{Warning|This will destroy all information on your USB flash drive!}}<br />
First, download the program from [http://sourceforge.net/projects/win32diskimager/ here]. Next, extract the archive and run the executable. Now, select the Arch Linux ISO under the {{ic|Image File}} section and the USB flash device letter (for example, [D:\]) under the {{ic|Device}} section. Finally, click {{ic|Write}} when ready.<br />
{{Note|After installation, you may need to restore the USB flash drive following a process as outlined in [[#Using dd]].}}<br />
<br />
==== USBWriter for Windows ====<br />
<br />
Download the program from http://sourceforge.net/projects/usbwriter/ and run it. Select the arch image file, the target USB stick, and click on the {{ic|write}} button. Now you should be able to boot from the usb stick and install Arch Linux from it.<br />
<br />
==== The Flashnul way ====<br />
<br />
[https://translate.google.com/translate?hl=&sl=ru&tl=en&u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2Freadme.rus.html&sandbox=1 flashnul] is an utility to verify the functionality and maintenance of Flash-Memory (USB-Flash, IDE-Flash, SecureDigital, MMC, MemoryStick, SmartMedia, XD, CompactFlash etc).<br />
<br />
From a command prompt, invoke flashnul with {{ic|-p}}, and determine which device index is your USB drive, e.g.:<br />
<br />
{{hc|C:\>flashnul -p|<br />
Avaible physical drives:<br />
Avaible logical disks:<br />
C:\<br />
D:\<br />
E:\<br />
}}<br />
<br />
When you have determined which device is the correct one, you can write the image to your drive, by invoking flashnul with the device index, {{ic|-L}}, and the path to your image, e.g:<br />
<br />
C:\>flashnul '''E:''' -L ''path\to\arch.iso''<br />
<br />
As long as you are really sure you want to write the data, type yes, then wait a bit for it to write. If you get an access denied error, close any Explorer windows you have open.<br />
<br />
If under Vista or Win7, you should open the console as administrator, or else flashnul will fail to open the stick as a block device and will only be able to write via the drive handle windows provides<br />
<br />
{{Note|Confirmed that you need to use drive letter as opposed to number. flashnul 1rc1, Windows 7 x64.}}<br />
<br />
==== Loading the installation media from RAM ====<br />
<br />
{{Merge|Multiboot USB drive#Using Syslinux and memdisk|This is the same method, only Syslinux is installed from Windows. Considering that [[multiboot USB drive]] can be used to boot an installation media and it is already linked from the Related articles box at the top, maybe this section should be merged there?}}<br />
<br />
This method uses [[Syslinux]] and a [[Ramdisk]] ([http://www.syslinux.org/wiki/index.php/MEMDISK MEMDISK]) to load the entire Arch Linux ISO image into RAM. Since this will be running entirely from system memory, you will need to make sure the system you will be installing this on has an adequate amount. A minimum amount of RAM between 500 MB and 1 GB should suffice for a MEMDISK based, Arch Linux install.<br />
<br />
For more information on Arch Linux system requirements as well as those for MEMDISK see the [[Installation guide]] and [http://www.etherboot.org/wiki/bootingmemdisk#preliminaries here]. For reference, here is the [https://bbs.archlinux.org/viewtopic.php?id=135266 preceding forum thread].<br />
<br />
{{Tip|Once the installer has completed loading you can simply remove the USB stick and even use it on a different machine to start the process all over again. Utilizing MEMDISK also allows booting and installing Arch Linux to and from the same USB flash drive.}}<br />
<br />
===== Preparing the USB flash drive =====<br />
<br />
Begin by formatting the USB flash drive as '''FAT32'''. Then create the following folders on the newly formatted drive.<br />
* {{ic|Boot}}<br />
** {{ic|Boot/ISOs}}<br />
** {{ic|Boot/Settings}}<br />
<br />
===== Copy the needed files to the USB flash drive =====<br />
<br />
Next copy the ISO that you would like to boot to the {{ic|Boot/ISOs}} folder. After that, extract from the following files from the latest release of {{pkg|syslinux}} from [http://www.kernel.org/pub/linux/utils/boot/syslinux/ here] and copy them into the following folders.<br />
* {{ic|./win32/syslinux.exe}} to the Desktop or Downloads folder on your system.<br />
* {{ic|./memdisk/memdisk}} to the {{ic|Settings}} folder on your USB flash drive.<br />
<br />
===== Create the configuration file =====<br />
<br />
After copying the needed files, navigate to the USB flash drive, /boot/Settings and create a {{ic|syslinux.cfg}} file.<br />
{{Warning|On the {{ic|INITRD}} line, be sure to use the name of the ISO file that you copied to your {{ic|ISOs}} folder!}}<br />
{{hc|/Boot/Settings/syslinux.cfg|2=<br />
DEFAULT arch_iso<br />
<br />
LABEL arch_iso<br />
MENU LABEL Arch Setup<br />
LINUX memdisk<br />
INITRD /Boot/ISOs/archlinux-2017.04.01-x86_64.iso<br />
APPEND iso}}<br />
For more information on Syslinux see the [[Syslinux|Arch Wiki article]].<br />
<br />
===== Final steps =====<br />
<br />
Finally, create a {{ic|*.bat}} file where {{ic|syslinux.exe}} is located and run it ("Run as administrator" if you are on Vista or Windows 7):<br />
{{hc|C:\Documents and Settings\username\Desktop\install.bat|<br />
@echo off<br />
syslinux.exe -m -a -d /Boot/Settings X:}}<br />
<br />
== Troubleshooting ==<br />
<br />
* If you get the "device did not show up after 30 seconds" error due to the {{ic|/dev/disk/by-label/ARCH_XXXXYY}} not mounting, try renaming your USB media to {{ic|ARCH_XXXXYY}} (e.g. {{ic|ARCH_201501}}).<br />
<br />
== See also ==<br />
<br />
* [https://wiki.gentoo.org/wiki/LiveUSB/HOWTO Gentoo wiki - LiveUSB/HOWTO]<br />
* [https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB Fedora wiki - How to create and use Live USB]<br />
* [http://en.opensuse.org/SDB:Live_USB_stick openSUSE wiki - SDB:Live USB stick]</div>Nfshttps://wiki.archlinux.org/index.php?title=Talk:Libinput&diff=460597Talk:Libinput2016-12-30T03:43:59Z<p>Nfs: </p>
<hr />
<div>== Fiddling with files in /usr/share ==<br />
<br />
The new tip suggests that users delete files in /usr/share/X11/xorg.conf.d. However, the X11 documentation says that files in this directory are for system use and user configuration files should go into /etc/X11/xorg.conf.d. Therefore I think that this tip should be worded differently but I do not feel completely certain.<br />
<br />
[[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 12:45, 1 September 2016 (UTC)<br />
<br />
:It doesn't say to ''delete'' the file. I think it can be overridden by naming the libinput file e.g. {{ic|60-libinput.conf}} so that it is applied before synaptics. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:05, 1 September 2016 (UTC)<br />
<br />
::What do you think about describing how to take care of the precedence issue in the previous paragraph and make the tip just "As a shortcut you could also uninstall xf86-input-synaptics"? [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 13:44, 1 September 2016 (UTC)<br />
<br />
:::It can be expanded in the tip itself. The surrounding text is 100% libinput and the tip is not needed for people not having synaptics in the first place. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:09, 1 September 2016 (UTC)<br />
<br />
::::I tried my best. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 16:53, 1 September 2016 (UTC)<br />
<br />
:::::Cheers, your edit had me come up with another approach which may roll smoother on updates. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 15:53, 3 September 2016 (UTC)<br />
<br />
::::::I feel like the new tip is not broad enough in scope. Where the old tip covered the general situation, the new one only covers the specific situation of no configuration files at all. Maybe they should have been combined instead. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 16:33, 3 September 2016 (UTC)<br />
<br />
:::::::Hm, I thought it was sufficient because [[Xorg#Using_.conf_files]] is linked to already. Added [https://wiki.archlinux.org/index.php?title=Libinput&type=revision&diff=451623&oldid=450978]. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 18:58, 22 September 2016 (UTC)<br />
<br />
== Scrolling issue ==<br />
<br />
I'm not sure where to go for support of this.<br />
<br />
'''Accidentally scrolling where my palm touches my T460s trackpad enters some text'''<br />
<br />
http://s.natalian.org/2016-09-16/libinput-list-devices.txt<br />
<br />
How do I limit or disable this unwanted behaviour?<br />
<br />
{{unsigned|02:30, 16 September 2016|Hendry}}<br />
<br />
:Look through the man page for {{man|4|libinput}}. {{ic|"DisableWhileTyping"}} might be what you are looking for. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 02:34, 16 September 2016 (UTC)<br />
<br />
== ClickMethod clickfinger/fingers ? ==<br />
<br />
I'm confused why the [https://cgit.freedesktop.org/xorg/driver/xf86-input-libinput/tree/src/xf86libinput.c#n526 source code] the [https://wayland.freedesktop.org/libinput/doc/latest/clickpad_softbuttons.html#clickfinger documentation], and the [https://www.mankier.com/4/libinput manpage] all mention "clickfinger" as the click_method, but <code>gsettings range org.gnome.desktop.peripherals.touchpad click-method</code> showed that I had to use "fingers", not "clickfinger" for the setting. Does anybody know why that is?<br />
<br />
{{unsigned|04:47, 3 November 2016|Wikizian}}<br />
<br />
:What you compare is the libinput x-wrapper nomenclatura to how gnome names it in its settings database. For the same reason the {{ic|DisableWhileTyping}} (see [[#Scrolling issue]] above) will have dashes when it arrives as a gnome gsettings key to toggle.[https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=4c5b1c1df399d6afaaccb237e299ccd1d5d29ddd] edit: I now see [https://wiki.archlinux.org/index.php?title=Libinput&curid=21515&diff=459643&oldid=457790], maybe gnome will follow suit. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 13:49, 20 December 2016 (UTC)<br />
<br />
== Touchscreen scrolling and kcm-pointing devices-git ==<br />
<br />
On the wiki page for libinput, it recommends installing kcm-pointing-devices-git for Plasma 5. However, this entails installing various dependencies including libxcb-git and xcb-proto-git. libxcb-git is marked as being out-of-date, and xcb-proto-git conflicts with the current xcb-proto.<br />
<br />
I am not sure I want to install the required dependencies, for various reasons, but mainly because I am not at all sure it would even help to solve the issue I am concerned with: to enable scrolling on my ELAN touchscreen.<br />
<br />
Can anyone comment on this issue?<br />
<br />
[[User:Nfs|Nfs]] ([[User talk:Nfs|talk]]) 17:19, 29 December 2016 (UTC)</div>Nfshttps://wiki.archlinux.org/index.php?title=Talk:Libinput&diff=460527Talk:Libinput2016-12-29T17:19:51Z<p>Nfs: /* Touchscreen scrolling and kcm-pointing devices-git */ new section</p>
<hr />
<div>== Fiddling with files in /usr/share ==<br />
<br />
The new tip suggests that users delete files in /usr/share/X11/xorg.conf.d. However, the X11 documentation says that files in this directory are for system use and user configuration files should go into /etc/X11/xorg.conf.d. Therefore I think that this tip should be worded differently but I do not feel completely certain.<br />
<br />
[[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 12:45, 1 September 2016 (UTC)<br />
<br />
:It doesn't say to ''delete'' the file. I think it can be overridden by naming the libinput file e.g. {{ic|60-libinput.conf}} so that it is applied before synaptics. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:05, 1 September 2016 (UTC)<br />
<br />
::What do you think about describing how to take care of the precedence issue in the previous paragraph and make the tip just "As a shortcut you could also uninstall xf86-input-synaptics"? [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 13:44, 1 September 2016 (UTC)<br />
<br />
:::It can be expanded in the tip itself. The surrounding text is 100% libinput and the tip is not needed for people not having synaptics in the first place. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:09, 1 September 2016 (UTC)<br />
<br />
::::I tried my best. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 16:53, 1 September 2016 (UTC)<br />
<br />
:::::Cheers, your edit had me come up with another approach which may roll smoother on updates. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 15:53, 3 September 2016 (UTC)<br />
<br />
::::::I feel like the new tip is not broad enough in scope. Where the old tip covered the general situation, the new one only covers the specific situation of no configuration files at all. Maybe they should have been combined instead. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 16:33, 3 September 2016 (UTC)<br />
<br />
:::::::Hm, I thought it was sufficient because [[Xorg#Using_.conf_files]] is linked to already. Added [https://wiki.archlinux.org/index.php?title=Libinput&type=revision&diff=451623&oldid=450978]. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 18:58, 22 September 2016 (UTC)<br />
<br />
== Scrolling issue ==<br />
<br />
I'm not sure where to go for support of this.<br />
<br />
'''Accidentally scrolling where my palm touches my T460s trackpad enters some text'''<br />
<br />
http://s.natalian.org/2016-09-16/libinput-list-devices.txt<br />
<br />
How do I limit or disable this unwanted behaviour?<br />
<br />
{{unsigned|02:30, 16 September 2016|Hendry}}<br />
<br />
:Look through the man page for {{man|4|libinput}}. {{ic|"DisableWhileTyping"}} might be what you are looking for. -- [[User:Cqql|Cqql]] ([[User talk:Cqql|talk]]) 02:34, 16 September 2016 (UTC)<br />
<br />
== ClickMethod clickfinger/fingers ? ==<br />
<br />
I'm confused why the [https://cgit.freedesktop.org/xorg/driver/xf86-input-libinput/tree/src/xf86libinput.c#n526 source code] the [https://wayland.freedesktop.org/libinput/doc/latest/clickpad_softbuttons.html#clickfinger documentation], and the [https://www.mankier.com/4/libinput manpage] all mention "clickfinger" as the click_method, but <code>gsettings range org.gnome.desktop.peripherals.touchpad click-method</code> showed that I had to use "fingers", not "clickfinger" for the setting. Does anybody know why that is?<br />
<br />
{{unsigned|04:47, 3 November 2016|Wikizian}}<br />
<br />
:What you compare is the libinput x-wrapper nomenclatura to how gnome names it in its settings database. For the same reason the {{ic|DisableWhileTyping}} (see [[#Scrolling issue]] above) will have dashes when it arrives as a gnome gsettings key to toggle.[https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=4c5b1c1df399d6afaaccb237e299ccd1d5d29ddd] edit: I now see [https://wiki.archlinux.org/index.php?title=Libinput&curid=21515&diff=459643&oldid=457790], maybe gnome will follow suit. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 13:49, 20 December 2016 (UTC)<br />
<br />
== Touchscreen scrolling and kcm-pointing devices-git ==<br />
<br />
On the wiki page for libinput, it recommends installing kcm-pointing-devices-git for Plasma 5. However, this entails installing various dependencies including libxcb-git and xcb-proto-git. libxcb-git is marked as being out-of-date, and xcb-proto-git conflicts with the current xcb-proto.<br />
<br />
I am not sure I want to install the required dependencies, for various reasons, but mainly because I am not at all sure it would even help to solve the issue I am concerned with. That is to enable scrolling on my ELAN touchscreen.<br />
<br />
Can anyone comment on this issue?<br />
<br />
[[User:Nfs|Nfs]] ([[User talk:Nfs|talk]]) 17:19, 29 December 2016 (UTC)</div>Nfs