Max Kaye

Results 50 comments of Max Kaye
trafficstars

I found a workaround: you can run it as x11 and not wayland by explicitly including x11 and disabling default features for eframe: `eframe = { version = "0.26.1", features...

> This is working perfectly but only with Intel CPUs :) With AMD CPUs it'd be +svm, but this is useless because Intel HAXM is'nt compatible with AMD virtualization :)...

Hmm, that is annoying. I have a repo with the upstream changes merged in here: https://github.com/XertroV/lg4k-linux/tree/patched_20201104-merge I've tested this and the device doesn't even show up for me anymore, so...

I have it working! However, I think that the firmware update doesn't complete if you don't fully power down (a reboot isn't good enough). When I logged back into windows...

Looks like the new firmware still works with the drivers in master: ``` ❯ dmesg | grep chip_version [ 13.496280] chip_version:20200811 ``` ![image](https://user-images.githubusercontent.com/1046448/100355043-30879280-3045-11eb-9337-c63f4b8b9a75.png) The video formats that work in OBS...

Cool, will do now. ------- dumping some useful commands here to make them easy to find later to update readme - `echo -n "0000:03:00.0" | sudo tee /sys/bus/pci/drivers/CL511H/unbind` -- replace...

Should I be using https://github.com/delphidabbler/bdiff to apply the patch btw? I didn't find anything looking for an appropriate linux package (and `patch` doesn't work). (Rebooting to windows now)

Thanks - `bsdiff` was the ticket (the package I linked didn't work) I'm now running into some compiler errors with AverMediaLib_64.o I tried applying the patch in a few ways....

I'm not sure I'm applying the patch to the right files. Going to dump some configurations here with details. ---- applying to vanilla 20201104 drivers Error: `ld: /home/xertrov/src/avermedia/cl511_20201104/driver//AverMediaLib_64.o: member /home/xertrov/src/avermedia/cl511_20201104/driver//AverMediaLib_64.o(pic_bmp.o)...

So given that I have things working with the current master on the latest firmware (20200811) and I'm not getting anywhere with the above, I'm going to close this issue....