J1900 4xLAN NanoPC

[gwaitsi]

Hey guys, i am new here. Not really if this can solve my problem.

I have a Chinese NanoPC fanless PC with AMI AptioV BIOS.

I am using it to run pfsense (freebsd).

I get the following error message during boot,

Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 128/32 (20171214/tbfadt-748)

I see in FreeBSD it is possible to override the DSDT from bios, so can minimise the risk being a newbie here.

acpi_dsdt_load="YES"

acpi_dsdt_name="/boot/DSDT.aml"

i attached a copy of the BIOS image. my questions are;

a) is the error solvable in the DSDT?

b) can someone help me with generating the fixed DSDT.aml that i can try to use with the overide

much appreciate the help.

Added in 45 minutes 32 seconds:

i've managed to use freebsd to create the asl file attached.

grateful for help in making the necessary patch to source.

AMI_APTIOV_Q1XXG4_07x64_UEFI2_4-PI1_3.zip

DSDT.asl.zip

[MaLd0n]

[ref]gwaitsi[/ref], DSDT.aml.zip

post one photo with error

[gwaitsi]

The first easyfix should be removing the acpi_button1 (sleep) - there is none on my machine.

I am not trying to convert to mac, i am trying to fix the generic ACPI issues showing up in freebsd.

I have the following errors in my freebsd boot up.

1)

ACPI APIC Table:

WARNING: L1 data cache covers less APIC IDs than a core

0 < 1

2)

Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 128/32 (20171214/tbfadt-748)

ioapic0 irqs 0-86 on motherboard

SMP: AP CPU #2 Launched!

SMP: AP CPU #1 Launched!

SMP: AP CPU #3 Launched!

3)

acpi0: on motherboard

acpi0: Power Button (fixed)

unknown: I/O range not supported

4)

atrtc0: port 0x70-0x77 on acpi0

atrtc0: Warning: Couldn't map I/O.

atrtc0: registered as a time-of-day clock, resolution 1.000000s

5)

pcib0: port 0xcf8-0xcff on acpi0

pcib0: _OSC returned error 0x10

pci0: on pcib0

Added in 8 minutes 24 seconds:

p.s. if i try to pass the acpidump file back to iasl, i get the error:

iASL warning: there was 1 external control method found during disassembly, but only 0 were resolved (1 unresolved). Additional ACPI tables may be required to properly disassemble the code. This resulting disassembler output file may not compile because the disassembler did not know how many arguments to assign to the unresolved methods. Note: SSDTs can be dynamically loaded at runtime and may or may not be available via host OS