andreasdr Does anybody know what to do about this root user issue?

Are you a member of wheel? (Note the perms. of devices in /dev/dri/)

      andreasdr add user to "operators" group and try

      “Only the paranoid survive.”

      ― Harold Finch
      NetBSD VPS , NetBSD , OS108

        "Yes! it works" or "Yes! I'm in wheel"? If the latter, see that the xorg binary hasn't lost its setuid bit.

            andreasdr What's your GPU? Mine is still not working. Can you share your kernel file in /netbsd?

                Hi there, I needed to abort. Need a work station to get work done.
                But it looks very promising. The old problems(screen artifacts, ...) started again after using X with non root user.
                So DRM for AMDGPU works fine as long as you use it with root user.
                As NetBSD DRM developer I would investigate here.

                rvp My user always has wheel group. I needed to add the user to operator/operators/video group. Didnt check in details, just added all the groups to my user.

                • rvp replied to this.

                    Bruno I just enabled amdgpu? There are entries for that in GENERIC kernel conf which are commented out with "#" at the beginning of the corresponding lines.

                      andreasdr I needed to add the user to operator/operators/video group.

                      There's no operators or video group in NetBSD; and I don't see how adding yourself to operator would help when the /dev/dri/* devices are only RW to root and wheel. OTOH, losing the setuid bit on the Xorg binary would prevent it from working esp. with an explicit modesetting config. like in the 1st post.

                      I also don't see why running as root would make any artifacts vanish...

                          rvp NetBSD has operator (singular), much like FreeBSD. See groups. On a fresh NetBSD installation, I would typically add an "admin" user with users as primary group, wheel AND operator as secondary group, and a custom staff login class with lowered resource restrictions defined in /etc/login.conf.

                          That being said, I agree on every other observation you raised; the fact that screen artifacts are only encountered while starting X as standard user id curious at the very least (isn't X setuid anyway?).

                          • rvp replied to this.

                              I created the groups. Believe it or believe it not. Those were my observations. X as root did work 100% for multiple hours, whereas everything I tried else to get X as non root running with DRM failed with sudden screen artifacts and such. Please retest if you are interesting in helping.

                              • rvp replied to this.

                                andreasdr I created the groups. Believe it or believe it not.

                                Oh, I believe you created those groups, but, I don't think those're what helped in the end.

                                For the screen artifacts, I think tnn@'s insights from last year are more pertinent.

                                JuvenalUrbino NetBSD has operator (singular), much like FreeBSD.

                                As far as I can see (doing a find / \( -user operator -o -group operator \) ls -ld {} +), group operator seems useful only for a) taking dumps and b) shutting the system down. (And, even those are a bit hinky: shutdown is setuid root, and not setgid operator for instance.)

                                      rvp As far as I can see (doing a find / ( -user operator -o -group operator ) ls -ld {} +), group operator seems useful only for a) taking dumps and b) shutting the system down.

                                      Yes, I remember discovering this as I was experimenting with dumps from FFS snapshots. IIRC I also needed operator to read from disks mounted via amd(8) though.

                                      (And, even those are a bit hinky: shutdown is setuid root, and not setgid operator for instance.)

                                      On my system though I see:

                                      ~ $ stat -l /sbin/shutdown
-r-sr-xr-- 1 root operator 25392 Sep  8 11:07:19 2023 /sbin/shutdown