helloSystem / ISO

helloSystem Live and installation ISO
https://github.com/helloSystem/
BSD 3-Clause "New" or "Revised" License
807 stars 58 forks source link

ISO Won't boot on metal nor VM #290

Closed ghost closed 2 years ago

ghost commented 2 years ago

Hello, I'm attemping to boot hello-0.6.0_0F54-FreeBSD-12.2-amd64.iso and it doesn't seem to work.

On bare metal, i get the FreeBSD logo and that's all, it just gets stuck. I've tried booting from UEFI and without.

In a VM (virtualbox), it does the same thing.

Please let me know what I should try to do, I believe my hardware SHOULD be supported.

probonopd commented 2 years ago

How long have you waited? It takes a couple of minutes due to https://github.com/helloSystem/ISO/issues/4. Please boot in verbose mode as shown in the documentation.

ghost commented 2 years ago

Appreciate the quick response, I didn't think that would really matter. I'm going to sleep now but I'll boot in verbose and report back tomorrow.

Sick project btw, really hope to get it running.

probonopd commented 2 years ago

The slow boot time of the Live ISO has nothing to do with the RAM size. The full content of the ISO is being copied to RAM, and this can take some time. We want to improve it.

probonopd commented 2 years ago

Please boot in verbose mode as shown in the documentation.

linlinger commented 2 years ago

I boot in verbose mode . It looks like it's waiting for live file system to appear .image

I've waited for about 5mins

probonopd commented 2 years ago

Indeed. Strange. Are you sure your downloaded ISO is OK?

linlinger commented 2 years ago

It looks okay. I've checked md5sum image

jhonnystene commented 2 years ago

I'm having the same issue on bare metal. I am booting with Ventoy.

probonopd commented 2 years ago

Please retry with the latest experimental 0.7.0 ISO. We have reworked the LIve Boot process and improved Ventoy compatibility. The latest Ventoy version is needed.

jhonnystene commented 2 years ago

Please retry with the latest experimental 0.7.0 ISO. We have reworked the LIve Boot process and improved Ventoy compatibility. The latest Ventoy version is needed.

That solved the issue.