Solved Fedora 43 booting to black screen, even after reinstalls

Solved issue


By default, Fedora doesn't "auto-update", you have to enable it.
You can disable it, if it is enabled.

But also the grub menu typically holds three kernel updates.
Use the down arrow at the grub menu to roll back to a previous version.
(It usually only gives you about 5 seconds or so to do this).
 
That means you never had the nvidia drivers installed but were using nouveau drivers.

1. Enable rpmfusion:
2. Install the Nvidia driver:
For Fedora 43 this is no longer required, the nvidia drivers are in the fedora repos.

But you are correct, you still have to install them, I suspect he is using novuaex.
@ozfbu seems my information is a bit outdated, but I'm not using Fedora. So try searching in the repos for "nvidia" as @dos2unix mentioned.
Code:
dnf search nvidia
 
You told him to "re-install", there was no matching package already installed with that name.
Yeah because that's the last known package name I've know for Nvidia on Fedora from rpmfusion, what's the name of the nvidia package called since it has been moved to the default repos?
 
sudo dnf install kmod-nvidia
gets the same error

You told him to "re-install", there was no matching package already installed with that name.
No package to install called "kmod-nvidia"



By default, Fedora doesn't "auto-update", you have to enable it.
You can disable it, if it is enabled.

But also the grub menu typically holds three kernel updates.
Use the down arrow at the grub menu to roll back to a previous version.
(It usually only gives you about 5 seconds or so to do this).
Ah. I meant "how do I apply all upgrades from or before a certain point?", so that I have a build that isn't months out of date ;)
 
Ah. I meant "how do I apply all upgrades from or before a certain point?", so that I have a build that isn't months out of date ;)
You install the updates from the software center, or run "sudo dnf update" from the terminal and it will update all available packages than can be updated.

Code:
dnf search nvidia
 
Yeah because that's the last known package name I've know for Nvidia on Fedora from rpmfusion, what's the name of the nvidia package called since it has been moved to the default repos?

For current NVIDIA cards
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia xorg-x11-drv-nvidia-cuda
You had the package name correct, the reason it failed, it because "re-install" looks for installed packages first, then the repo.
If it never was installed, it say "no match".

You were very very close :-), if you would have just said "install: instead of "reinstall" it would have worked :-).
 
You had the package name correct, the reason it failed, it because "re-install" looks for installed packages first, then the repo.
If it never was installed, it say "no match".
Yeah I missed that and I was under the assumption the driver was already installed since OP is using the Nvidia gpu, wasn't expecting that the nouveau driver was being used.

@ozfbu what @dos2unix said.
For current NVIDIA cards
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia xorg-x11-drv-nvidia-cuda
After it's done installing wait 2-3 minutes and then reboot.
 
@ozfbu what @dos2unix said.

dos2unix said:
For current NVIDIA cards
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia xorg-x11-drv-nvidia-cuda

After it's done installing wait 2-3 minutes and then reboot.

Curl error (6): Could not resolve hostname for https://mirror.fedoraproject.org/...
Pinging www.linux.org got the same error

On the one hand, this is obviously a network issue :)
On the other hand...Fedora and my account could connect to the Fedora mirrors, or I wouldn't have been able to download Fedora updates that led to the black screen
So...how do I get my computer connected to the Internet as before please?
 
Share the output of the following.
Code:
cat /etc/resolv.conf
A load of commented-out text, then:

Code:
nameserver 127.0.0.53
options edns0 trust-ad
search .
 
A load of commented-out text, then:
Can you share the output of the following then?
Code:
 nmcli con show bridge-br0 | grep -i dns
Replace "bridge-br0" with your actual connection name which you can find by running "nmcli con show".
 
Can you share the output of the following then?
Code:
 nmcli con show bridge-br0 | grep -i dns
Replace "bridge-br0" with your actual connection name which you can find by running "nmcli con show".

connection.mdns: -1 (default)
connection.dns-over-tls: -1 (default)
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.routed-dns: -1 (default)
ipv4.ignore-auto-dns: no
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: --
ipv6.dns-priority: 0
ipv6.routed-dns: -1 (default)
ipv6.ignore-auto-dns: no
 
Looks like the default is dns over tls, I can't remember that being the default with Fedora. You can look here how that works.

Main file is this, if you could share the output.
Code:
cat /etc/systemd/resolved.conf

And also check this file.
Code:
cat /etc/NetworkManager/conf.d/10-dns-systemd-resolved.conf

To check the status run the following.
Code:
resolvectl status
resolvectl query fedoraproject.org

Check the status of the needed services.
Code:
systemctl status systemd-resolved NetworkManager

Other thing you could try is adding normal dns servers to your config.
Code:
nmcli connection modify bridge-br0 +ipv4.dns "9.9.9.9 149.112.112.112
Replace "bridge-br0" with your network interface and then also run the following.
Code:
sudo nmcli con reload
 
Looks like the default is dns over tls, I can't remember that being the default with Fedora. You can look here how that works.

Main file is this, if you could share the output.
Code:
cat /etc/systemd/resolved.conf

And also check this file.
Code:
cat /etc/NetworkManager/conf.d/10-dns-systemd-resolved.conf

To check the status run the following.
Code:
resolvectl status
resolvectl query fedoraproject.org

Check the status of the needed services.
Code:
systemctl status systemd-resolved NetworkManager

Other thing you could try is adding normal dns servers to your config.
Code:
nmcli connection modify bridge-br0 +ipv4.dns "9.9.9.9 149.112.112.112
Replace "bridge-br0" with your network interface and then also run the following.
Code:
sudo nmcli con reload

cat /etc/systemd/resolved.conf
No such file or directory

cat /etc/NetworkManager/conf.d/10-dns-systemd-resolved.conf
No such file or directory

resolvectl status
I don't see anything that says "status", and it's a bit of information...what am I looking for more specifically please?

resolvectl query fedoraproject.org
Can't access it

systemctl status systemd-resolved NetworkManager
A lot of information

...
Network Name Resolution
...
Active: active (running)
...
Network Manager
...
Active: active (running)
...

I removed the VPN from Fedora via sudo dnf remove [VPN name] yesterday in case that was causing an issue; I have a VPN on my router (thanks forum)

I suspect that it's the lack of resolved.conf files in /etc that's causing my Internet issue. How do I re-create these please?
I have a USB with the Fedora ISO on
 
cat /etc/systemd/resolved.conf
No such file or directory

cat /etc/NetworkManager/conf.d/10-dns-systemd-resolved.conf
No such file or directory

resolvectl status
I don't see anything that says "status", and it's a bit of information...what am I looking for more specifically please?

resolvectl query fedoraproject.org
Can't access it
Seems like it's not setup then.

I removed the VPN from Fedora via sudo dnf remove [VPN name] yesterday in case that was causing an issue; I have a VPN on my router (thanks forum)
No idea if you vpn client handles some stuff, you could try disabling it and then see what happens.

Also still try this.
Other thing you could try is adding normal dns servers to your config.
nmcli connection modify bridge-br0 +ipv4.dns "9.9.9.9 149.112.112.112Replace "bridge-br0" with your network interface and then also run the following.
sudo nmcli con reload
 
Other thing you could try is adding normal dns servers to your config.
Code:
nmcli connection modify bridge-br0 +ipv4.dns "9.9.9.9 149.112.112.112
Replace "bridge-br0" with your network interface and then also run the following.
Code:
sudo nmcli con reload
Done, but same failures in name resolution

Looks like the default is dns over tls, I can't remember that being the default with Fedora. You can look here how that works.
I've followed steps 1, 2, and 3 to the character, but resolvectl status is not showing any DNS servers, and resolvectl query fedoraproject.org gives resolve call failed: No appropriate name servers or networks for name found

I attach a screenshot of what my configuration looks like:
 

Attachments

  • IMG_20260307_194108Z.jpg
    IMG_20260307_194108Z.jpg
    3 MB · Views: 53


Follow Linux.org

Members online


Top