From 69eae9c4badf3862bf85b1c4d7a6057ac897b93d Mon Sep 17 00:00:00 2001 From: Luca Beltrame Date: Sun, 7 Feb 2021 14:18:14 +0100 Subject: [PATCH] Ready to post --- assets/images/2021/pikvm2.jpg | 3 +++ content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md | 1 + 2 files changed, 4 insertions(+) create mode 100644 assets/images/2021/pikvm2.jpg diff --git a/assets/images/2021/pikvm2.jpg b/assets/images/2021/pikvm2.jpg new file mode 100644 index 0000000..c87632f --- /dev/null +++ b/assets/images/2021/pikvm2.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9aadeb9c67b1d5f13282d5af32400643d1ddeda16708af69aa7a2dfe78a5d2c +size 3825369 diff --git a/content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md b/content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md index edac231..12d831c 100644 --- a/content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md +++ b/content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md @@ -134,3 +134,4 @@ That is why I said it was a mistake to use that case, or at least the daughterbo So that's how I was able to prepare an affordable KVM-over-IP solution and be happy (?). The project's maintainer, [aside sponsorships](https://github.com/pikvm/pikvm#donate), is actually [working on a proper HAT (warning: video link)](https://www.youtube.com/watch?v=-SRL92VJ870&t=317s) which is about to go on sale: a possibly better option for those who don't want to fiddle too much like I did, which also offers additional options which require more manual work and that I did not do (like [ATX power control](https://github.com/pikvm/pikvm#hardware-for-v2) to control the server's power remotely). +{{< imgthumb src="images/2021/pikvm2.jpg" size="700x" caption="Adjusted version without daughterboard" >}}