Watchguard XTM 5 Series
-
For actually editing the image there are a number of tools that can open and modify the older pre-uefi AMI BIOSes. Including AMIs own proprietary tool amibcp. You'll have to go searching for that if you want to use it.
Bare in mind it's very easy to make an image that doesn't POST and then you need to reflash the chip directly. I did it several times!
https://forum.netgate.com/post/336712Steve
-
@Dufflepod thanks i'm aware about that procedure. I wish to edit the .ROM file not just to push it on the CHIP as is.
@stephenw10 i found the right (i think) 3.51 version of the amibcp tools but it seems to have a partial control on the bios. I think you found some more specific tool... to be able to change Arm/Disarm LED status and to change the LCD text during bios...
If you could help me at least telling me the name of the right software ;)
I know after that i have to do my hard work on my own...
Thanks -
The ARM LED is set by setting the appropriate SIO registers.
The LCD message I changed by hex editing the right module directly. Which is why it had to be the same number of characters. -
thx -
@stephenw10 Hi, I bought two XTM 5, they have same motherboard (MB-7580W v1.0, CK: 9A80 2010-02-03).
They differ by the flash bios: one (I'll call it A) has a label with YK12 1046, the other (I'll call it B) has this label with YJ96 3493.
So I installed pfsense on a CF and I flashed unit A with flashrom. All fine, on boot I see the new string and the red led.
I wasn't able to do the same with unit B, flashrom was unable to find the device to write. So I loaded freedos with afudos in a cf and flashed this way. All fine on boot I see the new string but red led doesn't come up.
I can enter the bios and chenge settings but this led doesn't turn on during boot.
What happens?Ps: I unmounted the lcd assembly and mounted on the unit A and red led works.
-
Hmm, are they the same model xtm5? There were two generation but they were almost identical as far as I know.
Can you you set the LED using WGXepc?Steve
-
@stephenw10 Just tryed, WGXepc64 changes the led. I tryed with green and red.
Any ideas why the bios don't turn on the led? -
I don't. It should, it uses the same set of register changes in the SuperIO chip that WGXepc does.
-
Consider the possibility that the BIOS was previously flashed with a custom image...
-
@t-rexky Before the flashing the bios was the stock one
-
My very new unit at the time (year old display model) did not turn on the red light either.
-
@chpalmer but with the modded bios it should.
Infact the other unit ("same" as this one) turns on the red led.
I can't find the differences between them. Adding that the led works with WXGepc package. -
@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.
-
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.
