On 2022-03-15, Grant Edwards wrote:
>> I bit the bullet, let it depclean and rebooted.
>
> I'll give that a go the next time I'm in the office (which is where
> the machine in question lives).
It _almost_ "just worked". The names of the displays changed, so I had
to modify my xinit/openbox
I was under the impression that xf86-video-intel was for older video Intel
sets only...
Lee
On Mar 15, 2022 at 6:33 PM, Grant Edwards
wrote:
On 2022-03-15, Neil Bothwick wrote:
> If X doesn't come up, simply re-emerge xf86-video-intel. That won't take
> long because you will obviously
On 2022-03-15, Neil Bothwick wrote:
> If X doesn't come up, simply re-emerge xf86-video-intel. That won't take
> long because you will obviously have quickpkg'd it before depcleaning...
You would think so. And you would think that would fix it.
--
Grant
On Tue, 15 Mar 2022 19:24:02 - (UTC), Grant Edwards wrote:
> > I bit the bullet, let it depclean and rebooted.
>
> I'll give that a go the next time I'm in the office (which is where
> the machine in question lives). I've got to remember to drag a loptop
> along with me so that if X
On 2022-03-14, Neil Bothwick wrote:
> On Mon, 14 Mar 2022 17:07:54 - (UTC), Grant Edwards wrote:
>
>> I was a bit startled thos morning when emerge --depclean wanted to
>> remove xf86-video-intel. I presume this is a result of the switch to
>> the "built in" modesetting driver? And there are
5 matches
Mail list logo
