Unending F42 install; Just hung on the final "Finalizaing" phase

Ask Fedora
1

System: Old asus motherboard running Athlonn 64 cpu

Started install using a usb drive.

It started up and took quite a bit of time on the first three parts. On the last part, Finalization, it was stuck for a couple of hours. I finally pressed the three dots on the top right of the screen which showed the following error:

Critical Error
The installer cannot continue due to a critical error.
Connection has timed out.

  1. This error was not made obvious. I wouldnt have known unless I clicked those ellipses.
    But the log file showed empty anyway.

Clicking Send logfile,
followed by quit was unresponsive! No effect.

So I had to manually shutdown the system.

I rebooted the system anyway and Fedora started with the usual questions of time zone and user name/id. Thats it.

  1. I wasnt asked for the hostname for the computer?
  2. I want to set the root passwd even though its not recommended. Yes, I plan to set up a couple of users and adding some to the sudo list. Really should be prompted for setting this passwd for users. I will try to set the root passwd using the grub method.
3

Try a different way of a Fedora 42 installation:

Fedora Everything 42 Network Installer

Select a minimal installation. No software. Reboot

Now download and install the rest: Desktop Enviroment, Software etc.

— Gnome —

Minimal Gnome and one terminal.

sudo dnf install -y gnome-shell alacritty

— Enable GNOME on boot.

systemctl enable gdm graphical.target
systemctl set-default graphical.target

Reboot

4

@karlsruhe: didnt qutie work.

Downloaded and booted from the Fedora Everything 42 installer you mentioned.
Seems to be the previous anaconda installer.
I dont really need gnome for now, so went with the xcfe desktop and very little else.
I was propmpted for the timezone, user id etc.
The install says it was a success.
However, upon boot up, grub did give me the fedora 42 option and fedora seems to be starting up but ends up in a black screen with no login prompt. I waited quite a while.
I hear the machine running though.

1 Like
5

Can you get a text console with “Ctrl Alt F3”? You can also use the grub2 editor to add a <space> 3 to the end of the kernel command line to boot into a text console.

If you can get a text console you may find useful details of the boot problem with journalctl. At this point it would also be useful to see the output (as pre-formatted text) from inxi -Fzxx.

1 Like
6

@gnwiii : Using your suggestion of adding 3 to the linux line, I was able to get into the console. A couple of errors:
The nouveau errors are after shutdown command though.

  1. unstable clock
  2. nouveau.* [HDMI.*scdc_low_rates::0] (ret: -22)

Hard to figure out from journalctl which are the errors that are contributing to a blank screen after bootup..