Black screen after a short time after system updates and bios update

i don’t know if it caused an manjaro software update or the bios uptate, but the solution I found contains a few things I didn’t find in the old forum posts
Short description:
Intel onboard and later AMD/ATI Radeon RX470
lightdm and x-server are faulty (systemctl)
x-server did not work because no displays were detected
AMD/ATI Radeon RX470 graphic card physically removed from the PC, no improvement
tried ssd on another PC with intel graphics, same error
back in the original PC, AMD graphics re-installed physical

under
/etx/X11/xorg.conf.d
at least the file
90-mhwd.conf
have to delete to have again a graphical system
I had made tests with terminal command and this means the file is missing, so I copy it after my solution again in this path, but the x-server could not run with it and in terminal mhwd does not create a new, maybe I’m using the mhwd command incorrectly

at first I thought this is my actual solution, creating a unit for systemd in the folder: /lib/systemd/system
xorg.service

[Unit]
Description=X Server
After=network.target

[Service]
User=root
ExecStart=/usr/bin/Xorg
Restart=always

[Install]
WantedBy=multi-user.target

than in tyy terminal:

systemctl daemon-reload
systemctl enable xorg
systemctl start xorg
systemctl status xorg

but I’m unsure because of the self failure with the file
90-mhwd.conf in the folder /etx/X11/xorg.conf.d

the kernel linux66 is used (6.6.54-2) (LTS)

later change frim onboard Intel to AMD/ATI RX470 in the bios settings

tests with gui hardinfo2 in both variants i.O.

But what was the real reason that the error occurred?
Has something been changed on systemd or on the x server or mhwd or pacman?

Can someone maybe give some hints, please?

Whats actually in 90-mhwd.conf ?
And what does mhwd say?

mhwd -li -l

This file contains usually instructions for nvidia and yes, it will block the graphical boot when no nvidia card or nvidia driver is found. I read in your profile that you had an Intel+Nivida setup and not Intel+AMD. So the switch must have caused the problem. Mhwd doesn’t remove the config in /etc/X11/ by removing the mhwd-config itself.

Why you update Bios and OS at the same time?

This would confuse everyone, no matter how much experience you have… update your OS, wait 2-4 days to get sure the OS is fine and then update your Bios.

2 Likes

the bios update to uefi was due to the intention to install Windows 11 for a specific application, but I rejected it;
after the bios update, I imagine that the manjaro worked quite normally;
the manjaro has only the purpose to realize audio recordings, I do not carry out updates so often, because I actually want to avoid problems;
but recently I switched from the other PC (manjaro KDE) to the manjaro Cinnamon PC because of a bug in LibreOffice Writer, on which FreeOffice did not have the bug; on the day I did the update and actually thought that I also did a reboot to be sure that it works; but I’m not sure about that

i sold the nvidia graphics card about a month after my last post about it and got one from AMD for it; i made benchmarks to compare the 2 cards; the PC definitely worked afterwards even without diue nvidia, with the AMD and the Intel onboard; what plays a role here is what is set in the bios, which variant then takes effect in Linux; i had installed the AMD graphics card back in the last time;

“Mhwd doesn’t remove the config in /etc/X11/ by removing the mhwd-config itself.”
this would mean that once you have installed an nvidia, the other graphics variants will no longer work, unless you personally delete the config file; yes OK, but the hint from you is still worth gold

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI
         network-r8168            2023.09.12                true            PCI
           video-linux            2024.05.06                true            PCI


Warning: No installed USB configs!
> 0000:01:00.0 (0300:1002:67df) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:06:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2023.09.12                true            PCI


> 0000:00:02.0 (0380:8086:0112) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI

That will be a problem.
You should remove this post-haste.
And probably force reinstall the ‘group’ open driver profile.

( You should also remove everything else you did … like the extra services, any other test configs, and dont mess with the mhwd file again unless you manually edited it … in which case remove it before reinstalling the drivers. Put everything back the way it was. )

sudo mhwd -r pci video-vesa
sudo mhwd -f -i pci video-linux

Someone else did the same thing recently and installed that without thinking about it … so theres some extra information over there;

troubleshooting was more important to me than reinstalling;
I will do what you wrote, only I need to know which config files I need to delete – the system does not run with “90-mhwd.conf”, the file is currently deleted or moved to another location;
Should I also delete the “xorg.service” file that I created myself? That would crash the x-server again. i’d better wait with that.
But, thank you very much !!!

Im pretty sure just about everything is related to having vesa installed.
So yes, I do suggest removing whatever you created.
The 90-mhwd file will be recreated in the above steps when reinstalling video-linux.
But with vesa removed I dont think you will have the same issues.

now

mhwd -li -l

> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
     video-modesetting            2020.01.13                true            PCI
         network-r8168            2023.09.12                true            PCI
           video-linux            2024.05.06                true            PCI


Warning: No installed USB configs!
> 0000:01:00.0 (0300:1002:67df) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:06:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2023.09.12                true            PCI


> 0000:00:02.0 (0380:8086:0112) Display controller Intel Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2024.05.06                true            PCI

but I haven’t rebooted yet

Oh I overlooked the dual-gpu.

You might have wanted to reinstall the modesetting driver as well.
Nevermind, looked it up and it doesnt really do anything these days.

But otherwise yay, vesa appears gone.

but one more question, I had the graphics drivers and lightdm and x-server all deninstalled, then the /lib/systemd/system
“xorg.service” file, then executed the systemd commands, only then the x server ran again, see my first post;
theoretically, the mhwd command would have done this after deleting the 90-mhwd.conf and removing the vesa drivers also done? because I used pacman to install

I’m not sure I understand the question?

You removed lightdm ? So you dont have a display manager?

You edited some systemd services?

Whatever the case … undo all of your changes.

Restore your system to how it was before.

If that means reinstalling a package or deleting file, then do those things.

When your system is otherwise ‘normal’;

  • Remove video-vesa via mhwd.

  • Reinstall video-linux via mhwd.

  • Reboot.

1 Like

I somehow missed that; too close to drinking-up time and getting those stools up and curtains shut, and probably also being snuggled by one of the Pub cats.

This does not look like a good approach.

I remember (when on Ubuntu-base years ago) that APT bug which took out loads of stuff like this; reinstalled the missing stuff using the logs I’d saved as reference for what to put back.

Maybe try that approach?