I finally switched from Win10. I booted it from a live USB, and everything was golden. Then, I decided to dual-boot it first in case anything goes wrong. After that, I rebooted, removed the USB, and launched Fedora on GRUB.

This is where weird things happen. It showed the launch screen first. Then… nothing. No key combination worked on that screen; only the power button works. When shutting down, it also shows the launch screen and shuts down.

Now here is my system: I’m using a Lenovo Ideapad 3 Gaming laptop with NVIDIA GTX 1650 Ti and AMD Ryzen 7 4800H with Radeon graphics. I’m definitely sure it’s caused by NVIDIA, but I couldn’t find a proper solution for me.

  • pinball_wizard@lemmy.zip
    link
    fedilink
    arrow-up
    2
    ·
    23 hours ago

    If your monitor is currently connected via HDMI, and supports any other type of cable, I would try any other type of cable.

    I have had similar issues when the Digital Rights Management (DRM) layer of HDMI was having timing issues, causing a blank screen.

    In my case, it would sometimes work, if the power up / wake up / boot up cycles of the monitor and CPU happened to align, but on certain of my PC builds the timing tended to not match up during most boots, and I usually got a blank screen.

    Edit: Oh, and classic advice for the ages - when I have the monitor hooked up to a graphics card, I switch it over for one boot and see if that fixes things long enough to pull some log files and get more info.

  • mag37@lemmy.ml
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 day ago

    Can you edit the kernel parameters in Grub (by pressing E on the Fedora alternative) and try adding nomodeset or nvidia_drm.modeset=0 at the end of the line starting with linux /boot/vmlinuz or similar. Then CTRL+X to start with the new (temporary) parameters.

    If that boots (and if you’ve installed the Nvidia drivers etc) - try forcing a rebuild of kmods and wait 5-10 minutes before restarting.
    sudo akmods --force --rebuild
    You can see if it’s don’t by running sudo journalctl -f -u akmods

    Maybe you have to remove the kmod prior, can’t recall:
    dnf remove kmod-nvidia-$(uname -r)