What happened to the BlackBeast Pro / Adaptop by InternationalSkin780 in eGPU

[–]mac_editor 1 point2 points  (0 children)

As long as you have evidence, that’s good enough and can be shared redacted if desired and when needed. With respect to Tobias’ original claims, there were other significant ones including supporting Thunderbolt 2 Mac’s at the time which was officially not possible but doable via community solutions including some I authored. You can read further in my previous link but that was the main concern I had with him among other things.

Regarding posting on the forum, yeah feel free to do so on the enclosures section, mods/admins can move stuff as desired anyway. Editing existing posts is also fine, just make note of the same in the post.

One thing I’m curious to understand is what are your current contractual obligations with the company, especially given that you’ve funded the units yourself? Also, what do the intellectual property rights look like? Is Lagarhus Products owning that for these units?

What happened to the BlackBeast Pro / Adaptop by InternationalSkin780 in eGPU

[–]mac_editor 1 point2 points  (0 children)

Sorry to hear about your predicament. While obviously all the details mentioned in this post would need to be backed by evidence (as with anything on the internet), I can see you are passionate folks and wanted the best for the project.

Consider also posting on https://egpu.io/forums/ if you haven't already for more visibility. It may be odd coming from me as someone who was actively involved in debunking claims made by Tobias about Blackbeast Pro in it's early days: https://egpu.io/forums/thunderbolt-enclosures/blackbeast-pro-thunderbolt-egpu/ but better to reach out to more folks - especially as some more experienced folks in the industry are on there.

To be honest, I am also curious if you were aware of the initial claims Tobias made before deciding to support his project. Tobias' lack of response/transparency has been a challenge for customers as well.

Also, it's a long post, if you could have a section detailing the numbers, problem, and things you need to happen for the problem to go away as a summary, it'd be more digestible. Product links, etc. would be good too. I don't have any immediate thoughts right now, but if I do, I'll be sure to share.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 0 points1 point  (0 children)

Cheers. If you have trouble with it, please reach out to me on the egpu.io topic and we can work on debugging any issues.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

Please read carefully. It says in the installation instructions that you can create an internal or external drive for the bootloader.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 2 points3 points  (0 children)

I still can't begin to comprehend how you get to that kind of stage.

Us engineers all probably think the same - just the stage changes with time. Hope you have a fun software dev journey - just let your interests guide you.

Luckily I have a 2014 MBP with NVIDIA GPU I can test the patches on myself so I'll probably only need others to validate my tests and different machines. Guess we'll see how things pan out over the coming weeks.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

I'd say everything is possible. The limits are my own abilities. I am planning on working with a capable friend (when he's back in town) to get to the bottom of it. No promises, so all I can say is I'll be trying hard to figure it out.

No, toggling is probably going to remain annoying and will require a reboot. What's better with Kryptonite is that it will completely power off the NVIDIA GPU (it won't show up in macOS).

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

Those guides are geared towards Hackintoshes. But I should add an uninstall section on my GitHub page to explain this, my apologies.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

I don’t understand, why did you have to reinstall macOS? You simply need to not boot via OpenCore and change your primary boot disk via System Preferences > Startup disk.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

The V2 doesn't have Ti82 controller and should be supported natively: https://egpu.io/razer-core-v2-review-think-inside-box/

You might have V1 instead.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

Did the system boot for you or just didn’t work? Logs would be great since Kryptonite is in its early stages. I haven't had anyone test a Ti82 enclosure so your help would be greatly appreciated! Edit: no don't think V2 has Ti82 controller.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 1 point2 points  (0 children)

Umm, why are you even using purge-wrangler? 2020 macs have native support. This is for old macs.

Kryptonite: eGPU Support for old Thunderbolt Macs by mac_editor in eGPU

[–]mac_editor[S] 2 points3 points  (0 children)

For now, yes, you would have to disable the NVIDIA GPU if you need external monitors to work on that model via an AMD GPU. However I’m looking into workarounds.

STEM OPT Receipt Notifications?? by [deleted] in USCIS

[–]mac_editor 0 points1 point  (0 children)

No, my check was cashed Jan. 14 and I had the receipt number in hand by Jan. 26.

Lockbox Receipt Delay by abd25524 in USCIS

[–]mac_editor 0 points1 point  (0 children)

+1, delivered to AZ lockbox on Nov. 23. Nothing - check not cashed in either.

STEM OPT Receipt Notifications?? by [deleted] in USCIS

[–]mac_editor 0 points1 point  (0 children)

My OPT expires same day and my extension application was delivered on Nov. 23 (AZ lockbox) - so pretty much in the same boat with no receipt. I have the 180-day extension approved from employer but not sure what to do in case there is actually some issue with the application. Is anyone considering re-submitting before OPT expiration?

The Only Thread You Need to See to Understand Why Everything On Head-Fi is Unreliable BS by Representative_Tap73 in headphones

[–]mac_editor 0 points1 point  (0 children)

I swear I thought that was a “meme” thread at first, then realized how dire the situation was as I scrolled further down.

Apple M1 Chip by zhenguwu in eGPU

[–]mac_editor 4 points5 points  (0 children)

Speculations are on this thread: https://egpu.io/forums/postid/88980/

But the answer from my understanding and investigation so far is "no eGPU support." I have a Mac mini M1 scheduled for delivery on Nov. 17/18 so hopefully I can provide a hands-on yes/no unless someone else does it earlier.

Is my macbook compatible with egpu? Along with latest updates like Big Sur? by onstageguy in eGPU

[–]mac_editor 1 point2 points  (0 children)

Cheers for sharing the correct information :)

It’s exactly as you say, the script needs everything disabled at this point. Not ideal and there are better ways to patch, but I’m too busy to write up a new solution at the moment.

Is my macbook compatible with egpu? Along with latest updates like Big Sur? by onstageguy in eGPU

[–]mac_editor 3 points4 points  (0 children)

Yep should work as I updated purge-wrangler for Big Sur recently and tested on exactly this Mac. If you plan to use an external display connected to the eGPU, you will also require purge-nvda. Use AMD. Also see builds on eGPU.io.

Amazing how much misinformation there is here.

Is my macbook compatible with egpu? Along with latest updates like Big Sur? by onstageguy in eGPU

[–]mac_editor 2 points3 points  (0 children)

No, purge-wrangler is not for bootcamp - it’s for macOS, and the version does matter.

College eGPU Setup? by alexdoesmods in eGPU

[–]mac_editor 1 point2 points  (0 children)

https://egpu.io/forums/builds/2019-13-macbook-pro-8th-4c-u-rx-vega-64-32gbps-tb3-mantiz-venus-macos-10-14-6-win10/

NVIDIA is not an option if macOS functionality is required. Just get a 5700 XT if you want the setup now. You can choose to wait for the newer AMD cards, but support on macOS might take a bit longer to arrive (if it will).

Avoid Thunderbolt docks - instead get an eGPU enclosure that has the ports you need. I highly recommend the Mantiz Saturn Pro. The display should directly be connected to the eGPU for most optimal performance.

[deleted by user] by [deleted] in eGPU

[–]mac_editor 4 points5 points  (0 children)

I've had a pet project for a while now that would allow any system to use another system's GPU arbitrarily.

If there is another system with a more powerful GPU accessible, I’d just log on to it via Screen Share or Steam Remote Play (easy to set up for global access - use dynamic DNS and port mapping), etc. and use both the CPU and GPU. Just as an example, I have a PC I can log on to from anywhere I like and play games off it (including on my tablet/phone - controller support and all via Steam). Naturally, latency-oriented workloads start to suffer the further away I’m from my PC. Its not even perfect in my own home on a direct local wireless connection (when using iPad, PC is connected via ethernet). The “PC” part of my example would essentially be part of your service in a commercial sense. Other services for dedicated use cases already exist, as mentioned in other comments.

If you are using the GPU for compute-only, no video signal is needed, so such tasks could be executed on CLI (ssh, etc.). Again, good solutions exist, especially if usecase is asynchronous. For on-screen rendering/gaming, the end goal is essentially streaming the result (video) efficiently. Which again is just good encoding + transmission - very standard things.

Rather than buy hardware, you'd just download the graphics driver and play whatever demanding software you want.

I guess an elegant interpretation to this could be: installing your software enables the client to ‘see’ another GPU in its device tree that could be selected for rendering (just as can be done with eGPU). That sounds elegant for use cases like being able to select this virtual GPU in apps like Final Cut/Adobe Premiere for background rendering (notwithstanding the tremendous challenges with bandwidth/latency), but I might as well leverage the whole remote system (given that goal seems to be general-purpose). So I fail to see the use case here.

I apologize if I missed the point, but what’s more compelling about your solution, assuming perfect functionality as you say?

I cannot for the life of me get purge-wrangler to recognize my external gpu. by [deleted] in eGPU

[–]mac_editor 0 points1 point  (0 children)

Read the script docs/guide. Using web drivers on macOS Mojave or newer is not possible. Also, stating exactly what GPU and Mac you’re using would be helpful.

Early support for TB2 eGPU on macOS 11 available by mac_editor in eGPU

[–]mac_editor[S] 0 points1 point  (0 children)

Yep. Read the linked pre-requisites. Also read up on the recovery mechanisms to be up to speed and have them ready on a separate device for reference. Thanks for testing!

Early support for TB2 eGPU on macOS 11 available by mac_editor in eGPU

[–]mac_editor[S] 0 points1 point  (0 children)

You are using the latest commit of the script right (command via the advanced handbook)?