User talk:Erus Iluvatar

From ArchWiki
Latest comment: 13 February by Erus Iluvatar in topic OVMF examples

Thank you

Thank you for your recent edit on Pipewire. I am new to ArchWiki and missed the correct formatting. Thanks for fixing it. Cheers! Darksaber (talk)

Don't worry, everyone has to start somewhere ;). If you want to read before future contributions, look at ArchWiki:Contributing#Resources. --Erus Iluvatar (talk) 13:23, 11 March 2022 (UTC)Reply[reply]

Minor edit mark

Thank you for your contributions to the wiki. Please mark your edits as minor when necessary, so readers can filter them with "non-minor edits" filter. Thank you. -- Thmeiov (talk) 12:17, 14 March 2022 (UTC)Reply[reply]

You're right, I should be more careful on this. Thank you for reminding me ! --Erus Iluvatar (talk) 12:30, 14 March 2022 (UTC)Reply[reply]

Thanks for the edits on the Virt-Manager page

Thanks for the recent edits you made im pretty new to ArchWiki/MediaWiki and suck formatting so thanks for fixing my bad formating ShinobuNarusaka (talk)

Hi ! Thank you for contributing a new page on a subject you're comfortable with. Don't worry, practice makes perfect. To double check your content before future contributions, look at ArchWiki:Contributing#Resources. --Erus Iluvatar (talk) 05:56, 27 March 2022 (UTC)Reply[reply]

$include Readline question

Hi, thanks for your work. I've seen that you have added a space in Readline#History. `man bash` (and some blogs) have no space in "$include /etc/inputrc". Do you have any reference? --Marzal (talk) 22:19, 14 April 2022 (UTC)Reply[reply]

Hi, thanks for pointing out my mistake: I had read the section too quickly and concluded this line was missing a space between the prompt and the command, but this is not the case. I've reverted my edit, sorry for the confusion. --Erus Iluvatar (talk) 03:43, 15 April 2022 (UTC)Reply[reply]

Thanks for improving the edit

Thanks for correcting the info, and naming it the 5000 series rather than Ryzen 9 or 5. AMD Ryzen series are even more ambiguous than Intel. AMD Ryzen 5xxx series processor could be Ryzen 5(5600x), Ryzen 9(5950x), or Ryzen 7(5800x). Currently using Ryzen 9 5950x and Ryzen 9 5900x on two of my desktops, on Windows they consume 100 watts less power and my current linux setup, so was looking into that article and was thinking of making the switch from Pop OS to Arch Linux. —This unsigned comment is by Gagan0123 (talk) 2022-06-17T04:56:21. Please sign your posts with ~~~~!

Hi! I saw the ambiguousness of the existing wording when finishing to revert your edit, so instead of having more people tripping on it I tried to make it better :)
Good luck on your journey ! --Erus Iluvatar (talk) 05:28, 17 June 2022 (UTC)Reply[reply]

Signature is unknown trust

Thanks for the edits! They made it easier to find the solution. --Topcat01 (talk)

Credit where credit is due: User:Lahwaacz did 99.99% of the work, I've only fixed a capitalization issue. --Erus Iluvatar (talk) 20:26, 29 July 2022 (UTC)Reply[reply]

Unified Extensible Firmware Interface/Secure Boot

Hi Erus Iluvatar, thank you for improving my contributions to the Unified Extensible Firmware Interface/Secure Boot article! Especially the formatting.

Do you think it is necessary to include an explanation what all the "basic" GRUB modules are doing, in the first code block? I couldn't find any good documentation about all these modules, I only found this thread on, which doesn't have all modules however and is already outdated. The official GNU GRUB manual has no documentation at all about the modules.

Do you think dividing the list of GRUB modules into these three parts, as done in the official Ubuntu build script, is meaningful, or is it arbitrarily / nonsensical?

Thank you in advance for an answer!

DasMenschy (talk) 12:30, 28 August 2022 (UTC)Reply[reply]

Hi! First of all, thank you for creating the content in the first place!
Regarding the creation of a dedicated section about GRUB modules: if you are motivated to create it, an explanation on GRUB modules would probably be a great fit for the GRUB page. I'm not sure where exactly it could fit though. Depending on the length, maybe creating GRUB/Modules could be appropriate? From a quick search in the page right now, nowhere do we explain what a "GRUB module" actually is even though we refer to them roughly 20 times!
Regarding the split into three parts: as for every classification, it is arbitrary, but nothing ever is truly neutrally written anyway :P It is logical given the reference material, and IMO feels like a good starting point for a reader trying to set up Secure Boot without wanting to include every existing modules.
Thank you again for your contributions.
--Erus Iluvatar (talk) 12:43, 28 August 2022 (UTC)Reply[reply]

Template:Archive in user pages


I saw your edits about Archive template in user pages, I put those following the discussion here because I didn't know of a better way to delete them. What's the proper way to get rid of those then ? Thanks ! (Bonne journée !)

-- Cvlc (talk) 15:01, 16 September 2022 (UTC)Reply[reply]

You're completely right to have followed the advice of User:Lahwaacz on that, I am not allowed to delete pages as a simple maintainer, I'll try to catch an Administrator to remove those.
Do you also want the User:Cvlc/Storage Layout and Alignment and User:Cvlc/Sector Size redirects deleted too?
As for a generic way to delete pages, as far as I know it is not possible even for you own pages… I'll see if we can document this properly somewhere.
--Erus Iluvatar (talk) 15:11, 16 September 2022 (UTC)Reply[reply]

You were right about /var filling up.

After testing for 2 weeks straight and installing/uninstalling random packages, it turns out that /var does in fact fill all the way up non-stop. Maybe that won't happen for a regular user because they wouldn't be spamming packages, but that's IMO enough for me to leave behind my suggestion of removing it off the Wiki, but yet again the decision is up to you whether it should stay on Partitioning or not. Cont999 (talk) 19:50, 20 September 2022 (UTC)Reply[reply]

I'm a little relieved to see that I was not completely missing the mark on the usage of /var :P
I'll be waiting for the result of the ongoing discussion at Talk:Partitioning#Separate /var: IMO keeping the sections as is should be good enough, but maybe a better wording on their actual relevance (or absence thereof) for a common setup can be achieved.
--Erus Iluvatar (talk) 20:05, 20 September 2022 (UTC)Reply[reply]


Thank you for the improvements you made to the pages I created! Steffo (talk) 02:27, 21 September 2022 (UTC)Reply[reply]

And thank you for creating the pages in the first place: I'm just trying to get the form to compliment the content :)
--Erus Iluvatar (talk) 05:46, 21 September 2022 (UTC)Reply[reply]

Thanks for the wiki page edits!

I intend User:Pongo1231/Arch on Steam Deck to be documentation of getting the Steam Deck UI fully working in Arch (alongside some opinionated sections like the Btrfs section), neither of which would obviously be a fit for Steam Deck. Of course I welcome any contributions to the page. :) -- Pongo1231 (talk) 22:14, 26 October 2022 (UTC)Reply[reply]

Thanks ! I was going to link to it in a forum exchange but it was referring to the now inexistant section of the official page, and I saw a few things I would have modified if the page was an official one, so I figured it would be good to update your guide, I'm glad you're OK with it :)
--Erus Iluvatar (talk) 05:11, 27 October 2022 (UTC)Reply[reply]

Thanks for signing my message

Thanks for signing my previously unsigned message, I'm new to this wiki and didn't know about this policy! Bean box69420 (talk) 20:53, 20 December 2022 (UTC)Reply[reply]

No problem, glad I could help :) --Erus Iluvatar (talk) 20:59, 20 December 2022 (UTC)Reply[reply]

ThinkPad Z13

Thanks for the revisions on my initial post. I also had not noticed the laptop guidelines earlier. The accessibility details about BIOS and beep codes, instructions for adding wacom file for the stylus, etc. should get added tonight or tomorrow. Soon, I plan to reformat, completely reset the BIOS, and reinstall Arch, so that should be a good opportunity to notice anything platform-specific that needs extra attention. I'll also bring anything notable in from the Lenovo Forums, as there are active discussions about current bugs and when/where to expect a fix. Take care! —PennRobotics 15:26, 21 February 2023 (UTC)Reply[reply]

Well, thank you for adding the content in the first place! I'm just helping formatting things uniformly to help readability as a whole :)
Don't feel rushed to add things, take all the time you need and don't hesitate to add to the dedicated page on a subject (e.g. Tablet PC#Stylus) if they are not providing the correct generic information or are unclear. Platform specific stuff should stay on the laptop page though.
--Erus Iluvatar (talk) 16:29, 21 February 2023 (UTC)Reply[reply]

Acer Swift 3

Thank you so much for pointing out what I was missing in Acer Swift 3 SF314-512. I am new to this wiki and did read the guidelines but missed the requirement on some sections. If you don't mind, any further revisions would be appreciated. 0xlogn (talk) 21:43, 21 February 2023 (UTC)Reply[reply]

I'm happy to have been helpful :)
Props for reading the guidelines, but there's always things that slip between the cracks: it still happens to me sometimes ^^
Do you want me to flag what I see as missing on the page or would you prefer that I list them here? (I'm going to sleep right now, will continue our exchange tomorrow)
--Erus Iluvatar (talk) 21:51, 21 February 2023 (UTC)Reply[reply]
Either way is fine for me. Might as well flag it on the page in the case that I don't get back to it. 0xlogn (talk) 22:13, 21 February 2023 (UTC)Reply[reply]
Done :)
Thank you again for your contribution! --Erus Iluvatar (talk) 07:19, 22 February 2023 (UTC)Reply[reply]
I can't seem to find the webcam or bluetooth in lspci or lsusb. Also, I know that Fn+F8 is a logout key, but I don't know how to trap the key and determine what it sends. Also (added/adding) the footnotes from the function keys table now. --0xlogn (talk) 16:34, 22 February 2023 (UTC)Reply[reply]
Thanks again :)
If the hardware probe is right, Bluetooth should be visible through USB: 8087:0033, the webcam should appear as a PCI device: 8086:465d.
For the keys, maybe try with a minimal environment like twm to avoid a possible interference from your desktop environment. See Help:Laptop page guidelines#Capturing function keys if it's being caught by systemd-logind instead.
--Erus Iluvatar (talk) 17:31, 22 February 2023 (UTC)Reply[reply]
Both of those IDs from the probe were correct. I was expecting a more detailed description than Intel Corp. (bluetooth) and Intel Corporation Device (webcam).
I'll try to do the key in a little bit. Thank you!
--0xlogn (talk) 17:50, 22 February 2023 (UTC)Reply[reply]
Thanks a bunch for double checking, I agree that the name used by lspci or lsusb is sometimes weird (e.g. some network card don't appear with their dedicated model number since they are close enough to an older one).
Take all the time you need, your page is already miles ahead of most "historical" ones (i.e. those created before having the laptop guidelines in place) :) --Erus Iluvatar (talk) 22:02, 22 February 2023 (UTC)Reply[reply]


Thanks for reviewing my changes on the Lenovo_Yoga_7i page, you definitely improved the presentation of the information a lot. Plus you helped me understand the mkinitcpio warnings too. My first time editing Arch Wiki went great!

Ask (talk) 23:50, 28 February 2023 (UTC)Reply[reply]

Thank you for taking the time to double check things with me :) --Erus Iluvatar (talk) 06:35, 1 March 2023 (UTC)Reply[reply]

Edits on the Dell G15 5525 Page

Hi, thanks for your review of the Dell G15 5525 Page! It is my first contribution to the wiki, and even though I read the guidelines, I have missed some recommendations. I updated the page, please let me know if there is any other info I should add!

—This unsigned comment is by Verge36 (talk) 2023-03-10T22:06:25. Please sign your posts with ~~~~!

Hi! Thank you very much for your contribution. As I had written in my edit summary, the very few things that were missing were minor details: I'm happy to see you came back and fixed everything :)
I've removed the style flag, but I also adjusted the hardware table, the PCI ID you had added for the microphone seems to be for an audio co-processor that is GPU-related (from the kernel config summary, it's related to "Yellow Carp" which is the codename for the Rembrandt family). I also used a Template:Yes for audio, since even if an unapproved kernel patch is needed, it's a simple addition to a list of hardware quirks, so nothing that should have unintended effect and the hardware works with the patch, so we can't say the support is "partial" as it's for parts that still do not work correctly with applied modifications.
Once again, a huge thanks, many hardware pages get much less polish than what you made!
Edit: You might also want to add an entry into Laptop/Dell#G15 to sum up the hardware support for your model :)
--Erus Iluvatar (talk) 22:20, 10 March 2023 (UTC)Reply[reply]

Thanks for tidying up

Thanks for sweeping up my half-asleep scrawl! Especially the battery part, I remembered that last and stuffed it in without checking the rest of the wiki first :D.

Much appreciated.

—This unsigned comment is by Muesli4brekkies (talk) 2023-03-27T07:21:26. Please sign your posts with ~~~~!

You're welcome :P
Thank you for taking the time to create the page, I've flagged a few things that are missing, I'll let you get to them when you find time :)
--Erus Iluvatar (talk) 07:30, 27 March 2023 (UTC)Reply[reply]

Sorry for messing up and thank you

Hi, sorry for messing up the VirtualBox/Install Arch Linux as a guest page. I read the page twice and didnt see that the stuff which I added was already on the page, i must have been pretty tired, sorry! And thank you.

DexyStorm (talk) 10:21, 18 April 2023 (UTC)Reply[reply]

Don't worry, if you did not see it it's probably because if was not at the best place in the logical reading order of the page, thanks for trying to improve the page anyway :)
--Erus Iluvatar (talk) 10:59, 18 April 2023 (UTC)Reply[reply]

Thank you for making my first Arch wiki's edit experience so amazing!

Thanks for helping fix the format in Lenovo ThinkPad X1 Carbon (Gen 11). I want to let you know that your help really makes my first edit in Arch wiki a really amazing experience. I was surprised to see my first page can really help others! I will continue to contribute other pages (and of course, I will pay attention to the format next time).

—This unsigned comment is by 1arch (talk) 2023-07-29T13:19:00. Please sign your posts with ~~~~!

I'm glad to see my edits have helped :)
Don't sweat too much on formatting, it's an easy fruit to pick for anyone, while adding content is less trivial.
Thank you for contributing !
--Erus Iluvatar (talk) 16:47, 29 July 2023 (UTC)Reply[reply]

Thanks for fixing my first wiki edit!

Thanks a lot for fixing my first edit by doing the right thing and extending the relevant section at the Emacs wiki instead!

I'm active on on multiple plumbing-layer linux projects, so I have a baseline to compare contributions experience to... and still, you made my first-hand experience amazing ;) --Darwi (talk) 20:57, 29 August 2023 (UTC)Reply[reply]

Thank you for adding the content in the first place! To be honest, at first I was trying to see how to make your solution work on more than GNOME, and stumbled upon the EmacsWiki page with exactly the complementary information ^^
I'm happy to see the solution I chose of having all the content in an external page was OK for you :)
--Erus Iluvatar (talk) 06:06, 30 August 2023 (UTC)Reply[reply]

Thanks for warm welcome

Hey Erus!

Thanks for your edit over my changes in Laptop/Other. I wanted to note as many things as possible as I recently ordered this magnificent device, and find that other people can't get it up and running. (talk) 11:43, 24 September 2023 (UTC)Reply[reply]

Thank you for the content addition :)
It reminds me that I really should update the table template (proposal at Template talk:Laptops table header#Add definitions to headers) to have a somewhere that documents what's expected in each column :P
--Erus Iluvatar (talk) 12:01, 24 September 2023 (UTC)Reply[reply]
That would be great, or some kind of an instruction how to put the information properly. Anyway, a reference on which device user has tested Arch would be also usable, I guess. In case there was a regression introduced on one package or another that prevents the device from working etc, user would have source of information. Maybe we should also think about having something like device pages like people from i.e. Lineage OS have, which version of kernel, from version... till... . IDK, just pondering :) (talk) 07:31, 25 September 2023 (UTC)Reply[reply]
Usually, only the model name and the date of the test is enough for most cases (e.g. saying it works with X processor is unnecessary, as the X+1 processor that was not tested is also likely to work, same for the kernel version which very rarely has regressions).
In the rare cases where there is a regression, we try to have it documented in a central point, e.g. Bluetooth#CSR dongle 0a12:0001.
For the dedicated pages, we have Help:Laptop page guidelines to create them, and I hope we never have to add information on a specific page with "X is supported from kernel version X to Y", as devices in the PC world should rarely become unsupported at the kernel level.
--Erus Iluvatar (talk) 08:42, 25 September 2023 (UTC)Reply[reply]
Sure! I've just added my Chuwi MiniBook X (2023) :). I will update it, as long as I find new issues and workarounds. It's a magnificent device. The one that I wanted - small, but powerful, and supporting (at least paritally :P) Linux / Android. It has it quirks (i.e. factory Windows 11 Installation did not recognize internal Wi-Fi. It can be no-go for "end-user".
However, sometimes old devices fall off the tree, but I believe those must be ancient one...
Anyway, I know that Arch is probably not the best distro for beginner (yet), but I hope my edits will ease it, at least a little :).
BTW. LOOOOOOOVE your nickname ;). (talk) 14:09, 25 September 2023 (UTC)Reply[reply]
Thanks :) --Erus Iluvatar (talk) 17:07, 25 September 2023 (UTC)Reply[reply]

Thanks for styling my topic on zram

Hi Erus,

Thanks, I didn't know the wiki constructs like {{hc| ... | ... }}. Now I learned something new. They are apparently templates. Is there a guide on which templates to use when on the arch wiki?

Also thanks for correcting my stupid typo I missed when proof reading. Rohoog (talk) 17:14, 17 October 2023 (UTC)Reply[reply]

Hi :)
Happy to see my style and wording edit was well received!
You can take a look at Help:Style and the various pages in the Help namespace :)
Always glad to be helpful :D
-- Erus Iluvatar (talk) 19:11, 17 October 2023 (UTC)Reply[reply]

Thanks for the BIOS flashing edits

First of all, thanks for all the style fixes to my section on getting a BIOS exe to work under Linux! I'm still pretty new to the Arch Wiki and I shouldn't have written it like a blog post.

To be honest though, I don't know how portable that advice is, which is why I set it aside as its own vendor-specific subsection. First of all, the innoextract step only applies to installers---ones that were made by a very specific installer set up tool. Second, the TDK extract step only applies to Phoenix TDK formatted firmwares. After all, it's just a firmware dev kit. When I search online for systems that have a Phoenix TDK BIOS, Lenovo is the only vendor that shows up. Third, the UEFI capsule format is also not a universal standard. Moreover, the firmware "device" itself might not be supported through fwupd.

Given how hacky the solution was for my one individual laptop, I don't know if it really deserves its own authoritative section with advice for other BIOS .exe's. Xenia (talk) 23:47, 10 November 2023 (UTC)Reply[reply]

Thank you for warning me, I had mistakenly assumed that since fwupdtool could be used with the UEFI capsule, your advice could be generalized to other vendors.
I'll move it back as a Lenovo-only solution.
Thanks again for adding the information in the first place!
-- Erus Iluvatar (talk) 06:54, 11 November 2023 (UTC)Reply[reply]

OVMF examples

I thought at first that you were only referring to my use of templating to include the user page, but I realised after subst'ing the page that you also were probably referring to the links to the other user subpages I made. I wanted to share the research and workarounds I made but didn't want them littering up an already unwieldy page. I can have another go at making the section for the Examples page a self-contained thing with as much relevant information as possible, but linking to the subpages I made for each different section feels important for clarity and I'm not sure how best to include that info. I appreciate the correction and the link to the style guide and hope to find a way my information can be included for future users. Alydev (talk) 13:35, 13 February 2024 (UTC)Reply[reply]

Given the sub-pages are mostly configuration files, these would probably be better as a single external link, e.g. on a dedicated repository from your GitHub while the explanations would still fit in PCI passthrough via OVMF/Examples?
P.S.: Thanks a bunch for wanting to share with others all the while trying to avoid cluttering an already huge page.
-- Erus Iluvatar (talk) 15:12, 13 February 2024 (UTC)Reply[reply]
I formatted the section for the Examples page and moved code snippets to GitHub. My primary anxiety in arranging things the way I did originally was avoiding link rot; I see the Arch wiki as a resource of Linux knowledge, and linking to external sites serving as effectively no more than a pastebin would seem to defeat this goal.
On writing the new section for the Examples page I did consider converting the markdown document from GitHub and putting it at PCI_passthrough_via_OVMF/Examples/Alydev, as then it would be in the wiki namespace and not the user namespace. But that felt a bit cheeky. Alydev (talk) 16:03, 13 February 2024 (UTC)Reply[reply]
The configuration info could also be generalised and applied to the relevant wiki pages, now I think about it. I'll make a note and see if I can adapt them for that purpose. Alydev (talk) 16:06, 13 February 2024 (UTC)Reply[reply]
Thanks again for the quick update :)
Looking through the page, most other entries seem to already have chosen either a code hosting platform or a pastebin to host the details, with only two of them being dead: if you're afraid GitHub could disappear, you can request an account on and host things there :P
Thanks for avoiding the cheeky solution :)
If you have the time, updating the relevant pages would be awesome!
-- Erus Iluvatar (talk) 17:13, 13 February 2024 (UTC)Reply[reply]