Quote:
Originally Posted by Qury
somewhere I've read that EFI only works properly if you set the chipset to ICH9 in virtualbox
|
I just checked, and it is set to PIIX3 for the chipset , I never actually touched that setting, so I don't know.
Quote:
Originally Posted by colorpurple21859
I coudn't duplicate your problem. I used your mkiso script as is only changed the -o option for the output file.
Was the iso tried on an already existing vm to begin with?
|
That was it, the VM already existed and I merely enabled EFI - *shrug* , I don't know why Virtualbox is so picky as in real life I would have the same use case, enable UEFI support or enable legacy. The solution was to delete the VM outright and start anew - again don't see why I would need to but whatever.
On my actual system, I will most likely still stay with legacy as I don't know why I would need UEFI yet - it is more for me to poke at mainly. What is weird still, I re-attached the ISO just to boot back the ISO, but the VM just boots Slackware , even though I made sure to have it boot via optical disc (iso) first, I don't know I guess Virtualbox still has its quirks with EFI.
So basically when there is another significant update to -Current or say when 15.0 finally is released, I still would have to delete the VM, because now Virtualbox doesn't boot my iso for whatever reason and just goes straight into Slackware.