User talk:Francoism

From ArchWiki

Splitting edits

Hey Francoism, thank you for contributing :) I wanted to talk about a couple of edits you've just made, [1] and [2]: when moving content, each move should be done in its own edit (the same edit, not cut in one and paste in another), without changing the content; only once the content is in the new place, it can be modified in a following separate edit; this is to ensure that every diff is understandable and it's always possible to determine what is the source of every piece of information.

You may be interested in reading ArchWiki:Contributing#Do_not_make_complex_edits_at_once and Help:Procedures#Move_a_section_within_the_same_page.

Another tip: you can use [[internal links]] in edit summaries, which is often very useful to point to related pages (e.g. when moving content to or from somewhere) or discussions.

Cheers — Kynikos (talk) 06:28, 9 March 2016 (UTC)Reply[reply]

Hi Kynikos, thanks for your input. I will be moving sections as preferred from now one.
Sometimes I simple forget to click on edit in the top-navigation and simple edit the sections separately instead.
Didn't know it was possible to use internal links, will read ArchWiki:Contributing for a second time. :)
Francoism (talk) 09:48, 10 March 2016 (UTC)Reply[reply]
Hi, thank you as always for helping looking after this wiki! I thought I'd remind you of the possibility to link to articles in edit summaries, for example it would have been useful in [3] to show that the content comes from [4] and it's not a new addition :)
Then, well, while I'm here for the sake of fairness I have to point out that splitting that move and [5] would have made it easier to understand the diffs for the users watching those pages ;)
Cheers -- Kynikos (talk) 15:36, 23 August 2017 (UTC)Reply[reply]

Typo in your talk page link

Just wanted to let you know, there is a typo in your talk page link in ArchWiki:Maintainers. -- nl6720 (talk) 10:04, 18 October 2016 (UTC)Reply[reply]

Thanks! Fixed. :) Francoism (talk) 10:09, 18 October 2016 (UTC)Reply[reply]

systemd page

Why did you revert my change? I just tested, you don't need the -f to override a previously-set default target. "systemctl set-default" will set the default regardless if it's been already set. --Chowbok (talk) 13:38, 20 March 2018 (UTC)Reply[reply]

This should first be discussed in Talk:Systemd.
Francoism (talk) 15:36, 20 March 2018 (UTC)Reply[reply]
This wouldn't be necessary if you at least tried it before hitting a button. If you can't think of a good reason to revert an edit, don't. -- Lahwaacz (talk) 17:44, 20 March 2018 (UTC)Reply[reply]
@Chowbok and @Lahwaacz: Sorry for the revert! I thought the force overwrite flag was necessary to overrule the init level.
Francoism (talk) 18:09, 20 March 2018 (UTC)Reply[reply]

NVIDIA page - crash on autogenerating xconfig using GDM

Hello! You've asked for reference in order to approve my edit. Should I post a topic on the forums with my issue and give that as reference? Opptur (talk) 16:34, 1 May 2018 (UTC)Reply[reply]

Please sign your comments. :)
It may be a bug, if not reported already, report upstream.
Good idea to first ask on the forums thought.
Francoism (talk) 16:31, 1 May 2018 (UTC)Reply[reply]
Sorry, I didn't pay attention to the header in this page. I have created a bug report here [6].
Opptur (talk) 18:00, 1 May 2018 (UTC)Reply[reply]
Doesn't seem to be a bug thought, this is the reason why no (auto-)generated Xorg config are being created anymore.
You should simple create a /etc/X11/xorg.conf.d/10-monitor.conf and/or /etc/X11/xorg.conf.d/20-nvidia.conf if you want to overrule settings, see Xorg and NVIDIA. Also consider asking the forum for help. Good luck!
Francoism (talk) 19:09, 2 May 2018 (UTC)Reply[reply]


Hi Francoism,

You recently added instructions for how to enable AMD DC at AMDGPU, but according to this Phoronix article, it should be enabled by default. Do you know if that article is incorrect?

Also, we refer to Sea Islands (CIK) as GCN2 at Xorg#AMD as does Wikipedia at w:Graphics Core Next. AMD has indeed previously called it GCN1.1, but I think we should keep our usage consistent.

Lonaowna (talk) 19:02, 28 June 2018 (UTC)Reply[reply]

Hi Lonaowna,
I am also confused about this, is this logged in dmesg and/or any other file?
Thanks for the suggestion! I was confused about GCN1/GCN1.1 thing, so I agree this is a better option.
Francoism (talk) 09:17, 29 June 2018 (UTC)Reply[reply]
I'm not sure how to test it; I don't have an AMD GPU myself. Looking at the source code, it seems that by default DC is used by default for CHIP_HAWAII (=GCN2/CIK) and newer, and can be enabled with the amdgpu.dc option for CHIP_BONAIRE,CHIP_KAVERI,CHIP_KABINI and CHIP_MULLINS. I don't know which cards that are, but it seems that the switch is not needed for Hawaii and newer.
Lonaowna (talk) 17:21, 29 June 2018 (UTC)Reply[reply]


Note that here you did more than what the edit summary said: you've removed one note and one out-of-date flag. See ArchWiki:Contributing#Do_not_make_complex_edits_at_once.

Since I can't undo this and similar changes selectively, I'll revert it all. Please try again with better splitting and better summaries.

-- Lahwaacz (talk) 21:22, 19 November 2018 (UTC)Reply[reply]

Regarding an old edit you made to KDE article

in this edit, you removed certain keywords from the KDE#Themes section that used to describe the easiest method of installing themes. That makes it seem like using the repositories is now more preferable than using this previously-called "easiest method."

However, in the same article, the KDE#Widgets section had the exact same keywords to describe the easiest method of installing widgets, which was literally the exact same as installing themes. But you only made these changes for the KDE#Themes section while ignoring and leaving KDE#Widgets the way it is, which contained the exact same words that described that same process as being the easiest (until a few hours ago, I removed the same keywords that you got rid of in the other section to keep the whole article consistent).

I'm wondering why you only made these changes to KDE#Themes and not KDE#Widgets? Did you miss it, or was that edit meant to be this way to imply that this method is only easier with KDE#Widgets?

If KDE#Widgets was meant to include those words to describe the process and the changes only applied to KDE#Themes, then I'll undo my changes. Thanks! Cont999 (talk) 15:50, 14 September 2022 (UTC)Reply[reply]