Thread Info
  • State Suggested Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 14437 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UEFI Boot XG Firewall 18.0 GA-Build379

Martin Gross

Hello,

I have ASRock J4105B-ITX board with PCIE 4Port NIC, and now I am not able to run SW SFOS 18.0 GA-Build379. Board supports only UEFI boot. The installation proceeds properly, but after a restart the system does not boot from the disk.

I tried the same version on an old HW (Celeron 1037U with dual NIC) switched to UEFI Only mode with the same result.

If I switch 1037U to Legacy boot only, it boots normaly afrer reinstallation in legacy mode. 

Is the problem only on the last Build?

I tried to download another build of v18 (339 and 354), but download link of iso file ends on other page - https://community.sophos.com/kb/en-us/135412

Is it possible to download iso build 354 somewhere?

 

Thank you



This thread was automatically locked due to age.
  • 0 in reply to rfcat_vk

    Hi all,

    I will not solve this problem. The boot ending on grub rescue, manual start is possible and without problem (must set root nad prefix variable and switch to the normal mode, the boot menu will starts and boot Sophos). It works, but not usable for real operation. I tried generate bootx64.efi with grub config from ubuntu which loads the original config from SSD. The boot menu will load, but system not starts, ending on error "Kernel doesn't support EFI handover". Bad way.... I need olders build (cannot be downloaded from the sophos web) or bootx64.efi file from the working system. On the file xboot64.efi on installation iso is all path hardcoced to bad destination and do not accept any config file.

    @Keyur - Is it possible to download an older iso somewhere? v17.5 does not support UEFi and last v18 not booting

     

    Martin

  • 0 in reply to rfcat_vk

    The NUC7 comes with a Realtek 81xx NIC. I think it's the problem with the EFI boot partition as well. The hdd does not contain a boot loader after the installation. 

  • 0 in reply to JJ FEI

    Hi,

    I am not sure what NUC7 you are  looking at and why you think Intel would pay Realtek licensing fees when intel have the i219-v which is their home/domestic NIC.

    All the NUC7s I have reviewed all come with i219-v.

    Further I  see they have internal expansion slots but nowhere can you access the added card at least not on my two.

    If you want to use a NUC7 for XG you will need to to install some form of VM software to mask the i219-v, the USB and WLAN devices so the XG thinks that are supported devices.

    ian

  • 0 in reply to Keyur

    Keyur said:

    Hi  

    I would request to check below given link,

    https://ideas.sophos.com/forums/330219-xg-firewall/suggestions/34090690-uefi-boot

    https://community.sophos.com/products/xg-firewall/b/blog/posts/xg-firewall-v18-ga_2d00_build354-is-now-available  << the ISO file is not available to download???? >>>

     

     

    Other people have also reported.  I would like to try this version v18??

  • 0 in reply to LuCar Toni

    LuCar Toni said:

    It was replaced with Build 379.

    https://community.sophos.com/products/xg-firewall/b/blog/posts/xg-firewall-18-0-ga-build379-released

     

    Thanks!  Downloaded and firmware loaded to hard disk ...not bootable as noted above... What are the chances SOPHOS will provide a full EFI bootable install?  v18 installer is now EFI boot aware and loads the firmware onto the newer hardware however we can't boot that image without the efi boot section on the installed disk based on what Martin discussed above and I can confirm.

    I am OK that we made this progress however as most new hardware comes to market less and less will be legacy BIOS based bootable. Can we get another v18 that is EFI bootable post image install? 

     

  • 0

    I maintained a server that had EFI (just before Intel made it public and it became UEFI) in 1998.

    In 1998. Yes. Before the famous 2000 year bug.  The century before the one we are living in.

    Yes 22 years ago.  We were still using diskette drives then.

    And yet, Sophos comes up with hardware with no workable UEFI and no TPM.  Like 25 years ago.

    Now, that's computer archeology.

    Paul Jr

  • 0

    So ?

    Anyone have the magic BIOS/UEFI setup recipe to have XG boot in UEFI ?

    Paul Jr

  • +3

    Same problem is on v18 MR-1-Build396, after fresh install is EFI partition empty.

    I tried to install a new grub from Ubuntu Live 20.04, but ending with error "kernel doesn`t support EFI handover". The problem was a new grub on Ubuntu. After installing the EFI loader from Ubuntu18.04 it already works fine.

    Solution:

    1) Install SFOS

    2) Boot from USB Flash Ubuntu Live 18.04

    3) Open terminal and write:

       sudo apt install grub-efi-amd64-bin
       sudo mount /dev/sda1 /boot
       sudo mkdir /boot/efi
       sudo mount /dev/sda2 /boot/efi
       sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi/

    4) reboot

  • 0 in reply to Martin Gross

    Martin Gross said:

    Same problem is on v18 MR-1-Build396, after fresh install is EFI partition empty.

    I tried to install a new grub from Ubuntu Live 20.04, but ending with error "kernel doesn`t support EFI handover". The problem was a new grub on Ubuntu. After installing the EFI loader from Ubuntu18.04 it already works fine.

    Solution:

    1) Install SFOS

    2) Boot from USB Flash Ubuntu Live 18.04

    3) Open terminal and write:

       sudo apt install grub-efi-amd64-bin
       sudo mount /dev/sda1 /boot
       sudo mkdir /boot/efi
       sudo mount /dev/sda2 /boot/efi
       sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi/

    4) reboot

     

     

     

    Martin ...Thanks!    

    SOPHOS ... What is the chances this can be corrected going forward to allow the community to use new hardware with out this intervention on all new firmware ??