-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PCI Bracket for ATX connection [SUGGESTION] #9
Comments
LOL you should probably link to that near the top of the README. Awesome though! |
Ok stupid question: Do you have a case for the ATXA-A adapter? It looks like the ATXA-A adapter card does not fit in the Blikvm shell, so I just need to know if I should design and 3D print a case for the adapter. Thanks, |
Sorry, this is a hardware design problem, you currently need to 3D print the shell for ATX-A, the interface will be unified later
At 2022-01-31 08:50:13, "Bryan Vaz" ***@***.***> wrote:
Ok stupid question: Do you have a case for the ATXA-A adapter?
It looks like the ATXA-A adapter card does not fit in the Blikvm shell, so I just need to know if I should design and 3D print a case for the adapter.
Thanks,
Bryan
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the KVM will usually be outside of the server, there is no clean way to run the ATX power breakout cables to the motherboard.
Do you know/can you recommend a PCI bracket that can pass through the ATX power connector?
I'm assuming a simple 8 pin male-to-male connector block mounted to a PCI bracket should do the trick, but I have not found one on AliExpress yet.
Otherwise, everything else is great! I would use the CM4 eMMC so I don't have to depend on an SD card, and looking forward to a POE version. I would prefer this for datacenter and remote office deployments over the normal KVM.
I do recommend forking the PiKVM repo to prebuild images with Github Actions, so that we have images that are known to work with the hardware stack (in case you need to include some custom drivers or code, or PiKVM upstream does something stupid and poisons their codebase - like colors.js and faker).
The text was updated successfully, but these errors were encountered: