Hi James,

Yes, packages are in sync with 6.9/packages.

The computer is relatively modern based on AMD Ryzen 4750U with integrated 
Radeon Graphics.

Radeon uses 
http://firmware.openbsd.org/firmware/6.9/amdgpu-firmware-20201218.tgz from 
/etc/firmware/amdgpu

So LibGL should load by MESA-LOADER: /usr/X11R6/lib/modules/dri without 
problems as I think. The firmware is actual and supports integrated Radeon 
since 6.9.

Maybe somebody knows what can affect on LibGl? I can't determine root of the 
problem.

Martin

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, May 16, 2021 1:08 PM, James Cook <falsif...@falsifian.org> wrote:

> On Thu, May 13, 2021 at 10:00:11AM +0000, Martin wrote:
>
> > By the way,
> > While running Firefox on OpenBSD host I have repeatedly appearing console 
> > messages like below:
> > ###!!! [Parent][MessageChannel] Error: 
> > (msgtype=0x6A0008,name=PMessagePort::Msg___delete__) Channel closing: too 
> > late to send/recv, messages will be lost
> > ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, 
> > messages will be lost
> > LibGl error: MESA-LOADER: failed to open radeonsi (search path 
> > /usr/X11R6/lib/modules/dri
> > LibGl error: failed to load driver: radeonsi
> > LibGl error: MESA-LOADER: failed to open swrast (search path 
> > /usr/X11R6/lib/modules/dri)
> > LibGl error: failed to load driver: swrast
> > Any advice is this normal or not?
> > Martin
>
> On my system at least, firefox tends to output some errrors on the
> console. I think some involved "Channel closing". If it would help, I
> can keep more careful track and report them to the list.
>
> The LibGl errors look less familiar. Stab in the dark: are your ports
> and system in sync? (I always run pkg_add -u after upgrading to a new
> snapshot.)
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> James


Reply via email to