Fedora Project: RPM, Memory Testing and DXVK
-
Using source-git to maintain packages in Fedora
Some time ago, we initiated a discussion on the devel list if dist-git is a good place to work. This thread received a great amount of wonderful feedback from you and we are so grateful for every message—it demonstrates the passion of the Fedora community.
If you are not familiar with how packages are being maintained in Fedora or what dist-git is, let me give you a quick summary. Every Fedora package has a dedicated git repository—a dist-git repository. It contains files needed to compile the sources and produce a binary RPM package which you can install on your Fedora Linux system. As an example, you can look at firefox dist-git repository.
-
Fedora Developers Brainstorming Options For Better Memory Testing
In looking beyond the massive Fedora 33 release in development, Fedora developers have begun discussing options for allowing better memory testing on their distribution for evaluating possible faulty RAM issues that otherwise often get mixed in with other software bugs and other sporadic behavior.
Currently Fedora does ship memtest86+ on all installations, but that only works on legacy/BIOS setups and not modern UEFI-enabled systems. It's only the proprietary memtest86 that has UEFI support right now and not the open-source memtest86+. Thus memtest86+ is inaccessible to those on modern platform booting from UEFI, but even if/when memtest86+ offers UEFI support there are other potential obstacles around Secure Boot and similar potential blocks. Additionally, while memtest86(+) is great at rooting out faulty memory scenarios, it can often take some time to spot any issues as another obstacle for end-users.
-
Fedora Looks To Make DXVK Their Default Back-End For Direct3D 9/10/11 On Wine
Fedora like most distributions ship their Wine packages as-is at the defaults, but for Fedora 33 we could see DXVK used by default on Wine in place of the conventional WineD3D back-end for Direct3D 9/10/11 usage.
While upstream Wine is working to ultimately support Vulkan with their WineD3D back-end, for now at least DXVK generally offers a far better and more performant experience for gamers by translating D3D9/D3D10/D3D11 calls to Vulkan rather than WineD3D that currently relies upon translating to OpenGL. Steam Play and Proton have shown the success and tremendous capabilities of DXVK while now Fedora is looking at possibly using DXVK by default with their Wine package.
- Login or register to post comments
- Printer-friendly version
- 3604 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
Linux distro Fedora 33 may get DXVK as the default for Wine
Linux distro Fedora 33 may get DXVK as the default for Wine