Xorg Wizard: 24-bit depth only

I am planning to remove the choice of 16-bit or 24-bit color depth in Xorg Wizard, and choose 24-bit only.

This is one less thing to decide. However, my main reason is that gmplayer does not work at 16-bit color depth -- I previously thought that this was also a JWM problem, but have found it is the same, get black windows in other window managers also.

JWM did have some problems awhile back with 16 versus 24 bit depth, but the latest version has fixed that.

If anyone has a reason for the Xorg Wizard to continue to offer a choice, please respond.

Posted on 31 Aug 2010, 12:03


Posted on 31 Aug 2010, 12:55 by broomdodger
foxit needs 24-bit, FlSynclient error
foxitreader also needs 24-bit (crash on 16-bit)


Just tried to open FlSynclient, error Can't access shared memory area. SHMconfig disabled?

What does that mean?
Known error?

Posted on 31 Aug 2010, 13:54 by Sage
8, 12,16,24,32?
This leaves me wondering whether this distro wouldn't be following a frequent trend claiming to be progressive, no doubt,and treading a path to its own demise?
An unscientific analysis of what folks are actually using Puppy for on the Forum, not just the most voluble from that certain nation, is to liberate yesteryears' HW from an early and untimely crushing. That is the strength of the compact distros. In those instances, the acid test might be: does it run 640x 480 on a 4Mb PCI video card - or at all?
Of course there's VESA, but that has had its own uncertainties and issue in recent years.
If ever there was a time for navel gazing, this must be it? Is 'retro' the new tomorrow?! Truly a watershed.

Posted on 31 Aug 2010, 15:17 by Rider1
16-bit necessity
Please keep the 16-bit depth in Xorg Wizard. It allows my P3 i815 box to drive a 1920x1080 monitor at full resolution, something that Intel's Windows XP video driver is incapable of doing! I suspect the 915 resolution hack permitted this amazing occurrence.
Currently running on Luci 219, multi-session live cdrw. Previously on Puppy 4.30 (

Posted on 31 Aug 2010, 16:41 by Terryphi
Default to 24-bit?
Why not retain the 16-bit option for those who need it but default to 24-bit? 16-bit can then be offered with a health warning about what it breaks.

Posted on 31 Aug 2010, 17:00 by gjuhasz
24-bit vs 24-bit
Some video cards report 32-bit capability as 24-bit. In this case, xorgwizard displays two 24-bit options and the user can select between the real 24-bit or the 32-bit resolution (and 16-bit, too).
In this aspect, depth selection should remain the user's choice with the highest as the default.

Posted on 31 Aug 2010, 19:21 by ICPUG
flsynclient 'error'

The 'Can't access shared memory area. SHMconfig disabled?' message is not an error as such.

if you manage to find the documentation for synclient (on which flsynclient is based) it will tell you that SHMconfig has to be enabled for it to work.

If you have a manually configured xorg.conf in use then SHMconfig should be defined as enabled in it somewhere for flsynclient to work. Not sure what happens when Xorg is configuring automatically.

Posted on 31 Aug 2010, 20:21 by BarryK
re synclient
The Xorg Wizard does create a synaptics section in xorg.conf, with this entry:

Option "SHMConfig" "on"

Posted on 31 Aug 2010, 23:07 by JonT
re re synclient
While "SHMConfig" "on" likely is a fix for most cases, sadly that is not always the case. For example, for me, Wary 060 video works properly with "i810" but synclient does not. With my Intel graphics, I can pick which feature doesn't work.

Posted on 32 Aug 2010, 6:33 by broomdodger
re synclient
The Xorg Wizard does create a synaptics section in xorg.conf, with this entry:

Option "SHMConfig" "on"

That is in my xorg.conf and synclient has error.

Posted on 32 Aug 2010, 6:45 by disciple
the 16bit option is essential
A lot of P3 era machines have been upgraded to 17 or 19 inch LCD monitors, but they can only run the native 1280x1024 resolution at 16bit.

Similarly, sometimes they can run the native resolution at 24bit, but the picture becomes blurry or they only have hardware acceleration at 16 bit.

Posted on 1 Sep 2010, 19:57 by mavrothal
pls keep 16 bit
On the OLPC XO-1 laptop 24 bit produces a flickering screen while gmplayer gives a black window on playback.
This may be related to server configuration and/or the geode driver but till this is shorted out, please keep 16 bit.

Posted on 2 Sep 2010, 14:35 by jeffrey
8-bit color is good!
For your amusement, I use 8-bit pseudo-color at work, although the machines that I run Puppy on don't (and obviously couldn't) run our pseudo-color application.
On whether to drop 16-bit color support it would seem wise to to retain it as an option to allow users with older hardware to display Puppy's beautiful GUI.

Posted on 3 Sep 2010, 6:54 by CLAM01
laptop lcd/tft displays
Most laptops up into P-3, and budget ones into P-4, had/have single optimum resolution, meaning full-screen resolution, lcd/tft displays. The number of transistors on those displays correlated to the resolution and to color-depth. Color depth of 16 was more or less 'standard' then, with 800x600 at 16 and 1024x786 at 16 normal for everyday laptops, because 24 or 32 required significantly more transistors. On those lcds, unlike with CRTs that give bigger image at lower resolution, if you set lower you got a smaller image display, the transistor-pixels over the number needed for the resolution forming a black border around the image. If you set higher resolution, or color depth, Xorg would default to the optimum it would read. So long as the puppy Xorg can default to 16 for older max 16 lcd/tft laptop displays, eliminating a choice of 16 should do no harm: It is probably safe to say that the displays of the majority of laptops linux has been installed on that max at 16 had 24 or 32 selected by the users.

Posted on 29 May 2011, 8:47 by anrika411
16 Bit Color
The older computer on which I have sometimes had Puppy installed, and which I am currently still using, needs the i810 driver for the Intel chipset. I've read that this setup only runs in 16-bit color though I wish it were otherwise. Right now I am using other linux distros for older hardware but I like to keep a Puppy Live CD handy, because sometimes I've needed it and I enjoy using it. I hope you'll leave the option for 16-bit color in newer versions.