On 2019-10-02 18:49, Ken Moffat via blfs-dev wrote:
On Wed, Oct 02, 2019 at 05:40:28PM -0500, Bruce Dubbs via blfs-dev
wrote:
On 10/2/19 3:41 PM, Ken Moffat via blfs-dev wrote:
> On Tue, Oct 01, 2019 at 10:25:58PM -0500, Bruce Dubbs via blfs-dev wrote:
> > On 10/1/19 9:23 PM, Ken Moffat via blfs-dev wrote:
> > > On Wed, Sep 25, 2019 at 02:05:57PM -0500, Bruce Dubbs via blfs-dev wrote:
> > > > On 9/25/19 12:07 PM, Ken Moffat via blfs-dev wrote:
> > > As an aside, perhaps amdgpu (and maybe radeon) has a second issue - I
> > > was testing out systemrescuecd-6.03 the other day - it has a 4.19
> > > kernel and startx fails, trying to load radeon instead of amdgpu
> > > (Picasso vga is not recognized, I suppose). By 'installing' the
> > > stick's contents in RAM I was able to drop radeon and amdgpu, but
> > > then startx failed, it could not use the framebuffer which I guess
> > > was not surprising because it didn't know about the Picasso firmware.
> >
>
> And startx (as a user) still failed.
>
> Snippets from /home/ken/.local/share/xorg/Xorg.0.log
> So on amdgpu I definitely have a separate problem.
But it works as root, right?
Yes (I had to create a .xinitrc for root, but I've now done that and
proved it works). And I've now installed the suid workaround in the
wrapper, so that the build can progress.
> Debian bug (for sysvinit)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801605
> is on an amd or radeon machine, reply says logind needs to be
> running and working, apparently fixed for normal user by installing
> libpam-systemd and systemd-shim.
A long thread from 2016.
Indeed. Rootless xorg is new, but had been restricted to systemd.
> But someone else had a similar problem with AMD Mullins, not fixed
> by installing those, fixed by suid. Or alternatively fixed by
> enabling the root perms in the systemd wrapper.
As best I can tell, something in the AMDGPU driver appears to do
something
dependent on something in systemd. It is a lot to ask, but you might
want
to do a systemd minimal build through xorg to see if that works.
Another
option would be to try an inexpensive nvidia card to see if that gives
different results.
-- Bruce
Possibly also in radeon (my old phenom with the RS780 variant of
R600, and the R600 card I bought last year similarly fail).
Good evening folks
I found the following things out while looking online for solutions to
this problem earlier. It seems to be due to the way that permissions are
handled on card0, since AMDGPU/ATI drivers need access to a kernel
function that is only available if you are root. The Intel and Nouveau
drivers don't use modesetting in the way that AMD/ATI cards do.
https://ch1p.io/blog/1/ (WARNING: The Security Certificate expired on
10/1. The site and the links within (attached) are safe.)
https://stackoverflow.com/questions/29708596/drmdropmaster-requires-root-privileges
https://github.com/gch1p/drm_master_util
https://f.ch1p.io/fnHHUx0b/rootless_modesetting_1.20.3.patch
From what I gather, the patch puts a call out over a file descriptor and
socket to spawn a suid wrapper indirectly, which only affects AMD cards.
I'm not 100% sure if my interpretation is correct though, since this is
all so complex...
- Doug
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
