Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Watchguard XTM 5 Series

    Scheduled Pinned Locked Moved Hardware
    1.1k Posts 130 Posters 1.5m Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • tiggymiggyT
      tiggymiggy
      last edited by

      @stephenw10

      OK, so looks like I need to generate this file. All I can find is Hackintosh community posts. Is it the same process?

      stephenw10S 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator @tiggymiggy
        last edited by

        Yup. Try my 8400 file. Probably a single edit from that. Or it might just work fine as is.
        xtm5_e8400.aml.txt

        tiggymiggyT 1 Reply Last reply Reply Quote 0
        • tiggymiggyT
          tiggymiggy @stephenw10
          last edited by tiggymiggy

          @stephenw10 Thanks for this file, I will try it in my pfsense install per your earlier posts in this thread.

          I am comparing it ti t-rexy's aml files, looks like I just need to get the right values in the _pr section.. The question is, how do I find or generate the correct values for this section?

           Scope (_PR)
              {
                  Processor (CPU1, 0x01, 0x00000810, 0x06)
                  {
                      Name (_PPC, Zero)  // _PPC: Performance Present Capabilities
                      Name (_PCT, Package (0x02)  // _PCT: Performance Control
                      {
                          ResourceTemplate ()
                          {
                              Register (FFixedHW, 
                                  0x10,               // Bit Width
                                  0x00,               // Bit Offset
                                  0x0000000000000199, // Address
                                  ,)
                          }, 
          
                          ResourceTemplate ()
                          {
                              Register (FFixedHW, 
                                  0x10,               // Bit Width
                                  0x00,               // Bit Offset
                                  0x0000000000000198, // Address
                                  ,)
                          }
                      })
                      Name (_CST, Package (0x02)  // _CST: C-States
                      {
                          One, 
                          Package (0x04)
                          {
                              ResourceTemplate ()
                              {
                                  Register (FFixedHW, 
                                      0x01,               // Bit Width
                                      0x02,               // Bit Offset
                                      0x0000000000000000, // Address
                                      0x01,               // Access Size
                                      )
                              }, 
          
                              One, 
                              0x02, 
                              0x61A8
                          }
                      })
                      Name (_PSS, Package (0x04)  // _PSS: Performance Supported States
                      {
                          Package (0x06)
                          {
                              0x0BB8, 
                              0xFDE8, 
                              0x0A, 
                              0x0A, 
                              0x0924, 
                              0x0924
                          }, 
          
                          Package (0x06)
                          {
                              0x0A6A, 
                              0xD228, 
                              0x0A, 
                              0x0A, 
                              0x081E, 
                              0x081E
                          }, 
          
                          Package (0x06)
                          {
                              0x091D, 
                              0xB98C, 
                              0x0A, 
                              0x0A, 
                              0x071A, 
                              0x071A
                          }, 
          
                          Package (0x06)
                          {
                              0x07D0, 
                              0xA410, 
                              0x0A, 
                              0x0A, 
                              0x0616, 
                              0x0616
                          }
                      })
                  }
          

          EDIT:
          File works! Now showing frequency strangely enough, of course max is now showing 3Ghz as the 8400 max frequency is. Really excited to get this aml file sorted!

          freq.png

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

                        Package (0x06)
                        {
                            0x07D0, 
                            0xA410, 
                            0x0A, 
                            0x0A, 
                            0x0616, 
                            0x0616
                        }
            

            It's been a while but IIRC you need one entry for each state.
            0x07D0 is 2000MHz the lowest speed
            0xA410 is the CPU voltage but I forget how that's calculated
            0x0616 is the CPU wattage passed to the OS, what pfSense shows in the sysctls.

            tiggymiggyT 1 Reply Last reply Reply Quote 0
            • tiggymiggyT
              tiggymiggy @stephenw10
              last edited by

              @stephenw10

              Could the voltage calculation have something to do with this? values are off... seem to need to divide by 4 to get in the right ballpark. i will keep looking though

              Meaning of the fid and vid
              The frequency ID (fid) is the multiplier for the reference clock (e.g. the FSB clock). The voltage ID (vid) is processor specific.

              Unfortunately Intel publishes no information about the meaning of this value but the conversion formula for Core CPU's seems to be

              UCpu = 700 mV + vid x 12.5 mV

              and for Core 2 CPU's it seems to be

              UCpu = 800 mV + vid x 12.5 mV

              1 Reply Last reply Reply Quote 2
              • X
                Xerox
                last edited by

                Hi all
                Is amibcp useful to change what is displayed on LCD ??
                What field ?

                After flashrom xtm5_83.rom it displays pfsense v1.8

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  You have to extract the module and then hex-edit it to change that. Or at least that's what I did long, long ago!

                  There are some more details on the forum here if you search through it.

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • C
                    CodeJACK
                    last edited by

                    Maybe you are referring to once pfsense is booted, you want to see other details on the LCD?

                    If so, you need to install the LCDproc package from the pfsense package manager. You will then see all the options that can be output on the LCD.

                    I've not been able to get this working with 2.7 though. So if anyone has any ideas for that???

                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Works fine in 2.7 for me. What problem are you seeing?

                      The only issue is the button mapping is incorrect. I think that's because it conflicted with the older devices at the time but none of those run pfSense any longer so maybe time to update it.

                      C 1 Reply Last reply Reply Quote 0
                      • C
                        CodeJACK @stephenw10
                        last edited by CodeJACK

                        @stephenw10 LCDproc service wont even start on mine.

                        Maybe its something left over from the upgrade as the install of Unifi Network Manager is also screwed since upgrading. ( https://github.com/unofficial-unifi/unifi-pfsense )

                        Is there any log in particular that I can explore to find out exactly why the service wont start?

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Try to start the service then check the system log. Though anything could be happening if you loaded that unifi package. That could very well be completely broken in 2.7 and may have pulled in some bad pkgs that also broke lcdproc.

                          C 1 Reply Last reply Reply Quote 0
                          • C
                            CodeJACK @stephenw10
                            last edited by

                            @stephenw10 Yeah, I thought that too but stripped it out and still have the same issue. I might try fresh install this weekend and see if there is any better results.

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              If you try starting lcdproc at the CLI it might throw more useful errors. If there have been some bad packages pulled in there will likely be missing lib errors.

                              C 1 Reply Last reply Reply Quote 1
                              • C
                                CodeJACK @stephenw10
                                last edited by CodeJACK

                                @stephenw10 OK, couldnt wait and had a look. So it seems there was a new version of LCDproc released in the past couple of days. I was using 0.11.4_1 but this version is now installed: 0.11.4_2
                                Yup, some changes were made but not seemingly something that should have affected me:
                                https://github.com/pfsense/FreeBSD-ports/commits/devel/sysutils/pfSense-pkg-LCDproc

                                It wouldnt start manually either when i ran "service lcdproc onestart" so I tried running "service LCDd onestart" and it started and displayed the server stats. So I restarted LCDproc and now its running without issues :-)

                                So I was either doing something stupid before or this new versions resolved something. Im thinking the former :-)

                                1 Reply Last reply Reply Quote 1
                                • X
                                  Xerox
                                  last edited by

                                  I never installed pfsense on this machine, I installed a voip pbx based on centos7, installed flashrom and flashed xtm5_83.rom
                                  From there, display says "pfsense v1.8" or so....

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Yeah, it's hardcoded in the BIOS module. To remind you to install pfSense. 😉

                                    X 1 Reply Last reply Reply Quote 0
                                    • X
                                      Xerox @stephenw10
                                      last edited by

                                      So can't I modify the .rom file directly ?

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        That's not what I did. I opened the rom file, extracted the module, hex-edited it then reinserted the module. It was years ago though and pretty much the first time I'd tried anything like that so there may well be a better way now.

                                        1 Reply Last reply Reply Quote 0
                                        • X
                                          Xerox
                                          last edited by

                                          Well, I don't understand the part "extract" the module from .rom file, which software to do it ?

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            Xerox @waterwall
                                            last edited by

                                            @waterwall said in Watchguard XTM 5 Series:

                                            The MMTool program is used to extract/insert/replace individual modules within the BIOS

                                            A little step ahead....
                                            MMtool shows me various modules, which one is related to LCD string ??

                                            X 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.