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

  • Mageia 8 Alpha 1 - Window for configuring repositories is worse.

    From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 21:12:10 2020

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and installed it.

    The first thing I do after installing some version of mageia is to add repositories.

    In previous versions there was a strange behavior. Now it's worse
    because a new window is opened for each selected repository. In addition
    to having to click more, you still have to wait for each one to load.

    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04


    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Sun Jul 12 21:22:51 2020
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO

    I would be extremely surprized if that were true.

    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and installed it.

    Why are you installing cauldron? Are you planning on debugging it? You
    should not be installing it to use it, unless you have very new hardware
    which is not supported by the mga7 kernel.


    The first thing I do after installing some version of mageia is to add repositories.

    In previous versions there was a strange behavior. Now it's worse

    What does "a strange behaviour" mean?

    because a new window is opened for each selected repository. In addition
    to having to click more, you still have to wait for each one to load.

    ?? You can always add them later rather than during installation.
    And why do you want more than one repository?


    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 21:35:18 2020
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO

    I would be extremely surprized if that were true.

    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Why are you installing cauldron? Are you planning on debugging it? You
    should not be installing it to use it, unless you have very new hardware which is not supported by the mga7 kernel.


    The first thing I do after installing some version of mageia is to add
    repositories.

    In previous versions there was a strange behavior. Now it's worse

    What does "a strange behaviour" mean?

    This was discussed here:

    <rdsjeb$1h6n$1@gioia.aioe.org>

    On Sun, 05 Jul 2020 09:14:34 -0400, Gilberto F da Silva
    <gfs1989@gmx.net> wrote:

    strangely when a repository is selected. It's been like this for some versions of Mageia. I never understand the reason for this strange
    behavior.

    The problem is well known. Whether or not it's visible depends on the hardware.
    It's due to the way selection windows written in perl (the langauge rpmdrake
    is written in) are handled, and the way some hardware handles the redraw of
    the window.

    The workaround is to maximize the window showing the list of
    repositories before
    making the selections.

    Regards, Dave Hodgins

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 21:55:45 2020
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO

    I would be extremely surprized if that were true.

    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Why are you installing cauldron? Are you planning on debugging it? You
    should not be installing it to use it, unless you have very new hardware which is not supported by the mga7 kernel.

    The upgrade to Caudron didn't work here. I am using Mageia 8 Alpha 1. The goal is to report any bugs. For some reason I still like Mageia.

    This motherboard is actually a little old. It was removed from discarded equipment.


    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:07:21 2020
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    because a new window is opened for each selected repository. In addition
    to having to click more, you still have to wait for each one to load.

    ?? You can always add them later rather than during installation.
    And why do you want more than one repository?

    Well ... The idea is to have access to all programs packaged for the
    version in use. I do this so as not to have to configure more
    repositories when I don't find any desired program. With all
    repositories enabled, if any package was not found it is because it does
    not exist.



    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz
    Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04




    --


    Gilberto F da Silva

    --- 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 Sun Jul 12 22:14:05 2020
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In previous versions there was a strange behavior. Now it's worse
    because a new window is opened for each selected repository.

    Ok, I can agree with your symptoms and a new window for each media
    is abusive.

    As a benchmark, I wiped Cauldron yesterday and did a network install
    and do not see your new window on each media problem.



    In addition
    to having to click more, you still have to wait for each one to load.

    I would like to know what media is being used, please provide the output from
    urpmq --list-media active

    Speed is relative to your connection and selected mirror. I would like
    to see the output from
    grep -i core /etc/urpmi/urpmi.cfg




    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04

    Please show us the output from
    inxi --graphics

    --- 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 Sun Jul 12 22:18:10 2020
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick.

    At a glance at your url hardware makes me wonder why not.

    What exactly did you do to create the "memory stick"?

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:30:14 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    Yes.

    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 2133/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 2h 27m
    Mem: 2275.7/3928.6 MiB (57.9%) Storage: 376.23 GiB (14.0% used) Procs:
    193 Shell: inxi: 3.1.04


    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:35:04 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add
    repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In Slackware it is explicit that * only one * repository should be
    added. In Mageia this is still not very clear in my mind.


    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:40:15 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add
    repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In previous versions there was a strange behavior. Now it's worse
    because a new window is opened for each selected repository.

    Ok, I can agree with your symptoms and a new window for each media
    is abusive.

    As a benchmark, I wiped Cauldron yesterday and did a network install
    and do not see your new window on each media problem.

    The last attempt to use Cauldron did not work. I installed Mageia 8 Alpha 1 in place.

    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 2133/600/800 MHz Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 2h 27m
    Mem: 2275.7/3928.6 MiB (57.9%) Storage: 376.23 GiB (14.0% used) Procs:
    193 Shell: inxi: 3.1.04

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:45:00 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add
    repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In previous versions there was a strange behavior. Now it's worse
    because a new window is opened for each selected repository.

    Ok, I can agree with your symptoms and a new window for each media
    is abusive.

    As a benchmark, I wiped Cauldron yesterday and did a network install
    and do not see your new window on each media problem.



    In addition
    to having to click more, you still have to wait for each one to load.

    I would like to know what media is being used, please provide the output
    from
    urpmq --list-media active

    [mageia8@localhost Telegram]$ urpmq --list-media active
    Core Release
    Core Release Debug
    Core Updates
    Core Updates Debug
    Core Updates Testing
    Core Updates Testing Debug
    Core Backports
    Core Backports Debug
    Core Backports Testing
    Core Backports Testing Debug
    Nonfree Release
    Nonfree Release Debug
    Nonfree Updates
    Nonfree Updates Debug
    Nonfree Updates Testing
    Nonfree Updates Testing Debug
    Nonfree Backports
    Nonfree Backports Debug
    Nonfree Backports Testing
    Nonfree Backports Testing Debug
    Tainted Release
    Tainted Release Debug
    Tainted Updates
    Tainted Updates Debug
    Tainted Updates Testing
    Tainted Updates Testing Debug
    Tainted Backports
    Tainted Backports Debug
    Tainted Backports Testing
    Tainted Backports Testing Debug
    Core 32bit Release
    Core 32bit Updates
    Nonfree 32bit Release
    Nonfree 32bit Updates
    Tainted 32bit Release
    Tainted 32bit Updates
    [mageia8@localhost Telegram]$




    Speed is relative to your connection and selected mirror. I would like
    to see the output from
    grep -i core /etc/urpmi/urpmi.cfg


    [mageia8@localhost Telegram]$ grep -i core /etc/urpmi/urpmi.cfg
    Core\ Release http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/core/release {
    Core\ Release\ Debug http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/debug/core/release { Core\ Updates http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/core/updates {
    Core\ Updates\ Debug http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/debug/core/updates { Core\ Updates\ Testing http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/core/updates_testing
    {
    Core\ Updates\ Testing\ Debug http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/debug/core/updates_testi ng
    {
    Core\ Backports http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/core/backports {
    Core\ Backports\ Debug http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/debug/core/backports
    {
    Core\ Backports\ Testing http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/core/backports_testing {
    Core\ Backports\ Testing\ Debug http://ftp.fau.de/mageia/distrib/cauldron/x86_64/media/debug/core/backports_tes ting
    {
    Core\ 32bit\ Release http://ftp.fau.de/mageia/distrib/cauldron/i586/media/core/release {
    Core\ 32bit\ Updates http://ftp.fau.de/mageia/distrib/cauldron/i586/media/core/updates {
    Core\ 32bit\ Updates\ Testing http://ftp.fau.de/mageia/distrib/cauldron/i586/media/core/updates_testing { Core\ 32bit\ Backports http://ftp.fau.de/mageia/distrib/cauldron/i586/media/core/backports {
    Core\ 32bit\ Backports\ Testing http://ftp.fau.de/mageia/distrib/cauldron/i586/media/core/backports_testing
    {
    [mageia8@localhost Telegram]$





    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz
    Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04

    Please show us the output from
    inxi --graphics


    Graphics: Device-1: Intel 82Q963/Q965 Integrated Graphics driver: i915
    v: kernel
    Display: x11 server: Mageia X.org 1.20.8 driver: intel,v4l resolution: 1920x1080~60Hz
    OpenGL: renderer: Mesa DRI Intel 965Q (BW) v: 2.1 Mesa 20.1.3


    --


    Gilberto F da Silva

    --- 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 Sun Jul 12 22:47:57 2020
    On Sun, 12 Jul 2020 18:30:14 -0300, Gilberto F da Silva wrote:

    You need to go back and read my replies and answer my questions.
    All of them, not just the first question.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 22:52:23 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick.

    At a glance at your url hardware makes me wonder why not.

    What exactly did you do to create the "memory stick"?


    With this software packaged in AppImage:

    https://www.balena.io/etcher/

    I believe it is a motherboard defect. The Dell laptop can boot from the
    memory stick.

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Sun Jul 12 23:13:37 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 18:30:14 -0300, Gilberto F da Silva wrote:

    You need to go back and read my replies and answer my questions.
    All of them, not just the first question.


    I answered all questions. Was there any missing?

    --


    Gilberto F da Silva

    --- 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 Sun Jul 12 23:14:04 2020
    On Sun, 12 Jul 2020 18:45:00 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:


    I would like to know what media is being used, please provide the output from
    urpmq --list-media active

    [mageia8@localhost Telegram]$ urpmq --list-media active
    Core Updates Debug
    Core Updates Testing
    Core Updates Testing Debug
    Core 32bit Release
    Core 32bit Updates
    Nonfree 32bit Release
    Nonfree 32bit Updates
    Tainted 32bit Release
    Tainted 32bit Updates

    Ok, unless you need 32 bit applications, I suggest you do not need
    to use 32bit media.

    You really should not be using anything from testing or debug media unless
    you really know you need something from that media selection.

    This is all I have in my Cauldron.

    urpmq --list-media active
    Core_Release
    Core_Updates
    Nonfree_Release
    Nonfree_Updates
    Tainted_Release
    Tainted_Update

    You might try running glxgears or teapot to get your fps value.
    if either app shows only around 60 fps then I would try adding
    vblank_mode=0
    to your kernel boot parameters and run the test again.

    With that setting I get
    Frame rate: 888 with teapot
    17428 frames in 5.0 seconds = 3485.444 FPS with glxgears

    mesa-demos rpm has glxgears and teapot applications.

    Running teapot in the startup mode gives you a/the realistic FPS rate
    seen while playing graphic games.

    If your frame rate is better, try running your mcc media setup again.


    --- 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 Sun Jul 12 23:15:57 2020
    On Sun, 12 Jul 2020 19:13:37 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 18:30:14 -0300, Gilberto F da Silva wrote:

    You need to go back and read my replies and answer my questions.
    All of them, not just the first question.


    I answered all questions. Was there any missing?

    Saw your followup post with the answers. I had expected to see them
    in your first reply.

    --- 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 Sun Jul 12 23:21:14 2020
    On Sun, 12 Jul 2020 18:52:23 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick.

    At a glance at your url hardware makes me wonder why not.

    What exactly did you do to create the "memory stick"?


    With this software packaged in AppImage:

    https://www.balena.io/etcher/

    No experience with that software.
    Usual method I used in the past is
    dd bs=2048 of=/dev/sdg if=whatever.iso
    and wait for usb stick to quit blinking.

    I believe it is a motherboard defect.

    Or maybe a bios selection needed.

    The Dell laptop can boot from the memory stick.

    Ok, that surprises me.

    --- 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 Sun Jul 12 23:06:39 2020
    On Sun, 12 Jul 2020 17:45:00 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    [mageia8@localhost Telegram]$ urpmq --list-media active
    Core Release
    Core Release Debug
    Core Updates
    Core Updates Debug
    Core Updates Testing
    Core Updates Testing Debug
    Core Backports
    Core Backports Debug
    Core Backports Testing
    Core Backports Testing Debug
    <snip rest>

    Ouch! Do not enable all repositories.

    On the terminology, I've always viewed each line shown by "urpmq --list-media" to
    be a separate repo.

    Especially, do not enable the backports repos. They should only be enabled on temporary basis, to install a selected package from that repo. Once the selected
    package has been installed, disable the backports repos.

    On Mageia 7, there are backports that can interfere with the regular packages. Those in the backports repo only for those who need that particular version. With the testing repos, they are intended for use by the qa team. Installing all packages from the testing repos will include packages that fail testing.

    On Cauldron, only the release repos should normally be enabled. The updates testing
    repos are used only while doing things like building kde plasma, where the packages
    are built in preperation for moving to the release repos, and for building packages
    that the packager is testing to see if it works. The updates repos are not used,
    so it doesn't matter if they are enabled or not.

    Having all repos enabled is very likely to break things on the installation, especially for cauldron where things like a new version of plasma consists
    of hundreds of packages, and installing the new packages during the middle of the build process will break the working of the desktop.

    For most people, the release and updates repos for Core, Nonfree and Tainted, are
    all that should be enabled.

    Any bug reports submitted when using this approach become questionable, since versions of packages that should not be used without good reason have been installed.

    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 Bit Twister@2:250/1 to All on Mon Jul 13 00:00:38 2020
    On Sun, 12 Jul 2020 18:06:39 -0400, David W. Hodgins wrote:


    For most people, the release and updates repos for Core, Nonfree and
    Tainted, are
    all that should be enabled.

    Any bug reports submitted when using this approach become questionable,
    since
    versions of packages that should not be used without good reason have been installed.

    I can agree with you there. I also suggest another clean install,
    with just release, Nonfree and Tainted with updates. all updates applied, reboot, then see if the problem still exists.

    If so, we have managed to narrow down the problem to the video hardware
    and driver.

    Hopefully vblank_mode=0 fixes the problem.



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Jul 13 00:09:50 2020
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and
    installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add
    repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In Slackware it is explicit that * only one * repository should be
    added. In Mageia this is still not very clear in my mind.


    It is still unclear what you mean by repository.
    Do you mean something like
    mirror.math.princeton.edu
    or
    mirrors.kernel.org
    or do you mean

    things like
    Core
    Core Updates

    If you mean the former, why would you want a whole bunch of them? They
    are the same.
    If you mean that latter, I do not know what this "one window per
    repository" means.



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Jul 13 00:15:44 2020
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm
    is not able to boot from the memory stick.

    At a glance at your url hardware makes me wonder why not.

    What exactly did you do to create the "memory stick"?


    With this software packaged in AppImage:

    https://www.balena.io/etcher/

    Why would you do that. The mageia isos are already set up for booting
    from. What you do is liable to produce something unuseable. Just because
    they say it produces miracles, does not mean it is so.


    I believe it is a motherboard defect. The Dell laptop can boot from the
    memory stick.


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Mon Jul 13 00:19:59 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 18:45:00 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:


    I would like to know what media is being used, please provide the output from
    urpmq --list-media active

    [mageia8@localhost Telegram]$ urpmq --list-media active
    Core Updates Debug
    Core Updates Testing
    Core Updates Testing Debug
    Core 32bit Release
    Core 32bit Updates
    Nonfree 32bit Release
    Nonfree 32bit Updates
    Tainted 32bit Release
    Tainted 32bit Updates

    Ok, unless you need 32 bit applications, I suggest you do not need
    to use 32bit media.

    I use wine to run an application. Slackware needs 32-bit libraries or it doesn't even compile. So in Mageia you should also need it.


    You really should not be using anything from testing or debug media unless you really know you need something from that media selection.



    urpmq --list-media active
    Core Release
    Core Updates
    Nonfree Release
    Nonfree Updates
    Tainted Release
    Tainted Updates
    Core 32bit Release
    Core 32bit Updates
    Nonfree 32bit Release
    Nonfree 32bit Updates
    Tainted 32bit Release
    Tainted 32bit Updates


    This is all I have in my Cauldron.

    urpmq --list-media active
    Core_Release
    Core_Updates
    Nonfree_Release
    Nonfree_Updates
    Tainted_Release
    Tainted_Update

    You might try running glxgears or teapot to get your fps value.
    if either app shows only around 60 fps then I would try adding
    vblank_mode=0
    to your kernel boot parameters and run the test again.

    With that setting I get
    Frame rate: 888 with teapot
    17428 frames in 5.0 seconds = 3485.444 FPS with glxgears

    mesa-demos rpm has glxgears and teapot applications.

    Running teapot in the startup mode gives you a/the realistic FPS rate
    seen while playing graphic games.

    If your frame rate is better, try running your mcc media setup again.


    I don't play on the computer. I only play some silly little game when I
    take the woman somewhere and keep waiting for her to come back.

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Mon Jul 13 00:25:01 2020
    On 7/12/20 4:00 PM, Bit Twister wrote:
    On Sun, 12 Jul 2020 18:06:39 -0400, David W. Hodgins wrote:


    For most people, the release and updates repos for Core, Nonfree and Tainted, are
    all that should be enabled.

    Any bug reports submitted when using this approach become questionable, since
    versions of packages that should not be used without good reason have been >> installed.

    I can agree with you there. I also suggest another clean install,
    with just release, Nonfree and Tainted with updates. all updates applied, reboot, then see if the problem still exists.

    If so, we have managed to narrow down the problem to the video hardware
    and driver.

    Hopefully vblank_mode=0 fixes the problem.



    I hope it does. But I guess that the choice of "cauldron"
    for the coming attraction assemblage was humorous but having read
    Shakespeare I would never download a Cauldron. Look at what the
    original (fictive) pot contained. If you have forgotten search on "Shakespeare, Cauldron."

    When you chose download a mess of such nature onto your computer
    of course it is your business but even if you have a CS degree you will
    have a hard time. I guess that is why Mageia maintains a Usenet presence.

    bliss

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Mon Jul 13 00:25:19 2020
    David W. Hodgins escreveu:
    On Sun, 12 Jul 2020 17:45:00 -0400, Gilberto F da Silva
    <gfs1989@gmx.net> wrote:
    [mageia8@localhost Telegram]$ urpmq --list-media active
    Core Release
    Core Release Debug
    Core Updates
    Core Updates Debug
    Core Updates Testing
    Core Updates Testing Debug
    Core Backports
    Core Backports Debug
    Core Backports Testing
    Core Backports Testing Debug
    <snip rest>

    Ouch! Do not enable all repositories.

    On the terminology, I've always viewed each line shown by "urpmq --list-media" to
    be a separate repo.

    Especially, do not enable the backports repos. They should only be
    enabled on a
    temporary basis, to install a selected package from that repo. Once the selected
    package has been installed, disable the backports repos.

    On Mageia 7, there are backports that can interfere with the regular packages.
    Those in the backports repo only for those who need that particular
    version.
    With the testing repos, they are intended for use by the qa team.
    Installing
    all packages from the testing repos will include packages that fail
    testing.

    On Cauldron, only the release repos should normally be enabled. The
    updates testing
    repos are used only while doing things like building kde plasma, where
    the packages
    are built in preperation for moving to the release repos, and for
    building packages
    that the packager is testing to see if it works. The updates repos are
    not used,
    so it doesn't matter if they are enabled or not.

    Having all repos enabled is very likely to break things on the
    installation,
    especially for cauldron where things like a new version of plasma consists
    of hundreds of packages, and installing the new packages during the
    middle of
    the build process will break the working of the desktop.

    For most people, the release and updates repos for Core, Nonfree and Tainted, are
    all that should be enabled.

    Any bug reports submitted when using this approach become questionable, since
    versions of packages that should not be used without good reason have been installed.

    Regards, Dave Hodgins


    Recommendation accepted. I removed unnecessary repositories.

    urpmq --list-media active
    Core Release
    Core Updates
    Nonfree Release
    Nonfree Updates
    Tainted Release
    Tainted Updates
    Core 32bit Release
    Core 32bit Updates
    Nonfree 32bit Release
    Nonfree 32bit Updates
    Tainted 32bit Release
    Tainted 32bit Updates

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jul 13 00:30:58 2020
    On Sun, 12 Jul 2020 19:15:44 -0400, William Unruh <unruh@invalid.ca> wrote:

    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    https://www.balena.io/etcher/
    Why would you do that. The mageia isos are already set up for booting
    from. What you do is liable to produce something unuseable. Just because
    they say it produces miracles, does not mean it is so.

    According to their website, they do a byte level copy, so it seems they are either using dd or equivalent. It should be ok for Mageia, as long as the copy is allowed to complete properly.

    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 Mon Jul 13 00:33:24 2020
    On Sun, 12 Jul 2020 19:25:19 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    Recommendation accepted. I removed unnecessary repositories.

    Next step is to use "urpmq --not-available" to get a list of the packages that should be downgraded or removed.

    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 Gilberto F da Silva@2:250/1 to All on Mon Jul 13 00:37:48 2020
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 18:52:23 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm >>>> is not able to boot from the memory stick.

    At a glance at your url hardware makes me wonder why not.

    What exactly did you do to create the "memory stick"?


    With this software packaged in AppImage:

    https://www.balena.io/etcher/

    No experience with that software.
    Usual method I used in the past is
    dd bs=2048 of=/dev/sdg if=whatever.iso
    and wait for usb stick to quit blinking.


    I've used it that way too, but it's more prone to human errors. This
    software prevents recording on the computer's internal disks. It is also
    more comfortable when you have a progress bar.

    I believe it is a motherboard defect.

    Or maybe a bios selection needed.

    I tried with all the boot options where "USB" appears.


    The Dell laptop can boot from the memory stick.

    Ok, that surprises me.



    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Mon Jul 13 00:48:43 2020
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    Bit Twister escreveu:
    On Sun, 12 Jul 2020 17:12:10 -0300, Gilberto F da Silva wrote:

    I found that my computer https://www.attro.com/motherboard/G7B330-B.htm >>>> is not able to boot from the memory stick. I downloaded the ISO
    https://www.mageia.org/eo/downloads/prerelease/, burned it on a CD and >>>> installed it.

    Information provided is still a bit vague.
    Are we to assume you are using the Mageia-8-alpha1-x86_64.iso?


    The first thing I do after installing some version of mageia is to add >>>> repositories. In addition to having to click more,

    Usually you would only install one repository.
    I will have to assume you mean media.

    In Slackware it is explicit that * only one * repository should be
    added. In Mageia this is still not very clear in my mind.


    It is still unclear what you mean by repository.
    Do you mean something like
    mirror.math.princeton.edu
    or
    mirrors.kernel.org
    or do you mean

    things like
    Core
    Core Updates

    If you mean the former, why would you want a whole bunch of them? They
    are the same.
    If you mean that latter, I do not know what this "one window per
    repository" means.



    Mageia has an icon on the taskbar. He refers to it as MCC (Mageia
    Control Center). in the window that opens, on the left side there are
    some options. The first sample shows four icons. The last icon allows
    you to select the repositories. This window is what I'm talking about.

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Mon Jul 13 00:56:07 2020
    David W. Hodgins escreveu:
    urpmq --not-available

    It resulted in a list larger than the computer screen.


    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jul 13 01:02:07 2020
    On Sun, 12 Jul 2020 19:37:48 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    I tried with all the boot options where "USB" appears.

    The menu presented when selecting a boot device can vary a lot depending on
    the firmware manufacturer and version.

    Normally there are two menu entries for the usb stick. One for booting in uefi firmware mode, and one for booting in bios firmware emulation (legacy) mode. Which one should be used, depends on how the system is set up to boot when booting from a hard drive. If that's set up to use uefi firmware mode, the
    usb stick used for installation must be booted using uefi firmware mode, or
    the system will not boot after installation. Likewise, if the hard drive is normally booted in bios firmware mode, the usb stick must be booted in bios mode for the install.

    The most common cause of problems is not waiting long enough for the writing to
    the usb stick to finish. The dd or equivalent command may end before all of the
    kernel buffers have been written to the device. Rebooting or unplugging the device too soon will result in a stick that will not boot properly, or have problems reading files during the install process.

    If you have a working install on the hard drive, check for the existence of
    the directory /sys/firmware/efi. If it's there, the system is set up for uefi boot. If not, it's set up for bios legacy boot. For checking in windows, see https://itsfoss.com/check-uefi-or-bios/

    Note that for Mageia, restricted boot (aka secure boot) in the uefi setup, must
    be disabled.

    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 Mon Jul 13 01:08:59 2020
    On Sun, 12 Jul 2020 19:56:07 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    David W. Hodgins escreveu:
    urpmq --not-available

    It resulted in a list larger than the computer screen.

    Not surprising. You can re-enable the debug repositories if you want for the currently enabled repos, which will likely cut down the list quite a bit. The debug repos are only used to get better back traces when reporting a segfault in some package. The packages tend to be larger than the actual applications packages, so most people do not install debug packages except when needed for diagnosing a segfault.

    Given that this is a cauldron install, it' probably easiest to re-install, ensuring the files systems are formatted again.

    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 Bit Twister@2:250/1 to All on Mon Jul 13 01:20:19 2020
    On Sun, 12 Jul 2020 20:19:59 -0300, Gilberto F da Silva wrote:
    Bit Twister escreveu:


    If your frame rate is better, try running your mcc media setup again.


    I don't play on the computer.

    I really do not care if you play games or not.

    Your problem is flickering video when running drakrpm-edit-media.

    If we find a solution to that, you can then open a bug report with
    the workaround solution which may help someone zero in on finding the
    problem quicker.

    Will all due respect to David W. Hodgins, I highly recommend
    a clean install, enable desired media, install updates,
    reboot, then verify if flickering problem still exists.
    If so, try my vblank_mode=0 setting.

    If that works, make it permanent. Hopefully that will prevent more
    video related problems getting in your way.

    Trust me, I have lots of experience with troubleshooting hardware and
    software problems.

    You have to have a known, repeatable setup with the least amount of
    variables, and a good fault isolation process in order to quickly
    solve a problem.

    In my stupid opinion, attempting to remove your debug/testing rpms
    will just leave orphans and dangling links that would not normally show
    up on a "typical" install/update.

    --- 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 Mon Jul 13 01:53:02 2020
    On Sun, 12 Jul 2020 20:02:07 -0400, David W. Hodgins wrote:
    On Sun, 12 Jul 2020 19:37:48 -0400, Gilberto F da Silva <gfs1989@gmx.net>
    wrote:
    I tried with all the boot options where "USB" appears.

    The menu presented when selecting a boot device can vary a lot depending on the firmware manufacturer and version.

    Normally there are two menu entries for the usb stick. One for booting in
    uefi
    firmware mode, and one for booting in bios firmware emulation (legacy) mode. Which one should be used, depends on how the system is set up to boot when booting from a hard drive.

    Very true, I had my bios set to uefi/CMS. Worked for awhile then after
    boot software change, I had to go back into bios and set it cms/legacy only.


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Gilberto F da Silva@2:250/1 to All on Mon Jul 13 03:07:45 2020
    David W. Hodgins escreveu:

    Not surprising. You can re-enable the debug repositories if you want for
    the
    currently enabled repos, which will likely cut down the list quite a
    bit. The
    debug repos are only used to get better back traces when reporting a segfault
    in some package. The packages tend to be larger than the actual
    applications
    packages, so most people do not install debug packages except when
    needed for
    diagnosing a segfault.

    Given that this is a cauldron install, it' probably easiest to re-install, ensuring the files systems are formatted again.

    Is Mageia 8 Alpha 1 considered Cauldron?

    --


    Gilberto F da Silva

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Mon Jul 13 03:19:38 2020
    On Sun, 12 Jul 2020 22:07:45 -0400, Gilberto F da Silva <gfs1989@gmx.net> wrote:
    Is Mageia 8 Alpha 1 considered Cauldron?

    Yes. Cauldron will become Mageia 8 when the final version is released, then a new
    cauldron will be created for the next release.

    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 Bit Twister@2:250/1 to All on Mon Jul 13 08:03:58 2020
    On Sun, 12 Jul 2020 23:07:45 -0300, Gilberto F da Silva wrote:

    Is Mageia 8 Alpha 1 considered Cauldron?

    Yes. As a side note, when you go to update your Cauldron install,
    you might want to check your mirror status at
    https://mirrors.mageia.org/status
    As I write this your mirror of choice is in the 12 hour range and is
    a little stale.

    Also, you might want to look at https://pkgsubmit.mageia.org/ to get
    a feel as to what is in the pipe to decide if you want to get the latest updates for your Cauldron install.

    Note: if your see a "Upload in progress for xxxx minutes" you may want
    to wait until the upload is completed AND is on your mirror of choice.

    Since you are running Plasma/KDE as your DE. I would keep an eye on the core/updates_testing queue for k* files. A large number of k* packages
    in that queue indicates another big update will show up for install
    on your Cauldron install.

    In the past when I used KDE, that was a signal to me that I better backup
    my Cauldron install just in case the updated does not do well.

    Speaking of stale mirrors. You may want to consider using a script
    to sync your synthesis.hdlist.cz database files, pull down all the updates, test if they will install, and if so, do the actual update.

    My systems are on 24/7 and I have a daily cron job to pull down any
    updates and mail me a message if there is anything to install.

    I can recommend using a script so you can have a log of what went on
    and automagically check it for any problems.

    Here is a quick hack for you or any lurkers to play with. -----8<-----8<-----8<- cut below this line----8<-----8<-----8<-----8< #!/bin/bash #**********************************************************************
    #*
    #* pull_updates - pulls down updates and installs them Version 1.0
    #* depending on how script is called.
    #*
    #* Usage:
    #* pull_updates downloads all rpms
    #* install_updates installs all rpms
    #*
    #* pull_updates can run in cron
    #*
    #*
    #* Assumptions: xmessage and wget rpms are installed and install
    #* location is in your PATH environment variable.
    #*
    #* Install procedure:
    #* Save script as pull_updates
    #* chmod +x pull_updates
    #*
    #* Verify it works with ./pull_updates
    #*
    #* Typical system install
    #* cp pull_updates /usr/local/bin
    #* cd /usr/local/bin
    #* ln -sf pull_updates install_updates
    #* cd
    #*
    #* This is free software released to public domain. Do with it whatever you want.
    #*
    #*********************************************************************

    export PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin

    _app=$(basename $0)
    _node=$(hostname --alias)
    _exe=$0

    TMPDIR=$HOME/tmp/$_app
    _cnt=0
    _dn_ldr="--downloader wget"
    _doing_what=""
    _exclude_words="-Conflicts|-error"
    _fault_words="fail|Broken pipe|affected|mismatch|missing|invalid|problem|unsatisfied|Unsafe| conflicts|problem reading|: line|wrong|Medium without key"
    _fn=""
    _log_fn="$TMPDIR/$_app.log"
    _tmp_fn=$TMPDIR/${_app}_$$.tmp
    _req_apps="xmessage wget"
    _rpm_dir=/var/cache/urpmi/rpms
    _urpmi_cmd="--test"
    _xmsg_fn=$TMPDIR/${_app}_$$.xmsg
    _xmsg_color=""
    _xmsg_title=""
    _xmsg_type="unknown"
    _x_title="$_node $_app ${_xmsg_type} ${_xmsg_title}"

    #**********************************
    #* dynamic variable setup
    #**********************************

    if [ "$_app" = "install_updates" ] ; then
    _urpmi_cmd=""
    _doing_what="\n\tChecking installed rpms and installing updates"
    _fault_words='bad rpm|warning|'$_fault_words
    else
    _doing_what="\n\tChecking installed rpms and pulling down updates"
    _fault_words='error|'$_fault_words
    fi

    if [ -z "$DISPLAY" ] ; then
    DISPLAY=:0
    fi


    tty -s
    export _cron_flg=$? # $?=0 interactive $?=1 cron

    if [ $_cron_flg -ne 0 ] ; then
    export COLUMNS=80
    export LINES=24
    fi

    function progress ()
    {
    #****************************************
    # outputs message unless running in cron.
    #****************************************

    if [ $_cron_flg -eq 0 ] ; then
    echo -e "$*"
    fi
    } # end function progress

    function xmsg ()
    {

    #***********************************************************************
    #*
    #* functions_xmsg - prints message in an xmessage pop up.
    #*
    #*
    #* Requirements:
    #* uses global variable _cron_flag to decide if running in cron or not
    #* and _app to create _xmsg_fn.
    #*
    #* xmsg arguments are in the following case statement
    #* contents of _xmsg_fn is what to be displayed.
    #*

    #***********************************************************************

    _xmsg_type="$1"

    _x_title="$_node $_app ${_xmsg_type} ${_xmsg_title}"
    echo -e "# $_xmsg_type message from $_exe on $_node\n " >> $_xmsg_fn
    case $_xmsg_type in
    FAILURE) _xmsg_color="-fg white -bg red" ;;
    FATAL) _xmsg_color="-fg white -bg red" ;;
    INFO) _xmsg_color="-fg black -bg PaleGreen1 " ;;
    TODO) _xmsg_color="-fg black -bg PaleTurquoise1 " ;;
    WARNING) _xmsg_color="-fg black -bg yellow" ;;
    *) _called_exe=$(ps -o command= $PPID)
    echo "Fatal codding error:
    invalid argument: $_xmsg_type
    passed to xmsg function.
    $_app $_called_exe
    "
    exit 1
    ;;
    esac

    if [ $_cron_flg -eq 0 ] ; then
    nohup xmessage -display $DISPLAY -title "$_x_title" $_xmsg_color \
    -file $_xmsg_fn \
    > /dev/null 2>&1 &
    sleep 2
    else
    cat $_xmsg_fn
    fi

    if [ $_xmsg_type = "FATAL" ] ; then
    exit 1
    fi
    } # end function xmsg

    function ck_cauldron ()
    {
    #**************************************************************
    #* if media is cauldron upload status
    #**************************************************************

    _cnt=$(grep --count cauldron /etc/urpmi/urpmi.cfg)
    if [ $_cnt -ne 0 ] ; then
    rm -f index.html
    wget --quiet --tries=2 --timeout=10 --no-remove-listing http://pkgsubmit.mageia.org/
    _cnt=$(grep --count -E "Upload in progress" index.html)
    if [ $_cnt -ne 0 ] ; then
    echo -e "FYI:
    cauldron Upload in progress
    so you might want to check http://pkgsubmit.mageia.org/
    " >> $_xmsg_fn
    _xmsg_title=ck_cauldron
    xmsg TODO
    fi
    fi
    } # end function ck_cauldron

    function update_synthesis_files ()
    {
    progress "\n\tchecking media files with"
    progress "\turpmi.update -a --wait-lock $_dn_ldr"

    _xmsg_fn=$TMPDIR/${_app}_update_synthesis_files_$$.tmp

    urpmi.update -a --wait-lock $_dn_ldr > $_xmsg_fn 2>&1
    if [ $? -ne 0 ] ; then
    _rtn=$?
    xmsg FAILURE
    exit $_rtn
    fi
    } # end function update_synthesis_files

    function list_rpms ()
    {
    _cnt=$(ls $_rpm_dir/* 2> /dev/null | wc -l)
    if [ $_cnt -ne 0 ] ; then
    echo -e "\n\t$_cnt packages in $_rpm_dir\n" > $_xmsg_fn
    ls $_rpm_dir/* >> $_xmsg_fn 2> /dev/null
    echo "

    # To install $_cnt packages, run
    install_updates

    " >> $_xmsg_fn
    _xmsg_title list_rpms
    xmsg TODO
    fi
    } # end function list_rpms


    function ck_4_rpms ()
    {
    #********************************
    #* check for any cached rpm files
    #********************************

    _cnt=$(ls $_rpm_dir/* 2> /dev/null | wc -l)
    if [ $_cnt -ne 0 ] ; then
    echo -e "\n\tPossible old or superseded rpms in $_rpm_dir\n" > $_xmsg_fn
    ls $_rpm_dir/* >> $_xmsg_fn 2> /dev/null
    echo "

    # To remove all uninstalled packages:
    /bin/rm -f $_rpm_dir/* ; pkill -f \"$_node $_app WARNING ck_4_rpms\"


    # To exclude failing install package add it to skip list
    # edit /etc/urpmi/skip.list
    " >> $_xmsg_fn
    _xmsg_title ck_4_rpms
    xmsg WARNING
    fi

    } # end function ck_4_rpms


    function fault_check ()
    {
    progress "\n\trunning function fault_check"
    cp -f /dev/null $_xmsg_fn

    pwck -r > $_tmp_fn 2>&1
    _cnt=$(wc -l < $_tmp_fn)
    if [ $_cnt -ne 0 ] ; then
    echo "The following came from running pwck -r " >> $_xmsg_fn
    cat $_tmp_fn >> $_xmsg_fn
    echo "------------------------" >> $_xmsg_fn
    fi

    ldconfig > $_tmp_fn 2>&1
    _cnt=$(wc -l < $_tmp_fn)
    if [ $_cnt -ne 0 ] ; then
    echo "The following came from running pwck -r " >> $_xmsg_fn
    cat $_tmp_fn >> $_xmsg_fn
    echo "------------------------" >> $_xmsg_fn
    echo " " >> $_urpmi_log
    fi

    _cnt=$(grep -iEv -- "$_exclude_words" $_log_fn | grep --count -iE "$_fault_words")
    if [ $_cnt -ne 0 ] ; then
    echo -e "\nThe following came from checking $_log_fn for faults " > $_tmp_fn
    sed 's/\(###\)\([[:alpha:]]\)/\1\n\2/' $_log_fn >> $_tmp_fn
    mv $_tmp_fn $_log_fn
    grep -iEv -- "$_exclude_words" $_log_fn | grep -iE "$_fault_words" >> $_xmsg_fn
    echo -e "
    #### above came from
    # $_app
    # log file is $_log_fn
    " >> $_xmsg_fn
    _xmsg_title="fault_check"
    xmsg FAILURE

    #****************************************
    # send a copy to root
    #****************************************
    tr -d \\r < $_xmsg_fn > $_tmp_fn
    mv -f $_tmp_fn $_xmsg_fn
    mail -S encoding=8bit -s "$_node has $_app failures" root < $_xmsg_fn
    fi

    if [ $_app = "install_updates" ] ; then
    ck_4_rpms
    fi

    progress "\n\tCompleted function fault_check"
    } # end function fault_check()

    #**********************************
    #* main code starts here
    #**********************************

    if [ $(id --user --name ) != "root" ] ; then
    echo "You need to be root to run $_app"
    exit 1
    fi

    for _ap in $_req_apps ; do
    _cnt=0
    type -p $_ap > /dev/null 2>&1
    if [ $? -ne 0 ] ; then
    echo "$_app requires $_ap to be installed"
    (( _cnt++ ))
    fi
    done

    if [ $_cnt -ne 0 ] ; then
    exit 1
    fi

    mkdir --parent --verbose $TMPDIR
    if [ $? -ne 0 ] ; then
    echo "$_app FATAL ERROR: unable to create $TMPDIR"
    exit 1
    fi

    cd $TEMPDIR
    if [ $? -ne 0 ] ; then
    echo "$_app FATAL ERROR: Unable to cd $TMPDIR"
    exit 1
    fi

    rm -f $TMPDIR/${_app}_*.tmp
    rm -f $TMPDIR/${_app}_*.xmsg

    pkill -f "title $_node $_app"

    ck_cauldron
    update_synthesis_files

    progress "$_doing_what"

    script -c "urpmi $_dn_ldr --auto --auto-update $_urpmi_cmd" $_log_fn
    fault_check

    progress "\nCompleted $_app\n"

    exit 0

    #******************** end pull_updates ********************************



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Mon Jul 13 12:29:21 2020
    On 7/12/20 5:07 PM, Gilberto F da Silva wrote:
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    because a new window is opened for each selected repository. In addition >>> to having to click more, you still have to wait for each one to load.

    ?? You can always add them later rather than during installation.
    And why do you want more than one repository?

    Bill, most of us use but one mirror, but we all have multiple
    repositories - Core Release, Core Updates, etc.

    Well ... The idea is to have access to all programs packaged for the
    version in use. I do this so as not to have to configure more
    repositories when I don't find any desired program. With all
    repositories enabled, if any package was not found it is because it does
    not exist.


    Please read

    https://wiki.mageia.org/en/Software_management

    When adding a mirror, I highly recommend using a specific mirror, rather
    than using "the automatic way" described in the wiki. I use the
    math.princeton mirror in the U.S. and have few problems.

    It is not a good idea to have all repositories marked as enabled. In
    general, you should only enable Core Release, Core Updates, Non-free
    Release, Non-free Updates, and if you want, Tainted Release and Tainted Updates. Unless you have a special need for them, do NOT activate any repository marked "testing" or "Debug" or "Backport."




    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz
    Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs:
    179 Shell: inxi: 3.1.04






    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Mon Jul 13 15:29:43 2020
    On 2020-07-13, TJ <TJ@noneofyour.business> wrote:
    On 7/12/20 5:07 PM, Gilberto F da Silva wrote:
    William Unruh escreveu:
    On 2020-07-12, Gilberto F da Silva <gfs1989@gmx.net> wrote:

    because a new window is opened for each selected repository. In addition >>>> to having to click more, you still have to wait for each one to load.

    ?? You can always add them later rather than during installation.
    And why do you want more than one repository?

    Bill, most of us use but one mirror, but we all have multiple
    repositories - Core Release, Core Updates, etc.

    I call a repository a place where I store things. A mirror is a special reporitory which is the same as some other fiducial repository. For me
    it is not like "CORE", "CORE UPDATE" ... It is like the difference
    between a bank and an account. One can have many accounts in one bank.

    It seems the OP and you call the equivalent to the accounts a
    repository. THat was why at one point I tried to get him to clarify what
    he meant by repository. That confusion was eventually cleared up.



    Well ... The idea is to have access to all programs packaged for the
    version in use. I do this so as not to have to configure more
    repositories when I don't find any desired program. With all
    repositories enabled, if any package was not found it is because it does
    not exist.


    Please read

    https://wiki.mageia.org/en/Software_management

    When adding a mirror, I highly recommend using a specific mirror, rather than using "the automatic way" described in the wiki. I use the math.princeton mirror in the U.S. and have few problems.

    It is not a good idea to have all repositories marked as enabled. In general, you should only enable Core Release, Core Updates, Non-free Release, Non-free Updates, and if you want, Tainted Release and Tainted Updates. Unless you have a special need for them, do NOT activate any repository marked "testing" or "Debug" or "Backport."




    root@localhost seamonkey]# inxi
    CPU: Dual Core Intel Core2 6400 (-MCP-) speed/min/max: 1600/600/800 MHz >>>> Kernel: 5.7.8-desktop-1.mga8 x86_64 Up: 22m
    Mem: 1187.8/3928.6 MiB (30.2%) Storage: 376.23 GiB (13.9% used) Procs: >>>> 179 Shell: inxi: 3.1.04






    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From TJ@2:250/1 to All on Mon Jul 13 19:26:09 2020
    On 7/13/20 10:29 AM, William Unruh wrote:
    On 2020-07-13, TJ <TJ@noneofyour.business> wrote:

    Bill, most of us use but one mirror, but we all have multiple
    repositories - Core Release, Core Updates, etc.

    I call a repository a place where I store things. A mirror is a special reporitory which is the same as some other fiducial repository. For me
    it is not like "CORE", "CORE UPDATE" ... It is like the difference
    between a bank and an account. One can have many accounts in one bank.

    It seems the OP and you call the equivalent to the accounts a
    repository. THat was why at one point I tried to get him to clarify what
    he meant by repository. That confusion was eventually cleared up.


    I was trying to follow the lead of the wiki, but it isn't consistent
    with the use of "repository," either. One thing I notice, though, is
    that while Core, etc are always called "repositories" in the wiki, the
    higher, more general level (the bank in your analogy) is called
    "sources," "media," "mirror," as well as "repository."

    TJ



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