I have performed a clean installation of solus 4.5 on my PC. But it always starts in the BIOS, I clarify that it does recognize the hard drive where I performed the installation.
I have tried changing the settings in the BIOS, UEFI with secure boot, UEFI without secure boot, Legacy but I always get the same result.
Also, in the installation, when creating the partitions, I choose the option to Erase the entire disk, and in the "Boot loader location" section I tried "Boot partition (/boot)" when I installed it with UEFI and secure boot; and I also tried "Main Boot Record (mbr)" for Legacy.
I have an old desktop PC, with an Intel pentium G3240, 4GB of Ram, Asus H81M-A motherboard
Problem when performing a clean installation
ji-roth It should be turn off fast boot,and secure boot either select eufi only or have it do both
check in your boot sequence I use usb then Hdd. (in bios)
Sounds like you did the rest right.
Does it show any errors or just go to bios.
Secure boot you have to install separate.
I cant say I have seen one boot to bios usually tells you something and asks you to.
You could try getting to your boot selection at startup and see if it boots that way
Axios It doesn't show any errors, it just starts in the BIOS.
I have tried disabling fast boot along with safe mode. But I still get the same result.
In any case, I chose to try Chrome OS Flex, since it is a PC that will be used for home use and basic things. And I was able to carry out the installation.
But anyway, it caught my attention that when I wanted to activate the Linux option in that OS, it did not allow me to do so. I don't know if it has to do with the hardware...
- Edited
ji-roth That is interesting so appears not to be just a Solus thing
I dont have an answer for you.
Will ponder it maybe something will hit me.
There was talk about how far linux would go back and support hardware but I dont think
thats the case here. I think your mobo around 2012 (not 100% sure)
If it boots the Solus live should run we are overlooking something.
This is a long shot but it could be your hard drive that is at fault here. If you boot into a live session can you mount the fitted hard drive and see the files that were loaded onto it during the install?
From experience I know that if the health of the drive is poor, writing to the drive is possible but on boot it will fail on POST.
Many live distros have tools that can test SMART data for the main drive. Probably worth the check.
- Edited
I had a brain Fart maybe Cmos battery?
Other than that got be something hardware I think
- Edited
i have 2 settings in my old bios: "legacy&uefi" and "uefi" only. keep it on uefi only.
I just installed XFCE. I would not let Calmares do any work for me with partitions.
Nuke your install, go into to live environment, open gparted, and format the whole drive that you dedicated to Solus (smart, btw) in GPT. this is a required pre-install step at least to me.
On top of that gpt disk you can build your 1GB /boot, your ext4 filesys, and your swap. Or let Solus-Calmares do that.
ji-roth , and in the "Boot loader location" section I tried "Boot partition (/boot)" when I installed it with UEFI and secure boot; and I also tried "Main Boot Record (mbr)" for Legacy.
maybe you do need to make one for calmares? no mbr needed.
short version: new install, uefi only. format your whole disk to gpt before calmares install.
2 cents
edit: I've read this thread twice and I don't get it all. Calmares tells you in dialogue that "Solus installed successfully now please reboot"? the installer confirms these words or thereabouts? and you pull usb stick out, reboot, and SOlus won't boot? Is that what's happening?
- Edited
I think asus at a point in time had some machines locked only to winders in eufi but you
could install to legacy still. (because of secure boot stuffs)
set bios to legacy only (If you can) and install legacy
Maybe thats why its going back to bios
Just another thought (if I am wrong disregard)
Note seen one complaint about that on the g series mobo from asus
Axios maybe you have a point. legacy only is probably that things default mode in the past. it could work if he avoids that mbr stuff. when I got into legacy for kicks the way the boot sees all the boots changes dramatically (duplicates of sorts) but that's hard to explain here. at this point the mythical solus grub install could work in legacy
brent edit: I've read this thread twice and I don't get it all. Calmares tells you in dialogue that "Solus installed successfully now please reboot"? the installer confirms these words or thereabouts? and you pull usb stick out, reboot, and SOlus won't boot? Is that what's happening?
Yes, That's exactly what's happening.
- Edited
ji-roth if the installer said the install was successful..and you pull the stick out, and reboot, you are just staring at a black screen, or one with a blinking cursor?
you changed to bios uefi then rebooted and no solus.
you changed to bios legay then rebooted and no solus.
if you reboot and there is some splash bios info before black screen then bios not effected.
do you have an F-key to spam while you are booting up to see what's available to boot? (for me its F11).
there will be clues there.
solus tells you it was a successful install but the something is keeping the bootloader from booting?
What I wonder?
Could go back in Live, then gparted, and see if your boot partition has the boot, esp flags. and the filesystem is ext4.
this is what the fresh install should look like (this is my budgie):
one last thing-- I would not let installation format disk for you. If it's a dedicated solus-only install I would have formatted it to GPT first (live environment, gparted), then let the Installation media do the rest. that's just me though.
edit: real short version. see if you can get a boot menu with an F-key when firing up. what does it say/show? take a picture of your install in gparted for kicks.