Watchguard XTM 5 Series
-
Almost everything anyone has tried is in this thread somewhere. I think it's possible to run 8G though I've not tried it myself and 4G is fine for almost everything.
The C2D E8400 is about the best performance for the price IMO. I did run that for a while with zero issues.Steve
-
Man, it's been a long time since I've been here. Amazed to see this thread is still going. I started re-reading the whole thread last night and just finished up. Looks like there's some more tinkering that could be done with the BIOS on these things... I'll have to check and see if I still have all the tools from before.
@stephenw10 I can confirm that it will run with 8GB of RAM as I just installed 2x4GB sticks that I had sitting on a shelf in it today. Specifically, they are a pair of Elpida 4GB 2Rx8 PC2-6400U-666 sticks that apparently came out of an HP machine. I believe the memory part number is EBE41UF8ABFA-8G-E 0921AXE0681 as both of those are written above the barcode and are the same on both sticks. The HP P/N is 492275-888 which is much easier to figure out. lol
From my understanding though, any "low density" 4GB DDR2 800 unbuffered RAM should work. Amazed at what the prices on that are still commanding. I thought I was going to have a bunch of extra RAM (that runs extra cool and is so much more awesome because they have that hip heat spreader on them... lol) that I could possibly look at unloading... But alas! Though they're sticks of 4GB DDR 2 from an HP Intel server, I only took a quick glance at it. It's PC2-5300F according to the sticker on the heat spreader. This has a slightly different placement of the pins and doesn't fit on the board. (Think the F might be one of the ECC designations, I can't remember and it's been a while since I pulled it out of whatever servers it was that they were in. But as they were servers, it most likely was ECC, though they were servers I saved from being sent to the recycler from another school district or local college. Or it might have been one of the ones we got from said recycler.) Would have saved me a bunch of trouble if I'd have just looked at it a little closer before bringing home a dozen or so sticks. lol
Having that serial port permanently installed on the back is rather handy when booting up into the FreeDOS image that I apparently still have on this CF card. Plugged it into the serial port on my PC and used a USB-to-DB9 with a "Cisco" (it's actually from Extreme, but they use the same Cisco rollover pinout) cable to the console port. 2 copies of KiTTY running so I don't have to switch settings between BIOS and FreeDOS. I think I might get/put together a VGA cable as well just to do it. Not sure if I'd want to put it on the back next to the serial port or maybe try to be very delicate and get it mounted in the front so I'd have the USB ports right next to it for a keyboard/KVM... Never thought I'd be looking at doing more hardware modding with this old box... lol
-
@stephenw10 do you have a copy of WGXepc64 that will work with 2.7?
-
The current version works:
[2.7.0-DEVELOPMENT][root@xtm5.stevew.lan]/root: ./WGXepc64 Found Firebox XTM5 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 modelsYou might also be interested in the attached script that I've had for a while but never got around to adding into WGXepc.
I'm seeing some odd instability in this box in 2.7a though. It is pretty old at this point I guess.
Steve
-
I actually lost my hard drive in my XTM5 that I was using at a remote site when I brought it back here and tried to load 2.7 on it.. Put a new drive in it and all is good.
When I try to execute commands for WGXepc64 I get "sh: /conf/WGXepc64: Permission denied"
Is there a different way these days to allow permissions?
-
How are you setting them? I usually:
chmod 0755 WGXepc64 -
@stephenw10 said in Watchguard XTM 5 Series:
How are you setting them? I usually:
chmod 0755 WGXepc64I actually referred back to https://forum.netgate.com/post/867995 which has always worked before..
-
Mmm, that should work. I have in /root but should be fine in /conf.
Unless.... something in ZFS. Are you running ZFS?
Edit: Yup. Hmm
[2.7.0-DEVELOPMENT][root@xtm5.stevew.lan]/conf: ls -ls total 165 9 drwxr-xr-x 2 root wheel 7 Apr 26 23:54 RAM_Disk_Store 17 -rwxr-xr-x 1 root wheel 27393 Apr 27 00:01 WGXepc64 9 drwxr-xr-x 2 root wheel 33 Apr 26 23:56 backup 101 -rw-r--r-- 1 root wheel 174381 Apr 26 23:56 config.xml 1 -rw-r--r-- 1 root wheel 14 Apr 26 22:42 copynotice_version 5 -rw-r--r-- 1 root wheel 5471 Apr 26 22:00 copyright 1 -rw-r--r-- 1 root wheel 6 Apr 26 07:47 enableserial_force 9 -rw-r--r-- 1 root wheel 15992 Apr 27 00:00 rules.debug.old 17 -rw-r--r-- 1 root wheel 49419 Apr 26 22:46 upgrade_log.latest.txt 1 -rw-r--r-- 1 root wheel 26 Apr 26 23:57 upgrade_log.txt [2.7.0-DEVELOPMENT][root@xtm5.stevew.lan]/conf: ./WGXepc64 ./WGXepc64: Permission denied. -
/conf is mounted noexec:
[2.7.0-DEVELOPMENT][root@xtm5.stevew.lan]/conf: mount -p pfSense/ROOT/default / zfs rw,noatime,nfsv4acls 0 0 devfs /dev devfs rw 0 0 pfSense/cf /cf zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/home /home zfs rw,noatime,nfsv4acls 0 0 pfSense/var /var zfs rw,noatime,nfsv4acls 0 0 pfSense /pfSense zfs rw,noatime,nfsv4acls 0 0 pfSense/cf/conf /cf/conf zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/var/log /var/log zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/var/empty /var/empty zfs rw,noatime,nfsv4acls 0 0 pfSense/var/cache /var/cache zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 pfSense/var/tmp /var/tmp zfs rw,nosuid,noatime,nfsv4acls 0 0 pfSense/reservation /pfSense/reservation zfs rw,noatime,nfsv4acls 0 0 pfSense/var/db /var/db zfs rw,noexec,nosuid,noatime,nfsv4acls 0 0 tmpfs /tmp tmpfs rw 0 0 tmpfs /var tmpfs rw 0 0 devfs /var/dhcpd/dev devfs rw 0 0 devfs /var/etc/named/dev devfs rw 0 0I assume it works for you in /root?
-
-rwxr-xr-x 1 root wheel 27K Nov 22 2020 WGXepc64
-
I shall try that.
-
Yes that worked. Thanks @stephenw10! I am going to edit my post with the instructions a bit.
-
Wowsers, this is some forum! :)
Hi, just picked up an XTM 5 510 (7580 v0.3) am trying to flash the BIOS I have read this entire thread and seen I am not alone with the following:
flashrom v1.2 on FreeBSD 13.0-STABLE (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 1ns). Found chipset "Intel ICH7/ICH7R". Enabling flash write... OK. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.Sadly I don't see any resolutions, did anyone come up with anything?
Not really sure what detail is best to provide here, maybe this?
# dmidecode 3.3 Scanning /dev/mem for entry point. SMBIOS 2.5 present. 44 structures occupying 2148 bytes. Table at 0x000FBDC0. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 080015 Release Date: 02/03/2010 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Targeted content distribution is supported BIOS Revision: 8.15All assistance very gratefully received!
-
Hmm, never seen it fail here. Never tried using 1.3 either though:
[2.7.0-DEVELOPMENT][root@xtm5.stevew.lan]/root: flashrom --programmer internal flashrom v1.2 on FreeBSD 12.3-STABLE (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 1ns). Found chipset "Intel ICH7/ICH7R". Enabling flash write... OK. Found Micron/Numonyx/ST flash chip "M25P80" (1024 kB, SPI) mapped at physical address 0x00000000fff00000. No operations were specified.Did you try 1.2 first? Can you see what the actual flash chip you have is?
Steve
-
Hi! Thanks so much for getting back to me, amazed you have not had enough of this thread!
[2.6.0-RELEASE][root@pfSense.home.arpa]/tmp: flashrom -r rom.orig -p internal flashrom v1.2 on FreeBSD 12.3-STABLE (amd64) flashrom is free software, get the source code at https://flashrom.org Using clock_gettime for delay loops (clk_id: 4, resolution: 1ns). Found chipset "Intel ICH7/ICH7R". Enabling flash write... OK. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically.Still the same result.
As far as I can make out the BIOS chip reads "25P80V6 GHAAA V5 CHN 636B"
The G's could be 6's likewise the B may well be an R, my aging eyes are struggling
-
Also not promising?
Probing for Micron/Numonyx/ST M25P80, 1024 kB: RDID byte 0 parity violation. probe_spi_rdid_generic: id1 0xff, id2 0xffff -
Yeah it's
25P80VGwhich is the same as I have. What you're seeing look exactly like this:
https://forum.netgate.com/post/461855That user was eventually able to read/write the bios using afudos in FreeDOS but to do so he had to add a port on the com2 header. Read forward from that post for the details.
Now more than 8 years ago!Steve
-
@stephenw10 hehe, permanently adding a serial port to the back of the box wasn't hard either, though most people will probably be content to just hook it up temporarily for setup. But it's nice having it there in case it's needed.
-
Thanks folks, I don't have time or patience for that so I think I will stop here, maybe one day I will get around to it :)
-
Yup, quite an involved process. And you don't actually need to flash it anyway, it will run pfSense just fine with the default BIOS.
Steve
