On Wednesday, May 20, 2020 2:10:14 PM CEST Dale wrote:
> Victor Ivanov wrote:
> > When the lbglvnd flag was introduced I remember I solved this issue by:
> >     # emerge --unmerge eselect-opengl
> >     # emerge -1qv mesa
> > 
> > After that, a simple update of @world rebuilt everything else on its own.
> > 
> > Personally, I had been waiting for libglvnd support for _a long time_.
> > This - and I mean GLVND in general - is something that should have come
> > to Linux many years ago, along with NVIDIAs PRIME render offloading.
> > 
> > 10y ago I used to have an Optimus laptop with an Nvidia GPU and it was
> > an absolute hell to get it running, I remember writing tonnes of scripts
> > using VirtualGL and a dummy X server running on the Nvidia GPU. This was
> > before bumblebee.
> > 
> > Today, I still need this with an external GPU.
> > 
> > But now it takes 1 environment variable to offload to the other GPU!
> > GLVND literally made my Linux work experience a million times better.
> > I'm extatic.
> > 
> > - V
> 
> My change went quite well here.  I removed the flag entry everywhere and
> then did a emerge world, with the correct options of course.  I then
> logged out, went to boot runlevel, reloaded the video drivers, went back
> to default and logged in.  I can't tell any difference here video wise
> tho. 
> 
> I did notice that my sddm problem is worse now.  It's worse now than it
> was when it first started.  In just a few hours it is consuming over
> 4GBs of memory.  That is ridiculous to me.  It using more than Firefox,
> both profiles, and any other software I have running.  I'm thinking
> about looking for a alternative to sddm.  I switched to it a while back
> but I don't like this memory hungry thing behaving this way. 

I missed the whole thing you are having with sddm, I just checked it on my 
laptop and not seeing anything like that.
Will reply further in the sddm-thread if I have any ideas.

--
Joost




Reply via email to