Fedora 36 will never reboot! Can only use "1 time after initial" install

Hello all,

I just installed Fedora 36.
The installation went well. I did a complete disk install.
Immediately after the install I clicked around on the desktop and everything seemed to be working fine.
But after trying to restart my laptop I cannot get anything to display.
I get a dark grey screen.
The only way to see anything is to reinstall Fedora again, and use it the first time the same way as I did in the beginning.
Then after reboot the same problem happens again.
Cannot see anything.
The only way to get to my bios boot menu is to click SHIFT + Power button. That will at least let me access the bios menu so I can see my boot order.
Everything appears to be fine in the order with FEDORA at the top.
Nothing works for me however.
Is there an advanced setting in the Bios menu that I am missing?
Anyone have this issue or anyone know of a fix?

  • I reinstalled again from bootable USB and exact thing was duplicated.
    What next?
    Thanks!
    Pizzaman

Welcome to ask.:fedora:edora @pizzaman

Could you please give us more info’s as :

inxi -Fzx in terminal and post the output as </> Preformatted text here.

Have you tried to fully update before rebooting?

Thanks for the speedy reply.
I have not done anything in terminal yet, as I should have tried to do a updates/upgrades first.
So I will have to reinstall Fedora 36 again from USB and use terminal.
By the way, I am new to Linux. Almost 2 years old, so I’m a toddler.
I will try that command that you mentioned and try to copy and paste the results.
Although I know nothing about it, hopefully I will copy the complete result as you asked for.
Thanks, See you soon.

Hi all :wave:

@pizzaman If you’re not even able to boot into the system (not even a recovery shell), it may also help to check GRUB’s boot instructions

Here are the results ------ >>>
But please know that I just did all updates and upgrades about 775 of them.
Hopefully everything will work now.
But I did NOT try to reboot yet.
Maybe I wait a few more minutes to see if you reply first before restart.
Thanks

System:
  Kernel: 5.17.5-300.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-24.fc36 Desktop: GNOME v: 42.0
    Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: SAMSUNG product: QX311/QX411/QX412/QX511 v: 0.1
    serial: <superuser required>
  Mobo: SAMSUNG model: QX311/QX411/QX412/QX511 v: FAB1
    serial: <superuser required> UEFI: Phoenix v: 10HS date: 11/27/2012
Battery:
  ID-1: BAT1 charge: 24.5 Wh (65.0%) condition: 37.7/61.0 Wh (61.8%)
    volts: 11.4 min: 11.1 model: SAMSUNG Electronics status: discharging
CPU:
  Info: dual core model: Intel Core i5-2430M bits: 64 type: MT MCP
    arch: Sandy Bridge rev: 7 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 798 min/max: 800/3000 cores: 1: 798 2: 798 3: 798
    4: 798 bogomips: 19156
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    vendor: Samsung Co driver: i915 v: kernel arch: Gen6 bus-ID: 00:02.0
  Device-2: DigiTech WebCam SCB-0380M type: USB driver: uvcvideo
    bus-ID: 1-1.4:3
  Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: gpu: i915 resolution: 1360x768~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 3000 (SNB GT2)
    v: 3.3 Mesa 22.0.1 direct render: Yes
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
    vendor: Samsung Co driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.17.5-300.fc36.x86_64 running: yes
  Sound Server-2: PipeWire v: 0.3.49 running: yes
Network:
  Device-1: Intel Centrino Wireless-N + WiMAX 6150 driver: iwlwifi v: kernel
    bus-ID: 01:00.0
  IF: wlp1s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Samsung Co driver: r8169 v: kernel port: 2000 bus-ID: 02:00.0
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-3: Intel Intel Centrino Wireless-N + WiMAX 6150 type: USB
    driver: N/A bus-ID: 2-1.3:3
Drives:
  Local Storage: total: 625.99 GiB used: 5.61 GiB (0.9%)
  ID-1: /dev/sda vendor: Samsung model: HM641JI size: 596.17 GiB temp: 35 C
  ID-2: /dev/sdb type: USB vendor: SanDisk model: Cruzer Glide
    size: 29.82 GiB
Partition:
  ID-1: / size: 7.36 GiB used: 5.61 GiB (76.3%) fs: ext4 dev: /dev/dm-0
    mapped: live-rw
Swap:
  ID-1: swap-1 type: zram size: 5.7 GiB used: 490.5 MiB (8.4%)
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 56.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 254 Uptime: 56m Memory: 5.7 GiB used: 3.46 GiB (60.6%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.0.1 Packages: N/A
  note: see --pkg Shell: Bash v: 5.1.16 inxi: 3.3.19

I can’t see anything wrong there…

What about the GRUB menu? I’d like to take a look to see the kernel parameters your system is booting with:

Ref: Working with the GRUB 2 Boot Loader :: Fedora Docs

TL;DR: open a terminal, sudo cat /boot/grub2/grub.cfg and paste back here the menuentry section. In my case it looks like this (I’m running Silverblue here but your output should be quite similar):

...
### BEGIN /etc/grub.d/15_ostree ###
menuentry 'Fedora Linux 36.20220908.0 (Kinoite) (ostree:0)' --class gnu-linux --class gnu --class os --unrestricted 'ostree-0-111c1a63-80f4-4f74-854f-05b85b8b9b5d' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
search --no-floppy --fs-uuid --set=root 111c1a63-80f4-4f74-854f-05b85b8b9b5d
linux16 /ostree/fedora-15dd779a74a2477a2b5b7367eef5e4da6db44e18cf5bf33408e8fd84ecb5f216/vmlinuz-5.19.7-200.fc36.x86_64 rd.luks.uuid=luks-950e329d-e6b6-455b-82ae-8ab5ca02eaba rhgb quiet root=UUID=6dff0f68-ffc9-44a3-b58d-c6cd354039b5 rootflags=subvol=root ostree=/ostree/boot.0/fedora/15dd779a74a2477a2b5b7367eef5e4da6db44e18cf5bf33408e8fd84ecb5f216/0 i915.enable_psr=0 mem_sleep_default=deep
initrd16 /ostree/fedora-15dd779a74a2477a2b5b7367eef5e4da6db44e18cf5bf33408e8fd84ecb5f216/initramfs-5.19.7-200.fc36.x86_64.img
}
### END /etc/grub.d/15_ostree ###
...

Martin - thanks for helping also.
Here is the result:
[liveuser@localhost-live ~]$ sudo cat /boot/grub2/grub.cfg
cat: /boot/grub2/grub.cfg: No such file or directory

Wow, that’s interesting, to say the least :sweat_smile:

Does this command show anything? sudo grubby --info=ALL (Ref: Working with the GRUB 2 Boot Loader :: Fedora Docs)

RESULTS:
[liveuser@localhost-live ~]$ sudo grubby --info=ALL
index=0
kernel=“/boot/vmlinuz-5.17.5-300.fc36.x86_64”
args=“ro net.ifnames=0 biosdevname=1 rd.auto=1 crashkernel=auto resume=/dev/mapper/vg_guests-LogVol01 rd.md.uuid=dbfe3984:bb1db3de:ab54a834:1dd02182 rd.luks.uuid=luks-6ff0f4ac-2d3b-4e05-9fe3-5da088bc966c rd.lvm.lv=vg_guests/LogVol00 rd.md.uuid=224bbce7:99bf5039:469e4629:6ddaecf8 rd.lvm.lv=vg_guests/LogVol01 rhgb quiet”
root=“/dev/mapper/vg_guests-LogVol00”
initrd=“/boot/initramfs-5.17.5-300.fc36.x86_64.img”
title=“Fedora Linux (5.17.5-300.fc36.x86_64) 36 (Workstation Edition)”
id=“c15b9e76eb834872a0b539bc0a429e08-5.17.5-300.fc36.x86_64”
index=1
kernel=“/boot/vmlinuz-0-rescue-c15b9e76eb834872a0b539bc0a429e08”
args=“ro net.ifnames=0 biosdevname=1 rd.auto=1 crashkernel=auto resume=/dev/mapper/vg_guests-LogVol01 rd.md.uuid=dbfe3984:bb1db3de:ab54a834:1dd02182 rd.luks.uuid=luks-6ff0f4ac-2d3b-4e05-9fe3-5da088bc966c rd.lvm.lv=vg_guests/LogVol00 rd.md.uuid=224bbce7:99bf5039:469e4629:6ddaecf8 rd.lvm.lv=vg_guests/LogVol01 rhgb quiet”
root=“/dev/mapper/vg_guests-LogVol00”
initrd=“/boot/initramfs-0-rescue-c15b9e76eb834872a0b539bc0a429e08.img”
title=“Fedora Linux (0-rescue-c15b9e76eb834872a0b539bc0a429e08) 36 (Workstation Edition)”
id=“c15b9e76eb834872a0b539bc0a429e08-0-rescue”

Please

While edit them, you can mark the output and click on the </> symbol in the edit window (see top-bar).

? huh ??

Is this before or after the initial boot following the install?

You do not say
If before you are still running in the live media.
If after it should come up and ask for some initial config info then come to the desktop.

There is a distinct difference in what needs done in each situation.

Hi Jeff,
To clarify a bit more.

  1. Booted by USB
  2. Installed Fedora
  3. At end of install it tells me install is complete.
  4. I launched it, and clicked around.
  5. Everything looked good, so I did a reboot and got stuck on Blank Screen!
    So I guess this was before my first real boot into Fedora (not counting the USB install boot).
    I’m thinking that this is an installation issue if Fedora cannot boot into itself since I made it “first” at the top of boot order.
    This never happened with Mint, PopOS, or any other OS system I installed.
    Any idea what may be causing this?
    Is it because Fedora never created a proper boot in partition even though I chose automatic install?
    I thought it created boot partitions when installing on complete disk?
    Oh, well.
    I have done 775 updates and upgrades, maybe this will fix whatever the problem is.
    I will try to boot again to see if the updates fixed things in a couple hours when I get some more time.
    Thanks

UPDATE:
I no longer need help but thanks to all of you that tried to help me.
I’ve installed a different OS very easily on the first shot.
The good news is that I’m using Linux!
Cheers!

1 Like

I believe @ilikelinux was pointing out that it would be nicer if you post the output as preformatted text. There are several ways to do so, for instance, you can select the text to be formatted and then click on that button on the top-bar:

Example of formatted text:

I believe @ilikelinux was pointing out that it would be nicer if you post the output as preformatted 
text. There are several ways to do so, for instance, you can select the text to be formatted and 
then click on that button on the top-bar:

This way it is usually easier to read debug info, logs, code, and so forth.

HTH

1 Like