System: Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7
wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine: Type: Desktop System: Gigabyte product: GA-970A-UD3 v: N/A serial: <filter> Chassis:
type: 3 serial: <filter>
Mobo: Gigabyte model: GA-970A-UD3 serial: <filter> BIOS: Award v: F4 date: 10/13/2011
Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 serial: <filter>
charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech M705 serial: <filter> charge: 50%
status: Discharging
CPU: Topology: 6-Core model: AMD Phenom II X6 1055T bits: 64 type: MCP arch: K10
L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 33827
Speed: 1393 MHz min/max: 800/2800 MHz Core speeds (MHz): 1: 1953 2: 1742 3: 1851
4: 1042 5: 805 6: 1829
Graphics: Device-1: NVIDIA GF114 [GeForce GTX 560] vendor: Micro-Star MSI driver: nvidia
v: 390.157 bus ID: 01:00.0 chip ID: 10de:1201
Display: x11 server: X.Org 1.20.13 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1280x102460Hz
OpenGL: renderer: GeForce GTX 560/PCIe/SSE2 v: 4.6.0 NVIDIA 390.157 direct render: Yes
Audio: Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1002:4383
Device-2: NVIDIA GF114 HDMI Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:0e0c
Sound Server: ALSA v: k5.15.0-91-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8168 v: 8.048.00-NAPI port: ee00 bus ID: 03:00.0 chip ID: 10ec:8168
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 1.82 TiB used: 128.72 GiB (6.9%)
ID-1: /dev/sda vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
speed: <unknown> serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WD5000HHTZ-04N21V0 size: 465.76 GiB
speed: 6.0 Gb/s serial: <filter>
ID-3: /dev/sdc vendor: Western Digital model: WD5000HHTZ-75N21V0 size: 465.76 GiB
speed: 6.0 Gb/s serial: <filter>
Partition: ID-1: / size: 915.33 GiB used: 128.72 GiB (14.1%) fs: ext4 dev: /dev/sda5
Sensors: System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 41%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/libreoffice-ppa-focal.list
1: deb http: //ppa.launchpad.net/libreoffice/ppa/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/teejee2008-ppa-focal.list
1: deb http: //ppa.launchpad.net/teejee2008/ppa/ubuntu focal main
Info: Processes: 289 Uptime: 4h 33m Memory: 15.61 GiB used: 4.74 GiB (30.4%) Init: systemd
v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 client
inxi: 3.0.38

[ IF YOU FIND MY WIFE'S MEASUREMENTS, PLEASE DELETE !!!]

    while running the DVD (solus live environment), open the Gparted tool.
    Your existing Ubu will show a 1MB boot partition, then a swap, then the system files.
    If there is no space then after that, then Solus may offer to shrink the Ubu crap ("Install Solus Alongside of X") option.
    If there IS a bunch of room for Solus then highlight the non-Ubu space in Gparted and format it to GPT.
    Hopefully Solus will direct itself there.
    OR
    Solus should give you the opportunity to direct the install there (there=new gpt partition).

    Since we don't know that...
    ...in fact there are still important things we don't know, chiefly because I suck going back and re-reading...

    at what exact point in the GUI Install process does Solus fail? What step? What does it say? Does it just freeze? Or abort? Send a pic of what it looks like when you open Gparted in the live dvd. That will help. Pics of the wife not necessary😉
    edit/punctuation

      blueicetwice OpenGL: renderer: GeForce GTX 560/PCIe/SSE2 v: 4.6.0 NVIDIA 390.157 direct render: Yes

      this will be deprecated (unsupported by nvidia) in solus and the homegrown Nouveau will work fine.
      I did not get the impression your Gigabyte product is "too new" for Solus--that's where common installs for 4.4 fail (new ISOs coming as you know)

      EDIT: XFCE may be a month of two away if I had to guess as an observer. try budgie.

      other thoughts: re-burn your Mate DVD for the hell of it. Pay attention to Solus's prep demands. I always find if I deviate then I've made a live medium useless and I try try again.

      Question remains: at what stage does install Fail?

        With 3 disks is this a multi Os boot setup?
        If it is might explain it (I am no expert at multi boot)
        Lunch time..lol

          brent

          Brent, my rig will not allow for GPT partition ! Both "disc" and "geeparted" show
          a successful installation, with Das Boot. Neverthebloodyless, when starting the boot
          it is not in the boot option. Odd, however, it does show up in the Grubhub Customizer. !

          I can not load any pixs, Brent. There were two abortions and the others stated "successful
          installation." Could this be an Ubuntu or Mint ploy or plot ?

              Axios

              AX, fix this issue and lunch is on me.

              I have tree HDD, with a single OS and each. I try not to comingle.

              The only multi boot dat I understand, was in basic training.

                blueicetwice ......in my limited understanding, the bios just guarantees a Grub install (I think) and Solus would meke the Grub partition itse;f..still don't see the correlation.

                It is utterly mindbogglind to me that Solus tells you installation was a success on boot then aborts on launch...

                To me this means one of two things:
                1) incompatible Graphics card (longshot)

                2)Or more likely Axios is right: the other jealous distros are interfering. My advice is UNPLUG the other two then boot solus again. I am predicting success. Something is goofy in the boot then if what you say (Solus says install was successful) is correct.

                Hang in there. this distro is well worth it and I've tried most.

                      D/Led GOGONOME and was told the installation was successful. Fabulous how the
                      screen slowly fads into darkness ! Brilliant engineering.

                      Upon restart, the issue again, Solus was not in the boot up order, even tho it was listed
                      in the Grubhub Customizer.

                      It has been a joy to communication with y'all, butt this is truly a waste of time, despite
                      being on home detention. 🇧 🇪 🇩 🇫 🇪 🇪 🇧 🇦 🇩 : <---------- my imoji are blockheads : - ))

                      blueicetwice reinstall with others unplugged was probably the better suggestion, but all good.
                      "D/Led GOGONOME and was told the installation was successful." I don't know what means. The installer usually says at the end something like 'solus installed successfully'; or similar so if that's where you saw it...then grandiose🙂

                        Brent, what dat means the installation was successful, according to
                        ISO d/l disc.

                        I did another install and Solus populated the boot up order. Den,
                        which I click the Solus boot line I got this: "ERROR: file /Das Boot/Solus Project.
                        current.6.3.8-240 not found"
                        ERROR: you need to load Lt. Kernel first.

                        Another dead end ! : - ( Next try, I will UNPLUG the two other HDD and the ninth
                        reinstall. In the meanwhile, time for dinner. The wifi is serving stir fried hard drive,
                        with stuffed Chinese Dram.

                        I did to fail to mention, I am installing on an HDD with Manjaro on it, but dat
                        should not make a difference.

                          blueicetwice did to fail to mention, I am installing on an HDD with Manjaro on it, but dat
                          should not make a difference.

                          'Sometimes' it makes a difference is my cryptic answer to that. you never know til you know. e.g. a partner OS installed with Grub will unceremoniously mug, then disappear, Solus' UEFI bootloader (if installed that way) about 8 times out of 10 if I had to guess and 10/10 for me personally (that's why separate drives per OS for me). Maybe it was Manjaro in the cellar with a candlestick (to bludgeon a Clue metaphor) the whole time?

                              brent

                              "Maybe it was Manjaro in the cellar with a candlestick (to bludgeon a Clue metaphor) the whole time?" LOL, LOL

                              (that's why separate drives per OS for me) ditoes for me, as well, Brent.

                              If Solus has a UEFI bootloader, den dat may explain the problems, since my mama board is
                              not compatible.

                              Hear, is what happen last night. I disconnected the other two HDD, as per your instruction
                              and holey heck, the installation was successful, even after a fresh bootie. Watching the boot
                              lines, I noticed that the boot for Microgates 7 and Minty Mint were absence. 🇧 🇦 🇩 To
                              quote Ms Greta Thunberg, "this is all wrong."

                              When I had only the Mint HDD plug in, the old bootloader lines appear !! Unfortunately, Solus
                              bootloader was not present. : - (( I now suspect it is not Solus fault, but rather my dated Mama
                              board. It is likely, I will have issue with other Linux discos, as well.

                              Brent, tanks for your support and the others, whom had commented. I have boarded an engine
                              power vessel, thus allowing Solus to sail to its next destination, less my baggage.

                              PS: This was not an issue, when I installed Solus some ten years ago.

                                  blueicetwice Solus defauklts to UEFI install but can be made (in the installation GUI I believe) to installal GRUB boot instead. I have never tried this.
                                  Either way, I agree, you tried.

                                      brent Its amazing the countless threads I have seen on here about Os,s not playing
                                      nice with each other.

                                          Axios yep it's happened to me with linux and windows. Solus get's bullied a lot in my experience, probably because efi bootloaders is alien to most things grub and also to windows who has a bootloader...although I saw a single instances here recently where someone claims Solus wrecked all their other existing boots but I've never seen that. Strange times!

                                            9 days later

                                            UPDATE for my mates.

                                            I tried two more installations and botf failed. Since Mint took a powder on me,
                                            I decided a last attempt, with Solus 4.5 XFCE. Now the installation was NOT
                                            a dual bootie, but a single installation on the entire HDD.
                                            HOLEY VACA [COW] <---- Latin, it not only did it install, but bootied up as well !!!!!!!!!!!!!!!! :<))

                                            Brent, was right about the problems with dual OSs, on a single drive. Same issue when da wifey
                                            is driving.

                                            The grubhub found itself on another HDD, so it required the change in HDD start up order. I bet if
                                            I try to reinstall MInty 20 next to Solus, it will fail too.

                                            The installer is the BEST I have ever used; quick, easy and with clear instructions. Mint installer, [21.3]
                                            is rather AARPish and much slower. And it was not the UEFI nor the advanced kernel, which
                                            I speculated as to the issue, in this twelve-year-old rig.

                                            I wonder what I should do with MInt ??? There is an orphanage just three miles from me.

                                            ![