AHCI Timeout on 18.1 but 17.7 installs fine

Started by pmcdonnell, February 02, 2018, 03:54:09 PM

Previous topic - Next topic
Quote from: DTRFX on February 04, 2018, 04:03:38 AM
Quote from: MrB on February 03, 2018, 03:44:03 PM
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?

Only have one SSD drive hooked up to the controller on SOC (SATA 0,1) but I also tried switching to the ASMedia ASM1061 controlled ports (SATA 2,3) but error only changed from ahcich0 to ahcich2/3.

Quote from: aj on February 04, 2018, 07:42:10 AM
Had the same issue on a J3455 and this was the only way I could get it to boot back up with 18.1 and get past the timeouts. Give it a try and let me know if it helps


hint.ahci.0.msi = "2"


For the sake of completeness these are the customizations I had to do for this particular board to get a clean boot in 18.1. But I think the first two have been covered in previous posts
machdep.disable_msix_migration = "1"
hint.hpet.0.clock = "0"
hint.ahci.0.msi = "2"

Yay! This worked, copied those to my /boot/loader.conf.local and now it boots. Thanks for the help :)



Glad I could help and hopefully save some frustration; it's proven to be a rather finicky platform with 11.1 kernel.

There is a known issue with ACHI and UEFI mode with FreeBSD. I have complained about it for 2 years and no one listens over there. All other Linux distros work ok.
Some BIOS'es just don't boot. Always stuck on logo. Have to use Legacy mode.
Dell Optiplex 3010,7010, and 9010 are systems I have seen this on.

As a loosely related anecdote: for UEFI we saw the rise of the new vt(4) console which caused a couple of issues in the FreeBSD 10 to 11 transitions because the sc(4) console behaviour suddenly changed. Now nobody wants to work on vt(4) anymore, people rather improve sc(4) again so we are now using a default console driver that receives less maintenance than the thing that got obsoleted. ;)


Cheers,
Franco

April 29, 2018, 01:17:53 PM #19 Last Edit: April 29, 2018, 02:17:30 PM by topuli
i can confirm that setting this variables also works for the supermicro e100-9ap (motherboard a2san-e) with an installed sata m.2 samsung 860 evo! without the settings, the ssd is not recognized by the installer (ssd is visible in the bios)

To recap the steps needed for 18.1 and my hardware:

* boot usb pendrive (amd64_vga image  prepared with dd) - booth a 2GB usb 2 and a 16GB usb 3 key worked
* press escape as soon as the boot logo appears
* cursor blinks beside the OK prompt
* type:
set machdep.disable_msix_migration=1 (press return)
set hint.hpet.0.clock=0 (press return)
set hint.ahci.0.msi=2 (press return) ahci.0 for channel 0 ahci.1 for channel1 or juste set it for both channels
set hint.ahci.1.msi=2 (press return)
* boot (press return)

* at the login prompt login as root with the password you have set during the installation process
choose 8.) shell

* with your favourite create the file /boot/loader.conf.local
you can also put it in the existing /boot/loader.conf, but this file will be overwritten with the next upgrade

* insert the lines :
machdep.disable_msix_migration=1
hint.hpet.0.clock=0
hint.ahci.0.msi=2
hint.ahci.1.msi=2

* write the file and reboot

hope it helps someone

t.

It seems a fix was committed in FreeBSD, hopefully coming to 11.2 and for us to backport easily:

https://github.com/opnsense/core/issues/2344


Cheers,
Franco

May 02, 2018, 10:46:00 PM #21 Last Edit: May 04, 2018, 11:12:08 PM by gbitglenn
I'm having the same problem with 18.1.6 on an Intel NUC NUC6CAYH, using an SSD drive. Upgrading from 17 to 18.1 killed my firewall as a result, good thing I only do upgrades at night :)

Topuli's instructions worked for me as well. That said, being at risk of stating the obvious here, hopefully there will be a fix to the installer coming soon.

NOTE: I was only able to resolve ALL issues - including the HPET hang by issuing all these commands at boot:

If the other instructions in this thread don't work, you also need "set hint.ahcich.0.sata_rev=2"

I'm using an Intel NUC6CAYH and it would only boot by setting the following at the bootloader prompt:

set hint.ahcich.0.sata_rev=2 *This one resolves the HPET hang
set machdep.disable_msix_migration=1
set hint.hpet.0.clock=0
set hint.ahci.0.msi=2
set hint.ahci.1.msi=2


January 04, 2019, 07:17:54 PM #22 Last Edit: January 07, 2019, 02:35:38 PM by topuli
Just in case someone is on the same hardware.
Upgraded my firmware for the supermicro E100-9AP to 1.2.
For some strange reason and to my surprise the system bootet into an sdhci pci X-slot 0  timeout.
After several timeouts the system continous to boot.

#I had to set the following in /boot/device.hints - looks like the file is overwritten by the latest update
So i set the following in /boot/loader.conf.local

hint.sdhci_pci.0.disabled="1"
hint.sdhci_pci.1.disabled="1"
hint.sdhci_pci.2.disabled="1"

t.