• Screen showing 3 question marks.

    From Doug Laidlaw@2:250/1 to All on Sun Sep 12 14:45:26 2021
    This has happened to me before, and from Bug 1964 (now closed) it was happening to quite a few people around that time. It was said not to be
    a bug affecting performance, only a cosmetic one.

    In my case, I see a gray screen having in the center, 3 small squares,
    more a dirty white color, each containing a "?". Mageia 8 keeps loading
    in text mode for a few lines, then the graphical login screen appears.
    My video card is nvidia, and I configure it to use Mageia's nvidia
    driver. Twice in a row, X says that it doesn't like that arrangement,
    changes the driver to nouveau, and tells me to reboot to give effect to
    the change. There may be a recent upgrade of the driver: it was O.K.
    about a week ago.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Sun Sep 12 17:35:16 2021
    On Sun, 12 Sep 2021 09:45:26 -0400, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:

    This has happened to me before, and from Bug 1964 (now closed) it was happening to quite a few people around that time. It was said not to be
    a bug affecting performance, only a cosmetic one.

    In my case, I see a gray screen having in the center, 3 small squares,
    more a dirty white color, each containing a "?". Mageia 8 keeps loading
    in text mode for a few lines, then the graphical login screen appears.
    My video card is nvidia, and I configure it to use Mageia's nvidia
    driver. Twice in a row, X says that it doesn't like that arrangement, changes the driver to nouveau, and tells me to reboot to give effect to
    the change. There may be a recent upgrade of the driver: it was O.K.
    about a week ago.

    The screen with 3 question marks is grub failing to load properly. Check the journal. It may be a filesystem failing to mount or some other problem preventing
    grub from loading the graphics it uses, such as a typo in the grub configuration.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Mon Sep 20 17:06:10 2021
    On 13/9/21 2:35 am, David W. Hodgins wrote:
    The screen with 3 question marks is grub failing to load properly. Check
    the
    journal. It may be a filesystem failing to mount or some other problem preventing
    grub from loading the graphics it uses, such as a typo in the grub configuration.

    Regards, Dave Hodgins

    Thanks, Dave. You are spot on. The journal is full of lines where each command from grub is read in turn. I didn't look back far enough
    before. There was a reference to a config error in my 40_custom file,
    so I will mark that file not executable and try again. Your comments
    seem to imply that the strange colours between screens come from the
    same cause. Also this:


    "40grub2: appears to be an automatic reference taken from another grub.cfg"

    I was always told that copying and pasting is the wrong way to do anything.

    Doug.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Mon Sep 20 17:23:32 2021
    On 9/20/21 09:06, Doug Laidlaw wrote:
    On 13/9/21 2:35 am, David W. Hodgins wrote:
    The screen with 3 question marks is grub failing to load properly.
    Check the
    journal. It may be a filesystem failing to mount or some other problem
    preventing
    grub from loading the graphics it uses, such as a typo in the grub
    configuration.

    Regards, Dave Hodgins

    Thanks, Dave. You are spot on.  The journal is full of lines where each command from grub is read in turn.  I didn't look back far enough
    before.  There was a reference to a config error in my 40_custom file,
    so I will mark that file not executable and try again.  Your comments
    seem to imply that the strange colours between screens come from the
    same cause.  Also this:


    "40grub2: appears to be an automatic reference taken from another grub.cfg"

    I was always told that copying and pasting is the wrong way to do anything.

    Doug.

    Doug, that depends on what you are doing.
    But is seems to be over-used at times in coding.

    bliss - Your tag lines (k) were stolen! (more)
    There is a puff of smoke!
    Damned theives...
    Quaff a Ption of See Invisble and it is Smeagol at high
    speed and teleporting. Draw Ringle and dispatch him.

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Mon Sep 20 18:36:59 2021
    On 21/9/21 2:23 am, Bobbie Sellers wrote:

        Doug, that depends on what you are doing.
    But is seems to be over-used at times in coding.

    I wouldn't know about coding, but it is over-used in genealogy. It is
    too easy to copy somebody else's work without any checking. Then when
    somebody who does check, comes along, he has a bigger mess to wade through.

    But here, I am basically having problems with "original" code that works
    for others, and that used to work for me. Disabling 40_custom did what
    it is supposed to, but didn't change anything. I thought that I had my
    box recovered from a BIG crash, but there are still issues.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Bobbie Sellers@2:250/1 to All on Mon Sep 20 20:15:44 2021
    On 9/20/21 10:36, Doug Laidlaw wrote:
    On 21/9/21 2:23 am, Bobbie Sellers wrote:

         Doug, that depends on what you are doing.
    But is seems to be over-used at times in coding.

    I wouldn't know about coding, but it is over-used in genealogy.  It is
    too easy to copy somebody else's work without any checking. Then when somebody who does check, comes along, he has a bigger mess to wade through.

    But here, I am basically having problems with "original" code that works
    for others, and that used to work for me.  Disabling 40_custom did what
    it is supposed to, but didn't change anything.  I thought that I had my
    box recovered from a BIG crash, but there are still issues.

    I feel your disquiet.
    One of mine has been sidelined since last month
    after an ill-considered attempt to get / more space.
    I have find time to think about what partitions to create.
    Timeshift could not find its backups so I moved to another
    not quite as powerful but adequate to my needs.

    bliss

    --
    bliss dash SF 4 ever at dslextreme dot com

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: dis-organization (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Thu Sep 23 00:53:25 2021
    On 21/9/21 5:15 am, Bobbie Sellers wrote:
    On 9/20/21 10:36, Doug Laidlaw wrote:
    On 21/9/21 2:23 am, Bobbie Sellers wrote:

         Doug, that depends on what you are doing.
    But is seems to be over-used at times in coding.

    I wouldn't know about coding, but it is over-used in genealogy.  It is
    too easy to copy somebody else's work without any checking. Then when
    somebody who does check, comes along, he has a bigger mess to wade
    through.

    But here, I am basically having problems with "original" code that
    works for others, and that used to work for me.  Disabling 40_custom
    did what it is supposed to, but didn't change anything.  I thought
    that I had my box recovered from a BIG crash, but there are still issues.

        I feel your disquiet.
        One of mine has been sidelined since last month
    after an ill-considered attempt to get / more space.
    I have find time to think about what partitions to create.
    Timeshift could not find its backups so I moved to another
    not quite as powerful but adequate to my needs.

        bliss

    Well, I got it fixed, but I am not entirely sure what did it.

    Normally, I have /var on a separate partition. On any reinstall, I
    blank the partition then restore any current data files from the latest backup. I then have to change the ownerships to match the new list of
    root user IDs. Anything that I miss, won't work. I found one lock file
    I had missed, that was preventing postfix from starting. While in
    nouveau, I uninstalled dkms-nvidia: it causes problems every time. Then
    I reinstalled the distro's nvidia package. That fixed everything except
    for a small graphic before the desktop comes up.

    --- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)