egpu-switcher VS jp

If you're ok with running X11, you can use egpu-switcher and modify the Xorg configuration yourself afterwards.

Only using Xorg since Wayland gave me more issues than fixes. I'm using egpu-switcher

Try installing eGPU-switcher, make sure you have the right drivers installed, and as others have said make sure you have the right cable. Last thing, only plug in or unplug the eGPU when the laptop is off.

You didn't mention the problems you ran into but it should be plug and play. You will have to set up the proper config for it to work properly, and I would recommend using hertg's egpu-switcher if you are having issues: https://github.com/hertg/egpu-switcher

I've been using egpu-switcher every single time.

The scripts are all-ways-egpu for Wayland and egpu-switcher for X11.

here is the hotplug script that seemed promising, but did not work for me (nVIDIA only) here is a more sophisticated-looking script that seems intended for Desktop-users though, and also specifically excludes hotplugging options...

It is not plug&play, but almost. https://github.com/hertg/egpu-switcher

The A750 is now a recognized PCIe device, and works with connected displays to an extent. During boot, KMS/Plymouth shows on connected displays, as well as GDM (albeit, laggy, but it did that before anyways). The problem starts with Xorg, where during startx, I get a No screens found error. My Xorg configuration was autogenerated by egpu-switcher, where it only fails in egpu mode (connected displays do not work in internal mode). GNOME on Wayland works surprisingly with my laptop display working as normal, but the eGPU's external displays come with various graphical glitches, stuttering, outputting to 1080i30 on a 1440p60 display, etc.

Several jq solutions here already, here's how you could do this in jp (pure Bash).

Seriously though, the article leads to the author's jp bash script which allows processing of JSON. It could be useful - but why it exists when jq is available, I don't know. Nonetheless, it looks like an impressive acheivment.

color='foobar';cat tests/share/package.json | jp '{"color":"'"$color"'"}' jp.++ { "color": "foobar", "name": "jp", "version": "0.0.1", "description": "A JSON processor written in Bash", "homepage": "http://github.com/dnmfarrell/jp", "repository": { "type": "git", "url": "https://github.com/dnmfarrell/jp.git" }, "bin": { "jp": "./jp" }, "dependencies": {}, "devDependencies": {}, "author": "David Farrell" }

However there was a flaw in how jp parsed large input: it repeatedly copied the input string which, for large inputs made it very slow. Maybe that's what you ran into? That is fixed now. jp can parse the 128kb of json in tests/share/ec2-describe-instances.json for example.