I’m trying to run this on an old PC. I’m using the latest release of KDE plasma.
As the computer starts, I select the USB for startup.
The PC successfully tests the USB, and proceeds to start.
I get the “Fedora” logo on the bottom of the screen.
Then the little circle rotates for about 5-10 sec…
Then the screen looses connection.
and I have to power off to get out of it.
Probably not losing connection. It takes some time for older systems to load the desktop.
Depending upon the age of the system and what hardware is installed it might be better to select a less demanding installation.
Both gnome (Workstation) and KDE are graphics intensive desktops and there are several spins of fedora that are much lighter to run on less powerful systems.
Thanks for the feedback.
Where can I look up the minimum requirements?
For reference, the PC is currently running WIN10 without issues. It’s not capable of the WIN 11 upgrade.
When I say looses connection, I don’t mean a blank screen. The screen itself says there is no connection to it. as if there is nothing plugged into it.
I was wondering if there was a compatability issue with the graphics card? I know that Fedora has a problem with NVIDEA graphics. but its not NVIDEA.
I can’t look it up exactly right now… not at that computer now.
The Processor is AMD A10-RADEON R7, 10 compute cores 4C+6G
Curious what happens if you hit esc while the little circle is spinning…
Feel free to snap a picture on your phone of whatever messages or errors you happen to see when you hit escape (as @coonmanx suggests) as the spinner is doing its thing - it’ll be the easiest way to show us what’s actually happening on this machine as it boots up.
Given that the monitor loses signal, I suspect it’ll be graphics card/driver related, but there are enough eyeballs here to help you through getting the thing up and running without giving you an aneurysm 
1 Like
Hi Guys, Thank you for taking a look at this for me.
I followed your suggestion of pressing the ESC during the Fedora logo, and found a bunch of read errors. I took the precaution of unplugging an external USB connected backup Hard Disk.
Those errors went away.
On the next try, this wo line message comes up before the Fedora Logo.
Then, after the logo comes up, I press esc and get the other longer list of messages.
After this, I let the system sit for about 5 min before I rebooted it again.
That last picture looks OK - the sp5100-tco message is just a watchdog timer which is not enabled on your machine - shouldn’t impact the boot process.
Replicate this situation and when you would normally let the system sit, press Ctrl-Alt-F3 (or F4 or F5 - doesn’t matter - it should open up a virtual terminal). Hopefully, you get a black screen with a login prompt. If so, enter your username and password.
Assuming you log in OK, issue journalctl -b -p warning | grep -Ei 'drm|gpu|fb|kms'. This will show us a hopefully small list of errors from the boot process. Take a picture, as I doubt this machine will have internet connectivity operational to enable you to upload the output.
If this doesn’t show us anything obvious, we’ll have to broaden the scope (and thus the amount of output it could produce).
Thank you, What user name/password would apply? this is the downloaded live stick.
The username and password you set up when you installed Fedora. To be clear, you should not be booting from the a USB stick - you should be booting up from the system you installed and is failing to give you a standard greeter screen, where you would enter that same userid and password to begin a graphical session.
All we’re doing here is using a text session without a desktop to see what’s causing the desktop to fail to appear.
1 Like
Hi Steve,
What I am using is the Fedora 43 LIVE USB . The purpose of this is to test Fedora and my hardware for compatibility before potentially damaging my existing WIN install. I intend to set this up as dual boot. If successful, you can install to the HD from the USB. I have previously used this USB to install a laptop, but it’s not dual boot.
I tried your suggestion of Ctrl-Alt-F3, and got a flashing cursor for a few seconds, then lost the monitor. it seems to be running in the background, but has an issue with the monitor connection. I do not have a dedicated video board, but the monitor is connected with HDMI.
Additional Update:
This time through exploring the menus, I found “troubleshoot” and “start with basic graphics”
It started properly, and it looks good.
However, It does not recognise any audio devices, which should be the monitor. This is likely due to the “basic garphics” mode? it’s not seeing the monitor speakers.
Also, although I can play youtube video, it’s not a ssmooth as I would like. Other video sites, such as the weather network, will not play at all.
I opened a terminal window to check the log as you suggested and got this in the top of the log. the rest of the log is pretty much all the same message continued.
liveuser@localhost-live:~$ journalctl -b -p warning | grep -Ei ‘drm|gpu|fb|kms’ | head
Dec 29 11:06:52 fedora kernel: amdgpu 0000:00:01.0: probe with driver amdgpu failed with error -22
Dec 29 16:08:48 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Could not find edid for connector DrmConn
ector(id=37, gpu=“/dev/dri/card0”, name=“Unknown-1”, connection=“Connected”, countMode=1)
Dec 29 16:08:48 localhost-live kwin_wayland[2217]: kwin_core: Failed to open drm node: “”
Dec 29 16:08:48 localhost-live kwin_wayland[2217]: kwin_scene_opengl: couldn’t find dev node for drm device
Dec 29 16:08:50 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Dec 29 16:09:07 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Dec 29 16:09:07 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Dec 29 16:09:25 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Dec 29 16:09:25 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Dec 29 16:09:25 localhost-live kwin_wayland[2217]: kwin_wayland_drm: Failed to create framebuffer: Invalid arg
ument
Hope this helps you help me…
Thanks
Good evening, I have a similar problem while I am trying to install Fedora 43 from a live ISO. My platform is a MacBook Pro M1 (arm64) with Parallels as hypervisor. It worked fine with Fedora 40 some time ago. Now it stucks immediately at the first boot at the steps shown in the screenshot. After around 2 or 3 minutes, the emergency mode appears.
I don’t know so much about Linux, so I’m asking here if someone can help me.
fedora kernel: amdgpu 0000:00:01.0: probe with driver amdgpu failed with error -22
There is your issue. The boot process is not able to load the amdgpu drivers for your graphics adapter.
I suggest you either try
- Boot Fedora in safe graphics mode (its been a while, I don’t remember if Fedora Live has this option in boot menu) when booting from the USB stick
- Try a different distro like Ubuntu or Mint and see if they are able to boot with your CPU/GPU
1 Like
Thanks for your answer! GRUB only gives me the option for ‘Basic Graphics Mode’, this doesn’t work.
To narrow down the problem:
- My Ubuntu VM (Ubuntu 22.04 LTSC) works fine.
- I tried to boot an old Fedora 36 Image, this works fine aswell.
- Fedora 42 (just downloaded) somehow doesn’t.
1 Like
The VM does not use the same driver.
Maybe there is some updated amdgpu driver in F42 ISO that does not work with your hardware. I’d suggest F41 or F43 ISO for testing. For technical help I am not knowing enough about amdgpu.
1 Like
Hi Everyone, thanks for your input. In the end, I dugup and old HDD and did the install from the safe graphics mode. I removed my good windows disk and plugged this one in.
The good news is the graphics seems to be resolved. the system bootted correctly. Therefore I’ll close this thread, and open a new one for my other issue ( no sound, not web video playing ). I’m concidering buying a video card to resolve that issue since im currently using the onboard virtual card. Thanks again, when I get this working, I’ll setup my primary disk as dual boot.