ermo
dear ermo,
thanks for your support!
why did i not follow your instructions?

  1. someone in the Manjaro-Forum wrote that its not good to just erase the master boot record. there always should remain a partition table + bootloader to not damage the whole disk. so it is advised to better overwrite the contents with new info than delete them.

  2. today 2 tries to install Solus, but again the Solus-installer always only created a GPT Partition Table on the Master Boot Record. I assume this is the reason why my laptop is unbootable from that.

  3. re-installed Manjaro and the Manjaro-installer creates a MSDOS Partition Table on the Master Boot Record and MBR-bootloader. from there Manjaro boots into a GRUB without problem.

  4. As the Solus installer only creates GPT partition table on my MBR master boot record, my conclusion was that it would have made no difference if i had followed your instructions to erase the master boot record or not, because the system ends up unbootable in any case, wheter i had erased the MBR before or not.

the Manjaro-installer delivers MSDOS partition table out of the box.
if you have any more ideas what i could try...

      BTO someone in the Manjaro-Forum wrote that its not good to just erase the master boot record. there always should remain a partition table + bootloader to not damage the whole disk

      That is in the case that the user don't want to delete the mbr partition for "reuse" in later installations.
      I recommend, if doing a clean install of solus, to not conserve any partitions and letting the installer to do what it needs to do, or for the advanced user, make manual partitioning.
      Just take into account Manjaro is not Solus, Solus is independent and implements some things different compared to other distros; one example is that solus uses clr-boot-manager to manage boot in uefi or bios environments and not directly in to grub.

        I have pondered this I believe I would do what Ermo asked alot of stuff can hide in a MBR and if you
        wipe it there is no reference to manjaro or anything and no MBR at all.(So solus will install a fresh Boot)
        I had to do this years ago wipe a disk to correct things. (More than once)

        Also on a note from what Nolan mentioned it appears your laptop will do eufi from what I can tell to.

        Either of these two things I would think would get Solus going.

        Note: Rescatux has been around long long time even used it back in the day and prob if it had issues correcting
        things I would do above mentioned.

        And when you say Solus wont boot is there anything on the screen?

        Maybe your USB drive has a corrupt installation. As advised above, try Ventoy.

        BTO

        Solus-installer always only created a GPT Partition Table on the Master Boot Record. I assume this is the reason why my laptop is unbootable from that."

        BTO, my rig remodeled in 2011, it did the same thing, placing a GPT on one of the HDD. The MBR, is out-of-order and needs to be repaired. Reinstalling Solus, will not solve this issue, IMHO.

        PLEAZE READ DAS: https://www.minitool.com/lib/gpt.html

            blueicetwice
            in that case, it's interesting 🤔
            EDIT:
            GPT partition table is for UEFI systems
            MSDOS partition table is for legacy BIOS, GPT won't work here rendering the ssd/hdd un-bootable as a direct consequence.

                pomon, excellent guide indeed.

                This command will indict weather one is using a legacy or UEFI boot.

                ls -d /sys/firmware/efi

                  blueicetwice

                  1. PLEASE do NOT highjack/spam my request !!!

                  2. PLEASE: it is NOT a question of wheter i have UEFI or BIOS !

                  i AM definitley on BIOS on this machine.
                  and i have an even older laptop that ONLY has BIOS too.
                  and i want to keep them aline.
                  but if i can not get it to work here, then it does not work on the older one too !!!

                    blueicetwice This command will indict weather one is using a legacy or UEFI boot.

                    I think you might have meant that it will indicate whether ... legacy or UEFI.
                    That doesn't seem to be something that's worth an indictment, whatever the result of the test.

                      BTO someone in the Manjaro-Forum wrote that its not good to just erase the master boot record. there always should remain a partition table + bootloader to not damage the whole disk. so it is advised to better overwrite the contents with new info than delete them.

                      I don't really see the point in trying to help you if you refuse to do the steps exactly as I laid them out.

                      There was a reason I laid them out that way and part of that reason was that, this way, the solus installer and boot manager could do exactly what they need to do from a clean slate.

                      But if you don't want to do that and instead want to insist on following Manjaro advice when you're trying to install Solus and asking for help on accomplishing this on the Solus forum, well, I guess there's no getting through to you.

                      Best of luck I guess -- I'm officially out of this conversation.

                      • BTO replied to this.

                          @BTO I would strongly recommend following the advice ermo provided. He's part of the Solus Team, helps with package and system development and has helped test our ISOs including multiple ways of installing.

                          5 days later

                          ermo
                          dear ermo,
                          i was able to install Solus by the instructions that were thankfully given to me in the Manjaro-Forum:

                          1. GPARTED: Create a new MSDOS partition table
                          2. Solus-installer: choose option REPLACE a partition

                          https://forum.manjaro.org/t/how-can-i-install-budgie-solus-and-create-new-mbr/155371/18

                          Now i have 2 problems on BUDGIE:

                          1. after taking off the laptop from the docking station, and putting it onto it again: ALL sound goes now PARALLEL to the internal laptop-loudspeakers and to the docking stations LineOut.
                            How can i switch off the internal laptop loudspeakers, and set the sounds to its origin docking stations LineOut-ONLY?
                            i already tried with pavucontrol and with alsamixer: no success.
                            i cannot live without my stereo working properly...

                          https://discuss.getsol.us/d/10255-budgie-all-sound-goes-now-parallel-to-loudspeakers-and-lineout

                          1. NEMO: standard installation, standard settings, all OK.
                            i launch nemo.
                            i plug in an usb.
                            a new window is NOT openend. i always have to right-click on the usb and select "open in a new window" manually.

                          why is Nemo file manager not AUTOMATICALLY opening a new window when i plug in an usb-stick or usb-drive?

                          is this behaviour on purpose on Solus-Budgie?
                          could this be solved with setting SYSTEMD or whatever with a command line in a terminal?

                          https://discuss.getsol.us/d/10250-why-does-nemo-not-automatically-open-a-new-window-when-i-plugin-an-usb

                          Might i ask, could you have a look at these 2 problems and response to my new threads?
                          many thanks!