mirror of
https://github.com/jetkvm/kvm.git
synced 2026-03-02 22:58:00 -05:00
ATX module does not seem to function #96
Labels
No labels
component/keyboard-layout
component: cloud
component: device screen
component: extensions
component: hid/keyboard
component: hid/mouse
component: network
component: timesync
component: ui
component: updater
component: usb
component: usb/hid
component: usb/storage
component: video
component: webrtc
component: webserver
need-more-details
status: working-in-progress
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/kvm#96
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Nyarumi on GitHub (Feb 1, 2025).
App: 0.3.4
System: 0.2.0
I just got my JetKVM and hooked it up with the ATX module supplying power to the USB on the board then to the JetKVM through the RJ-11 jack, which worked fine. But, I see no options on how to actually use the module and your website doesn't really mention much about it either. Has that feature not been implemented yet? Or perhaps I'm missing some setting?
@Nevexo commented on GitHub (Feb 1, 2025):
The software for it hasn't yet been implemented, the latest I know is the code is very nearly complete, so shouldn't be too far off.
@Nevexo commented on GitHub (Feb 1, 2025):
Actually - I'll keep this open until the code is in so people can find this one.
@nemymongus commented on GitHub (Feb 9, 2025):
Are there any reports of the ATX module causing stability issues? So far when I have mine connected it causes the video feed to drop on a recurring basis. The JetKVM doesn't seem to reboot and a continuous ping doesn't show any dropped packets. I still have more testing to do but the stability issues seem to resolve when I disconnected the RJ11 cable.
@jo3see commented on GitHub (Apr 3, 2025):
Hello there. It's been a couple of months since the last post. Figured I'd reach out and see if there's an update to this yet?
@diegozalez commented on GitHub (Apr 4, 2025):
It's working for me, I didn't have to update or anything it just started working
@Cah1982 commented on GitHub (Apr 4, 2025):
I couldnt get mine to work
but couldnt leave it in place as the rj11/12 is too short
I get the KVM is connected to usb for keyboard input, but will this then supply power to the ATX module? or does the ATX module need ithe USB power as well?
@BaneusCatrix commented on GitHub (Apr 4, 2025):
I got my ATX Power Control board today. It works perfect with version 0.3.8 (app) and 0.2.3 (system). The only problem was, that the Extension menu disappeared once from the JetKVM website. It came back after a site reload.
@ryan-shaw commented on GitHub (Apr 18, 2025):
@BaneusCatrix does the power button work for you? The PCs power button works fine attached through the ATX extension board, as does the HDD and power LEDs display fine in the UI, but the power button in the UI does nothing for me.
@BaneusCatrix commented on GitHub (Apr 18, 2025):
@ryan-shaw Yes, everything works. Power button, reset button and the leds, both in the web ui and physical.
@maronism commented on GitHub (Apr 19, 2025):
I have a pair of ATX Power Control boards, and the Power button in the UI does nothing. Pass-through, the power buttons on the cases work fine. Both JetKVM are updated to App 0.3.9 and System 0.2.3.
Additionally, did no one fit test the board in a half-height installation? It does not fit at all above a PCIe slot. So, in both ATX cases where each chassis slot is situated in front of a PCIe slot on the mainboard, the ATX Power board has to free float inside the case with no attachment. Why bother include a half-height bracket at all? There's so much of the Power baord that is unused, why couldn't the components have been moved slightly higher, and either the board made shorter or a notch cut out so fit over a PCIe slot?
@ghjm commented on GitHub (Apr 19, 2025):
I'm in the same situation - my power button in the UI also does nothing, but my physical power button works via passthrough.
@jo3see commented on GitHub (Apr 19, 2025):
My app has been updated to 0.3.9 and system to 0.2.3. Still no go on the ATX Power control. LEDs and physical power button works fine through the ATX Power control board. This is the main reason why I purchased this device. I need it for Unraid to remote power cycle when I'm away from home. I don't even use/need k/v/m access!
@ryan-shaw commented on GitHub (Apr 21, 2025):
Ok, so I didn’t try this as I assumed power switch polarity did not matter but I guess the KVM is powering one leg of the switch cable. I just switched them around and it works perfectly now.
@jo3see commented on GitHub (Apr 21, 2025):
OK, so I always thought ATX power supply power buttons were a single pole, single throw switch. So I understand, can you tell me which leads you reversed? Did you switch the cable connector on the cable that goes to the motherboard where it terminates on the standoffs?
@ryan-shaw commented on GitHub (Apr 21, 2025):
@jo3see yea I switched the 2 cables around on the motherboard, you can either do it there or on the ATX extension board.
@BaneusCatrix commented on GitHub (Apr 21, 2025):
I can confirm that swapping the pins of the power switch on the main board leads to a not working power on via the web ui.
@jetpacktuxedo commented on GitHub (Apr 25, 2025):
Also confirming, had the same issue, physical power button worked but not through the jetkvm, swapped the pins on the motherboard side and everything works fine now 👍
@jo3see commented on GitHub (Apr 25, 2025):
When you swapped pins, you did it at the motherboard pins, correct?
@jetpacktuxedo commented on GitHub (Apr 25, 2025):
I did say "at the motherboard side" 😂
@jo3see commented on GitHub (Apr 25, 2025):
Sarcasm aside, I get that. There are two ends of the cable that are on the motherboard side where they terminate.. at the motherboard and then the atx power board, then there's the cable that goes from that atx power board to the power switch.
This makes me wonder if the power switch is just a short to ground and the atx board does nothing but provide ground signal via one of the two pins.
@jetpacktuxedo commented on GitHub (Apr 28, 2025):
I personally would call the first "at the motherboard side", the second "at the atx module", and the third "the power switch cable". To be totally clear, I swapped the order of the pins where they terminate on the motherboard header pins. They would be very difficult to swap the order at the atx module because (at least on mine?) it is just one big long rail. I didn't want to switch the power switch cable around because it seemed less likely to do anything and also seemed more annoying to do.
I think this is very likely the issue. If I get annoyed enough by it to pull out my multimeter I can check it, but since I have it working now I honestly probably won't touch it lol. It does seem like a weird way to do that instead of just running it through a transistor or mosfet or relay or something 🤷♂️
@iLeonidze commented on GitHub (Apr 30, 2025):
Same thing here. I've tried many combinations of switching pins, but no luck.
My setup:
JetKVM is powered via a Type-C splitter. It's connected to the ATX board using the original RJ12 cable from the box. The ATX board is not powered by a separate Type-C cable; it works solely through the RJ12 connection. In the UI, I see the Power LED and HDD LED, but the Power Button and Reset Button do nothing. The physical buttons on the case work as expected, with no issues. I assume I didn't mess up the pin order, since the LED signals are received and the physical buttons function properly.
What I did:
I can't figure out what I'm doing wrong. There are no official documents explaining how to connect everything properly, but I'm confident I did it correctly. There also don't seem to be any hardware issues with the motherboard, cables, pins, or physical buttons.
@StarWhiz commented on GitHub (May 2, 2025):
I too thought it doesn't matter which wire goes where on the motherboard, because normally in person shorting the atx pins for power turns on and off the PC.... But remotely I was not having any luck.
However when I swapped the + and - wires on the motherboard for
powerand + and - wires on the motherboard forreset. They both finally work remotely!I can hold the power button on the webui to forcibly power off my computer! AMAZING.
Btw if I'm trying to power this externally I have to use a usb-A to usb-c cable or use a usb-A to C adapter for one end of my usb c to c cable.
@jo3see commented on GitHub (May 2, 2025):
Normally I’d say pics or it didn’t happen but in this case I need to just suck it up and give it a try on mine. Thank you for posting this. Hearing this from more than a couple of people makes those couple of people look not-so-crazy! Haha
@lamarios commented on GitHub (May 6, 2025):
Does the row (bottom or top) matter for which is the motherboard side and the kvm side ? There is no documentation about this and I can't even get the physical buttons to work.
@jo3see commented on GitHub (May 6, 2025):
I'd just like to take a minute and thank everyone in this thread for updating and sharing the pins on the motherboard may need reversed. I took the time to bring down my system yesterday and crack it open. Ironically, if you look on the motherboard user manual, it actually says GND on one of the two pins of the power button standoffs. When I initially connected the extension board to the motherboard, I paid no attention to neither the power button pinout or reset pinout - as no one usually does because there's never a polarity indicator on the harness coming from the front of the PC.
BUT
I can now confirm that by swapping the two pins on both my power button and reset button, I am now successfully able to reboot the device, power down, and power up the device with the JetKVM interface.
If only JetKVM spent just a little more time working on their manual to call out the silly little things like this and other problems people are having, this is such an incredible product for the price, they could sell these all over the place for people like me who don't have giant servers and utilize a regular desktop PC as a home 'server' solution!
@jo3see commented on GitHub (May 6, 2025):
I don't understand your question. I assume "the kvm side" is the extension board. On the extension board side, the black molex connector on the small 'rainbow' harness has all the pins on a straight line. On the motherboard side, all the pins are broken out individually because motherboards differ wildly with the front pin layouts so it can accomodate multiple vendors boards.
@lamarios commented on GitHub (May 6, 2025):
Sorry my question wasn't super clear.
There are two rows of pins on the board. One from the board to motherboard and another one from the case to the board.
I was wondering if it mattered which row of pin is assigned to the motherboard or the case.
@jo3see commented on GitHub (May 6, 2025):
Ahh, I understand now, no worries! Yeah, I scratched my head on that one too, but if you look on the underside of the board, they are just in parallel (meaning the pins in both rows are essentially the same), since the connections coming from the front panel do nothing more than just pass through the extension board on to the motherboard. Hope this helps!
@ryanbortoluzzi commented on GitHub (May 8, 2025):
I also had the same issue where the reset button would work in pass-through mode through the ATX module, but I was unable to control the reset button via the JetKVM software. I swapped the pins (polarity) on the ATX to motherboard wiring and the reset button now works via software. The only thing I can think of is the ATX board is acting as a dry contact closure switch using a transistor to close the circuit. The circuit closure sensing current flow from the motherboard is not being passed by the transistor. Reversing the wiring polarity allows current to flow in the path the transistor supports. Just a guess!
@JPL4494 commented on GitHub (Jun 21, 2025):
Just to confirm here, we would need to swap the + and - (or just flip the connector) for the button that isn't working, right? Neither of mine are working, so I'd flip the power and reset buttons?
@ryanbortoluzzi commented on GitHub (Jun 21, 2025):
Do you physical buttons on your case work to control the power and reset switches on the motherboard (i.e. pass through works)? If they do, then swap the +ve and -ve pins on the cable going from ATX control module to the motherboard. If your case physical buttons don't work at all, then you have some other wiring issues to investigate.
My physical buttons always worked. I had to reverse the +ve and -ve on the cable from the ATX module to the motherboard to gain software control from the KVM.
@JPL4494 commented on GitHub (Jun 21, 2025):
@ryanbortoluzzi Yeap, physical buttons work, just not the JetKVM. I'm glad to see I'm not the only person with issues, I thought I had a bad unit. Since it's on my server, I won't be testing turning it off for a while, so I'll just have to wait for a bit
@timmyo2l commented on GitHub (Jun 22, 2025):
Found this thread after much frustration, swapped the pins that are connected to the mobo and this indeed solved my problem! All virtual buttons now work!!
@wasabinator commented on GitHub (Jul 26, 2025):
I've tried everything with my setup. Swapping cables, different cables, different polarity. I can get all functions working except for power on, which is the only one I bought this board for. I suspect there is a hardware flaw with this, as the power push button daisy chained down the same cable will work fine.
@adamshiervani commented on GitHub (Oct 16, 2025):
We've updated the Troubleshooting docs to better help people with ATX board issues.
@bcyran commented on GitHub (Nov 19, 2025):
After my first attempt at connecting the ATX extension, the LED indicators worked but the buttons did not. Swapping the pins for both buttons fixed the issue, now everything works correctly.
I really think this should be mentioned in the documentation. I'm not sure what was the update mentioned by @adamshiervani above, but as of now I do not see any mention that the polarity of button pins might be important. Please consider clearly stating this somewhere in the docs.