PfSense with Gigabyte GA-J1900N-D3V
-
Good morning
There are 2 new motherboard Asrock q1900. One is itx and other is micro atx. As somebody tried these boards with pfsense ? Thanks -
@midacts
careful, the gigabyte board in the op's post only has a pci slot and you linked a pcie x4 nicI am also looking into this board for a pfsense build and I drawn to it due to its extremely low power consumption. I remember reading reviews on newegg for the asrock variants of the intel j1900 and a few users were saying to enable some boot option to support booting nix/bsd type operating systems. But for some reason all of newegg's reviews on the asrock j1900 boards are now removed??? So I took a look through asrock's manual in search for the boot option. I'm pretty sure what the newegg reviewers were saying was to disable Compability Support Module in order to boot nix/bsd OS's. Maybe the gigabyte boards have this boot option also, so if someone who already purchased one if these boards could test it out I would greatly appreciate it.
Also to those who purchased the gigabyte board, could you please post what memory you are using, more specifically the voltage that the sodimm's run at.
Thank You
-
Thanks wait and see !
-
Also to those who purchased the gigabyte board, could you please post what memory you are using, more specifically the voltage that the sodimm's run at.
Thank You
It requires DDR3 SODIMM's that run at 1.35v.
-
That will be Celsius almost certainly.
Steve
Edit: Don't know what I did here, this post is totally out of context. ::)
-
I bought this board (only found out about this thread afterwards) last Monday, together with 2 x 4GB Crucial Ballistix @ 1.35V and a 60GB Kingston (SSDNow). After having upgraded to F2 (which was indeed a bit of a pain) I got 2.2-ALPHA running without further issues. I followed the guides elsewhere on the forum and enabled CSM as well as disabling C-State. I've also enabled TRIM support by rebooting into single-user mode and running 'tunefs -t enable /'.
As mentioned, running smooth now and not seeing any issues (yet). Will keep it running for another night before replacing my old firewall though (m0n0wall on an ancient Nokia IP110), just to be sure :)
Just thought I'd share some positive news, hope this helps somebody!
-
awesome dwaler! keep up posted.
I am really liking this board. I'm itching to put it in a m-350 mini-itx case with a pico psu and have a super small form factor pfsense box.
-
Hey Everyone, this is my first post so I say hello!
I bought this board as soon as I figured out I wanted to build a pfsense box, without looking into all the troubles it had. I experienced so many problems trying to get it installed, I just left it alone for a week because I had lost all patience.
I tried 32 and 64 bit versions of the live usb, then live dvd, always to encounter either intermittent usb failure during install, complete lack of usb function at all, kernel panics, would get to install on hard drive, then when booted there were geometry errors. I tried many times to install windows 8.1 so I could update to bios version F2 but always failed miserably. So still on Bios F1.
I downloaded version 2.1.3 , then went into bios and set my cpu to 1 core. loaded the dvd and BOOM, it decided that it would boot and then properly install for me, much to my disbelief. I then rebooted and switched back to all 4 cpu cores and It has now been running stable for 3 days with an openvpn tunnel and zero errors!
I hope this helps some of you with all the problems you are having with this board!
-
Hey Everyone, this is my first post so I say hello!
I bought this board as soon as I figured out I wanted to build a pfsense box, without looking into all the troubles it had. I experienced so many problems trying to get it installed, I just left it alone for a week because I had lost all patience.
I tried 32 and 64 bit versions of the live usb, then live dvd, always to encounter either intermittent usb failure during install, complete lack of usb function at all, kernel panics, would get to install on hard drive, then when booted there were geometry errors. I tried many times to install windows 8.1 so I could update to bios version F2 but always failed miserably. So still on Bios F1.
I downloaded version 2.1.3 , then went into bios and set my cpu to 1 core. loaded the dvd and BOOM, it decided that it would boot and then properly install for me, much to my disbelief. I then rebooted and switched back to all 4 cpu cores and It has now been running stable for 3 days with an openvpn tunnel and zero errors!
I hope this helps some of you with all the problems you are having with this board!
Where in the bios do you see the option to disable the cores? I'm on the F2 bios so not sure if that makes a difference. I am having no luck getting this board to boot 2.1.3.
-
I just wanted to add that I'm running the GA-C1037UN-EU board earlier mentioned in this thread.
I'm running it with an additional NIC in the PCI port, so have three NICs all in all. I also use vlans and everything is working great.
I run it of an SSD and everything is very low temperature. I have a slow running 120mm case fan but I think it is not needed.
It's been running it 24/7 since last year, so about 6-7 months now. Highly recommended. ;D ;D ;D
The only drawback is that it's PCI and not PCIe if you want to add a dual or quad network card. A regular pci slot can handle one gigabit without trouble. But perhaps it's academic anyway since there are usually data bottlenecks elsewhere in the chipset and the cpu.
-
First post, so… hello :D
This mb work well with the last release of pfsense? And what about the realtek lan?
Thanks for the help -
Does it work better with Bios F3 version?
-
Looks like it should be:
@http://www.silentpcreview.com/forums/viewtopic.php?p=585025&sid=956a29819e12154d85832fd26f45d365#p585025:I have to say that the F3C BIOS seems quite stable, it provides a lot of previously missing options (working PXE legacy boot, USB support, advanced options)
Steve
-
did pfsense support the onboard nic.
gigabyte website did not state the model of the nic chip. (i think it may be 8111G??? not sure :'() -
@pete.s.:
I just wanted to add that I'm running the GA-C1037UN-EU board earlier mentioned in this thread.
I'm running it with an additional NIC in the PCI port, so have three NICs all in all. I also use vlans and everything is working great.
I run it of an SSD and everything is very low temperature. I have a slow running 120mm case fan but I think it is not needed.
It's been running it 24/7 since last year, so about 6-7 months now. Highly recommended. ;D ;D ;D
The only drawback is that it's PCI and not PCIe if you want to add a dual or quad network card. A regular pci slot can handle one gigabit without trouble. But perhaps it's academic anyway since there are usually data bottlenecks elsewhere in the chipset and the cpu.
I've bought the GA-C1037UN-EU under the impression that it would be no problem, but now the NIC's don't get an IP from the DHCP server. Do I have to copy the if_re.ko from topics in this forum (see https://forum.pfsense.org/index.php?topic=65355.30) ?
uname0u gives FreeBSD 8.3-RELEASE-p16
How did you install this c1037un board?
-
If you've assigned the interface as type DHCP then it is appearing correctly, the driver is not the problem.
What have you done so far?Steve
-
If you've assigned the interface as type DHCP then it is appearing correctly, the driver is not the problem.
What have you done so far?Steve
I've installed pfSense, assigned the re0 to the WAN interface (DHCP) an plugged in the cable modem (after properly powercycling it). Alas…no IP. Then I've connected the WAN to my old pfSense LAN and I can see in the old pfSense log that it is indeed giving out a DHCP ip, but all the c1037un does is sending more requests for an IP.
Then I've changed the etc.conf with the following :synchronous_dhclient="YES". Still no IP...
Then I've loaded the if_re.ko from various posts in this forum (https://forum.pfsense.org/index.php?topic=65355.45) to /boot/kernel and /boot/modules. Also added if_re_load="YES" to /boot/loader.conf.local.
Still no IP :-X
From what I gather Realtek changes it hardware sometimes without changing the model number, thus it might work for one person but not for the next >:(
I'm at a loss now, with the Ubuntu live CD the nics work flawlessly and get an IP. Maybe I have to virtualize pfSense just to get it working?
-
Hmm, well that's odd behaviour. You could well be right, Realtek do like to change hardware.
What does pciconf list the NIC as? The PCI revision usually indicates what the NIC type is.Steve
-
Hmm, well that's odd behaviour. You could well be right, Realtek do like to change hardware.
What does pciconf list the NIC as? The PCI revision usually indicates what the NIC type is.Steve
Due to the problems with the nic on bare-metal pfSense I've decided to use esxi and run pfSense on top of that. As it turns out this is something I should've done right from the beginning, it works perfect.
-
Any new information regarding this board? Does the NIC's works out of the box?
