https://wiki.archlinux.org/api.php?action=feedcontributions&user=Wan109020&feedformat=atomArchWiki - User contributions [en]2024-03-29T14:56:43ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:ClamAV&diff=573650Talk:ClamAV2019-05-22T07:25:44Z<p>Wan109020: change word use</p>
<hr />
<div>Should instructions for standalone (non-daemon) operation be added here or on its own page? --[[User:Papabean|papabean]] 22:56, 11 October 2009 (EDT)<br />
<br />
<br />
The new procedure of enabling and starting clamav with systemd goes something along the lines of:<br />
# systemctl enable freshclamd<br />
# systemctl start freshclamd<br />
#* Once freshclam has finished downloading the database to /var/lib/clamav:<br />
# systemctl enable clamd<br />
# systemctl start clamd<br />
I suspect there's a better way to do this so I haven't updated the article myself.--[[User:Kit|Kit]] ([[User talk:Kit|talk]]) 18:56, 16 October 2012 (UTC)<br />
<br />
== OnAccess Scanning ==<br />
<br />
It would be great it the page could also contain a section on how to configure OnAccess scanning - how to set up directories, the permissions, how virus findings are reported, ...<br />
[[User:Mephinet|Mephinet]] ([[User talk:Mephinet|talk]]) 19:17, 22 August 2016 (UTC)<br />
<br />
----<br />
<br />
Is it possibile to enable the 'OnAccessScan' editing the /etc/clamav/clamd.conf and add this options:<br />
<br />
{{hc|/etc/clamav/clamd.conf|# Enable scan on access, required clamd service running<br />
ScanOnAccess true <br />
# Set the mount point where to perform the scan,<br />
# this could be every path o multiple path (one line for path)<br />
# / for all<br />
OnAccessMount /<br />
# block all operation for the file during the scan<br />
OnAccessPrevention false<br />
# perform scans on newly created, moved, or renamed files<br />
OnAccessExtraScanning true<br />
# check UID and pid<br />
OnAccessExclude UID 0<br />
# action to perform when detects a malicious file (is possibile to specify a script path)<br />
# in headless server<br />
VirusEvents "echo $(date) - ${CLAM_VIRUSEVENT_VIRUSNAME}: ${CLAM_VIRUSEVENT_FILENAME} {{!}} wall"<br />
# client with libnotify<br />
# notify-send "Virus Found ${CLAM_VIRUSEVENT_VIRUSNAME}" "${CLAM_VIRUSEVENT_FILENAME} detected"<br />
# is also possible to delete the file with 'rm $CLAM_VIRUSEVENT_FILENAME'<br />
<br />
# clamd should run as root<br />
User root<br />
}}<br />
<br />
If you are using AppArmor it is necessary to allow clamd to run as root:<br />
<br />
$ sudo aa-complain clamd<br />
<br />
<br />
Source: http://blog.clamav.net/2016/03/configuring-on-access-scanning-in-clamav.html<br />
<br />
[[User:Edoz90|Dodo]] ([[User talk:Edoz90|talk]]) 04:00, 14 March 2017 (UTC)Edoz90<br />
<br />
: According to the ClamAV official documentation at https://www.clamav.net/documents/on-access-scanning, it seems that {{ic|OnAccessMountPath}} cannot be used in conjunction with {{ic|OnAccessExcludePath}} and {{ic|OnAccessExtraScanning}}. Is it that we should change the {{ic|OnAccessMountPath}} to {{ic|OnAccessIncludePath}}? Please correct me if I'm wrong as I'm also new to ClamAV. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 06:46, 22 May 2019 (UTC)<br />
: Oh, it feels like the VirusEvent is broken for some while. See https://bbs.archlinux.org/viewtopic.php?id=237489. The response script specified in VirusEvent will not be fired which makes the OnAccessScan feature ineffective. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 07:23, 22 May 2019 (UTC)</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:ClamAV&diff=573649Talk:ClamAV2019-05-22T07:23:42Z<p>Wan109020: VirusEvent will not be fired in current (0.101.2)</p>
<hr />
<div>Should instructions for standalone (non-daemon) operation be added here or on its own page? --[[User:Papabean|papabean]] 22:56, 11 October 2009 (EDT)<br />
<br />
<br />
The new procedure of enabling and starting clamav with systemd goes something along the lines of:<br />
# systemctl enable freshclamd<br />
# systemctl start freshclamd<br />
#* Once freshclam has finished downloading the database to /var/lib/clamav:<br />
# systemctl enable clamd<br />
# systemctl start clamd<br />
I suspect there's a better way to do this so I haven't updated the article myself.--[[User:Kit|Kit]] ([[User talk:Kit|talk]]) 18:56, 16 October 2012 (UTC)<br />
<br />
== OnAccess Scanning ==<br />
<br />
It would be great it the page could also contain a section on how to configure OnAccess scanning - how to set up directories, the permissions, how virus findings are reported, ...<br />
[[User:Mephinet|Mephinet]] ([[User talk:Mephinet|talk]]) 19:17, 22 August 2016 (UTC)<br />
<br />
----<br />
<br />
Is it possibile to enable the 'OnAccessScan' editing the /etc/clamav/clamd.conf and add this options:<br />
<br />
{{hc|/etc/clamav/clamd.conf|# Enable scan on access, required clamd service running<br />
ScanOnAccess true <br />
# Set the mount point where to perform the scan,<br />
# this could be every path o multiple path (one line for path)<br />
# / for all<br />
OnAccessMount /<br />
# block all operation for the file during the scan<br />
OnAccessPrevention false<br />
# perform scans on newly created, moved, or renamed files<br />
OnAccessExtraScanning true<br />
# check UID and pid<br />
OnAccessExclude UID 0<br />
# action to perform when detects a malicious file (is possibile to specify a script path)<br />
# in headless server<br />
VirusEvents "echo $(date) - ${CLAM_VIRUSEVENT_VIRUSNAME}: ${CLAM_VIRUSEVENT_FILENAME} {{!}} wall"<br />
# client with libnotify<br />
# notify-send "Virus Found ${CLAM_VIRUSEVENT_VIRUSNAME}" "${CLAM_VIRUSEVENT_FILENAME} detected"<br />
# is also possible to delete the file with 'rm $CLAM_VIRUSEVENT_FILENAME'<br />
<br />
# clamd should run as root<br />
User root<br />
}}<br />
<br />
If you are using AppArmor it is necessary to allow clamd to run as root:<br />
<br />
$ sudo aa-complain clamd<br />
<br />
<br />
Source: http://blog.clamav.net/2016/03/configuring-on-access-scanning-in-clamav.html<br />
<br />
[[User:Edoz90|Dodo]] ([[User talk:Edoz90|talk]]) 04:00, 14 March 2017 (UTC)Edoz90<br />
<br />
: According to the ClamAV official documentation at https://www.clamav.net/documents/on-access-scanning, it seems that {{ic|OnAccessMountPath}} cannot be used in conjunction with {{ic|OnAccessExcludePath}} and {{ic|OnAccessExtraScanning}}. Is it that we should change the {{ic|OnAccessMountPath}} to {{ic|OnAccessIncludePath}}? Please correct me if I'm wrong as I'm also new to ClamAV. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 06:46, 22 May 2019 (UTC)<br />
: Oh, it feels like the VirusEvent is broken for some while. See https://bbs.archlinux.org/viewtopic.php?id=237489. The response script specified in VirusEvent will not be fired which makes the OnAccessScan feature useless. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 07:23, 22 May 2019 (UTC)</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:ClamAV&diff=573644Talk:ClamAV2019-05-22T06:46:13Z<p>Wan109020: OnAccessMountPath cannot be used in conjunction to OnAccessExtraScanning and OAccessExcludePath</p>
<hr />
<div>Should instructions for standalone (non-daemon) operation be added here or on its own page? --[[User:Papabean|papabean]] 22:56, 11 October 2009 (EDT)<br />
<br />
<br />
The new procedure of enabling and starting clamav with systemd goes something along the lines of:<br />
# systemctl enable freshclamd<br />
# systemctl start freshclamd<br />
#* Once freshclam has finished downloading the database to /var/lib/clamav:<br />
# systemctl enable clamd<br />
# systemctl start clamd<br />
I suspect there's a better way to do this so I haven't updated the article myself.--[[User:Kit|Kit]] ([[User talk:Kit|talk]]) 18:56, 16 October 2012 (UTC)<br />
<br />
== OnAccess Scanning ==<br />
<br />
It would be great it the page could also contain a section on how to configure OnAccess scanning - how to set up directories, the permissions, how virus findings are reported, ...<br />
[[User:Mephinet|Mephinet]] ([[User talk:Mephinet|talk]]) 19:17, 22 August 2016 (UTC)<br />
<br />
----<br />
<br />
Is it possibile to enable the 'OnAccessScan' editing the /etc/clamav/clamd.conf and add this options:<br />
<br />
{{hc|/etc/clamav/clamd.conf|# Enable scan on access, required clamd service running<br />
ScanOnAccess true <br />
# Set the mount point where to perform the scan,<br />
# this could be every path o multiple path (one line for path)<br />
# / for all<br />
OnAccessMount /<br />
# block all operation for the file during the scan<br />
OnAccessPrevention false<br />
# perform scans on newly created, moved, or renamed files<br />
OnAccessExtraScanning true<br />
# check UID and pid<br />
OnAccessExclude UID 0<br />
# action to perform when detects a malicious file (is possibile to specify a script path)<br />
# in headless server<br />
VirusEvents "echo $(date) - ${CLAM_VIRUSEVENT_VIRUSNAME}: ${CLAM_VIRUSEVENT_FILENAME} {{!}} wall"<br />
# client with libnotify<br />
# notify-send "Virus Found ${CLAM_VIRUSEVENT_VIRUSNAME}" "${CLAM_VIRUSEVENT_FILENAME} detected"<br />
# is also possible to delete the file with 'rm $CLAM_VIRUSEVENT_FILENAME'<br />
<br />
# clamd should run as root<br />
User root<br />
}}<br />
<br />
If you are using AppArmor it is necessary to allow clamd to run as root:<br />
<br />
$ sudo aa-complain clamd<br />
<br />
<br />
Source: http://blog.clamav.net/2016/03/configuring-on-access-scanning-in-clamav.html<br />
<br />
[[User:Edoz90|Dodo]] ([[User talk:Edoz90|talk]]) 04:00, 14 March 2017 (UTC)Edoz90<br />
<br />
: According to the ClamAV official documentation at https://www.clamav.net/documents/on-access-scanning, it seems that {{ic|OnAccessMountPath}} cannot be used in conjunction with {{ic|OnAccessExcludePath}} and {{ic|OnAccessExtraScanning}}. Is it that we should change the {{ic|OnAccessMountPath}} to {{ic|OnAccessIncludePath}}? Please correct me if I'm wrong as I'm also new to ClamAV. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 06:46, 22 May 2019 (UTC)</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&diff=572280Talk:Installation guide2019-05-01T15:56:58Z<p>Wan109020: Fix identation</p>
<hr />
<div>== Read this first before adding new suggestions ==<br />
<br />
* systemd tools such as ''hostnamectl'', ''timedatectl'' and ''localectl'' [https://github.com/systemd/systemd/issues/798#issuecomment-126568596 do not work] in the installation chroot environment, so please do not propose to use them in the guide unless you can prove that they have been made to work also in that case. See [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=388727#General_problems], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=404695#Replace_commands_with_their_systemd_equivalents], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=418662#Utilizing_systemd_tools] and [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=434985#change_configuration_system_from_old_way_to_new_way.28using_systemd_commands.29] for some past discussions about this issue.<br />
* {{ic|localectl list-keymaps}} does not work due to bug {{Bug|46725}}. For the chosen replacement command, see [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=435044#localectl].<br />
* {{ic|localhost}} must be set explicitely in {{ic|/etc/hosts}}, as it is otherwise resolved over the network. See {{Bug|56684}}.<br />
-- [[ArchWiki:Administrators|The ArchWiki Administrators]] 22:17, 2 September 2016 (UTC)<br />
__TOC__<br />
<br />
== Link to the German version ==<br />
<br />
Instead of [[de:Arch Install Scripts]] you could choose [[de:Anleitung für Einsteiger]] it means "Beginner's Guid" and is a very <br />
detailed artikel for very new arch users and the future experts.<br />
<br />
:Thank you, [https://wiki.archlinux.org/index.php?title=Installation_guide&type=revision&diff=509961&oldid=508505 done]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 16:31, 6 February 2018 (UTC)<br />
<br />
::This was already proposed last year and rejected: [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=466950#Suggesting_different_page_for_German_translation]. I don't see what has changed since then. If someone adds me as admin to the german wiki or changes the protection settings, I can update [[de:Arch Install Scripts]] as required. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:13, 6 February 2018 (UTC)<br />
<br />
:::I see, I didn't remember that discussion so I've reverted the change, hopefully you'll make it to update the translation, let's leave this open until the problem is solved, otherwise this kind of suggestion will keep appearing recurrently. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 17:53, 7 February 2018 (UTC)<br />
<br />
== Network configuration ==<br />
<br />
=== dhcpcd for installed environment ===<br />
<br />
How about we add a sentence to [[Installation_guide#Network_configuration]] describing how to restore use of ''dhcpcd'' as done on the installation medium? That way if the connection already worked on installation people only need a brief look at [[dhcpcd]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:48, 27 May 2018 (UTC)<br />
<br />
:I think that would just hide the possibility of choice from users. Maybe just say that dhcpcd is not enabled on the installed system without recommending anything. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 17:34, 27 May 2018 (UTC)<br />
<br />
== Why should a static IP be preferred over 127.0.1.1 in /etc/hosts? ==<br />
<br />
"If the system has a permanent IP address, it should be used instead of 127.0.1.1."<br />
<br />
I think the ArchWiki should not just say do X but also why. [[User:Alad|Alad]] as you added this, perhaps you can explain?--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 15:14, 21 May 2018 (UTC)<br />
<br />
:In [[Network_configuration#Local hostname resolution]]: "For a system with a permanent IP address, that permanent IP address should be used instead of 127.0.1.1." -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:48, 22 May 2018 (UTC)<br />
<br />
::[https://wiki.archlinux.org/index.php?title=Network_configuration&diff=340138&oldid=333485 First] appearance in our wiki, cited [https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution source], also [https://wiki.archlinux.org/index.php?title=Talk:Network_configuration&oldid=360328#Hostname_resolution discussion]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:26, 22 May 2018 (UTC)<br />
<br />
== Network Configuration -- WiFi discussion ==<br />
<br />
I'm starting a new thread seeing as the last one took a different direction and never really got resolved.<br />
<br />
----<br />
<br />
As it stands, the current instructions for the installation guide make it challenging for users who need to connect to the internet via a Wireless connection rather than wired. The [[Installation_guide#Connect_to_the_Internet]] section essentially assumes the users are using a wired connection, and to test it with a ping. Otherwise, they are directed to the [[Network_configuration]] page. Unfortunately, that page does not provide clear instructions for new users (or even those who just want to do a quick connection) to establish a connection via wireless. Equally so, should users find their way to the [[Wireless_network_configuration]] page, there is some digging to do there in order to find instructions to setup a connection. These are currently using the iw command, which may prove to be challenging to some.<br />
I see a few different possible solutions to improve the user experience:<br />
* Add explicit instructions to the installation guide<br />
** This is not ideal, as it adds another place to maintain likely duplicate information<br />
* Add a reference to the [[Wireless_network_configuration]] page<br />
** This is better, though the page would likely need a new section, or some tweaking to allow users to more easily find the information they need to get setup<br />
* Add new/better instructions to the [[Network_configuration]] page<br />
** This may also prove to be tricky, seeing as that page is already fairly monolithic, and focuses mostly on wired connections<br />
One other consideration (of which I also don't see any progress) is the discussions revolving around moving and breaking down the Network Configuration guides, to separate Wired and Wireless content. With this move I could see such instructions being provided there. In any case, the guide should provide instructions that are:<br />
* Easy to follow, particularly for new users<br />
* Puts no emphasis on persisting configurations, as this is not applicable during the install phase<br />
* Offers options (choice is King)<br />
--[[User:CubeTheThird|CubeTheThird]] ([[User talk:CubeTheThird|talk]]) 23:47, 26 August 2018 (UTC)<br />
<br />
:The [[Wireless network configuration]] link [[Special:Diff/523161|was removed]] because it cannot be used independently of [[Network configuration]]. I propose the following:<br />
:# Implement [[Talk:Network configuration#Moving Ethernet-specific sections to Wired subpage]]. [[Network configuration]] currently isn't straightforward. The actual setup instructions are hidden in the ''Network management'' section and it's confusing that wireless has a subpage but wired and medium-agnostic configuration are mixed together. See [[User:Larivact/drafts/Network configuration|my demo]].<br />
:# <s>Have the ''Connect to the Internet'' section only link [[Network configuration]] and move the dhcpcd udev rule note there.</s><br />
:# Move [[Wireless network configuration]] to [[Network configuration/Wireless]] and move its ''iw'' section to a dedicated article because since recently we also have [[iwd]].<br />
:The result should be more user-friendly without duplicating content.<br />
:--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 07:13, 27 August 2018 (UTC)<br />
<br />
::As for your demo, note that in [[Talk:Network_configuration#Ongoing_rewrite]], [[User:Alad|Alad]] said: "ping is one of the very first commands a new user has to run on installation to verify the availability of an internet connection". So unless you intend to direct users from the installation guide directly to the [[Network configuration#Troubleshooting]] section, there is still some more thinking to be done... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:21, 28 August 2018 (UTC)<br />
<br />
:::Well then let's keep ''Connect to the Internet'' and revise it:<br />
<br />
The installation image has [https://git.archlinux.org/archiso.git/tree/configs/releng/airootfs/etc/udev/rules.d/81-dhcpcd.rules a udev rule] that enables the [[dhcpcd]] service for Ethernet network interfaces on boot. If you use Ethernet, verify the connection with [[ping]]:<br />
<br />
# ping archlinux.org<br />
<br />
If the ping fails see [[Network configuration#Troubleshooting]]. If you want to use Wi-Fi or a static IP address, [[stop]] the ''dhcpcd'' service with {{ic|systemctl stop dhcpcd@''interface''}} where the {{ic|''interface''}} name can be [[Wikipedia:Command-line_completion|tab-completed]] and proceed with [[Network configuration]].<br />
<br />
:::--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 08:41, 28 August 2018 (UTC)<br />
<br />
::::That looks good to me. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:57, 28 August 2018 (UTC)<br />
<br />
== fstab ==<br />
<br />
The section about generating the fstab with genfstab mentions -U and -L options but not the possibility to use GPT identifiers PARTUUID and PARTLABEL with the '-t' option. Those are described in [[Persistent block device naming]] and are a better choice for some users. genfstab itself doesn't explicitly list the GPT options either so IMHO it would be helpful to add this info here.<br />
<br />
{{unsigned|15:12, 9 October 2018|Grmat}}<br />
<br />
:In that case you should open a bug / file a patch such that {{ic|genfstab}} does list these options. The wiki shouldn't make up for missing basic documentation in distribution tools. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:49, 13 March 2019 (UTC)<br />
<br />
== Wording in example layout table and size of EFI partition ==<br />
<br />
=== Wording in example layout table ===<br />
<br />
Regarding [[Installation_guide#Example_layouts]]:<br />
<br />
even if many users will understand remainder of the device as what is left after size of /dev/sdx1 and /dev/sdx3 are subtsructed from the size of the device, I think the order of the table might be confusing for some. Some people might set /dev/sdx2 to the size of the device minus size of /dev/sdx1, and then stumbled at where from 512 MiB, or larger, are to be found for /dev/sdx3. Either suggest the swap space as /dev/sdx2 and / as /dev/sdx3, or better explain the meaning of the remainder of the device for sdx2. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 14:05, 29 December 2018 (UTC)<br />
<br />
:Using /dev/sdx2 for swap is questionable, it doesn't emphasize that swap is optional nor is it consistent with other articles like [[dm-crypt/Encrypting an entire system]]. If you have some better explanation for "remainder of the device" feel free to propose it. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:55, 30 December 2018 (UTC)<br />
:: I was trying to say that a user that patitions his HD by following the table might do the following: look at first row in the table, and creates the EFI partition. Than continue with the 2nd row. So he creates a partition at the remainder of his HD. Now he comes to the 3rd row: where will he get 512 MiB, or larger? As for [[dm-crypt/Encrypting an entire system]], I might be wrong thinking that each partition is considered a separate device, so it doesn't matter if the swap space is before, or after, the / partition. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 12:41, 30 December 2018 (UTC)<br />
<br />
::: Perhaps call it "Principal part of the device" instead. NB the term "remainder of the device" is often used for a separate {{ic|/home}} in other articles. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 21:33, 3 February 2019 (UTC)<br />
<br />
=== <s>Size of EFI partition</s> ===<br />
<br />
: Moved to [[Talk:EFI system partition#Size_of_EFI_partition]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:40, 13 March 2019 (UTC)<br />
<br />
== Boot loader installation ==<br />
<br />
[[Installation guide#Boot loader]] doesn't say to '''install''' a boot loader, it only refers to a list of them. How about adding something like "Choose and install at least one boot loader."? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 19:46, 14 March 2019 (UTC)<br />
<br />
: ''At least'' one? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:09, 14 March 2019 (UTC)<br />
<br />
:: Might not be the most common scenario, but it's possible to use one boot loader for BIOS booting and another for UEFI booting. E.g. [[rEFInd]] for UEFI booting + [[Syslinux]] for BIOS booting. If that use case is too uncommon to be mentioned then just add "Choose and install a boot loader.". -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 21:31, 14 March 2019 (UTC)<br />
<br />
=== Boot loader options ===<br />
<br />
Is it worth saying that without {{Pkg|systemd-sysvcompat}}, you need to add the {{ic|1=init=/lib/systemd/systemd}} kernel parameter?<br />
<br />
I got a bad surprise when I uninstalled the thing. – [[User:Flying_sheep|flying sheep]] 08:05, 18 April 2019 (UTC)<br />
<br />
:That is not something that belongs in the [[Installation guide]]. The {{ic|1=init=}} parameter is documented in [[Kernel parameters#Parameter list]] and its description hints at the consequences of uninstalling {{Pkg|systemd-sysvcompat}}.<br />
:What made you decide to uninstall {{Pkg|systemd-sysvcompat}}? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 10:37, 18 April 2019 (UTC)<br />
<br />
::I decided I didn’t need the aliases it provides. Little did I know that one of them is Linux’ defaults.<br />
::I think it’s a bit hidden there and there should be some way to discover this in the wiki while installing – [[User:Flying_sheep|flying sheep]] 16:58, 22 April 2019 (UTC)<br />
<br />
:::I'm not against making it a bit more discoverable, but the [[Installation guide]] is not the place for that. I think it would best belong somewhere in the [[systemd]] page. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:58, 24 April 2019 (UTC)<br />
<br />
== <s>Verify signature -- alternative keyserver</s> ==<br />
<br />
It seems <code>pgp.mit.edu</code> has been down for weeks.<br />
<br />
Given that GnuPG has setup its keyserver <code>keys.gnupg.net</code>, perhaps we could add it as an alternative?<br />
<br />
Despite currently it uses a self signed certificate, which limits TLS.<br />
<br />
[[User:LuxD3si9n|LuxD3si9n]] ([[User talk:LuxD3si9n|talk]]) 18:33, 26 March 2019 (UTC)<br />
<br />
:I don't know even know why we add a specific keyserver to that line... how to deal with keyservers is described in [[GnuPG#Use_a_keyserver]] already. [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=569896&oldid=568871] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:23, 27 March 2019 (UTC)<br />
<br />
== Confusing partition numbers ==<br />
<br />
The partition numbers on this page are confusing. The table calls the root partition /dev/sdX2, while the text below calls it /dev/sdX1. It should be matched for consistency. [[User:Sabinscabin|Sabinscabin]] ([[User talk:Sabinscabin|talk]]) 20:29, 13 April 2019 (UTC)<br />
<br />
== Note for EFI formatting ==<br />
<br />
Under the section '''"Format the partitions"''', I believe it can be confusing for newcomers wanting to set up an EFI system. <br />
An EFI system requires that the boot partition is formatted as FAT, and this could easily be overlooked going through the installation guide.<br />
I believe a note saying something along the lines ''"Please note that for an EFI system partition, FAT12, FAT16 or FAT32 is mandatory"'' followed by a codeblock containing ''# mkfs.fat -F32 /dev/sdxY''.<br />
I came across this with a friend, helping him to install Arch, and I believe I also overlooked this during my first attempt.<br />
<br />
Please let me know your thoughts.<br />
--[[User:AustralianZim|AustralianZim]] ([[User talk:AustralianZim|talk]]) 11:23, 30 April 2019 (UTC)<br />
<br />
:The EFI system partition requirements are explained in the [[EFI system partition]] article which is linked from [[Installation guide#Example layouts]]. Also, an UEFI system does not require using the FAT file system for the boot partition. An UEFI system may need a EFI system partition that must be formatted as FAT, but it doesn't require that the ESP is used as {{ic|/boot}}. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 11:41, 30 April 2019 (UTC)<br />
<br />
<s>== Microcode Update ==<br />
<br />
Installing processor microcode is probably something easily forgotten. And perhaps people just don't know there's microcode update for their processor. The system might still works very stable w/o Microcode Update, but still it's something good to have. <br />
Maybe it's a good idea to include the link to the microcode wiki in the beginner guide. </s><br />
{{Unsigned|02:09, 1 May 2019 (UTC)|Wan109020}}<br />
<br />
:There already is a link to the [[Microcode]] page in [[Installation guide#Boot loader]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:24, 1 May 2019 (UTC)<br />
:: I overlooked that. I'm sorry. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 15:56, 1 May 2019 (UTC)</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&diff=572279Talk:Installation guide2019-05-01T15:56:29Z<p>Wan109020: /* Microcode Update */</p>
<hr />
<div>== Read this first before adding new suggestions ==<br />
<br />
* systemd tools such as ''hostnamectl'', ''timedatectl'' and ''localectl'' [https://github.com/systemd/systemd/issues/798#issuecomment-126568596 do not work] in the installation chroot environment, so please do not propose to use them in the guide unless you can prove that they have been made to work also in that case. See [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=388727#General_problems], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=404695#Replace_commands_with_their_systemd_equivalents], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=418662#Utilizing_systemd_tools] and [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=434985#change_configuration_system_from_old_way_to_new_way.28using_systemd_commands.29] for some past discussions about this issue.<br />
* {{ic|localectl list-keymaps}} does not work due to bug {{Bug|46725}}. For the chosen replacement command, see [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=435044#localectl].<br />
* {{ic|localhost}} must be set explicitely in {{ic|/etc/hosts}}, as it is otherwise resolved over the network. See {{Bug|56684}}.<br />
-- [[ArchWiki:Administrators|The ArchWiki Administrators]] 22:17, 2 September 2016 (UTC)<br />
__TOC__<br />
<br />
== Link to the German version ==<br />
<br />
Instead of [[de:Arch Install Scripts]] you could choose [[de:Anleitung für Einsteiger]] it means "Beginner's Guid" and is a very <br />
detailed artikel for very new arch users and the future experts.<br />
<br />
:Thank you, [https://wiki.archlinux.org/index.php?title=Installation_guide&type=revision&diff=509961&oldid=508505 done]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 16:31, 6 February 2018 (UTC)<br />
<br />
::This was already proposed last year and rejected: [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=466950#Suggesting_different_page_for_German_translation]. I don't see what has changed since then. If someone adds me as admin to the german wiki or changes the protection settings, I can update [[de:Arch Install Scripts]] as required. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:13, 6 February 2018 (UTC)<br />
<br />
:::I see, I didn't remember that discussion so I've reverted the change, hopefully you'll make it to update the translation, let's leave this open until the problem is solved, otherwise this kind of suggestion will keep appearing recurrently. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 17:53, 7 February 2018 (UTC)<br />
<br />
== Network configuration ==<br />
<br />
=== dhcpcd for installed environment ===<br />
<br />
How about we add a sentence to [[Installation_guide#Network_configuration]] describing how to restore use of ''dhcpcd'' as done on the installation medium? That way if the connection already worked on installation people only need a brief look at [[dhcpcd]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:48, 27 May 2018 (UTC)<br />
<br />
:I think that would just hide the possibility of choice from users. Maybe just say that dhcpcd is not enabled on the installed system without recommending anything. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 17:34, 27 May 2018 (UTC)<br />
<br />
== Why should a static IP be preferred over 127.0.1.1 in /etc/hosts? ==<br />
<br />
"If the system has a permanent IP address, it should be used instead of 127.0.1.1."<br />
<br />
I think the ArchWiki should not just say do X but also why. [[User:Alad|Alad]] as you added this, perhaps you can explain?--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 15:14, 21 May 2018 (UTC)<br />
<br />
:In [[Network_configuration#Local hostname resolution]]: "For a system with a permanent IP address, that permanent IP address should be used instead of 127.0.1.1." -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:48, 22 May 2018 (UTC)<br />
<br />
::[https://wiki.archlinux.org/index.php?title=Network_configuration&diff=340138&oldid=333485 First] appearance in our wiki, cited [https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution source], also [https://wiki.archlinux.org/index.php?title=Talk:Network_configuration&oldid=360328#Hostname_resolution discussion]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:26, 22 May 2018 (UTC)<br />
<br />
== Network Configuration -- WiFi discussion ==<br />
<br />
I'm starting a new thread seeing as the last one took a different direction and never really got resolved.<br />
<br />
----<br />
<br />
As it stands, the current instructions for the installation guide make it challenging for users who need to connect to the internet via a Wireless connection rather than wired. The [[Installation_guide#Connect_to_the_Internet]] section essentially assumes the users are using a wired connection, and to test it with a ping. Otherwise, they are directed to the [[Network_configuration]] page. Unfortunately, that page does not provide clear instructions for new users (or even those who just want to do a quick connection) to establish a connection via wireless. Equally so, should users find their way to the [[Wireless_network_configuration]] page, there is some digging to do there in order to find instructions to setup a connection. These are currently using the iw command, which may prove to be challenging to some.<br />
I see a few different possible solutions to improve the user experience:<br />
* Add explicit instructions to the installation guide<br />
** This is not ideal, as it adds another place to maintain likely duplicate information<br />
* Add a reference to the [[Wireless_network_configuration]] page<br />
** This is better, though the page would likely need a new section, or some tweaking to allow users to more easily find the information they need to get setup<br />
* Add new/better instructions to the [[Network_configuration]] page<br />
** This may also prove to be tricky, seeing as that page is already fairly monolithic, and focuses mostly on wired connections<br />
One other consideration (of which I also don't see any progress) is the discussions revolving around moving and breaking down the Network Configuration guides, to separate Wired and Wireless content. With this move I could see such instructions being provided there. In any case, the guide should provide instructions that are:<br />
* Easy to follow, particularly for new users<br />
* Puts no emphasis on persisting configurations, as this is not applicable during the install phase<br />
* Offers options (choice is King)<br />
--[[User:CubeTheThird|CubeTheThird]] ([[User talk:CubeTheThird|talk]]) 23:47, 26 August 2018 (UTC)<br />
<br />
:The [[Wireless network configuration]] link [[Special:Diff/523161|was removed]] because it cannot be used independently of [[Network configuration]]. I propose the following:<br />
:# Implement [[Talk:Network configuration#Moving Ethernet-specific sections to Wired subpage]]. [[Network configuration]] currently isn't straightforward. The actual setup instructions are hidden in the ''Network management'' section and it's confusing that wireless has a subpage but wired and medium-agnostic configuration are mixed together. See [[User:Larivact/drafts/Network configuration|my demo]].<br />
:# <s>Have the ''Connect to the Internet'' section only link [[Network configuration]] and move the dhcpcd udev rule note there.</s><br />
:# Move [[Wireless network configuration]] to [[Network configuration/Wireless]] and move its ''iw'' section to a dedicated article because since recently we also have [[iwd]].<br />
:The result should be more user-friendly without duplicating content.<br />
:--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 07:13, 27 August 2018 (UTC)<br />
<br />
::As for your demo, note that in [[Talk:Network_configuration#Ongoing_rewrite]], [[User:Alad|Alad]] said: "ping is one of the very first commands a new user has to run on installation to verify the availability of an internet connection". So unless you intend to direct users from the installation guide directly to the [[Network configuration#Troubleshooting]] section, there is still some more thinking to be done... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:21, 28 August 2018 (UTC)<br />
<br />
:::Well then let's keep ''Connect to the Internet'' and revise it:<br />
<br />
The installation image has [https://git.archlinux.org/archiso.git/tree/configs/releng/airootfs/etc/udev/rules.d/81-dhcpcd.rules a udev rule] that enables the [[dhcpcd]] service for Ethernet network interfaces on boot. If you use Ethernet, verify the connection with [[ping]]:<br />
<br />
# ping archlinux.org<br />
<br />
If the ping fails see [[Network configuration#Troubleshooting]]. If you want to use Wi-Fi or a static IP address, [[stop]] the ''dhcpcd'' service with {{ic|systemctl stop dhcpcd@''interface''}} where the {{ic|''interface''}} name can be [[Wikipedia:Command-line_completion|tab-completed]] and proceed with [[Network configuration]].<br />
<br />
:::--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 08:41, 28 August 2018 (UTC)<br />
<br />
::::That looks good to me. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:57, 28 August 2018 (UTC)<br />
<br />
== fstab ==<br />
<br />
The section about generating the fstab with genfstab mentions -U and -L options but not the possibility to use GPT identifiers PARTUUID and PARTLABEL with the '-t' option. Those are described in [[Persistent block device naming]] and are a better choice for some users. genfstab itself doesn't explicitly list the GPT options either so IMHO it would be helpful to add this info here.<br />
<br />
{{unsigned|15:12, 9 October 2018|Grmat}}<br />
<br />
:In that case you should open a bug / file a patch such that {{ic|genfstab}} does list these options. The wiki shouldn't make up for missing basic documentation in distribution tools. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:49, 13 March 2019 (UTC)<br />
<br />
== Wording in example layout table and size of EFI partition ==<br />
<br />
=== Wording in example layout table ===<br />
<br />
Regarding [[Installation_guide#Example_layouts]]:<br />
<br />
even if many users will understand remainder of the device as what is left after size of /dev/sdx1 and /dev/sdx3 are subtsructed from the size of the device, I think the order of the table might be confusing for some. Some people might set /dev/sdx2 to the size of the device minus size of /dev/sdx1, and then stumbled at where from 512 MiB, or larger, are to be found for /dev/sdx3. Either suggest the swap space as /dev/sdx2 and / as /dev/sdx3, or better explain the meaning of the remainder of the device for sdx2. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 14:05, 29 December 2018 (UTC)<br />
<br />
:Using /dev/sdx2 for swap is questionable, it doesn't emphasize that swap is optional nor is it consistent with other articles like [[dm-crypt/Encrypting an entire system]]. If you have some better explanation for "remainder of the device" feel free to propose it. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:55, 30 December 2018 (UTC)<br />
:: I was trying to say that a user that patitions his HD by following the table might do the following: look at first row in the table, and creates the EFI partition. Than continue with the 2nd row. So he creates a partition at the remainder of his HD. Now he comes to the 3rd row: where will he get 512 MiB, or larger? As for [[dm-crypt/Encrypting an entire system]], I might be wrong thinking that each partition is considered a separate device, so it doesn't matter if the swap space is before, or after, the / partition. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 12:41, 30 December 2018 (UTC)<br />
<br />
::: Perhaps call it "Principal part of the device" instead. NB the term "remainder of the device" is often used for a separate {{ic|/home}} in other articles. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 21:33, 3 February 2019 (UTC)<br />
<br />
=== <s>Size of EFI partition</s> ===<br />
<br />
: Moved to [[Talk:EFI system partition#Size_of_EFI_partition]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:40, 13 March 2019 (UTC)<br />
<br />
== Boot loader installation ==<br />
<br />
[[Installation guide#Boot loader]] doesn't say to '''install''' a boot loader, it only refers to a list of them. How about adding something like "Choose and install at least one boot loader."? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 19:46, 14 March 2019 (UTC)<br />
<br />
: ''At least'' one? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:09, 14 March 2019 (UTC)<br />
<br />
:: Might not be the most common scenario, but it's possible to use one boot loader for BIOS booting and another for UEFI booting. E.g. [[rEFInd]] for UEFI booting + [[Syslinux]] for BIOS booting. If that use case is too uncommon to be mentioned then just add "Choose and install a boot loader.". -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 21:31, 14 March 2019 (UTC)<br />
<br />
=== Boot loader options ===<br />
<br />
Is it worth saying that without {{Pkg|systemd-sysvcompat}}, you need to add the {{ic|1=init=/lib/systemd/systemd}} kernel parameter?<br />
<br />
I got a bad surprise when I uninstalled the thing. – [[User:Flying_sheep|flying sheep]] 08:05, 18 April 2019 (UTC)<br />
<br />
:That is not something that belongs in the [[Installation guide]]. The {{ic|1=init=}} parameter is documented in [[Kernel parameters#Parameter list]] and its description hints at the consequences of uninstalling {{Pkg|systemd-sysvcompat}}.<br />
:What made you decide to uninstall {{Pkg|systemd-sysvcompat}}? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 10:37, 18 April 2019 (UTC)<br />
<br />
::I decided I didn’t need the aliases it provides. Little did I know that one of them is Linux’ defaults.<br />
::I think it’s a bit hidden there and there should be some way to discover this in the wiki while installing – [[User:Flying_sheep|flying sheep]] 16:58, 22 April 2019 (UTC)<br />
<br />
:::I'm not against making it a bit more discoverable, but the [[Installation guide]] is not the place for that. I think it would best belong somewhere in the [[systemd]] page. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:58, 24 April 2019 (UTC)<br />
<br />
== <s>Verify signature -- alternative keyserver</s> ==<br />
<br />
It seems <code>pgp.mit.edu</code> has been down for weeks.<br />
<br />
Given that GnuPG has setup its keyserver <code>keys.gnupg.net</code>, perhaps we could add it as an alternative?<br />
<br />
Despite currently it uses a self signed certificate, which limits TLS.<br />
<br />
[[User:LuxD3si9n|LuxD3si9n]] ([[User talk:LuxD3si9n|talk]]) 18:33, 26 March 2019 (UTC)<br />
<br />
:I don't know even know why we add a specific keyserver to that line... how to deal with keyservers is described in [[GnuPG#Use_a_keyserver]] already. [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=569896&oldid=568871] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:23, 27 March 2019 (UTC)<br />
<br />
== Confusing partition numbers ==<br />
<br />
The partition numbers on this page are confusing. The table calls the root partition /dev/sdX2, while the text below calls it /dev/sdX1. It should be matched for consistency. [[User:Sabinscabin|Sabinscabin]] ([[User talk:Sabinscabin|talk]]) 20:29, 13 April 2019 (UTC)<br />
<br />
== Note for EFI formatting ==<br />
<br />
Under the section '''"Format the partitions"''', I believe it can be confusing for newcomers wanting to set up an EFI system. <br />
An EFI system requires that the boot partition is formatted as FAT, and this could easily be overlooked going through the installation guide.<br />
I believe a note saying something along the lines ''"Please note that for an EFI system partition, FAT12, FAT16 or FAT32 is mandatory"'' followed by a codeblock containing ''# mkfs.fat -F32 /dev/sdxY''.<br />
I came across this with a friend, helping him to install Arch, and I believe I also overlooked this during my first attempt.<br />
<br />
Please let me know your thoughts.<br />
--[[User:AustralianZim|AustralianZim]] ([[User talk:AustralianZim|talk]]) 11:23, 30 April 2019 (UTC)<br />
<br />
:The EFI system partition requirements are explained in the [[EFI system partition]] article which is linked from [[Installation guide#Example layouts]]. Also, an UEFI system does not require using the FAT file system for the boot partition. An UEFI system may need a EFI system partition that must be formatted as FAT, but it doesn't require that the ESP is used as {{ic|/boot}}. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 11:41, 30 April 2019 (UTC)<br />
<br />
<s>== Microcode Update ==<br />
<br />
Installing processor microcode is probably something easily forgotten. And perhaps people just don't know there's microcode update for their processor. The system might still works very stable w/o Microcode Update, but still it's something good to have. <br />
Maybe it's a good idea to include the link to the microcode wiki in the beginner guide. </s><br />
{{Unsigned|02:09, 1 May 2019 (UTC)|Wan109020}}<br />
<br />
:There already is a link to the [[Microcode]] page in [[Installation guide#Boot loader]]. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:24, 1 May 2019 (UTC)<br />
: I overlooked that. I'm sorry. [[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 15:56, 1 May 2019 (UTC)</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&diff=572254Talk:Installation guide2019-05-01T02:09:32Z<p>Wan109020: suggestion to add applying Microcode processor update to the installation guide</p>
<hr />
<div>== Read this first before adding new suggestions ==<br />
<br />
* systemd tools such as ''hostnamectl'', ''timedatectl'' and ''localectl'' [https://github.com/systemd/systemd/issues/798#issuecomment-126568596 do not work] in the installation chroot environment, so please do not propose to use them in the guide unless you can prove that they have been made to work also in that case. See [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=388727#General_problems], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=404695#Replace_commands_with_their_systemd_equivalents], [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=418662#Utilizing_systemd_tools] and [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=434985#change_configuration_system_from_old_way_to_new_way.28using_systemd_commands.29] for some past discussions about this issue.<br />
* {{ic|localectl list-keymaps}} does not work due to bug {{Bug|46725}}. For the chosen replacement command, see [https://wiki.archlinux.org/index.php?title=Talk:Beginners%27_guide&oldid=435044#localectl].<br />
* {{ic|localhost}} must be set explicitely in {{ic|/etc/hosts}}, as it is otherwise resolved over the network. See {{Bug|56684}}.<br />
-- [[ArchWiki:Administrators|The ArchWiki Administrators]] 22:17, 2 September 2016 (UTC)<br />
__TOC__<br />
<br />
== Link to the German version ==<br />
<br />
Instead of [[de:Arch Install Scripts]] you could choose [[de:Anleitung für Einsteiger]] it means "Beginner's Guid" and is a very <br />
detailed artikel for very new arch users and the future experts.<br />
<br />
:Thank you, [https://wiki.archlinux.org/index.php?title=Installation_guide&type=revision&diff=509961&oldid=508505 done]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 16:31, 6 February 2018 (UTC)<br />
<br />
::This was already proposed last year and rejected: [https://wiki.archlinux.org/index.php?title=Talk:Installation_guide&oldid=466950#Suggesting_different_page_for_German_translation]. I don't see what has changed since then. If someone adds me as admin to the german wiki or changes the protection settings, I can update [[de:Arch Install Scripts]] as required. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 18:13, 6 February 2018 (UTC)<br />
<br />
:::I see, I didn't remember that discussion so I've reverted the change, hopefully you'll make it to update the translation, let's leave this open until the problem is solved, otherwise this kind of suggestion will keep appearing recurrently. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 17:53, 7 February 2018 (UTC)<br />
<br />
== Network configuration ==<br />
<br />
=== dhcpcd for installed environment ===<br />
<br />
How about we add a sentence to [[Installation_guide#Network_configuration]] describing how to restore use of ''dhcpcd'' as done on the installation medium? That way if the connection already worked on installation people only need a brief look at [[dhcpcd]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 15:48, 27 May 2018 (UTC)<br />
<br />
:I think that would just hide the possibility of choice from users. Maybe just say that dhcpcd is not enabled on the installed system without recommending anything. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 17:34, 27 May 2018 (UTC)<br />
<br />
== Why should a static IP be preferred over 127.0.1.1 in /etc/hosts? ==<br />
<br />
"If the system has a permanent IP address, it should be used instead of 127.0.1.1."<br />
<br />
I think the ArchWiki should not just say do X but also why. [[User:Alad|Alad]] as you added this, perhaps you can explain?--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 15:14, 21 May 2018 (UTC)<br />
<br />
:In [[Network_configuration#Local hostname resolution]]: "For a system with a permanent IP address, that permanent IP address should be used instead of 127.0.1.1." -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 06:48, 22 May 2018 (UTC)<br />
<br />
::[https://wiki.archlinux.org/index.php?title=Network_configuration&diff=340138&oldid=333485 First] appearance in our wiki, cited [https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution source], also [https://wiki.archlinux.org/index.php?title=Talk:Network_configuration&oldid=360328#Hostname_resolution discussion]. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 10:26, 22 May 2018 (UTC)<br />
<br />
== Network Configuration -- WiFi discussion ==<br />
<br />
I'm starting a new thread seeing as the last one took a different direction and never really got resolved.<br />
<br />
----<br />
<br />
As it stands, the current instructions for the installation guide make it challenging for users who need to connect to the internet via a Wireless connection rather than wired. The [[Installation_guide#Connect_to_the_Internet]] section essentially assumes the users are using a wired connection, and to test it with a ping. Otherwise, they are directed to the [[Network_configuration]] page. Unfortunately, that page does not provide clear instructions for new users (or even those who just want to do a quick connection) to establish a connection via wireless. Equally so, should users find their way to the [[Wireless_network_configuration]] page, there is some digging to do there in order to find instructions to setup a connection. These are currently using the iw command, which may prove to be challenging to some.<br />
I see a few different possible solutions to improve the user experience:<br />
* Add explicit instructions to the installation guide<br />
** This is not ideal, as it adds another place to maintain likely duplicate information<br />
* Add a reference to the [[Wireless_network_configuration]] page<br />
** This is better, though the page would likely need a new section, or some tweaking to allow users to more easily find the information they need to get setup<br />
* Add new/better instructions to the [[Network_configuration]] page<br />
** This may also prove to be tricky, seeing as that page is already fairly monolithic, and focuses mostly on wired connections<br />
One other consideration (of which I also don't see any progress) is the discussions revolving around moving and breaking down the Network Configuration guides, to separate Wired and Wireless content. With this move I could see such instructions being provided there. In any case, the guide should provide instructions that are:<br />
* Easy to follow, particularly for new users<br />
* Puts no emphasis on persisting configurations, as this is not applicable during the install phase<br />
* Offers options (choice is King)<br />
--[[User:CubeTheThird|CubeTheThird]] ([[User talk:CubeTheThird|talk]]) 23:47, 26 August 2018 (UTC)<br />
<br />
:The [[Wireless network configuration]] link [[Special:Diff/523161|was removed]] because it cannot be used independently of [[Network configuration]]. I propose the following:<br />
:# Implement [[Talk:Network configuration#Moving Ethernet-specific sections to Wired subpage]]. [[Network configuration]] currently isn't straightforward. The actual setup instructions are hidden in the ''Network management'' section and it's confusing that wireless has a subpage but wired and medium-agnostic configuration are mixed together. See [[User:Larivact/drafts/Network configuration|my demo]].<br />
:# <s>Have the ''Connect to the Internet'' section only link [[Network configuration]] and move the dhcpcd udev rule note there.</s><br />
:# Move [[Wireless network configuration]] to [[Network configuration/Wireless]] and move its ''iw'' section to a dedicated article because since recently we also have [[iwd]].<br />
:The result should be more user-friendly without duplicating content.<br />
:--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 07:13, 27 August 2018 (UTC)<br />
<br />
::As for your demo, note that in [[Talk:Network_configuration#Ongoing_rewrite]], [[User:Alad|Alad]] said: "ping is one of the very first commands a new user has to run on installation to verify the availability of an internet connection". So unless you intend to direct users from the installation guide directly to the [[Network configuration#Troubleshooting]] section, there is still some more thinking to be done... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:21, 28 August 2018 (UTC)<br />
<br />
:::Well then let's keep ''Connect to the Internet'' and revise it:<br />
<br />
The installation image has [https://git.archlinux.org/archiso.git/tree/configs/releng/airootfs/etc/udev/rules.d/81-dhcpcd.rules a udev rule] that enables the [[dhcpcd]] service for Ethernet network interfaces on boot. If you use Ethernet, verify the connection with [[ping]]:<br />
<br />
# ping archlinux.org<br />
<br />
If the ping fails see [[Network configuration#Troubleshooting]]. If you want to use Wi-Fi or a static IP address, [[stop]] the ''dhcpcd'' service with {{ic|systemctl stop dhcpcd@''interface''}} where the {{ic|''interface''}} name can be [[Wikipedia:Command-line_completion|tab-completed]] and proceed with [[Network configuration]].<br />
<br />
:::--[[User:Larivact|Larivact]] ([[User talk:Larivact|talk]]) 08:41, 28 August 2018 (UTC)<br />
<br />
::::That looks good to me. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 14:57, 28 August 2018 (UTC)<br />
<br />
== fstab ==<br />
<br />
The section about generating the fstab with genfstab mentions -U and -L options but not the possibility to use GPT identifiers PARTUUID and PARTLABEL with the '-t' option. Those are described in [[Persistent block device naming]] and are a better choice for some users. genfstab itself doesn't explicitly list the GPT options either so IMHO it would be helpful to add this info here.<br />
<br />
{{unsigned|15:12, 9 October 2018|Grmat}}<br />
<br />
:In that case you should open a bug / file a patch such that {{ic|genfstab}} does list these options. The wiki shouldn't make up for missing basic documentation in distribution tools. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:49, 13 March 2019 (UTC)<br />
<br />
== Wording in example layout table and size of EFI partition ==<br />
<br />
=== Wording in example layout table ===<br />
<br />
Regarding [[Installation_guide#Example_layouts]]:<br />
<br />
even if many users will understand remainder of the device as what is left after size of /dev/sdx1 and /dev/sdx3 are subtsructed from the size of the device, I think the order of the table might be confusing for some. Some people might set /dev/sdx2 to the size of the device minus size of /dev/sdx1, and then stumbled at where from 512 MiB, or larger, are to be found for /dev/sdx3. Either suggest the swap space as /dev/sdx2 and / as /dev/sdx3, or better explain the meaning of the remainder of the device for sdx2. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 14:05, 29 December 2018 (UTC)<br />
<br />
:Using /dev/sdx2 for swap is questionable, it doesn't emphasize that swap is optional nor is it consistent with other articles like [[dm-crypt/Encrypting an entire system]]. If you have some better explanation for "remainder of the device" feel free to propose it. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:55, 30 December 2018 (UTC)<br />
:: I was trying to say that a user that patitions his HD by following the table might do the following: look at first row in the table, and creates the EFI partition. Than continue with the 2nd row. So he creates a partition at the remainder of his HD. Now he comes to the 3rd row: where will he get 512 MiB, or larger? As for [[dm-crypt/Encrypting an entire system]], I might be wrong thinking that each partition is considered a separate device, so it doesn't matter if the swap space is before, or after, the / partition. [[User:Regid|Regid]] ([[User talk:Regid|talk]]) 12:41, 30 December 2018 (UTC)<br />
<br />
::: Perhaps call it "Principal part of the device" instead. NB the term "remainder of the device" is often used for a separate {{ic|/home}} in other articles. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 21:33, 3 February 2019 (UTC)<br />
<br />
=== <s>Size of EFI partition</s> ===<br />
<br />
: Moved to [[Talk:EFI system partition#Size_of_EFI_partition]]. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 17:40, 13 March 2019 (UTC)<br />
<br />
== Boot loader installation ==<br />
<br />
[[Installation guide#Boot loader]] doesn't say to '''install''' a boot loader, it only refers to a list of them. How about adding something like "Choose and install at least one boot loader."? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 19:46, 14 March 2019 (UTC)<br />
<br />
: ''At least'' one? -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 21:09, 14 March 2019 (UTC)<br />
<br />
:: Might not be the most common scenario, but it's possible to use one boot loader for BIOS booting and another for UEFI booting. E.g. [[rEFInd]] for UEFI booting + [[Syslinux]] for BIOS booting. If that use case is too uncommon to be mentioned then just add "Choose and install a boot loader.". -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 21:31, 14 March 2019 (UTC)<br />
<br />
=== Boot loader options ===<br />
<br />
Is it worth saying that without {{Pkg|systemd-sysvcompat}}, you need to add the {{ic|1=init=/lib/systemd/systemd}} kernel parameter?<br />
<br />
I got a bad surprise when I uninstalled the thing. – [[User:Flying_sheep|flying sheep]] 08:05, 18 April 2019 (UTC)<br />
<br />
:That is not something that belongs in the [[Installation guide]]. The {{ic|1=init=}} parameter is documented in [[Kernel parameters#Parameter list]] and its description hints at the consequences of uninstalling {{Pkg|systemd-sysvcompat}}.<br />
:What made you decide to uninstall {{Pkg|systemd-sysvcompat}}? -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 10:37, 18 April 2019 (UTC)<br />
<br />
::I decided I didn’t need the aliases it provides. Little did I know that one of them is Linux’ defaults.<br />
::I think it’s a bit hidden there and there should be some way to discover this in the wiki while installing – [[User:Flying_sheep|flying sheep]] 16:58, 22 April 2019 (UTC)<br />
<br />
:::I'm not against making it a bit more discoverable, but the [[Installation guide]] is not the place for that. I think it would best belong somewhere in the [[systemd]] page. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 07:58, 24 April 2019 (UTC)<br />
<br />
== <s>Verify signature -- alternative keyserver</s> ==<br />
<br />
It seems <code>pgp.mit.edu</code> has been down for weeks.<br />
<br />
Given that GnuPG has setup its keyserver <code>keys.gnupg.net</code>, perhaps we could add it as an alternative?<br />
<br />
Despite currently it uses a self signed certificate, which limits TLS.<br />
<br />
[[User:LuxD3si9n|LuxD3si9n]] ([[User talk:LuxD3si9n|talk]]) 18:33, 26 March 2019 (UTC)<br />
<br />
:I don't know even know why we add a specific keyserver to that line... how to deal with keyservers is described in [[GnuPG#Use_a_keyserver]] already. [https://wiki.archlinux.org/index.php?title=Installation_guide&diff=569896&oldid=568871] -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 00:23, 27 March 2019 (UTC)<br />
<br />
== Confusing partition numbers ==<br />
<br />
The partition numbers on this page are confusing. The table calls the root partition /dev/sdX2, while the text below calls it /dev/sdX1. It should be matched for consistency. [[User:Sabinscabin|Sabinscabin]] ([[User talk:Sabinscabin|talk]]) 20:29, 13 April 2019 (UTC)<br />
<br />
== Note for EFI formatting ==<br />
<br />
Under the section '''"Format the partitions"''', I believe it can be confusing for newcomers wanting to set up an EFI system. <br />
An EFI system requires that the boot partition is formatted as FAT, and this could easily be overlooked going through the installation guide.<br />
I believe a note saying something along the lines ''"Please note that for an EFI system partition, FAT12, FAT16 or FAT32 is mandatory"'' followed by a codeblock containing ''# mkfs.fat -F32 /dev/sdxY''.<br />
I came across this with a friend, helping him to install Arch, and I believe I also overlooked this during my first attempt.<br />
<br />
Please let me know your thoughts.<br />
--[[User:AustralianZim|AustralianZim]] ([[User talk:AustralianZim|talk]]) 11:23, 30 April 2019 (UTC)<br />
<br />
:The EFI system partition requirements are explained in the [[EFI system partition]] article which is linked from [[Installation guide#Example layouts]]. Also, an UEFI system does not require using the FAT file system for the boot partition. An UEFI system may need a EFI system partition that must be formatted as FAT, but it doesn't require that the ESP is used as {{ic|/boot}}. -- [[User:nl6720|nl6720]] ([[User talk:nl6720|talk]]) 11:41, 30 April 2019 (UTC)<br />
<br />
<br />
== Microcode Update ==<br />
<br />
Installing processor microcode is probably something easily forgotten. And perhaps people just don't know there's microcode update for their processor. The system might still works very stable w/o Microcode Update, but still it's something good to have. <br />
Maybe it's a good idea to include the link to the microcode wiki in the beginner guide.</div>Wan109020https://wiki.archlinux.org/index.php?title=Talk:Hardware_video_acceleration&diff=553697Talk:Hardware video acceleration2018-11-08T18:08:11Z<p>Wan109020: Suggested to include the Intel-Hybrid-driver option to VP9</p>
<hr />
<div>== VDPAU_DRIVER Variable ==<br />
This variable may need to be set when using older AMD cards even with open source drivers. I fixed this by adding a simlink in {{ic|/usr/lib/dri/r300_drv_video.so --> vdapu_video.so}} but this may have been able to be fixed with this environmental variable. It seems to work alright and doesn't break anything with my old backup laptop but this is probably not a preferred solution.<br />
{{bc|VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300]}}<br />
{{hc|pacman -Qqs vdpau && pacman -Qqs mesa|<br />
libva-vdpau-driver<br />
libvdpau<br />
mesa<br />
mesa-libgl<br />
mesa-vdpau}}<br />
[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 02:39, 26 May 2016 (UTC)<br />
<br />
:The [[Hardware_video_acceleration#Configuring_VDPAU]] section says:<br />
::"For the open source AMD/ATI driver set it to the proper driver version depending on your GPU (see below)."<br />
:So yes, you should have set the VDPAU_DRIVER variable instead of creating the symlink.<br />
:-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:04, 28 May 2016 (UTC)<br />
<br />
:: Yes, I probably should change it but I had that as a solution before finding that info in the wiki. I bring this up because it seemed to be indicated that that information may be unnecessary for open source AMD drivers. Maybe it isn't needed for newer AMD cards? The above example is from a laptop which is at least 11 years old this summer. Anyway, I still think that information is useful to keep in the wiki.<br />
::[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 22:07, 28 May 2016 (UTC)<br />
<br />
:::I've been thinking about swapping Configuring and Verifying for exactly this reason, but the problem is that I don't know when it is '''needed''' to set the the variable, it seems to very from system to system.<br />
:::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 15:31, 29 May 2016 (UTC)<br />
:::: I have an idea. If you look at the third line of the output of {{ic|vainfo}}, it lists a file in the directory {{ic|/usr/lib/dri/foo.so}}. As far as I am aware, all drivers which '''do not need''' to have the variable set will have the file asked for provided ''somewhere'' in a package. NOTE: I ran out this example on my workstation which uses the nvidia driver which is why it is asking for {{ic|/usr/lib/dri/nvidia_drv_video.so}} below.<br />
::::{{bc|<nowiki>libva info: VA-API version 0.39.0<br />
libva info: va_getDriverName() returns 0<br />
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so<br />
libva info: Found init function __vaDriverInit_0_35<br />
libva info: va_openDriver() returns 0<br />
vainfo: VA-API version: 0.39 (libva 1.7.0)<br />
vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 0.7.4<br />
vainfo: Supported profile and entrypoints<br />
VAProfileMPEG2Simple : VAEntrypointVLD<br />
VAProfileMPEG2Main : VAEntrypointVLD<br />
VAProfileMPEG4Simple : VAEntrypointVLD<br />
VAProfileMPEG4AdvancedSimple : VAEntrypointVLD<br />
VAProfileH264Baseline : VAEntrypointVLD<br />
VAProfileH264Main : VAEntrypointVLD<br />
VAProfileH264High : VAEntrypointVLD<br />
VAProfileVC1Simple : VAEntrypointVLD<br />
VAProfileVC1Main : VAEntrypointVLD<br />
VAProfileVC1Advanced : VAEntrypointVLD</nowiki>}}<br />
::::Then you can use {{ic|pkgfile -d /usr/lib/dri}} to list all packages in Arch which contain the listed directory.<br />
::::{{bc|<nowiki>extra/libva<br />
extra/libva-intel-driver<br />
extra/libva-mesa-driver<br />
extra/libva-vdpau-driver</nowiki>}}<br />
::::Finally, you can use {{ic|pkgfile -l | grep /usr/lib/dri}} on each listed package and put together a list of what would be supported by each package. If someone runs {{ic|vainfo}} and gets a {{ic|/usr/lib/dri/foo.so}} in that third line which is not listed, then they would need to set the variable or possibly {{ic|vaapi}} might just not be supported by anything.<br />
::::{{bc|<nowiki>extra/libva /usr/lib/dri/dummy_drv_video.so<br />
extra/libva-intel-driver /usr/lib/dri/i965_drv_video.so<br />
extra/libva-mesa-driver /usr/lib/dri/gallium_drv_video.so<br />
extra/libva-vdpau-driver /usr/lib/dri/nvidia_drv_video.so<br />
extra/libva-vdpau-driver /usr/lib/dri/s3g_drv_video.so<br />
extra/libva-vdpau-driver /usr/lib/dri/vdpau_drv_video.so</nowiki>}}<br />
::::Example: Running {{ic|vainfo}} on my old HP laptop which I cited above asks for a file name {{ic|/usr/lib/dri/r300_drv_video.so}} which is not included on the above list and therefore requires the environmental variable be set. Apologies for the length of this discussion but I couldn't really think of a better way of working through this. Not sure how to best represent this on the wiki, perhaps a table of some kind?<br />
::::Just taking a second to look at the results of that list, it seems that anyone with an AMD card which does not use {{ic|/usr/lib/dri/gallium_drv_video.so}} from the {{ic|libva-mesa-driver}} package or anyone using AMD and installing {{ic|libva-vdpau-driver}} will need to set the variable. There may be additional situations but I think that would cover the most common ones.<br />
::::[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 21:20, 29 May 2016 (UTC)<br />
<br />
:::::Now you're talking about VA-API, not VDPAU, i.e. you'd need to set {{ic|LIBVA_DRIVER_NAME}} instead of {{ic|VDPAU_DRIVER}}. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:33, 30 May 2016 (UTC)<br />
<br />
::::::I was always talking about that. Perhaps a bit misled because the package {{ic|libva-vdpau-driver}}. Like I said, I'm no great expert in video acceleration. Just had some time to research that a bit and try to put some stuff together. It is still part of the same (type) of issue though. Perhaps a similar procedure could be used to determine which conditions would require the other variable be set as well? I'm guessing that would be on Intel chips mostly as they tend to be what uses native VAAPI to get VDPAU.<br />
::::::[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 09:58, 30 May 2016 (UTC)<br />
:::::::Check the wiki page now, should explain it all better.<br />
:::::::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 16:58, 7 June 2016 (UTC)<br />
::::::::Yeah that seems a lot less confusing now.<br />
::::::::[[User:TheChickenMan|TheChickenMan]] ([[User talk:TheChickenMan|talk]]) 00:53, 8 June 2016 (UTC)<br />
:::::::::Well it seems like Lahwaacz reverted the changes. Lahwaacz: why did you do this? The changes were carefully thought out and removed a ton a useless misleading mess. The changes were too complex to change in several commits though. I mean I basically put together this page and already spent more than 6 hours on it and this was the final change making it complete in my eyes (disregarding a few small details).<br />
:::::::::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 12:29, 8 June 2016 (UTC)<br />
<br />
::::::::::Changes are never too complex to split in multiple edits -- bulking them together makes them complex, splitting makes them simpler. In this case, you should have first swapped the order of the sections, then deal with the content, e.g. one section after another. Among other benefits, you would have had much more space in edit summaries to describe the complexity.<br />
::::::::::As for the "useless misleading mess", why have you removed the link to [http://www.freedesktop.org/wiki/Software/vaapi/#driversback-endsthatimplementva-api] and the explicit suggestions of VA-API and VDPAU drivers? Your changes don't indicate that at all and considering the AMD case, I somewhat doubt that the details are as useless as you suggest.<br />
::::::::::And the original authors are shown [https://wiki.archlinux.org/index.php?title=VA-API&action=history here] and [https://wiki.archlinux.org/index.php?title=VDPAU&action=history here]. You have merged the two pages and reduced duplication, for which we are very grateful, but now we're past that. The pages are a [[Help:Style#Non-pertinent_content|community effort]].<br />
::::::::::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:14, 8 June 2016 (UTC)<br />
<br />
:::::::::::Wait, don't take me wrong, I am '''not''' taking authorship for this page, but I am taking (at least some) responsibility for it. I'm sorry if I sounded like another bigheaded idiot and I assure you I'm not (at least I try to, heh). I just (for the first and probably the last time) mentioned the time it took to do it all to prove that I'm not a vandal, that I'm trying my best to make the wiki better, and that I hope it earned me at least a teeny bit of trust in making edits like this. As for the edits, I know it is important and I take care to lay them out usually, but this one edit took at least an hour to make which is a '''lot''' of time for me unfortunately, and since I was going away for a few days I wanted to get it done and I just put the final state to a higher priority than making the edits slightly clearer.<br />
:::::::::::As for the 'useless misleading mess', let me clarify it: VDPAU and VA-API are actually really good at guessing the driver and it only fails if the driver doesn't exist; it's still guessed correctly though. Therefore the user should not manually configure the driver if everything works. The current layout suggests that not only the drivers have to (or should) be configured manually, but also that different cards need different drivers - if you look at the checksums of them you can see that many of the drivers are just copies with a different name (all the libraries in {{pkg|mesa-vdpau}} (r300, r600, radeonsi, nouveau) or {{pkg|libva-mesa-driver}} (nvidia, s3g and vpdau) are identical), the names are there just for compatibility reasons or something. And also the line about overriding the driver based on what VDPAU guessed itself is just nonsense. I tried to a) explain how the variable actually works, b) teach the user to '''test''' and try instead of relying on an (obselete/incomplete) table and c) make it at least a bit more future-proof while hopefully getting better results at the same time.<br />
:::::::::::As for the link - I looked at it a bit more carefully I see it's not a list of supported cards as I thought earlier, but it's still just a subsection of an already mentioned link and doesn't say much useful. It should be under installation though anyway, but I admit I shouldn't've removed it.<br />
:::::::::::With you permission I'd like to apply the changes again, this time in seperate commits though. Sorry for the trouble.<br />
:::::::::::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 13:17, 11 June 2016 (UTC)<br />
<br />
::::::::::::I apologize for the delay, unfortunately I was rather busy back then and somewhat forgot about this...<br />
::::::::::::Now where were we... OK, the mess is pretty much useless and misleading, except for the AMD case, which I think deserves at least some hand-holding. The installation section sounds as if {{pkg|libva-mesa-driver}} and {{pkg|libva-vdpau-driver}} were equivalent alternatives for all cards, but that is not the case since there is no {{ic|r300}} VAAPI driver in {{pkg|libva-mesa-driver}}, not to mention that [[AMDGPU]] is not mentioned at all on the page. Further, the {{ic|vdpau}} and {{ic|va_gl}} drivers are never automatically detected (for NVIDIA it's only thanks to the {{ic|nvidia_drv_video.so}} -> {{ic|vdpau_drv_video.so}} symlink), so in this case it's not "only proceed if something fails", but "unless you do this, something fails" (i.e. normal configuration). Your approach to the introduction of the section of course works generally, but I'm afraid that mixing these cases will always cause some confusion on one side or the other.<br />
::::::::::::So of course please feel free to continue improving the page, e.g. by combining your changes with my comments above ;)<br />
::::::::::::-- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:32, 4 August 2016 (UTC)<br />
:::::::::::::Hey, I can't believe it took me half a year to get to this, sorry for that.<br />
:::::::::::::The wiki has changed quite a bit since I last edited it, I've been reading it but I still need to figure some stuff out, but until then, please clarify the AMD thingy.<br />
:::::::::::::The wiki says (quote):<br />
:::::::::::::* For [[radeon]] the driver name can determined by running:<br />
:::::::::::::{{bc|<nowiki>$ grep -iE 'vdpau|dri driver' ~/.local/share/xorg/Xorg.0.log<br />
(II) RADEON(0): [DRI2] DRI driver: radeonsi<br />
(II) RADEON(0): [DRI2] VDPAU driver: radeonsi</nowiki>}}<br />
:::::::::::::In this case you want to use {{ic|radeonsi}} for both VA-API and VDPAU.<br />
:::::::::::::End of quote.<br />
:::::::::::::Here VDPAU ''guesses'' {{ic|radeonsi}}, and applies it too. Why would we want to override something to something already automatically set? The only way this could be useful is to find out what to use for VA-API, but that might not work, as the drivers aren't identical.<br />
:::::::::::::Also, looks like the difference between VA-API and VDPAU for the open-source AMD driver is non-existent, it really depends on the app, according to this: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/887994-vaapi-or-vdpau<br />
:::::::::::::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 21:11, 26 December 2016 (UTC)<br />
::::::::::::::I updated some parts of the wiki, it should solve most (if not all) of the above issues.<br />
::::::::::::::-- [[User:DoctorJellyface|DoctorJellyface]] ([[User talk:DoctorJellyface|talk]]) 10:03, 26 March 2017 (UTC)<br />
<br />
== Other Video acceleration ==<br />
<br />
Video decoding with other methods like cuda (usable through mpv) is not mentioned. It seems much more reliable than vdpau for nvidia cards. [[User:Ivanoff|Ivanoff]] ([[User talk:Ivanoff|talk]]) 07:25, 21 May 2017 (UTC)<br />
<br />
== vdpauinfo and optirun ==<br />
<br />
I disagree with this edit: https://wiki.archlinux.org/index.php?title=Hardware_video_acceleration&diff=next&oldid=519606<br />
Running {{ic|optirun vdpauinfo}} still tries to access display :0 and thus the intel gpu. If you want to get the info for nvidia, you need to correctly set DISPLAY.<br />
{{Unsigned|19:23, 1 May 2018 (UTC)|DrLuke}}<br />
<br />
== VP9 acceleration on Haswell/Bay-Trail-M/Broadwell/Braswell/Skylake ==<br />
Support for partially hardware accelerated encode and decode on Haswell and to skylake can be achieved by Intel Hybrid driver(https://aur.archlinux.org/packages/intel-hybrid-codec-driver/), as mentioned in https://gist.github.com/Brainiarc7/24de2edef08866c304080504877239a3 (Option 1: point 3)<br />
<br />
As it only provides partially decoding, performance may suffer, but IMO it's still an option that worth mentioning<br />
<br />
[[User:Wan109020|Wan109020]] ([[User talk:Wan109020|talk]]) 18:08, 8 November 2018 (UTC)</div>Wan109020