New beta test firmware: 1.5.0 beta1 for RM1(Comet)

KVM
1

https://fw.gl-inet.com/kvm/rm1/test/glkvm-RM1-1.5.0-0825-1756094794.img

GL.iNet KVM Release Notes - V1.5.0 beta1

New Features & Improvements

Bug Fixes

  • Fix known issue
  • Fixed the problem of ustreamer-dump not being supported. You can now save screen recordings using the following command:
    ustreamer-dump --sink kvmd::ustreamer::h264 --output - | ffmpeg -use_wallclock_as_timestamps 1 -i pipe: -c:v copy my_video.mp4
7 Likes
2

That is great. Even better than having a portable version of the GLKVM app. All that is desparately needed now is tablet / touchscreen support (i.e. being able to remote control PC using Android/iPad).

2 Likes
3

are the code changes visible on github for this beta?

4

This rocks, I had found a way for remote control without VPN/tailscale and no app but what a hassle this is awesome!

1 Like
5

I have never used/changed the "Device Identity" option before and using it for the first time, I just get a black screen when chnging it from the default. Is this behaviour to be expected?

6

It would request a reboot. WEBUI should show this

7

Thanks. It is actually following the reboot that the screen goes completely black and would only resume working after changing Device ID back to default followed by another reboot.

8

Hi, May I confirm that you change the hostname before and the problem occur when upgrading to 1.5?

9

Time zone thing does not seem to work correctly, if you select either +1 or -1. I am actually in UTC-01:00 (Ireland) and time is off...

10

Using it. Works great so far. Any plans to integrate this into www.goodcloud.xyz?

11

Never tried switching the Device ID before this latest version of the firmware to be honest but I have just tried the same on a second Comet on a completely different PC at a different site and got exactly the same problem with the black screen:

111
1111584×892 63.2 KB

222
2221584×892 46.7 KB

12

After changing device ID, device reboot is needed.

image
image442×251 34.1 KB

Does the other PC you try with can restore by rebooting?

13

will be solved in the next release

14

Interesting question. I checked the backend settings, and when you set it to UTC+1, it actually sets to Paris time. The issue is that Paris observes daylight saving time, which causes it to switch to UTC+2. So, do you want it to strictly follow UTC+1 without supporting daylight saving time/winter time?

15

Seems like the simple solution is to declare daylight savings time as a crime against humanity and ban it :slight_smile:

16

Well... I am in Ireland :ireland: time zone. Not Paris./France :france: time zone. Folks in UK :united_kingdom: will have the same issue.