Watchguard Firebox M400/M500
-
I have an M400 which I have tried to flash with Zanthos' BIOS. Have used a CH341A SPI Flash Reader and ASprogammer. When I start up the Wathguard it is on for 3-4 seconds and then it turns off again. Is there something I did wrong or has the flash itself failed? It said that everything was successful.
-
Hmm, that's not good. Could be either with those symptoms.
You might try re-flashing it. Or restoring the old file if you backed it up.
-
@stephenw10 Tried to reflash and restore back to the original BIOS without success. Have also tried another PSU, but with the same result.
-
Hmm, not sure what else to suggest. Had you swapped out any hardware before that?
-
@stephenw10 Have not replaced any hardware. It should be said that I tried a long time ago to flash the bios with software flash with Zanthos' version and that's when it failed. Finally ordered an SPI reader and thought it would work. I extracted the original BIOS from an identical M400 that I have that works. It might not work?
-
I would expect it to work. It's possible you had a hardware failure that happened to coincide with the original BIOS flash attempt of course. Seems pretty unlikely but....
-
@stephenw10 Tried to find a detailed overview of the motherboard, but can't find it anywhere. Do you know where I can possibly find it?
-
The Lanner FW-7585 manual is the closest you're likely to find. It's not exactly the same but close enough.
-
@stephenw10 Thank you very much! Will have to see if I can get the M400 to stay on.
-
@stephenw10 Hello. I tried the link you shared for the fan control software, but it's doesn't work anymore.
I went to git and downloaded the .c code, but it won't run. I assume I need to compile it which I'm unfamiliar with how to do.
When I do try to run it even as root, I get permission denied.
This is on an M400 with Stock bios.
Thanks -
Which link? I put a compiled binary up on github that should work, here.
Otherwise, yes, you'd have to compile it in FreeBSD and copy it to pfSense.
Steve
-
@stephenw10 said in Watchguard Firebox M400/M500:
Turns out it was relatively easy to add the fan control to WGXepc as it's pretty much identical to the Mx70 boxes. Though I managed to break it several times by not setting enough things and ending up with a negative temperature/speed ramp.
So find the updated code: https://github.com/stephenw10/WGXepc/blob/master/WGXepc.c
And a compiled binary here for those willing to trust it.
This is the file I'm referring to.
-
So fetch it onto your firewall, change the permissions so it's executable, run it:
[2.7.0-DEVELOPMENT][admin@m400-2.stevew.lan]/root: fetch https://github.com/stephenw10/WGXepc/raw/master/WGXepc64 WGXepc64 26 kB 3625 kBps 00s [2.7.0-DEVELOPMENT][admin@m400-2.stevew.lan]/root: chmod +x WGXepc64 [2.7.0-DEVELOPMENT][admin@m400-2.stevew.lan]/root: ./WGXepc64 Found Firebox M400/500 WGXepc Version 1.6_1 22/11/2020 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 -
@stephenw10 Just changing the permissions of the file resolved the issue. I set the CPU fan to 5 instead of 14 as you had done, and it initially lowered the fan speed, but it's been ramping up and down even though the interface temp values are reporting that it's only getting to 35C. Is this normal?
-
Yes the actual fan speed should vary with temperature. The value you set there is the minimum fan speed, the actual speed is determined by the minimum plus a value proportional to the CPU temp above a minimum temp value.
-
I'm running into the weirdest issue. I've been super happy with the M400 that I upgraded the BIOS and installed 2.6 on so I decided to do the same for my backup M400. Both M400s have i3-4130T CPUs.
Updated the BIOS, used Rufus to install the 2.6 image to CF... but I'm stuck in the installer where it partitions the CF.
I selected EUFI, then GPT... but I keep getting an error. "File exists. geom 'ada0'". I can't get past this to do the install.
Would you happen to have any pointers on how to get past this?
-
You can't install to the CF card if you wrote the installer image to the CF card and booted that.
You need to boot from USB and install to CF. Or boot from CF and install to SSD etc.
-
@stephenw10 That makes total sense, I’ll try that later… but somehow it worked when I did it on the first machine! Twilight Zone! Ha ha
-
@stephenw10 Wow, I'm just having terrible luck this go-around.
I used Rufus to put the 2.6 image on a thumb drive. Booted off the thumb drive. Had it to install to ad0. When it was ready to reboot, I shut down and removed the thumb drive. Power back up and then get an error message that it can't find a proper boot device. It appears that it didn't format the CF to be bootable. Did I miss a step in the install somewhere?
-
@eisenb11 I figured it out. I went back into the bios and looked under boot and it had a weird selection for the boot order. I changed it and it can now boot correctly.
