Fedora logo appears and then the screen goes black with just a blinking _ showing.
And selecting a different kernel /older version from the grub menu does not work either, exactly the same issue
Any suggestions??
Are you using an nvidia gpu with the nvidia drivers?
You may be able to boot by pressing e for edit when the grub menu appears and add the option nomodeset into the line that begins with linux. Continue booting by pressing ctrl-X or F10 and see if it comes up.
If it does then we can take steps to correct the issue.
No nvidia drivers. And adding that entry doesn’t fix the issue, same issue
No nvidia drivers, but do you have an nvidia GPU?
NO nvidia GPU.
Do you have a way to start a terminal session when the system is showing the blinking _? You may be able to get a console with <Ctrl-Alt-FN> (N=3 usually works or me) or (assuming you previously configured ssh access) with ssh from another system. In a terminal you can use journalctl to look for errors.
To get details of the problem, you can press “e” in the GRUB2 menu and edit the command-line to remove “rhgb quiet”, but on a fast system the messages may go by too fast to read.
Did you try booting the “rescue” kernel?
If you can get a terminal, it would be good to post the output from inxi -Fzxx (as text using the </> button).
Please give us your hardware info, Make/Model, PC/Laptop, GPU, Fedora Version ( F38/F39, Workstation, Silverblue, etc )
Custom PC. Amd motherboard with in built graphics, 16gb ddr 2133, 960 gb SSD for running fedora 39, running KDE but not the spin. Used the webinall iso to originally install it.
So AMD Phenom/Athlon APU? or a Motherboard with GPU onboard? Either way, I think the old Legacy AMD driver is in the kernel 
I need to do some digging.
What iso is that? I don’t find any iso for installation with a name similar to what you just stated.
Was that possibly the Network Installer iso also possibly referred to as the everything iso.
When providing information please try to be as exact as you possibly can to remove any ambiguity from the possibility of misunderstanding what is stated.
That said, what you have posted so far seems to indicate that the hardware is pretty standard. However for a complete understanding please add the mobo brand and model as well as the processor brand and model. Amd motherboard with built in graphics is just too generic for us to understand the hardware involved. The processor may be Athlon, Phenom, Ryzen, and there are a lot of motherboards that support amd processors as well as a lot of different versions of those processors supporting on-board graphics. Some mobos have intel or amd chipsets and some processors have/support either intel or amd chipsets.
I think you can see why additional info is necessary
If it is the amd gpu in that combination I think the amdgpu driver is included in fedora and works with 99+% of all amd gpus.
Once we know the exact processor and mobo in use then detailed answers may be possible.
Hey @computersavvy ! , I deduced it’s the Legacy driver because of the Motherboard using a DDR2 memory, so an FM+/FM2 motherboard that’s an APU and I think would use the Legacy AMD driver not the current build since this is not a Add-In card. I think Mesa might cover it here. Older Intel (pre Gen3 and this build would be handled that way since it’s ) around the same time period.
1 Like
Yes, was network installer. Been running on my hardware for over a year without issues until two days ago after doing a sudo dnf - - refresh upgrade.
I believe the motherboard is an FM+ one if I recall. Will boot to windows and check with CPU-Z any other relevant specs later
EDIT: I can reach the command line using ctrl alt f2
Are you running 6.8 kernel? I think there is an AMD bug?!
Are you running 6.8 kernel? I think there is an AMD bug?!
6.6.8
Great. That will allow you to run inxi -Fzxx, which should provide some of the requested hardware details. Another good option (especially for homebrews) is a Linux Hardware Database (LHDB) probe. The site has instructions for running a probe on the command line and uploading results (sensitive details are removed). You then post the ID of your probe here.
You should be able to get error messages from journalctl – the trick is to find search criteria to select the relevant messages from the massive content. For starters:
journalctl -b -p 4– high priority (low numbers) from current bootjournalctl -b -g amdgpujournalctl -b -g firmware
Once you find the right filters you can redirect output to file (screen images often truncate lines, losing important details).
A lot of BTRFS ERRORS, bad tree block start.
Also don’t know how relevant the following is:
1 Like
Ok, how to upload full logs?
Yeah, that’s not good.
A few points:
- That GPU is probably old enough that it uses the old Radeon driver, which is fine, and unlikely to see a whole lot of active development or surprises.
- The fact that it doesn’t work with older kernels also suggests it’s probably not the kernel-specific GPU driver
- The logs here suggest you might have a failing hard-drive
. Back up anything you can that you don’t already have backed up ASAP. It’s possible that it’s a bad/loose cable to the hard-drive, but backup what you can before you try anything else, IMO.
1 Like
sudo btrfs check -b /dev/sdb2
Opening filesystem to check…
Checking filesystem on /dev/sdb2
UUID: aba5ef09-c420-4eaa-8522-e52e1a32e526
[1/7] checking root items
[2/7] checking extents
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
bad tree block 214780477440, bytenr mismatch, want=214780477440, have=0
ERROR: errors found in extent allocation tree or chunk allocation
[3/7] checking free space tree
[4/7] checking fs roots
parent transid verify failed on 214560686080 wanted 691359 found 683341
Ignoring transid failure
ERROR: root [4318 691359] level 0 does not match 2
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214780477440 wanted 0x00000000 found 0xb6bde3e4
bad tree block 214780477440, bytenr mismatch, want=214780477440, have=0
checksum verify failed on 215598366720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215598366720 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215598366720 wanted 0x00000000 found 0xb6bde3e4
bad tree block 215598366720, bytenr mismatch, want=215598366720, have=0
parent transid verify failed on 102013009920 wanted 692036 found 686258
checksum verify failed on 102013009920 wanted 0x00000000 found 0xb6bde3e4
parent transid verify failed on 102013009920 wanted 692036 found 686258
Ignoring transid failure
ERROR: root [4324 692036] level 0 does not match 2
parent transid verify failed on 103515422720 wanted 692149 found 686340
checksum verify failed on 103515422720 wanted 0x00000000 found 0xb6bde3e4
parent transid verify failed on 103515422720 wanted 692149 found 686340
Ignoring transid failure
ERROR: root [4325 692149] level 0 does not match 2
checksum verify failed on 214711926784 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214711926784 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 214711926784 wanted 0x00000000 found 0xb6bde3e4
bad tree block 214711926784, bytenr mismatch, want=214711926784, have=0
checksum verify failed on 215207313408 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215207313408 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215207313408 wanted 0x00000000 found 0xb6bde3e4
bad tree block 215207313408, bytenr mismatch, want=215207313408, have=0
checksum verify failed on 215571431424 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215571431424 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 215571431424 wanted 0x00000000 found 0xb6bde3e4
bad tree block 215571431424, bytenr mismatch, want=215571431424, have=0
parent transid verify failed on 101632442368 wanted 693280 found 682608
checksum verify failed on 101632442368 wanted 0x00000000 found 0xb6bde3e4
parent transid verify failed on 101632442368 wanted 693280 found 682608
Ignoring transid failure
ERROR: root [4335 693280] level 0 does not match 2
ERROR: errors found in fs roots
found 134867267584 bytes used, error(s) found
total csum bytes: 70614376
total tree bytes: 2328281088
total fs tree bytes: 2047590400
total extent tree bytes: 180944896
btree space waste bytes: 519030630
file data blocks allocated: 2080801775616
referenced 162324209664