pfSense Forum

pfSense English Support => Hardware => Topic started by: Eams on May 04, 2013, 03:01:38 pm

Title: Watchguard Firebox XTM 8 Series
Post by: Eams on May 04, 2013, 03:01:38 pm
Having recently won a Watchguard Firebox XTM 810 in an unknown bidding war with Stephenw10, I've started this thread to help document it for others.

Mine came with no PSU or CF card.

The PSU for this is a 270w job - FSP270-60LE looks to be the OEM part supplied in these XTM 8's. http://www.headingonline.com/p-726-270w-flex-atx-power-supply-fsp270-60le.aspx (http://www.headingonline.com/p-726-270w-flex-atx-power-supply-fsp270-60le.aspx)

The juicy bits;
There is a unused PCI Bus header at the back on the left side of the motherboard.

The left 4 network ports are on daughter board which also has a Cavium Networks Nitrox PX CN1620 chip [http://www.cavium.com/pdfFiles/NITROX_PX_PB_Rev1.3.pdf]
Daughterboard connects via a PCI Express 16x connecter.

1x CPU Quad Core Intel Q9400
1x VGA marked up on the board near CPU/Chipset - 11 pin header.
1x KB/Mouse marked up on the board near LCD ribbon connector - 6pin header.
1x SPI-ROM 10pin header
1x Sata connector on the board, next to it is a SunplusIT SATALINK SPIF223A-HF022 ic.
1x COM2 header connected to rear serial port.
Also COM1 and USB2.0 marked up on the board but no headers soldered in.
3x CPU fan headers at the rear.
1x case fan heared at the rear.
2x DDR2 Slots - 1 populated, board marked DDR2 800
10x LAN ports:
- Mainboard 5x Intel 82573L NIC + 1 NIC same as daughterboard ones below
- Daughtboard 4x Intel NIC however very difficult to make out the numbers looks like 82574L or 82674L
Markings near CPU socket - FSB 1333 and MB-8750 WG1 V1.1

LCD Display sticker: VITEK DISPLAY VC220W-GGE-JC01. PCB marking 202W-REVS.1

No network relays on the boards - although solder pads and markings are there.

Pictures here: https://plus.google.com/photos/115736786050007462202/albums/5874219398935451569

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 04, 2013, 06:32:45 pm
Booting up with no CF card in gives me this output in PuTTY:

Code: [Select]
                                                                                   
AMIBIOS(C)2006 American Megatrends, Inc.                                       
MB-8750 Ver.AAA 12/02/08                                                       
CPU : Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz                           
 Speed : 2.66 GHz                                   
                                                    (F3 on Remote Keyboard)                               
The MCH is operating with DDR2 800/CL5/Tras18/Trp5/Trcd5                       
Initializing USB Controllers .. Done.                                           
2039MB OK
Reboot and Select proper Boot device                                           
or Insert Boot Media in selected Boot device and press a key
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 04, 2013, 08:16:21 pm
Looks like it's all working then. Always a bit of a risk buying incomplete from ebay.  ;)

I imagine the lcd is compatible with all their previous models.

I assume it has an arm/disarm led on the front? Does it come up correctly as red when you boot the bios?

Interesting that the bios date is two years earlier than the XTM5. Might just be Lanners date.

Also a bit odd that they chose to use com2 and have it at the rear.  :-\

Does it have thermal fan control? The unmodified XTM5 bios would allow you to check the system temperatures and voltages and almost nothing else.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:27:26 am
Yeah it seems to be working ok, as far as I can tell without having a CF card or a hdd to hand.

Ebay is a gamble at the best of times anyway ;) PSU's are built to take the damage without passing it on to the motherboard so I was pretty confident it would be ok - unless it blew due to a short on the motherboard - took it out to ensure no screws were stuck under and it was all clear :)

The LCD seems to be the same as previous models as you say so should be ok.

There is an arm/disarm led on the front, it hasn't lit up yet.

Yeah COM2 is a bit weird I guess - the Lanners FW-8750 does have one at the front - it's marked but un headed on the XTM8 next to the front USB ports.
Having looked at Lanner's website and registered, there is no bios update for the FW-8750 board :(

There is however some useful info there about the FW-8750 of which this board seems to be from:

Platform
Processor: Supports one Intel Core 2 Quad, Core 2 Duo, Pentium dual-core processor, LGA 775
Chipset: Intel Q35 + ICH9D0
Front Side Bus: 1333/1066/800 MHz
Max Speed: 3.0GHz

System Memory
Technology: Dual-channel DDR2 800/667 MHz
Max Capacity: 4GB
Socket: 240P DIMM x 2

Storage
HDD Bay(s) 3.5 x 1
Storage Interface: Serial ATA x 4, CompactFlash (type II) x 1
RAID: N/A

Networking
Ethernet Ports: 6 onboard (RJ45 x 6), 2 pair support bypass function, 1 optional module
Controller: Intel 82573L x 5, Intel 82566DM x 1, see module specifications for expansion ports

Supported Modules
NM-8750G4A: 4 port GbE (RJ45 x 4) Intel 82574L
NM-8750S4A: 4 port SFP (SFP x 4) Intel 82575EB

I/O Interface
Console: DB9 RS-232 x 1
USB 2.0: 2
Expansion: RC-87501A: PCI x1

Cooling
Processor: 1U CPU active heatsink (3 cooling fans)
System: Cooling fan x 1 with Smart Fan

Environmental Parameters
Temperature, ambient operating / storage: 0C ~40C / -20C~70C
Humidity (RH), ambient operating 5 ~ 90%, non-operating: 5 ~ 95%, non condensing

Miscellaneous
LCD Module: 2 x 20 character
Watchdog
Internal RTC with Li Battery

Physical Dimensions
426x44.4x396 mm (16.7x1.7x215.6 in) (WxHxD)
Weight: 8.2 kg (18.1 lbs)

Power
Type / Watts: 1U ATX SPS / 270W
Input: AC 100~240V at 50~60Hz


So potential to stick in a lower powered Core 2 Duo to get the watts down. Worth noting is that this board can take a 3.16Ghz Quad Core 2 processer!

It does seem to have themal fan control from the specs above and from having a poke in the BIOS. It powers them up at full thurst when first switched on, then slows them to almost a stop, then back to around 75% of the inital power up speed.

The only thing the BIOS allows you do do is set the time and date, and thats it. But you can view a load of other pages, temps, boot order and a bunch of other things I can't recall from late last night.

I did however log the screens from PuTTY - see next post.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:55:41 am
BIOS menus from XTM 8

Done as screen shots as it was easier than having to format the PuTTY log file!

Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:56:54 am
Notice on Hardware Health screen - fans have PWM settings ;)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 05, 2013, 05:46:35 am
Ah, yes that all look very familiar. This box looks very similar to the XTM5. I'd be willing to bet the arm/disarm led control is in the same place too. Some investigation would be required to find out for sure once you have it booting into pfSense.
Have you seen the price of those boxes new.  :o That's mostly licensing I guess but still.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 10:53:37 am
I should have it booting into pfSense soon, managed to pick up a CF card and a reader, can then see what this board says :)

Yeah saw online how much they are new :o even without licences they *can* still go for a lot. But the money is in the licencing for Watchguard.

Eamon



Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 11:37:20 am
Hmm not getting any joy no matter what image I put on this CF card :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 05, 2013, 02:16:23 pm
What image exactly are you using? How are you writing it?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 02:45:13 pm
I've tried:
pfSense-2.0.3-RELEASE-4g-i386-nanobsd-20130412-1022 - my 4g cf card is a smidge to small for this image :(
pfSense-2.0.3-RELEASE-4g-amd64-nanobsd-20130412-1027 - ditto above.
and
pfSense-2.0.3-RELEASE-2g-i386-nanobsd-20130412-1022.img - XTM 8 POSTs then hangs with the screen cleared.
pfSense-2.0.3-RELEASE-2g-amd64-nanobsd.img - ditto

Using Win32DiskImager to burn the images after extracting them - using a all in one usb card reader to write to the card (Windows 7 64bit)
Tried a few FreeDos images and they booted up fine on the XTM 8, so just a bit puzzled  ???

Eamon

[Edited to add about card reader]
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 05, 2013, 03:03:05 pm
Could it be that the XTM8 is using com2 for its serial port? Can you see if two serial ports are enabled in the bios?
Though if a FreeDOS image boots correctly that wouldn't explain it.

Are you using the correct baud rate? The bios usually comes up at 115200 where as pfSense uses 9600 by default.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:10:59 pm
I've been using 115200 8,n,1 No Parity, XON/OFF from the get go and it's been fine.
I did try it on 9600, but just got garbage!

Yeah it is using COM2 2F8h, IRQ 3.. Would pfSense switch to/assume COM1 and be trying to write to that?

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:13:30 pm
I can only see 1 COM port in the BIOS and thats COM2.

One in Advanced>Configure Remote Access and the other is under Advanced>Super IO Configuration - same address used 2F8/IRQ 3.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 05, 2013, 03:21:15 pm
pfSense will use com1 but that will just be whatever the first detected com port is. If there's only one enabled it will use that.
Did you use my FreeDOS image? That is configured to use com1 but also to use 9600bps so if you are seeing that then it should be working. If you used a standard FreeDOS image then what you are seeing is being redirected by the BIOS code which remains resident after boot if enabled. This could be interfering perhaps?

Try starting your serial terminal at 9600 after the machine has booted. Sometimes putty (if you're using that) has a problem when the baud rate changes.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 05, 2013, 03:35:56 pm
I saw you had a post of a FreeDos .vhd file but I don't use any virtualisation software on my main pc  - I just went to their website and used some images off there and they worked.

I did close down PuTTY between baud changes - I just get garbage and then the garbage stops!

In Advanced>Remote Config screen it has Redirection After BIOS POST [Always]
But I've no way of changing it due to the 'View Only Item' message on everything :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 05, 2013, 08:33:22 pm
The .vhd file was my first effort though I think it can be written by anything. Try this image instead:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios2.img.gz

That is set to use com1 at 9600 and it will beep three times just before it switches to the serial console.

If pfSense is booting in the background you will see the HD activity LED flashing after the console garbage has stopped. If that isn't happening then I suggest that the image is not writing correctly to the card. What are you extracting it with?

I always use phydiskwriteGUI which does the decompression on the fly. I know some people have had trouble with Windows 7 getting in the way.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 06, 2013, 07:13:51 am
You could also try this image which is mostly the same as the other one:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios.img

Since that's not gzip'd you won't have to extract it. If that runs but the others didn't you know it's an extraction problem.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 06, 2013, 07:33:08 am
Ok, wrote the FreeDosBios2 image to the card - boots up to the DOS menu ok, but after the 3 beeps - nothing (on 115200).
Changed the baud rate to 9600 got the garbage, beeps then nothing again.

Did FreeDosBios2 image through WinDiskImager.

Wrote nanobsd.full.img with physdiskwrite - wrote ok - (after using DiskPart to clean the partitions) - got nothing on XTM 8 both at 115200 and 9600.

The HD led does light up during POST but nothing when loading pfSense, however it does flicker up to the beeps on FreeDosBios2 image.

I have read something about UDMA/S.M.A.R.T. having an effect on other Fireboxes - the message shows when pfSense is on the cf card, but doesn't when FreeDos is on it  ???

I think my options are:
1. Get a 12pin IDC to 15pin VGA cable and connect up a monitor.
2. Install pfSense on a VM, configure it for COM2 and transfer that to the cf card.
3. Solder a header on to the COM1 space on the board.
4. Flash the BIOS to change COM2 address to the COM1 address.

Of which:
1. Do-able but would have to wait a few days for it to arrive.
2. Do-able although I have no knowledge of FreeBSD/pfSense.
3. No chance, I can solder but I'm not willing to risk it on this board.
4. No BIOS update to flash so no go.

I'm gonna have a go at changing the FreeDosBios2 image to use COM2 - Dos I can do ;)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 06, 2013, 07:39:44 am
You could also try this image which is mostly the same as the other one:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios.img

Since that's not gzip'd you won't have to extract it. If that runs but the others didn't you know it's an extraction problem.

Steve

Tried that one with physdiskwrite - worked the same as the gz one, booted up but that after the beeps nothing :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 06, 2013, 08:12:43 am
Yes that's the first thing I'd try. Edit the autoexec.bat file to put the console to com2 instead. Relatively easy test and it would confirm the problem.

If you boot with putty at 115200 does it show anything after the bios post that might indicate the card is booting? You should have an opportunity to interrupt the process and give the bootloader some parameters. You could potentially tell it to use com2 at that point.

You could try using one of the nanobsd_vga images. That will attempt to use the keyboard/monitor as the console. The resident bios code may redirect that to the com port. No idea if that would work.

It's possible to modify the bios like I did with the XTM5 but it's risky stuff. I managed to 'brick' the box a number of times but it did give me the opportunity to learn how to recover it!  ;D

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 06, 2013, 02:00:25 pm
Ok so I've got a decent version of FreeDOS loaded. I used the image that worked and copied over the other files from the image you posted.

I got a Nanobsd_vga booted to the pfSense menu but then stopped outputting once it carried on, however the HDD light did flicker every so often, nothing came over COM2 :(

I didn't think it would redirect and convert vga to ansi but it was worth a go!

So at the mo I've my own version of the FreeDOSBios image loaded, is there anything I need to run that could be of interest?

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 07, 2013, 03:17:15 am
Hmm, OK.
So your hybrid FreeDOS image doesn't switch the console to the com port I take it? Or is it using com2?

Interesting the the nanobsd_vga image booted to the menu. I would not expect to see anything on the com port normally from that image. Its console output is all text mode so I would have thought there was a good chance of it being redirected. Can you escape from the boot process at the menu to get a prompt?

So booting the normal nanobsd image do you see anything after the POST?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 07, 2013, 02:15:57 pm
Yeah with the FreeDOS image I just left everything as it was, no redirection to COM ports done and it works fine - I guess the bios is handling all of the redirection to COM2.

With nanobsd_vga it was just the first pfSense text menu that showed up, then nothing - I guess bios handling the redirection then the switch to vga ends the output.

Booting nanobsg_vga I can escape to a command prompt. I didn't get much out of it as I am not familiar with FreeBSD - managed ls but that was it!

A normal nanobsd image - nothing - however UDMA/SMART message shows in POST - it didn't show with any of the above where I can boot and at least see something.

I've a 12pin IDC to 15pin Vga lead on order from ebay, might make things simplier!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 07, 2013, 02:38:53 pm
Ah some progress.  :)
Probably the vga cable will make things a lot easier as long as it fits. The boxes I have here have a 2mm pitch connector instead of the more common 2.54mm (0.1"). You have a link to that cable?

Here are some things you can do at the boot loader prompt:
http://doc.pfsense.org/index.php/Booting_Options
Though I've never had to try any of them.

It appears there is no way (no practical way) use any serial port other than com1 for the console:
Quote from: http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html
27.6.5.2 Using a Serial Port Other Than sio0 for the Console

Using a port other than sio0 as the console requires the boot blocks, the boot loader, and the kernel to be recompiled as follows.

That's for standard FreeBSD though not NanoBSD.  :-\

I take it you tried editing the autoexec.bat file in my FreeDOS image to com2?

Steve

Edit: I see fro your BIOS shots that although there is only one serial port enabled it is still set to com2 and still uses 0x2F8 for its I/O address. Thus if this is hardcoded for com1 it won't work. But FreeDOS should be able to do it.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 07, 2013, 03:12:09 pm
Some other thoughts while I think of it.
There is another difference between the nanobsd and nanobsd_vga images. The straight nano images have dma disabled for the CF card interface. That's because many CF card readers do have required connections for DMA but the cards still report that they are DMA capable causing all sorts of trouble. However the nanobsd_vga image does not do this because it was developed for a specific device that will not boot if DMA is disabled. Could this be an issue here? I think it's probably just that it's trying to use com1 but that doesn't explain why it doesn't continue to boot in the background (flashing the HD LED).

One possibility would be to pre-install a config file on the CF card with some interfaces setup and then use the web interface to configure from there.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 08, 2013, 03:42:17 pm
Ah some progress.  :)
Probably the vga cable will make things a lot easier as long as it fits. The boxes I have here have a 2mm pitch connector instead of the more common 2.54mm (0.1"). You have a link to that cable?

You're right it's 2mm pitch and not 2.54mm which is what arrived :( The Keyboard/Mouse header is 2.54mm pitch though.

Here are some things you can do at the boot loader prompt:
http://doc.pfsense.org/index.php/Booting_Options
Though I've never had to try any of them.

I tried the set console command but got nowhere.


It appears there is no way (no practical way) use any serial port other than com1 for the console:
Quote from: http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html
27.6.5.2 Using a Serial Port Other Than sio0 for the Console

Using a port other than sio0 as the console requires the boot blocks, the boot loader, and the kernel to be recompiled as follows.

That's for standard FreeBSD though not NanoBSD.  :-\

I'm deffo not compiling my own, I don't know anything/enough about FreeBSD to be doing that.

I take it you tried editing the autoexec.bat file in my FreeDOS image to com2?

Steve

Edit: I see fro your BIOS shots that although there is only one serial port enabled it is still set to com2 and still uses 0x2F8 for its I/O address. Thus if this is hardcoded for com1 it won't work. But FreeDOS should be able to do it.

I didn't edit the autoexec.bat file, and I didn't put anything in about COM - just left it as a standard DOS boot up - the BIOS does a good job of redirecting it all to COM2 :)

Eamon

Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 08, 2013, 06:08:55 pm
Some other thoughts while I think of it.
There is another difference between the nanobsd and nanobsd_vga images. The straight nano images have dma disabled for the CF card interface. That's because many CF card readers do have required connections for DMA but the cards still report that they are DMA capable causing all sorts of trouble. However the nanobsd_vga image does not do this because it was developed for a specific device that will not boot if DMA is disabled. Could this be an issue here? I think it's probably just that it's trying to use com1 but that doesn't explain why it doesn't continue to boot in the background (flashing the HD LED).

One possibility would be to pre-install a config file on the CF card with some interfaces setup and then use the web interface to configure from there.

Steve

All the successful boots I've had with pfSense (to the menu) or FreeDos (to the command prompt) is when the UDMA/SMART message hasn't appreared in the POST screen. When it does appear it just blank screens and hangs.

The config file thing is a problem, I can't edit anything on the cf card when pfSense is on it, no go in windows or linux, so kinda stumped on that front.

The VM way might be worth a go. Convert img to vdi, edit, convert back..

Eamon

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 08, 2013, 07:23:58 pm
You may be able to do this but I don't know if nanobsd checks or not:
http://doc.pfsense.org/index.php/Automatically_Restore_During_Install

I would definitely try one of my images with autoexec edited for com2 instread of com1. That would at least indicate what the issue is.

All the successful boots I've had with pfSense (to the menu) or FreeDos (to the command prompt) is when the UDMA/SMART message hasn't appreared in the POST screen. When it does appear it just blank screens and hangs.

This is interesting. Where exactly does this message appear? The fact that dma is disabled in the image should not affect the POST, how could it.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 09, 2013, 01:40:39 am
I was actually looking at this on the FreeBSD website, it seems to be built into FreeBSD's nanobsd build - as it's documented on pfSense I would say it's safe to assume it's in pfSense nanobsd build too.

I'll try out a autoexec with com2 in it and see how that goes. I've another cf card on order so that'll make it easier to deal with mulitple images.

Yeah the UDMA/SMART thing is puzzling, I'll get a log from PuTTY later to show where it is.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 09, 2013, 02:51:41 pm
Something else while I think of it. You could potentially change the hardware resource settings for com2 in the BIOS so they use the com1 defaults. Of course you'd need to first mod the bios to open the settings.  ;)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 01:12:07 pm
Not been on here as much as I expected recently however... I have made some progress!

Forgive me for the lack of PuTTY log for the UDMA/SMART message :(

I've managed to connect a monitor to the onboard VGA connector and I can now see whats happening!

Having gotten nowhere with the nanobsd serial builds due to it being complied for COM1 and this machine having no COM1, I've been trying with the vga builds as they output to text. However they were still no good - it didn't redirect the text screen to COM2  :(

While trying the above on build of pfSense-memstick-2.1-BETA1-i386-20130510-1628.img.gz I had the monitor attached but it's giving me errors about partitioning!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 01:12:59 pm
Oh forgot to add, I connected a keyboard via usb and it works :)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 13, 2013, 01:33:43 pm
Loving your VGA hook up!  ;)

The memstick image expects to be connected via USB so if you put it on a CF card it will probably complain.

So with the monitor connected you still can't boot the nano_vga image?
Hmm, I wonder if it set to use dual consoles. I suspect that anything hard coded to talk to the com1 resources will have a problem when they are not available. You'd hope it would fail gracefully but I no idea.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 01:42:58 pm
Haha, the vga hookup was one of two ways and this was easiest that didn't involve cutting any wires or anything.

Only connected green as I figured it'd let me see everything - apart from bold white!

I'm just writing a nano_vga image as I type on the sandisk 4gig cf card - this one will take the 4gig image!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 02:08:32 pm
Getting some weird READ_DMA error.

Obligatory dmesg:

$ dmesg
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
   The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RELEASE-p13 #0: Fri Apr 12 11:55:06 EDT 2013
    root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap_vga.8.amd64 amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz (2660.01-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x1067a  Family = 6  Model = 17  Stepping = 10
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x408e3fd<SSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 2147483648 (2048 MB)
avail memory = 2043940864 (1949 MB)
ACPI APIC Table: <120208 APIC1015>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff8040b400, 0) error 1
wlan: mac acl policy registered
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff8040b4a0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff8040b540, 0) error 1
wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (wpi_fw, 0xffffffff8058a010, 0) error 1
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <120208 XSDT1015> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7f600000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci7: <ACPI PCI bus> on pcib1
pcib2: <PCI-PCI bridge> mem 0xfe7e0000-0xfe7fffff irq 16 at device 0.0 on pci7
pci8: <PCI bus> on pcib2
pcib3: <PCI-PCI bridge> irq 16 at device 0.0 on pci8
pci14: <PCI bus> on pcib3
pci14: <encrypt/decrypt, network/computer crypto> at device 0.0 (no driver attached)
pcib4: <PCI-PCI bridge> irq 17 at device 1.0 on pci8
pci13: <PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff,0xfebdc000-0xfebdffff irq 17 at device 0.0 on pci13
em0: Using MSIX interrupts with 3 vectors
em0: [ITHREAD]
em0: [ITHREAD]
em0: [ITHREAD]
pcib5: <PCI-PCI bridge> irq 16 at device 4.0 on pci8
pci12: <PCI bus> on pcib5
pcib6: <PCI-PCI bridge> irq 18 at device 6.0 on pci8
pci11: <PCI bus> on pcib6
em1: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 18 at device 0.0 on pci11
em1: Using MSIX interrupts with 3 vectors
em1: [ITHREAD]
em1: [ITHREAD]
em1: [ITHREAD]
pcib7: <PCI-PCI bridge> irq 16 at device 8.0 on pci8
pci10: <PCI bus> on pcib7
em2: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 16 at device 0.0 on pci10
em2: Using MSIX interrupts with 3 vectors
em2: [ITHREAD]
em2: [ITHREAD]
em2: [ITHREAD]
pcib8: <PCI-PCI bridge> irq 17 at device 9.0 on pci8
pci9: <PCI bus> on pcib8
em3: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 17 at device 0.0 on pci9
em3: Using MSIX interrupts with 3 vectors
em3: [ITHREAD]
em3: [ITHREAD]
em3: [ITHREAD]
vgapci0: <VGA-compatible display> port 0x3800-0x3807 mem 0xfe100000-0xfe17ffff,0xd0000000-0xdfffffff,0xfe000000-0xfe0fffff irq 16 at device 2.0 on pci0
em4: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x3880-0x389f mem 0xfe1c0000-0xfe1dffff,0xfe1fe000-0xfe1fefff irq 20 at device 25.0 on pci0
em4: Using an MSI interrupt
em4: [FILTER]
pcib9: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0
pci6: <ACPI PCI bus> on pcib9
em5: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xac00-0xac1f mem 0xfe6e0000-0xfe6fffff irq 16 at device 0.0 on pci6
em5: Using an MSI interrupt
em5: [FILTER]
pcib10: <ACPI PCI-PCI bridge> irq 16 at device 28.1 on pci0
pci5: <ACPI PCI bus> on pcib10
em6: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x9c00-0x9c1f mem 0xfe5e0000-0xfe5fffff irq 17 at device 0.0 on pci5
em6: Using an MSI interrupt
em6: [FILTER]
pcib11: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci4: <ACPI PCI bus> on pcib11
em7: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x8c00-0x8c1f mem 0xfe4e0000-0xfe4fffff irq 18 at device 0.0 on pci4
em7: Using an MSI interrupt
em7: [FILTER]
pcib12: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci3: <ACPI PCI bus> on pcib12
em8: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x7c00-0x7c1f mem 0xfe3e0000-0xfe3fffff irq 19 at device 0.0 on pci3
em8: Using an MSI interrupt
em8: [FILTER]
pcib13: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0
pci2: <ACPI PCI bus> on pcib13
em9: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0x6c00-0x6c1f mem 0xfe2e0000-0xfe2fffff irq 16 at device 0.0 on pci2
em9: Using an MSI interrupt
em9: [FILTER]
uhci0: <Intel 82801I (ICH9) USB controller> port 0x3c00-0x3c1f irq 23 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <Intel 82801I (ICH9) USB controller> on uhci0
uhci1: <Intel 82801I (ICH9) USB controller> port 0x4000-0x401f irq 19 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <Intel 82801I (ICH9) USB controller> on uhci1
ehci0: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xfe1ff800-0xfe1ffbff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus2: EHCI version 1.0
usbus2: <Intel 82801I (ICH9) USB 2.0 controller> on ehci0
pcib14: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci1: <ACPI PCI bus> on pcib14
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH9 SATA300 controller> port 0x4c00-0x4c07,0x4880-0x4883,0x4800-0x4807,0x4480-0x4483,0x4400-0x440f,0x4080-0x408f irq 19 at device 31.2 on pci0
atapci0: [ITHREAD]
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
atapci1: <Intel ICH9 SATA300 controller> port 0x5c00-0x5c07,0x5880-0x5883,0x5800-0x5807,0x5480-0x5483,0x5400-0x540f,0x5080-0x508f irq 19 at device 31.5 on pci0
atapci1: [ITHREAD]
ata4: <ATA channel 0> on atapci1
ata4: [ITHREAD]
ata5: <ATA channel 1> on atapci1
ata5: [ITHREAD]
acpi_button0: <Power Button> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71 irq 8 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
ppc0: <Parallel port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppc0: [ITHREAD]
ppbus0: <Parallel port bus> on ppc0
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
ad7: 3815MB <SanDisk SDCFH-004G HDX 7.07> at ata3-slave UDMA33 SATA 1.5Gb/s
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 4 ports with 4 removable, self powered
ugen0.2: <Chicony> at usbus0
ukbd0: <Chicony USB Keyboard, class 0/0, rev 2.00/1.57, addr 2> on usbus0
kbd2 at ukbd0
ad7: FAILURE - READ_DMA timed out LBA=7813117
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813103
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813116
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
Trying to mount root from ufs:/dev/ufs/pfsense0
ad7: FAILURE - SETFEATURES 0x85 status=51<READY,DSC,ERROR> error=4<ABORTED>
pflog0: promiscuous mode enabled
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119


Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 13, 2013, 03:10:52 pm
Right, that's what I mentioned earlier. The nanobsd_vga images have DMA enabled because of a specific device but many CF card slots do not have enough pins. Probably that's what's happening here.
Interrupt the boot process at the loader menu and do this:
http://doc.pfsense.org/index.php/Booting_Options#Disable_DMA_for_IDE_drives

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: wallabybob on May 13, 2013, 03:53:44 pm
My suspicion, based on the high LBA reported, is that your 4GB card is a bit short of providing 4GiB (1024 x 1024 x 1024) and the 4G image didn't quite fit. Some people have had to put a 2GB image on  a "4GB" card/stick. Note the card is reported having 3815MB which would allow a LBA of up to around 7630000 which is a bit short of the reported LBAs.

If I recall correctly, the FreeBSD GEOM component goes looking for a GEOM signature on the apparent last sector or two of the disk.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 05:28:04 pm
I put a 2g nano_vga 64bit image on the same card and got the same LBA error.

Did the set hw.ata.atapi_dma=0 thing too which stopped the LBA errors, however got a different LBA error!


ad7: 3815MB <SanDisk SDCFH-004G HDX 7.07> at ata3-slave PIO4 SATA 1.5Gb/s
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813117
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813103
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813116
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
ugen0.u1g:ue gn<e2I.nn11t.:e 1l:<> I <naIttne ltue>s lb>au ts a0tus
ubsubsu2s
u1h
ub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
Root mount waiting for: usbus2 usbus1 usbus0
uhub2: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
uhub1: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
ad7: FAILURE - SETFEATURES 0x85 status=51<READY,DSC,ERROR> error=4<ABORTED>
ugen0.2: <Chicony> at usbus0
ukbd0: <Chicony USB Keyboard, class 0/0, rev 2.00/1.57, addr 2> on usbus0
kbd2 at ukbd0
pflog0: promiscuous mode enabled
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119
ad7: FAILURE - READ status=51<READY,DSC,ERROR> error=10<NID_NOT_FOUND> LBA=7813119


Burning 2g nano_vga 32bit gives the same error on the same card (4gig SanDisk Ultra)

Booting up on the no name cf card with the same 32bit 2g nano_vga image gives no errors - no ser hw.ata.ata_dma=0 performed - wierd;


ad7: 3639MB <CF Card Ver5.04> at ata3-slave UDMA33 SATA 1.5Gb/s
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
ugen0u.1g:e n<2I.n1t:e l<>I natte l>u saubtu guss0beuns1
2.1
: <Intel> at usbus1
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub1: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
Root mount waiting for: usbus2 usbus1 usbus0
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
uhub2: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
ugen0.2: <Chicony> at usbus0
ukbd0: <Chicony USB Keyboard, class 0/0, rev 2.00/1.57, addr 2> on usbus0
kbd2 at ukbd0
pflog0: promiscuous mode enabled


How very bizarre.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 13, 2013, 05:51:53 pm
The 'nid not found' error is common and nothing to worry about:
http://doc.pfsense.org/index.php/DMA_and_LBA_Errors

I would guess that your no-name card is not DMA capable so didn't cause the problem.

Did it boot successfully then?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 13, 2013, 07:32:39 pm
Damn I bought the exact same cf card that's in that link! I guess that's that error sorted then.

Yes it did boot, even with the LBA errors, looks like it was a combination of both errors mentioned by yourself and wallabybob.
Its pretty nippy to say the least  ;)
I gotta figure out how to set it up now. At least 10x GbE ports gives me plenty to play with haha!

I've contacted Lanner to see if I can get the BIOS for the 8750 this is based on, that would help even further.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: fmertz on May 15, 2013, 09:16:16 am
The LCD seems to be the same as previous models as you say so should be ok.

There is an arm/disarm led on the front, it hasn't lit up yet.

There is some useful info there about the FW-8750 of which this board seems to be from:

Platform
Chipset: Intel Q35 + ICH9D0


Eamon
The LCD code assumes parallel port, so, at a minimum, the sdeclcd driver part of the lcdproc package should run. Might even work, too.

For the LEDs, the driver code supports the various models based on standard PCI detection of the ICH. We definitely need to add an entry for this ICH9 in the driver code. Once you guys get around to it, can you confirm this is, in fact, an ICH9D0, identified by Vendor x8086, device x2914 (the numbers are listed on page 12 of the "Intel I/O Controller Hub 9 (ICH9) Family Specification Update")?

Generally, the LEDs can be wired off of the GPIO device part of this ICH (like in the older models), but, more likely, they are wired off of the SuperIO chip (like the XTM 5). A further screen shot seems to list an ITE8718. This is where the research comes in to identify which line these LEDs are wired off of. I'll be happy to code this in when it is discovered.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 15, 2013, 01:41:09 pm
Commence experimental probing!  ;D

Since you don't have the Watchguard OS we can't look for clues in it's boot messages.

Not using a Winbond sio chip, interesting.

You could extract the bios code with flashrom and look at it for hidden menus.

Steve

Edit: Looks to be supported by superiotool as well.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 16, 2013, 03:33:52 pm
fmertz:
Ok, fired up lcdproc, but nothing seems to happen :(

The boot up screen shows 'Starting package LCDproc...done.'

Under Status: Services it shows as Stopped. Clicking to start it doesn't change it's status.

ICH9 Chipset - think you were right, experimental probe..:

$ pciconf -lc
hostb0@pci0:0:0:0:   class=0x060000 card=0x29b08086 chip=0x29b08086 rev=0x02 hdr=0x00
    cap 09[e0] = vendor (length 11) Intel cap 11 version 1
pcib1@pci0:0:1:0:   class=0x060400 card=0x29b18086 chip=0x29b18086 rev=0x02 hdr=0x01
    cap 0d[88] = PCI Bridge card=0x29b18086
    cap 01[80] = powerspec 3  supports D0 D3  current D0
    cap 05[90] = MSI supports 1 message
    cap 10[a0] = PCI-Express 1 root port max data 128(128) link x4(x16)
vgapci0@pci0:0:2:0:   class=0x030000 card=0x29b28086 chip=0x29b28086 rev=0x02 hdr=0x00
    cap 05[90] = MSI supports 1 message
    cap 01[d0] = powerspec 2  supports D0 D3  current D0
em4@pci0:0:25:0:   class=0x020000 card=0x00008086 chip=0x10bd8086 rev=0x02 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 13[e0] = PCI Advanced Features: FLR TP
pcib9@pci0:0:28:0:   class=0x060400 card=0x29408086 chip=0x29408086 rev=0x02 hdr=0x01
    cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x29408086
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
pcib10@pci0:0:28:1:   class=0x060400 card=0x29428086 chip=0x29428086 rev=0x02 hdr=0x01
    cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x29428086
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
pcib11@pci0:0:28:2:   class=0x060400 card=0x29448086 chip=0x29448086 rev=0x02 hdr=0x01
    cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x29448086
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
pcib12@pci0:0:28:3:   class=0x060400 card=0x29468086 chip=0x29468086 rev=0x02 hdr=0x01
    cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x29468086
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
pcib13@pci0:0:28:4:   class=0x060400 card=0x29488086 chip=0x29488086 rev=0x02 hdr=0x01
    cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
    cap 05[80] = MSI supports 1 message
    cap 0d[90] = PCI Bridge card=0x29488086
    cap 01[a0] = powerspec 2  supports D0 D3  current D0
uhci0@pci0:0:29:0:   class=0x0c0300 card=0x29348086 chip=0x29348086 rev=0x02 hdr=0x00
    cap 13[50] = PCI Advanced Features: FLR TP
uhci1@pci0:0:29:1:   class=0x0c0300 card=0x29358086 chip=0x29358086 rev=0x02 hdr=0x00
    cap 13[50] = PCI Advanced Features: FLR TP
ehci0@pci0:0:29:7:   class=0x0c0320 card=0x293a8086 chip=0x293a8086 rev=0x02 hdr=0x00
    cap 01[50] = powerspec 2  supports D0 D3  current D0
    cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14
    cap 13[98] = PCI Advanced Features: FLR TP
pcib14@pci0:0:30:0:   class=0x060401 card=0x244e8086 chip=0x244e8086 rev=0x92 hdr=0x01
    cap 0d[50] = PCI Bridge card=0x244e8086
isab0@pci0:0:31:0:   class=0x060100 card=0x29148086 chip=0x29148086 rev=0x02 hdr=0x00
    cap 09[e0] = vendor (length 12) Intel cap 1 version 0
       features: SATA RAID-5, 4 PCI-e x1 slots
atapci0@pci0:0:31:2:   class=0x01018f card=0x29208086 chip=0x29208086 rev=0x02 hdr=0x00
    cap 01[70] = powerspec 3  supports D0 D3  current D0
    cap 13[b0] = PCI Advanced Features: FLR TP
none0@pci0:0:31:3:   class=0x0c0500 card=0x29308086 chip=0x29308086 rev=0x02 hdr=0x00
atapci1@pci0:0:31:5:   class=0x010185 card=0x29268086 chip=0x29268086 rev=0x02 hdr=0x00
    cap 01[70] = powerspec 3  supports D0 D3  current D0
    cap 13[b0] = PCI Advanced Features: FLR TP
pcib2@pci0:7:0:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 upstream port max data 128(2048) link x4(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib3@pci0:8:0:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x4(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib4@pci0:8:1:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib5@pci0:8:4:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x0(x8)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib6@pci0:8:6:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib7@pci0:8:8:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
pcib8@pci0:8:9:0:   class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
    cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
    cap 0d[a4] = PCI Bridge card=0x862410b5
none1@pci0:14:0:0:   class=0x100000 card=0x0001177d chip=0x0010177d rev=0x01 hdr=0x00
    cap 01[40] = powerspec 3  supports D0 D3  current D0
    cap 05[50] = MSI supports 1 message, 64 bit
    cap 10[70] = PCI-Express 1 endpoint max data 128(256) link x4(x4)
em0@pci0:13:0:0:   class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
    cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em1@pci0:11:0:0:   class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
    cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em2@pci0:10:0:0:   class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
    cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em3@pci0:9:0:0:   class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
    cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em5@pci0:6:0:0:   class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em6@pci0:5:0:0:   class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em7@pci0:4:0:0:   class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em8@pci0:3:0:0:   class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em9@pci0:2:0:0:   class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
    cap 01[c8] = powerspec 2  supports D0 D3  current D0
    cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
    cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)


Stephen:
I managed to upload superiotool to /tmp/ but don't know how to run it :(

Ditto flashrom!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 16, 2013, 03:42:33 pm
Another experimental probe..


$ sysctl hw
hw.machine: i386
hw.model: Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz
hw.ncpu: 4
hw.byteorder: 1234
hw.physmem: 2120441856
hw.usermem: 2066382848
hw.pagesize: 4096
hw.floatingpoint: 1
hw.machine_arch: i386
hw.realmem: 2137784320
hw.amr.force_sg32: 0
hw.an.an_cache_iponly: 1
hw.an.an_cache_mcastonly: 0
hw.an.an_cache_mode: dbm
hw.an.an_dump: off
hw.ata.setmax: 0
hw.ata.wc: 1
hw.ata.atapi_dma: 1
hw.ata.ata_dma_check_80pin: 1
hw.ata.ata_dma: 1
hw.ath.bstuck: 4
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.resetcal: 1200
hw.ath.shortcal: 100
hw.ath.longcal: 30
hw.ath.hal.swba_backoff: 0
hw.ath.hal.sw_brt: 10
hw.ath.hal.dma_brt: 2
hw.bce.msi_enable: 1
hw.bce.tso_enable: 1
hw.bge.allow_asf: 0
hw.bt848.slow_msp_audio: -1
hw.bt848.format: -1
hw.bt848.reverse_mute: -1
hw.bt848.tuner: -1
hw.bt848.card: -1
hw.bwn.wme: 1
hw.bwn.usedma: 1
hw.bwn.hwpctl: 0
hw.bwn.bluetooth: 1
hw.bwn.bfp: 0
hw.cardbus.cis_debug: 0
hw.cardbus.debug: 0
hw.cxgb.snd_queue_len: 128
hw.cxgb.use_16k_clusters: -1
hw.cxgb.force_fw_update: 0
hw.cxgb.multiq: 1
hw.cxgb.ofld_disable: 0
hw.cxgb.msi_allowed: 2
hw.cxgb.tx_reclaim_threshold: 32
hw.cxgb.tx_coalesce_enable_stop: 256
hw.cxgb.tx_coalesce_enable_start: 512
hw.cxgb.tx_coalesce_force: 0
hw.cxgb.txq_mr_size: 1024
hw.em.eee_setting: 0
hw.em.rx_process_limit: 100
hw.em.enable_msix: 1
hw.em.sbp: 0
hw.em.smart_pwr_down: 0
hw.em.txd: 1024
hw.em.rxd: 1024
hw.em.rx_abs_int_delay: 66
hw.em.tx_abs_int_delay: 66
hw.em.rx_int_delay: 0
hw.em.tx_int_delay: 66
hw.igb.rx_process_limit: 100
hw.igb.num_queues: 0
hw.igb.header_split: 0
hw.igb.max_interrupt_rate: 8000
hw.igb.enable_msix: 1
hw.igb.enable_aim: 1
hw.igb.txd: 1024
hw.igb.rxd: 1024
hw.firewire.hold_count: 0
hw.firewire.try_bmr: 1
hw.firewire.fwmem.speed: 2
hw.firewire.fwmem.eui64_lo: 0
hw.firewire.fwmem.eui64_hi: 0
hw.firewire.phydma_enable: 1
hw.firewire.nocyclemaster: 0
hw.firewire.fwe.rx_queue_len: 128
hw.firewire.fwe.tx_speed: 2
hw.firewire.fwe.stream_ch: 1
hw.firewire.sbp.tags: 0
hw.firewire.sbp.use_doorbell: 0
hw.firewire.sbp.scan_delay: 500
hw.firewire.sbp.login_delay: 1000
hw.firewire.sbp.exclusive_login: 1
hw.firewire.sbp.max_speed: -1
hw.firewire.sbp.auto_login: 1
hw.hifn.maxbatch: 1
hw.hifn.debug: 0
hw.malo.txbuf: 256
hw.malo.rxquota: 256
hw.malo.rxbuf: 256
hw.malo.txcoalesce: 8
hw.malo.pci.msi_disable: 0
hw.mfi.max_cmds: 128
hw.mfi.event_class: 0
hw.mfi.event_locale: 65535
hw.mwl.rxdmalow: 3
hw.mwl.rxquota: 640
hw.mwl.txcoalesce: 8
hw.mwl.txbuf: 256
hw.mwl.rxbuf: 640
hw.mwl.rxdesc: 256
hw.pccard.cis_debug: 0
hw.pccard.debug: 0
hw.cbb.debug: 0
hw.cbb.start_32_io: 4096
hw.cbb.start_16_io: 256
hw.cbb.start_memory: 2281701376
hw.pcic.pd6722_vsense: 1
hw.pcic.intr_mask: 57016
hw.pci.usb_early_takeover: 1
hw.pci.honor_msi_blacklist: 1
hw.pci.enable_msix: 1
hw.pci.enable_msi: 1
hw.pci.do_power_resume: 1
hw.pci.do_power_nodriver: 0
hw.pci.enable_io_modes: 1
hw.pci.default_vgapci_unit: -1
hw.pci.host_mem_start: 2147483648
hw.pci.mcfg: 1
hw.pci.irq_override_mask: 57080
hw.safe.rngmaxalarm: 8
hw.safe.rngbufsize: 16
hw.safe.rnginterval: 1
hw.syscons.kbd_debug: 1
hw.syscons.kbd_reboot: 0
hw.syscons.bell: 1
hw.syscons.saver.keybonly: 1
hw.syscons.sc_no_suspend_vtswitch: 0
hw.usb.no_boot_wait: 0
hw.usb.debug: 0
hw.usb.usb_lang_mask: 255
hw.usb.usb_lang_id: 9
hw.usb.template: 0
hw.usb.power_timeout: 30
hw.usb.uath.regdomain: 0
hw.usb.uath.countrycode: 0
hw.usb.urtw.preamble_mode: 2
hw.usb.urtw.debug: 0
hw.usb.ucom.cons_baud: 9600
hw.usb.ucom.cons_unit: -1
hw.wi.debug: 0
hw.wi.txerate: 0
hw.intr_storm_threshold: 1000
hw.pagesizes: 4096 0
hw.availpages: 517686
hw.bus.devctl_queue: 1000
hw.bus.devctl_disable: 0
hw.kbd.keymap_restrict_change: 0
hw.nve_pollinterval: 0
hw.busdma.total_bpages: 128
hw.busdma.zone0.total_bpages: 128
hw.busdma.zone0.free_bpages: 128
hw.busdma.zone0.reserved_bpages: 0
hw.busdma.zone0.active_bpages: 0
hw.busdma.zone0.total_bounced: 0
hw.busdma.zone0.total_deferred: 0
hw.busdma.zone0.lowaddr: 0xffffffff
hw.busdma.zone0.alignment: 4096
hw.clockrate: 2660
hw.via_feature_xcrypt: 0
hw.via_feature_rng: 0
hw.instruction_sse: 1
hw.apic.enable_extint: 0
hw.mca.erratum383: 0
hw.mca.amd10h_L1TP: 1
hw.mca.enabled: 1
hw.mca.count: 0
hw.mca.interval: 3600
hw.mca.force_scan: 0
hw.acpi.supported_sleep_state: S1 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: NONE
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1


Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 16, 2013, 03:47:51 pm
Another..


$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.P001
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.cx_supported: C1/0
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% last 5000us
dev.cpu.0.freq: 330
dev.cpu.0.freq_levels: 2646/-1 2315/-1 1984/-1 1653/-1 1323/-1 992/-1 661/-1 330/-1
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.P002
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/0
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% last 5000us
dev.cpu.2.%desc: ACPI CPU
dev.cpu.2.%driver: cpu
dev.cpu.2.%location: handle=\_PR_.P003
dev.cpu.2.%pnpinfo: _HID=none _UID=0
dev.cpu.2.%parent: acpi0
dev.cpu.2.cx_supported: C1/0
dev.cpu.2.cx_lowest: C1
dev.cpu.2.cx_usage: 100.00% last 5000us
dev.cpu.3.%desc: ACPI CPU
dev.cpu.3.%driver: cpu
dev.cpu.3.%location: handle=\_PR_.P004
dev.cpu.3.%pnpinfo: _HID=none _UID=0
dev.cpu.3.%parent: acpi0
dev.cpu.3.cx_supported: C1/0
dev.cpu.3.cx_lowest: C1
dev.cpu.3.cx_usage: 100.00% last 5000us


Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 16, 2013, 06:07:15 pm
To use either of those tools you have to install the FreeBSD package properly, so:

As you are running NanoBD first remount the filesystem read-write
Code: [Select]
[2.0.3-RELEASE][root@pfsense.fire.box]/root(1): /etc/rc.conf_mount_rw
Then add the package. You have to specify the complete path beacsue FreeBSD 8.1 is now quite old
Code: [Select]
[2.0.3-RELEASE][root@pfsense.fire.box]/root(2): pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/superiotool.tbz
Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/superiotool.tbz... Done.
same for flashrom
Code: [Select]
[2.0.3-RELEASE][root@pfsense.fire.box]/root(3): pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/flashrom.tbz
Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/flashrom.tbz... Done.
Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/All/libpci-3.1.7_1.tbz... Done.

Then remount the filesystem read-only again
Code: [Select]
[2.0.3-RELEASE][root@pfsense.fire.box]/root(4): /etc/rc.conf_mount_ro
Finally issue a rehash to re-index the new files so FreeBSD knows where to find them
Code: [Select]
[2.0.3-RELEASE][root@pfsense.fire.box]/root(5): rehash
Now you run the tools.  :)

After you install the lcdproc-dev package via the pfSense GUI you have to configure the various parameters before it will run and then start the service manually the first time in Status: Services:

Steve

Title: Re: Watchguard Firebox XTM 8 Series
Post by: fmertz on May 16, 2013, 06:42:11 pm
isab0@pci0:0:31:0:   class=0x060100 card=0x29148086 chip=0x29148086 rev=0x02 hdr=0x00
Yep, confirmed ICH9D0. Dom 0, bus 0, device 31, function 0 is the L(ow)P(in)C(ount) device. We can use it to identify the exact ICH model number.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 16, 2013, 07:03:49 pm
I had lcdproc loaded - removed and installed lcdproc-dev - selected WatchGuard Firebox with SDEC (x86only) - see attached pics.

Looks like powerd is doing it's job running the cpu at 330Mhz - fans however haven't slowed down any though :(

Superiotool probe..:
$ superiotool -d
superiotool r
Found ITE IT8718F (id=0x8718, rev=0x4) at 0x2e
Register dump:
idx 20 21 22 23 24 2b
val 87 18 04 10 00 00
def 87 18 01 00 00 00
LDN 0x00 (Floppy)
idx 30 60 61 70 74 f0 f1
val 00 00 00 00 04 00 00
def 00 03 f0 06 02 00 00
LDN 0x01 (COM1)
idx 30 60 61 70 f0 f1 f2 f3
val 00 03 f8 04 00 50 00 7f
def 00 03 f8 04 00 50 00 7f
LDN 0x02 (COM2)
idx 30 60 61 70 f0 f1 f2 f3
val 01 02 f8 03 00 50 00 7f
def 00 02 f8 03 00 50 00 7f
LDN 0x03 (Parallel port)
idx 30 60 61 62 63 70 74 f0
val 01 03 78 00 00 07 04 08
def 00 03 78 07 78 07 03 03
LDN 0x04 (Environment controller)
idx 30 60 61 62 63 70 f0 f1  f2 f3 f4 f5 f6
val 01 0a 10 0a 00 00 80 00  00 00 a0 00 ff
def 00 02 90 02 30 09 00 00  00 00 00 NA NA
LDN 0x05 (Keyboard)
idx 30 60 61 62 63 70 71 f0
val 01 00 60 00 64 01 02 00
def 01 00 60 00 64 01 02 00
LDN 0x06 (Mouse)
idx 30 70 71 f0
val 01 0c 02 00
def 00 0c 02 00
LDN 0x07 (GPIO)
idx 25 26 27 28 29 2a 2c 60  61 62 63 64 65 70 71 72  73 74 b0 b1 b2 b3 b4 b5  b8 b9 ba bb bc bd c0 c1  c2 c3 c4 c5 c8 c9 ca cb  cc e0 e1 e2 e3 e4 e5 e6  e7 f0 f1 f2 f3 f4 f5 f6  f7 f8 f9 fa fb fc fd fe  ff
val 41 d3 00 00 00 20 1f 00  00 0a 20 0a 30 00 00 00  00 00 00 00 00 00 00 00  40 00 00 00 00 00 40 d3  00 40 00 00 40 d0 00 40  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 bc 00 00  00
def 01 00 00 40 00 00 00 00  00 00 00 00 00 00 00 20  38 00 00 00 00 00 00 00  00 00 00 00 00 00 01 00  00 40 00 00 01 00 00 40  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  00 00 00 00 00 NA 00 00  00
LDN 0x0a (Consumer IR)
idx 30 60 61 70 f0
val 00 00 00 00 06
def 00 03 10 0b 00


Hope that is of some use ;D

Haven't managed to get flashrom to run  ???

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: fmertz on May 16, 2013, 07:24:20 pm
Selected WatchGuard Firebox with SDEC (x86only) - see attached pics.
That was an easy win. Good to see, though. Have you tried the buttons? Best guess, they sort of work, but are not mapped correctly...
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 16, 2013, 07:29:34 pm
What happens when you try to run flashrom?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 17, 2013, 02:54:52 am
fmertz:
I've tried the buttons, but with the display being so faint, it's hard to see properly. I'll try and have a further play tonight.

Steve:
With flashrom I'm getting the error:
/usr/local/bin/flashrom: Exec format error. Binary file not executable.


Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 17, 2013, 03:27:19 am
Ah, that's interesting. Looking back through the boot logs you posted earlier it looks like you were running 64bit, is that still the case?
That explains the wrong binary error.

If that is the case:
Remount the filesystem and remove flashrom with
Code: [Select]
pkg_delete flashrom
Then add the correct version
Code: [Select]
pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/flashrom.tbz
See how that goes, I'm not entirely sure what will happen. You may need to manually remove libpci-3.1.7_1 it may just be overwritten.  :-\

Interesting that superiotool worked fine and that the sdeclcd driver worked.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 18, 2013, 05:49:56 am
Removed flashrom and libpci-3.1.7_1 but still got the same /usr/local/bin/flashrom: Exec format error. Binary file not executable error.

Just checked and I'm running the nano_vga i386 build ::)

Removed both mentioned above and applied the i386 packages - flashrom now works :)

Code: [Select]
$ flashrom -V
flashrom v0.9.2-r1001 on FreeBSD 8.1-RELEASE-p13 (i386), built with libpci 3.1.7, GCC 4.2.1 20070719  [FreeBSD]
flashrom is free software, get the source code at http://www.flashrom.org

Initializing internal programmer
No coreboot table found.
dmidecode execution unsucessfull - continuing without DMI info
Found ITE Super I/O, id 8718
Found chipset "Intel ICH9DO", enabling flash write...
0xfff80000/0xffb80000 FWH IDSEL: 0x0
0xfff00000/0xffb00000 FWH IDSEL: 0x0
0xffe80000/0xffa80000 FWH IDSEL: 0x1
0xffe00000/0xffa00000 FWH IDSEL: 0x1
0xffd80000/0xff980000 FWH IDSEL: 0x2
0xffd00000/0xff900000 FWH IDSEL: 0x2
0xffc80000/0xff880000 FWH IDSEL: 0x3
0xffc00000/0xff800000 FWH IDSEL: 0x3
0xff700000/0xff300000 FWH IDSEL: 0x4
0xff600000/0xff200000 FWH IDSEL: 0x5
0xff500000/0xff100000 FWH IDSEL: 0x6
0xff400000/0xff000000 FWH IDSEL: 0x7
0xfff80000/0xffb80000 FWH decode enabled
0xfff00000/0xffb00000 FWH decode enabled
0xffe80000/0xffa80000 FWH decode disabled
0xffe00000/0xffa00000 FWH decode disabled
0xffd80000/0xff980000 FWH decode disabled
0xffd00000/0xff900000 FWH decode disabled
0xffc80000/0xff880000 FWH decode disabled
0xffc00000/0xff800000 FWH decode disabled
0xff700000/0xff300000 FWH decode disabled
0xff600000/0xff200000 FWH decode disabled
0xff500000/0xff100000 FWH decode disabled
0xff400000/0xff000000 FWH decode disabled
Maximum FWH chip size: 0x100000 bytes
BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1

Root Complex Register Block address = 0xfed1c000
GCS = 0x464: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI)
Top Swap : not enabled
SPIBAR = 0xfed1c000 + 0x3800
0x04: 0x6008 (HSFS)
FLOCKDN 0, FDV 1, FDOPSS 1, SCIP 0, BERASE 1, AEL 0, FCERR 0, FDONE 0
0x50: 0x0000ffff (FRAP)
BMWAG 0, BMRAG 0, BRWA 255, BRRA 255
0x54: 0x00000000 (FREG0)
0x58: 0x01020003 (FREG1)
0x5C: 0x00000fff (FREG2)
0x60: 0x00020001 (FREG3)
0x64: 0x00000fff (FREG4)
0x74: 0x00000000 (PR0)
0x78: 0x00000000 (PR1)
0x7C: 0x00000000 (PR2)
0x80: 0x00000000 (PR3)
0x84: 0x00000000 (PR4)
0x90: 0x00414004 (SSFS, SSFC)
0x94: 0x5006     (PREOP)
0x96: 0x463b     (OPTYPE)
0x98: 0x05d80302 (OPMENU)
0x9C: 0xc79f0190 (OPMENU+4)
0xA0: 0x00000000 (BBAR)
0xB0: 0x00004000 (FDOC)
Programming OPCODES...
program_opcodes: preop=5006 optype=463b opmenu=05d80302c79f0190
done
SPI Read Configuration: prefetching disabled, caching enabled, OK.
This chipset supports the following protocols: FWH,SPI.
No IT87* serial flash segment enabled.
Calibrating delay loop... 1995M loops per second, 10 myus = 11 us, 100 myus = 102 us, 1000 myus = 1002 us, 10000 myus = 10006 us, OK.
Probing for AMD Am29F010A/B, 128 KB: skipped.
Probing for AMD Am29F002(N)BB, 256 KB: skipped.
Probing for AMD Am29F002(N)BT, 256 KB: skipped.
Probing for AMD Am29F016D, 2048 KB: skipped.
Probing for AMD Am29F040B, 512 KB: skipped.
Probing for AMD Am29F080B, 1024 KB: skipped.
Probing for AMD Am29LV040B, 512 KB: skipped.
Probing for AMD Am29LV081B, 1024 KB: skipped.
Probing for ASD AE49F2008, 256 KB: skipped.
Probing for Atmel AT25DF021, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF041A, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF081, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF321, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF321A, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25DF641, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25F512B, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25FS010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT25FS040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT26DF041, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT26DF081A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT26DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT26DF161A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT26F004, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT29C512, 64 KB: skipped.
Probing for Atmel AT29C010A, 128 KB: skipped.
Probing for Atmel AT29C020, 256 KB: skipped.
Probing for Atmel AT29C040A, 512 KB: skipped.
Probing for Atmel AT45CS1282, 16896 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB011D, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB021D, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB041D, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB081D, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB161D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB321C, 4224 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB321D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT45DB642D, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Atmel AT49BV512, 64 KB: skipped.
Probing for Atmel AT49F002(N), 256 KB: skipped.
Probing for Atmel AT49F002(N)T, 256 KB: skipped.
Probing for AMIC A25L40PT, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for AMIC A25L40PU, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for AMIC A29002B, 256 KB: skipped.
Probing for AMIC A29002T, 256 KB: skipped.
Probing for AMIC A29040B, 512 KB: skipped.
Probing for AMIC A49LF040A, 512 KB: skipped.
Probing for EMST F49B002UA, 256 KB: skipped.
Probing for Eon EN25B05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B05T, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B10T, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B20T, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B40T, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B80T, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B16T, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B32T, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25B64T, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25D16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN25F32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Eon EN29F010, 128 KB: skipped.
Probing for EON EN29F002(A)(N)B, 256 KB: skipped.
Probing for EON EN29F002(A)(N)T, 256 KB: skipped.
Probing for Fujitsu MBM29F004BC, 512 KB: skipped.
Probing for Fujitsu MBM29F004TC, 512 KB: skipped.
Probing for Fujitsu MBM29F400BC, 512 KB: skipped.
Probing for Fujitsu MBM29F400TC, 512 KB: skipped.
Probing for Intel 28F001BX-B, 128 KB: skipped.
Probing for Intel 28F001BX-T, 128 KB: skipped.
Probing for Intel 28F004S5, 512 KB: skipped.
Probing for Intel 28F004BV/BE-B, 512 KB: skipped.
Probing for Intel 28F004BV/BE-T, 512 KB: skipped.
Probing for Intel 28F400BV/CV/CE-B, 512 KB: skipped.
Probing for Intel 28F400BV/CV/CE-T, 512 KB: skipped.
Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for Macronix MX25L512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L1005, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L2005, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L4005, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L8005, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L1605, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L1635D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L3205, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L3235D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L6405, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX25L12805, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix MX29F001B, 128 KB: skipped.
Probing for Macronix MX29F001T, 128 KB: skipped.
Probing for Macronix MX29F002B, 256 KB: skipped.
Probing for Macronix MX29F002T, 256 KB: skipped.
Probing for Macronix MX29LV040, 512 KB: skipped.
Probing for Numonyx M25PE10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Numonyx M25PE20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Numonyx M25PE40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Numonyx M25PE80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Numonyx M25PE16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV020, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm25LV512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC Pm29F002T, 256 KB: skipped.
Probing for PMC Pm29F002B, 256 KB: skipped.
Probing for PMC Pm39LV010, 128 KB: skipped.
Probing for PMC Pm39LV020, 256 KB: skipped.
Probing for PMC Pm39LV040, 512 KB: skipped.
Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for Sanyo LF25FW203A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for Spansion S25FL008A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Spansion S25FL016A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for SST SST25VF016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Chip status register is 00
Chip status register: Block Protect Write Disable (BPL) is not set
Chip status register: Auto Address Increment Programming (AAI) is not set
Chip status register: Bit 5 / Block Protect 3 (BP3) is not set
Chip status register: Bit 4 / Block Protect 2 (BP2) is not set
Chip status register: Bit 3 / Block Protect 1 (BP1) is not set
Chip status register: Bit 2 / Block Protect 0 (BP0) is not set
Chip status register: Write Enable Latch (WEL) is not set
Chip status register: Write In Progress (WIP/BUSY) is not set
Resulting block protection : none
Found chip "SST SST25VF016B" (2048 KB, SPI) at physical address 0xffe00000.
Probing for SST SST25VF032B, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for SST SST25VF040.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x41
Probing for SST SST25VF040B, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for SST SST25VF040B.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x41
Probing for SST SST25VF080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for SST SST28SF040A, 512 KB: skipped.
Probing for SST SST29EE010, 128 KB: skipped.
Probing for SST SST29LE010, 128 KB: skipped.
Probing for SST SST29EE020A, 256 KB: skipped.
Probing for SST SST29LE020, 256 KB: skipped.
Probing for SST SST39SF512, 64 KB: skipped.
Probing for SST SST39SF010A, 128 KB: skipped.
Probing for SST SST39SF020A, 256 KB: skipped.
Probing for SST SST39SF040, 512 KB: skipped.
Probing for SST SST39VF512, 64 KB: skipped.
Probing for SST SST39VF010, 128 KB: skipped.
Probing for SST SST39VF020, 256 KB: skipped.
Probing for SST SST39VF040, 512 KB: skipped.
Probing for SST SST39VF080, 1024 KB: skipped.
Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0xbb, id2 0x5d, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for SST SST49LF020, 256 KB: skipped.
Probing for SST SST49LF020A, 256 KB: skipped.
Probing for SST SST49LF040, 512 KB: skipped.
Probing for SST SST49LF040B, 512 KB: skipped.
Probing for SST SST49LF080A, 1024 KB: skipped.
Probing for SST SST49LF160C, 2048 KB: skipped.
Probing for ST M25P05-A, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P05.RES, 64 KB: Ignoring RES in favour of RDID.
Probing for ST M25P10-A, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P10.RES, 128 KB: Ignoring RES in favour of RDID.
Probing for ST M25P20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P40-old, 512 KB: Ignoring RES in favour of RDID.
Probing for ST M25P80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M25P128, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST M29F002B, 256 KB: skipped.
Probing for ST M29F002T/NT, 256 KB: skipped.
Probing for ST M29F040B, 512 KB: skipped.
Probing for ST M29F400BT, 512 KB: skipped.
Probing for ST M29W010B, 128 KB: skipped.
Probing for ST M29W040B, 512 KB: skipped.
Probing for ST M29W512B, 64 KB: skipped.
Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for ST M50LPW116, 2048 KB: skipped.
Probing for SyncMOS S29C31004T, 512 KB: skipped.
Probing for SyncMOS S29C51001T, 128 KB: skipped.
Probing for SyncMOS S29C51002T, 256 KB: skipped.
Probing for SyncMOS S29C51004T, 512 KB: skipped.
Probing for TI TMS29F002RB, 256 KB: skipped.
Probing for TI TMS29F002RT, 256 KB: skipped.
Probing for Winbond W25Q80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25Q16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25Q32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W25x64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Winbond W29C011, 128 KB: skipped.
Probing for Winbond W29C020C, 256 KB: skipped.
Probing for Winbond W29C040P, 512 KB: skipped.
Probing for Winbond W29EE011, 128 KB: skipped.
Probing for Winbond W39V040A, 512 KB: skipped.
Probing for Winbond W39V040B, 512 KB: skipped.
Probing for Winbond W39V040C, 512 KB: skipped.
Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080A, 1024 KB: skipped.
Probing for Winbond W49F002U, 256 KB: skipped.
Probing for Winbond W49V002A, 256 KB: skipped.
Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content
Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content
Probing for Atmel unknown Atmel SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for EON unknown EON SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Macronix unknown Macronix SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for PMC unknown PMC SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for SST unknown SST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for ST unknown ST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Sanyo unknown Sanyo SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Generic unknown SPI chip (RDID), 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541
Probing for Generic unknown SPI chip (REMS), 0 KB: probe_spi_rems: id1 0xbf, id2 0x41
===

Eamon


Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 18, 2013, 07:13:23 am
Ok, wonder why it didn't work the first time? Hmm.
Never mind, now you can read out the bios file and open it with a bios editor to see if it holds any secrets. It probably won't to be honest. Only the X-Core box had the ability to set the arm/disarm led status from the bios. It will let you see how easy it would be to unlock the bios menus. On the XTM5 it was simply a matter of changing to default access level but it was high risk as you've probably read in the xtm5 thread.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 18, 2013, 09:19:08 am
Yeah.. I think I might have downloaded the 64bit package when I was in fact running the 32bit nanobsd build - having tried so many different builds :P

Ok I've got the BIOS saved to disk, what do I use to open it and have a look, modbin6 from the freedos image?

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 18, 2013, 10:10:18 am
No, modbin6 only works for Award bioses.
You have to use an AMI bios editor, there are several, none of them work very well!  ::)
There is a patched version of AMIBCP that sort of works. MMTool can extract/replace bios modules.
None of them are too easy to get hold of I recal.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 18, 2013, 10:13:45 am
Ah ok, I found this... www dot bios-mods dot com/downloads/

Eamon

Edit: Hyperlink removed.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 18, 2013, 10:20:30 am
Yeah that looks good. 3.13 is the version I have.
Perhaps not a great plan to link there from the forum. Don't want to bring down any heat on the dev team.  :)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 19, 2013, 05:09:28 am
I checked the XTM5 bios and it reports:
Code: [Select]
AMIBIOS 080015  02/03/10(C)2006
So that looks like it's bios core version 8.00.15 which is the same as yours (see your first screenshot). The only difference is that yours is twice the size.
I found a copy of amibcp 3.51, which is the most recent I could find, and it still couldn't open your rom file. All those amibcp programs are dated 2008 though so none are terribly new. There are v4 available but I'm lead to believe they are for much newer efi bioses.
Edit: Yep V4.53 can't open any files I have here.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 19, 2013, 07:31:10 am
I'm thinking the bios dump is somehow wrong.

Had a bit of a dig around the Watchguard support site and I found this on the XTM 8

Hardware Specifications
                                XTM 8 Series
Processor                   2 .66 GHz Quad Core
Memory: Flash            1 GB
Memory: RAM             2 GB


Now that's either the BIOS flash memory or the compact flash card.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 19, 2013, 08:17:11 am
It's the CF that's 1GB. A 1GB BIOS would be huge!  ;)

I agree the most likely thing seems to be that the image is corrupt. That could have happened during extraction, a flashrom problem, or during transfer or something else.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on May 19, 2013, 08:29:16 am
Haha!! that's what I get for looking at the specs when I'm half awake!!

Ok so how do I get the BIOS saved properly? I did flashrom -r file.bin then I downloaded it via the pfSense webgui.

Is there a better way?

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on May 19, 2013, 01:23:26 pm
Hmm. Ok. Sometimes your web browser can try to interpret files.
When extracting the bios from the XTM5 I used a filename that was filename.rom and I transfered it via SCP using WinSCP (http://winscp.net/eng/index.php).

To check the file integrity you can generate an MD5 sum for it on the box and then on your windows machine or where ever you put it.

Code: [Select]
[2.1-BETA1][root@pfsense.localdomain]/tmp(3): flashrom -r backup.rom
flashrom v0.9.5.2-r1515 on FreeBSD 8.3-RELEASE-p8 (i386), built with libpci 3.1.9, GCC 4.2.1 20070719  [FreeBSD], little endian
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Found chipset "Intel ICH7/ICH7R". Enabling flash write... OK.
Found ST flash chip "M25P80" (1024 kB, SPI) at physical address 0xfff00000.
Reading flash... done.
[2.1-BETA1][root@pfsense.localdomain]/tmp(4): md5 backup.rom
MD5 (backup.rom) = fcefa2906d7c3179264a8528ba0a7cea

I use WinMD5 (http://www.winmd5.com/) to check it after transfer.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on June 02, 2013, 06:48:59 am
Ok so as it stands my XTM 8 is locked in a never ending bios reboot due to a "CMOS Checksum Bad" error :(

How this happened is as follows:

I had flashed the Lanner FW-8750 firmware to the board - flashrom0.9.2 gave an error and to get on irc.

I spoke with idwer/stefan and a couple of other flashrom devs who were kind enough to compile the lastest flashrom (0.9.6.2 - I think) for pfsense 2.0.3 (many thanks guys).

However before that had come through, I flashed back the back up Bios - got the same error - rebooted and the XTM 8 was back to how it was from the factory ie bios locked but working.

I then followed the Lanner reps advice and used AFUDOS to flash the Lanner bios, which reported it had flashed successfully! and thats how I got to the never ending bios reboot :(

So at the moment I'm waiting on a SPI programming board to arrive from the US so I can flash the bios via the SPI header.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 02, 2013, 08:21:34 am
Yikes, that's a message you never want to see.  :o

Although the xtm8 is based on the 8750 is not an 8750, there are hardware differences that may mean the standard BIOS cannot work. Though I can't think what they might be.

Failed CMOS checksum is a fairly standard error after updating the BIOS. I take it you've tried clearing the cmos or trying to load the default values. I'm sure the flashrom guys will have discussed that.

You can always try the 4 resistors like I did.  ;)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on June 02, 2013, 08:28:53 am
No it's not the message I wanted to see either!

The bios they sent was after I had supplied the serial number and board model/version so one would assume it would match!

Yeah I've cleared the cmos, it won't allow me to get into the bios which is the worst part :(

I'm avoiding the 4 resistors and going for a proper SPI programmer ;)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 02, 2013, 09:00:01 am
More patient than me.  :)
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on June 02, 2013, 09:02:22 am
Not really, I just hate soldering ;)
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on June 14, 2013, 01:15:28 pm
Looks like I'll have to go the soldering route :(

I've tried the BlackCat SPI programmer but it just won't recognise the rom even though it supports it :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 14, 2013, 01:17:39 pm
Is the ROM chip powered? How does it connect?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on June 14, 2013, 01:21:11 pm
The rom chip is powered when the unit is in standby.

The SPI programmer connects directly to the SPI-ROM header on the motherboard. I've tried it every which way but no joy :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 14, 2013, 01:28:37 pm
Well that's quite disappointing. A long wait for no result.  :(
Good luck with the soldering. :)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 13, 2013, 11:00:38 am
My XTM 510 is flashed with unlocked BIOS, thanks @ stephenw10. It works like a charm with pfsense.
Now i have two XTM 810 and will try to run pfsense on them. I want to get into the BIOS without luck.
Can someone tell me the correct serial settings for that and has someone a unlocked BIOS running?

greetz from Germany


edit:
Get into Bios with keyboard connected to the XTM 810 and del key ok.
Now i try to make a cf with pfsense and run it and make a Bios backup file.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 13, 2013, 12:32:28 pm
Excellent. If you could post your success flashing the bios in the xtm5 thread that would be great.

I hope you have read through this whole thread. Eams discovered to his misfortune that the flashrom program is not compatible with the eprom in the xtm8. I think he also struggled using a dos flasher. I suggest you make sure you can read/write the chip via the SPI header before experimenting. ;)

No one has manger to get pfSense running on an xtm8 yet. One of the problems is that the console port is com2 and the Nano pfSense images are hardcoded to use com1.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 13, 2013, 12:41:15 pm
Yes, nano bsd image do not boot.
I do not have spi, but two XTM 8. If something goes wrong i have a second chance :-)

I think to install pfsense to the cf with a vm on a esxi server.
I report my experiences.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 13, 2013, 08:01:26 pm
Please keep us updated with anything you find.  :)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 14, 2013, 06:24:45 am
Update
I was able to boot freedos and make a backup of my XTM810 bios.
Test to flashback the bios was ok. But i can not load the bios in any editor i found. :-(
Here is a link if someone need it.

http://uploaded.net/file/kzeu66vy

Can someone tell me a tool to look into the bios?

Now i made the original XTM OS image on the cf and boot the box with logging in putty. Here is the output file.

http://ul.to/jxmxmvul
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 14, 2013, 03:24:43 pm
How did you boot FreeDOS? Using com2 using a video card? I'm not sure if Eams ever managed to boot it.
The log is interesting, you'll notice it's on ttyS1 but the pfSense images are hardcoded for ttyS0. At least I believe they use the I/O and memory addresses directly. One possible solution to that would be to swap those addresses in the BIOS if it can be unlocked.

If you read back through the thread you'll see we had trouble opening the file also. It seems the BIOS file is available in two types, the bios code itself and a container file than has additional information. The bios editors can only open the code and not the container. By opening the larger file in the hex editor and comparing it to a known bios file I was able to remove the code from the container and open it in amibcp but I have no idea if it can be put back into the container.

Steve

A page referencing the two file types can be found here (http://www.tyan.com/tech/clear_cmos.aspx). Of course it doesn't apply directly.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 15, 2013, 02:18:45 am
I was able to open my bios backup file in a Windows XP VM with "MMTOOL V3.22 BKMOD".
It show me the correct Bios Version and many things. So i think the Bios is ready to edit but i don' t know what to do.
I hope it is a step forward :-)
Here is a screenshot from this tool.

http://ul.to/2c1k11h0

I booted freedos from the CF, but it only boot with an option at boot time.
F8 to use single step boot and than esc key brings me to a prompt. Than dir to the bios folder where i have copied the afudos.exe.
This works fine, i made the backup and i flashed the backup to test. Always with no errors.
When i find the time today i make pictures from the boot and bring it online.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 15, 2013, 06:08:48 am
Interesting.
So are you using a usb keyboard? A video card in the box? I assume you aren't using serial since I don't think afudos would work.  :-\

You have to use AMIBCP to edit the bios parameters, MMtool is for adding or removing modules. It's interesting that your backup file is 1MB. All the backup files we have from other methods are 2MB which causes problems. Given that your file is only 1MB you should be able to open it in AMIBCP. I'll download your backup file and try it.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 15, 2013, 06:59:21 am
I don' t use vga card. I try it with the vga connector but i  don 't know the right pins i have to connect to the vga cable.
All i have done is with serial connection via RS232 and putty on 115200 baudrate.
All done with a USB Keyboard connected to XTM810.

My backup will not load in amipcb.  :(

I have made a video how i get the bios file. The Upload is very huge and takes an hour.

http://youtu.be/S7ZGi3sCJDQ
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 15, 2013, 09:46:10 am
Ah! Thanks for that.  :)
So you're using the freedos image I posted but interrupting the boot process before it switches to serial console. This relies on the bios serial redirect code to function. Worth baring in mind if you ever change anything, serial port parameters, redirect settings etc.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 15, 2013, 10:32:43 am
I downloaded your bios backup file and it opened fine in AMIBCP 3.46.  :)
Here is a modified version: https://sites.google.com/site/pfsensefirebox/home/xtm8v1.rom
The only thing I have done is changed the user access level defaults from 2 (limited) to 3 (full). The MD5 of the file is f831c43035334db94f070644ca272380. I did try to add some text but it didn't like that so I that's the only change I've made.

Obviously you flash this at your own risk!

Steve

Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 15, 2013, 11:09:37 am
Flashed your bios successfully.
Try to boot freedos after flashing was ok, the box is still ok.
Look into Bios still locked, i now have removed CMOS battery and wait 10 Minutes.

I report soon.

Many Thanks for your great work steve!

Edit:

It' s done steve, bios is unlocked and the "view only" crap is gone :-)
But in redirect it shows only com2, there is no option to change it in anything else.

Here is a screen from that menu.

http://ul.to/feznohzh

Can you tell me where the access level in amibcp is that you had modyfied?

If i can anything to try out commands or something elsa let me know.



Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 15, 2013, 12:29:44 pm
Ah yes, sorry, I should have said you need to clear the cmos to force it reload the default values including the new user access level.

The setting for that is in the first tab in amibcp (edit: Setup Configuration) where you can select the bios menus. It's in the security menu. Nothing there is labelled or has any explanation of the different settings.

You don't want to choose anything other than com2 for the redirect because that's the only serial port on the box. The standard Lanner box it's based on has a com port for console access on the front and that's com1. No idea why Watchguard didn't want it. Anyway com1 is not present in the XTM8 so it's disabled in the bios. It may be possible to swap com 1 and 2 by simply reassigning their resources and thus allow pfSense nano image to boot correctly. Usually com ports are assigned a standard set of resources (http://en.wikipedia.org/wiki/COM_%28hardware_interface%29), if you reassign com2 to have I/O address 0x3f8 and IRQ 4 there's a good chance that nanobsd might use it. There's also a good chance it will break console redirection!  ;) However you can always clear the cmos to get back to a working state.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 16, 2013, 09:22:17 am
Change to 3f8 and IRQ 4 but nano image of pfsense still not boot.
I tried for a test to boot from a usb stick with a ESXi on it. It shows me the initial of the boot process, so it' s able to boot usb sticks.
Later i test to boot a debian netinstall and a pfsense live image on usb stick.

I think i must become the vga output to work. But i recognize not the right pin settings and i read that not all monitors allow this.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 16, 2013, 01:15:33 pm
Damn.  :(
You could try changing the redirect to 9600bps. It may be that the two processes are conflicting. Even try disabling console redirect completely. You'll have to reset the cmos afterwards to get back to the bios defaults if it doesn't work. I doubt it will since the XTM5 has those settings and it doesn't cause a problem.

Annother possible way to go would be to re-programme the superIO chip to change which com port is com1. That might cause problems with the console redirect function though. Looking at the bios strings it seems all references to com1 have been removed from it.

The VGA header is standard VGA, any monitor should be able to display it. The problem is finding a suitable header cable. The 20pin header is 2mm pitch rather than the much more common 2.54mm (0.1"). You'll see that Eams did it by connecting individual wires directly to the header and using only green.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 16, 2013, 04:36:12 pm
Ok, now i have the green screen :-)
Booted my pfsense install that i have done in a vm and it gives me an error to mount root from ufs:/dev/da0s1a
I think this is a failure trough install in a VM on the CF attached via usb.
Than i tried to boot a VMware ESXi installation by the same way. This i have done many times to usb sticks that later boot the VM ESXi Server.
It loads without errors and it shows me all NICs that the box have. Even from the doughter board.
Tomorrow i will soldering the vga cable and try to install pfsense a better way. Or to change the boot entry. But iam not so familar with bsd. In debian i came from i know there is a /etc/fstab where all the boot things are in.

Before i forget it, i find out that the hdd led only lit when the cf is booting. When i boot from HDD it is never on, but on my screen via vga cable i could see the boot process.
And another interesting thing, i opened my bios backup and looked a little around the menus and entrys. I found there a entry with console redirections on 9600 baudrate. But bios is reachable with 115200 baudrate. Can it be a conflict with pfsense?
 

Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 16, 2013, 05:39:59 pm
Possibly, might as well change it and see.

I'm a bit confused about the mountroot error. That should never happen with one of the nanobsd images which always expect to be on ad0. What did you write to the CF card and how?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on September 16, 2013, 11:54:06 pm
Oh sorry, thats not a nano image. This i have installed with a live cd from pfsense to a sata hdd not a cf card in a vm.
And i think thats the reason for the faulty boot path.

Later i will try to bring the pfsense live image to the cf card and boot the box with that. A install to the hdd connected to the sata port could be possible.

I dont want to change more things in the bios file and flash. I think it is good to be unlocked, but every flash is risk.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 18, 2013, 01:17:40 am
After month of no time to bring up and running pfsense on a XTM 8 device, yesterday i found a way how it works!
A detaild setup i will bring up next year in a blog.
What i found is:
Boot nano image not working.
Box only boots from CF or HDD, USB not bootable.
I attached a ssd with a win7 installation and it boots, really nice with a green vga output ;-)
Attached a Live installation hdd boot, but it fail by wrong fstab entry.
The XTM8 will boot from /dev/ad8s1a or /dev/ad8s0a, i can not remember now. But in the afternoon i tell the correct entry.
After setup and boot the live installation in a second box (PC) and edit the fstab by:
mounting / rw
editing with vi the /etc/fstab to the right entry
poweroff the second box and attaching the hdd to the xtm8 and it boots correctly

The nano image from cf, i think had same problems. I will test it with same way.

Title: Re: Watchguard Firebox XTM 8 Series
Post by: Darkk on December 18, 2013, 09:45:28 am
Sweet!! Keep us posted!!
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 18, 2013, 09:50:24 am
Sweet indeed.  ;)
These boxes are unfortunately so rarely available second hand that I doubt I'll get my hands on one to play with any time soon.  :(
I'll just keep looking....

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 18, 2013, 11:24:42 am
OK, the xtm8 now boot pfsense from cf.
I installed the cf to a igel thin client, connect a usb cdrom and install pfsense to it with Live CD.
Found the correct entry for fstab and edit it with vi.
Put the cf in the XTM8 and boom ;-)

Here the correct entrys:
HDD connected to internal sata: /dev/ad8s1a
CF Card: /dev/ad10s1a

Can someone tell me why such numbers and not ad0s1a like default?

Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 18, 2013, 02:25:30 pm
It's just down to the order in which they are initialised. If the board has a few SATA interfaces the numbers start adding up quick. Still ad10 is surprising.
You shouldn't really run a full install (or anything except Nano) from a CF card. The writes may kill it.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 18, 2013, 02:42:22 pm
Find it!
I had changed the bios ide settings to ahci.
Turn it back to ide it brings me the fault fstab entry. Turn back to ahci is working with the ad10s1a.
Now i have to find the correct entry for ide mode.

@steve
is it possible to change the bios for a pfsense in display?

Edit:

in ide mode
cf: /dev/ad7s1a

Now the question stay on ahci or change to ide and edit fstab to ad7?
And is there a way a nano install to change to correct fstab settings?

Will try it with my Igel Thin Client.


Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 18, 2013, 02:57:25 pm
It is possible but it's risky.
On the XTM5, which has a very similar bios, I managed to produce corrupted bios images a number of times. The only way to recover from that was to flash the bios ROM directly via the spi header but that does not work on the XTM8 as Eams found. So if the image turns out corrupt it's going to brick the box.  ;)
To do it you have to extrct the bios modules from the rom image, edit the correct one with a hex editor and then rebuild the image.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 18, 2013, 03:13:12 pm
ok, i let this bios. now flashed the second box with this bios to work on the nano installation and modifying the fstab on nano image. Hope i found the way to do it.

No way with nano image. It only brings a flashing prompt after bios. No output, nothing. Looks like it not looking for a bootloader.
But other things booting.

Write the nano image with win32diskimager on the cf. In my xtm5 the nano cf is booting without problems..
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 18, 2013, 05:51:06 pm
As soon as the bootloader runs the console will switch to com1 which as we've seen doesn't exist on the xtm8. It should boot a cf card that has had interfaces already configured though, assuming the configuration is compatible with the box.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 19, 2013, 01:03:16 am
I can say that a 32 bit nano image run in the Igel Thin Client. Put it in the xtm8 but the orange led for hdd not flash. When running the full install on cf the led is flashing all the boottime. I Think this is a indicator that the nano image will not try to boot.


Edit:

Try now pfSense-2.1-RELEASE-1g-i386-nanobsd_vga.img.gz and it is booting without any problem!
Boottime is very fast!

Can this point to a kernel problem?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 19, 2013, 05:55:36 am
I think it's likely that the standard Nano image attempts to write to the non-existent com1 and crashes. The only way around that seems to be either:
1. Reprogram the rear com port to be com1
or
2. Build a Nanobsd image that is coded to use com2

I'm not sure what determines which port is seen as com1. It may be possible to switch them by altering the superIO chip register settings for example. More research needed.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 19, 2013, 07:28:11 am
The easy way is to use a nano_vga image. You only have to download it, write it to the cf and all is fine.
With monitor on vga header it can be configured. The console at start works on same settings with bios output (115200). At the Point after the question how to boot (default, acpi disabled . . .) the console shows nothing. Tried all settings in bios, tried to change baudrate to 14400 in pfsense. Nothing helps.

This is my plan!
I will now close my first box, it is ready.
Make the second box up running pfsense 64 bit vga nano too.
Make a default configuration with em0 (dhcp use) for wan.
Make a backup from this cf.
Upload it for everyone need it.

Than if need new install this must be the way:
write the backup to cf
boot the box with em0 (wan) connected to router
wan becomes an ip from the router dhcp
connect a usb keyboard
without see anything:
"8" for shell
"pfctl -d"
to disable firewall and connect to em0 IP that can be found in the router
configure pfsense with own settings for wan and lan.


Correct me if there is a better way.
Think it is the only fast way without vga output to bring pfsense on it.

For me, it s done!
 
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 19, 2013, 09:09:55 am
If you configure only one interface, WAN, then that is the only way to access the webgui so the default firewall rule is there. There is no need to disable the firewall from option 8. However as soon as you add another interface the default rule moves to LAN.
If you are going to create a new image you could just start out with two interfaces defined, WAN and LAN, which would avoid any console configuration. That's how the Alix box works out of the box.

You could also try to set the comconsole to com2 after boot which would be useful.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 19, 2013, 09:35:55 am
 Need a little hint to doing that set console output to com2. Aborting boot process and than on the cli and there with set command? If this doing a output to com there is no need to do a backup image.

Edit:

Found it!
With 7 interrupt boot
set console=comconsole [Enter]
change putty from 118200 to 9600 and hit [Enter]
boot [Enter]

boot and output via console ;-)

Now there is no need to make backup.
With this info everyone can install pfsense on it.
I think there is no need to flash the original bios.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 19, 2013, 10:28:59 am
:-( console output ends with "Bootup complete"

i attached a bootlog
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 20, 2013, 12:47:32 am
I made the backup with lan interface configured to a static ip and dhcp server on. Good to know, when configure em0 to wan and em1 to lan, than em0 is port0 and lan is port 4 of interfaces in front of the Watchguard XTM 8 Series.  ;)
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 20, 2013, 05:49:25 am
Hmm, that's slightly odd about the ports being 1 and 4. The numbering in pfSense is determined by he order in which they're probed..

I'm confused as to what you did to get that bootlog, I've forgotten quite where we were.  ::)
So firstly it includes some information about the serial redirect module which is something I've not seen on any other box.
I assume that you got this from the rear com port whilst booting the Nano-VGA image. In which case I think it's safe to assume that it only got there by being redirected by the module (which is set to continue after boot). That could explain why you don't see anything after 'bootup complete'. The redirect module can only handle basic text so perhaps the menu is drawn in some way that it can't handle?

See: https://www.freebsd.org/doc/handbook/serialconsole-setup.html#serialconsole-com2
Seems to imply that simply selecting the I/O address of the port selects the com port. That's why I was hopeful that changing the port address in the bios would suffice. It seems not.  :-\

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 20, 2013, 01:59:11 pm
Yes, its from the rear com port. Baudrate 118200 is showing system initializing and bios and the first boot process only to the question how to boot. At this point the boot must interupt with 7 and tell the box to use comconsole for output. After this command the baudrate must set to 9600 and it is showing the rest and stops with "Boot completed".

But now we know the way and i think with my backup from the default installation there is no need to do complete serial output. But i will test more in the new year.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on December 20, 2013, 04:45:09 pm
Ah, maybe similar to the serial quirk then:
https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Serial_Port_Quirk
In the X-core box that stops in exactly that place.

Even if it's not necessary to have access to the serial console it's very useful to have it in case you are locked out of the webgui.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: angelkiller on December 21, 2013, 11:40:00 am
Not at home for christmas. Will test it in a few days.

merry xmas!
Title: Re: Watchguard Firebox XTM 8 Series
Post by: _Adrian_ on February 27, 2014, 11:41:19 am
Any updates ???

I'm looking at an XTM810 and would like to know the ins and outs which seem it may need a bit a messin about but the end product is well worth it!
Title: Re: Watchguard Firebox XTM 8 Series
Post by: ScottMcNaught on June 02, 2014, 09:09:52 am
Hey guys,

I have recently bought an XTM 810.  I can get it to boot but I lose video & console input. 
Can see boot loader, can see first pfSense options menu, after this I lose video and it continues to boot completely with the startup noise.  (The video and input disappear after the first pfSense options menu.)

So I press 7 to exit to shell.  But when I type:
set console=comconsole

... I lose all video and control.  This is noted to be due to it redirecting output to COM1 which is a blank header at the front of the board.  COM2 at the back as discussed.  Note: I have tried Putty at 9600 and tried comconsole_speed="115200" in /boot/loader.conf and /boot/loader.conf.local.

My question is:  How did you get it to use COM2 instead of COM1?


On another note, angelkiller, if you get stuck at the step "Bootup complete", on other Watchguard products, as a work around with this serial quirk you can Control+C the bootup right before "Bootup complete", and then run /etc/rc.initial via command.  This will give you the configuration menu and allow you to setup the interfaces and IP addresses.


Cheers,
Scott
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 02, 2014, 10:40:07 am
Replied to your PM before I read this.  ::)
I don't think anyone has got com2 to work yet, Angelkiller used a Nano+VGA image I think. However JimP rcently posted a possible method for changing com ports:
https://forum.pfsense.org/index.php?topic=76382.msg418066#msg418066

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: ScottMcNaught on June 11, 2014, 02:01:48 am
Hey Guys,

I bought off eBay this item: http://www.ebay.com/itm/VGA-Graphics-Card-Bracket-Header-Cable-11pin-12P-Small-/150600480861?ssPageName=ADME:L:OC:AU:3160

It makes life so much easier.  It works with both the XTM 5 and the XTM 8 series.
USB ports work on both devices.  You can access the BIOS etc.

I bought another 4 of these today.  My plan is to case-mod the chassis of all my boxes and permanently add this to the side of the box.  Honestly, it is the best money I have ever spent.

XTM 8 works great out of the box with nano-bsd vga, and this vga header cable.

Cheers,
Scott
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 11, 2014, 07:42:41 am
Thanks for the link. Good to know.  :)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: John McDonnell on June 30, 2014, 07:23:25 pm
I'll have to keep this in mind for down the road. Don't really need VGA as the serial works rather well on the XTM 5, but always nice to have options.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 01, 2014, 04:45:14 am
I'm back!

I see there's been some good activity and progress on here with the XTM 8's now more readily available :)

I'm still stuck with my duff XTM 8 but I now want it working!

I tried various SPI programmers but got nowhere, is my only option to source a bios chip and replace my current one or is there an easier way?

Considering the bios chip is a SMD and therefore it will be very hard to remove/replace :(

Regards
Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 02, 2014, 07:23:47 pm
Welcome back!  ;)
Perhaps you could remind us of your stuation, what have you tried so far. Did you ever try the '4 resistors' parallel port meathod? Have you tried any software other than flashrom?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 04, 2014, 04:50:03 am
Thanks :)

Ok so I flashed the Bios, it gave an error, I tried to reflash it back to normal but no joy, rebooted and now it's in an endless reboot loop without completing POST :(

I never did try the 4 resistor method, would this work do you think?

Unable to try any other software on the XTM 8 as it won't boot to a command prompt :(

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 04, 2014, 05:16:05 pm
When I bricked my xtm5 the 4 resistors/parallel port connection was the only thing that worked. Though I only tried one other thing! I know when you first had trouble you tried various versions of flashrom, any of them show anything different?
Did you try anything other than flashrom via the SPI connector?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: jimkisa on August 06, 2014, 08:09:42 am
Eams thanks for this topic , it's really help me .
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 06, 2014, 03:31:01 pm
No Probs Jimkisa, - stephenw10 helped too :)

Ste,

Flashrom is what got it bricked, so since then I tried a couple of SPI programmers (BlackCat and some other one off ebay - has no name on it but it had good reviews on the net).

The software for both were pretty much garbage and I couldn't get anywhere with them.

Whats needed for the parallel port hack? I might as well give that a try!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 06, 2014, 05:36:16 pm
It's on the website I linked to:
http://rayer.ic.cz/elektro/spipgm.htm
Might have to use the way back machine. The site now seems to be behind some security. (Edit: looks legit. I forgot it's in Czech though!)

You need: a parallel port plug, 4 resistors, a cable/connector to connect to the SPI header and something to solder it together. Perhaps harder to find these days is anything with a parallel port on it to run flashrom. I happened to have an old laptop running FreeBSD 8.1 I was using for pfSense development that fitted the bill.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 07, 2014, 05:02:33 am
Thanks for the link Ste.

The security is just a Captcha form. Get past and the info is all there in Czech!

I did find this thou which looks to be the same http://write-code.blogspot.co.uk/2012/08/parallel-port-spi-flash-programmer-and-unbrick-wm8650.html?m=1 (http://write-code.blogspot.co.uk/2012/08/parallel-port-spi-flash-programmer-and-unbrick-wm8650.html?m=1)

I'll try and give that a go at the weekend.

I think my old laptop has a parallel port on it. If not I've deffo got one on a old Abit VP6 computer I have :)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 07, 2014, 08:38:31 am
That's a good link. I didn't have to use the battery or capacitors since the XTM5 provides that in standby. I believe the XTM8 does too.
You can also try the SPIPGM program under Windows if flashrom doesn't work.  :)

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 11, 2014, 03:06:07 pm
For information to help others, I've attached linked two handy pdf's from Lanner.

Motherboard Spec and Motherboard Layout with Pinouts in the user manual - these are for the Lanner FW-8750 which the XTM 8 is based on (doesn't include the SPI header).

Bear in mind WatchGuard changed/didn't include a few things e.g. COM1, Power Switch Header, Northbridge Fan Header, USB 2 Header, etc..

https://drive.google.com/folderview?id=0B0TOx6iNE-K4Rml0bmduRURuUDg&usp=sharing (https://drive.google.com/folderview?id=0B0TOx6iNE-K4Rml0bmduRURuUDg&usp=sharing)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 11, 2014, 03:16:09 pm
Ste,

I was experimenting with the BlackCat USB programmer I have and one combination of settings detected it was connected to a chip, however it didn't pull up the chip name/number as it is supposed to.

It did however suggest the exact addresses the chip requires for it's functions to read/write etc.. Writing the rom didn't work though :o

Having looked everywhere for the pdf I had of the SPI header pinouts, resulted in no joy. So I've ordered a SOIC Clip I can attach directly to the chip and to the BlackCat programmer, with a bit of luck I should be able to flash it that way.

The parallel port is still an option once I get the SOIC clip, if the BlackCat programmer is fruitless :)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 20, 2014, 02:58:18 pm
Ste,

I've built the 4 resistor parallel port SPI programmer.

SPIPGM gives back FF's when reading and no chip is identified. However it does ay that WH# (I think) needs to be pulled high.

Looking at the SST chip datasheet this looks like pin 3(WH#) needs to be connected to pin 8 (VDD) would that be right?

I'm using 100ohm resistors, but I see the same design but with 145ohm and 150ohm resistors do these need changing you think?

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 20, 2014, 04:45:03 pm
I remember reading the datasheet for the chip in the XTM5 and thinking that I would need to pull some pins one way or the other but in the end I didn't need to. The circuitry provided on the board did enough. Reading back the write protect pin is not conneceted at all on the XTM5 but that didn't seem to be a problem. If you try to pull up the WP pin use a resistor to be safe.

The original developer uses 150Ohm resistors. The value is not critical, they must be sufficiently large that the parallel port doesn't try to sink or supply too much current and the voltages on the pins are able to be distinguished as logic high or low. I used two 150Ohm and two 160Ohm resistors because that's what I had. Going higher is less likely to cause problems as long as you're still orders of magnitude lower than the input/output impedance of the parallel port (which I don't know but is probably ~10KOhms  ;)).

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 21, 2014, 06:29:27 am
Forgot to mention it's important to keep the cable length as short as possible. Long cables can pickup interference and cause problems. My cable was as short as I could make it, ~15cm.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 22, 2014, 08:46:13 am
Thanks for the info Ste.

My lead is about 15cm long too!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 25, 2014, 04:41:15 am
Ok, so I've been trying this out the parallel port hack over the last couple of weekends.

What I've discovered so far - the XTM8 doesn't seem to power the chip when it's in standby - SPIPGM reports chip as unknown.

When the PSU is fully off and the board it's in standby, SPIPGM reports the SST25VF016B chips as being detected but WH# needs to be set to high.

Having connected WP# (Pin3) to VCC (Pin8) and HLD# (Pin7) - still no joy in being able to erase/write to the chip - (in standby or off).

Looks like I have to go the full way and connect a battery and capacitor to complete the circuit as per http://4.bp.blogspot.com/-EN9HFZFkT5Y/UCXczDe11mI/AAAAAAAAARY/64Wap6-FXBM/s1600/simple_diagram.jpg (http://4.bp.blogspot.com/-EN9HFZFkT5Y/UCXczDe11mI/AAAAAAAAARY/64Wap6-FXBM/s1600/simple_diagram.jpg).

More fun and games!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 25, 2014, 06:58:36 am
I pulled out my cable and looked at it again and I do indeed have pins 3, 7 and 8 (VCC, HLD and #WP) on the SPI connector joined. Another, perhaps important difference, is that I have the GND pin connected to pins 18-25 on the parallel port connector, they are strapped together. I have no idea why I did that though I'm sure I was following a diagram from somewhere. 18-25 are all ground anyway but I seem to remember other programmers requiring them externally joined.
The XTM5 and XTM8 are the same generation of hardware from the same manufacturer probably from the same factory. It seems unlikely they would have designed it to use different programming hardware. Not impossible though.  :-\

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 25, 2014, 09:54:29 am
Ste,

I've connected up the GND 18-25 as per your lead.. and it seems to be working!
Chip unlocked.
Chip erased.
Wrote the rom xtm8v1.bin (1024kb) but it errored out at 50% saying 'unexpected end of file'. This is the rom you had posted for a fellow XTM8 owner.
I still have the original 1meg and 2meg roms sent to me by Lanner support so I think I'll try flashing the 2meg one.
 

Things are looking up!

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 25, 2014, 06:02:05 pm
Managed to write the original 2meg rom file, no writing errors - didn't verify.

Added a 1000uf capacitor between GND and VCC/HLD/WH# - wrote ok, verified ok!!

Cleared bios via jumper, booted up - XTM8 does a boot cycle, reboots then sits there and the fans go into a low power mode - thats it, nothing on screen at all :(

Added the battery to between GND and VCC etc - result same as above  >:(

Not sure what else to do apart from unsolder the chip and program it off the motherboard or replace it.

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 25, 2014, 07:26:56 pm
Hmm, interesting about the capacitor.
If the fans are changing speed then that implies at least some bios code is running to reprogram the superio chip.
Where did the 2Mb file come from? Perhaps you're not seeing any output for some reason other than it didn't write to the flash?
What program are you using to write the chip?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 29, 2014, 10:17:45 am
The 2meg rom file came form Lanner direct, they sent me two, one that was 1meg and one that was 2meg.

Currently using SPIPGM.

You're gonna suggest FLASHROM aren't you? Considering this is part of how I got into this mess I suppose it's worth a try!

Tried Flashrom, didn't seem to detect the chip, where as SPIPGM does.

Re-did it with SPIPGM... And it's only come back from the dead!!!

The rom I used was one you had edited back when I first saved the BIOS to disk prior to flashing to try and open up the menus.

I haven't tried going into the BIOS yet - but it did request boot media - stuck in a 4gb flash drive from last year and pfsense booted up!!

Of course it only got to the menu then defaulted to COM1, but after a few mins it did its beeps to confirm it was loaded :)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 29, 2014, 11:00:31 am
Persistence for the win!  ;D
Nice one.

JimP suggested a method for switching the com port even in Nano a while ago you might try that if you can edit the files on the CF card:
https://forum.pfsense.org/index.php?topic=76382.msg418066#msg418066

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on August 29, 2014, 11:04:36 am
Thanks, I'm chuffed I managed to get it back from the dead  ;D

Do I try and update the BIOS to an unlocked one?... haha, might do. Getting COM2 reassigned as COM1 would be handy!

Thanks for your help Ste :)

Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: tojaktoty on November 21, 2014, 12:47:14 am
Hey Guys,

I bought off eBay this item: http://www.ebay.com/itm/VGA-Graphics-Card-Bracket-Header-Cable-11pin-12P-Small-/150600480861?ssPageName=ADME:L:OC:AU:3160

It makes life so much easier.  It works with both the XTM 5 and the XTM 8 series.
USB ports work on both devices.  You can access the BIOS etc.

I bought another 4 of these today.  My plan is to case-mod the chassis of all my boxes and permanently add this to the side of the box.  Honestly, it is the best money I have ever spent.

XTM 8 works great out of the box with nano-bsd vga, and this vga header cable.

Cheers,
Scott



I bought that same item from that seller and just tested the vga connector on a XTM8 and seeing no vga signal on two different monitors. Can't see bios or anything else.

Console interfacing thru minicom I see nano-bsd-vga on the CF start and then console screen freezes once pfsense is booting.

What am I doing wrong with the vga? And is there any fix the COM2 redirection in pfsense?

Is there anything else I am missing?

Otherwise as a last option I may just try to solder on a connector to COM1 on the pcb but is it an active interface that would function in pfsense?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Eams on November 21, 2014, 05:19:04 am
Hi tojaktoty,

So your headache is just beginning!

I've added some extra pictures for the VGA connection - I used a 15 Pin Male to Female VGA adaptor and then some Female to Male PCB adaptors to them connect the motherboard VGA connector to the female end of the VGA connector.

I suspect your VGA header card is wired straight throu, either unsolder the VGA plug end and re do the wires as below or go the makeshift route I did.

Pictures here: https://plus.google.com/photos/115736786050007462202/albums/5874219398935451569 (https://plus.google.com/photos/115736786050007462202/albums/5874219398935451569)

PDF for the VGA header pin out here: https://drive.google.com/folderview?id=0B0TOx6iNE-K4Rml0bmduRURuUDg&usp=sharing (https://drive.google.com/folderview?id=0B0TOx6iNE-K4Rml0bmduRURuUDg&usp=sharing)

Motherboard is:
1 VGA_R
2 Ground
3 VGA_G
4 Ground
5 VGA_B
6 Ground
7 HSYNC_3V N/C
9 VSYNC_3V
10 Ground
11 DD_DATA
12 DD_CLK
 
VGA cable is Pin out: http://en.wikipedia.org/wiki/VGA_connector (http://en.wikipedia.org/wiki/VGA_connector)

I connected green as most monitors usually sync on green or at least they used to - it works.

Soldering on to COM1 on the motherboard isn't going to allow you to do anything as the BIOS is hard set to COM2.

Stick a USB keyboard in at the front, and connect up your monitor as above, and away you go.

Careful if you choose to flash the BIOS it seems to be a little hit and miss shall we say ;)

Once you have the monitor connected, flash pfSense to a card, stick it in and have fun. Mine currently runs nanobsd i386 - I should really stick the 64bit one on someday.


Eamon
Title: Re: Watchguard Firebox XTM 8 Series
Post by: davislg on June 10, 2015, 08:48:00 am
Hello,

I was wandering if anyone could help me get my xtm 8 working. I followed the post above and have the VGA setup working. I have tried installing both 2.2.1 i386 and 2.2.2 amd64 versions of pfsense. I've installed both version fine and everything appears to work from the WAN side. I can ping address to my gateway and to the outside world using both IP and DNS. When I disable the firewall (pfctl -d) i can also ping and access the firewall though ssh from the WAN side. WAN seems to work fine. On the other hand, the LAN is giving me nothing but grief. I cannot get anywhere on the LAN. I've tried pinging and ssh from the firewall out to the LAN and from the LAN into the firewall. I get either host is down or timeout. Cables are all good. I've tested everything I can think of. the only oddity that I can note is that when I look at ifconfig for em1 (where LAN is configured) it says no carrier. I've swapped out the cables with know good cables. I've also tried connecting to 3 different computers, switches, and wifi ap. Nothing seems to work. Any thoughts on this are greatly appreciated.

Thank you,
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 10, 2015, 12:23:23 pm
Hmm, that's weird.
Can you show us the output of 'ifconfig -a'
Do you see carrier on any of the other interfaces if you connect to them? Do you see link LEDs?

By the way it may be possible to do this far more easily now. Since the new ADI boxes are using com2 as their console the commands to change the console are known.  I havent actually tried though.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: davislg on June 11, 2015, 02:34:22 am
Thank you for the response. I think I have it figured out tonight. I had pfSense auto probe for the active ports on LAN and when I looked at the status of the ports in ifconfig, I noticed that it was always +1 (e.g. em1 connected, but em2 would show up as active). So I took this into account and have everything working now. WAN {em0 = em0}; LAN {em0 = em1}.

Although it appears to work, is this correct behavior or is there something else going on? I never had this type of an issue w/ x700, x1250e or any other fireboxes. I'm fine with the setup, just seems odd.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 11, 2015, 06:48:41 am
Hmm, I'm not sure I understand what you're saying there? That sounds very odd. Can you get a screen shot showing this difference?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: davislg on June 11, 2015, 01:44:15 pm
Sure Steve. Please see the attached screen shots showing that LAN is configured on em5 and that em5 has a status of active while em4 (where my ethernet cable is actually connected) shows as no carrier.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 12, 2015, 08:07:20 am
How do you know your cable is connected to em4? The numbers on the case are only really applicable if you're running Linux, maybe even only Watchguards cut down OS.
Are all the interfaces detected as em on the XTM8? The XTM5 has one fxp interface which offsets everything by 1.
Which NICs on the front are which pfSense interfaces is determined only by the order in which they are detected at boot.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: davislg on June 12, 2015, 11:30:26 am
Hi Steve,

It's a good point. All of the interfaces are name em0 through em9. I assumed that they names corresponded to the numbers on the front because when I go into assign the cards it shows the ports I have an ethernet cable connected to as being up.

On an alternate note, what you are suggesting makes sense. In discussions with some other friends and testing, we found that it appears em0 is automatically assigned as wan and excluded from the list on boot. Along with this, we found that the other ports seems to round robin (e.g. label 1 = em 2, label 2 = em3, label 3 = em1, and on the main board: label 4 = em 5 ... label 9 = em4}. So what you're saying about the determination does seem to have little to do with the labels on the front.

Thank you for your help and helping me to understand the setup.

~Davis
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on June 12, 2015, 12:30:04 pm
No problem. If you can document which port equates to which em interface I'm sure other will find that helpful.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: davislg on June 12, 2015, 12:48:33 pm
Of course. What I found when troubleshooting the different network configurations on 2 different XTM 810 firewalls.

Note: I was unable to get WAN to work on anything but em0, although I didn't put a lot of effort into it other than trying to connect once or twice. I planned on using Label0 (em0) anyway and therefore left it at that.

Also, the Labels refer to the the labels on the front of the WatchGuard XTM 8. This is for an XTM 810.

WAN:

LAN (Daughterboard):

LAN (Mainboard):
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pfsmile on February 03, 2016, 12:25:52 pm
hi there,

i got hold of a functioning 810 with working fw:
if someone needs it i can send some files and time to get this box supported as easy asl the x-core models.

a dmesg for example:
Code: [Select]
  Booting 'WatchGuard (SysA)'

root (hd0,2)
 Filesystem type is ext2fs, partition type 0x83
kernel /bzImage ro root=/dev/sda3 console=ttyS1,115200 crashkernel=16M@16M wg_p
tfm=xtm8
   [Linux-bzImage, setup=0x2e00, size=0x242280]

[    0.000000] Linux version 2.6.35.12 (release@cm19se) (gcc version 4.4.5 (WatchGuard Inc./crosstool-ng version: 0.1.5/1.9.0) ) #1 SMP Fri Mar 8 13:44:55 PST 2013
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  BIOS-e820: 0000000000000000 - 000000000009dc00 (usable)
[    0.000000]  BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved)
[    0.000000]  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
[    0.000000]  BIOS-e820: 0000000000100000 - 000000007f6c0000 (usable)
[    0.000000]  BIOS-e820: 000000007f6c0000 - 000000007f6ce000 (ACPI data)
[    0.000000]  BIOS-e820: 000000007f6ce000 - 000000007f6e0000 (ACPI NVS)
[    0.000000]  BIOS-e820: 000000007f6e0000 - 000000007f6ee000 (reserved)
[    0.000000]  BIOS-e820: 000000007f6f0000 - 000000007f700000 (reserved)
[    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
[    0.000000]  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
[    0.000000] Notice: NX (Execute Disable) protection cannot be enabled: non-PAE kernel!
[    0.000000] DMI present.
[    0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
[    0.000000] last_pfn = 0x7f6c0 max_arch_pfn = 0x100000
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] found SMP MP-table at [b00ff780] ff780
[    0.000000] init_memory_mapping: 0000000000000000-000000002effe000
[    0.000000] crashkernel reservation failed - memory is in use.
[    0.000000] ACPI: RSDP 000f9570 00024 (v02 ACPIAM)
[    0.000000] ACPI: XSDT 7f6c0100 0004C (v01 120208 XSDT1015 20081202 MSFT 00000097)
[    0.000000] ACPI: FACP 7f6c0290 000F4 (v03 120208 FACP1015 20081202 MSFT 00000097)
[    0.000000] ACPI: DSDT 7f6c0440 058F4 (v01  1AAAA 1AAAA000 00000000 INTL 20051117)
[    0.000000] ACPI: FACS 7f6ce000 00040
[    0.000000] ACPI: APIC 7f6c0390 0006C (v01 120208 APIC1015 20081202 MSFT 00000097)
[    0.000000] ACPI: MCFG 7f6c0400 0003C (v01 120208 OEMMCFG  20081202 MSFT 00000097)
[    0.000000] ACPI: OEMB 7f6ce040 00071 (v01 120208 OEMB1015 20081202 MSFT 00000097)
[    0.000000] ACPI: GSCI 7f6ce0c0 02024 (v01 120208 GMCHSCI  20081202 MSFT 00000097)
[    0.000000] 1286MB HIGHMEM available.
[    0.000000] 751MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 2effe000
[    0.000000]   low ram: 0 - 2effe000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   Normal   0x00001000 -> 0x0002effe
[    0.000000]   HighMem  0x0002effe -> 0x0007f6c0
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x0000009d
[    0.000000]     0: 0x00000100 -> 0x0007f6c0
[    0.000000] Using APIC driver default
[    0.000000] ACPI: PM-Timer IO Port: 0x808
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[    0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] Allocating PCI resources starting at 7f700000 (gap: 7f700000:7f700000)
[    0.000000] setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 14 pages/cpu @b2800000 s32832 r0 d24512 u1048576
[    0.000000] pcpu-alloc: s32832 r0 d24512 u1048576 alloc=1*4194304
[    0.000000] pcpu-alloc: [0] 0 1 2 3
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 517727
[    0.000000] Kernel command line: ro root=/dev/sda3 console=ttyS1,115200 crashkernel=16M@16M wg_ptfm=xtm8 vmalloc=512M
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Enabling fast FPU save and restore... done.
[    0.000000] Enabling unmasked SIMD FPU exception support... done.
[    0.000000] Initializing CPU#0
[    0.000000] xsave/xrstor: enabled xstate_bv 0x3, cntxt size 0x240
[    0.000000] Subtract (47 early reservations)
[    0.000000]   #1 [0000001000 - 0000002000]   EX TRAMPOLINE
[    0.000000]   #2 [0001000000 - 0001549e44]   TEXT DATA BSS
[    0.000000]   #3 [000154a000 - 0001550193]             BRK
[    0.000000]   #4 [00000ff790 - 0000100000]   BIOS reserved
[    0.000000]   #5 [00000ff780 - 00000ff790]    MP-table mpf
[    0.000000]   #6 [000009dc00 - 00000fc5d0]   BIOS reserved
[    0.000000]   #7 [00000fc814 - 00000ff780]   BIOS reserved
[    0.000000]   #8 [00000fc5d0 - 00000fc814]    MP-table mpc
[    0.000000]   #9 [0000010000 - 0000011000]      TRAMPOLINE
[    0.000000]   #10 [0000011000 - 0000012000]         PGTABLE
[    0.000000]   #11 [0001551000 - 0001552000]         BOOTMEM
[    0.000000]   #12 [0001552000 - 0002542000]         BOOTMEM
[    0.000000]   #13 [0001549e80 - 0001549e84]         BOOTMEM
[    0.000000]   #14 [0001549ec0 - 0001549f80]         BOOTMEM
[    0.000000]   #15 [0001549f80 - 0001549fc8]         BOOTMEM
[    0.000000]   #16 [0002542000 - 0002545000]         BOOTMEM
[    0.000000]   #17 [00015501c0 - 000155023c]         BOOTMEM
[    0.000000]   #18 [0002545000 - 000254b000]         BOOTMEM
[    0.000000]   #19 [0001550240 - 0001550267]         BOOTMEM
[    0.000000]   #20 [0001550280 - 00015503b4]         BOOTMEM
[    0.000000]   #21 [00015503c0 - 0001550400]         BOOTMEM
[    0.000000]   #22 [0001550400 - 0001550440]         BOOTMEM
[    0.000000]   #23 [0001550440 - 0001550480]         BOOTMEM
[    0.000000]   #24 [0001550480 - 00015504c0]         BOOTMEM
[    0.000000]   #25 [00015504c0 - 0001550500]         BOOTMEM
[    0.000000]   #26 [0001550500 - 0001550540]         BOOTMEM
[    0.000000]   #27 [0001550540 - 0001550580]         BOOTMEM
[    0.000000]   #28 [0001550580 - 00015505c0]         BOOTMEM
[    0.000000]   #29 [00015505c0 - 0001550600]         BOOTMEM
[    0.000000]   #30 [0001550600 - 0001550640]         BOOTMEM
[    0.000000]   #31 [0001550640 - 0001550695]         BOOTMEM
[    0.000000]   #32 [00015506c0 - 0001550715]         BOOTMEM
[    0.000000]   #33 [0002800000 - 000280e000]         BOOTMEM
[    0.000000]   #34 [0002900000 - 000290e000]         BOOTMEM
[    0.000000]   #35 [0002a00000 - 0002a0e000]         BOOTMEM
[    0.000000]   #36 [0002b00000 - 0002b0e000]         BOOTMEM
[    0.000000]   #37 [0001550740 - 0001550744]         BOOTMEM
[    0.000000]   #38 [0001550780 - 0001550784]         BOOTMEM
[    0.000000]   #39 [00015507c0 - 00015507d0]         BOOTMEM
[    0.000000]   #40 [0001550800 - 0001550810]         BOOTMEM
[    0.000000]   #41 [0001550840 - 00015508e0]         BOOTMEM
[    0.000000]   #42 [0001550900 - 0001550948]         BOOTMEM
[    0.000000]   #43 [000254b000 - 000254f000]         BOOTMEM
[    0.000000]   #44 [000254f000 - 00025cf000]         BOOTMEM
[    0.000000]   #45 [00025cf000 - 000260f000]         BOOTMEM
[    0.000000]   #46 [0001550980 - 0001550bc0]         BOOTMEM
[    0.000000] Initializing HighMem for node 0 (0002effe:0007f6c0)
[    0.000000] Memory: 2064400k/2087680k available (2608k kernel code, 22820k reserved, 1492k data, 384k init, 1317640k highmem)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfff67000 - 0xfffff000   ( 608 kB)
[    0.000000]     pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
[    0.000000]     vmalloc : 0xdf7fe000 - 0xff7fe000   ( 512 MB)
[    0.000000]     lowmem  : 0xb0000000 - 0xdeffe000   ( 751 MB)
[    0.000000]       .init : 0xb1402000 - 0xb1462000   ( 384 kB)
[    0.000000]       .data : 0xb128c35d - 0xb14013b0   (1492 kB)
[    0.000000]       .text : 0xb1000000 - 0xb128c35d   (2608 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Verbose stalled-CPUs detection is disabled.
[    0.000000] NR_IRQS:384
[    0.000000] Extended CMOS year: 2000
[    0.000000] Console: colour VGA+ 80x25
[    0.000000] console [ttyS1] enabled
[    0.000000] Fast TSC calibration using PIT
[    0.000000] Detected 2660.191 MHz processor.
[    0.010003] Calibrating delay loop (skipped), value calculated using timer frequency.. 5322.06 BogoMIPS (lpj=8867303)
[    0.016669] pid_max: default: 32768 minimum: 301
[    0.020076] Mount-cache hash table entries: 512
[    0.023447] CPU: Physical Processor ID: 0
[    0.026669] CPU: Processor Core ID: 0
[    0.030003] mce: CPU supports 6 MCE banks
[    0.033340] CPU0: Thermal monitoring enabled (TM2)
[    0.036670] using mwait in idle threads.
[    0.040006] Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
[    0.048338] ... version:                2
[    0.050002] ... bit width:              40
[    0.053335] ... generic registers:      2
[    0.056669] ... value mask:             000000ffffffffff
[    0.060002] ... max period:             000000007fffffff
[    0.063335] ... fixed-purpose events:   3
[    0.066668] ... event mask:             0000000700000003
[    0.070330] Freeing SMP alternatives: 16k freed
[    0.073342] ACPI: Core revision 20100428
[    0.086707] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[    0.090300] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.128817] CPU0: Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz stepping 0a
[    0.136666] Booting Node   0, Processors  #1
[    0.013332] Initializing CPU#1
[    0.233427]  #2
[    0.013332] Initializing CPU#2
[    0.333414]  #3 Ok.
[    0.013332] Initializing CPU#3
[    0.433344] Brought up 4 CPUs
[    0.436669] Total of 4 processors activated (21287.06 BogoMIPS).
[    0.444055] NET: Registered protocol family 16
[    0.447098] ACPI: bus type pci registered
[    0.450184] dca service started, version 1.12.1
[    0.453404] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.456669] PCI: not using MMCONFIG
[    0.460138] PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=14
[    0.463334] PCI: Using configuration type 1 for base access
[    0.474743] bio: create slab <bio-0> at 0
[    0.481938] ACPI: Executed 1 blocks of module-level executable AML code
[    0.495014] ACPI: Interpreter enabled
[    0.496668] ACPI: (supports S0 S5)
[    0.500563] ACPI: Using IOAPIC for interrupt routing
[    0.503383] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[    0.513263] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[    0.513335] PCI: Using MMCONFIG for extended config space
[    0.530969] ACPI Warning: Incorrect checksum in table [OEMB] - 0x4B, should be 0x45 (20100428/tbutils-314)
[    0.540653] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.543639] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[    0.547021] pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7]
[    0.550002] pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
[    0.553335] pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
[    0.556669] pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000dffff]
[    0.560002] pci_root PNP0A08:00: host bridge window [mem 0x7f700000-0xdfffffff]
[    0.563335] pci_root PNP0A08:00: host bridge window [mem 0xf0000000-0xffffffff]
[    0.570618] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0a00 (mask 00ff)
[    0.573643] pci 0000:00:01.0: PCI bridge to [bus 07-0e]
[    0.577158] pci 0000:07:00.0: PCI bridge to [bus 08-0e]
[    0.580147] pci 0000:08:00.0: PCI bridge to [bus 0e-0e]
[    0.583568] pci 0000:08:01.0: PCI bridge to [bus 0d-0d]
[    0.586723] pci 0000:08:04.0: PCI bridge to [bus 0c-0c]
[    0.590235] pci 0000:08:06.0: PCI bridge to [bus 0b-0b]
[    0.593567] pci 0000:08:08.0: PCI bridge to [bus 0a-0a]
[    0.600035] pci 0000:08:09.0: PCI bridge to [bus 09-09]
[    0.603585] pci 0000:00:1c.0: PCI bridge to [bus 06-06]
[    0.606891] pci 0000:00:1c.1: PCI bridge to [bus 05-05]
[    0.610223] pci 0000:00:1c.2: PCI bridge to [bus 04-04]
[    0.613557] pci 0000:00:1c.3: PCI bridge to [bus 03-03]
[    0.616889] pci 0000:00:1c.4: PCI bridge to [bus 02-02]
[    0.620069] pci 0000:00:1e.0: PCI bridge to [bus 01-01] (subtractive decode)
[    0.642579] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 11 12 14 *15)
[    0.645966] ACPI: PCI Interrupt Link [LNKB] (IRQs *5)
[    0.647347] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 *11 12 14 15)
[    0.655391] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 *10 11 12 14 15)
[    0.659310] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 *4 6 7 10 11 12 14 15)
[    0.662633] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
[    0.667936] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
[    0.676364] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 6 7 10 11 12 *14 15)
[    0.680453] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[    0.683351] vgaarb: loaded
[    0.686936] SCSI subsystem initialized
[    0.690250] usbcore: registered new interface driver usbfs
[    0.693435] usbcore: registered new interface driver hub
[    0.696737] usbcore: registered new device driver usb
[    0.700318] PCI: Using ACPI for IRQ routing
[    0.703711] Switching to clocksource tsc
[    0.708026] Slow work thread pool: Starting up
[    0.712507] Slow work thread pool: Ready
[    0.716451] FS-Cache: Loaded
[    0.719401] CacheFiles: Loaded
[    0.722481] pnp: PnP ACPI init
[    0.725549] ACPI: bus type pnp registered
[    0.736091] pnp: PnP ACPI: found 15 devices
[    0.740284] ACPI: ACPI bus type pnp unregistered
[    0.744910] system 00:01: [mem 0xfed14000-0xfed19fff] has been reserved
[    0.751525] system 00:01: [mem 0xfed90000-0xfed93fff] has been reserved
[    0.758141] system 00:08: [io  0x0a00-0x0a0f] has been reserved
[    0.764054] system 00:08: [io  0x0a10-0x0a1f] has been reserved
[    0.769974] system 00:08: [io  0x0a20-0x0a2f] has been reserved
[    0.775893] system 00:08: [io  0x0a30-0x0a3f] has been reserved
[    0.781814] system 00:09: [io  0x04d0-0x04d1] has been reserved
[    0.787731] system 00:09: [io  0x0800-0x087f] has been reserved
[    0.793649] system 00:09: [io  0x0480-0x04bf] has been reserved
[    0.799568] system 00:09: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    0.806182] system 00:09: [mem 0xfed20000-0xfed8ffff] has been reserved
[    0.812795] system 00:0b: [mem 0xffc00000-0xffefffff] has been reserved
[    0.819408] system 00:0c: [mem 0xfec00000-0xfec00fff] could not be reserved
[    0.826365] system 00:0c: [mem 0xfee00000-0xfee00fff] has been reserved
[    0.833300] system 00:0d: [mem 0xe0000000-0xefffffff] has been reserved
[    0.839910] system 00:0e: [mem 0x00000000-0x0009ffff] could not be reserved
[    0.846869] system 00:0e: [mem 0x000c0000-0x000cffff] could not be reserved
[    0.853827] system 00:0e: [mem 0x000e0000-0x000fffff] could not be reserved
[    0.860786] system 00:0e: [mem 0x00100000-0x7f6fffff] could not be reserved
[    0.907043] pci 0000:00:1c.0: BAR 15: assigned [mem 0x7f700000-0x7f8fffff 64bit pref]
[    0.914871] pci 0000:00:1c.1: BAR 15: assigned [mem 0x7f900000-0x7fafffff 64bit pref]
[    0.922697] pci 0000:00:1c.2: BAR 15: assigned [mem 0x7fb00000-0x7fcfffff 64bit pref]
[    0.930521] pci 0000:00:1c.3: BAR 15: assigned [mem 0x7fd00000-0x7fefffff 64bit pref]
[    0.938346] pci 0000:00:1c.4: BAR 15: assigned [mem 0x7ff00000-0x800fffff 64bit pref]
[    0.946174] pci 0000:08:01.0: BAR 15: can't assign mem pref (size 0x200000)
[    0.953131] pci 0000:08:09.0: BAR 15: can't assign mem pref (size 0x200000)
[    0.960090] pci 0000:08:00.0: PCI bridge to [bus 0e-0e]
[    0.965314] pci 0000:08:00.0:   bridge window [io  disabled]
[    0.970975] pci 0000:08:00.0:   bridge window [mem disabled]
[    0.976636] pci 0000:08:00.0:   bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
[    0.984374] pci 0000:08:01.0: PCI bridge to [bus 0d-0d]
[    0.989598] pci 0000:08:01.0:   bridge window [io  0xe000-0xefff]
[    0.995691] pci 0000:08:01.0:   bridge window [mem 0xfeb00000-0xfebfffff]
[    1.002475] pci 0000:08:01.0:   bridge window [mem pref disabled]
[    1.008571] pci 0000:08:04.0: PCI bridge to [bus 0c-0c]
[    1.013793] pci 0000:08:04.0:   bridge window [io  disabled]
[    1.019454] pci 0000:08:04.0:   bridge window [mem disabled]
[    1.025111] pci 0000:08:04.0:   bridge window [mem pref disabled]
[    1.031205] pci 0000:08:06.0: PCI bridge to [bus 0b-0b]
[    1.036429] pci 0000:08:06.0:   bridge window [io  0xd000-0xdfff]
[    1.042523] pci 0000:08:06.0:   bridge window [mem 0xfea00000-0xfeafffff]
[    1.049307] pci 0000:08:06.0:   bridge window [mem pref disabled]
[    1.055402] pci 0000:08:08.0: PCI bridge to [bus 0a-0a]
[    1.060624] pci 0000:08:08.0:   bridge window [io  0xc000-0xcfff]
[    1.066718] pci 0000:08:08.0:   bridge window [mem 0xfe900000-0xfe9fffff]
[    1.073504] pci 0000:08:08.0:   bridge window [mem pref disabled]
[    1.079597] pci 0000:08:09.0: PCI bridge to [bus 09-09]
[    1.084820] pci 0000:08:09.0:   bridge window [io  0xb000-0xbfff]
[    1.091270] pci 0000:08:09.0:   bridge window [mem 0xfe800000-0xfe8fffff]
[    1.098054] pci 0000:08:09.0:   bridge window [mem pref disabled]
[    1.104150] pci 0000:07:00.0: PCI bridge to [bus 08-0e]
[    1.109370] pci 0000:07:00.0:   bridge window [io  0xb000-0xefff]
[    1.115466] pci 0000:07:00.0:   bridge window [mem 0xfe800000-0xfebfffff]
[    1.122250] pci 0000:07:00.0:   bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
[    1.129993] pci 0000:00:01.0: PCI bridge to [bus 07-0e]
[    1.135212] pci 0000:00:01.0:   bridge window [io  0xb000-0xefff]
[    1.141305] pci 0000:00:01.0:   bridge window [mem 0xfe700000-0xfebfffff]
[    1.148091] pci 0000:00:01.0:   bridge window [mem 0xfdf00000-0xfdffffff 64bit pref]
[    1.155832] pci 0000:00:1c.0: PCI bridge to [bus 06-06]
[    1.161055] pci 0000:00:1c.0:   bridge window [io  0xa000-0xafff]
[    1.167149] pci 0000:00:1c.0:   bridge window [mem 0xfe600000-0xfe6fffff]
[    1.173934] pci 0000:00:1c.0:   bridge window [mem 0x7f700000-0x7f8fffff 64bit pref]
[    1.181691] pci 0000:00:1c.1: PCI bridge to [bus 05-05]
[    1.186914] pci 0000:00:1c.1:   bridge window [io  0x9000-0x9fff]
[    1.193008] pci 0000:00:1c.1:   bridge window [mem 0xfe500000-0xfe5fffff]
[    1.199793] pci 0000:00:1c.1:   bridge window [mem 0x7f900000-0x7fafffff 64bit pref]
[    1.207533] pci 0000:00:1c.2: PCI bridge to [bus 04-04]
[    1.212757] pci 0000:00:1c.2:   bridge window [io  0x8000-0x8fff]
[    1.218851] pci 0000:00:1c.2:   bridge window [mem 0xfe400000-0xfe4fffff]
[    1.225637] pci 0000:00:1c.2:   bridge window [mem 0x7fb00000-0x7fcfffff 64bit pref]
[    1.233375] pci 0000:00:1c.3: PCI bridge to [bus 03-03]
[    1.238599] pci 0000:00:1c.3:   bridge window [io  0x7000-0x7fff]
[    1.244692] pci 0000:00:1c.3:   bridge window [mem 0xfe300000-0xfe3fffff]
[    1.251477] pci 0000:00:1c.3:   bridge window [mem 0x7fd00000-0x7fefffff 64bit pref]
[    1.259218] pci 0000:00:1c.4: PCI bridge to [bus 02-02]
[    1.264442] pci 0000:00:1c.4:   bridge window [io  0x6000-0x6fff]
[    1.270534] pci 0000:00:1c.4:   bridge window [mem 0xfe200000-0xfe2fffff]
[    1.277320] pci 0000:00:1c.4:   bridge window [mem 0x7ff00000-0x800fffff 64bit pref]
[    1.285060] pci 0000:00:1e.0: PCI bridge to [bus 01-01]
[    1.290281] pci 0000:00:1e.0:   bridge window [io  disabled]
[    1.295943] pci 0000:00:1e.0:   bridge window [mem disabled]
[    1.301602] pci 0000:00:1e.0:   bridge window [mem pref disabled]
[    1.307703] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.314410] pci 0000:07:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.321116] pci 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.327827] pci 0000:08:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.334531] pci 0000:08:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.341240] pci 0000:08:06.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[    1.348286] pci 0000:08:08.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.354992] pci 0000:08:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.361700] pci 0000:00:1c.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.368406] pci 0000:00:1c.1: PCI INT B -> GSI 16 (level, low) -> IRQ 16
[    1.375115] pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.381823] pci 0000:00:1c.3: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[    1.388530] pci 0000:00:1c.4: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    1.395405] NET: Registered protocol family 2
[    1.399826] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[    1.407115] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    1.414840] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
[    1.421630] TCP: Hash tables configured (established 131072 bind 65536)
[    1.428237] TCP reno registered
[    1.431384] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    1.437307] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    1.443751] NET: Registered protocol family 1
[    1.467652] highmem bounce pool size: 64 pages
[    1.472101] HugeTLB registered 4 MB page size, pre-allocated 0 pages
[    1.478820] msgmni has been set to 1458
[    1.483603] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    1.490997] io scheduler noop registered
[    1.494921] io scheduler deadline registered
[    1.499226] io scheduler cfq registered (default)
[    1.507247] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
[    1.515594] ACPI: Power Button [PWRB]
[    1.519346] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    1.526738] ACPI: Power Button [PWRF]
[    1.575013] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.581502] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[    1.588111] 00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[    1.596237] brd: module loaded
[    1.600432] loop: module loaded
[    1.603899] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    1.611035] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[    1.616354] scsi0 : ata_piix
[    1.619417] scsi1 : ata_piix
[    1.623848] ata1: SATA max UDMA/133 cmd 0x4c00 ctl 0x4880 bmdma 0x4400 irq 19
[    1.630983] ata2: SATA max UDMA/133 cmd 0x4800 ctl 0x4480 bmdma 0x4408 irq 19
[    1.638138] ata_piix 0000:00:1f.5: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    1.645273] ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
[    1.650567] scsi2 : ata_piix
[    1.653621] scsi3 : ata_piix
[    1.657969] ata3: SATA max UDMA/133 cmd 0x5c00 ctl 0x5880 bmdma 0x5400 irq 19
[    1.665108] ata4: SATA max UDMA/133 cmd 0x5800 ctl 0x5480 bmdma 0x5408 irq 19
[    1.672388] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.678929] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    1.686076] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    1.691310] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[    1.698722] ehci_hcd 0000:00:1d.7: debug port 1
[    1.707153] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe1ff800
[    1.726109] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[    1.732043] hub 1-0:1.0: USB hub found
[    1.735798] hub 1-0:1.0: 4 ports detected
[    1.739952] uhci_hcd: USB Universal Host Controller Interface driver
[    1.746335] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    1.753480] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    1.758704] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    1.766113] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00003c00
[    1.772038] hub 2-0:1.0: USB hub found
[    1.775793] hub 2-0:1.0: 2 ports detected
[    1.779895] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    1.787036] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    1.792266] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[    1.799672] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00004000
[    1.805604] hub 3-0:1.0: USB hub found
[    1.809357] hub 3-0:1.0: 2 ports detected
[    1.813753] PNP: No PS/2 controller found. Probing ports directly.
[    1.820353] serio: i8042 KBD port at 0x60,0x64 irq 1
[    1.825324] serio: i8042 AUX port at 0x60,0x64 irq 12
[    1.830561] mice: PS/2 mouse device common for all mice
[    1.835890] rtc_cmos 00:03: RTC can wake from S4
[    1.840590] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    1.846697] rtc0: alarms up to one month, y3k, 114 bytes nvram
[    1.852577] i2c /dev entries driver
[    1.856246] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    1.864326] it87: Found IT8718F chip at 0xa10, revision 4
[    1.869732] it87: in3 is VCC (+5V)
[    1.873134] it87: in7 is VCCH (+5V Stand-By)
[    1.877780] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
[    1.883496] iTCO_wdt: Found a ICH9DO TCO device (Version=2, TCOBASE=0x0860)
[    1.890557] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    1.896664] IT87 WDT: Cannot register miscdev on minor=130 (err=-16)
[    1.903030] cpuidle: using governor ladder
[    1.907124] ioatdma: Intel(R) QuickData Technology Driver 4.00
[    1.913715] TCP cubic registered
[    1.916942]
[    1.916943] wg_shim_init: Built Mar  8 2013 13:44:43 CPUs 4
[    1.916944]
[    1.925496] wg_shim_init: xfrm_skb_cb 36 Hw_callback_data 12
[    1.931169] Initializing XFRM netlink socket
[    1.935514] NET: Registered protocol family 10
[    1.940132] lo: Disabled Privacy Extensions
[    1.944344] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    1.949743] NET: Registered protocol family 17
[    1.954198] NET: Registered protocol family 15
[    1.958650] Using IPI Shortcut mode
[    1.962367] registered taskstats version 1
[    1.967080] rtc_cmos 00:03: setting system clock to 2016-02-03 18:23:51 UTC (1454523831)
[    2.011428] ata4: SATA link down (SStatus 0 SControl 300)
[    2.022331] ata3: SATA link down (SStatus 0 SControl 300)
[    2.335190] ata1.00: SATA link down (SStatus 0 SControl 300)
[    2.340919] ata1.01: SATA link down (SStatus 0 SControl 300)
[    2.487547] ata2.00: SATA link down (SStatus 0 SControl 300)
[    2.493258] ata2.01: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    2.524781] ata2.01: ATA-0: TRANSCEND, 20071116, max MWDMA2
[    2.530429] ata2.01: 1993824 sectors, multi 0: LBA
[    2.535383] ata2.01: applying bridge limits
[    2.551464] ata2.01: configured for MWDMA2
[    2.555674] scsi 1:0:1:0: Direct-Access     ATA      TRANSCEND        2007 PQ: 0 ANSI: 5
[    2.564096] sd 1:0:1:0: [sda] 1993824 512-byte logical blocks: (1.02 GB/973 MiB)
[    2.571821] sd 1:0:1:0: [sda] Write Protect is off
[    2.576855] sd 1:0:1:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.586478]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[    2.593635] sd 1:0:1:0: [sda] Attached SCSI disk
[    2.601731] VFS: Mounted root (ext2 filesystem) readonly on device 8:3.
[    2.608565] Freeing unused kernel memory: 384k freed
[    3.033604] Running /etc/runlevel/1/S02rootrw...Done.
[    3.045110] Running /etc/runlevel/1/S10armled...Done.
[    3.056315] Running /etc/runlevel/1/S12mproc...Done.
[    3.056686] Running /etc/runlevel/1/S17sysfs...Done.
[    3.057290] Running /etc/runlevel/1/S18seed-random...Reseeded random generator
[    3.058743] Done.
[    3.065792] Running /etc/runlevel/2/S10var...Done.
[    3.066640] Running /etc/runlevel/2/S11shm...Done.
[    3.067253] Running /etc/runlevel/2/S13devpts...Done.
[    3.067854] Running /etc/runlevel/2/S14temp...Done.
[    3.068218] Running /etc/runlevel/2/S15mbootext2...Done.
[    3.069890] Running /etc/runlevel/2/S16checkgrub...S16checkgrub: check SYSA file
[    3.073480] S16checkgrub passed: No Action Required!
[    3.073555] Done.
[    3.073579] Running /etc/runlevel/2/S16pending...Done.
[    3.074060] Running /etc/runlevel/2/S18data...fsck 1.41.0 (10-Jul-2008)
[    3.130692] e2fsck 1.41.0 (10-Jul-2008)
[    3.169758] /dev/wgrd.sysa_data: recovering journal
[    3.423384] /dev/wgrd.sysa_data: clean, 490/51712 [    3.286636] EXT3-fs: barriers not enabled
files, 124359/82[    3.291898] kjournald starting.  Commit interval 5 seconds
5520 blocks
[    3.298554] EXT3-fs (sda6): using internal journal
[    3.304705] EXT3-fs (sda6): mounted filesystem with writeback data mode
[    3.452239] Done.
[    3.452281] Running /etc/runlevel/2/S18hotplug...Done.
[    3.688667] Running /etc/runlevel/2/S18kdump...Then try loading kdump kernel
[    3.709022] Memory for crashkernel is not reserved
[    3.709097] Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel
[    3.709246] Don[    3.585057] pkp_drv: module license 'CAVIUM' taints kernel.
[    3.591091] Disabling lock debugging due to kernel taint
e.
[    3.709270] Running /etc/runlevel/2/S19fips...Done.
[    3.709610] Running /etc/runlevel/2/S19ipv6...dis[    3.605886] Cavium Driver --- 1.01-abling IPv6 autoNitrox-PX found at Bus 14 Slot 0
conf for all
[ [    3.614325] pci 0000:0e:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    3.622682] Using memory-mapped bar for device 0x177D:0x10
   3.710275] dis[    3.628381] bar 0: fdfff000
abling IPv6 autoconf for default
[    3.710341] enable IPv6 forwarding for all
[    3.710400] enable IPv6 forwarding for default
[    3.710465] disabling IPv6 for all
[    3.710529] disabl[    3.648916] NO DDR on the chip
[    3.652603] Resorting to Context memory on Host.
[    3.657465] part number=1620
ing IPv6 for def[    3.660481] totoal number of cores=8
[    3.665654] Finished Initializing this device
ault
[    3.710[    3.670310] Total Number of Nitrox Devices: 1
606] Done.
[    3.710629] Runni[    3.677658] Starting poll_thread
ng /etc/runlevel[    3.682392] device count = 1
/2/S20cavium...[    3.686796] Starting poll_thread
[    3.686825] Starting poll_thread
[    3.686827] device count = 1
[    3.686852] Starting poll_thread
[    3.686854] device count = 1
[    3.686967] Registration is a success The major device number is 125
[    3.686968] To talk to the device driver, please use device appropriate device node.
[    3.686970] Device's minor number corresponds to the microcode to be used.
[    3.686972] Please read the README file for further instructions
[    3.686973]
[    3.686985] Loaded Cavium Driver --- 1.01-device count = 1
[    5.966801] Write 0xf00000ff into CORE ENABLE after Interrupt bits check
[    5.973772] UEN = 0xff
[    5.976214] Final Core Mask = 0x000000ff
[    5.980374] Loaded Boot microcode
[    5.987838] All cores joined to group 0,REG_EXEC_GRP: 0x11111111
[    5.994021] Additional setup for CN1600
[    5.997993] Config: Device Control Reg (offset 0x78): 0x00092810
[    6.004241] PCI-E Link error detected: 0x00090000
[    6.009149] Disabling units: mask 0xff
[    6.013063] Loading ucode 4
File: /lib/microcode/boot_mc2_px.out
[    6.638271]  Version = CNPx-MC-BOOT-2.00
[    6.638334]  Code length = 17536     Data length[    6.507968] Initializing USB Mass Storage driver...
 = 152
[    6.6[    6.514132] usbcore: registered new interface driver usb-storage
38435] 0: name=/[    6.521726] USB Mass Storage support registered.
lib/microcode/boot_mc2_px.out, index=0, core=0
[    6.638530] File: /lib/microcode/main_ipsec2_px.out
[    6.638604]  Version = CNPx-MC-IPSEC[    6.539596] sky2: driver version 1.28
-MAIN-0006
[    6.638671]  Code length = 38448     Data length = 1176
[    6.638744] 1: name=/lib/microcode/main_ipsec2_px.out, index=4, core=8
[    6.638845] CSP1 core assignments
[    6.638891]       BOOT : 0x000000
[    6.638937]  IPSEC_MLM : 0x0000ff
[    6.638983] Done.
[    6.639007] Running /etc/runlevel/2/S20cleanup-dbg...Done.
[    6.639088] Running /etc/runlevel/2/S20fipstest...Done.
[    6.639294] Running /etc/runlevel/2/S20usb...Done.
[    6.668512] Running /etc/runlevel/2/S20wgbase...Done.
[    6.672853] Running /etc/runlevel/2/S21eth...[    9.559630] e1000e: Intel(R) PRO/1000 Network Driver - 1.6.3-NAPI
[    9.565941] e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
[    9.572142] e1000e 0000:00:19.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[    9.902055] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:28
[    9.910455] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[    9.917789] e1000e 0000:00:19.0: eth0: MAC: 8, PHY: 6, PBA No: FFFFFF-0FF
[    9.924833] e1000e 0000:0d:00.0: Disabling ASPM L0s
[    9.930003] e1000e 0000:0d:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   10.052016] e1000e 0000:0d:00.0: eth1: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:1f
[   10.060368] e1000e 0000:0d:00.0: eth1: Intel(R) PRO/1000 Network Connection
[   10.067752] e1000e 0000:0d:00.0: eth1: MAC: 4, PHY: 8, PBA No: FFFFFF-0FF
[   10.074941] e1000e 0000:0b:00.0: Disabling ASPM L0s
[   10.080100] e1000e 0000:0b:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   10.202027] e1000e 0000:0b:00.0: eth2: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:22
[   10.210255] e1000e 0000:0b:00.0: eth2: Intel(R) PRO/1000 Network Connection
[   10.217651] e1000e 0000:0b:00.0: eth2: MAC: 4, PHY: 8, PBA No: FFFFFF-0FF
[   10.224725] e1000e 0000:0a:00.0: Disabling ASPM L0s
[   10.229910] e1000e 0000:0a:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   10.352015] e1000e 0000:0a:00.0: eth3: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:20
[   10.360369] e1000e 0000:0a:00.0: eth3: Intel(R) PRO/1000 Network Connection
[   10.367729] e1000e 0000:0a:00.0: eth3: MAC: 4, PHY: 8, PBA No: FFFFFF-0FF
[   10.374742] e1000e 0000:09:00.0: Disabling ASPM L0s
[   10.379962] e1000e 0000:09:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   10.502018] e1000e 0000:09:00.0: eth4: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:21
[   10.510387] e1000e 0000:09:00.0: eth4: Intel(R) PRO/1000 Network Connection
[   10.517745] e1000e 0000:09:00.0: eth4: MAC: 4, PHY: 8, PBA No: FFFFFF-0FF
[   10.524908] e1000e 0000:06:00.0: Disabling ASPM L0s L1
[   10.530248] e1000e 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   10.646777] e1000e 0000:06:00.0: eth5: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:23
[   10.655153] e1000e 0000:06:00.0: eth5: Intel(R) PRO/1000 Network Connection
[   10.662530] e1000e 0000:06:00.0: eth5: MAC: 3, PHY: 2, PBA No: FFFFFF-0FF
[   10.669606] e1000e 0000:05:00.0: Disabling ASPM L0s L1
[   10.674970] e1000e 0000:05:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   10.790836] e1000e 0000:05:00.0: eth6: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:24
[   10.799122] e1000e 0000:05:00.0: eth6: Intel(R) PRO/1000 Network Connection
[   10.806474] e1000e 0000:05:00.0: eth6: MAC: 3, PHY: 2, PBA No: FFFFFF-0FF
[   10.813583] e1000e 0000:04:00.0: Disabling ASPM L0s L1
[   10.818957] e1000e 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   10.937889] e1000e 0000:04:00.0: eth7: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:25
[   10.946315] e1000e 0000:04:00.0: eth7: Intel(R) PRO/1000 Network Connection
[   10.953641] e1000e 0000:04:00.0: eth7: MAC: 3, PHY: 2, PBA No: FFFFFF-0FF
[   10.960768] e1000e 0000:03:00.0: Disabling ASPM L0s L1
[   10.966159] e1000e 0000:03:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[   11.087902] e1000e 0000:03:00.0: eth8: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:26
[   11.096394] e1000e 0000:03:00.0: eth8: Intel(R) PRO/1000 Network Connection
[   11.103725] e1000e 0000:03:00.0: eth8: MAC: 3, PHY: 2, PBA No: FFFFFF-0FF
[   11.110843] e1000e 0000:02:00.0: Disabling ASPM L0s L1
[   11.116264] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   11.234576] e1000e 0000:02:00.0: eth9: (PCI Express:2.5GT/s:Width x1) 00:90:7f:83:0a:27
[   11.242902] e1000e 0000:02:00.0: eth9: Intel(R) PRO/1000 Network Connection
[   11.250288] e1000e 0000:02:00.0: eth9: MAC: 3, PHY: 2, PBA No: FFFFFF-0FF
No Marvell interfaces found, probi[   11.366064] Parallel LCM Driver Version 0.0.6 is loaded
ng for Intel
[ [   11.372719] plcm_drv: LPTx Address = 378
  11.505011] Done.
[   11.505037] Running /etc/runlevel/2/S21frontpanel...[   11.532260] <plcm_init>:keypad thread created, threadp = de879410
[   11.532272] <keypad_thread>:keypad thread started
Done.
[   11.685312] Running /etc/runlevel/2/S22flashrom...[   11.550643]
[   11.552184]
[   11.553780]
[   11.555332]
[   11.596672]
[   11.598238]
[   11.599795]
[   11.601391]
Done.
[   11.743702] Running /etc/runlevel/2/S22login...Done.
[   11.744051] Running /etc/runlevel/2/S22rtc...Done.
[   11.752257] Running /etc/runlevel/2/S23pppoe...[   11.620263] PPP generic driver version 2.4.2
[   11.628697] PPP MPPE Compression module registered
[   11.635143] PPP Deflate Compression module registered
[   11.641574] NET: Registered protocol family 24
Done.
[   11.790401] Running /etc/runlevel/2/S23sslvpn...[   11.654239] tun: Universal TUN/TAP device driver, 1.6
[   11.660061] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Done.
[   11.807290] Running /etc/runlevel/2/S24l2tpvpn...[   11.671410] L2TP core driver, V2.0
[   11.677311] L2TP netlink interface
[   11.685395] PPPoL2TP kernel driver, V2.0
Done.
[   11.830164] Running /etc/runlevel/2/S25wgcfg...No conversion required from version 11.7.2 to 11.7.2.
[   12.176300] Done.
[   12.176331] Running /etc/runlevel/2/S27cfgcheck...Config ok
[   12.547144] Done.
[   12.547222] Running /etc/runlevel/2/S29firewall...Done.
[   12.547694] Running /etc/runlevel/2/S29wgcore...Done.
[   12.576943] Running /etc/runlevel/2/S30bonding...[   12.447622] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
[   12.455360] bonding: MII link monitoring set to 100 ms
Done.
[   12.601324] Running /etc/runlevel/2/S30net...[   12.473269] Bridge firewalling registered
[   12.480469] Ebtables v2.0 registered
[   12.499416] GRE over IPv4 tunneling driver
[   12.511813] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[   12.518848] All bugs added by David S. Miller <davem@redhat.com>
Done.
[   12.667066] Running /etc/runlevel/2/S30upgrade...Done.
[   12.668018] Running /etc/runlevel/2/S31bwsigs...Done.
[   12.670895] Running /etc/runlevel/2/S31cacert...Done.
[   12.672893] Running /etc/runlevel/2/S31cert...Done.
[   12.730127] Running /etc/runlevel/2/S31crypto...[   12.596143]
[   12.596144] wg_crypto_init: Built Mar  8 2013 13:45:48 FIPS 0
[   12.596146]
[   12.605242] wg_crypto_init: Insert aead  'authenc(digest_null,cbc(des3_ede))-wg'
[   12.613121] wg_crypto_init: Insert aead  'authenc(digest_null,cbc(aes))-wg'
[   12.620399] wg_crypto_init: Insert aead  'authenc(hmac(sha1),cbc(cipher_null))-wg'
[   12.628355] wg_crypto_init: Insert aead  'authenc(hmac(sha1),cbc(des3_ede))-wg'
[   12.636082] wg_crypto_init: Insert aead  'authenc(hmac(sha1),cbc(aes))-wg'
Done.
[   12.783967] Running /etc/runl[   12.646163] Netfilter messages via NETLINK v0.30.
evel/2/S31xtables...[   12.655662] ip_set_init[1869]: ip_set: protocol 5
[   12.697897] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   12.704273] nf_conntrack_init_init_net: conntrack max=65536 high water mark=52428
[   12.712149] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
[   12.719865] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
[   12.728139] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[   12.743813] ip_tables: (C) 2000-2006 Netfilter Core Team
[   12.760760] nf_ct_ftp: Maximum expected value 1
[   12.785900] ctnetlink v0.93: registering with nfnetlink.
[   12.822992] arp_tables: (C) 2002 David S. Miller
[   12.850934] u32 classifier
[   12.853757]     Performance counters on
[   12.857723]     input device check on
[   12.861518]     Actions configured
Done.
[   13.012115] Running /etc/runlevel/2/S31xtables6...Done.
[   13.021044] Running /etc/runlevel/2/S32clst...Done.
[   13.036692] Running /etc/runlevel/2/S32hotspot...Done.
[   1[   12.901093] ipt_addrpairs_6 v0.1.0: Loading
3.037708] Running /etc/runlevel/2/S32wgxt...[   12.910767] xt_session6 : Loading
[   12.914139] xt_session6 : Loaded limit 1000 hash 1024 WG IPC ID 184549376 (0x0B000000)
[   12.927752] ipt_addrpairs v0.1.0: Loaded
[   12.934551] xt_ifset: Loaded with set limit 5000 and entry limit 5000
[   12.941718] xt_classify : Loaded
[   12.945657] xt_master: Loaded
[   12.949319] xt_MASTER: Loaded
[   12.953352] xt_WGTEE: Loaded
[   12.956996] xt_STP: Loaded
[   12.960791] Schedule: Loaded
[   12.964354] xt_POLICY: Loaded
[   12.968050] xt_policy : Loaded
[   12.971885] xt_EXPIRES: Loaded
[   12.975711] xt_IPPRECEDENCE: Loaded
[   12.981115] xt_PKTCACHE: Loaded
[   12.989181] xt_session : Loaded limit 1000 hash 1024 WG IPC ID 92274688 (0x05800000)
[   13.003564] xt_CONNCLASSIFY: Loaded
[   13.007721] xt_connclassify : Loaded
[   13.012714] xt_ipspoof : Loaded
[   13.021234] xt_LBDNAT: Loaded
[   13.027759] xt_MWAN: Loaded
[   13.033005] xt_psd: Loaded
[   13.036855] xt_ipsd: Loaded
[   13.040807] xt_ddos: Loaded
[   13.044955] xt_dos: Loaded
[   13.050710] xt_wgaccount: Loaded
[   13.067280] xt_block : Loaded limit 1000 hash 1024 WG IPC ID 155189248
[   13.075579] xt_localroute: Loaded
[   13.080327] xt_duplicate: Loaded
Done.
[   13.228111] Running /etc/runlevel/2/S33appID...[   13.129112] WG workqueue: Loaded
[   13.139566] bw driver: Loaded
Done.
[   13.283826] Running /etc/runlevel/2/S33proxy...Linking proxy needed libs to sandbox
[   13.306128] Linking Done.
[   13.306166] Done.
[   13.306189] Running /etc/runlevel/2/S34proxy...Done.
[   13.306735] Running /etc/runlevel/2/S35proxy...Done.
[   13.307098] Running /etc/runlevel/2/S35scand...Done.
[   13.307779] Running /etc/runlevel/2/S36dynroute...Done.
[   13.308123] Running /etc/runlevel/2/S42ssh...Done.
[   13.309860] Running /etc/runlevel/2/S44sysb...Done.
[   13.311737] Running /etc/runlevel/2/S50nettune...Setting IPv4 route garbage collection timeout to 2 minutes
[   13.312357] Setting promote_secondaries to 1
[   13.312406] Done.
[   13.312432] Running /etc/runlevel/2/S53configdhash...Done.
[   13.312887] Running /etc/runlevel/2/S80seed-random...Saved random seed
[   13.681687] Done.
[   13.681707] Running /etc/runlevel/2/S99igmp...Done.
[   13.682556] Running /etc/runlevel/2/S99rootro...Done.
[   20.288381] Running /etc/runlevel/4/S51armled...Done.

XTM_8_Series login:

Title: Re: Watchguard Firebox XTM 8 Series
Post by: _Adrian_ on July 31, 2016, 08:44:04 pm
Any updates ??

Was thinking if I go this route ( XTM8 ) an E8400 would be nice upgrade since they aren't an arm and a leg anymore... but I do have to say the QX9650 is twice the chip ( literally !!) however its not the "buck" bargain that the E8400 is... But there also the option of the Q9550 or even the Q9650 which are both great options...

Also having the max RAM 2X2GB wouldn't hurt either. I'm guessing it would call for PC2-6400-2Gb Low Density Non-ECC ??

Reason behind the Upgrades is the few "streamers" in the house that are being VPN hogs... 4 Clients at 10-15Mbps and my X1250 is getting slow and need to update to a XTM5 or preferably to an XTM8 very soon !
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 02, 2016, 11:22:06 am
Is that encryption happening on the X-e box? If it's just passing the encrypted traffic it shouldn't have much trouble.

I never managed to get hold of an XTM 8. Now I have access to more interesting hardware.  ;)

However the initial problems we had installing are probably not applicable now as both consoles are active by default and em is the default NIC type.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: _Adrian_ on August 02, 2016, 10:59:24 pm
Is that encryption happening on the X-e box? If it's just passing the encrypted traffic it shouldn't have much trouble.

I never managed to get hold of an XTM 8. Now I have access to more interesting hardware.  ;)

However the initial problems we had installing are probably not applicable now as both consoles are active by default and em is the default NIC type.

Steve
Yes Steve it is...
Seems like anytime any heavy streaming / downloading happens the box just bogs down.
CPU jumps from Idle ( ~ 3-5% ) to Heavy Load ( 90+% ) as well as any local traffic is down down to a crawl ! (2-5mbit on a 170ish mbit service)
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on March 30, 2017, 04:23:32 pm
I just purchased a XTM 810 from Ebay. I currently have a XTM 525 running pfSense. My goal is to setup a high availability setup between the two.

My question is about the vga connection on the 810. What do I need to get working with a monitor and what version of the pfsense install file should I use?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on March 30, 2017, 07:08:39 pm
Is this correct VGA cable for the XTM 810? It is a 11 pin cable with the blockout on the 3rd pin.

http://www.ebay.com/itm/Low-Profile-Half-Height-Video-Graphics-Card-VGA-Port-Extension-Cable-11Pin-3-25-/161134847823?hash=item258462a74f:g:k5MAAOxywbNRBOos
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 02, 2017, 08:30:34 am
Probably not. It needs to be 2mm pitch: https://forum.pfsense.org/index.php?topic=61970.msg335371#msg335371 I can't see the pitch specified there.

No clue if the pinout matches there either. No way of swapping the pins on that connector so you'd have to be lucky.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 02, 2017, 08:50:52 am
Probably not. It needs to be 2mm pitch: https://forum.pfsense.org/index.php?topic=61970.msg335371#msg335371 I can't see the pitch specified there.

No clue if the pinout matches there either. No way of swapping the pins on that connector so you'd have to be lucky.

Steve

Ok.. So what can I do to get a display working with the XTM 810 device? I will receive the unit tomorrow.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 02, 2017, 09:25:23 am
You may not need to. Since em is now a default NIC type it might boot completely on the first boot using the Nano image and you can then connect to the webgui via the LAN port.

I would at least test that first.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 02, 2017, 09:37:24 am
You may not need to. Since em is now a default NIC type it might boot completely on the first boot using the Nano image and you can then connect to the webgui via the LAN port.

I would at least test that first.

Steve

Can you provide me a link to the image I need to install. I will be installing a SSD drive in the XTM 810. So how do I install pfsense on the hard drive? Do I need to have the pfsense installer on a CF card and install first on the CF card? Just trying to figure out how to get pfsense installed on the SSD drive that will be installed in the XTM 810.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 02, 2017, 09:40:36 am
That would be more difficult. You would probably need to install pfSense in some other machine first then move the SSD. You could use the XTM5 you have to do that. As long as you only assign the em NICs it will boot in the XTM8.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 02, 2017, 10:12:06 am
That would be more difficult. You would probably need to install pfSense in some other machine first then move the SSD. You could use the XTM5 you have to do that. As long as you only assign the em NICs it will boot in the XTM8.

Steve

On the install on the XTM 525, I have a LAGG LAN connection using interface em3 & em4.  So, I am wondering if I can make a disk copy of the XTM 525 SSD and use it in the XTM 810?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 02, 2017, 03:05:28 pm
You could do that as long as you don;t have the fxp NIC assigned. Since that doesn't exist on the XTM8 it will stop at the assign interfaces screen (which you won't be able to see) waiting for you input if it is.

Though I would probably just install fresh onto the new SSD in the XTM5 then move it across to minimise any additional config you don't need.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 02, 2017, 05:58:01 pm
You could do that as long as you don;t have the fxp NIC assigned. Since that doesn't exist on the XTM8 it will stop at the assign interfaces screen (which you won't be able to see) waiting for you input if it is.

Though I would probably just install fresh onto the new SSD in the XTM5 then move it across to minimise any additional config you don't need.

Steve

So which pfsense installer should I use?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 03, 2017, 04:42:36 am
Will the WGXepc64 program work on the XTM 810? If yes, please answer the following questions:

1. What folder should be the file be stored in?
2. How do you run the program automatically on startup?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 03, 2017, 06:53:56 am
Use whichever installer you used previously on the XTM5 It's the same image type for the XTM8 only the console difference prevents you using it directly.

WGXepc64 will run but may not recognise the box. I've never had access to one to look at the values and add the code.

You can add it to /conf as described here: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Controlling_hardware_with_WGXepc
In Nano that is shared between slices and kept across an upgrade.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 03, 2017, 07:42:38 am
Use whichever installer you used previously on the XTM5 It's the same image type for the XTM8 only the console difference prevents you using it directly.

WGXepc64 will run but may not recognise the box. I've never had access to one to look at the values and add the code.

You can add it to /conf as described here: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Controlling_hardware_with_WGXepc
In Nano that is shared between slices and kept across an upgrade.

Steve

I got pfsense installed on a SSD and assigned the LAN interface to em0.

How do I run the WGXepc program on start up? Is there a startup file somewhere?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 03, 2017, 12:06:51 pm
You can use shellcmd to run it at startup, either via the package or manually entering the xml:
https://doc.pfsense.org/index.php/Executing_commands_at_boot_time

Steve

Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 03, 2017, 08:10:49 pm
Received the XTM 810 today and I can't get pfsense to boot from a SSD. Additionally I can't get vga to work. What am I going to do?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 03, 2017, 09:08:13 pm
Got it all working finally.. I had the pin configuration on the make shift VGA cable outlined in this thread wrong. Now able to see pfsense on the screen and configure the LAN and WAN interfaces. I will complete the remaining configuration from the WEB GUI...
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 03, 2017, 10:11:28 pm
Here are some photos of my make shift VGA connector based on some posts in this thread.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 04, 2017, 07:52:40 pm
The  WGXepc64 program does not work on the XTM 810. What option do I have to turn down the fans?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 05, 2017, 07:26:46 am
You may be able to set the target temperature or the minimum fan speed in the BIOS. The PSU fan is not controllable though obviously.
It looks like there are some settings there: https://forum.pfsense.org/index.php?topic=61970.msg334448#msg334448

Replace the fans with quieter ones is always an option.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 05, 2017, 09:46:55 am
You may be able to set the target temperature or the minimum fan speed in the BIOS. The PSU fan is not controllable though obviously.
It looks like there are some settings there: https://forum.pfsense.org/index.php?topic=61970.msg334448#msg334448

Replace the fans with quieter ones is always an option.

Steve

I thought the BIOS was locked.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 05, 2017, 11:05:20 am
I might be, I don't have access to one of these boxes to check. It was on the XTM5.

In which case swapping out the fans might be your best option. Or unlocking the BIOS yourself.  ;)

I assume WGXepc reports it did't find a firebox?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 05, 2017, 11:09:50 am
I might be, I don't have access to one of these boxes to check. It was on the XTM5.

In which case swapping out the fans might be your best option. Or unlocking the BIOS yourself.  ;)

I assume WGXepc reports it did't find a firebox?

Steve

Yes... That is the message I received..
Title: Re: Watchguard Firebox XTM 8 Series
Post by: mppkll on April 10, 2017, 08:10:57 pm
Stephenw10,

I'm getting "ELF interpreter /libexec/lad-elf.so.1 not found, error 8" when I try to run WGXepc. An I missing something?  This is a fresh install from a memstick image to a SDD running on the XTM 810.  Also how would one go about finding the hardware registers to add to WGXepc?  I have a copy of the BIOS and some documentation from lanner on the FW-8750 MB that the XTM 8 is based.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 11, 2017, 05:31:59 pm
It's probably the 32bit version on a 64bit install (or vice versa).

As you say there's no code in there for the XTM8 (yet) anyway.

You can see how we found the registers for the XTM5 here (and in the previous few posts):
https://forum.pfsense.org/index.php?topic=43574.msg261279#msg261279

It wouldn't surprise me to find they are in the the exact same place on the XTM8.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: mppkll on April 11, 2017, 06:45:11 pm
I've figured out a lot since last post,

1st the Super IO chip is a IT8718F and it is handleing the both the environmental control and gpio.

2nd I was able to extract the modules from the BIOS and found that some of the super IO devices are disabled (COM port 1 most importantly) so changing settings in an unlocked BIOS still wont help that.  Also some close inspection of the hardware, TTL to RS232 chips are missing from the MB so COM 1 is a write off.

3rd I got the datasheets from the Super IO chip and have figured out how to set the chip into MB PnP mode to read and change a fan control register (there are 5 fans controls and 3 temp registers).

4th I hope you don't mind, I am working on a new version of the WGXepc for the XTM 8 only (as the super IO is different), I'm focusing on fan control but I think LCD and LED may be possable, looking at the BIOS Super IO boot and register blocks it looks like parallel port and 3 GPIO pins are in use for the LCD/LED/Keypad board.  Of course I will post it as I go.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: pglover19 on April 11, 2017, 07:19:18 pm
I've figured out a lot since last post,

1st the Super IO chip is a IT8718F and it is handleing the both the environmental control and gpio.

2nd I was able to extract the modules from the BIOS and found that some of the super IO devices are disabled (COM port 1 most importantly) so changing settings in an unlocked BIOS still wont help that.  Also some close inspection of the hardware, TTL to RS232 chips are missing from the MB so COM 1 is a write off.

3rd I got the datasheets from the Super IO chip and have figured out how to set the chip into MB PnP mode to read and change a fan control register (there are 5 fans controls and 3 temp registers).

4th I hope you don't mind, I am working on a new version of the WGXepc for the XTM 8 only (as the super IO is different), I'm focusing on fan control but I think LCD and LED may be possable, looking at the BIOS Super IO boot and register blocks it looks like parallel port and 3 GPIO pins are in use for the LCD/LED/Keypad board.  Of course I will post it as I go.

I am eagerly awaiting your results since I own a XTM 810 unit. I would love to be able to control the fans and the LCD/LED.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: fmertz on April 11, 2017, 08:32:44 pm
I would love to be able to control the LCD/LED.

You might want to give a try to the lcdproc package, and configure it to use the SDEC driver. This will hopefully let you control the LCD...
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on April 11, 2017, 10:01:30 pm
Yeah the LCD is still SDEC compatible that should work already.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: mppkll on May 04, 2017, 12:41:44 pm
I wanted to give you guys an up date as to where I stand, there will be a significant pause ( couple months) in my work on this because of life stuff.

So far this is the status of things:

LCD Back-light / LCD:  Working: no changes where needed.

LED: not working yet:  I have the GPIO system up but need to put some time into tracing the PCB traces to/from the LED pins on the LCD jack and figure out what pin# controls them. I don't want to just turn on/off GP pins because most of them have a dual purposes, so I need to trace the hardware.  The IT8718F has a LED flashing system that may be usable to provide the flashing as well as just on/off depending on what GP Pin# the LEDs are on.  I will focus on this once the fans are all working.

FANS:  Partially working: I can read the speed from 4 of the 5 fans (3 processor fans-can read, 1 case fan-can read, 1 power supply fan-can't read) , but so far can only adjust 1 (case fan) of the 5.  I'm sure that I will get 4 of the 5 working totally as they are controlled by the IT8717F but the power supply fan will not be controllable.

TEMP: Working: I can read all of the temp and voltage registers.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on August 25, 2017, 11:07:31 pm

I'm trying to get WGXepc to work in an XTM 800 series, have you had a chance to update it yet?

Can't even hear my self think with these fans running so high.

Thanks,

Title: Re: Watchguard Firebox XTM 8 Series
Post by: mppkll on August 26, 2017, 10:13:10 am
No, I have not had a chance to get back at this, I moved and my workshop/office is not yet painted and still in boxes.  I also had to put up another pfsense to run a VPN since the only ISP I could get was Comcast  >:(   In reality because of the things that I need to get done before snow flys on the new property I might not get back to this until winter.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on August 27, 2017, 07:14:28 pm
Can't even hear my self think with these fans running so high.

Yeah the fans are loud. Like excessively so!

You think all the fans are addressable by the SIO chip?

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on September 03, 2017, 02:57:26 pm

I have access to other XTM models, actually probably older models too.

Is there a list of models that are fully supported by WGXepc?

Thanks,

Title: Re: Watchguard Firebox XTM 8 Series
Post by: stephenw10 on September 03, 2017, 06:54:36 pm
The X-Core, X-Peak, X-Core/Peak-e and XTM5. Though the XTM5 only has one of it's fans easily addressable.

The SuperIO chip is completely different in the XTM8 as detailed here which makes it more challenging than simply copy/pasting with some new values unfortunately.

Steve
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on September 29, 2017, 04:20:31 pm

So if I want to be able to control the LCD and ALL of the internal fans I need to grab a X-Core, X-Peak, or X-Core/Peak-e model and not an XTM5 or 8 at this point?
Title: watchguard XTM 820
Post by: meph on October 10, 2017, 11:58:26 am
Anybody have a backup of the watchguard OS available? I bought this watchguard off ebay and it had pfsense installed... i would like to restore it. any help would be appreciated.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: meph on October 24, 2017, 10:14:57 am
Or the original firmware so i can get it to recovery mode?
Title: Re: watchguard XTM 820
Post by: DeLorean on October 26, 2017, 03:16:41 am
Anybody have a backup of the watchguard OS available? I bought this watchguard off ebay and it had pfsense installed... i would like to restore it. any help would be appreciated.

You have got PM  :)


Grtz
DeLorean
Title: Re: watchguard XTM 820
Post by: meph on October 26, 2017, 09:41:56 am
Anybody have a backup of the watchguard OS available? I bought this watchguard off ebay and it had pfsense installed... i would like to restore it. any help would be appreciated.

You have got PM  :)


Grtz
DeLorean

Thanks... let me give it a try.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: DeLorean on November 07, 2017, 06:57:51 pm
Did it work ?


Grtz
DeLorean
Title: Re: Watchguard Firebox XTM 8 Series
Post by: BrettMerrick on November 16, 2017, 03:28:24 pm
Hi,

Found this thread extremely helpful, thanks to all who have contributed!

I was able to install 2.4.1 on to the 1GB CF card by using the VGA hack and putting the installer image on a sata drive. I did have to plug the CF in shortly after boot though so it booted from the sata drive first...

I also had to manually partition the drive as it complained that it wasn't a full 1GB.

I found than once installed I could enable the serial console by modifying /boot/device.hints and switching the IRQ and Address for the uart:

hint.uart.0.at="isa"
hint.uart.0.port="0x2F8"
hint.uart.0.flags="0x10"
hint.uart.0.irq="3"
hint.uart.1.at="isa"
hint.uart.1.port="0x3F8"
hint.uart.1.irq="4"

I got the LCD working by simply installing the LCDproc package and configuring it for Parallel port 1 and Watchguard Firebox with SDEC. I made a few other setting changes to my preference, including setting the backlight to on, however it seems to switch off again after a short time.

Now I just need to sort the noise! - Anything I can help with mppkll?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on December 12, 2017, 02:38:51 pm
Any updates to the program to control the fans and LCD on the XTM 8 Series?
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on January 02, 2018, 10:14:47 pm

I'm looking at selling this XTM 850 on eBay and need to know if there's a way to return the internal hard drive back to factory defaults?

I have the SD card back to factory and it boots to the OS, however during testing of pFsense I used the drive. Is there a way to return for use with the embedded OS before I sell it?

Thanks,
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Scorch95 on January 03, 2018, 01:18:23 pm
If Im not mistaken, which I often am, I do not believe these shipped with internal drives other than the CF.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: daveinfla on January 03, 2018, 02:59:05 pm

Mine had the 2GB CF card installed and a 250GB SATA hard drive mounted in a factory mount and connected.
Title: Re: Watchguard Firebox XTM 8 Series
Post by: Scorch95 on January 03, 2018, 05:54:14 pm
I stand corrected. Do you have a picture of the mount?