Invalid Format error

Hi I just upgraded to Fedora 33 Server from 32 Server. When it reboots with the 5.10.6 kernel, I get a graphic that appears on the screen saying “Invalid Format”. Any ideas?

Here are my filesystems:

/dev/mapper/fedora-root / xfs defaults 0 0
UUID=96618861-e388-4bc8-ad09-9512be41aee2 /boot ext4 defaults 1 2
UUID=11E9-576B /boot/efi vfat umask=0077,shortname=winnt 0 2
/dev/mapper/fedora-swap swap swap defaults 0 0
UUID=e221b68a-fe29-4171-b47e-af5cbc8c9fac /media/usbdrive xfs defaults 0 2

The bottom xfs filesystem is a USB external hard drive.

Thanks for the help!

2 Likes

Try to boot with another kernel version, otherwise use chroot in a live session and collect the output:

lsblk -o +FSTYPE,UUID; cat /etc/default/grub; grep -v -e ^# -e ^$ /etc/fstab

@jihood welcome to ask.fedora

I believe the error is caused because your efi is not fat32. At least it is what i was reading here in the forum a while ago.

This would be my idea why you get the “invalid format” message.

I booted into the prior kernel, version 5.9.16. Here is the output from your commands:

NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT      FSTYPE      UUID
sda               8:0    0 465.8G  0 disk
├─sda1            8:1    0   200M  0 part /boot/efi       vfat        11E9-576B
├─sda2            8:2    0     1G  0 part /boot           ext4        96618861-e388-4bc8-ad09-9512be41aee2
└─sda3            8:3    0 464.6G  0 part                 LVM2_member dKEbqt-QeKt-3RzZ-8pdx-IRbT-hzQu-YFaCAz
  ├─fedora-root 253:0    0    15G  0 lvm  /               xfs         ffc47ab5-5082-4137-b61f-d7cb8ac3c7fb
  └─fedora-swap 253:1    0   7.9G  0 lvm  [SWAP]          swap        3bfe86d2-2861-41e3-92a9-b9068e0be287
sdb               8:16   0   1.8T  0 disk
└─sdb1            8:17   0   1.8T  0 part /media/usbdrive xfs         e221b68a-fe29-4171-b47e-af5cbc8c9fac
zram0           252:0    0     4G  0 disk [SWAP]
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet pci=noaer"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
/dev/mapper/fedora-root                   /                       xfs     defaults        0 0
UUID=96618861-e388-4bc8-ad09-9512be41aee2 /boot                   ext4    defaults        1 2
UUID=11E9-576B                            /boot/efi               vfat    umask=0077,shortname=winnt 0 2
/dev/mapper/fedora-swap                   swap                    swap    defaults        0 0
UUID=e221b68a-fe29-4171-b47e-af5cbc8c9fac /media/usbdrive         xfs     defaults        0 2
1 Like

This matches what I have (except for UUID of course) so I see no reason for that to be invalid format.

How did you do the upgrade from 32 to 33? Using dnf with the system-upgrade plugin? or something else?
Is that message coming from grub or after the kernel starts to load?
Have you run fsck on /dev/mapper/fedora-root and the /boot device while booted from the live USB just in case?
Since you were able to boot from an earlier kernel, which one? F33 base kernel or F32 kernel?
Have you tried booting with the USB device removed to eliminate that possibility?
Have you tried to do a “dnf upgrade”, or “dnf erase kernel*5.10.6*” followed by “dnf upgrade”, while booted from the kernel that does work?

If everything works except that kernel the uninstall followed by a new install of that kernel may fix it totally.

My workstation runs fine with the 5.10.6 kernel.
Your 3 primary partitions are 3 different file system types (vfat, ext4, and xfs) so anything is possible, but I am led toward the kernel problem first.

Hey JV,

Thanks for the ideas. Let me reply first with the ones I already know and circle back again once I’ve tried your other suggestions.

How did you do the upgrade from 32 to 33?

$ sudo dnf upgrade --refresh
$ #sudo dnf install dnf-plugin-system-upgrade (did this long ago when upgrading from F28->F29)
$ sudo dnf system-upgrade download --releasever=33
$ sudo dnf system-upgrade reboot

Is that message coming from grub or after the kernel starts to load?

Not 100% sure… it’s at least after the grub menu goes away, leaving the default top one alone - F33’s 5.10.6. It’s a moving animated graphic, similar in appearance to what a screensaver would look like. I wish I could upload a picture of it, but the forum says new users aren’t allowed to do that. :slight_smile:

Since you were able to boot from an earlier kernel, which one? F33 base kernel or F32 kernel?

An F32 kernel, 5.9.16, which was the most recent F32 one available before the upgrade.

1 Like

Check this one to isolate the issue:

sudo dnf downgrade kernel

Have you tried booting with the USB device removed to eliminate that possibility?

Gave that a whirl, no luck unfortunately.

Have you tried to do a “dnf upgrade”

I hadn’t yet since upgrading to F33, but I now tried “sudo dnf upgrade” while booted from F32’s 5.9.16. It upgraded to 5.10.7. Still the Invalid Format error upon reboot into 5.10.7.

or “dnf erase kernel5.10.6” followed by “dnf upgrade”, while booted from the kernel that does work?

Since I did the “dnf update” already, I needed to erase 2 kernels:

$ sudo dnf erase kernel*5.10.7*
$ sudo dnf erase kernel*5.10.6*
$ sudo reboot # then chose F32's 5.9.16 from grub menu
$ sudo dnf upgrade
$ sudo reboot # then chose F33's 5.10.7 from grub menu

Unfortunately same result. At this point, I only have 5.10.7 and 5.9.16

However… I did just notice after these steps, I was able to ssh into the box successfully while the “Invalid Format” graphic was up on the box’s display. I then ran the commands again from @vgaetera. All the filesystems still look to be there also.

$ lsblk -o +FSTYPE,UUID; cat /etc/default/grub; grep -v -e ^# -e ^$ /etc/fstab
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT      FSTYPE      UUID
sda               8:0    0 465.8G  0 disk
├─sda1            8:1    0   200M  0 part /boot/efi       vfat        11E9-576B
├─sda2            8:2    0     1G  0 part /boot           ext4        96618861-e388-4bc8-ad09-9512be41aee2
└─sda3            8:3    0 464.6G  0 part                 LVM2_member dKEbqt-QeKt-3RzZ-8pdx-IRbT-hzQu-YFaCAz
  ├─fedora-root 253:0    0    15G  0 lvm  /               xfs         ffc47ab5-5082-4137-b61f-d7cb8ac3c7fb
  └─fedora-swap 253:1    0   7.9G  0 lvm  [SWAP]          swap        3bfe86d2-2861-41e3-92a9-b9068e0be287
sdb               8:16   0   1.8T  0 disk
└─sdb1            8:17   0   1.8T  0 part /media/usbdrive xfs         e221b68a-fe29-4171-b47e-af5cbc8c9fac
zram0           252:0    0     4G  0 disk [SWAP]
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=/dev/mapper/fedora-swap rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet pci=noaer"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
/dev/mapper/fedora-root                   /                       xfs     defaults        0 0
UUID=96618861-e388-4bc8-ad09-9512be41aee2 /boot                   ext4    defaults        1 2
UUID=11E9-576B                            /boot/efi               vfat    umask=0077,shortname=winnt 0 2
/dev/mapper/fedora-swap                   swap                    swap    defaults        0 0
UUID=e221b68a-fe29-4171-b47e-af5cbc8c9fac /media/usbdrive         xfs     defaults        0 2

Have you run fsck on /dev/mapper/fedora-root and the /boot device while booted from the live USB just in case?

I wish I could check this. My BIOS is resisting me on booting from a USB or SD card.

While making the live image though, I was able to successfully download the F33 Server iso from my laptop to /media/usbdrive on my F33 box via a Samba share pointing to that location. So, smbd and the external drive’s XFS filesystem also appear to be working fine under 5.7.10. While ssh’d into the box, I was also able to create the image with that iso file.

$ uname -a
Linux zbox.home.lan 5.10.7-200.fc33.x86_64 #1 SMP Tue Jan 12 20:20:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 
$ ls -l /media/usbdrive/downloads/Fe*
-rw-rw-r--. 1 samba media 2076180480 Jan 17 12:07 /media/usbdrive/downloads/Fedora-Server-dvd-x86_64-33-1.2.iso
$ sudo dnf install livecd-tools
$ sudo livecd-iso-to-disk --format --reset-mbr /media/usbdrive/downloads/Fedora-Server-dvd-x86_64-33-1.2.iso /dev/sdc
$ sudo mount /dev/sdc1 /media/sdcard
$ ls -l /media/sdcard
total 40
drwxr-xr-x.  3 root root  4096 Jan 17 13:15 EFI
drwxr-xr-x.  3 root root  4096 Jan 17 13:15 images
drwx------.  2 root root 16384 Jan 17 13:14 lost+found
-r--r--r--.  1 root root    95 Jan 17 13:15 media.repo
dr-xr-xr-x. 28 root root  4096 Jan 17 13:15 Packages
dr-xr-xr-x.  2 root root  4096 Jan 17 13:15 repodata
drwxr-xr-x.  2 root root  4096 Jan 17 13:18 syslinux
$ sudo umount /media/sdcard

So with the above abilities, I’m wondering if the filesystems may be ok and “Invalid Format” refers to something else? Is there a way to dismiss the moving animated graphic and see the console or look at a log somewhere while ssh’d into the box?

Thoughts on whether you think this is still a possibility given the discovery on @computersavvy’s reply?

The problem is probably specific to the 5.10 kernel and could be fixed in the 5.11 release, otherwise it’s worth raising an issue.

I agree it does not seem to be filesystem. It also is not likely directly tied to the kernel, but quite possibly video related.

What do you have for video and what drivers are installed. Please post the results of

inxi -Gxx
1 Like
$ sudo dnf install inxi
$ inxi -Gxx
Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5916
           Display: server: X.org 1.20.10 driver: modesetting unloaded: fbdev,vesa tty: 136x40
           Message: Advanced graphics data unavailable in console. Try -G --display
$ inxi -Gxx --display
Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5916
           Display: server: X.org 1.20.10 driver: modesetting unloaded: fbdev,vesa
           Message: No advanced graphics data found on this system.

On a normal boot up of this box, it just comes up to the console login. However, in case it’s relevant, I do have an X server installed for occasional KDE use as needed – which I just launch with “startx” for that.

Does the error appear in the terminal window or when you startx

That is an intel gpu so I am wondering why the errors since intel drivers are usually no problem. Booting from the 5.9 kernel is OK but not the 5.10 kernel— Hmmmm!
This seems specific to the 5.10 kernel and/or grub since you get that from grub during boot with the 5.10 kernel.

You have already removed and reinstalled the kernel so lets try a little bit different tack.

  1. boot to the 5.9 kernel
  2. rebuild grub
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Then try booting to one of the 5.10 kernels again.

If that works then good. If it fails then lets look at all your hardware with “inxi -Fxx”

The error appears after grub menu goes away and booting begins. The box appears to get pretty far in the boot process as many services are available (e.g., sshd, smbd, filesystem mounts) – but not so far in booting as seeing a console login. No startx command done on my part.

You have already removed and reinstalled the kernel so lets try a little bit different tack.

  1. boot to the 5.9 kernel
  2. rebuild grub
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

Then try booting to one of the 5.10 kernels again.

$ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

No luck. Same “Invalid Format” screensaver-esque error animation.

If it fails then lets look at all your hardware with “inxi -Fxx”

$ sudo inxi -Fxx
System:    Host: zbox.home.lan Kernel: 5.10.7-200.fc33.x86_64 x86_64 bits: 64 compiler: gcc v: 2.35-15.fc33) Console: tty 0
           DM: SDDM Distro: Fedora release 33 (Thirty Three)
Machine:   Type: Laptop Mobo: ZOTAC model: ZBOX-CI527/CI547NANO v: XX serial: XXXXXXXX UEFI: American Megatrends v: B331P208
           date: 06/26/2018
CPU:       Info: Dual Core model: Intel Core i3-7100U bits: 64 type: MT MCP arch: Amber Lake rev: 9 L1 cache: 128 KiB
           L2 cache: 3072 KiB L3 cache: 3000 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19200
           Speed: 500 MHz min/max: 400/2400 MHz Core speeds (MHz): 1: 500 2: 500 3: 501 4: 500
Graphics:  Device-1: Intel HD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5916
           Display: server: X.org 1.20.10 driver: modesetting unloaded: fbdev,vesa tty: 136x40
           Message: Advanced graphics data unavailable in console for root.
Audio:     Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71
           Sound Server: ALSA v: k5.10.7-200.fc33.x86_64
Network:   Device-1: Intel Ethernet I219-LM driver: e1000e v: kernel port: f040 bus ID: 00:1f.6 chip ID: 8086:156f
           IF: enp0s31f6 state: down mac: 00:01:2e:84:6b:01
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: e000 bus ID: 01:00.0
           chip ID: 10ec:8168
           IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: 00:01:2e:84:6b:02
           Device-3: Intel Wireless 3165 driver: iwlwifi v: kernel port: e000 bus ID: 02:00.0 chip ID: 8086:3165
           IF: wlp2s0 state: down mac: 6a:b3:48:71:c0:d2
Drives:    Local Storage: total: 2.30 TiB used: 13.24 GiB (0.6%)
           ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB speed: 6.0 Gb/s serial: 1823E14244B9
           temp: 33 C
           ID-2: /dev/sdb type: USB vendor: Western Digital model: WD Elements 25A2 size: 1.82 TiB
           serial: 57583731453636325A325334
           ID-3: /dev/sdc type: USB vendor: Generic model: SD MMC MS PRO size: 29.16 GiB serial: 20120926571200000
Partition: ID-1: / size: 14.99 GiB used: 9.15 GiB (61.0%) fs: xfs dev: /dev/dm-0
           ID-2: /boot size: 975.9 MiB used: 190.2 MiB (19.5%) fs: ext4 dev: /dev/sda2
Swap:      ID-1: swap-1 type: partition size: 7.86 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-1
           ID-2: swap-2 type: zram size: 4.00 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 34.0 C mobo: 29.8 C
           Fan Speeds (RPM): N/A
Info:      Processes: 178 Uptime: 1m Memory: 15.55 GiB used: 470.5 MiB (3.0%) Init: systemd v: 246 runlevel: 3
           target: multi-user.target Compilers: gcc: N/A Packages: rpm: 1896 Shell: Bash v: 5.0.17 running in: tty 0
           inxi: 3.1.08

Also, would there be any differences in what daemons are loaded between the 2 kernel boot-ups (either in which ones are loaded or what versions are loaded)? If so, could one of the daemons be creating this graphic during the boot sequence?

Another thing I can’t rule out yet either is if there’s something amiss with Plymouth, given its graphical boot animations during the boot process? This box is a sits in a TV stand unit, whose display when necessary is an LG 55’ OLED HDTV connected via HDMI. This setup is working fine in F32 and in ones before that. I tried changing the Plymouth theme to rule that out, but that had no effect:

$ plymouth-set-default-theme
bgrt
$ plymouth-set-default-theme --list
bgrt
details
spinner
text
tribar
$ sudo plymouth-set-default-theme details -R
$ sudo reboot
$ sudo cat /var/log/boot.log # see excerpt of this output below
$ sudo plymouth-set-default-theme bgrt -R
$ sudo reboot

Excerpt from boot.log:

------------ Tue Jan 19 01:59:27 CST 2021 ------------
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Found device /dev/mapper/fedora-root.
[  OK  ] Reached target Initrd Root Device.
[  OK  ] Found device /dev/mapper/fedora-swap.
         Starting Resume from hibernation using device /dev/mapper/fedora-swap...
[  OK  ] Finished Resume from hibernation using device /dev/mapper/fedora-swap.
[  OK  ] Reached target Local File Systems (Pre).
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Create Volatile Files and Directories.
[  OK  ] Reached target System Initialization.
[  OK  ] Reached target Basic System.
[  OK  ] Finished dracut initqueue hook.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting File System Check on /dev/mapper/fedora-root...
[  OK  ] Finished File System Check on /dev/mapper/fedora-root.
         Mounting /sysroot...
[  OK  ] Mounted /sysroot.
[  OK  ] Reached target Initrd Root File System.
         Starting Reload Configuration from the Real Root...
[  OK  ] Finished Reload Configuration from the Real Root.
[  OK  ] Reached target Initrd File Systems.
[  OK  ] Reached target Initrd Default Target.
         Starting dracut pre-pivot and cleanup hook...
[  OK  ] Finished dracut pre-pivot and cleanup hook.
         Starting Cleaning Up and Shutting Down Daemons...
[  OK  ] Stopped target Timers.
[  OK  ] Stopped dracut pre-pivot and cleanup hook.
[  OK  ] Stopped target Initrd Default Target.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Initrd Root Device.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target Slices.
[  OK  ] Stopped target Sockets.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped target Swap.
[  OK  ] Stopped dracut initqueue hook.
         Starting Plymouth switch root service...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Coldplug All udev Devices.
         Stopping Rule-based Manager for Device Events and Files...
[  OK  ] Finished Cleaning Up and Shutting Down Daemons.
[  OK  ] Stopped Rule-based Manager for Device Events and Files.
[  OK  ] Finished Plymouth switch root service.
[  OK  ] Closed udev Control Socket.
[  OK  ] Closed udev Kernel Socket.
[  OK  ] Stopped dracut pre-udev hook.
[  OK  ] Stopped dracut cmdline hook.
         Starting Cleanup udev Database...
         Stopping Hardware RNG Entropy Gatherer Daemon...
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create list of static device nodes for the current kernel.
[  OK  ] Finished Cleanup udev Database.
[  OK  ] Reached target Switch Root.
         Starting Switch Root...
[  OK  ] Stopped Hardware RNG Entropy Gatherer Daemon.

Welcome to Fedora 33 (Server Edition)!

[  OK  ] Stopped Switch Root.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Created slice system-modprobe.slice.
[  OK  ] Created slice system-sshd\x2dkeygen.slice.
[  OK  ] Created slice system-swap\x2dcreate.slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Set up automount Arbitrary Executable File Formats File System Automount Point.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Stopped target Switch Root.
[  OK  ] Stopped target Initrd File Systems.
[  OK  ] Stopped target Initrd Root File System.
[  OK  ] Reached target Slices.
[  OK  ] Listening on Device-mapper event daemon FIFOs.
[  OK  ] Listening on LVM2 poll daemon socket.
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
         Activating swap /dev/mapper/fedora-swap...
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Starting Create list of static device nodes for the current kernel...
         Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
         Starting Load Kernel Module configfs...
         Starting Load Kernel Module drm...
         Starting Load Kernel Module fuse...
         Starting Preprocess NFS configuration convertion...
[  OK  ] Stopped Plymouth switch root service.
[  OK  ] Stopped File System Check on Root Device.
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
         Starting Load Kernel Modules...
         Starting Remount Root and Kernel File Systems...
         Starting Coldplug All udev Devices...
[  OK  ] Activated swap /dev/mapper/fedora-swap.
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Finished Create list of static device nodes for the current kernel.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Preprocess NFS configuration convertion.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
[  OK  ] Finished Load Kernel Modules.
[  OK  ] Finished Remount Root and Kernel File Systems.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
         Starting Configure read-only root support...
         Starting Apply Kernel Variables...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Started Journal Service.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Finished Configure read-only root support.
         Starting Load/Save Random Seed...
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Create Static Device Nodes in /dev.
         Starting Rule-based Manager for Device Events and Files...
[  OK  ] Finished Coldplug All udev Devices.
         Starting Wait for udev To Complete Device Initialization...
[  OK  ] Finished Flush Journal to Persistent Storage.
[  OK  ] Started Rule-based Manager for Device Events and Files.
         Starting Load Kernel Module configfs...
[  OK  ] Finished Load Kernel Module configfs.
         Starting Load Kernel Module fuse...
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Created slice system-systemd\x2dbacklight.slice.
         Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
[  OK  ] Finished Load/Save Screen Backlight Brightness of backlight:acpi_video0.
[  OK  ] Created slice system-lvm2\x2dpvscan.slice.
         Starting LVM event activation on device 8:3...
[  OK  ] Finished LVM event activation on device 8:3.
[  OK  ] Found device /dev/zram0.
         Starting Create swap on /dev/zram0...
[  OK  ] Finished Create swap on /dev/zram0.
         Activating swap Compressed swap on /dev/zram0...
[  OK  ] Activated swap Compressed swap on /dev/zram0.
[  OK  ] Reached target Swap.
         Mounting Temporary Directory (/tmp)...
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Load/Save RF Kill Switch Status.
[  OK  ] Finished Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
[  OK  ] Finished Wait for udev To Complete Device Initialization.
[  OK  ] Reached target Local File Systems (Pre).
         Starting File System Check on /dev/disk/by-uuid/11E9-576B...
         Starting File System Check on /dev/disk/by-uuid/96618861-e388-4bc8-ad09-9512be41aee2...
         Starting File System Check on /dev/disk/by-uuid/e221b68a-fe29-4171-b47e-af5cbc8c9fac...
[  OK  ] Finished File System Check on /dev/disk/by-uuid/11E9-576B.
[  OK  ] Finished File System Check on /dev/disk/by-uuid/96618861-e388-4bc8-ad09-9512be41aee2.
[  OK  ] Finished File System Check on /dev/disk/by-uuid/e221b68a-fe29-4171-b47e-af5cbc8c9fac.
         Mounting /boot...
         Mounting /media/usbdrive...
[  OK  ] Mounted /boot.
         Mounting /boot/efi...
[  OK  ] Mounted /boot/efi.
[  OK  ] Mounted /media/usbdrive.
[  OK  ] Reached target Local File Systems.
         Starting Restore /run/initramfs on shutdown...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Restore /run/initramfs on shutdown.
[  OK  ] Finished Tell Plymouth To Write Out Runtime Data.
[  OK  ] Finished Create Volatile Files and Directories.
         Mounting RPC Pipe File System...
         Starting Security Auditing Service...
         Starting Network Name Resolution...
[  OK  ] Started Security Auditing Service.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Finished Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started dnf makecache --timer.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Daily rotation of log files.
[  OK  ] Started Updates mlocate database every day.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started daily update of the root trust anchor for DNSSEC.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Timers.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
         Starting Cockpit Web Service Socket.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Listening on Open-iSCSI iscsid Socket.
[  OK  ] Listening on Open-iSCSI iscsiuio Socket.
[  OK  ] Listening on PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Listening on SSSD Kerberos Cache Manager responder socket.
[  OK  ] Mounted RPC Pipe File System.
[  OK  ] Reached target rpc_pipefs.target.
[  OK  ] Listening on Cockpit Web Service Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Modem Manager...
         Starting ABRT Automated Bug Reporting Tool...
[  OK  ] Started Manage Sound Card State (restore and store).
[  OK  ] Reached target Sound Card.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Bluetooth service...
         Starting NTP client/server...
         Starting firewalld - dynamic firewall daemon...
[  OK  ] Started irqbalance daemon.
         Starting Hardware Monitoring Sensors...
[  OK  ] Started Machine Check Exception Logging Daemon.
         Starting Generate rndc key for BIND (DNS)...
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
         Starting System Logging Service...
         Starting Self Monitoring and Reporting Technology (SMART) Daemon...
[  OK  ] Reached target sshd-keygen.target.
         Starting System Security Services Daemon...
[  OK  ] Started System Logging Service.
[  OK  ] Started NTP client/server.
[  OK  ] Finished Generate rndc key for BIND (DNS).
         Starting D-Bus System Message Bus...
[  OK  ] Started Network Name Resolution.
[  OK  ] Finished Hardware Monitoring Sensors.
[  OK  ] Started PC/SC Smart Card Daemon.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Bluetooth service.
[  OK  ] Reached target Bluetooth.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started ABRT Automated Bug Reporting Tool.
[  OK  ] Started Creates ABRT problems from coredumpctl messages.
[  OK  ] Started ABRT kernel log watcher.
[  OK  ] Started ABRT Xorg log watcher.
         Starting Authorization Manager...
[  OK  ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
         Starting Hostname Service...
[  OK  ] Started Modem Manager.
[  OK  ] Started Authorization Manager.
[  OK  ] Started Hostname Service.
[  OK  ] Started System Security Services Daemon.
[  OK  ] Reached target User and Group Name Lookups.
         Starting User Login Management...
[  OK  ] Started User Login Management.
[  OK  ] Started firewalld - dynamic firewall daemon.
[  OK  ] Reached target Network (Pre).
         Starting Network Manager...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting Network Manager Wait Online...
         Starting CUPS Scheduler...
         Starting GSSAPI Proxy Daemon...
         Starting Logout off all iSCSI sessions on shutdown...
         Starting Berkeley Internet Name Domain (DNS)...
         Starting OpenSSH server daemon...
         Starting Vsftpd ftp daemon...
[  OK  ] Started GSSAPI Proxy Daemon.
[  OK  ] Finished Logout off all iSCSI sessions on shutdown.
[  OK  ] Reached target NFS client services.
[  OK  ] Started Vsftpd ftp daemon.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Started OpenSSH server daemon.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Berkeley Internet Name Domain (DNS).
[  OK  ] Reached target Host and Network Name Lookups.
         Starting WPA supplicant...
[  OK  ] Started WPA supplicant.
[  OK  ] Created slice system-dbus\x2d:1.8\x2dorg.freedesktop.problems.slice.
[  OK  ] Started dbus-:1.8-org.freedesktop.problems@0.service.
[  OK  ] Finished Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting Cockpit motd updater service...
[  OK  ] Started Node.js HomeKit Server.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting Samba NMB Daemon...
         Starting Notify NFS peers of a restart...
         Starting Permit User Sessions...
[  OK  ] Started Notify NFS peers of a restart.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Deferred execution scheduler.
[  OK  ] Started Command Scheduler.
         Starting Hold until boot process finishes up...
         Starting Terminate Plymouth Boot Screen...
[  OK  ] Finished Cockpit motd updater service.

With that said, I then connected this box to just a vanilla HDMI monitor instead of the HDTV. It booted up just fine all the way to a console login. So, the issue is definitely something related to the display at boot.

That may be related to the resolution required for the HDTV. Using that may require a different GPU to support the higher resolution. Since that is a laptop I am not sure there is any fix other than to use the standard monitor, or possibly set the resolution on the HDTV down to match what the laptop can support.

Although inxi reports it as a laptop, it is a MiniPC that is used as a home server for a variety of purposes. The HDTV is simply for the occasional display (e.g., for upgrades and special-purpose booting), as it is located in the same TV stand as the HDTV. The LG TV was already working just fine in F32 and in editions prior to that, so this to me appears to be regression introduced in F33.

Might be worth filing a bug on that issue. I have never seen a problem with mine but I use nvidia and the nvidia drivers. That looks, as you said, like a regression in either the kernel or the i915 driver.

I wonder if it would be different if you were booting to the graphics? Your inxi output shows that advanced graphics data is unavailable in the console