PrawnOS VS evdi

The OP's computer is one of those Rockchip ARM models. It is much more difficult to get an alternate OS on it compared to Intel models. Maybe this one: https://github.com/SolidHal/PrawnOS

> I'd hardly argue that the RK3399 SoC is more "open" than any of the broadcom SoCs.

What? The gru-kevin chromebook (RK3399) can be booted without using a single binary blob, absolutely everything (even the arm trusted firmware) built from source. I use mine that way.

I've never seen a laptop with a "broadcom SoC" that could make that claim.

https://github.com/SolidHal/PrawnOS

chromebooks fork linux almost as badly as androids. instead of mainline + some patches/modules you get a custom kernel made for the hardware in question, usually with lots of proprietary drivers that make it hard for users to update. this is worse for ARM chromebooks than x86 chromebooks, but often has the same result on both: instead of downloading your favorite distro's ISO and installing it, you need to find something like PrawnOS that supports your specific model. in many cases you can't dualboot either because google's gimped UEFI/uboot/whatever implementation only boots chromeOS, and once you replace it with a custom firmware chromeOS becomes unbootable

You might want to look for an installation guide for your specific model. For example I used this one to install PrawnOS on my Acer C201P

the mainstream name is core/libreboot like used here but there's various other custom firmware too

git clone https://github.com/DisplayLink/evdi.git

So I'm currently on Ubuntu 22.10 with Mesa and asahi-edge kernel. You need both to allow using primary GPU as source output. I'm using evdi 1.13.1 with the correction to set the module to the 1.12.0 to run the script displaylink from Synaptics for Ubuntu.

The RPM version never worked for me. It's only useful for getting the services installed. After that clone the repo from https://github.com/DisplayLink/evdi and change to the devel branch. Run make and sudo make install. If you use SecureBoot you also need to sign the resulting evdi.ko with your key. After that restart displaylink.service or reboot and it should work. At least it did for me. I's been a while since I had to use it.

Uninstallation steps complete. darren@pop-os:~/displaylinkfix$ ./displaylink-driver-5.6.1-59.184.run --noexec --keep Creating directory displaylink-driver-5.6.1-59.184 Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing DisplayLink Linux Driver 5.6.1-59.184 100% darren@pop-os:~/displaylinkfix$ cd ./displaylink-driver-5.6.1-59.184 darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ curl -L https://github.com/DisplayLink/evdi/archive/refs/heads/devel.tar.gz -o evdi.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 80603 0 80603 0 0 179k 0 --:--:-- --:--:-- --:--:-- 179k darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano evdi.tar.gz darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$

I'm afraid this might be a hardware issue, maybe with the cable. I don't have a second cable to swap out unfortunately. A new one won't be here until Saturday. And it seems like a hell of a coincidence for the cable to fail when there's other issues reported within the last few days that seem very similar.

https://github.com/DisplayLink/evdi states

Theres a bug in the 6.2 kernel right now with at least the evdi package (dont know about evdi-git) but can be fixed with a patch. Pr for it is already open but yet to be merged https://github.com/DisplayLink/evdi/pull/401