On Thu, 28 Jul 2022 at 12:38:10 -0500 (CDT), John D. Baker wrote:
> I updated my -current install to shortly after the GCC 10.4 update,
> doing a non-update build on everything. I then rebuilt all my extra
> packages.
>
> Logging via xdm using the failsafe mode, the in-tree 'ctwm' works
>
mrg@ wrote:
> > > (1) out of bounds problem in xserver/hw/xfree86/modes/xf86Crtc.h
[snip]
> this looks simple enough to just do.
> > > (2) "-flipPixels" option removal
[snip]
> go for it.
Both committed. Thanks!
https://mail-index.netbsd.org/source-changes/2022/07/30/msg140050.html
> > (1) out of bounds problem in xserver/hw/xfree86/modes/xf86Crtc.h
> >
> > OpenBSD/luna88k maintainer (Kenji Aoyama) reported the following fix
> > was neceesary for non-XFree86 driver based dumb server (on luna88k etc.):
> > https://gist.github.com/ao-kenji/afb0ea5b6dca04975161f84ab41ba32b
>
I wrote:
> mrg@ wrote:
>
> > i've updated most of xsrc to their latest versions.
> > fontconfig and Mesa are remaining. i've tested the
> > new code on amd64 and arm64, and built several ports
> > to confirm they still build. the biggest change is
> > the new xorg-server.
>
> On 1.21.x, I'm
On Mon, 2022-07-18 at 21:23 -0400, David H. Gutteridge wrote:
> On Mon, 2022-07-18 at 07:17 +1000, matthew green wrote:
> > > can you post the whole Xorg.0.log somewhere? most of
> > > my i915 systems have become non-functional the last few
> > > years, but i have one system to test.
> >
> >
On Sun, 2022-07-17 at 00:28 -0400, David H. Gutteridge wrote:
> Separately, libX11 added a feature called "thread safety constructor"
> which we have enabled. It can cause hangs with X11 clients that aren't
> coded safely. This did include xfce4-settings from Xfce until the
> version I pushed to
Robert Swindells writes:
>
> I wrote:
> > It looks like not all the functions are getting setup in the glamor
> > struct by load_glamor(), I'm guessing because those functions are
> > not exported by libglamoregl.so.
> >
> > Do we need to add more source files to this:
> >
> >
Martin Husemann wrote:
>
> Does anyone happen to have firefox-102.0.1nb1 installed and not yet
> updated the X server and Xlib?
Have rebuilt firefox-102.0.1, works fine with the old X stack.
I wrote:
> It looks like not all the functions are getting setup in the glamor
> struct by load_glamor(), I'm guessing because those functions are
> not exported by libglamoregl.so.
>
> Do we need to add more source files to this:
>
>
matthew green wrote:
>
> with a normal build, you should at least be able to get
> a stack trace with function names, if not line numbers.
The last function name that I get is drmmode_init().
Comparing the updated source with the working version shows this:
{
#ifdef GLAMOR_HAS_GBM
I have a minor (but strange) issue with the new X setup.
My Radeon amdgpu does not fully work yet (strange colours, some drawing
artifacts, otherwise mostly ok), so I am using vesfb and wsfb_drv
(but the same effect happens with the amdgpu driver).
I hadn't updated firefox before the X server
Robert Swindells writes:
>
> I wrote:
> >
> >>> [ 378.033] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x44) [0x1467d46d5]
> >>> [ 378.033] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x79) [0x1467d0465]
> >>> [ 378.033] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0)
> >>> [0x75b46379c930]
>
I wrote:
>
>>> [ 378.033] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x44) [0x1467d46d5]
>>> [ 378.033] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x79) [0x1467d0465]
>>> [ 378.033] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0)
>>> [0x75b46379c930]
>>> [ 378.034] (EE)
>>> [ 378.034]
> can you post the whole Xorg.0.log somewhere? most of
> my i915 systems have become non-functional the last few
> years, but i have one system to test.
unfortunately, my system (kaby lake, GT 630) seems to work
fine with xorg-server 21.1.4 for me.
>> [ 378.033] (EE) 0: /usr/X11R7/bin/X (xorg_backtrace+0x44) [0x1467d46d5]
>> [ 378.033] (EE) 1: /usr/X11R7/bin/X (os_move_fd+0x79) [0x1467d0465]
>> [ 378.033] (EE) 2: /usr/lib/libc.so.12 (__sigtramp_siginfo_2+0x0)
>> [0x75b46379c930]
>> [ 378.034] (EE)
>> [ 378.034] (EE)
> TL;DR: after upgrading via the sets available from releng builds from
> July 16th (http://releng.netbsd.org/builds/HEAD/202207160630Z) I'm not
> able to start X on amd64 with i915 graphics. Separately, there may be
> issues with libX11 1.8.1 where clients will hang due to recursive locks
>
On Fri, 15 Jul 2022 at 15:12:07 +1000, matthew green wrote:
> i've updated most of xsrc to their latest versions.
> fontconfig and Mesa are remaining. i've tested the
> new code on amd64 and arm64, and built several ports
> to confirm they still build. the biggest change is
> the new
Hello,
On Fri, 15 Jul 2022 15:12:07 +1000
matthew green wrote:
> i've updated most of xsrc to their latest versions.
> fontconfig and Mesa are remaining. i've tested the
> new code on amd64 and arm64, and built several ports
> to confirm they still build. the biggest change is
> the new
Thanks for your work.
mrg@ wrote:
> i've updated most of xsrc to their latest versions.
> fontconfig and Mesa are remaining. i've tested the
> new code on amd64 and arm64, and built several ports
> to confirm they still build. the biggest change is
> the new xorg-server.
On 1.21.x, I'm afraid
19 matches
Mail list logo
