brent I never heard of the old 4.2 isos giving anyone a headache.

You might want to read back into the threads from 2020 or thereabouts. Discrete graphics card drivers and wifi drivers have been a perennial problem, and that hasn't changed.

Neumie Consider: if the RX 7000 series and Intel ARC GPUs released today and someone had them in their PC. Would the current Solus ISO be enough to get a new install completed in a smooth and trouble free way? Or would they need to pass in extra kernel parameters? Or would they be stuck looking at a blank screen?

Neither is supported by the ISO kernel (5.13) or the current kernel (5.15), so both would have issues running under Solus at this point. It isn't clear to me whether the 5.18 kernel supports either/both or how well. Kernel support for the newest hardware is always a problem in Linux, because OEM's aren't diligent about delivering drivers to the kernel and the kernel always lags.

That is not to disparage/deny your basic point, which is that the Solus ISO needs to be updated relatively frequently (twice a year, maybe) in order to keep up with the pace of hardware development.

Edit/Update: I am scratching my head again this morning, trying to sort out whether or not to install Solus Budgie on my railroad laptop (Latitude 7390), rather than continue to use Windows 11 on that laptop. My brain says "No" (scaling and battery life issues) but my heart says "Yes". However that sorts itself, it reminds me that Linux presents issues beyond the state of the ISO for many users, even those using vanilla hardware.

        I thought the install experience was good. The GUI installer in the Live ISO is nicer and easier to follow than other distros (I'm looking at you Fedora). Afterwards, went to the software center and updated. It took a long while to download and install the updates, but it didn't require any intervention on my part.

        tomscharbach You might want to read back into the threads from 2020 or thereabouts. Discrete graphics card drivers and wifi drivers have been a perennial problem, and that hasn't changed.

        I was here, I read 'em. Had that caveat in my reply, i.e., it could happen to anyone

          murbert that would all have to be graphics card/kernel incompatibility I suppose---I mean for the ones that can't boot the .iso...
          ...for some reason I thought going backwards may improve that situation.

            @tomscharbach thanks pointing me to the discussion, it was an interesting read.

            I would like to clarify, when I said Minimal ISO I was thinking:

            • The ISO would not have a live environment, booting the ISO will bring you directly to an installer
              1. The ISO would contain all the packages necessary to install any of the Desktop Environments, then run an update
                Calling this a Minimal ISO maybe misleading, since it would likely be much larger in size the a normal Solus ISO. (Just no Live Environment)
              2. The ISO would pull most/all packages necessary to install the selected Desktop Environment form the Repository
                This would basically be an "online installer", personally hate those and would avoid it if possible. Though I can see logic logic behind it when first thing you do is is run an update, and practically your entire install is outdated.
              3. The ISO only contains and installs a single Desktop Environment
                Basically what we already have, but without the Live Environment

            My though process was that: If the difficulty in providing more frequent ISO updates, was caused by the need to test and ensure the stability/quality of the Live Environment. Then maybe stripping down the ISO to include only an Installer and the Packages needed to install the OS would enable more frequent ISO updates.

            Option 3 was not really suggested in my original post, but added it for completeness

              QTC The ISO only contains and installs a single Desktop Environment
              Basically what we already have, but without the Live Environment

              Thanks for clarifying.

              A small technical note: Budgie, Gnome and MATE desktops are somewhat "switch and swap" but Plasma is not: "WARNING: Do NOT attempt to install ANY other desktop environments next to KDE Plasma Desktop. This scenario is NOT supported and you will be told so in no uncertain terms if asking for support." So I suspect that the idea would work with Budgie, Gnome and MATE, but not Plasma.

              That being said, I have run across a "roll your own" installer (can't remember which distro) that supposedly uses check boxes to pick (1) which drivers are installed, (2) which DE is installed, and (3) which applications are installed. I looked at it because I thought it might have been designed along the modular "plug and play" model that I've been interested in for years, but it was not. I say "supposedly" only because I read about the distro but wasn't interested enough to try to install it, so I don't know if/how it works.

              • QTC replied to this.

                  @tomscharbach I never considered the possibility of installing multiple Desktop Environments concurrently. I was originally thinking that there would be a radial button, drop down menu, or a list where you can select which version of Solus you would like to install. (Not dissimilar to those Windows ISOs that ask if you want to install Basic, Pro, Enterprise...)

                  If Solus would want to implement multi DE install, then upon a user selecting an option they could gray out (disable) the incompatible options. Which would basically amount to Install only Plasma, or anything but Plasma.

                  Though personally I see the install of multiple Desktop Environments as a advanced user feature, that only a subset of users would probably want or actively use.

                  tomscharbach A small technical note: Budgie, Gnome and MATE desktops are somewhat "switch and swap" but Plasma is not

                  I'm actually a Plasma user these days. Even though I have a Budgie dual boot, I haven't booted it (or updated it) in more then a half year or so.

                  Based on my impression of situation, it looks like the instability between plasma and other DE's is mainly due to incompatible configuration settings. I also suspect that some DE's packages react poorly to the presence of Plasma, or the other way around.

                  That being said, we all share one Repository. To my knowledge when the build server builds a package, it doesn't build said package for a specific Desktop Environment (except for DE specific packages such as the window manager, libraries, and some apps like the settings panel...).

                  In which case:

                  • The Core of the OS should practically be the same for all DE's (kernel, display server, sound server, SystemD...)
                    • DE's often share the some of the same default applications as well (LibreOffice, Firefox...).
                  • Creating an ISO that has all the packages needed to install every DE they support should not be technically infeasible, though I question how much complexity this may add and whether it will be worth it or not in the end
                  • If the level of duplication between different Desktop Environments is high as I suspect, the combined ISO would significantly smaller then 7.6GiB (The total for the 4 Solus 4.3 ISOs)
                  Edits:
- Change: radial button, or a drop down menu >> radial button, drop down menu, or a list
- Fix: quote link should link to post of said quote, not the user account
                    23 days later

                    I warn I didn't read it all, even more because of off-topicness. I think a new iso is urget: I have two friends with potato computers who are next to install Solus due to my recommendation. But the old iso has two problems: if not immediately updated and rebooted, nothing ever opens. It happened in all installs I did something other than update and rebooted. Even changing the mouse to left-handed caused that.

                    The other problem is more obvious: so much to update in one time is a problem by itself. Here in a country with not so cheap not so fast internet, updating 1,4 GBs will be, at least, scary. And it would be frustating if after downloading all that, the system break (are non opening apps a break, right?)

                    I remember nothing of this happening when the iso was new.

                    It's more than a year old, it should already have been updated.

                      drama I think a new iso is urget: I have two friends with potato computers

                      Potato computers will not benefit from a new ISO

                      drama But the old iso has two problems: if not immediately updated and rebooted, nothing ever opens

                      1st thing you should do with ANY distro is update
                      1 month after a new ISO comes out the updates will be big again

                          drama A few thoughts:

                          (1) The consensus on this forum (from other threads concerning the question) is that Solus should update the Budige, Gnome, MATE and Plasma ISOs periodically to support new hardware as it comes along. As far as I can tell, there is no consensus, however, on how frequently Solus should update the ISOs. Annual or twice annual updates seem to be the most supported. That said, I suspect almost everyone on the forum believes that it is time for an updated ISO set.

                          (2) Post-ISO updates are a routine (and necessary) part of installing any distro. The size of the Solus post-ISO updates is currently high (it varies from DE to DE), but not particularly so in comparison to many other distros (in particular rolling-release distros, which update packages frequently).

                          (3) A number of distros "hide" the post-ISO update process by installing updates during the installation process (which lengthens the installation process but is invisible to the user), but of those that do not, my experience is that it isn't at all unusual for 600-1000 packages to be updated post-installation.

                          (4) As @murbert pointed out, an updated ISO is not likely to affect anything with "potato" computers, because "won't boot without update" issues are almost always hardware-related, and the hardware in "potato" computers (generally five years old or older) is usually supported by kernels that are much older than the 5.13 kernel (released in July 2021). As a general rule, if the "Live" USB session runs on a computer, the installed ISO from the USB will run on the computer. My personal "potato", a now-defunct Dell Inspiron 11-3180 circa 2017, installed and ran fine on the 4.xx kernel, although (because of the computer's low specs) downloading, installing and updating took a long time.

                          (5) Because Solus is a curated rolling release, in which almost all packages are updated over the course of a few months, the number of packages installed post-ISO will be high again within a few months after release of any ISO. My experience (if I remember right) is that roughly 500-600 packages updated post-installation within a month or two after the 4.3 ISO was released.

                          (6) Because you live in an area with slow and expensive internet, I wonder if your friends might be better off with a traditional LTS release because fewer packages update weekly. I run both Solus Budgie and Ubuntu Budgie 22.04 LTS, and I've noticed that Ubuntu Budgie's weekly updates are significantly smaller than Solus Budgie's.