From 713a9d220fd453d9f46ad0a7fb182ba971548176 Mon Sep 17 00:00:00 2001 From: Luca Beltrame Date: Sun, 7 Feb 2021 14:27:20 +0100 Subject: [PATCH] Fix image position --- content/post/2021-02-07-dyi-kvm-over-ip-with-pikvm.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) 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 6d63c04..9609139 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 @@ -123,6 +123,7 @@ I was at my wits' end, so I just [posted a question on the subreddit dedicated t I proceeded to do so, and after removing one side of the case (or the USB C cable wouldn't fit), I came up with the following solution: +{{< imgthumb src="images/2021/pikvm2.jpg" size="700x" caption="Adjusted version without daughterboard" >}} And after I attached it back to the server, lo and behold, *keyboard input was working*! @@ -133,5 +134,3 @@ That is why I said it was a mistake to use that case, or at least the daughterbo # Conclusion 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" >}}