Homelab, Linux, JS & ABAP (~˘▾˘)~
 

Tag: Monitor

GNU/Linux

[Hardware] Monitor Firmware Update on my Samsung CHG90 (2017)

 , , , , , , ,

A few years ago, I bought a used Samsung CHG90 (LC49HG90DMUXEN) monitor on eBay. After I got the device, I learned that this model series had a hardware issue (see here or here). Fortunately, the problems only occurred every few weeks. Since some people on Reddit wrote that a firmware update had improved the situation, even though it was a hardware issue, I tried updating the firmware as well. There is a generic update guide from Samsung, but it is not detailed enough to actually do the update…

The required firmware update can be found on the Samsung website under support > user manuals and guide and by searching with the model code: LC49HG90DMUXEN

https://www.samsung.com/de/support/user-manuals-and-guide

Although the latest firmware version is from September 2020, I was able to perform an update because my monitor was still running version 1017.2. The hardest part was figuring out how to find the software updater in the monitor menu, but after a quick search in the documentation, I found the right section. The trick was to open the menu and hold down the arrow key for 5 seconds.

https://downloadcenter.samsung.com/content/UM/202103/20210305193233676/BN46-00699A-Eng.pdf

The update took only a few seconds and completed successfully. Let’s see if this improves anything…

Proxmox, Software, ZFS

[Proxmox] Installing Cockpit with ZFS Manager extension

 , , , , , ,

The Cockpit ZFS Manager requires Cockpit version 201 or above. In the Debian Buster repository there’s only cockpit version 188, so you have to use the buster backports repository, which contains cockpit version 223.

# install cockpit
echo "deb http://deb.debian.org/debian buster-backports main" > /etc/apt/sources.list.d/buster-backport.list
apt update
apt-get -t buster-backports install cockpit
# add ZFS manager
git clone https://github.com/optimans/cockpit-zfs-manager.git
cp -r cockpit-zfs-manager/zfs /usr/share/cockpit
# start cockpit
systemctl start cockpit.service
systemctl enable cockpit.service
systemctl status cockpit.service

Now browse to https://ip-address-of-machine:9090 and login.

Links

[Hardware] A guide to monitor response times

 , ,

Find the article here: A guide to monitor response times

“Response time” is basically the amount of time it takes for a pixel to change (“transition”) from one color to another, typically measured in milliseconds (ms). This is different from framerate or refresh rate of a monitor, typically measured in hertz (hz).

Here are some common refresh rates and their corresponding windows:

  • 60 hz = 1/60 = 16.67 ms
  • 75 hz = 13.33 ms
  • 100 hz = 10.00 ms
  • 120 hz = 8.33 ms
  • 144 hz = 6.94 ms
  • 240 hz = 4.167 ms

Any response time you see on a monitor box will most likely be “G2G” or gray to gray. Unsurprisingly, response times change depending on the color that is currently displayed and the color you wish to transition to.

To fully understand what a monitor is capable of, you have to consider both speed (response times) and accuracy (overshoot).

In theory, a 1 ms monitor with no accuracy issues would provide a very clean image. At 144hz, it would be displaying a frame every 6.94 ms. This means it would be transitioning for 1 ms, and providing a static image for the remaining 5.94 ms.