1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • Slow Graphics issue

    From Doug Laidlaw@2:250/1 to All on Mon Sep 21 05:36:45 2020
    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M
    CPU bought this year
    Graphics card nVidia with Mageia driver : worked OK until less than a
    week ago.

    Graphics in my favorite Jigsaw program are extremely slow. Pieces take
    a couple of seconds to start moving. Accurate placing is almost
    impossible. Teapot and GLX Gears show a top FPS of 60.

    Running the same program in 8 is quite normal. That should cover the recommendation to run it from a "junk" user.

    Doug.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Mon Sep 21 07:38:18 2020
    On Mon, 21 Sep 2020 14:36:45 +1000, Doug Laidlaw wrote:
    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M
    CPU bought this year
    Graphics card nVidia with Mageia driver : worked OK until less than a
    week ago.

    Graphics in my favorite Jigsaw program are extremely slow. Pieces take
    a couple of seconds to start moving. Accurate placing is almost
    impossible. Teapot and GLX Gears show a top FPS of 60.

    Running the same program in 8 is quite normal. That should cover the recommendation to run it from a "junk" user.

    Workaround, log into either your user account or junk,
    click up a terminal and
    export vblank_mode=0
    teapot

    If you get 10x+ 60FPS then try running the program from the command line.

    Note, teapot with Help screen FPS is a realistic FPS for graphic games.
    teapot without the Help or glxgears are not realistic values.

    Usual location for setting environment variables system wide for users
    logging in is a script in /etc/profile.d/whatever_like_fn.sh or .csh
    ls /etc/profile.d/
    for examples.

    I use xx_ wherever possible, and since I multi-boot versions I use a link
    to a directory shared across installs.

    $ ls -al /etc/profile.d/xx*
    lrwxrwxrwx 1 root root 23 Jul 29 02:48 \
    /etc/profile.d/xx__login.sh -> /local/bin/xx__login.sh



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Mon Sep 21 12:15:35 2020
    On 21/9/20 4:38 pm, Bit Twister wrote:
    On Mon, 21 Sep 2020 14:36:45 +1000, Doug Laidlaw wrote:
    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M
    CPU bought this year
    Graphics card nVidia with Mageia driver : worked OK until less than a
    week ago.

    Graphics in my favorite Jigsaw program are extremely slow. Pieces take
    a couple of seconds to start moving. Accurate placing is almost
    impossible. Teapot and GLX Gears show a top FPS of 60.

    Running the same program in 8 is quite normal. That should cover the
    recommendation to run it from a "junk" user.

    Workaround, log into either your user account or junk,
    click up a terminal and
    export vblank_mode=0
    teapot

    If you get 10x+ 60FPS then try running the program from the command line.

    Note, teapot with Help screen FPS is a realistic FPS for graphic games. teapot without the Help or glxgears are not realistic values.

    Usual location for setting environment variables system wide for users logging in is a script in /etc/profile.d/whatever_like_fn.sh or .csh
    ls /etc/profile.d/
    for examples.

    I use xx_ wherever possible, and since I multi-boot versions I use a link
    to a directory shared across installs.

    $ ls -al /etc/profile.d/xx*
    lrwxrwxrwx 1 root root 23 Jul 29 02:48 \
    /etc/profile.d/xx__login.sh -> /local/bin/xx__login.sh


    I am not sure that I follow you. In a terminal,

    export vblank_mode=0
    teapot

    gives me 59.5 to 60 fps. to my way of thinking, that is "the command line."

    Trying to run teapot from tty2, I don't have a display.

    I have just noticed Unruh's post "Weird X Freeze." Maybe it is the same
    bug, mutated? My graphics driver is still nvidia.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Mon Sep 21 13:59:29 2020
    On Mon, 21 Sep 2020 21:15:35 +1000, Doug Laidlaw wrote:
    On 21/9/20 4:38 pm, Bit Twister wrote:

    Workaround, log into either your user account or junk,
    click up a terminal and
    export vblank_mode=0
    teapot

    I am not sure that I follow you. In a terminal,

    export vblank_mode=0
    teapot

    gives me 59.5 to 60 fps. to my way of thinking, that is "the command line."

    Ah, yep, that is quite correct.

    Trying to run teapot from tty2, I don't have a display.

    But I said nothing about command line, let alone using hot keys to switch
    to a terminal. I said click up a terminal. Only way I know to do that
    is while running in a DE environment where the terminal can run gui
    apps using the DISPLAY environment variable.

    I have just noticed Unruh's post "Weird X Freeze."

    Yeah, and I would have thought faeychild would have read the same thread.

    Maybe it is the same bug, mutated?

    Offhand I would not think so; thinking Unruh's problem was intermittent.

    My graphics driver is still nvidia.

    I do not understand why you think that is per-tent.

    Max ~60 FPS does not seem to be tied to only nvidia hardware.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Mon Sep 21 16:34:56 2020
    On 21/9/20 10:59 pm, Bit Twister wrote:
    On Mon, 21 Sep 2020 21:15:35 +1000, Doug Laidlaw wrote:
    On 21/9/20 4:38 pm, Bit Twister wrote:

    Workaround, log into either your user account or junk,
    click up a terminal and
    export vblank_mode=0
    teapot

    I am not sure that I follow you. In a terminal,

    export vblank_mode=0
    teapot

    gives me 59.5 to 60 fps. to my way of thinking, that is "the command line."

    Ah, yep, that is quite correct.

    Trying to run teapot from tty2, I don't have a display.

    But I said nothing about command line, let alone using hot keys to switch
    to a terminal. I said click up a terminal. Only way I know to do that
    is while running in a DE environment where the terminal can run gui
    apps using the DISPLAY environment variable.

    I have just noticed Unruh's post "Weird X Freeze."

    Yeah, and I would have thought faeychild would have read the same thread.

    Maybe it is the same bug, mutated?

    Offhand I would not think so; thinking Unruh's problem was intermittent.

    My graphics driver is still nvidia.

    I do not understand why you think that is per-tent.

    That was what happened to faeychild, the driver reverted to nouveau. I
    have seen that happen when for some reason, the nvidia driver cannot be
    loaded (e.g., the "nokmsboot" parameter is missing.)

    Max ~60 FPS does not seem to be tied to only nvidia hardware.

    Between Mga 7 and 8, the kernels would be different, but I would expect
    the video driver to be the same in both. They update less frequently.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Mon Sep 21 23:11:20 2020
    On 21/9/20 2:36 pm, Doug Laidlaw wrote:
    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M
    CPU bought this year
    Graphics card nVidia with Mageia driver : worked OK until less than a


    I found the Nouveau driver to be a bit useless after I discovered it had
    been installed by stealth
    Try the Nvidia driver


    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Sep 22 18:06:36 2020
    On 22/9/20 1:34 am, Doug Laidlaw wrote:
    On 21/9/20 10:59 pm, Bit Twister wrote:
    On Mon, 21 Sep 2020 21:15:35 +1000, Doug Laidlaw wrote:
    On 21/9/20 4:38 pm, Bit Twister wrote:

    Workaround, log into either your user account or junk,
    click up a terminal and
            export vblank_mode=0
            teapot

    I am not sure that I follow you.  In a terminal,

            export vblank_mode=0
            teapot

    gives me 59.5 to 60 fps.  to my way of thinking, that is "the command
    line."

    Ah, yep, that is quite correct.

    Trying to run teapot from tty2, I don't have a display.

    But I said nothing about command line, let alone using hot keys to switch
    to a terminal. I said click up a terminal. Only way I know to do that
    is while running in a DE environment where the terminal can run gui
    apps using the DISPLAY environment variable.

    What does "click up" mean? I don't run Level 3, but I thought you meant
    to create a window in a console, somehow.

    I have just noticed Unruh's post "Weird X Freeze."

    Yeah, and I would have thought faeychild would have read the same thread.

    Maybe it is the same bug, mutated?

    Offhand I would not think so; thinking Unruh's problem was intermittent.

    My graphics driver is still nvidia.

    I do not understand why you think that is per-tent.

    That was what happened to faeychild, the driver reverted to nouveau.  I have seen that happen when for some reason, the nvidia driver cannot be loaded (e.g., the "nokmsboot" parameter is missing.)

    Max ~60 FPS does not seem to be tied to only nvidia hardware.

    Between Mga 7 and 8, the kernels would be different, but I would expect
    the video driver to be the same in both.  They update less frequently.
    I have eliminated almost all factors that can cause this problem:

    FPS: Teapot with menu shows identical rates (60 fps) in both 7.1
    Official and * (Cauldron.) but Cauldron runs O.K.

    RAM: I haven't run a prop[er RAM check, but gkrellm indicates that I
    have 8 GiB RAM and 4 GiB swap. Both installations use the same hardware

    KERNEL: I kept one previous kernel in 7. Booting into it made no
    difference.

    nvidia driver: I haven't compared the driver version numbers. That is
    about the only possibility left.

    JOURNAL: I clicked up the little 5-line window that Bits suggested: It
    showed nothing relevant. It DID show the multiple lines created by
    BOINC: "No protocol specified." This is a common problem. Suspending
    BOINC improved things, but wasn't a complete cure. I don't run BOINC in Cauldron.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Sep 22 19:41:31 2020
    On 23/9/20 3:06 am, Doug Laidlaw wrote:
    JOURNAL:  I clicked up the little 5-line window that Bits suggested: It showed nothing relevant.  It DID show the multiple lines created by
    BOINC: "No protocol specified."  This is a common problem.  Suspending BOINC improved things, but wasn't a complete cure. I don't run BOINC in Cauldron.

    It seems that BOINC is the problem. htop shows it using 2.9G in red, in
    the VIRT column. VIRT is something I have never understood. What does
    it mean?

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Sep 22 19:56:14 2020
    On Wed, 23 Sep 2020 03:06:36 +1000, Doug Laidlaw wrote:
    On 22/9/20 1:34 am, Doug Laidlaw wrote:
    On 21/9/20 10:59 pm, Bit Twister wrote:


    Trying to run teapot from tty2, I don't have a display.

    But I said nothing about command line, let alone using hot keys to switch >>> to a terminal. I said click up a terminal. Only way I know to do that
    is while running in a DE environment where the terminal can run gui
    apps using the DISPLAY environment variable.

    What does "click up" mean?

    Use a mouse click to bring up terminal.

    I don't run Level 3,

    Ok, then I will guess runlevel 5 is default, which is gui on Mageia.

    but I thought you meant to create a window in a console, somehow.

    Well. terminology means different things to different people.
    For instance, I wanted you to use your mouse to launch a terminal
    which would open a window where you would be at a command line prompt.
    When you launch teapot, it would open a window with the rotating
    teapot.

    FPS: Teapot with menu shows identical rates (60 fps) in both 7.1
    Official and * (Cauldron.)

    That does not surprise me, but does seem to indicate FPS is not
    the problem, unless your system is is busier on 7 than on 8.

    but Cauldron runs O.K.

    Which leads us back to the need for elimination on Mageia 7 install.
    Does the problem exist at a user level or system level.

    Easy test. Log into a test account, say junk, launch the game
    and if problem still exists, it is a system wide problem.

    RAM: I haven't run a prop[er RAM check, but gkrellm indicates that I
    have 8 GiB RAM and 4 GiB swap.

    Usually swap is defined/sized as same amount of ram or larger depending
    on operational requirements and/or usage.
    If you are going to use hibernation/sleep, swap should be at least
    the size of ram + 512meg.

    Both installations use the same hardware

    Usually a very good indication that ram and other hardware is not
    a problem.

    KERNEL: I kept one previous kernel in 7. Booting into it made no difference.

    nvidia driver: I haven't compared the driver version numbers. That is
    about the only possibility left.

    Hopefully at this point you are using the same video driver (nouveau,nvidia)
    I would expect version to be different.

    JOURNAL: I clicked up the little 5-line window that Bits suggested: It showed nothing relevant. It DID show the multiple lines created by
    BOINC: "No protocol specified." This is a common problem. Suspending
    BOINC improved things, but wasn't a complete cure. I don't run BOINC in Cauldron.

    If you want any further help from me, I would like to know the names
    of your Display Manager (DM). Display Environment (DE), video card/driver and jigsaw game.

    # DM found with
    systemctl status display-manager.service | grep -E "PID:|bin/"

    # DE found with
    echo $XDG_CURRENT_DESKTOP

    # video card/driver found with
    lspcidrake -v | grep Card:

    # and do not forget to supply the name of the jigsaw game.


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Sep 22 20:05:21 2020
    On Wed, 23 Sep 2020 04:41:31 +1000, Doug Laidlaw wrote:
    On 23/9/20 3:06 am, Doug Laidlaw wrote:
    JOURNAL:  I clicked up the little 5-line window that Bits suggested: It
    showed nothing relevant.  It DID show the multiple lines created by
    BOINC: "No protocol specified."  This is a common problem.  Suspending
    BOINC improved things, but wasn't a complete cure. I don't run BOINC in
    Cauldron.

    It seems that BOINC is the problem. htop shows it using 2.9G in red, in
    the VIRT column. VIRT is something I have never understood.
    What does it mean?

    Question is somewhat vague, which it is it, red or virt.

    Using https://www.google.com/advanced_search and htop red in the first
    box gets me
    About 941,000 results (0.55 seconds)

    Using
    htop columns explanation
    gets me.
    About 20,500 results (0.47 seconds)


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Sep 22 20:11:10 2020
    On Tue, 22 Sep 2020 14:41:31 -0400, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:
    It seems that BOINC is the problem. htop shows it using 2.9G in red, in
    the VIRT column. VIRT is something I have never understood. What does
    it mean?

    From man htop ...
    M_SIZE (VIRT)
    The size of the virtual memory of the process.

    M_RESIDENT (RES)
    The resident set size (text + data + stack) of the process (i.e. the size of the process's used physical memory).

    So the VIRT is the total of ram and swap used while the RES is the actual ram used.

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Fri Oct 16 03:08:44 2020
    On 22/9/20 8:11 am, faeychild wrote:
    On 21/9/20 2:36 pm, Doug Laidlaw wrote:
    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M
    CPU bought this year
    Graphics card nVidia with Mageia driver : worked OK until less than a


    I found the Nouveau driver to be a bit useless after I discovered it had been installed by stealth
    Try the Nvidia driver



    The nouveau driver can't handle some of my tasks. I was running
    Mageia's Nvidia driver.

    My system was getting slower and slower: even keyboard input was taking
    a couple of seconds to appear on the screen. To my limited
    understanding, that suggests that the video system is not the problem.

    Since I don't know enough to run a full error-check, I did an "upgrade" re-install of 7.1. I find that it often fixes configuration problems.
    The delay in typing has gone. The graphics seem to be better than before.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Fri Oct 16 21:57:35 2020
    On 16/10/20 1:08 pm, Doug Laidlaw wrote:

    Since I don't know enough to run a full error-check, I did an "upgrade" re-install of 7.1.  I find that it often fixes configuration problems.
    The delay in typing has gone.  The graphics seem to be better than before.

    Yes I'm familiar with the feeling of where do I look, where do I go next

    Htop can be somewhat useful

    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Sat Oct 17 00:10:10 2020
    On Mon, 21 Sep 2020 14:36:45 +1000, Doug Laidlaw wrote:

    Mageia 7.1 Official. (No problem on 8)
    Mobo Gigabyte 8365M CPU bought this year Graphics card nVidia with
    Mageia driver : worked OK until less than a week ago.

    Graphics in my favorite Jigsaw program are extremely slow. Pieces take
    a couple of seconds to start moving. Accurate placing is almost
    impossible. Teapot and GLX Gears show a top FPS of 60.

    Running the same program in 8 is quite normal. That should cover the recommendation to run it from a "junk" user.

    My backup machine slowed to a crawl, with hard drive constantly on, mouse cursor basically non-functional, etc.

    htop brought baloo indexing to my attention, and a check of the 'Net says
    it has created such problems on ubuntu and other Linux systems.

    I found it had been installed on Mageia5 or Mageia6, probably as a
    dependency of kde or maybe one of the kde packages such as gwenview.

    My main machine does not have it installed, so I removed it from my
    backup machine, and so far so good.

    rpm -qa |grep baloo
    to see what (if any) baloo packages you have installed. When I removed a half-dozen, another 15 dependencies were removed, but nothing I really
    thought was critical.

    I assume it was triggered by one of the recent updates to system
    software, but do not really know.

    Cheers!

    jim b.



    --
    UNIX is not user-unfriendly, it merely
    expects users to be computer friendly.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sat Oct 17 03:41:22 2020
    On Fri, 16 Oct 2020 19:10:10 -0400, Jim Beard <jim.beard@verizon.net> wrote:
    My backup machine slowed to a crawl, with hard drive constantly on, mouse cursor basically non-functional, etc.

    htop brought baloo indexing to my attention, and a check of the 'Net says
    it has created such problems on ubuntu and other Linux systems.

    I found it had been installed on Mageia5 or Mageia6, probably as a
    dependency of kde or maybe one of the kde packages such as gwenview.

    My main machine does not have it installed, so I removed it from my
    backup machine, and so far so good.

    I disable it on most of my systems. https://community.kde.org/Baloo/Configuration

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sat Oct 17 05:28:38 2020
    On Fri, 16 Oct 2020 22:41:22 -0400, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    I disable it on most of my systems. https://community.kde.org/Baloo/Configuration

    I also disable akonadi.
    http://www.linux-databook.info/?page_id=3728

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sat Oct 17 21:57:44 2020
    On 17/10/20 3:28 pm, David W. Hodgins wrote:


    I also disable akonadi.
    http://www.linux-databook.info/?page_id=3728

    Regards, Dave Hodgins




    I have some doubts about msec.
    It would have a little more credibility if it didn't continue to flag
    the same files each time, after claiming to have corrected them.

    fortunately it doesn't clobber the system performance



    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Oct 19 02:38:56 2020
    On Sat, 17 Oct 2020 16:57:44 -0400, faeychild <faeychild@nomail.afraid.org> wrote:
    I have some doubts about msec.
    It would have a little more credibility if it didn't continue to flag
    the same files each time, after claiming to have corrected them.
    fortunately it doesn't clobber the system performance

    That's partly due to me. Back in Mandriva days, I reported a problem with msec altering ownership of unowned files and directories to the user nobody.

    The problem with that approach is that with multiple installs, and different installs having different a different uid for each user, was that every time msec ran, the other installs were being made un-bootable due to the differences
    in system user ids due to the different packages installed and the order they were installed.

    The msec program was altered to remove the actual changing, but the wording
    of the report was not altered.

    Since then, I find the msec reports useful as a tool to identify what may need changing, and have never bothered to get the wording fixed.

    One of these days, I'll get around to asking for the wording to be fixed.

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)