24.04 LTS and your AMD graphics card

Looking to stay with AMD graphics. What is currently in your computers (desktops) with 16x port. I had nothing but trouble trying to get that last card to work. I want this card to work with both windows and linux 24.04.xx LTS. I will be upgrading from 22.04 LTS when I get a new card. Part that throws everything into wack is 2008 Mac Pro. Currently using 256MB msi radeon 5600xt without any problems what so ever with stock drivers. so!

Simply:

-Dual boot windows and Linux 24.04.xx LTS

-Already in your desktop and working with 24.04.xx LTS

-AMD Card 4-8gb

-Dont give a rats A** if it works with OSX or has the apple boot logo***

-would be nice if you upgraded from 22.04 LTS to 24.04 without any hiccups

2 Likes

How did you get it running in the first place ?

As far as I remember, your processor is missing certain commands that the GPU driver needed.

2 Likes

tkn!!! you found me again! Correction I tried to edit the post it is rv630/2600xt***** sold with the mac. I have always had to use this card as a backup to get to my mac startup logo/UEFI (holding option key) boot screen. It has worked with ubuntu 20.04LTS, 21.04 , and 22.04 LTS always.

I have given up with the rx550 completely with ubuntu mate. I will no longer work with this card, it has become a project i gave up on. Facts are I got it to work, whatever genius i did I will no longer think about. Whatever happened when I went to 22…..deleted my genius to get the drivers to work or somehow overrode something i created. Its gone. Every time i want to get to windows to play my simulation game, i have to get down on the ground and switch graphics cards. No more. We will no longer talk of this devilish card.

I am currently on my laptop for daily use, Pro not near me. I will be moving on. Have you any ideas?

3 Likes

My thinking is that its probably as simple as you just need an older kernel. RX550 support came in with kernel 4.15 and there's probably a good chance the 4.xx kernels would still work on your old Xeon. There's a tiny chance you could modify newer kernels to support your CPU + RX550 combo - but patching and building a kernel is serious work!

Sometimes you just have to forgo the newer packaged kernels to keep old hardware running. Thats what I've been doing on my 14 year old laptop with a GeForce 780M. [EDIT]Correction; 360M[/EDIT].

2 Likes

Here is some info/background about @Pfos86 's hardware:

1 Like

I have forgotten about this!!! :hot_face: I know after this post I had DL the SSE instructions straight from INTEL and I was trying to get the kernel or start the SSE instructions for the processors straight from the boot process but I was not linking them correctly. I was also looking into an emulator. I kept using “legacy” within my last (years) posts. so here we go all over again.

Explanation: because my mind has been all over the place in these last (years) posts!

I started this whole shinanigans on Ubuntu 16 with my Pro 1,1 2x2.66 with 32efi 64cpu ( https://mattgadient.com/) though I ran into EFI mode problems and installed 16 in BIOS MODE I believe with radeon drivers, not the usual drivers Ubuntu was picking. (this is where the word legacy has been mixed in throughout this process). I believe i used old legacy drivers without messing with kernels and drivers from Mesa but I could be wrong. I also had to go in and switch around in between lightdm display manager etc modes, even go in depending and change the grub display size. Keeping my progress I always had to (which i was warned somewhere) to only upgrade “add on top of existing linux” during installation. I went from 16—>18—>20.04LTS—>21.04. 21 stopped support. (After all that i bought a Pro’ 3,1 2x2.8 and just switched guts everything working) I upgraded to the 3,1 bc it was 64efi 64cpu.

I manually upgraded to 22.04LTS and back to the black screen of death. FML. I had the 550 legacy radeon drivers installed/configured/working SOMEHOW ALTHOUGH i had never in all of anything i had done heard of SSE INTEL processor instructions (which tkn caught and has made apparent once again). I never switched kernels either, or “backdated” them ever. I found a loophole or somewhere created something in which I never documented online nor in my findings at my computer table. I was so happy it got working I just went with it.

I will be reading through this all over again, he has caught me and pointing me back to the TA DA/DUH moment I never realized somehow I had got around in the first place. Doing a quick search I believe I installed in BIOS mode bc that directed the driver to find the GPU and it would start up. 22.04 installation would not even open the driver. This of course being in EFI installation where tkn again has pointed me to the problem. The problem is my stubborness that I had it working without all this SSE instruction problems. SO!!……

-I need to re-read about these SSE problems and decide some things…. or just get another computer although there is nothing wrong with the 3,1 just the exact problem I want to avoid which is graphics problems . Nothing else has given me a hard time.

2 Likes

I will re-read through all of this!! I’m sure you saw my post and said….WHY is this guy still fooling with this, did he not read anything I wrote?? Yes i did, and I DL and started fooling with it and was trying to get 22.04 efi to start boot process and use INTEL instructions for the GPU. I was doing something incorrectly and never got there. I believe I left off with just trying to see if the boot was linking even through I was using the 2600xt and it was not…..

There has been a lot going on in my life, and completely forgot about efi and SSE instructions, giving up the 550 will not change my problem just continue my stubbornness. Just getting the 4,1/5,1 Pro’ will get the processors I need. You are probably also wondering why i just dont make a hackintosh or drop the mac board being I dont use mac anyways. Because I work with what I have and this stupidity of this project interests me. I like Tinkering with things, and this will be a satisfying project.

To be brutally honest tkn this also is a hobby that takes up hours of my time instead of drinking, for I am an alcoholic and this is a project. I need a project. This keeps me sober. This is the facts. Please be understanding through the stupidity of this project, for I will find a way. I will.

******************For the time being I will read through everything again*************

2 Likes

Not at all, I was glad I recognized your issue and I hope I was of some help :slight_smile:

1 Like

I wouldnt get too excited about opemu because that project is basically dead. Doesnt work on newer kernels and no one has picked it up for years. The only action on the GitHub is people trying to figure out the license for the code.

Which is funny if you ask me because the code don't work!

2 Likes

Got an AMD Ryzen 7800 and it works great w/3 monitors

2 Likes

correct- i found a post or two but this is exactly my thinking and on one post someone took it a step further yet for reasons i tend not to care for. I just want one that works, not for gaming experience on the linux side. Otherwise the Msi Radeon RX 580 seems to be a top pick as of OOB experience for linux ubuntu for many people. I am not looking to upgrade to any newer type card bc of the SSE 4.2 jumbled brain scramble that seems to get me into. All SSE 4.2 code that i can find are for Mac OS X, though still for UNIX type system it is for OS X drivers and I have found nothing on any person using/testing it for Ubuntu. No code there seems to be tested whatsoever on linux.

Also Intel’s SDE is for testing purposes, some people fooling with it there. More I read, one answer I can get that was hidden in the drawer, I remember that I messed around and changed the GPU’s hardware ID code to get it to work (i think with the radeon driver). I believe that was somewhere near my final solution and the display finally came on. Agian, it was just to get it to work. It was not for any gaming purposes. I tricked the driver. I dont remember which ID i used either. SO!!!

-Top pick RX 580 oc 8gb!!!

I found one here in town for $50 and getting one later today. I will not get to installing and trying this for a month, but I will damn sure update you guys on my progress.

2 Likes

I have a desktop I built in 2013 with dual AMD 4234 CPUs and an HIS Radeon HD 7750 1 GB GDDR5 PCI Express x16 3.0 Graphics card. Works great under both Windows 7 and Ubuntu MATE 24.04 (currently - can’t remember what I started with in 2013). Never had a single problem with Ubuntu. I also have another HP Pavillion 500-314 desktop with AMD A8-7600 with integrated Radeon R7 graphics also running Ubuntu MATE 24.04 without issue. Finally, I have an even older Toshiba laptop with AMD Turion TL-58 with integrated Radeon graphics, also running Ubuntu MATE. (Starting to see a theme here? :slight_smile: )

And yes, I’ve upgraded them all for many years through many versions. All these systems are dual boot with Windows.

4 Likes

Mac Pro 3,1 GIGABYTE RX 550 WORKING AGAIN
I Flashed the card with amdvbflash 4.71 just so I was not going crazy. File 195410.rom

RX 550 GAMING 2G OC REV 1.0= device ID 1002:699f

Under #nano /etc/default/grub is:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" amdgpu.dc=1

Going over Journalctl I noticed “amdgpu 0000:02:00.0: [drm] Cannot find any crtc or sizes”, I let the computer start up without plugging the monitor in and hearing the login chime, plugged in the HDMI cord and VIOLA!!! I tried nomodeset, black screen. amdgpu.dc=0, black screen. (both with monitor plugged in, boot hang) This is amdgpu.dc=1 (monitor not plugged in at startup) Following is what I know is usually asked. Any other commands you want me to try just ask!!

lspci -k | grep -EA3 'VGA|3D|Display'
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)
Subsystem: Gigabyte Technology Co., Ltd Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
Kernel driver in use: amdgpu
Kernel modules: amdgpu

#inxi -G
Graphics:
Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.11 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
resolution: 1600x900~60Hz
API: EGL v: 1.5 drivers: radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa
v: 25.0.7-0ubuntu0.24.04.2 renderer: AMD Radeon RX 550 / 550 Series
(radeonsi polaris12 ACO DRM 3.57 6.8.0-88-generic)
API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib

# glxinfo | grep "direct rendering"
direct rendering: Yes

# journalctl -b | grep -i amdgpu
Dec 21 14:00:44 Pro64 kernel: [drm] amdgpu kernel modesetting enabled.
Dec 21 14:00:44 Pro64 kernel: amdgpu: Virtual CRAT table created for CPU
Dec 21 14:00:44 Pro64 kernel: amdgpu: Topology: Add CPU node
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: enabling device (0006 -> 0007)
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: Fetched VBIOS from VFCT
Dec 21 14:00:44 Pro64 kernel: amdgpu: ATOM BIOS: xxx-xxx-xxx
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: vgaarb: deactivate vga console
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: PCIE atomic ops is not supported
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
Dec 21 14:00:44 Pro64 kernel: [drm] amdgpu: 2048M of VRAM memory ready
Dec 21 14:00:44 Pro64 kernel: [drm] amdgpu: 6985M of GTT memory ready.
Dec 21 14:00:44 Pro64 kernel: amdgpu: hwmgr_sw_init smu backed is polaris10_smu
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4!
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: [drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS with error code 4!
Dec 21 14:00:44 Pro64 kernel: snd_hda_intel 0000:02:00.1: bound 0000:02:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Dec 21 14:00:44 Pro64 kernel: kfd kfd: amdgpu: skipped device 1002:699f, PCI rejects atomics 730<0
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: SE 2, SH per SE 1, CU per SH 5, active_cu_number 8
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: Using BACO for runtime pm
Dec 21 14:00:44 Pro64 kernel: [drm] Initialized amdgpu 3.57.0 20150101 for 0000:02:00.0 on minor 0
Dec 21 14:00:44 Pro64 kernel: amdgpu 0000:02:00.0: [drm] Cannot find any crtc or sizes
Dec 21 14:00:44 Pro64 sensors[1344]: amdgpu-pci-0200
Dec 21 14:00:56 Pro64 kernel: fbcon: amdgpudrmfb (fb0) is primary device
Dec 21 14:00:56 Pro64 kernel: amdgpu 0000:02:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Dec 21 14:01:10 Pro64 snapd-desktop-integration.snapd-desktop-integration[3735]: /usr/share/libdrm/amdgpu.ids: No such file or directory
Dec 21 14:01:10 Pro64 snapd-desktop-integration.snapd-desktop-integration[3735]: /usr/share/libdrm/amdgpu.ids: No such file or directory
Dec 21 14:02:43 Pro64 kernel: amdgpu 0000:02:00.0: amdgpu: Disabling VM faults because of PRT request!


5 Likes

Congratulations!

If you want to know more about debugging the display core (and what amdgpu.dc does) see: Display Core Debug tools — The Linux Kernel documentation

3 Likes