Re: xscreensaver PLIST errors

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

Yesterday night I tested it again. It's very strange - If I run one of
the simple - even not OpenGL - screensaver, like anemone, with
'-root', IT does not actually show anything on screen. even if I think
it is working - a ktruss shows the expected sequence, similar to it
being invoked in a window (which works as normal). It is as if the
root window where it is supposed to display to is created under the
current window manager (the test was done under the latest available
in pkgsrc MATE).

On Wed, 22 Jan 2020 at 13:53, David H. Gutteridge <david%gutteridge.ca@localhost> wrote:
>
> On Sat, 18 Jan 2020 at 23:46:30 +0000, Chavdar Ivanov wrote:
> > That's fine now; I usually build it with GL enabled. The individual
> > programs in /usr/pkg/libexec work just fine when invoked on the
> > command
> > line or in the small preview of xscreensaver-demo, but if I run them
> > full-screen, I get either a message from Mesa that the device could
> > not
> > be recognized, or a black screen with the mouse cursor (working) and
> > nothing else - I even can't switch to another console with Ctrl-ALT-Fx
> > and had to ssh into the machine to reboot - killing all running
> > programs
> > related to it did not solve it (the program itself, xdcreensaver[-
> > demo],
> > X, gdm - the screen stays the same).
> >
> > This is on 9.99.39 amd64, the laptop has Intel 530 graphics; from
> > dmesg:
> >
> > ...
> >
> > nouveau0 at pci1 dev 0 function 0: NVIDIA product 139a (rev. 0xa2)
> > i915drmkms0 at pci0 dev 2 function 0: Intel HD Graphics 530 (GT2)
> > (rev.
> > 0x06)
> > nouveau0: info: NVIDIA GM107 (1171a0a2)
> > nouveau0: autoconfiguration error: error: bios: unable to locate
> > usable
> > image
> > nouveau0: autoconfiguration error: error: bios ctor failed, -22
> > nouveau0: autoconfiguration error: unable to create nouveau device: 22
> > i915drmkms0: interrupting at ioapic0 pin 16 (i915drmkms0)
> > kern error:
> > [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.
> > c:636)i915_firmware_load_error_print]
> > *ERROR* kern error:
> > [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/intel_guc
> > _loader.c:560)guc_fw_fetch]
> > *ERROR* Failed to fetch GuC firmware from i915/skl_guc_ver4.bin (error
> > -2)
> > failed to load firmware i915/skl_dmc_ver1.bin (0)
> > kern error:
> > [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_drv.
> > c:651)i915_firmware_load_error_print]
> > *ERROR* The driver is built-in, so to load the firmware you need to
> > kern error:
> > [drm:(/home/sysbuild/src/sys/external/bsd/drm2/dist/drm/i915/i915_gem.
> > c:5419)i915_gem_init_hw]
> > *ERROR* Failed to initialize GuC, error -5 (ignored)
> > intelfb0 at i915drmkms0
> > intelfb0: framebuffer at 0xffff96014dac0000, size 1920x1080, depth 32,
> > stride 7680
> > wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation),
> > using wskbd0
>
> I'm not able to duplicate that with my amd64 -current test laptop. It
> runs random OpenGL screensaver choices generally without issue. (There
> are times when an individual one will cause a core dump, but that
> doesn't bring anything down.) The distinction may be that mine has older
> Intel graphics than yours (HD4000).
>
> Regards,
>
> Dave
>
>


-- 
----