This commit is contained in:
parent
accb893a56
commit
713a9d220f
1 changed files with 1 additions and 2 deletions
|
@ -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" >}}
|
||||
|
|
Loading…
Add table
Reference in a new issue