unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Adriano Peluso <randomlooser@riseup.net>
To: Bone Baboon <bone.baboon@disroot.org>, help-guix@gnu.org
Subject: Re: h-node video card reporting
Date: Thu, 22 Apr 2021 10:21:35 +0200	[thread overview]
Message-ID: <be4a3e2e22bd6243a36ff72762464b5cf8df73be.camel@riseup.net> (raw)
In-Reply-To: <87lf9bpk6k.fsf@disroot.org>

Il giorno mer, 21/04/2021 alle 14.27 -0400, Bone Baboon ha scritto:
> As I have tested GPUs on five computers I would like to add my
> finding
> to h-node.
> 
> Is the lack of /dev/dri/ sufficient to put a GPU in the
> "does_not_work"
> category in video cards on h-node?
> 
> The h-node documentation says to test a GPUs 3D capability with
> `rss-glx` and `compiz`.
> https://h-node.org/wiki/page/en/How-to-test-your-hardware#Video%20Cards
> 
> Searching for `rss-glx` and `compiz` with `guix search` I do not get
> any
> results.
> 
> Would `rss-glx` or `compiz` work with a Wayland window manager?
> 
> What other ways can I test a GPUs 3D capabilities?
> 
> Is the ability to start Sway a Wayland window manager sufficient to
> put
> a GPU in the "works_without_3D" or "works_with_3D" category in video
> cards on h-node (based on the GPUs 3D capability)?
> 


I think the questions you asked about hardware support and updating the
docs about that would be better suited for the guix-devel mailing list

As far as I understand, the help mailing list is more for Guix users
and help with use cases

and the issues you are raising seem more as dev issues, to me





      reply	other threads:[~2021-04-22  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 18:27 h-node video card reporting Bone Baboon
2021-04-22  8:21 ` Adriano Peluso [this message]

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=be4a3e2e22bd6243a36ff72762464b5cf8df73be.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=bone.baboon@disroot.org \
    --cc=help-guix@gnu.org \
    /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.
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).