Hello Hakim,
Not sure if you have already tried xscreensaver-demo and tried random,
instead of the blank screen or single hack mode.
You could also pkill xscreensaver and rerun it like: xscreensaver -debug
-verbose 2> myoutput and send me the myoutput file.
From xorg.conf output it seems you have a single hack (single
screensaver) selected as the mode in your prefs and that hack
is failing due to some bug in the driver, causing a blank screen.
Hopefully you are still seeing the unlock dialog box and can
unlock your screen :-)
With random mode, and shorter cycle timeouts for hack changes you will
see the screensaver hacks that dont depend on AIGLX.
Alternatively you can turn the AIGLX hacks off through your
xscreensaver-demo prefs dialog or manually editing the
$HOME/.xscreensaver file.
Meanwhile someone else may have a better idea as to why i945 graphics
driver while working fine in NV build 68 is giving AIGLX errors in build 77.
I think the hacks are all in /usr/X11/bin/xscreensaver/hacks directory.
You could just run the hacks manually in a window like % atlantis -root etc.
See the man page on xscreensaver and type % hackname -help for hack options.
--mahmood
ps: Quite possibly since you reinstalled and the default mode is blank
screen, is the reason you may be getting no screen savers.
The AIGLX errors in xorg log may not be the real culprit for this
behavior ;-)
//
S. Hakim Hamdani wrote:
> Hello all,
>
> I recently upgraded from build 68 to 77 on my laptop with i945 graphics. My
> xorg.conf hasn't changed, it was already hand-tuned before the upgrade.
> Since, xscreensaver doesn't show any screensavers anymore, whereas other
> graphics output (e.g. mplayer) is just fine...
>
> The only warnings in my xorg log are:
>
> (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
>
> (WW) intel(0): Bad V_BIOS checksum
>
> (WW) AIGLX: 3D driver claims to not support visual 0x23
> (WW) AIGLX: 3D driver claims to not support visual 0x24
> (WW) AIGLX: 3D driver claims to not support visual 0x25
> (WW) AIGLX: 3D driver claims to not support visual 0x26
> (WW) AIGLX: 3D driver claims to not support visual 0x27
> (WW) AIGLX: 3D driver claims to not support visual 0x28
> (WW) AIGLX: 3D driver claims to not support visual 0x29
> (WW) AIGLX: 3D driver claims to not support visual 0x2a
> (WW) AIGLX: 3D driver claims to not support visual 0x2b
> (WW) AIGLX: 3D driver claims to not support visual 0x2c
> (WW) AIGLX: 3D driver claims to not support visual 0x2d
> (WW) AIGLX: 3D driver claims to not support visual 0x2e
> (WW) AIGLX: 3D driver claims to not support visual 0x2f
> (WW) AIGLX: 3D driver claims to not support visual 0x30
> (WW) AIGLX: 3D driver claims to not support visual 0x31
> (WW) AIGLX: 3D driver claims to not support visual 0x32
>
> I know where the first two come from and that they are irrelevant, but what
> about the latter ones? Lies therein maybe a clue as to why my xscreensaver
> won't work anymore? I get no errors from it, just the screensaver remains
> "blank".
>
> Many thanks, cheers, Hakim
>
>
> This message posted from opensolaris.org
> _______________________________________________
> xwin-discuss mailing list
> xwin-discuss at opensolaris.org
>
