unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Bone Baboon <bone.baboon@disroot.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: Starting Sway a Wayland window manager
Date: Wed, 31 Mar 2021 17:12:40 -0400	[thread overview]
Message-ID: <87im57f2nr.fsf@disroot.org> (raw)
In-Reply-To: <878s65zumy.fsf@yucca>


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:
>>
>> ```
>> localhost dbus-daemon[380]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.24" (uid=1000 pid=26112 comm="sway ") interface="org.freedesktop.login1.Session" member="SetType" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=381 comm="/gnu/store/jdk3r1gs4d36n3aj9fscsvwwc9prnrzp-elogin")
>
>                           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?

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.

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.

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.

The relevant parts of the system configuration on computer 2 are:


```
  (packages
    (append
     (list
      sway ;Wayland window manager
      dmenu ;a selection utility that Sway can use to launch programs
      foot) ;a terminal emulator that works with Sway
     %base-packages))

  (services
   (append
    (list
     (service elogind-service-type))
   %base-services))
```


  reply	other threads:[~2021-03-31 21:13 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 [this message]
2021-03-31 22:41               ` Vagrant Cascadian
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=87im57f2nr.fsf@disroot.org \
    --to=bone.baboon@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=vagrant@debian.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).