+- Damn Small Linux Forums (https://damnsmalllinux.org/forums)
+-- Forum: Damn Small Linux Forum (https://damnsmalllinux.org/forums/forum-1.html)
+--- Forum: Help Section (https://damnsmalllinux.org/forums/forum-4.html)
+--- Thread: Graphics error after boot menu, boot unsuccessful. (/thread-175.html)
RE: Graphics error after boot menu, boot unsuccessful. - Cactus2580 - 11-16-2024
(11-16-2024, 10:45 AM)grindstone Wrote: Outstanding work. Need a bit to process.
On the off-chance you are around at this minute, what happens if you just append
vga=ask
Do you even get any text at all or does it stay rainbow snow?
Sorry, didn't get to this earlier. If I append VGA=ask it does the same thing as if I use the F7-ask boot flag presented by the bootloader. Green text asking me my resolution. Picking the correct resolution ends in undefined video mode, picking any other resolution ends up with more rainbow but less snow, some of them are just endless scrolling lines. Either way, I've tried every option it gives and no luck so far. Did see a bit on forcing the Radeon driver using kernel commands from a Google search last night, so will try that a bit later and report back.
Thanks again for your help!
RE: Graphics error after boot menu, boot unsuccessful. - grindstone - 11-17-2024
Appreciate the report. Thank you for the patience and for all the work. Was wondering if you tried xorg=radeon on the RC7, too. Got interrupted today as well so gotta hit it another later but more to come.
RE: Graphics error after boot menu, boot unsuccessful. - Cactus2580 - 11-17-2024
(11-17-2024, 12:12 AM)grindstone Wrote: Appreciate the report. Thank you for the patience and for all the work. Was wondering if you tried xorg=radeon on the RC7, too. Got interrupted today as well so gotta hit it another later but more to come.
No worries! As for xorg=Radeon, yes, have tried that to no effect, but that was before moving firmware from AntiX to DSL so I will give it a shot on the reroll as well and see if it is any different.
RE: Graphics error after boot menu, boot unsuccessful. - grindstone - 11-19-2024
Loaded amd graphics fw pkg, made new initrd for stock 5.10.188-antix1-486-smp (~14MB gzipped):
https://drive.proton.me/urls/C5XGJGRMH0#V8UsycwwCqJr
(Still needs the CEDAR and maybe PALM under /usr/lib/firmware/radeon directory I think, but if you threw them all in /radeon it should be fine).
Yes, I know, now that it's done I think to ask if you tried the whole -core /boot directory, but...
Lemme know.
------------
Edit: Staring at Debian kernel patches, it needs the whole /radeon directory.
Code:
Subject: radeon, amdgpu: Firmware is required for DRM and KMS on R600 onward
Date: Tue, 08 Jan 2013 03:25:52 +0000
Bug-Debian: https://bugs.debian.org/607194
Bug-Debian: https://bugs.debian.org/607471
Bug-Debian: https://bugs.debian.org/610851
Bug-Debian: https://bugs.debian.org/627497
Bug-Debian: https://bugs.debian.org/632212
Bug-Debian: https://bugs.debian.org/637943
Bug-Debian: https://bugs.debian.org/649448
Bug-Debian: https://bugs.debian.org/697229
Bug-Debian: https://bugs.debian.org/1053764
Forwarded: no
Last-Update: 2023-11-08
radeon requires firmware/microcode for the GPU in all chips, but for
newer chips (apparently R600 'Evergreen' onward) it also expects
firmware for the memory controller and other sub-blocks.
radeon attempts to gracefully fall back and disable some features if
the firmware is not available, but becomes unstable - the framebuffer
and/or system memory may be corrupted, or the display may stay black.
Therefore, perform a basic check for the existence of
/lib/firmware/radeon when a device is probed, and abort if it
is missing, except for the pre-R600 case.