Watchguard Firebox M400/M500

stephenw10

Hmm, I wonder what's differet about the 4160 and 4370 then...

With the 4160 it would not boot at all when I disabled hyperthreading as a test.

Scorch95

@stephenw10
Could it be possible that when the bios was written that the 4160 and 4370 didn't exist yet so it was written in a way that just doesn't jive with something in these two processors? Although I don't see why there would be anything truly different other than speed that would cause a conflict.

stephenw10

Mmm, maybe. They are both 2014 vs 2013 for the CPUs that work as expected. The Xanthos bios has updated modules though and still behaves the same....

Steve

kr81

Hello,

i unlocked my m400 with bios from zanthos. Can i use the same bios file for my m500?

stephenw10

You almost certainly can (though I've never tried). As far as I know it's the same board.
Do so at your own risk etc.....

Steve

kr81

Flashed the Bios on M500 successfully

Mookatroid

@Mookatroid said in Watchguard Firebox M400:

Update time ! :)
Xeon E3-1265L v3 arrived.
Installed it and posted without issue.
Dropped a 128GB SATA SSD onto SATA4 interface and tucked it into the front left corner.
Pushed USB installer image to CF card.
Powered up and booted from CF.
Installed to SSD without issue.
Reboot and running pfSense 2.4.4 from SSD without issue
:)

PS ... fan control set manually to 67

Final deployment update :)
My M400 build and bench testing finally wrapped up and I went live with a brand new 120/20 cable ISP with it.
The ISP drop is a single gigabit line to the M400 WAN interface, but I setup a 2xgigabit LACP LAGG between the M400 and my primary switch for PrivateLAN traffic and a 2xgigabit LACP LAGG (with assigned VLAN tagging) for my GuestLAN (both wired and wireless clients).
All is ripping along at a beautiful pace !!
:)

Humble_Servant

@eisenb11 Where you ever able to get the LED lights to Arm/ Disarm? If so what steps did you use to achieve this function? I have a WatchGuard m400 with pfSense installed to a 16GB CF Card and the LAN & Wan's are working however I can not get the LEDs to work as with the XTM 5 Series.

stephenw10

See the post below his question.

https://forum.netgate.com/post/803206

Steve

Humble_Servant

@stephenw10 This does not appear to work either. Screenshot (18).png

stephenw10

Because you are running an ancient version :

[2.5.0-DEVELOPMENT][admin@m400-2.stevew.lan]/root: ./WGXepc64 
Found Firebox M400/500
WGXepc Version 1.4 13/8/2019 stephenw10
WGXepc can accept two arguments:
 -f (CPU fan) will return the current and minimum fan speed or if followed
    by a number in hex, 00-FF, will set it.
 -f2 (System fan) will return the current and minimum fan speed or if followed
    by a number in hex, 00-FF, will set it.
 -l (led) will set the arm/disarm led state to the second argument:
    red, green, red_flash, green_flash, red_flash_fast, green_flash_fast, off
 -b (backlight) will set the lcd backlight to the second argument:
    on or off. Do not use with LCD driver.
 -t (temperature) shows the current CPU temperature reported by the
    SuperIO chip. X-e box only.
Not all functions are supported by all models

Steve

Humble_Servant

Well that explains why it is not working do you have the link to the updated version?

stephenw10

The link from that post should always point to the most recent version.
WGXepc64 binary

Steve

Humble_Servant

Thank you so much! That worked nicely.

zanthos

Hey there,

I created a new BIOS ROM file. Version 6.
I used the image provided by @Mookatroid. Thanks again for that.

Modifications so far:

the latest Intel CPU microcodes
NVMe driver (if anyone should ever want to use that )
some carefully selected default settings
unlocked everything

And as always, I had to mess around with the file size. It was 16m and I had to reduce it to 8m by replacing parts using UEFItool.

Warning: I flashed using SPI. Maybe it will work with software based BIOS updating, such as @stephenw10 has described some posts above.
Warning2: I have not yet tested it any further than 5 minutes runnning time...

Be sure to clear CMOS after updating! J4 pin 4-6 must be shortened.

Download here (m400_v6.7z)

Have fun!

kr81

If someone need this information, it works! Flashed the new bios with afudos. M400 is up and running. But where is the J4. Can you share a picture? I removed the cmos battary for 2 minutes.

Mookatroid

@zanthos said in Watchguard Firebox M400:

Hey there,

I created a new BIOS ROM file. Version 6.
I used the image provided by @Mookatroid. Thanks again for that.

Modifications so far:

the latest Intel CPU microcodes

NVMe driver (if anyone should ever want to use that )

some carefully selected default settings

unlocked everything

And as always, I had to mess around with the file size. It was 16m and I had to reduce it to 8m by replacing parts using UEFItool.

Warning: I flashed using SPI. Maybe it will work with software based BIOS updating, such as @stephenw10 has described some posts above.
Warning2: I have not yet tested it any further than 5 minutes runnning time...

Be sure to clear CMOS after updating! J4 pin 4-6 must be shortened.

Download here (m400_v6.7z)

Have fun!

Woohoo ! :)

Mookatroid

@kr81 said in Watchguard Firebox M400:

If someone need this information, it works! Flashed the new bios with afudos. M400 is up and running. But where is the J4. Can you share a picture? I removed the cmos battary for 2 minutes.

Woohoo x 2 !! LOL
:)

A Former User

@zanthos said in Watchguard Firebox M400:

Warning: I flashed using SPI. Maybe it will work with software based BIOS updating, such as @stephenw10 has described some posts above.
Warning2: I have not yet tested it any further than 5 minutes runnning time...

Everyone updated BIOS via Software?
Which parameter are neccessary?

zanthos

@jayphizzle
According to @stephenw10
(read his post here: console log of BIOS update)

afudos backup.rom /O
afudos m400.rom /B /P /N

The first line creates a backup of your existing rom.
The second one flashes the file "m400.rom"