![]() ![]() ![]() RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible. SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock. SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-Ĭontrol: AttnInd Off, PwrInd Off, Power- Interlock. Slot #5, PowerLimit 0.000W Interlock- NoCompl. SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise. LnkSta: Speed 5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt+ LnkCtl: ASPM Disabled RCB 64 bytes Disabled- CommClk-ĮxtSynch- ClockPM- AutWidDis- BWInt- AutBWInt. LnkCap: Port #8, Speed 5GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us MaxPayload 128 bytes, MaxReadReq 128 bytesĭevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend. RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop. Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-Ĭapabilities: MSI: Enable- Count=1/2 Maskable- 64bit-Ĭapabilities: Express (v2) Root Port (Slot+), MSI 00ĭevCap: MaxPayload 256 bytes, PhantFunc 0ĭevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported. PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-Ĭapabilities: Power Management version 3įlags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B. Subsystem: Samsung Electronics Co Ltd Device a801Ĭontrol: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ +-05.0-00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 Ġ2:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 (prog-if 02 ) +-00.0 Intel Corporation 5400 Chipset Memory Controller Hub And that all worked pretty nice for me! So I knew the nvme driver of MP51 cannot be bad for my machine. and use the various commands like 'load' 'drivers' 'connect -r' 'map -u'. You can also start experimenting by entering the EFI Shell (hit ESC very fast). I modified the startup.nsh so that it also loads the nvme.efi file similarly to how it loads the apfs.efi. I copied the EFI Folder of the EFI Partition to the EFI Partition of a thumb drive in order to do the initial boot from there loading then nvme and apfs driver so the NVMe disk can be read and macOs can be booted.Ĭ) So I extracted a NVMe EFI driver from Mojave's 10.14.5 MP5,1.fd firmware file using UEFITool by "extract body" on the NVMe DXE Driver's "PE32 image section" -> Saved to nvme.efi next to apfs.efi. The latter will install a efi bootloader (actually an EFI Shell) in the EFI Partition which will load the apfs driver via a the startup.nsh script.ī) Now I wasn't able to boot the NVMe disk, because the drive cannot be seen by the firmware. When applying the dosdude patches I chose the APFS patch. Without any Boot-Rom Modification loading NVME and APFS EFI drivers from a non nvme driveĪ) I booted dosdude Mojave Patcher and installed macOs on the NVMe disk using APFS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |