OPNsense Forum

Archive => 17.7 Legacy Series => Topic started by: Ren on December 04, 2017, 11:22:35 pm

Title: UEFI Installation on ASROCK J3455M
Post by: Ren on December 04, 2017, 11:22:35 pm: I currently cannot get OPNSENSE installed in UEFI mode on my ASROCK J3455M motherboard. Installation is extremely slow (4HRS so far) then gets stuck at 67%.

I see HPET bug when installing pfsense which i didn't experience https://www.reddit.com/r/PFSENSE/comments/7eeh70/asrock_j3455m_problems/#bottom-comments

Installing via MBR works just fine (may be 5mins if not less) but this is just work around for now until i can finish configuring the firewall.

Any suggestions on resolving my UEFI installation issue ?
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Stefan on December 04, 2017, 11:58:22 pm: amd64? I'm having similar problems with the 17.7.5-amd64 distribution.
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Ren on December 05, 2017, 01:17:01 am: Quote from: Stefan on December 04, 2017, 11:58:22 pm
amd64? I'm having similar problems with the 17.7.5-amd64 distribution.
yes
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Stefan on December 05, 2017, 01:44:41 am: Not that it will help any, but the pf system has the same issues trying to shoehorn 64 bit BSD into the Intel platform. It's bootloader for the Intel is the i386 bootloader. And after trying to do a plain vanilla install of BSD my feeling is the BSD "little trick" to bootstrap 64 bits into the Intel architecture is likely where the problem lays.
Title: Re: UEFI Installation on ASROCK J3455M
Post by: MrB on December 09, 2017, 12:32:43 am: I had the exact same thing happen on a Gigabyte J3455N board, installation took hours and got stuck at 67%. Same hardware & same USB stick loaded a Linux "live cd" in no time, so I knew the hardware was OK. After trying n+1 suggestions found on Google I got around to messing about with the BIOS options and saw a setting for USB Mode (or was it emulation). This was set to "Auto" and had options for CD-Rom, Zip, FDD, HDD etc., changed it to HDD and after that the installation went through in under 10 minutes.

The only difference I can think of is that in Rufus the Linux image was written as an ISO image whereas OpnSense as a DD image, but why that would make any difference as to how the BIOS sees the USB stick is beyond me.
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Ren on December 10, 2017, 07:56:45 pm: I ended up installing in SAFE mode which worked fine. Now i'm running into weird delays when the system is booting. Takes 3+ minutes to boot in UEFI mode but in MBR less than a minute. Currently looking to boot in verbose mode and pulling back system log
Title: Re: UEFI Installation on ASROCK J3455M
Post by: franco on December 11, 2017, 02:06:32 pm: Maybe this is a console setting: System: Settings: Administration, choose "EFI" as primary console.

Cheers,
Franco
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Ren on December 12, 2017, 04:32:31 am: Quote from: franco on December 11, 2017, 02:06:32 pm
Maybe this is a console setting: System: Settings: Administration, choose "EFI" as primary console.

Cheers,
Franco

ok
Title: Re: UEFI Installation on ASROCK J3455M
Post by: Ren on December 12, 2017, 04:44:55 am: ok getting several weird errors in my system.log

1st

Code: [Select]
Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 0: ioport 0xc00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 1: ioport 0x1c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 2: ioport 0x2c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 3: ioport 0x3c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 4: ioport 0x4c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 5: ioport 0x5c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 6: ioport 0x6c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 7: ioport 0x7c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 8: ioport 0x8c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 9: ioport 0x9c00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 10: ioport 0xac00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 11: ioport 0xbc00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 12: ioport 0xcc00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 13: ioport 0xdc00 alloc failed Dec 10 04:48:57 OPNsense kernel: ahc_isa_identify 14: ioport 0xec00 alloc failed
Found this FreeBSD bug in regards to issue https://lists.freebsd.org/pipermail/freebsd-current/2014-October/052554.html

Second error

Code: [Select]
module_register_init: MOD_LOAD (vesa, 0xffffffff81149b90, 0) error 19
From what i was able to find this is a video driver issue which shouldn't affect my boot time.

I'll put it into production this weekend. I can live with the delayed boot time at this point
Title: Re: UEFI Installation on ASROCK J3455M
Post by: ULtImatefreak on December 20, 2017, 12:50:53 pm: I had similar issues on a gigabyte GA-J3455N-D3H an solved it by disabling c-states in the cpu-settings in the bios.
After that it runs realy fast!

Greetz
Uli