netkas.org forum
August 19, 2018, 12:35:41 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Information for registering users http://forum.netkas.org/index.php/topic,2246.0.html
 
   Home   Help Search Login Register  
Pages: 1 2 [3] 4 5 ... 10
 21 
 on: August 14, 2018, 04:12:09 AM 
Started by Rominator - Last post by vidkidd
Big EFI update from Apple today for the cMP in Mojave DP7.  Were up to ROM 0138.

5.0 GT/s has been enabled for MANY AMD Cards.  7850, rx470 rx480 rx580 etc.  No hardware mod required.  If there is a driver, it supports 5.0GT/s

EFI Firmware can now be updated without an EFI Card.  More microcodes.. No NVMe booting without a mod.

 22 
 on: August 12, 2018, 01:21:02 PM 
Started by Spacedust - Last post by Spacedust
I've runned linux checker and it shows Mac Pro is still vulnerable for Spectre Variant 3a and 4 so Apple needs to update microcodes again!

Quote
[root@livedvd Desktop]# ./spectre-meltdown-checker.sh                       
Spectre and Meltdown mitigation detection tool v0.38+                       

Checking for vulnerabilities on current system
Kernel is Linux 2.6.32-754.el6.x86_64 #1 SMP Tue Jun 19 21:26:04 UTC 2018 x86_64
CPU is Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz                         

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)           
    * SPEC_CTRL MSR is available:  YES                     
    * CPU indicates IBRS capability:  YES  (SPEC_CTRL feature bit)
  * Indirect Branch Prediction Barrier (IBPB)                     
    * PRED_CMD MSR is available:  YES                             
    * CPU indicates IBPB capability:  YES  (SPEC_CTRL feature bit)
  * Single Thread Indirect Branch Predictors (STIBP)             
    * SPEC_CTRL MSR is available:  YES                           
    * CPU indicates STIBP capability:  YES  (Intel STIBP feature bit)
  * Speculative Store Bypass Disable (SSBD)                         
    * CPU indicates SSBD capability:  NO                             
  * Enhanced IBRS (IBRS_ALL)                                         
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO         
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO     
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO
  * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO
  * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO                                                                             
  * CPU microcode is known to cause stability problems:  NO  (model 0x2c family 0x6 stepping 0x2 ucode 0x1e cpuid 0x206c2)                                     
* CPU vulnerability to the speculative execution attack variants               
  * Vulnerable to Variant 1:  YES                                               
  * Vulnerable to Variant 2:  YES                                               
  * Vulnerable to Variant 3:  YES                                               
  * Vulnerable to Variant 3a:  YES                                             
  * Vulnerable to Variant 4:  YES                                               

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  YES  (Mitigation: Load fences)
* Kernel has array_index_mask_nospec:  NO                                   
* Kernel has the Red Hat/Ubuntu patch:  YES                                 
* Kernel has mask_nospec64 (arm64):  NO                                     
> STATUS:  NOT VULNERABLE  (Mitigation: Load fences)                       

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigated according to the /sys interface:  YES  (Mitigation: Full retpoline)
* Mitigation 1                                                                 
  * Kernel is compiled with IBRS support:  YES
    * IBRS enabled and active:  NO
  * Kernel is compiled with IBPB support:  YES
    * IBPB enabled and active:  YES
* Mitigation 2
  * Kernel has branch predictor hardening (arm):  NO
  * Kernel compiled with retpoline option:  YES
    * Kernel compiled with a retpoline-aware compiler:  YES  (kernel rel retpoline compilation)
    * Retpoline is enabled:  YES
> STATUS:  NOT VULNERABLE  (Full retpoline + IBPB are mitigating the vuty)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
* Kernel supports Page Table Isolation (PTI):  YES
  * PTI enabled and active:  YES
  * Reduced performance impact of PTI:  YES  (CPU supports PCID, perforact of PTI will be reduced)
* Running as a Xen PV DomU:  NO
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

CVE-2018-3640 [rogue system register read] aka 'Variant 3a'
* CPU microcode mitigates the vulnerability:  NO
> STATUS:  VULNERABLE  (an up-to-date CPU microcode is needed to mitigaulnerability)

CVE-2018-3639 [speculative store bypass] aka 'Variant 4'
* Mitigated according to the /sys interface:  NO  (Vulnerable)
* Kernel supports speculation store bypass:  YES  (spec_store_bypass)
> STATUS:  VULNERABLE  (Your CPU doesn't support SSBD)

Need more detailed information about mitigation options? Use --explain
A false sense of security is worse than no security at all, see --discl

 23 
 on: August 10, 2018, 11:38:31 AM 
Started by Rominator - Last post by edgerider
Be careful, as I disc covered the hard way this cable can become "MARRIED" to the board, and only come out in pieces.

I was first getting 6 Core working in X-Serve, but you can be first with 12 Core. Not sure how fans will respond as mine were out of control anyway. And as pointed out, there is a chance you can then install Windows since 4,1/5,1 support it.


@ rominator

can you post here where the cable is located on the board?

 24 
 on: August 09, 2018, 11:40:40 AM 
Started by thebart123 - Last post by thebart123
NEVER MIND - PROBLEM SOLVED!!!!!!!!!!

SOLUTION:

(notice this is the device-id of your card which is 679a, NOT 697a as used in the example in the original post of this thread)

697a is NOT 679a!!!!!!!!

 25 
 on: August 09, 2018, 10:26:53 AM 
Started by thebart123 - Last post by thebart123
Thank You Rominator for reply

Is it something connected with "fixrom.py"?  I got no confirmation script execute it? I've installed mac Phyton - and no changer to Terminal summary Sad

I would not create new tread if my case would not be crazy nor if I would not know (I think) what I am doing Sad

Don't know what I got wrong? Java version on MacBook? Radeon BIOS dumped when drivers installed? AMD drivers installed but not Sapphire or PowerColor?

I don't think it is problem because I dumped Radeon BIOS using GPUz or programmed with Win Ati Flash instead of DOS app

 26 
 on: August 04, 2018, 05:15:27 PM 
Started by Rominator - Last post by netkas
So, cmp3,1
patched to include apfs.efi driver into firmware

high sierra 10.13.5 on hfs+

took out disk, put it into usb3.0 to sata adapter, connected to mbp2015

converted hfs+ to apfs,
Added preboot partition to apfs container ( https://www.belightsoft.com/products/resources/apfs-bootable-clone-with-command-line ) and VM partition.
updated os to 10.13.6, this added Recovery partition to apfs container as well

put ssd back into cmp3,1
macosx boots find on apfs and is updated.

 27 
 on: August 04, 2018, 04:02:17 PM 
Started by jabbawok - Last post by Spacedust
The Boot EFI hacks are fun but beware that Windows doesn't like them, AT ALL.
I flashed modded bootROM on MP3,1 adding the NVME driver.
I was still able to boot windows 7 like I always have, maybe it doesn't affect Win7 or maybe not 3,1 but what is it that windows does / complains about?

In normal mode or EFI?

 28 
 on: August 03, 2018, 10:10:34 PM 
Started by jabbawok - Last post by Ludacrisvp
The Boot EFI hacks are fun but beware that Windows doesn't like them, AT ALL.
I flashed modded bootROM on MP3,1 adding the NVME driver.
I was still able to boot windows 7 like I always have, maybe it doesn't affect Win7 or maybe not 3,1 but what is it that windows does / complains about?

 29 
 on: August 03, 2018, 09:49:39 PM 
Started by Rominator - Last post by Ludacrisvp
Will the kernel boot flag "-no_compat_check" no longer work for PlatformSupport bypass?
This made HS an easy to update machine since it no longer mattered what was in the PS.plist.

Code:
$ cat /Library/Preferences/SystemConfiguration/com.apple.Boot.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel Flags</key>
<string>-v mbasd=1 -no_compat_check</string>
</dict>
</plist>

 30 
 on: August 03, 2018, 07:34:17 PM 
Started by jabbawok - Last post by Spacedust
The Boot EFI hacks are fun but beware that Windows doesn't like them, AT ALL.

That's why I don't want to use anything like this. One software update and you will have to reimage whole Windows drive. So far my Windows 7 is rock stable on PCIe SSD (hasn't been reinstalled since 2011) and got all updates.

Pages: 1 2 [3] 4 5 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!