![]() The assembly went pretty well (and took a bit more than an hour-not bad for the first time building a PC from scratch in 23 years, while live streaming it!). To round out the build, I bought a B550 motherboard so I could use PCIe Gen 4.0, some Corsair RAM (RGB since my kids would enjoy seeing it), and I used a case and 144 Hz gaming monitor repurposed from my Raspberry Pi Gaming PC build. Since I also wanted a faster Linux kernel build platform than my M1 Mac mini, I stretched my budget a little and bought an AMD Ryzen 5 5600x. It will be part a massive upgrade from my current HP desktop PC with integrated graphics. Though my initial effort was fruitless, I've since hacked the driver to work through at least a few 'rings' of AMD's doorbell init process.Īnyways, because I had that graphics card laying around, I decided to put it to use while it's not being tested on the Pi. My initial goal was to see if I could get the card working on a Raspberry Pi. We already have a universal interface thanks to the display servers, it's just waiting for someone to wrap it up in a bow and make it nice and pretty.Last year, due to some extreme luck and help from a viewer, I picked up an AMD RX 6700 XT for MSRP (around $500). We wouldn't need to depend on proprietary control panel software anymore. If someone wrote an open source package that wrapped all the xrandr/"whatever the Wayland equivalent to that is" commands needed to do all the things that Catalyst/Nvidia control panel into a simple, and easy to use driver agnostic GUI, that would make life so much easier. My point was just that AMDs proprietary driver package is the only one that ships with the Catalyst software for configuration. That's usually how it works nowadays as it's more efficient than running a driver in userland, and also allow interfacing directly with the card through the driver if needed. As far as I know both drivers are running as kernel mode modules that simple receive commands from the display sever, be it X or Wayland. I believe the x11 driver are just the drivers that are packaged for Xorg instead. If they're using the default GNOME desktop it likely had the Wayland drivers installed by default. Whatever distro you use, you get the best AMD driver it has by default.Īs noted, however, what you don't get is anything to configure/tweak the card. Ditto, the 590, Vega 56, Vega 64, etc.) because it releases its driver code for all those cards as open source and it's incorporated in the kernel. If memory serves, the "xorg-X11-drv-amdgpu" package in the repos moves things back to the X server.ĪMD has no reason to release Fedora drivers for its Pro line of cards (which, again, the 580 isn't. I.e., "moves this process from the X server's DDX drivers to the kernel". I'm a little fuzzy on this, but Fedora deals with current AMD cards via kernel modesetting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |