[deleted]
CorvusRuber Yes, I was saying they could use it to write an iso onto a USB stick so that they could overwrite their current install of Solus
CorvusRuber Yes, I was saying they could use it to write an iso onto a USB stick so that they could overwrite their current install of Solus
Yes but the problem is when I boot the USB key with the Solus installer on it my computer doesn't launch the installer and just put me on the screen: reboot into firmware. How do I solve that please ?
Thanks for your answers
Widraz
Is this the Windows/Solus dual boot system that you mentioned in your other posts ?
If yes, is fast startup disabled ?
That thing can seriously mess up with new system installations.....
Last thing worth to mention: are you absolutely sure that your USB key has been properly set up and it's working as it should ?
It was a dual boot system. I deleted the Windows partition
CorvusRuber Yes I set it up with Rufus with the Solus ISO
CorvusRuber I deleted the Windows partition with Gparted on Solus
LVM?
Widraz
And that left what on the disk ? We can't go on all day like this, describe in detail what you did, how you did it, on what (ie : hardware specs of your still unknown system) and then perhaps a solution could be found.
Otherwise, a neverending stream of one liner answers we'll get us nowhere.
CorvusRuber Here is what I did exactly step by step. I had Solus OS and Windows 10 in dual boot and I prefer Solus OS so I wanted to give the space of theWindows partition to Solus. So I launched Solus, opened Gparted and deleted the Windows partition and Gparted put the me that space as unallowed space. Before that I had prepared a USB device with the Solus ISO prepared on it with Rufus. In the BIOS I allowed USB boot, disabled secure boot and put the USB device as the first one to boot (before my HDD). My PC detects the USB device but just puts on the screen "reboot into firmware". Do you understand better what I did ?
Widraz There is a topic about Reboot into Firmware
Widraz
Can you show us (screenshot) what you see in Gparted in the pc's current state? A screenshot would show the exact state of your disk, which can help debugging your issue more reliably than messaging back and forth.
It's even possible that, since you didn't specify it in your steps, it could be that you simply forgot to apply the changes in Gparted (this happened to me once as well, since Gparted already shows it as 'Unallocated' before you apply the changes).