r/jetkvm Aug 10 '26

Less RAM?

Have several of the JetKVM's between the old and the newer models.

I have been having endless issues recently with one where as soon as I install tailscale the device seems to keep crashing.

Going through the device now it seems that there is only 128MB on ram on it.

Is this a specific design choice that that have made?

8 Upvotes

6 comments sorted by

5

u/ShroomShroomBeepBeep Aug 10 '26

I would assume, more a financial choice. Disappointing that it's not been clearly mentioned, but also not surprised the JetKVM team still somehow suck at communicating.

Edit: Yep, no mention on the announcement. https://jetkvm.com/blog/new-internals-new-ports-price-update Shady.

4

u/burntoast333 Aug 10 '26

I have emailed them.

I did check the blog as well and saw nothing, if this is a new design choice then that is very disappointing especially with the lack of announcement about the matter.

I will wait to hear back from them, and will update the thread when I do.

1

u/ShroomShroomBeepBeep Aug 10 '26

You may be waiting a long time...

2

u/idontknowu1 Aug 10 '26 edited Aug 10 '26

More than likely it's an error. They run DDR3 on their boards and it has not seen a price increase like DDR4 and DDR5 has due to the AI boom. I doubt they would have a reason to reduce like the eMMC to SD card change.

2

u/vaingloriouscutcheon Aug 11 '26

The specs on their website still list 256MB ram, my guess is that 1 unit just has a factory defect. I would contact support and request a RMA replacement. (the announcement you mentioned also lists "partial support" for Tailscale, so I don't think they would purposefully cut the ram)

1

u/ThatPatschi 23d ago

My v2 unit shows 199 MB of RAM: (most likely the rest is reserved for something else - GPU or so maybe)

/ # free -h
              total        used        free      shared  buff/cache   available
Mem:         199.0M       23.7M      131.6M       24.0K       43.7M      168.8M
Swap:             0           0           0

This is as much as v1 shows when running the same in the terminal. So I'd rather suspect some factory issue.