goalque / automate-eGPU

Other
604 stars 103 forks source link

Os X booting freeze / amd w4100 / akitio thunder2 #7

Open irozhkov opened 9 years ago

irozhkov commented 9 years ago

External Monitor flicker for a moment and then turn off so... booting freeze during loading bar

mbp 2015 13" retina os x 10.10 or 10.11

Akitio thunder2 AMD W4100 (firepro)

Trying to restart GPU (AMD Radeon HD 7xxx)... Sep 10 22:19:28 ibook13 DumpGPURestart[753]: Saved gpuRestart report for kernel to /Library/Logs/DiagnosticReports/Kernel_2015-09-10-221928_ibook13.gpuRestart Sep 10 22:19:29 ibook13 com.apple.xpc.launchd1: Service only ran for Sep 10 22:18:48 ibook13 racoon[723]: failed to bind to address fded:c844:7264:4825:7480:8953:63a0:150d[4500](Can't assign requested address). Sep 10 22:18:48 ibook13 racoon[723]: failed to bind to address fded:c844:7264:4825:7480:8953:63a0:150d[4500]: because interface address is/was not ready (flags 2).

1 seconds. Pushing respawn out by 9 seconds. Sep 10 22:19:33 ibook13 kernel[0]: [10:0:0] GPU HangState 0x0000002e, HangFlags 0x00000007: IndividualEngineHang 1, NonEngineBlockHang 1, FenceNotRetired 1, PerEngineReset 0, FullAsicReset 1 Sep 10 22:19:34 ibook13 launchd[1]: BUG in libdispatch: 15A282a - 1631 - 0x0 Sep 10 22:19:34 ibook13 kernel[0]: 0xf0000000 0xf0000000 0xf0000000 0xf0000000 Sep 10 22:19:34 ibook13 kernel[0]: 0xf0000000 0xf0000000 0xf0000000 0xf0000000 0xf0000000 0xf0000000 0xf0000000 0xf0000000 Sep 10 22:19:34 --- last message repeated 180 times --- Sep 10 22:19:34 ibook13 kernel[0]: HWRingDumpEnd

irozhkov commented 9 years ago

i found problems only here. if u need full log, let me know

irozhkov commented 9 years ago

However, i found that i can boot with safe mode! graphic is very slow and have error message: Thu Sep 10 22:44:54 2015

* Panic Report * panic(cpu 3 caller 0xffffff80159d6a9a): Kernel trap at 0xffffff7f97d94042, type 14=page fault, registers: CR0: 0x0000000080010033, CR2: 0x0000000000000098, CR3: 0x000000000b641060, CR4: 0x00000000003627e0 RAX: 0x0000000000000000, RBX: 0xffffff80e7ba3000, RCX: 0x0000000000000020, RDX: 0x0000000000000000 RSP: 0xffffff9121fcbb00, RBP: 0xffffff9121fcbb00, RSI: 0x0000000000000000, RDI: 0x0000000000000000 R8: 0xffffff802b8f7600, R9: 0x0000000000000000, R10: 0xffffff802b8f7600, R11: 0xffffff9121fcbba8 R12: 0xffffff9121fcbc00, R13: 0x0000000000000000, R14: 0xffffff802b76f000, R15: 0xffffff802b8f7600 RFL: 0x0000000000010246, RIP: 0xffffff7f97d94042, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0x0000000000000098, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0

Backtrace (CPU 3), Frame : Return Address 0xffffff9121fcb790 : 0xffffff80158e5357 0xffffff9121fcb810 : 0xffffff80159d6a9a 0xffffff9121fcb9f0 : 0xffffff80159f4093 0xffffff9121fcba10 : 0xffffff7f97d94042 0xffffff9121fcbb00 : 0xffffff7f98b26763 0xffffff9121fcbb50 : 0xffffff8015ee2ca1 0xffffff9121fcbb80 : 0xffffff8015ee45d0 0xffffff9121fcbbe0 : 0xffffff8015ee1657 0xffffff9121fcbd20 : 0xffffff80159a0780 0xffffff9121fcbe30 : 0xffffff80158e9af3 0xffffff9121fcbe60 : 0xffffff80158cd448 0xffffff9121fcbea0 : 0xffffff80158dcfc5 0xffffff9121fcbf10 : 0xffffff80159c135a 0xffffff9121fcbfb0 : 0xffffff80159f48b6

  Kernel Extensions in backtrace:
     com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f97d68000->0xffffff7f97dd3fff
        dependency: com.apple.iokit.IOPCIFamily(2.9)[34605DF6-1FDD-337E-9E8B-3B206C132995]@0xffffff7f961a0000
        dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[32DFEE70-778B-3C05-B882-DFDA6420FAEA]@0xffffff7f96c11000
     com.apple.AMDRadeonX4000(1.3.6)[7EF533C4-1C21-3FD5-B9D5-E75105C904C7]@0xffffff7f98b21000->0xffffff7f99158fff
        dependency: com.apple.iokit.IOPCIFamily(2.9)[34605DF6-1FDD-337E-9E8B-3B206C132995]@0xffffff7f961a0000
        dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[32DFEE70-778B-3C05-B882-DFDA6420FAEA]@0xffffff7f96c11000
        dependency: com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f97d68000

BSD process name corresponding to current thread: Dock

Mac OS version: 15A282a

goalque commented 9 years ago

AMD FirePro W4100 TDP is 50W. AKiTiO specs say that PCIe x16 slot provides a maximum of 25W, which comes from the fact that TB controller needs ~30W when both ports are in use and ~12W per port. The total power consumption is > 60W and may lead to instability if you use the included 60W power brick.

Taking into account that AKiTiO is unstable with newer AMD cards in low power conditions, even if you use an ATX PSU, the result might what you described.

W4100 device id is not listed as default in AMDRadeonX4000, so the reason might be also the AMD driver itself.

1) Have you tried booting without an external monitor? 2) What do you see when you start up in verbose mode (Command-V)? 3) Open console and filter “pci pause”, do you get some rows?

irozhkov commented 9 years ago

I have 120W additional PSU If I add IOPCITunnelCompatible to KEXT IOPCIfamily, IOGraphicsfamily and ioacceleratorfamily2 I can boot with external monitor, but external monitor graphics speed is very slow (white lines during update the screen) and... my notebook main screen loose ability of scaling.

W4100 not listed, but it is only the analog of the same R7 consumer card

2) nothing bad with verbose mode. OS x got freeze after booting, during loading bar.

3) no. Do not have.

irozhkov commented 9 years ago

P.s. W4100 should be same as... R7 250 Cape Verde

1) Can not boot without external monitor (if I do not change these 3 additional KEXT)

irozhkov commented 9 years ago

p.s. I also can boot with:

goalque commented 9 years ago

Since you are using 120W power adapter, we can rule out power issue.

"nothing bad with verbose mode. OS x got freeze after booting, during loading bar."

And kernel panic happens after this + Mac reboots, or do you have to force shut down? You can locate the same rows from system console log. Would be interesting to see what lines appear in log just before the freeze.

"bad quality on external monitor If I delete IOPCITunnelCompatible from x4000 KEXT"

This is normal situation when the OS X doesn't load the acceleration driver.

What's the manufacturer of your W4100? The new 2015 MBP behaves differently than 2013-2014 models at booting stage. I probably have to do some NVRAM changes.

irozhkov commented 9 years ago

"And kernel panic happens after this + Mac reboots, or do you have to force shut down?"

Kernel panic happens in the centre of loading bar. Then i need to force shutdown. My first message contain "last rows". Maybe u need something before it? It seems like not panic, but "infinity loop" of ------Trying to restart GPU-------

"What's the manufacturer of your W4100?"

AMD. really... native from AMD inc. ) http://www.amd.com/en-us/products/graphics/workstation/firepro-3d/4100

And small off-topic. What i need to install or buy to setup this card in Windows? If i not mistaken, i need to buy one program for 25$ ?

goalque commented 9 years ago

Thanks. Just a thought that some brand may have video BIOS which is not Mac friendly. I have no experience of this card, but AMD provides Boot Camp drivers:

http://support.amd.com/en-us/download/desktop/bootcamp

With a little file copy-pasting, I can also use the latest Catalyst drivers.

irozhkov commented 9 years ago

a little file copy-pasting in Windows ? I tried to install both consumer and workstation drivers. But in both installations I had: "no compatible card found". Hm...

goalque commented 9 years ago

I have only a bunch of R9s, so I don’t know if the same method works with your card but I had to use Boot Camp driver installer. Back to OS X, you can try the following (assuming that you've already run the script):

1) Boot without eGPU

2) Replace the IOPCIMatch pattern of AMDVerdeGraphicsAccelerator in /System/Library/Extensions/AMDRadeonX4000.kext/Contents/Info.plist to 0x682C1002, which is W4100. Confirm that the block contains IOPCITunnelCompatible key.

3) sudo kextcache -system-caches

4) Shut down, connect eGPU, and turn on Mac.

If still the same result, you can revert back to original kexts by typing “sudo ./automate-eGPU.sh -uninstall”, then run the script again without option, which makes the backup.

irozhkov commented 9 years ago

Same kernel panic...(

"I have only a bunch of R9s, so I don’t know if the same method works with your card" maybe i can try?

  Kernel Extensions in backtrace:
     com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f82d15000->0xffffff7f82d80fff
        dependency: com.apple.iokit.IOPCIFamily(2.9)[34605DF6-1FDD-337E-9E8B-3B206C132995]@0xffffff7f8112d000
        dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[32DFEE70-778B-3C05-B882-DFDA6420FAEA]@0xffffff7f81bb6000
     com.apple.AMDRadeonX4000(1.3.6)[7EF533C4-1C21-3FD5-B9D5-E75105C904C7]@0xffffff7f83ab7000->0xffffff7f840eefff
        dependency: com.apple.iokit.IOPCIFamily(2.9)[34605DF6-1FDD-337E-9E8B-3B206C132995]@0xffffff7f8112d000
        dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[32DFEE70-778B-3C05-B882-DFDA6420FAEA]@0xffffff7f81bb6000
        dependency: com.apple.iokit.IOAcceleratorFamily2(203.7.1)[5178DF8C-1F96-3D87-8BD4-46B996C4184A]@0xffffff7f82d15000
goalque commented 9 years ago

It was to be expected… thanks anyway! If the card is manufactured by XFX, it likely doesn’t have Mac compatible VBIOS. For Windows, if the linked Boot Camp driver installer won’t find the card, I can’t much help. Seems that Catalyst package doesn’t contain drivers for FirePro series.

irozhkov commented 9 years ago

I can tell u more! I can not install videocard even with FirePro package. Same problem "can not detect videocard" But! I can install FirePro driver via windows autoupdate or manually "install from folder (FirePro driver folder)" But my video card is still not working in windows.

This videocard is Sapphire manufactured. As Sapphire is main (and one if we speak about firepro) AMD's enterprise partner

It is very interesting, but I can install this videocard in a PC (windows computer) both using consumer and FirePro packages.

Now i am trying to find a way (possibility) to add this driver to bootcamp Catalyst...

goalque commented 9 years ago

Sapphire should work. I guess Windows 10 has built-in AMD drivers. Currently I don’t use Windows. I’ll let you know if I find out something regarding OS X. Your results indicate that this is more likely AMD driver issue than script issue. I would try other card, older HD series should be stable with the AKiTiO.

irozhkov commented 9 years ago

yee... i know. Maybe problem with MacBook Pro 2015 13" bcs even apple thunderbolt ethernet adapter can't work with Akitio T2

capture copy
PankovSerge commented 8 years ago

Dear @goalque, i have a problem with akitio + any pcie device :\ I use bootcamp with windows 10, and pcie device in akitio don't show in device manager. I create a barrel connector and use 600w atx psu but it does not help. I check 3 or 4 thunderbolt cables, and all time no result. I try it with pcie tp-link network card, geforce gt740, etc. Any device don't recognized. But in device manager i can see "thunderbolt" and 4-5 "Pci-to-pci bridge". 12625850_10207305129178447_37340692_n 2016-01-30

Thanks!

irozhkov commented 8 years ago

Thunderbolt GPu doesn't work with Windows 10 in most cases. I recommend u to use Windows 8.1

agosto-levitomes commented 8 years ago

What? Everything should work the same in Windows 10. I would argue things have worked better since I moved to 10.

irozhkov commented 8 years ago

Macbook 2015 13" - absolutely does not work with Win10 Most users in TI wrote about problems with Win10.

agosto-levitomes - whats your config? Really interesting 4me

agosto-levitomes commented 8 years ago

I'm back on a 2014 mbpr still! Different hardware i suppose. Great Windows 10 support on this rig so far.

noberasco commented 8 years ago

Windows 10 working here with eGPU, too, but my hardware is rather old (MacBookPro8,2). Have some difficulties booting up Windows with eGPU connected (black screen, boot won't progress) but after a few reboots it usually works fine. On Mac side the boot-up process is flawless with goalque script :-)

ltomes commented 8 years ago

I experience the same boot issues intermittently with windows.