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.
    • D
      Darkk
      last edited by

      Another new board about to be released:

      Gigabyte Announces Quad-Core J1900-Based Motherboard

      http://www.tomshardware.com/news/gigabyte-j1900-motherboard,26067.html

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

        So you would probably have to wait until pfSense 2.2 for these boards to work?

        1 Reply Last reply Reply Quote 0
        • B
          bryan.paradis
          last edited by

          @midacts:

          So you would probably have to wait until pfSense 2.2 for these boards to work?

          Could have problems if there aren't any usb 2.0 ports and depending on the chipset and network.

          1 Reply Last reply Reply Quote 0
          • L
            luismartins351
            last edited by

            Motherboard  with onboard Realtek NIC are very bad…
            Pfsense 2.1 and also 2.1.1  is not compatible with Gigabyte Motherboard with J1800/1900 because this motherboards have NIC Realtek 8111G.
            At this moment also Intel Nic I210 not working with Psense 2.1.1
            Bst
            Luis Martins

            1 Reply Last reply Reply Quote 0
            • ?
              Guest
              last edited by

              @luismartins351:

              Motherboard  with onboard Realtek NIC are very bad…

              Well, they're not "very bad", but the performance of the Realtek NICs isn't good.

              @luismartins351:

              Pfsense 2.1 and also 2.1.1  is not compatible with Gigabyte Motherboard with J1800/1900 because this motherboards have NIC Realtek 8111G.

              Some variants of the RT 8111 do work.  I don't know about the 'G' version though.

              @luismartins351:

              At this moment also Intel Nic I210 not working with Psense 2.1.1

              Really?  It should.

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

                The new igb driver was backed out on 19th Feb. The driver in 2.1.1 snapshots currently is the same as that which shipped in 2.1 release which doesn't support the i210. As far as I'm aware at least.  ;)
                https://forum.pfsense.org/index.php/topic,72763.msg398485.html#msg398485

                Steve

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

                  So that Gigabyte Quad-Core J1900 motherboard may work with pfsense 2.1.1 and maybe 2.1?

                  Will its Realtek NICs be a big loss in performance compared to an Intel NIC?

                  1 Reply Last reply Reply Quote 0
                  • T
                    Tikimotel
                    last edited by

                    What I like about the GigaByte J1900 board is that the PCI slot isn't blocked by jumpers or big capacitors.
                    However you might not be able to use the mini-pci-e slot…
                    I can install my PCI-X based dual intel NIC without a hitch and disable the onboard realtek nics.

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

                      Supermicro already has a j1900 board out, and it comes with dual Intel® i210AT NICs:
                      http://www.supermicro.com/products/motherboard/celeron/X10/X10SBA-L.cfm

                      Would that board work out of the box with pfsense 2.1/2.1.1, even if you did have to use a PCI NIC to get it to work? or even any of the J1800/J1900 motherboards for that matter

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tikimotel
                        last edited by

                        http://www.asrock.com/ipc/overview.asp?Model=IMB-150

                        Coming mid-April  ::)

                        They describe the realtek NIC as :
                        RTL8111G (in the PDF data diagram)
                        or
                        RTL8111E-VL (specs)

                        1 Reply Last reply Reply Quote 0
                        • K
                          kenmasterson
                          last edited by

                          I built a J1900-based pfSense box, only to find that pfSense has issue with Bay Trail processors that prevents it from booting properly: https://redmine.pfsense.org/issues/3678

                          I hope that this will save someone else from having the same trouble, or encourage the issue to get resolved.

                          1 Reply Last reply Reply Quote 0
                          • S
                            sdl007
                            last edited by

                            Hi Everyone

                            I just got a Gigabyte J1900N-D3V motherboard and booted off my trusty pfSense memory stick. Only to be presented with the dreaded "Bogus Interrupt Trigger Mode" message.
                            After looking around the interweb and trying different things, I found this to work for me.
                            Update the bios to F3 (came shipped with F2)
                            I re-imaged my trusty pfSense memory stick with "pfSense-memstick-2.1.3-RELEASE-amd64-20140501-1552.img" just to be sure.

                            Installed first time, no errors.

                            Here is the strange bit. If I do a 5) Reboot system, it boots back every time.
                            If I do a 6) Halt system, she will error out with this error once I hit the power button to start up again.
                            panic: Bogus Interrupt Polarity
                            Now at this stage, I hit the reset button on the box (as opposed to powering off) and it will boot.
                            Just seems to be an issue when starting the box from a fully shutdown state.

                            weird or what? 2 parts of annoying I might add.

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

                              As linked to in kenmasterson's bug report this is a BIOS bug in the form of a bad ACPI table, I guess Gigabyte didn't fix all the problems with F3. Get on them with your error, you never know they might actually fix it in F4.  ;)

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • K
                                kenmasterson
                                last edited by

                                @stephenw10:

                                As linked to in kenmasterson's bug report this is a BIOS bug in the form of a bad ACPI table, I guess Gigabyte didn't fix all the problems with F3. Get on them with your error, you never know they might actually fix it in F4.  ;)

                                Steve

                                Let's hope so. I'm reporting the issue to Asrock, too.

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

                                  Better than not booting at all!  ;)
                                  You may be able to prevent the hang at halt problem by disabling suspend/low sleep states in the BIOS.

                                  Steve

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

                                    @kenmasterson:

                                    @stephenw10:

                                    As linked to in kenmasterson's bug report this is a BIOS bug in the form of a bad ACPI table, I guess Gigabyte didn't fix all the problems with F3. Get on them with your error, you never know they might actually fix it in F4.  ;)

                                    Steve

                                    Let's hope so. I'm reporting the issue to Asrock, too.

                                    I have done the same for my Q1900M, although I'm not expecting too much from them.

                                    Does anyone have any advice, is there some BIOS settings I could try?

                                    1 Reply Last reply Reply Quote 0
                                    • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.