Help needed, I'm trying to get free of windows and fedora 43 or 42 live won't boot

The failure is in the PCI BUS, sounds like something on the board verses software?

I was just skimming through some of the recent reports on AMD’s issue tracker and I wonder if what you are seeing could be some variant of this bug?:

That is a HP system and the user is reporting a blank screen when using the AMD GPU.

In that case, it looks like they are pointing the finger at a “Microsoft display Mux”. :person_shrugging:

Anyway, if you feel up to it, you might try digging through some of those reports on that issue tracker and see if you can find something recent that is similar to the problem you are seeing.

2 Likes

Thank you. This sounds like a solid lead on the problem, for tonight my brain is getting a bit clouded, tired. I’ll take this back up tomorrow afternoon. Thank you so much for all the help, Greg, Mark, and Steve.

2 Likes

I want to update anyone that was watching this post, but first a sincere thank you to Greg, Mark, Steve, and anyone else that was helping me with this, and the unexpected speed at which I received help from this community.

The computer is solved.

Here is what I did,

I took it in to Best Buy to get my money back or exchange under my warranty and I was referred to their Tech department (Geek Squad). With all the info I had from the exchange on this post and what was found on Linux-Hardware.org specific to my computer (the problem report on the GPU-PCI-BUS that failed) and I had an instant change in tone from the Tech’s working their and the supervisor in the back even came out. There was a surprising amount of excitement for my problem (not a windows problem). We went through the process of booting up at the counter and all the “things” discussed here and they were perplexed. Then the supervisor, and what I would later learn is a young family man that has been free from Windows in his house now for a year and Fedora “Plasma” was his favorite and his personal OS, has been learning to customize it on a code level? I gave him a print out of the problem from Linux-Hardware.org and he looked it over carefully for a few minutes and then went in to the back to study it, this all took about 30 minutes at the counter. My computer was taken in to test and determine, and two days later I got a call from the supervisor and he said he fixed the problem and wanted to talk to me in person when I came to pick up the computer.

When I picked up my computer the supervisor had it hooked up at the counter and I reasoned with him that if I can’t load Fedora myself then it’s not fixed (after thanking him of course for all the work that was done already) and he agreed and was professional and patient though he was excited to work on something he is personally interested in. We went through his notes and here is what was needed to load Fedora 43 Workstation on a brand new computer (manufacture date is Nov, 2025, Ryzen 5, HP Omni-desk, with just the integrated graphics),

On the selection in grub to choose between “trying Fedora Live” on the 1st line, “testing then trying Fedora Live” 2nd line, or “Troubleshooting” 3rd line, press “e” for edit on the first line “try Fedora Live” (the troubleshooting line would not work with the edits only edits on the 1st line).
Then once your in the “edit” for the “try Fedora Live” (I know this community has all the proper ways of saying what I can only say in lay terms so please feel free to educate) go to the 2nd line and at the end of the 2nd line after rhgb, and type “nomodeset” then a space and acpi=off, then it will boot third party software, and that’s fixed for me, because I was able to replicate the process twice at the counter and it all worked.

I am now officially free of Windows and am trying to help my adult children to be free of Windows also. I am thrilled to own my computer and software, I wish I knew the freedom in this when I was younger, but I’m here now.

The special note on this,

I was told by the supervisor it was his opinion that there was some possible collaboration between the manufacturers to block us from potentially booting third party software in a quiet way, and that he now expects to see more of this on the “new” systems being sold. This was his personal opinion and in his professional opinion he pointed out how the BIOS doesn’t have “Fast-boot” as an option and some other things that I’m sorry, but I can’t remember and didn’t think to write it down at the time, but it seems this acpi=off may be a new work around in the future as people buy new machines and have this problem with booting third party software.

To be clear to anyone reading this new, I’m not experienced with this, I’m learning, I just tried to write about the interaction as best I could for others to benefit and maybe the experts that work on this software, though they are probably already aware if there is a there, there, but who knows, just in case.

I love my new system and so does my Wife, so thank you. :slightly_smiling_face:

3 Likes

I am glad to see that you found a fix, and that you shared the solution with the members here.
Host: Hewlett-Packard 8D32 SMVB 2025 - desktop with Fedora 43
HP Omnidesk Desktop PC (M02-0224)

Please mark your post with the solution so others know the solution was found and what it was.

It is interesting that adding acpi=off is enough to make your graphics work, but do be aware that that setting turns of all power management. That might not be a big problem for your use case, but if you notice odd things about the power management (e.g. the system won’t power off after you press the shutdown button), that acpi=off setting is the reason why. What you’ve been provided should be considered a temporary workaround. It’s great that you found a way to make your system “work”, but without the “Advanced Configuration and Power Interface”, I wouldn’t consider the system to be 100% Linux compatible (at least not yet).


Also, this was mentioned earlier, but nomodeset will lock your graphics at a lower resolution, color depth, and refresh rate than what your video card is capable of when the full video driver is loaded.

2 Likes

Greg this is concerning. I have not noticed problems yet with my graphics but I haven’t played any HD videos. I’ve loaded multiple windows with tabs and the system seems to be functional. I am concerned I’m in a grey area with warranty? Also if I install some dedicated graphics might that solve the issue? I don’t want to throw money at a machine that is never going to be right.

When turning off the acpi will that also carry over to the new system or does it just affect the live OS operation?

If there is verbiage in the warranty about what software/os you run on the hardware, that is news to me. I don’t think it should be a problem.

IIRC, options applied to boot the Live image were copied to the final installation after you run Anaconda (the Fedora Linux installer). However, Anaconda has undergone significant revisions since I last looked at it. That might not be the case anymore. You can add or remove kernel parameters after you install the OS, so it doesn’t really matter.

Yes, it seems likely that you could solve this problem that way. Of course, it depends on whether the added video card is compatible. Maybe you could ask Geek Squad to demonstrate that the new video card works with Fedora Linux in your PC before you purchase it?


Another option might be to just make do with the workaround you’ve found for now and hope that a future upgrade will fix the problem. I think that bug report I linked earlier is probably related to the problem you are seeing. I have no idea how long it might take for the patch to be developed. It could be a few months (likely) or it might take a year or (unlikely) even more.

You can often see if your system works with linux using https://linux-hardware.org/?computer=c121046b8442. There is just one probe and it indicates a graphics issue with Fedora 43. Makes me wonder if HP only sold one!