Talk:Installation guide

From ArchWiki
Jump to navigation Jump to search

Read this first before adding new suggestions

  • systemd tools such as hostnamectl, timedatectl and localectl 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 [1], [2], [3] and [4] for some past discussions about this issue.
  • localectl list-keymaps does not work due to bug FS#46725. For the chosen replacement command, see [5].
  • localhost must be set explicitely in /etc/hosts, as it is otherwise resolved over the network. See FS#56684.

-- The ArchWiki Administrators 22:17, 2 September 2016 (UTC)

Link to the German version

Instead of de:Arch Install Scripts you could choose de:Anleitung für Einsteiger it means "Beginner's Guid" and is a very detailed artikel for very new arch users and the future experts.

Thank you, done. -- Kynikos (talk) 16:31, 6 February 2018 (UTC)
This was already proposed last year and rejected: [6]. 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. -- Alad (talk) 18:13, 6 February 2018 (UTC)
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. -- Kynikos (talk) 17:53, 7 February 2018 (UTC)

Network configuration

dhcpcd for installed environment

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. -- Alad (talk) 15:48, 27 May 2018 (UTC)

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. -- Lahwaacz (talk) 17:34, 27 May 2018 (UTC)

once chrooted, one has to configure again

One chrooted, configuration file edited in the previous steps, will have to be redone in the chrooted environment (/etc/systemd/network/ files). This is the same for ntp configuration (/etc/systemd/timesyncd.conf).

This should be worth noting.

—This unsigned comment is by Mrechte (talk) 12:27, 14 May 2019‎. Please sign your posts with ~~~~!

The guide does not say to edit anything under /etc/systemd/ in the first place, so there is nothing to be redone. Furthermore, Installation guide#Network configuration says to "Complete the network configuration for the newly installed environment." -- Lahwaacz (talk) 17:27, 17 May 2019 (UTC)

include example DHCP client command

Under Installation_guide#Connect_to_the_internet -> 'Configure your network connection', it would be helpful to people unfamiliar with the syntax to include an example. For installation, the common path is to enable networking via DHCP so a DHCP client example along the lines of: 'For example, 'dhcpcd /interface/' where /interface/ comes from 'ip link' output' Yes, there's a wiki link to DHCP in there for those who want to know more but many users could save some time with a simple and up-front example. Rwat (talk) 20:18, 21 March 2020 (UTC)

There is also a link to dhcpcd in the note where you can find out how dhcpcd can be controlled. Also note what the note actually says. -- Lahwaacz (talk) 22:12, 21 March 2020 (UTC)

Why should a static IP be preferred over in /etc/hosts?

"If the system has a permanent IP address, it should be used instead of"

I think the ArchWiki should not just say do X but also why. Alad as you added this, perhaps you can explain?--Larivact (talk) 15:14, 21 May 2018 (UTC)

In Network_configuration#Local hostname resolution: "For a system with a permanent IP address, that permanent IP address should be used instead of" -- Lahwaacz (talk) 06:48, 22 May 2018 (UTC)
First appearance in our wiki, cited source, also discussion. -- Kynikos (talk) 10:26, 22 May 2018 (UTC)

Network Configuration -- WiFi discussion

I'm starting a new thread seeing as the last one took a different direction and never really got resolved.

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. I see a few different possible solutions to improve the user experience:

  • Add explicit instructions to the installation guide
    • This is not ideal, as it adds another place to maintain likely duplicate information
  • Add a reference to the Wireless_network_configuration page
    • 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
  • Add new/better instructions to the Network_configuration page
    • This may also prove to be tricky, seeing as that page is already fairly monolithic, and focuses mostly on wired connections

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:

  • Easy to follow, particularly for new users
  • Puts no emphasis on persisting configurations, as this is not applicable during the install phase
  • Offers options (choice is King)

--CubeTheThird (talk) 23:47, 26 August 2018 (UTC)

The Wireless network configuration link was removed because it cannot be used independently of Network configuration. I propose the following:
  1. 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 my demo.
  2. Have the Connect to the Internet section only link Network configuration and move the dhcpcd udev rule note there.
  3. Move Wireless network configuration to Network configuration/Wireless and move its iw section to a dedicated article because since recently we also have iwd.
The result should be more user-friendly without duplicating content.
--Larivact (talk) 07:13, 27 August 2018 (UTC)
As for your demo, note that in Talk:Network_configuration#Ongoing_rewrite, 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... -- Lahwaacz (talk) 07:21, 28 August 2018 (UTC)
Well then let's keep Connect to the Internet and revise it:

The installation image has a udev rule that enables the dhcpcd service for Ethernet network interfaces on boot. If you use Ethernet, verify the connection with ping:

# ping

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 systemctl stop dhcpcd@interface where the interface name can be tab-completed and proceed with Network configuration.

--Larivact (talk) 08:41, 28 August 2018 (UTC)
That looks good to me. -- Lahwaacz (talk) 14:57, 28 August 2018 (UTC)
(Copied from Below) I'd like to propose adding a sub-section to the Installation_guide#Connect_to_the_internet section, for quickly establishing a connection over wireless. As it stands, this section currently links to the Network_configuration/Wireless page. Although this has its uses, from the perspective of a new user simply looking to connect to the internet to perform the installation, it is not particularly helpful. As an alternative (or addition), I would prefer seeing simple instructions such as those with Iwd#Connect_to_a_network or NetworkManager#nmcli_examples (perhaps both?). I feel that, as long as it's made clear to the user this is a quick and temporary connection (does not persist in installed environment or between reboots) it would be helpful. CubeTheThird (talk) 17:13, 17 March 2020 (UTC)
Question; Why is there no reference to the handy boot-media tools wifi-menu noted in either the installation manual, or the page about configuring wifi? This makes it easy to set up wifi for installation...
I'd suggest it be added as a small note in the installation guide; something such as 'installation media provides the 'wifi-menu' script for wifi configuration' or something as such
Thoughts? —This unsigned comment is by Thenextdon13 (talk) 20:00, 31 December 2019‎. Please sign your posts with ~~~~!
For the moment I'm only briefly linking the edit that removed the last mention of wifi-menu from the guide, and the last state of the discussion that led there. -- Kynikos (talk) 13:45, 2 January 2020 (UTC)

Wording in example layout table and size of EFI partition

Wording in example layout table

Regarding Installation_guide#Example_layouts:

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. Regid (talk) 14:05, 29 December 2018 (UTC)

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. -- Alad (talk) 08:55, 30 December 2018 (UTC)
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. Regid (talk) 12:41, 30 December 2018 (UTC)
Perhaps call it "Principal part of the device" instead. NB the term "remainder of the device" is often used for a separate /home in other articles. --Indigo (talk) 21:33, 3 February 2019 (UTC)
Partioning disks mentions fdisk but better is gdisk /dev/sdX (x representing your drive. mine is sda) then running commands x, z, y, y after that run cgdisk Drillsar (talk) 01:04, 16 May 2019 (UTC)

Confusing partition numbers

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. Sabinscabin (talk) 20:29, 13 April 2019 (UTC)

Probably better to do it as [7] -- Alad (talk) 18:53, 1 May 2019 (UTC)

HiDPI on the console

With an ever increasing number of HiDPI displays, including at the begging of the article a section about adjusting the scaling factor or changing the font can be helpful, see HiDPI#Linux_console. Goetzc (talk) 02:21, 8 August 2019 (UTC)

It could be added as an example for setfont in Installation_guide#Set_the_keyboard_layout. The issue I have is that HiDPI#Linux_console mentions that tty2-6 may be unusable, while the Installation guide specifically instructs to change ttys as required in Installation_guide#Boot_the_live_environment. -- Alad (talk) 13:07, 7 September 2019 (UTC)
May be as an example for the line "See README.bootparams for a list of boot parameters" Installation_guide#Boot_the_live_environment, it could be specified to hit e button to edit the boot entry and add the following parameters to the boot line, like video=1920x1080 if you have HiDPI display. -- Xzorg6 (talk) 22:41, 15 December 2019 (UTC)
video= will just change the resolution. To get a bigger font on the console, you need CONFIG_FONT_TER16x32=y in the kernel config and fbcon=font:TER16x32 in the kernel command line. Since the official kernels don't enable CONFIG_FONT_TER16x32, someone will need to open a bug report asking for it. After that, the instructions for setting the fbcon=font:TER16x32 kernel parameter could be added to the wiki. -- nl6720 (talk) 06:52, 16 December 2019 (UTC)
linux 5.5.6.arch1-1 (currently in testing) has CONFIG_FONT_TER16x32=y (FS#64861). If if gets move to core before March, then the March iso will have it. It's probably a good idea to start drafting a tip to place in Installation guide#Boot the live environment. -- nl6720 (talk) 11:12, 26 February 2020 (UTC)
And just after I wrote this, the package was moved to core. -- nl6720 (talk) 11:27, 26 February 2020 (UTC)
I'm seeing multiple claims[8][9][10] that people with HiDPI screens are getting the TER16x32 font. I was not aware that the kernel chooses a font depending on screen size. Can anyone confirm that this really is the case? If it really works that way and unless FS#65680 messes this up, then there's nothing to add to the Installation guide about this topic. -- nl6720 (talk) 06:02, 11 March 2020 (UTC)
As per the decision to use ter16x32 is not based on screen size but only resolution.So even though a 1080p screen may be hidpi it does not use ter16x32 M.Srikanth (talk) 10:17, 11 May 2020 (UTC)
At least that part is now clear, thanks. The first step should be to get HiDPI#Linux console up to date. After that, as I've said before, a tip for the installation guide can be drafted. -- nl6720 (talk) 11:04, 11 May 2020 (UTC)
I fixed the page and removed the template M.Srikanth (talk) 12:25, 11 May 2020 (UTC)

First mention of /mnt in example partition layout

/mnt is mentioned at mount point in Installation_guide#Partition_the_disks, while /mnt is made explicit two sections later in Installation_guide#Mount_the_file_systems. As I recall it, this was changed because some users blindly copy pasted commands and mounted /boot on the live system, instead of /mnt/boot. Some options:

  • Introduce another column describing the mount point on the installed system.
  • Actually explain /mnt early.
  • Revert the "mount point" to not include /mnt.

-- Alad (talk) 13:03, 7 September 2019 (UTC)

I don't understand what's the actual problem here... -- Lahwaacz (talk) 09:36, 8 September 2019 (UTC)
From what I read on #archlinux-wiki, this comes from where the user was confused by the lack of root mountpoint (i.e. /mnt vs /). A question could be raised, if we should concern ourselves with users who have strong opinions about the wiki content yet can't be bothered to propose improvements in the talk pages...
About Alad's proposed options: I disagree with the first option, I think it will just complicate things even further. I support the third option and maybe adjusting the column header like in Special:Diff/581800.
I'd actually would like to go even further and change the commands run from outside chroot to be visually distinct, e.g.:
root@archiso # mount /dev/sdX1 /mnt
I think it would better solve the underlying issue.
-- nl6720 (talk) 15:26, 8 September 2019 (UTC)
I'm not overly fond of the longer column name. For the last proposed option, I may agree if this is formalized in Help:Style, so that it is not specfic to the Installation guide. -- Alad (talk) 11:20, 10 September 2019 (UTC)
Adding it Help:Style was my intention, since other articles, too, will need to use that style for some commands. I'm thinking of creating a template for it: Special:Permalink/581945. -- nl6720 (talk) 10:19, 11 September 2019 (UTC)
Sounds good to me, I'd just prefer the regular (non-bold) font for the prompt as above. -- Alad (talk) 21:54, 13 September 2019 (UTC)
Special:Permalink/582327. Are there any other opinions about creating such a template? Or should I take this discussion to Help talk:Template per Help:Template#Creation? -- nl6720 (talk) 18:31, 14 September 2019 (UTC)
  1. How are you going to call the template? This template would probably add to the Help:Template#Code formatting templates series, should it be named in a consistent fashion?
  2. Should this template support custom prompts, and if so, should it be called "pc" (from "(custom) prompted" code)?
  3. I don't like the red color too much, if bold is not an option maybe we can go green|purple|blue, something that recalls less a warning of some kind? Or can we just leave it with the default font color? Or a slightly fainter black?
  4. I haven't looked well into it, but maybe we can instead add an optional argument to Template:bc and Template:hc that prefixes a custom (colored) prompt? I wouldn't see a problem with repeating "root@archiso #" in every instance, or we may derive the new template from those two at that point.
  5. The template should probably be derived from Template:bc in any case, for simpler code, see User:Kynikos/Template:Sandbox2.
-- Kynikos (talk) 17:36, 16 September 2019 (UTC)
  1. Initially I was going to call it Template:Archiso since it would be Archiso-specific, but I'm starting to think that creating a more general-purpose template would be better. It could then be used in PostgreSQL and the [postgres]$ convention would get formalized in Help:Style. Now the issue is the [user@peer-a]# in Template:hc used in WireGuard. I'd rather not create two new templates, but I'm having trouble getting Template:Sandbox to work :(
  2. I like your "Template:pc" suggestion.
  3. Be glad I didn't post my first draft that was slightly more colorful. From your offered colors, I'd choose purple.
  4. I'd rather not mess with the established templates just for this change, so I'd prefer creating a new template.
  5. I didn't even think about using Template:bc. Is it a good idea to do that? The new template might need to be updated if Template:bc is ever changed in an incompatible way.
-- nl6720 (talk) 07:33, 17 September 2019 (UTC)
Yeah, after viewing your attempts and looking into it myself, I think modifying bc/hc is out of discussion, it would add too much code/style for so little use.
Thinking about this again one day after, I feel I'm realizing that my concerns in general may descend from the fact that we're going to create a template to represent (block) code, even though we already have 2 which basically do the same thing, including allowing to include a prompt; the only addition of this "Archiso" or "pc" template would be the formatting around the prompt, so why not keep it simple (I know, "simplicity" is often subjective and controversial) and instead either make a Template:Archiso to be used like {{bc|{{Archiso}} mount /dev/sdX1 /mnt}} or Template:ps (or Template:PS) to be used like {{hc|{{ps|root@archiso #}} mount /dev/sdX1 /mnt}}? They also work with Template:hc and space-prefixed code blocks!
Putting the choice of color aside, if the above idea of a standalone prompt template isn't welcome, I think my second choice would be to make two Template:pbc and Template:phc that work like {{pbc|$|ls}} and {{phc|$|ls|...}}, with the style rule to use them only in case of complex prompts. I'd still derive them from bc/hc to inherit any changes that we'd decide to make to them, and avoid repeating that ugly <pre> hack even more.
Otherwise I give up and accept the Template:Archiso that works like {{Archiso|mount /dev/sdX1 /mnt}}, in the hope that one day we won't need an analogous "hc" version.
-- Kynikos (talk) 14:24, 17 September 2019 (UTC)
I can't say I really like the idea of {{bc|{{Archiso}} mount /dev/sdX1 /mnt}} or {{hc|{{ps|root@archiso #}} mount /dev/sdX1 /mnt}}. I'd prefer creating Template:pbc and Template:phc.
I still don't get what's wrong with Template:Sandbox. It should just work:
prompt # command
-- nl6720 (talk) 04:43, 18 September 2019 (UTC)
FWIW (and a bit of fun) I've fixed Template:Sandbox, although I'm not sure if we really need that level of automation ^^ I stick to my position above, is there a third (or more) opinion? -- Kynikos (talk) 15:48, 18 September 2019 (UTC)
I think you like the #800080 shade of purple, right? ;-) Lahwaacz (talk) 11:39, 21 September 2019 (UTC)
Yes, I do like that one :D but I think it would be too bright for this template. -- nl6720 (talk) 11:52, 21 September 2019 (UTC)

Changes for the base package

Installations without base

The base group was replaced with the base package: [11] This change was reflected in Installation_guide#Install_the_base_packages with [12]

With [13], I removed the sentence "We only officially support installations that have the base package installed." because it opens a new rabbit-hole when something is "officially supported" in the installation guide, is not. With this sentence included, pretty much anything (including "installations" that are not, or only partially, followed from the Installation guide) may be supported merely from having the base package installed.

On the other hand, some notion that removing the base package results in an installation that is "not Arch" makes sense, but we should discuss on the best approach on doing this. -- Alad (talk) 10:22, 6 October 2019 (UTC)

How to write the image to a USB stick?

This is something the wiki page is silent about.

Only mention that "The image can be burned to a CD, mounted as an ISO file, or be directly written to a USB stick using a utility like dd." But this is still little information.

I must admit I've never learned the details of writing images to USB sticks. I always used high level tools for that. I thought there was no philosophy - simply write the image, that's all - so in Linux Mint I was always using their tool to write iso images to USB sticks.

Then I tried using this tool to write the Windows installer to USB. This suddenly didn't work. I learned that, contrary to what I had been believing, there were MANY ways an image could be written to USB and the Mint tool was only supposed to support writing Mint installers to USB, not other kinds of images. I ended up using Rufus to write the Windows installer which finally worked, although I did not learn which precise parameters were supposed to be set to which precise values and why. All I know is that *writing images to USBs is more complicated than I thought and that it seemed*.

For this reason, I find the recommendation to 'directly write the image to a USB stick using a utility like dd' confusing. Will it be valid if I type dd if=path/to/arch/installer.archlinux-2020.02.01-x86_64.iso of=/def/sdb, assuming that /dev/sdb is the USB stick? Or should I set some other parameters to something else?

I think that for the sake of completeness the wiki page should include an example of the dd command.

Kind regards, Kmph (talk) 14:12, 12 February 2020 (UTC)

The guide already links to USB flash drive, which shows a lot of the ways to write the iso to an USB, including dd, and covers much more than a simple dd example would. Grazzolini (talk) 14:31, 12 February 2020 (UTC)
IMHO the sentence that links to it is not constructed in the best way. It just lists possible booting options without telling the reader that they need to use any of them.
I think that we should add a "Prepare an installation medium" section between Verify signature and Boot the live environment. And explicitly state that a installation medium needs to be prepared using one of the available methods. Or maybe "medium" would not be the best choice, if PXE is listed among the options...
-- nl6720 (talk) 07:23, 13 February 2020 (UTC)

locale.conf for the rest of us

The locale.conf that the current page has sets LANG to en_US.UTF-8, the downside of this is that the imperial units are inherited for the vast majority of the world that do not live in English speaking countries. For instance in KDE, but also plenty of cli commands like `date` end up with output that is confusing when its different between countries. Date formats, commas vs dots in decimals. You name it.

The suggestion is to give an example where people get their own localization while setting the language to English, so apps (Gui as well as cli) still talk English. The suggested content would then be:


The suggestion at its base is to introduce the LANGUAGE variable because the default LANG-only is limited in usage to people wanting their computer to use their native language. Most of us are much more comfortable with English even though we don't live in an English-speaking country. It is not supported to use LANG=en_NL, seeing the LANGUAGE here is a great idea for the rest of us that grew up with English computers, but don't speak that natively. TomCat (talk) 18:19, 10 March 2020 (UTC)

LANGUAGE is non-standard and used only by GNU gettext. Also, all of this is non-essential and already described on the locale page which is already linked from the installation guide. The example in the installation guide is just an example - not a recommendation. -- Lahwaacz (talk) 18:37, 10 March 2020 (UTC)
gettext is rather univerally used by cli commands, additionally most of Gnome and indeed the KDE framework and thus all its apps use gettext. Lack of support can't be the reason to reject this, honestly. This suggestion is indeed to make the example show a little more than just LANG, as an example. Exactly because its not a recommendation is the introduction of the LANGUAGE variable useful. Naturally, if people prefer the LC_MESSAGES instead, thats all the same to me. TomCat (talk) 20:50, 10 March 2020 (UTC)
As mentioned, this is out of scope for the installation guide, closing. -- Alad (talk) 21:15, 14 March 2020 (UTC)

Refer to your motherboard's manual for details?

Part of the instructions says if you are missing the (non-essential) efi firmware files, that my system "may be booted in BIOS or CSM mode." It's clearly one of those (no "may" necessary) and that I should "Refer to your motherboard's manual for details.". Why? To find out what information? What should I do differently if my system booted in BIOS or in CSM mode? thanks Gcb (talk) 19:08, 24 March 2020 (UTC)

It may not boot at all if your motherboard does not support the BIOS mode. -- Lahwaacz (talk) 19:16, 24 March 2020 (UTC)

Placing boot loader section before pacstrap

It's my understanding that most boot loaders (e.g. grub, systemd-boot) should already be set up, with their partitions mounted to /mnt/boot, before the kernel is installed. Accordingly, it doesn't make much sense to me to have boot loaders as the last section. Why not move it up so it's just before "Install essential packages?" BigfootLives (talk) 16:52, 3 April 2020 (UTC)

On the contrary, you can't properly configure a boot loader until you decide which kernel will be installed. -- Lahwaacz (talk) 16:57, 3 April 2020 (UTC)

Link to the persian(Farsi) version

Hi At some point in the past i added link to persian version of this page but it is not present any more. As this page is locked it is no longer possible to add the necessery option to it. I would appreciate if you could help me. Риал Краесис (talk) 14:13, 10 April 2020 (UTC)

What is the link? -- Lahwaacz (talk) 14:28, 10 April 2020 (UTC)
there you goراهنمای_تازه%E2%80%8Cکاران
Риал Краесис (talk) 14:33, 10 April 2020 (UTC)
Thanks, now it's there. -- Lahwaacz (talk) 15:20, 10 April 2020 (UTC)
Thanks!Риал Краесис (talk) 15:28, 10 April 2020 (UTC)

Mention the Local Install Guide

It seems like in the top matter of the wiki version there should be a mention of the local install guide, in /root in the iso.

I know a lot of people have phones and such to read the wiki while installing, but it'd still be nice to know. I'm just learning it's and I've been an arch user for years.

M00n (talk) 16:02, 13 May 2020 (UTC)

Instructions on how to start GMP

I'd like to suggest that immediately following Update the system clock and before Partitioning the disk a section is added Enable GMP.

Something like:

If you have a mouse and wish to use it for copy and pasting, you can enable it with:

# systemctl start gpm

It took me days to figure this out, and it would have helped me to have a mouse from the start.

CarloWood (talk) 00:19, 4 May 2020 (UTC)

Buggy graphics driver

Can there be a hint that nomodeset parameter could be used if the graphics driver is buggy (I've heard nouveau may be buggy sometimes) M.Srikanth (talk) 04:47, 12 May 2020 (UTC)

Add a warning to #Localization

For Chinese users, they may want to set the locale to Chinese. These users may not know, which can lead to TTY garbled code. A warning should be added in this section to warn them that they should not be set to Chinese locale (just like the simplified Chinese version). -- Blackteahamburger (talk) 05:46, 12 May 2020 (UTC)

Add a reference in <#Partition the disks> to EFI formatting

As is, there's no hint as to how to format the EFI partition in this section or in the links, so I suggest we add that this line, See EFI system partition#Format the partition. —This unsigned comment is by Ttoirrah (talk) 07:03, 15 May 2020 UTC. Please sign your posts with ~~~~!

Installation guide#Partition the disks has two links to the EFI system partition article. Did you perhaps mean Installation guide#Format the partitions? -- nl6720 (talk) 09:42, 15 May 2020 (UTC)