unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso--- via Guix-patches via <guix-patches@gnu.org>
To: pelzflorian@pelzflorian.de, 58357@debbugs.gnu.org
Cc: efraim@flashner.co.il
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Sat, 08 Oct 2022 15:33:25 +0000	[thread overview]
Message-ID: <3132924a6c819b24e814f67b1e3b75da@dismail.de> (raw)
In-Reply-To: <87czb2ljvt.fsf@pelzflorian.de>

October 8, 2022 5:56 AM, "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:

> Hmm Joshua, recommending these thinkpads may be good or may be bad.

Thanks for the response Florian!  I'm a bit curious.  Do you think that
I should try to re-word what I've said?  I can resend another patch, if
you think it appropriate.
 
> Off-the-shelf hardware too often is at odds with freedom, and newcomers
> underestimate how hard it is to find hardware.

Can you give me some examples of "bad thinkpads"?  Perhaps really new 
ones?  I'm honestly a little torn about what hardware to recommend to
newcomers to Guix System.  I cannot maintain my integrity and recommend
a librebooted laptop.  I use an osbooted Thinkpad, because with the
cpu microkernel updates, the laptop is SOOO much more stable.  
My librebooted laptop would crash whenever I tried doing video editing.

Perhaps we should list sellers that sell hardware with Guix system
pre-installed.  I see in reddit, people asking with some frequency
what hardware they should buy for Guix System.  It would be nice to 
at least recommend some specific hardware.  :)  I think the current
manual is too vague for newcomers.  Just my 2 cents.

Or maybe this wiki page may be of use:

https://wiki.parabola.nu/Computers

> Joshua Branson via Guix-patches via <guix-patches@gnu.org> writes:
> 
>> * doc/guix.texi (Hardware Considerations): add a reccomended system and a
>> short commentary about graphics cards.
> 
> For graphics cards <https://issues.guix.gnu.org/36786> “Warn of AMD GPUs
> unusable with Guix System” is related. As Ricardo said there, we do
> point to h-node.

Thanks for pointing me to that!

> 
>> +@cindex Graphics Cards, hardware support
>> +Graphics cards have a hard time running properly under linux-libre,
>> +because those drivers usually require propritary firmware, which
>> +linux-libre removes. Users should avoid brand new graphics cards.
>> +Older Kepler Nvidia graphics cards and integrated Intel GPUs work the
>> +best.
> 
> It would be bad to make recommendations that end up not working. I have
> doubts if new Intel GPUs is a safe advise.

I can re-word to to say "old integrated Intel GPUs".  I'm not sure how
old I should say though.  5 years?  Will the Intel Arc graphics cards
be FYF or do they have a binary blob.  I don't actually know...

> 
>> +For the best Guix System experience, Guix developers recommend an X86_64
>> +system with at least 2GB of RAM. An old Thinkpad in the T or X series
>> +is usually a good choice. If you decide to run Guix System on ARM or
>> +Power architectures, then please use a system with a 64 bit CPU.
> 
> IMHO ARM and Power need not be mentioned so explicitly. On the website,
> there is no Guix System download link for ARM except the Pinebook image
> (I don’t own a Pinebook and can’t test that). Guix on ARM works well,
> now that rsvg works on ARM.

How recent was that?  That rsvg started working on ARM  ?

> 
> And once there is a new release, bordeaux will be enabled by default,
> then Guix on ARM will be much better even by default.

I certainly hope so!

> Regards,
> Florian




  parent reply	other threads:[~2022-10-08 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yz/FHD608HeU6iIM@3900XT>
2022-10-07 14:24 ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55   ` pelzflorian (Florian Pelz)
2022-10-08 15:33   ` jbranso--- via Guix-patches via [this message]
2022-10-10 10:07     ` pelzflorian (Florian Pelz)
2022-10-14 15:12       ` Ludovic Courtès
2022-10-14 15:47         ` kiasoc5 via Guix-patches via
2022-10-15  9:47           ` pelzflorian (Florian Pelz)
2022-10-16 11:53             ` pelzflorian (Florian Pelz)
2022-10-14 17:09         ` pelzflorian (Florian Pelz)
2022-10-15 15:51           ` pelzflorian (Florian Pelz)
2022-10-17 16:35           ` Ludovic Courtès
2022-10-14 19:28         ` jbranso--- via Guix-patches via
2022-11-03 19:21         ` Ludovic Courtès
2022-11-16  0:22   ` pelzflorian (Florian Pelz)
2022-11-16 23:16     ` jbranso--- via Guix-patches via
2022-11-17 16:26       ` pelzflorian (Florian Pelz)
2022-11-19 14:06         ` Joshua Branson via Guix-patches via
2022-12-08 17:02           ` pelzflorian (Florian Pelz)
2023-03-09 21:06     ` pelzflorian (Florian Pelz)
2023-08-20 17:44       ` pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3132924a6c819b24e814f67b1e3b75da@dismail.de \
    --to=guix-patches@gnu.org \
    --cc=58357@debbugs.gnu.org \
    --cc=efraim@flashner.co.il \
    --cc=jbranso@dismail.de \
    --cc=pelzflorian@pelzflorian.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).