On Tuesday 24 April 2018 22:24:06 Alan Corey wrote:
> Don't know anything about that but on a Pi at least configuration
> files that get replaced in upgrades end up in ~/oldconffiles
>
> And I just got Valgrind working on a pi by building from source, never
> seen it work before. Source later tha
Uh-oh:
--- next part --
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: text/x-log
Size: 22331 bytes
Desc: not available
>From the x11 list. Just get it on your clipboard and paste it.
Xorg.logs normally have error messages, it's going to be hard to tell which
on
OK, I got it from somewhere, I'm on an xorg list too. Now I'm posting
to 3 lists by replying.
Watch the lines with (EE) in them, those are the actual error lines.
[ 331.529] (EE) modeset(G0): glamor initialization failed
[ 331.742] (EE) modeset(G0): drmSetMaster failed: Invalid argument
[
Greetings;
The vendors programmers are attempting to bring the dual Mali gfx
engines to life on this credit card sized arm64 board.
I am at the end of the text message phase of the bootup, getting a
black screen which I don't believe is vt7. I have a blinking underline
cursor, and anything tha
It looks to me like if both armsoc and modesetting are trying to use the same
GPU, acting like there are two separate GPUs. The modesetting fails to call
drmSetMaster on it, maybe because armsoc already did that first.
You could try if it gets better by disabling additonal GPUs by adding a
conf
