Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Xs 1,1-3,1 Xserve 2020 [Xs3,1]
- Thread starter nos1609
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Hi, Thanks for this! Appreciated.
I found your pcitree.sh, script. Here's the output that i think matters. (editied: see below for full output.)
Code:
┬[0000:00]
├┬00:1c.0-[04] # g1x2 [8086:3a40] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
│└─04:00.0 # g3x4 > g1x2 [c0a9:540a] [010802] (rev 01) Non-Volatile memory controller [NVM Express] : Micron/Crucial Technology P2 NVMe PCIe SSDHere's the whole thing.
Code:
#=========================================================================================
┬[0000:00]
├─00:00.0 # g1x4 [8086:3406] [060000] (rev 13) Host bridge : Intel Corporation 5520 I/O Hub to ESI Port
├┬00:01.0-[01] # g2x4 > g1x4 [8086:3408] [060400] (rev 13) PCI bridge [Normal decode] : Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1
│└─01:00.0 # g1x8 > g1x4 [1000:0056] [010000] (rev 08) SCSI storage controller : Broadcom / LSI SAS1064ET PCI-Express Fusion-MPT SAS
├┬00:03.0-[02] # g2x16 > g1x0 [8086:340a] [060400] (rev 13) PCI bridge [Normal decode] : Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3
├┬00:07.0-[03] # g2x16 > g1x16 [8086:340e] [060400] (rev 13) PCI bridge [Normal decode] : Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7
│├─03:00.0 # g3x16 > g1x16 [1002:67df] [030000] (rev e1) VGA compatible controller [VGA controller] : Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
│└─03:00.1 # g3x16 > g1x16 [1002:aaf0] [040300] Audio device : Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
├─00:0d.0 # g0x0 [8086:343a] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0d.1 # g0x0 [8086:343b] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0d.2 # g0x0 [8086:343c] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0d.3 # g0x0 [8086:343d] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0d.4 # g0x0 [8086:3418] [060000] (rev 13) Host bridge : Intel Corporation 7500/5520/5500/X58 Physical Layer Port 0
├─00:0d.5 # g0x0 [8086:3419] [060000] (rev 13) Host bridge : Intel Corporation 7500/5520/5500 Physical Layer Port 1
├─00:0d.6 # g0x0 [8086:341a] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0d.7 # g0x0 [8086:341b] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0e.0 # g0x0 [8086:341c] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0e.1 # g0x0 [8086:341d] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0e.2 # g0x0 [8086:341e] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0e.3 # g0x0 [8086:341f] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0e.4 # g0x0 [8086:3439] [060000] (rev 13) Host bridge : Intel Corporation Device
├─00:0f.0 # g0x0 [8086:3424] [110100] (rev 13) Performance counters : Intel Corporation Device
├─00:10.0 # [8086:3425] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 Physical and Link Layer Registers Port 0
├─00:10.1 # [8086:3426] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 Routing and Protocol Layer Registers Port 0
├─00:11.0 # [8086:3427] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500 Physical and Link Layer Registers Port 1
├─00:11.1 # [8086:3428] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500 Routing # 0000:00:11.1 Protocol Layer Register Port 1
├─00:13.0 # [8086:342d] [080020] (rev 13) PIC [IO(X)-APIC] : Intel Corporation 7500/5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller
├─00:14.0 # g0x0 [8086:342e] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 I/O Hub System Management Registers
├─00:14.1 # g0x0 [8086:3422] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
├─00:14.2 # g0x0 [8086:3423] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 I/O Hub Control Status and RAS Registers
├─00:14.3 # [8086:3438] [080000] (rev 13) PIC [8259] : Intel Corporation 7500/5520/5500/X58 I/O Hub Throttle Registers
├─00:15.0 # [8086:342f] [080020] (rev 13) PIC [IO(X)-APIC] : Intel Corporation 7500/5520/5500/X58 Trusted Execution Technology Registers
├─00:16.0 # g0x0 [8086:3430] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.1 # g0x0 [8086:3431] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.2 # g0x0 [8086:3432] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.3 # g0x0 [8086:3433] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.4 # g0x0 [8086:3429] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.5 # g0x0 [8086:342a] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.6 # g0x0 [8086:342b] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:16.7 # g0x0 [8086:342c] [088000] (rev 13) System peripheral : Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
├─00:1a.0 # [8086:3a37] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
├─00:1a.1 # [8086:3a38] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
├─00:1a.2 # [8086:3a39] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
├─00:1a.7 # [8086:3a3c] [0c0320] USB controller [EHCI] : Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
├─00:1b.0 # g0x0 [8086:3a3e] [040300] Audio device : Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
├┬00:1c.0-[04] # g1x2 [8086:3a40] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1
│└─04:00.0 # g3x4 > g1x2 [c0a9:540a] [010802] (rev 01) Non-Volatile memory controller [NVM Express] : Micron/Crucial Technology P2 NVMe PCIe SSD
├┬00:1c.2-[05] # g1x1 [8086:3a44] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 3
│└─05:00.0 # g1x1 [8086:10f6] [020000] Ethernet controller : Intel Corporation 82574L Gigabit Network Connection
├┬00:1c.3-[06] # g1x1 [8086:3a46] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 4
│└─06:00.0 # g1x1 [8086:10f6] [020000] Ethernet controller : Intel Corporation 82574L Gigabit Network Connection
├┬00:1c.4-[07-08] # g1x1 [8086:3a48] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5
│└┬07:00.0-[08] # g1x1 [104c:823e] [060400] (rev 01) PCI bridge [Normal decode] : Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express]
│ └─08:00.0 # [104c:823f] [0c0010] (rev 01) FireWire (IEEE 1394) [OHCI] : Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
├┬00:1c.5-[09] # g1x1 [8086:3a4a] [060400] PCI bridge [Normal decode] : Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6
│└─09:00.0 # g1x1 [102b:0522] [030000] (rev 02) VGA compatible controller [VGA controller] : Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1)
├─00:1d.0 # [8086:3a34] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
├─00:1d.1 # [8086:3a35] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
├─00:1d.2 # [8086:3a36] [0c0300] USB controller [UHCI] : Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
├─00:1d.7 # [8086:3a3a] [0c0320] USB controller [EHCI] : Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
├┬00:1e.0-[0a] # [8086:244e] [060401] (rev 90) PCI bridge [Subtractive decode] : Intel Corporation 82801 PCI Bridge
├─00:1f.0 # [8086:3a18] [060100] ISA bridge : Intel Corporation 82801JIB (ICH10) LPC Interface Controller
├─00:1f.2 # [8086:3a22] [010601] SATA controller [AHCI 1.0] : Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
└─00:1f.3 # [8086:3a30] [0c0500] SMBus : Intel Corporation 82801JI (ICH10 Family) SMBus Controller
Last edited:
The full thing would be interesting but won't give more info about this slot. Surround the text with
[code] [/code] to format it correctly.From what you've posted so far, it seems that it cannot do more than 2.5 GT/s x2 which is < 500 MB/s and matches your benchmarks.
ICH10 chipset manual doesn't mention anything greater than 2.5 Gb/s per lane for PCIe and DMI.
Ok, I'm puzzled by this. So Noob question follows....
The Xserve 3.1 sports two full 16x pcie 2.0 slots on the x58 Northbridge, but, the MXM slot is on the slower ICH10 southbridge, limiting it this slot to PCIe 1.0 performance?
Is that right?
Ah okay found a block diagram confirming this. I had no idea. That is so weird!
Explains why the mxm slot is so slow for more modern AMD GPUs definitively though. PCIe 1.0 X2. Yikes.
Attachments
There's two gen 2 x16 slots but you're only using one of them for an RX 560. Is the GPU two slots wide? How does that fit in an Xserve? Are you planning on using something else in the other slot?
The Xserve is only 1 rack unit tall so you can’t run a dual slot wide card in it. The slot on one side also has less clearance for something larger than 1 slot because there’s the mxm slot heatsink to compete with.
you can see some photos of the guts here.
Well my Xserve has not been 1U for a few years now.... There are some single slot Rx 560's Yeston make one, XFX another. Not too easy to find.
I run an Rx 590 8gb currently, but have run a 6600XT, 5700 XT, Vega 56.....I use a PCI extender with dual slot bracket and an external PSU.
I was not happy with the noise of my xserve, and when i upgraded to dual 6 cores, i felt it need a cooling system upgrade. So im more like 4U-ish
I use the other PCIe 2.0 for an Kyro evo M.2 NVME. Bootable and works great. I've probably try using the mxm slot for usb 3.0 with m.2 to pcie x4 adaptor. or for a second nvme.
Another option (though super expensive) is external PCIe chassis, like the Netstor NA255A that I have for my MacPro3,1. It gives you 4 double wide PCIe gen 3 x8 slots. Comes with a PSU.
That is interesting, but, yes kind of expensive is an understatement! You'd definitely need to have the extra PCIe.
I'm content in gaining the use of one PCIe 1.0 X2 port from the mxm slot for potentially 40 euros.
I ran two Vegas in my xserve for a while just to see how OS X would detect them. It worked. Two or more GPU's connecting through one PCIe 2.0 x16. That'd be fun to see. Look nice and beefy PSU as well.
Curious what you use in that?
Mostly for experiments. The slots are gen 3 so I can get full performance from gen 3 PCIe cards up to x8.
I've got a ASUS ThunderboltEX 4, Gigabyte GC-TITAN RIDGE, and Gigabyte GC-ALPINE RIDGE. They all work as USB 3.1 gen 2 cards (the Alpine Ridge requires some EFI code before startup to enable USB). I haven't done a lot of Thunderbolt stuff with them. A warm boot from Windows can enable PCIe tunnelling but not hot plug. I would need to flash the cards and/or add a Thunderbolt SSDT. The Thunderbolt cards can convert DisplayPort to USB-C DisplayPort Alt Mode.
https://forums.macrumors.com/threads/testing-tb3-aic-with-mp-5-1.2143042/
Recently, I did some testing with a Radeon HD 4870 Mac Upgrade GPU that I had before I got the EVGA GTX 680 Mac Edition.
https://forums.macrumors.com/thread...ngs-another-t221-thread.2387219/post-32118394
That is a lot of thunderbolt. I've considered a thunderbolt card, but, have no real need for it just now. Seen a few flashed cards for sale on ebay. I'll keep limping by on fw800.
I had a mac pro 3.1 and EVGA 680 (PC version but flashed for mac.) It's was a fast card. Not far off a GTX 970.
I had a mac pro 3.1 and EVGA 680 (PC version but flashed for mac.) It's was a fast card. Not far off a GTX 970.
Hello,
Question for anyone who is running the MacPro 5,1 firmware on the 3,1 Xserve using the x5690 CPU's (assuming that is the fastest you can get), how is the noise on the server? Does the fan array stay quiet except when there is load on the system, or does it ramp up at 100% because it is an unsupported CPU or unsupported firmware? I'm running the x5570 2.93 GHz CPU's in my 3,1 right now with the latest stock firmware. The Fans respond properly and they only are loud during initial boot and under high CPU / high heat conditions. I had put in the 3.33 CPU's a while back, with those CPU's which were never supported with the 3,1 firmware, the fans run at 100% and the thing is just way too loud. I'd consider the MacPro 5,1 firmware hack to put in x5690's, but only if the fan array works properly. There is no way to silence the box otherwise.
Question for anyone who is running the MacPro 5,1 firmware on the 3,1 Xserve using the x5690 CPU's (assuming that is the fastest you can get), how is the noise on the server? Does the fan array stay quiet except when there is load on the system, or does it ramp up at 100% because it is an unsupported CPU or unsupported firmware? I'm running the x5570 2.93 GHz CPU's in my 3,1 right now with the latest stock firmware. The Fans respond properly and they only are loud during initial boot and under high CPU / high heat conditions. I had put in the 3.33 CPU's a while back, with those CPU's which were never supported with the 3,1 firmware, the fans run at 100% and the thing is just way too loud. I'd consider the MacPro 5,1 firmware hack to put in x5690's, but only if the fan array works properly. There is no way to silence the box otherwise.
The fan array should work fine. They are controlled by the SMC rather than the bootROM.
We don’t change the SMC in this crossflashing of the rom.
I have L5640 in my 3,1 crossflashed which I’m not sure if they were ever used by Apple and the fans seem to behave properly to me.
Interesting though, I wonder why when I upgraded to the W5590 processors, the fans ramped up to 100%? The processors worked, but the box was so loud I couldn't really leave it like that. That was my primary concern with this upgrade. Do the hard drive lights, ethernet, and power lights still work as intended? The article in this thread says those work, but I read from other people that they don't after the flash.
I finally succeeded in installing Windows on the Xserve(MP5,1 flashed ).
What I used was OCLP, WX7100(GOP), and Windows 2019SV(USB).
Needless to say, without BOOTCAMP; UEFI mode.
Naturally, it's a good to also install BOOTCAMP after the installation is complete.
Also, the "Intel 82574L" was not automatically recognized, so I had to manually install the driver.
Have a good Xserve
What I used was OCLP, WX7100(GOP), and Windows 2019SV(USB).
Needless to say, without BOOTCAMP; UEFI mode.
Naturally, it's a good to also install BOOTCAMP after the installation is complete.
Also, the "Intel 82574L" was not automatically recognized, so I had to manually install the driver.
Have a good Xserve
need to do anything special to make it happen?
what's your RAM setup? with 192GB i assume you're doing opencore custom memory layout with the 12 dimms populated? curious if windows will handle the 12 dimms directly.
what's your RAM setup? with 192GB i assume you're doing opencore custom memory layout with the 12 dimms populated? curious if windows will handle the 12 dimms directly.
Sorry for the late reply. In order to use 12 ram sticks, you need to manually configure them using OC. Don't forget to set 'Custom Memory' to "True".
so uh, I have something quite incredible in my posession, I think.
I've got a brand new 2009 xserve3,1, well, it's a long story, the chassis is old, the logic board, it's been booted 3 times as of now.
the logic board was sealed fresh in the esd bag from apple when I got it off of ebay a few years ago, I've not had the time or energy to do more than fit it in the chassis and then put it aside due to health issues that nearly killed me a few years back.
anyway, today, having finally gotten some figurative steam back in the boiler, I dusted it off and I've finally booted it up with 10.11.6 and confirmed, it's stock, brand new, no serial number, no BBS has been run on it.
I installed one CPU and used the cpu bypass jumper near CPU A's thermal sensor connector, to bypass CPU B, that works great as well, not documented anywhere that I could reach via google so now that's documented somewhere at least, it's not even in the xserve3,1 service manual (I had GSX access as an authorised repairer less than 5 years ago so I had the newest version of the manual available). anyway, I've dumped the firmware, it has not had blank board serialiser run.
my intention in doing this is to make the xserve 2009 a better platform for those who are fortunate to own them, I've obtained so much help just quietly consuming content from this forum for the better part of a decade or possibly two now, it's hard to remember, made and lost a few accounts, so if this is something useful I can give back, I do it gladly.
I'm not going to share the rom yet until I've confirmed whether it's safe to do so, I don't particularly have any info or anything important on this machine, it's a chassis a customer threw away when they changed over to mac minis.
at this point I've got a working dual socket 2009 3,1 and a spare single socket 3,1 board as well as a consequence of the upgrade.
what concerns me about the "do the mp4,1 to 5,1 process" for the xserve3,1, is that we already know from things like running macschrauber's tool on the mac pro 4,1 and 5,1, that the process even leaves a mac pro's firmware in quite a mess, I don't want to imagine what it would do to an xserve3,1 if it doesn't go exactly right. as I understand it, it can shorten the machine's lifespan if the flash rom keeps getting trashed or space wasted on it from a bad firmware flash when you consider that mac os keeps writing settings to it over and over, wear levelling down that flashrom over the years.
in theory, since this machine's never been used or booted to much other than an already installed OS, the flash memory should only contain a factory flash and factory config and little much else, ready to be programmed with BBS, is this not a potential missing link needed for xserve 2009 firmware related work?
I've got a brand new 2009 xserve3,1, well, it's a long story, the chassis is old, the logic board, it's been booted 3 times as of now.
the logic board was sealed fresh in the esd bag from apple when I got it off of ebay a few years ago, I've not had the time or energy to do more than fit it in the chassis and then put it aside due to health issues that nearly killed me a few years back.
anyway, today, having finally gotten some figurative steam back in the boiler, I dusted it off and I've finally booted it up with 10.11.6 and confirmed, it's stock, brand new, no serial number, no BBS has been run on it.
I installed one CPU and used the cpu bypass jumper near CPU A's thermal sensor connector, to bypass CPU B, that works great as well, not documented anywhere that I could reach via google so now that's documented somewhere at least, it's not even in the xserve3,1 service manual (I had GSX access as an authorised repairer less than 5 years ago so I had the newest version of the manual available). anyway, I've dumped the firmware, it has not had blank board serialiser run.
my intention in doing this is to make the xserve 2009 a better platform for those who are fortunate to own them, I've obtained so much help just quietly consuming content from this forum for the better part of a decade or possibly two now, it's hard to remember, made and lost a few accounts, so if this is something useful I can give back, I do it gladly.
I'm not going to share the rom yet until I've confirmed whether it's safe to do so, I don't particularly have any info or anything important on this machine, it's a chassis a customer threw away when they changed over to mac minis.
at this point I've got a working dual socket 2009 3,1 and a spare single socket 3,1 board as well as a consequence of the upgrade.
what concerns me about the "do the mp4,1 to 5,1 process" for the xserve3,1, is that we already know from things like running macschrauber's tool on the mac pro 4,1 and 5,1, that the process even leaves a mac pro's firmware in quite a mess, I don't want to imagine what it would do to an xserve3,1 if it doesn't go exactly right. as I understand it, it can shorten the machine's lifespan if the flash rom keeps getting trashed or space wasted on it from a bad firmware flash when you consider that mac os keeps writing settings to it over and over, wear levelling down that flashrom over the years.
in theory, since this machine's never been used or booted to much other than an already installed OS, the flash memory should only contain a factory flash and factory config and little much else, ready to be programmed with BBS, is this not a potential missing link needed for xserve 2009 firmware related work?
Last edited:
Here's the dump on macintosh repository.
www.macintoshrepository.org
XServe 3,1 (2009) Brand New Firmware Dump - Macintosh Repository
This is a dump from a quite unique Xserve 2009 which had a brand new logic board that was still sealed in the packaging before I installed it in...
www.macintoshrepository.org
My Dumper has been tested to read and flash Xserve 3,1 firmware.
github site: https://github.com/Macschrauber/Macschrauber-s-Rom-Dump
download: https://github.com/Macschrauber/Mac...d/Release/Download.the.Dumper.from.github.zip
Also I was able to update a XS3,1 firmware to MP5,1 with keeping the Xserve data points (system serial number, sales order number, hardware code, logic board serial number, build date and board MAC address).
The compatibility downsides, like losing 2 ram slots and the USB front stuff are still there, of course.
Talk is cheap, here is a log of a XS3,1 - MP5,1 upgrade. This particular machine was updates with a unpersonalized board, serialized with BBS. So no sales order number and hwc. What is ok, in this case.
This machine has not yet run thru a garbage collection, so the 2nd VSS store is not populated.
Also there is EnableGop injected, what gives a native Apple boot picker with GPUs that have a valid GOP in their firmware. As role of thumb: If OpenCore displays its boot menu (without tinkering by preload GOP), then EnableGop should work.
I'd need a few more dumps of XS3,1 to get more data points. So please send me your dumps. Of course I keep them private. Also I can offer to upgrade them, properly.
[best read in Menlo]
github site: https://github.com/Macschrauber/Macschrauber-s-Rom-Dump
download: https://github.com/Macschrauber/Mac...d/Release/Download.the.Dumper.from.github.zip
Also I was able to update a XS3,1 firmware to MP5,1 with keeping the Xserve data points (system serial number, sales order number, hardware code, logic board serial number, build date and board MAC address).
The compatibility downsides, like losing 2 ram slots and the USB front stuff are still there, of course.
Talk is cheap, here is a log of a XS3,1 - MP5,1 upgrade. This particular machine was updates with a unpersonalized board, serialized with BBS. So no sales order number and hwc. What is ok, in this case.
This machine has not yet run thru a garbage collection, so the 2nd VSS store is not populated.
Also there is EnableGop injected, what gives a native Apple boot picker with GPUs that have a valid GOP in their firmware. As role of thumb: If OpenCore displays its boot menu (without tinkering by preload GOP), then EnableGop should work.
I'd need a few more dumps of XS3,1 to get more data points. So please send me your dumps. Of course I keep them private. Also I can offer to upgrade them, properly.
[best read in Menlo]
Code:
HEXADECIMAL DESCRIPTION
--------------------------------------------------------------
0x3F0098 Bootblock from 144.0.0.0.0 - rebuilt Firmware
0x3FFEF0 LBSN_BD sector Build Date YYMMDDYYMMDD: 0903x10903x1 LBSN: J591xxxxxxPHC
0x3FFFEC LBSN sector from Mac Pro 5,1
nvram.vol position: 0x120000, size: 0x30000, header size: 0x48
vss1_position: 00120048: 2456 5353 $VSS
vss2_position: 00130048: ffff ffff ....
Fsys_position: 00148000: 4673 7973 Fsys
Gaid_position: 00148800: 4761 6964 Gaid
0x120048 first stream start position ok, stored in /tmp/VSS_Store1.bin, length: 0x0000ffb8
0x148000 Fsys start position ok, header: 040000 000008
0x148800 Gaid start position ok, header: 040000 000018
scanvss_available: true
Firmware 144.0.0.0.0 (latest) built on Fri Apr 12 12:48:00 2019
Bios Version $IBIOSI: MP51.88Z.F000.B00.1904121248
Bootloader AAPLEFI1.88Z.0005.I00.1904121247 built on Fri Apr 12 12:47:00 2019
Bootblock of 144.0.0.0.0 (rebuilt firmware)
XS31, serial from firmware: YM0xxxxxxx0S
Macserial reported the serial number seems to be possibly valid
XS31 backplane
LBSN: J591xxxxxxPHC BD: 0903x10903x1 Firmware MAC: 00:xx:df:dd:xx:78 LBSN sector of XS31
EnableGop 1.4 EFI module identified
Base_20 hardware descriptor
Fsys | Gaid headers: 040000 000008 | 040000 000018
Fsys: 0 overrides, 1 override-version, 2 ssn, 3 EOF (son, hwc are missing)
fmm-computer-name: nxxxxxxx
MTC count (VSS1, normal): 20
MTC counts (VSS1, deleted) ( 1): 13
MTC counts (VSS1, deleted) ( 2): 14
MTC counts (VSS1, deleted) ( 3): 15
MTC counts (VSS1, deleted) ( 4): 16
MTC counts (VSS1, deleted) ( 5): 17
MTC counts (VSS1, deleted) ( 6): 18
MTC counts (VSS1, deleted) ( 7): 19
CSR policy is 0x77:
0x001 CSR_ALLOW_UNTRUSTED_KEXTS
0x002 CSR_ALLOW_UNRESTRICTED_FS
0x004 CSR_ALLOW_TASK_FOR_PID
0x010 CSR_ALLOW_APPLE_INTERNAL
0x020 CSR_ALLOW_UNRESTRICTED_DTRACE
0x040 CSR_ALLOW_UNRESTRICTED_NVRAM
BootOrder: 1:Boot0080
Boot0080: \System\Library\CoreServices\boot.efi
BootFFFF: \System\Library\CoreServices\boot.efi
8 firmware boots since last garbage collection, MTC counter: 13 - 20
1 (7 deleted) Memory Configs g (ok)
1 (7 deleted) Memory Configs h (ok)
1 (0 deleted) Memory Configs i (ok)
0 Microsoft certificates (ok)
0 (1 deleted) Boot PathProperties0000 (ok)
1 (0 deleted) NVRAM PathProperties0000 (ok)
1 (1 deleted) Boot00xx variables
0 (0 deleted) OCbt00xx variables
1 (0 deleted) csr-active-config (ok)
23989 bytes free space of 65464
VSS1 (Formatted) (Healthy), found 71 variables (20 valid, 51 deleted)
CRC32 checksums: ok
---------------------
all variables in VSS1:
1 (ACPI Variable):AcpiGlobalVariable (Normal)
1 (Apple Boot Variable):csr-active-config (Normal)
1 (Apple Boot Variable):efi-boot-device (Normal)
1 (Apple Boot Variable):efi-boot-device-data (Normal)
1 (Apple Boot Variable):fmm-computer-name (Normal)
1 (Apple Boot Variable):test-id (Normal)
1 (Apple NVRAM Variable):AAPL,PathProperties0000 (Normal)
1 (Apple NVRAM Variable):security-key (Normal)
1 (EFI Global):Boot0080 (Normal)
1 (EFI Global):BootFFFF (Normal)
1 (EFI Global):BootOrder (Normal)
1 (EFI Global):ConOut (Normal)
1 (EFI Global):GFXVENDOR (Normal)
1 (EFI Global):Lang (Normal)
1 (EFI Global):MemoryConfig (Normal)
1 (EFI Global):MemoryConfih (Normal)
1 (EFI Global):MemoryConfii (Normal)
1 (MTC variable):MTC (Normal)
1 (Setup Variable):Setup (Normal)
1 8983fd2d-113c-4e2b-8f47-0abfeb20a41a:SmmS3NvsData (Normal)
---------------------
1 (ACPI Variable):AcpiGlobalVariable (DELETED)
1 (Apple Boot Variable):AAPL,PathProperties0000 (DELETED)
1 (Apple NVRAM Variable):security-key (DELETED)
1 (EFI Global):Boot0080 (DELETED)
1 8983fd2d-113c-4e2b-8f47-0abfeb20a41a:SmmS3NvsData (DELETED)
3 (EFI Global):BootFFFF (DELETED)
6 (EFI Global):BootNext (DELETED)
7 (EFI Global):MemoryConfig (DELETED)
7 (EFI Global):MemoryConfih (DELETED)
7 (MTC variable):MTC (DELETED)
8 (EFI Global):ConOutDev (DELETED)
8 (EFI Global):_AGP_DISABLED (DELETED)
-------------------------------------------------------------------
LBSN sector
-------------------------------------------------------------------
Type: Section
Subtype: Raw
Fixed: No
Base: 3FFEF0h
Header address: FFFFFEF0h
Data address: FFFFFEF4h
Offset: E90h
Type: 19h
Full size: 110h (272)
Header size: 4h (4)
Body size: 10Ch (268)
===================================================================
00000000: 1001 0019 ....
-------------------------------------------------------------------
00000000: 0000 0000 0000 0000 0000 0000 ea00 23df ..............#.
00000010: xxxx xxxx xxxx xxxx xxxx xxxx xxxx 5048 xxx.J5xxxxxxx1PH
00000020: 4320 2020 2020 ffff ffff ffff ffff ffff C ..........
00000030: ffff ffff ffff ffff ffff ffff ffff ffff ................
*
00000050: ffff ffff ffff ffff ffff ffff 3039 3033 ............0903
00000060: xxxx xxxx xxxx xxxx 3718 07d0 0fff ffff 31xxxxxx7.......
00000070: ffff ffff ffff ffff ffff ffff 01ff ffff ................
00000080: ffff ffff ffff ffff ffff ffff 0000 0000 ................
00000090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
*
000000d0: 0000 0000 0000 0000 0000 0000 bf50 41eb .............PA.
000000e0: 1d00 0000 0000 0000 0000 0000 ffff ffff ................
000000f0: ffff ffff ffff ffff e802 ffff 0f09 e9fb ................
00000100: f200 0000 7856 3412 0000 ffff ....xV4.....
#-xJ59xxxxxx1PHC 090xxxxxxx3317PAxV4
===================================================================
Firmware volumes CRC32 count: 9
Firmware volumes CRC32 checksums match
Bootblock vector and checksum was updated
Bootblock CRC32 is valid
Fsys checksum is correct in YM0xxxxxxx0S 144 xs enablegop.bin
Gaid checksum is correct in YM0xxxxxxx0S 144 xs enablegop.bin
Last edited:
Here's the dump on macintosh repository.
XServe 3,1 (2009) Brand New Firmware Dump - Macintosh Repository
This is a dump from a quite unique Xserve 2009 which had a brand new logic board that was still sealed in the packaging before I installed it in...
This dump has no data points in Fsys (no system serial number etc)
but it has a MAC address, Logic Board serial number and build date in the LBSN block.
So using it with BBS gives kind of clones of the same logic board. This is not recommended, if one wants to use it with Mac Os and Apple services.
Code:
LBSN: J59xxxxxxx1PHC BD: 09xxxx09xxxx Firmware MAC: xx:xx:xx:dd:xx:xx LBSN sector of XS31
Last edited: