Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - DTRFX

#1

Quote
I have a different motherboard from OP, mine is a Gigabyte GA-J3455N-D3H (rev. 1.0) but I'm guessing the chipset might be the same.

What's your sata configuration in BIOS and also as I understand your board has two controllers... Have you tried using SATA_2 or SATA_3 on your board instead?
#2
Think it's the same... Not too sure though... I didn't have any ahci problems on 2.4.2...but it's definitely worth trying to get Opnsense running
#3
Did u do a clean reinstall or an upgrade? Whats your hardware?

and at which point exactly does it fail?

My instructions above are for after the upgrade from 17.7 to 18.1
#4
tell us if it worked :)
#5
Habs doch noch fixen können - hab hier beschrieben wies geht:

https://forum.opnsense.org/index.php?topic=7142.0
#6
Quote from: pmcdonnell on February 03, 2018, 01:08:26 PM

I did see this on a FreeBSD forum, but I'm not sure it's entirely related:

https://forums.freebsd.org/threads/51868/page-2

Thanks for the hint, managed to get it fixed now:

For first booting:

1. On OPNsense boot screen select "exit to loader prompt" (i think it's option 3)

2. type:

set hint.hpet.0.clock=0

to address the HPET issue (if u have it)

3. type:

set hint.ahcich.0.sata_rev=2 (depending on which channel your harddrive is using replace the '0' with 1 or 2 or 3 etc.)

4. type:

boot

it should boot up fine now

5. add the settings to /boot/loader.conf.local:

- log in after boot, choose option "8 ) Shell"
- type:
edit /boot/loader.conf.local
- in the file add the following two lines (again, see above, only add the hpet line if u have the issue and choose the right channel number for your harddrive):
hint.hpet.0.clock=0
hint.ahcich.0.sata_rev=2
- save the file on exit and reboot
- done
#7
u can fix the HPET issue by using:

set hint.hpet.0.clock=0

on loader prompt (problem has been round pfsense for a while now, too), but then you are still stuck with the ahci timeout.
Hope this is fixed soon - have the same issue with my ASRock board :(
#8
Hab das gleiche Board mit dem gleichen Problem beim Update von 17.7 auf 18.1. Next step: zurück auf 17.7  :(