XG Home hang on Booting 18_0_0_180

Hi Paul,

I'm confident that CPU is supported as it's the same family as the N4000 CPUs which I have seen work.

Have you changed the UEFI BIOS to operate in legacy BIOS mode?

At this time, the XG is not compatible with UEFI.

Edit: It could also be because you have a single NIC, the XG does not like having only one NIC

Emile

Hi Emile,

I understand. Maybe I asked wrong quiestion. I should ask for UEFI support.

Due to Intel restrictions, lot of vendors are taking away from legacy BIOS. So now I can buy only boards with UEFI only boot :-( And mostly all new board will have these restrictions - U can google for "intel support legacy bios".

When I first saw new SFOS 18 ISO, it came with UEFI boot, And now I am able to install SFOS on UEFI motherboard. WOW

After restart, GRUB is loaded. And after few seconds system shows "Booting 18_0_0_180". HDD LEDs are blinking for few seconds, and thats all.

But ... wait ... I had just one NIC. I shoul try tomorrow.

Thank you.

When I was setting up the EAP in a VM for testing, I noticed the setup also hung on boot because I only had one NIC selected (although I got a warning message that let me know). After setting up the VM with two NICs, it worked just fine.

Thanks to all of you.

I can confirm now, that SFOS v18 is ready for UEFI boot, without CSM workaround.

My problem was, I think, I was expecting some info on the screen after boot. But there was just "Booting SFOS ...". But XG answered on 172.16.16.16 and all goes fine. Web management works. And I used two NICs.

ASR J5005-ITX is capable of running Sophos XG v18.

uff.

Pavel

Thanks to all of you.

I can confirm now, that SFOS v18 is ready for UEFI boot, without CSM workaround.

My problem was, I think, I was expecting some info on the screen after boot. But there was just "Booting SFOS ...". But XG answered on 172.16.16.16 and all goes fine. Web management works. And I used two NICs.

ASR J5005-ITX is capable of running Sophos XG v18.

uff.

Pavel