Watchguard XTM 5 Series
-
@valepe69 said in Watchguard XTM 5 Series:
@chpalmer but with the modded bios it should.
Infact the other unit ("same" as this one) turns on the red ledYes. it did. :) Watchguard must have made changes at some point.. Ive had several stock units (which I put pfsense on for friends) come through and noted the earlier ones had the red LED whereas mine and a later unit did not.
I always change the firmware on them when I get them.
-
stephenw10 Netgate Administratorlast edited by stephenw10 Nov 20, 2020, 5:38 PM Nov 20, 2020, 5:38 PM
Hmm, that my bios or t-rexky's? Or am I misremembering?
There are a number of things required to enable the red arm led. I'm pretty sure I set all of them....
If you run WGXepc at the command line after rebooting does it show it's having to set the GPIO pins?
https://github.com/stephenw10/WGXepc/blob/master/WGXepc.c#L1398The BIOS has to set those up for the LED to work so boxes running a modded BIOS should never show those messages.
Steve
-
@stephenw10 I used your one. When I run WGXepc I don't remeber messages. Only the the led operation.
-
Hmm, well I would try rebooting it and running WGXepc from the CLI again. If you do see one or more of those it will show the BIOS is not setting up the SIO device as expected.
Steve
-
@stephenw10 turning on the led WGXepc64 shows these lines:
Found Firebox XTM5
Enabling GPIO2
Setting GPIO2 pins as outputTurning the led off It shows only:
Found Firebox XTM5 -
OK, so it only shows that the first time it is run. It only needs to setup the GPIO pin once.
It the BIOS was setting it up correctly it wouldn't have to so you would never see those messages. You could confirm that on the other box.
So we can say that, for some reason, the BIOS is not running the SIO table on that box.Unfortunately I have no idea why that might be.
Steve
-
Anyone upgraded to pfsense 2.5 yet? Any issues with compatibility for WGXepc64 or other mods mentioned in this thread?
-
Did it last night on mine.
No major problems, except for issues with Core temp and the IPV6 Gateway bug.
I have swapped the processor for a Xeon and coretemp gets the wrong values. I fixed this before but the Kernel is now based on version 12 instead of 11 so I have had to recompile the module.
For those of you that are using Xeons, new coretemp module is attached here.
Upload coretemp2.ko to /boot/modules/coretemp2.ko
Chmod 755 coretemp2.ko
In your /boot/loader.conf.local add the following:
coretemp2_load="YES"
Then reboot.
You should now have a correct temperature reading.
-
Yeah, works fine here. No significant issues seen so far, I've been running 2.5 snapshots on it for months.
Including the coretemp values with a Xeon:Name xtm5.stevew.lan System pfSense Netgate Device ID: e436ea6ef44065f7f646 BIOS Vendor: American Megatrends Inc. Version: 080015 Release Date: Wed Feb 3 2010 Version 2.5.0-RELEASE (amd64) built on Tue Feb 16 08:56:29 EST 2021 FreeBSD 12.2-STABLE The system is on the latest version. Version information updated at Sun Feb 21 14:34:55 GMT 2021 CPU Type Intel(R) Xeon(R) CPU L3110 @ 3.00GHz Current: 2000 MHz, Max: 3000 MHz 2 CPUs: 1 package(s) x 2 core(s) AES-NI CPU Crypto: NoI'm guessing you're using a Xeon with a pin-mod?
Steve
-
Yes it is a L5420 771 to 775 conversion.
Core temp thinks it is a core2duo. Both processors have the same ID.
-
Great, ill plan for an upgrade so. Im using the box as a UniFi controller also. If there is no compatibility issues there, ill upgrade. Thanks!
-
Ah, well running unifi on there is probably completely untested. However you have installed that would need to be updated for FreeBSD 12. Really it's much better not to do that anyway.
Steve
-
I know this thread / topic is quite but I am just now getting into "flashing" an XTM 525 that I have had for years and didn't know where to begin nor really had the time. To be completely transparent, I am above average in knowledge in IT networking etc, but am definitely not up there with some of you guys. I encountered an issue while flashing and have no idea what it could be. The box powers on and that's pretty much it. Fans run like hell, full speed, never come down. The lCD is backlit and that is all. I was following a tutorial, I have actually seen it referenced here. Here is the link.
https://alpha-labs.net/2017/08/pfsense-on-watchguard/
I removed the CF Card in order to boot from the SSD's as instructed but the fans and the lcd are all I get. No serial output, nothing.
Any insight would be greatly appreciated.
-
You should see some output on the console even if there is no boot drive installed.
It should also beep and the fans should slow down when it POSTS.
If you don't see any of that it's probably failing to POST which is usually a hardware issue. Have you added any hardware components?Steve
-
Thanks for the quick reply. Yes, I swapped the cpu for an Intel E5700, put in 2 new ram modules (2gb each, non ecc), and was going to boot from 2 ssd's that have pfsense installed by another pc. Tried to boot from the ssd's and that was the 1st occurrence of the issue. I put all of the original hardware back in as well to no avail. I also put the CF card in a reader and it appeared to have been corrupted.
-
Hmm, try resetting the CMOS. Just pull the battery if the jumper is not obvious.
I assume it did boot correctly before you swapped in the CPU and RAM?
The CF card still had the WG OS on it?
The E8400 is better CPU choice IMO. As long as your RAM will run at 1333. 3x the L2 cache of the Pentium E5700. Or it will run a Core2Quad if you need it.
Steve
-
Sorry it's been so long. I abandoned the project for a little bit due to work and life circumstances. I am starting to think I followed a botched tutorial or somehow missed something and botched it myself. I have since acquired another 5 series and have it running pfsense without any bios mods. On the previous box, discussed in my last comm, I had installed 2 ssd's, updated RAM, and the E3400 CPU. When I traced back everything I did, nothing stood out as a root cause of this issue. I have tested the box with another power supply and get the same reponse. Fans sound like they're going to lift off, all leds near the fans and cpu are illuminated. Is it possible for BIOS to have been wiped somehow? I am willing to purchase the appropriate kit/s and attempt to flash the bios via spi.
Regards
-
It's possible the BIOS was damaged but unlikely.
It's probably cheaper to get a different XTM5 than SPI flash interface so it depends why you're doing this. -
Just a learning experience more than anything really. I got the 1st box for free from a previous employer when they upgraded their network. IT guy told me to "Have at it" with the contents of the big pallet boxes of various equipment they were sending off to the recycling company. At the time I knew what it was but I didn't know it's potential and how sought after of a device it may have been more so at the time (2015). They took really good care of their equipment. Not a scratch, dent, or ding. I must be mistaken on what is required equipment wise to flash it. I take it the aardvark and not the usb with the battery jumper looking clip lol.
-
@bryanjlaz said in Watchguard XTM 5 Series:
Just a learning experience more than anything really. I got the 1st box for free from a previous employer when they upgraded their network. IT guy told me to "Have at it" with the contents of the big pallet boxes of various equipment they were sending off to the recycling company. At the time I knew what it was but I didn't know it's potential and how sought after of a device it may have been more so at the time (2015). They took really good care of their equipment. Not a scratch, dent, or ding. I must be mistaken on what is required equipment wise to flash it. I take it the aardvark and not the usb with the battery jumper looking clip lol.
Forgot to add. The fact that it was such a good find for free, I hate to see it go to waste.