I am trying to set up a particular screensaver on a Debian Linux machine running Debian8 (jessie). It's quite an old laptop, but I've upgraded the memory from 500Mb (in the form of 2 x 256Mb modules) to 2Gb (in the form of 2 x 1Gb modules). This is the maximum permitted for this machine.
The screensaver (called 'pinion') starts OK but then stops, with an error message. One version of the error message occasionally appears in the terminal window where I started the screensaver with the command xscreensaver-demo (more on this later). The error message is:
WRITE DOMAIN RELOC FAILURE 0x1 6 4
WRITE DOMAIN RELOC FAILURE 0x1 6 4
pinion: ../../../../../../../src/mesa/drivers/dri/radeon/radeon_fbo.c:451: radeon_unmap_renderbuffer: Assertion `ok' failed.
Observing the behaviour in more detail, the screensaver starts OK after the designated delay (2 mins), but then stops, displaying over the frozen image the message:
WRITE DOMAIN RELOC FAILURE 0x1 6 4
WRITE DOMAIN RELOC FAILURE 0x1 6 4
pinion: ../../../../../../../src/mesa/drivers/dri/radeon/radeon_fbo.c:451: radeon_unmap_renderbuffer: Assertion `ok' failed.
xscreensaver: signal: 0: child pid 2233 (pinion) terminated with signal 6.
After a few minutes, the screen goes blank, and then after a few more minutes, the screensaver starts again, but freezes again as before. The pid number in the above message is different each time. The screensaver just keeps cycling like this.
I thought I would update the mesa drivers (having read the post
here).
Following this suggestion, I executed the command:
apt-get update && apt-get install libgl1-mesa-dev
then also:
apt-get install libglu1-mesa-dev
and
apt-get install freeglut3-dev
However, these updates and installs have not made any difference to the behaviour of the screensaver.
After each start or reboot of the machine, I start the screensaver with the command 'xscreensaver-demo'. I am prompted to set the screensaver daemon going, which I do. Eventually, I would like to find out how to set up this daemon automatically, so that the screensaver is active whenever the system is booted, but want to get it working properly first, before I automate it.
I have a feeling that this behaviour has started after the new memory modules were fitted, but I can't be 100% sure. The memory has tested OK.
The command 'free -m' results in the following output:
total used free shared buffers cached
Mem: 2023 992 1031 35 45 518
-/+ buffers/cache: 428 1595
Swap: 1021 0 1021
Any idea what's going on and what the remedy might be?