Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Gigabyte Intros Bay Trail J1800 Based Mini-ITX Board

    Scheduled Pinned Locked Moved Hardware
    35 Posts 15 Posters 20.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      So you have the Asrock Q1900M? And it's failing to boot showing the 'interrupt trigger' error?

      Make sure you're running the most recent BIOS. Try disabling ACPI features in the BIOS.

      Steve

      1 Reply Last reply Reply Quote 0
      • P
        paulsnoop
        last edited by

        Hi Steve, thanks for the reply.

        @stephenw10:

        So you have the Asrock Q1900M? And it's failing to boot showing the 'interrupt trigger' error?

        Yes I have the Q1900M, error is 'bogus interrupt polarity'.

        @stephenw10:

        Make sure you're running the most recent BIOS. Try disabling ACPI features in the BIOS.

        BIOS is the latest (1.30). Here is what I have tried so far:
        CPU
        Disabled Speedstep
        Disabled C States
        Disabled Enhanced Halt (C1E)

        Chipset
        GPU memory to 64mb
        Disabled IGPU
        Disabled Onboard Audio
        Disabled S5 Sleep

        Various submenus
        ACHI mode
        Disabled Intel Smartconnect
        Disabled Serial port
        Disabled Parallel port

        ACPI menu
        Disabled suspend to RAM
        Enabled ACPI HPET table
        Disabled all power on (keyboard, LAN etc)

        Boot menu
        CSM Enabled
        Legacy mode OpROM policy for PXE, Storage, Video

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Hmm, well 3 options I see:
          1: Fix the bios yourself. Might not be that tough but it's risky.
          2: Run a hypervisor and run pfSense as a VM.
          3. Wait for Asrock to fix it. Could be a loooooooong time!

          I did also look into the possibility of overriding the faulty table at boot. You can do that with the DSDT table but I'm not sure about the MADT.
          The actual patch to FreeBSD required to workaround this is small but appears to have gone in only on Jun 23 this year so will not have made it into 10-rel and hence pfSense 2.2.
          https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187966

          Steve

          Edit: typos

          1 Reply Last reply Reply Quote 0
          • P
            paulsnoop
            last edited by

            Thanks for the tips Steve. As VMWare also has problems with this CPU, I suspect I'll end up going with Hyper-V.

            1 Reply Last reply Reply Quote 0
            • N
              notar
              last edited by

              Good morning
              I have a q1900M motherborard with two intel nics pro/100 and, this morning, i have finish the router with pfsense. When i load pfsense and i select 1 in the menu, i have the same problem with ACPI but, when i select 2 in the menu, all work fine and install go fine. I am just a problem with the route. Sorry for my English, i have French.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                So you can boot if you select 'ACPI disabled'?
                You can make that permanent by adding the line in /boot/loader.conf.local. See:
                https://doc.pfsense.org/index.php/Booting_Options#pfSense_2.0

                Steve

                1 Reply Last reply Reply Quote 0
                • N
                  notar
                  last edited by

                  @stephenw10:

                  So you can boot if you select 'ACPI disabled'?
                  You can make that permanent by adding the line /boot/loader.conf.local. See:
                  https://doc.pfsense.org/index.php/Booting_Options#pfSense_2.0

                  Steve

                  Good morning
                  Yes, i can boot with ACPI disable. Thanks for the tip. Notar
                  PS : I can't install amd64, it bug. I have installed the i386

                  1 Reply Last reply Reply Quote 0
                  • N
                    notar
                    last edited by

                    Good morning
                    I have tested the pfsense 2.2 alpha and it work fine with acpi enable. Just the dns seem don't work and it is necessary to put a dns in network config. Why this, i don' know. Notar

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      2.2 is still in alpha. A new DNS forwarder is being used and I guess a bug was introduced while things are being ironed out.

                      https://forum.pfsense.org/index.php?topic=78356.0

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • E
                        elbob
                        last edited by

                        Hi,

                        Long time pfsense user but this is my first post here.

                        I just want to add to this thread by saying I recently bought a J1900-D3V board. I got around to assembling it yesterday and came across the same issues others were having.

                        However I did try a trick that was suggested above that worked. On cold boot I get the Interrupt Trigger error. However If I press the reset switch it will boot up with no issues.

                        I've installed 2.1.4 64bit.

                        Hopefully this workaround will help someone until a more permanent fix is available from Gigabyte or BSD kernel workaround.

                        I forgot to mention that I'm using the F3 version of the BIOS and I also disabled all the UFI stuff so everything in the Advanced –> CSM configuration section of the BIOS is set to Legacy.

                        1 Reply Last reply Reply Quote 0
                        • M
                          molle
                          last edited by

                          Here is a patch for FreeBSD 8.3 64 Bit, its just a backport of the patch from the bugreport.

                          Somehow i can't login into the bugtracker, just posting it here for interested people.

                          https://gist.github.com/cHolzberger/419d214d3c16ae2a8f25

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Interesting. Is it possible to add that as a module or does it require a complete kernel rebuild?

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • M
                              molle
                              last edited by

                              it requires a new kernel to be build.
                              wont work that great with updates…

                              i just sent the patch to the dev@ mailinglist. perhaps it gets included in next stable?

                              1 Reply Last reply Reply Quote 0
                              • A
                                AveryFreeman
                                last edited by

                                I have a pfSense build I made with a Lenovo H100s motherboard (j1800) that I bought off ebay for $15 and a Pro 1000 VT quad NIC, and a couple Intel SLC SSDs in a gmirror, running 2.3.3_1  bare metal.

                                I can confirm that the bay trail processor works great with 2.3.3.  Iperf over 900mbs across local network, rarely goes above 30% CPU with OpenVPN tunnel running concurrently.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post
                                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.