Fedora 43 black screen. (Workarounds do not work for me)

Ask Fedora
, ,
1

Hi, I installed fedora 43 on a laptop with a i7-9750h CPU and a gtx 1660ti mobile GPU, but I got a black sreen when booting.

  1. No external monitor connected.
  2. Edit the boot parameter and remove rhgb does not work.

Initially, the boot process is fine, systemd showing some messages.
Then some error popped up:

nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
usci_ccg 8-0008: i2c_transfer failed -110
usci_ccg 8-0008: usci_ccg_init failed -110
usci_ccg 8-0008: probe with driverucsi_ccg failed with error -110

And the boot process continues, but boots to a black screen after some seconds (screen is on, but no picture)
Several last lines from systemd:

[ OK ] Started atd.service - Deferred execution scheduler.
[ OK ] Stared crmod.service - Command scheduler.
       Starting initial-setup.service - Initial setup configuration program...
       Starting plymouth-quit.service - Terminate Plymouth Boot Screen...

I tried re-downloading and re-installing fedora several times, but no luck. Need some help, thanks!

Edit: also, unable to switch to other ttys.
Edit 2: forgot to say, it’s KDE version.

1 Like
2

When you were going through the install from live boot, did you enable 3rd-party drivers?

4

There are no options to enable third party driver during the installation process, I believe.

5

There is it’s enabling third party packages I believe it is on the 3rd page of the install

6

I only have the following pages:

  1. Welcome
  2. Date and time
  3. Installation method
  4. Storage configuration
  5. Create account
  6. Review and install
7

It’s in the welcome center sorry I forget it is not in the actual installer but the welcome center.

8

IMG_5646.jpg2868Ă—1320 317 KB

9

Oh, I didn’t notice there was such an option. I just tried reinstalling with it enabled, but unfortunately nothing seems to have changed. Same error, same behavior.
But thank you!

10

Have you checked if secureboot is enabled? can you get to a TTY? or have you seen the grub menu?

11

Secure boot was disabled, but turning it on doesn’t fix it.
No, I am unable to go to ttys.
Yes, I can see the grub menu, but both fedora and fedora(rescue) does not boot.

Actually I just found that it’s not entirely black screen, there’s a small _ at the top left corner when it stuck.

12

Yes, ok, so it’s for sure a graphic issue/kde plasma I had this yesterday due to my own stupidity, and it took me like 8 hours to fix just by wiping my system.

So were you ever able to boot into the system after installing from the live boot session?

Remove the rhgb quiet like you did at the grub and replace with systemd.unit=multi-user.target and Ctl x it should allow you to boot to a TTY. Then you should have the CLI login, and i would look and see if lspci -k | grep -A 3 -i vga shows nouveau or nvidia

13

Sorry. I don’t understand what do you mean by “boot into the system after installing from the live boot session”

14

sorry after installing your system were you able to login using the graphical interface?

15

No, I can’t see the login screen (SDDM I believe)

16

ok so i would do this

Remove the rhgb quiet like you did at the grub and replace with systemd.unit=multi-user.target and Ctl x it should allow you to boot to a TTY. Then you should have the CLI login, and i would look and see if lspci -k | grep -A 3 -i vga shows nouveau or nvidia.
i would then make sure to

dnf upgrade --refresh
dnf install mesa-dri-drivers mesa-vulkan-drivers vulkan-loader
17

Somehow it’s still running into Starting plymouth-quit.service (then stuck) even I removed rhgb and quiet, adding systemd.unit=multi-user.target
Did I doing anything wrong?

18

No try doing systemd.unit=emergency.target instead of multi-user.target

19

It says cannot open access to console, the root account is locked. After pressing enter it continues to boot, and, stuck.

20

see if pressing enter gets you to # if it does your in as root. i think it might be a false flag but i could be wrong

21

No, it does not let my type any commands, only a _ at top left corner.
But this time the last systemd message is not Plymouth related, the final one is wifi related.
I am sure the wifi should be fine, though.