I wonder if its possible to make public exactly which hardware platforms various OMLx releases are tested on before release?
Knowing this would allow OMLx users who are shopping for a new(ish) computer, or adding a GPU or printer or whatever to know what is definitely gonna work, and so on, and may fractionally reduce the level of support requests.
I can provide detail on some of the hardware I have running:
ROME Machine:
AMD Zen4 Ryzen 9 7900X
Sapphire AMD 9070XT Pulse GPU
ASUS ProArt X670E-CREATOR WIFI
Kingston 64GB (2x32GB) DDR5 6000Mhz CL30
A mix of Samsung NVME + SATA SSD's
10Gb Aquantia AQtion AQC113CS NIC (onboard mobo)
Intel I225-V (onboard mobo)
Mediatek MT7922 802.11ax WIFI +Bluetooth (onboard mobo)
Mellanox Connect-X3 MT27500 10Gb SFP+ PCIE NIC
Cooker Machine:
AMD Zen 2 Ryzen 9 3900X
Sapphire AMD 6750XT Nitro+ GPU
ASUS PRIME X570-PRO motherboard
Corsair 64GB (4x16GB) DDR4 3200Mhz
A mix of Samsung NVME + SATA SSD's
Intel I211-AT 1Gb NIC (onboard)
10Gb Aquantia NIC (AIC)
Mellanox Connect-X3 MT27500 10Gb SFP+ PCIE NIC
I have numerous peripheral devices plugged into each of those machines, too many to list individually, but here is a rough outline:
Keyboards, Mice, Monitors, Hardware KVM, Trackballs, Bluetooth devices, Speakers & Soundbars (analog and digital/optical), Serial Port devices, various USB Powered Hubs, USB Serial Devices/Debuggers (STLINK-V3MINI etc), USB cameras, USB/UVC HDMI capture devices, Audio Interfaces, Bench Power Supply via USB serial, Oscilloscope via USB serial, etc.
In addition to that hardware I have multiple VM’s for each OMLx Release (Cooker/ROME/ROCK) set up on my ROME machine for doing development and testing in.
I know there is a mix of newer/older hardware and various laptops other folks do testing on, but what those are you will have to wait for them to offer up that information.
Plus we get all the user feedback when people report successes or issues with hardware & software which is immensely helpful not just for us but for everyone who uses OpenMandriva Lx.
Hardware compatibility is a function of the kernel. Some things are out-of-tree, like those Asus Zephyr laptops with the second tiny screen built in, but for the most part if something works with Linux then it will work with OM.
I am going sound overly critical about this suggestion, but hear me out.
If we make a list like that, then testing of platforms that don’t work will never happen. The whole reason the list comes into being is because people tried to install the distro and it didn’t work for some reason.
A better idea would be to have a more interactive user community instead of people thinking that using a Linux distro is just a drop in replacement for Windows or macOS. In some scenarios, Windows is not a drop in solution, either. People need to use computers and engage with the community that built the software they use instead of perpetuating the mentality that “someone else will deal with this.” The hardware belongs to the user, not us. We may own similar hardware to some users, but we don’t have a plethora of stolen money to just buy rooms full of hardware to test.
But, it’s not. That is probably how Linux distros went so wrong. It’s not “Poor Man’s Windows”.
I think you misunderstand. There is no one that comes here wanting that. Everyone wants to get it to do things that are not right out of the box. For instance, behaving like Windows.
I’m just being honest about the expectations for the value proposition. If people want something that just works, then Windows was a viable solution for that. It’s practically no cost if you buy a cheap PC, and upgrades only cost you your privacy and data.
The hope is that people who use OMLx will join the community and help us make it better. If we never hear from anyone that uses it, it will never be better. Providing something at no cost and expecting people to be part of the process that fixes things that do not work on their systems isn’t a big ask.
You can just use OMLx. That’s okay. No one is trying to judge or guilt you for that. Just don’t go around saying that we need to do more work to make things easier while you sit on the sidelines. You could be cataloging issues and bugs and compiling them into a list. That doesn’t require specialty hardware.
I’m only pushing back on you because you are asking us to do something that you could be doing and making excuses why you can’t do it. Then you spin it like I’m being the asshole.
I am giving you a valid scenario that occurs regularly. We get more “issues” and “bug reports” that have to do with users wanting the distro to work like Windows or any other distro. The way things get done around here is you roll up your sleeves and you do it. If you can’t do it, then be honest about that. Making a list does not require you to own any other hardware, and you are being very cavalier with everyone else’s time.
If you want it to work out of the box, install it and browse the web. OMLx has the same issues all the other distros do (or will) have regarding hardware and other things outside of the default experience that they want to do. It’s no big secret (over the past 20 years) that you will need to be conscious of the hardware you choose to run a Linux distro on, even if that has lessened in the past 5 years. It’s a night and day difference now from what it was, because people did the work to report issues.
All I wanted was a list of hardware that the testers use before an official release, and you seem to make it sound like I’m asking for the world on a plate.
That’s kind of assuming the ignorance of the reader by thinking they cannot scroll up.
It has nothing to do with me acting like anything. It has to do with you making my point for me. You don’t want to test, you feel you shouldn’t have to test, but there needs to be someone that tests. The very first thing I said was that work is not going to get done if a list already exists, which is a logical statement. It’s a chicken-egg problem. Why do you test when there is no reason to test? Very obviously, other tools exist already to solve the problem. The larger problem is, we don’t have the hardware to test, and you don’t have the hardware to test. So, who does the testing to make the list?
Eventually the need to test is going to fall off, though. That is how it has been over the past 20 years of growth of Linux and other driver modules. I don’t like that this DVDRW probably works just fine, but has issues with my tower. Is that an issue with the driver, the system board, the PSU, or k3b? I’m only going to find that out by testing it. I can’t expect anyone else to do that with my hardware, because it’s my hardware.