From: Vagrant Cascadian <vagrant@debian.org>
To: Bone Baboon <bone.baboon@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Starting Sway a Wayland window manager
Date: Wed, 31 Mar 2021 15:41:17 -0700 [thread overview]
Message-ID: <87r1jvx7xu.fsf@yucca> (raw)
In-Reply-To: <87im57f2nr.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]
On 2021-03-31, Bone Baboon wrote:
> Vagrant Cascadian writes:
>
>> On 2021-03-29, Bone Baboon wrote:
>>> When I run `dbus-run-session sway` on virtual terminal 1 sway does not
>>> start and I get this output:
...
>> vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
>>> [backend/backend.c:303] Failed to open any DRM device
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> I think this is your fundamental problem. There's no DRM device
>> available (at least to your user). Are there devices in /dev/dri/, and
>> are they writeable by your user?
>
> What is the significance of the /dev/dri/ devices?
> Is /dev/dri/ related to the GPU of a computer?
> If there are no /dev/dri devices does that mean that the graphics card
> is not compatible with Linux-libre or Guix and that a Wayland window
> manager is not going to work?
Yes, you need /dev/dri for graphics acceleration to work, and wayland
needs at least basic graphics acceleration, as I understand it.
So missing/broken graphics drivers is the issue on two of your machines.
> I am trying to get Sway working on three computers.
>
> Computer 0:
> No /dev/dri/ directory.
> The sticker on the computer says AMD Radeon Vega Graphics.
> neofetch says the GPU is AMD ATI 05:00.0 Picasso.
>
> Computer 1:
> No /dev/dri/ directory.
> neofetch says the GPU is NVIDEA GeForce FX 5200.
Both NVIDIA and AMD have a history of not always having free
drivers/firmware/etc for their graphics hardware.
> Computer 2:
> Has a /dev/dri/ directory with devices that are writable by my user.
> noefetch says the GPU is Intel Mobile 4 Series Chipset.
And in my experience Intel chips usually work without problems...
> I have not got Sway working on computer 0 or 1.
>
> On computer 2 I am able to start Sway with `sway` on virtual terminal
> 1.
That's consistent with my assertion, then, at least. :)
So it sounds like you have sway configured correctly, but some of your
hardware may be incompatible with linux-libre.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-03-31 22:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 0:43 Starting Sway a Wayland window manager Bone Baboon
2021-03-28 1:05 ` jbranso
2021-03-28 1:30 ` Vagrant Cascadian
2021-03-28 2:27 ` Joshua Branson
2021-03-28 16:45 ` Joshua Branson
2021-03-29 13:53 ` Bone Baboon
2021-03-29 15:07 ` Joshua Branson
2021-03-29 3:19 ` Bone Baboon
2021-03-29 3:55 ` Joshua Branson
2021-03-29 13:45 ` Bone Baboon
2021-03-29 18:23 ` Vagrant Cascadian
2021-03-31 21:12 ` Bone Baboon
2021-03-31 22:41 ` Vagrant Cascadian [this message]
2021-03-29 3:14 ` Bone Baboon
2021-03-29 3:54 ` Joshua Branson
2021-03-29 15:37 ` raingloom
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=87r1jvx7xu.fsf@yucca \
--to=vagrant@debian.org \
--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).