XPost: alt.comp.os.windows-10   
   From: nospam@needed.invalid   
      
   On Wed, 10/29/2025 4:34 PM, vallor wrote:   
   > At Wed, 29 Oct 2025 08:50:09 -0400, Paul  wrote:   
   >   
   >> On Wed, 10/29/2025 8:42 AM, Felix wrote:   
   >>> Felix wrote:   
   >>>> Dan Purgert wrote:   
   >>>>> On 2025-10-27, J. P. Gilliver wrote:   
   >>>>>> On 2025/10/27 17:17:7, Paul wrote:   
   >>>>>>> There should be two articles. The "nyah nyah, I have new hardware"   
   >>>>>>> article, and the "boo hiss, I have old hardware and can't afford   
   >>>>>> Or, "I have old hardware which did all I wanted it to do".   
   >>>>> So far, the only hardware I've run into that slams into *that* wall was   
   >>>>> some 32-bit POS from 200x ... it still "runs", but "mainstream distros"   
   >>>>> are out.   
   >>>>>   
   >>>>> Granted, I also have just enough awareness to realize that I can't   
   >>>>> "demand" that someone else keep spending their time on 32bit support   
   >>>>> just because I have an antique that I want to keep running.   
   >>>>>   
   >>>>> All my 64-bit stuff from 2010/2012 onwards seems to not have any   
   >>>>> troubles even with the newer distros, barring a few cases of "dammit   
   >>>>> broadcom" that I fixed with some realtek USB dongle.   
   >>>>>   
   >>>>   
   >>>> I have 10 -15 yo PC's here running LM 21.3 no issues   
   >>>>   
   >>>   
   >>> p.s. I leave them at 21.3 because someone said 22+ is for newer machines   
   >>>   
   >>   
   >> Test and see.   
   >>   
   >> That's what I'm running right now, is install tests.   
   >>   
   >> The results are pure weirdness, for sure.   
   >>   
   >> For example, everything I've installed so far, has   
   >> exactly the same GLXGEARS results. One claims to be   
   >> pure X11, another might be Wayland. There is supposed   
   >> to be a difference here... because I tested for this   
   >> before, and Wayland ran at half the speed of X11.   
   >> It would seem the video card is somehow smothering   
   >> the detail.   
   >>   
   >>    Paul   
   >   
   > By default, glxgears syncs to vblank.  To unlock it:   
   >   
   > $ vblank_mode=0 __GL_SYNC_TO_VBLANK=0 glxgears   
   > 106787 frames in 5.0 seconds = 21357.289 FPS   
   > 108361 frames in 5.0 seconds = 21671.984 FPS   
   > 108247 frames in 5.0 seconds = 21648.572 FPS   
   > ^C   
   >   
      
   The runs I did, were done that way. I have   
   that in my notes file, when I forget.   
      
   The runs were all in the 5000 range, as it's a   
   HD6450 that draws 13 watts and it is not exactly   
   a powerhouse. That is its claim to fame, is it   
   does not overload the PSU in the Optiplex 780.   
   (The PSU has no PCIe power connectors.)   
   I guess the result is accelerated, as I don't think I   
   would hit 5000 via just a Core2 processor doing   
   fallback rendering.   
      
   If I run glxgears in Bash shell on this machine,   
   that's an unaccelerated graphics stack.   
      
   $ vblank_mode=0 glxgears   
   ATTENTION: default value of option vblank_mode overridden by environment.   
   772 frames in 5.0 seconds = 154.328 FPS   
   654 frames in 5.0 seconds = 130.761 FPS   
   653 frames in 5.0 seconds = 130.454 FPS   
   637 frames in 5.0 seconds = 127.245 FPS   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)