Note: this guide is for Windows, you may use it for getting an idea of what the requirements are for a successful firmware but don’t expect a guide for any other OS to be made. If you find this guide saving you time and hassle you can thank me here.

Prepare your USB stick

You will need to property format and partition your USB in order for the monitor to detect the files. Let’s wipe all the data in a USB stick below.

• Open a Command Window (cmd)
• Enter diskpart
• Enter list disk (it is important you KNOW which disk is the USB key you are formatting)
• Enter select disk x where x is your USB key
• Enter clean
• Enter convert MBR
• Enter create part primary
• Enter select part 1
• Enter active
• Enter format fs=fat32 label=”firmware” (Label is optional – ensures USB key is labelled as ”firmware” in Explorer etc)

Download firmware and copy to USB

Visit samsung.com support page for the G9 monitor, grab the .zip file containing the update. It should look like something like “M-T9549GGAA-1016.0[1109]” (1016.0 is the current version as of this posting).

1. Download .zip file from samsung.
2. Unpack .zip
3. Grab the single file “M-T9549GGAA-1016.0[1109]” and put it on the USB stick on the parent (never put inside a folder inside usb stick).
4. Connect USB to back of monitor; ensure all other USB plugs are unplugged and only the USB stick is connected.
5. Turn on monitor (if not already on), go to MENU > Support > Software Update and hit enter.
6. Monitor should detect the update file/usb stick and apply the newest firmware.

Validate a successful update

Before and after a firmware update do these steps to check your firmware version on the monitor.

1. Turn on monitor (if not already on).
2. Go to MENU > Support > Information
3. Your Model, Serial Number, Software version is displayed. Take note of it.

If samsung.com says your current version is equal or higher than their download then your firmware does not need to be updated.

Important notes (read this!)

• DO NOT RENAME the .img files after unzipping. Just copy them to USB as it is named.
• SAMSUNG ARE IDIOTS. Upgrading a very old firmware to latest version may not be detected as an update; regardless of the proper naming and format in the USB stick. If you face errors of ‘no update files detected’ then find the next firmware release after your current running firmware. I was forced to upgrade from 1008 firmware to M-T9549GGAA-1012.1[984C].img before I was able to flash the latest version downloaded from samsung’s website.

If this guide / tips / how-to saved you time consider thanking me here.

You would think this would be pretty easy, a few clicks and done? That wasn’t my experience on Azure and setting this up isn’t easy nor straightforward. Below is how to get it done, if this helps you – you can buy me a coffee or beer.

Updates

June 2021: Reader “Ben R” contacted me about this article and shared some noteworthy information for folks using older VM images or installations. DHCPv6 may be disabled and must be manually enabled. See this article for enabling DHCPv6 on Azure.

# Find the route decision for a given address.
ip route get 2a00:1450:4001:820::200e

ip -6 route
route -A inet6 (apt-get install net-tools) # equivalent to netstat -rn -A inet6
netstat -A inet6 -rn
netstat -r
ip -6 route show table 51820
ip -6 neigh
ip -6 neigh show proxy

# DHCPv6 release / renew
dhclient -6 -r ens18
dhclient -6 ens18

# Flush IPv6 neighbors cache
ip -family inet6 neigh flush any

# Find the route decision for a given address.
ip route get 2a00:1450:4001:820::200e

# Request a router advertisement (apt-get install -y ndisc6)
rdisc6 eth0

# Perform a Neighbor Solicitation (arp IPv4 equivalent) (apt-get install -y ndisc6)
ndisc6 2001:db8::42 eth0

# ping multicast address to have all link-local hosts to respond.
ping ff02::1%eth0

Good articles about IPv6:

• IPv6 range blocks
• IPv6 unicast, anycast, multicast – well known addresses.

Troubleshooting tools:

• IPv6 ping from multiple locations.

# zpool set autoexpand=on {pool name}

# zpool online -e {pool-name} {disk name/id as displayed on zpool status}

Your pool should resize after running the second command. The first command was only to make sure you had set the zfs property that’s needed for the second command to expand the pool.

So I created a scheduled task that resets the device, after resuming from hibernate open your Event Viewer > System.

Look for event ID 27 – “The boot type was 0x2.” right click  “Attach task to this event”

Run program: powershell.exe

Arguments: Restart-NetAdapter -InterfaceDescription ‘Edimax AC1750 Wi-Fi USB Adapter’ -Confirm:$false

This should fix the issue automatically after every reboot. Your interface description may be different, in powershell run “Get-NetAdapter” to get the device’s specific and edit the arguments above as needed.

The problem with creating a directory for something before is mounted is that when zfs-mount.service runs and attempts to mount the zfs mount points you will get these kind of errors:

root@pve:~# systemctl status zfs-mount.service
● zfs-mount.service - Mount ZFS filesystems
Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2017-06-30 18:10:21 PDT; 21s ago
Process: 6590 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
Main PID: 6590 (code=exited, status=1/FAILURE)

Jun 30 18:10:19 pve systemd[1]: Starting Mount ZFS filesystems...
Jun 30 18:10:20 pve zfs[6590]: cannot mount '/gdata/pve/subvol-102-disk-1': directory is not empty
Jun 30 18:10:20 pve zfs[6590]: cannot mount '/gdata/pve/subvol-106-disk-1': directory is not empty
Jun 30 18:10:20 pve zfs[6590]: cannot mount '/gdata/pve/subvol-109-disk-1': directory is not empty
Jun 30 18:10:21 pve systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE
Jun 30 18:10:21 pve systemd[1]: Failed to start Mount ZFS filesystems.
Jun 30 18:10:21 pve systemd[1]: zfs-mount.service: Unit entered failed state.
Jun 30 18:10:21 pve systemd[1]: zfs-mount.service: Failed with result 'exit-code'.

Fixing the root of the problem: change how proxmox deals with mounts by editing /etc/pve/storage.cfg – you need to add “mkdir 0” and “is_mountpoint” to the directory mount. Example:

dir: gdata-dump
path /gdata/vz
content iso,vztmpl,backup
maxfiles 0
shared 0
mkdir 0
is_mountpoint 1

Now we need to do some system cleanup before we reboot and confirm the problem is fixed.

Let’s check which mount points have failed:
root@pve:~# zfs list -r -o name,mountpoint,mounted

Now let’s umount all zfs mount points (except rpool of course – assuming the rootfs is zfs)

# zfs umount -a

After making sure ZFS mount points are unmounted, now we can delete the empty folders. Recall the failed mount points that the zfs list command gave you and one by one delete them like so:

# rm -rf /gdata/pve/subvol-102-disk-1

Do this for each folder that showed issues mounting. You have a choice to remount everything with zfs mount -O -a — or better… reboot the system and check its fixed. I like the later better. So reboot.

After it boots back up check that service was able to mount zfs without issues:

# systemctl status zfs-mount.service
# zfs list -r -o name,mountpoint,mounted

That’s all folks… if you made the edit to storage.cfg and added the two variables this should not occur again. This was an annoying bug to deal with but good to have found a better solution than a startup script doing some dirty tricks!

In *nix any usage of well-known ports (aka 1024 or less) requires special privileges or a kernel setting. In FreeBSD a simple sysctl net.inet.ip.portrange.reservedhigh =1 was enough to allow the BSD jail to use any port on the jail.

On LXC, I had to figure out how to do the same thing and its quite different. My environment is a debian stretch LXC container but should work on other linux versions.

# apt-get install libcap2-bin
# setcap 'cap_net_bind_service=+ep' /usr/bin/transmission-daemon

In the example above, the binary /usr/bin/transmission-daemon is now able to open any port, or port 80 http in my case all while running a service as a non-root user.

Hopefully these helps folks out there, the answer took some digging but I already had an idea on what was needed thanks to my FreeBSD experience in zones

Jun 11 12:15:54 gserver xhci_do_command: Command timeout!
Jun 11 12:15:54 gserver xhci_do_command: Controller reset!
Jun 11 12:15:54 gserver xhci0: Resetting controller
Jun 11 12:15:54 gserver usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored)
Jun 11 12:15:54 gserver xhci_device_state_change:
Jun 11 12:15:54 gserver ugen0.2: <Unknown> at usbus0 (disconnected)
Jun 11 12:15:54 gserver uhub_reattach_port: could not allocate new device
Jun 11 12:15:54 gserver xhci_root_intr: port 2 changed
Jun 11 12:15:55 gserver xhci_root_intr: port 2 changed
Jun 11 12:15:55 gserver xhci_root_intr: port 4 changed
Jun 11 12:15:55 gserver xhci_ep_clear_stall:
Jun 11 12:15:55 gserver xhci_cmd_enable_slot:
Jun 11 12:15:55 gserver xhci_do_command: Command timeout!
Jun 11 12:15:55 gserver xhci_reset_command_queue_locked:
Jun 11 12:15:55 gserver xhci_reset_command_queue_locked: Command ring running
Jun 11 12:15:55 gserver xhci_reset_command_queue_locked: CRCR=0x00000000057cfd80
Jun 11 12:15:55 gserver xhci_do_command: Command timeout!
Jun 11 12:15:55 gserver xhci_do_command: Controller reset!
Jun 11 12:15:55 gserver usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored)
Jun 11 12:15:55 gserver xhci_device_state_change:
Jun 11 12:15:55 gserver ugen0.2: <Unknown> at usbus0 (disconnected)
Jun 11 12:15:55 gserver uhub_reattach_port: could not allocate new device
Jun 11 12:15:55 gserver uhub0: at usbus0, port 1, addr 1 (disconnected)
Jun 11 12:15:55 gserver xhci_set_hw_power:
Jun 11 12:15:55 gserver xhci_set_hw_power_sleep: Stopping the XHCI
Jun 11 12:15:55 gserver xhci_halt_controller:
Jun 11 12:15:55 gserver xhci_set_hw_power_sleep: Starting the XHCI
Jun 11 12:15:55 gserver xhci_start_controller:
Jun 11 12:15:56 gserver xhci_start_controller: CONFIG=0x00000000 -> 0x00000020
Jun 11 12:15:56 gserver xhci_start_controller: ERSTSZ=0x00000000 -> 0x00000001
Jun 11 12:15:56 gserver xhci_start_controller: ERDP(0)=0x00000000057cf080
Jun 11 12:15:56 gserver xhci_start_controller: ERSTBA(0)=0x00000000057cf000
Jun 11 12:15:56 gserver xhci_start_controller: CRCR=0x00000000057cfd80
Jun 11 12:15:56 gserver xhci_set_hw_power:
Jun 11 12:15:56 gserver uhub0: <0x1912 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
Jun 11 12:15:56 gserver uhub0: 4 ports with 4 removable, self powered
Jun 11 12:15:56 gserver xhci_set_hw_power:
Jun 11 12:15:56 gserver xhci_root_intr: port 2 changed
Jun 11 12:15:56 gserver xhci_root_intr: port 4 changed
Jun 11 12:15:56 gserver xhci_ep_clear_stall:
Jun 11 12:15:56 gserver xhci_cmd_enable_slot:
Jun 11 12:15:57 gserver xhci_do_command: Command timeout!

Trying the following without rebooting did not work

[root@gserver] ~# sysctl hw.usb.xhci.xhci_port_route=-1

I enabled debugging to get the logs:

[root@gserver] ~# sysctl hw.usb.xhci.debug=1

Apparently we need to add this to: /boot/loader.conf and reboot then try again.

# Workaround desantolo.com USB3 loop
sysctl hw.usb.xhci.xhci_port_route=-1

On servers with more than two network interfaces Debian/Proxmox renames all interfaces and does not properly detect eth0 as the on-board ethernet as many other linux flavors. This may cause a mild headache if you just installed Proxmox with static IP addresses using the installer and upon reboot you can’t access any network resources.

I already explained the cause and you could argue that on the Proxmox installer they could add a built-in network detection check to properly label eth0 as eth0 as the device is named in many other linux distros. That currently does not exist so I will walk you around the troubleshooting.

Upon reboot or first boot after the installation is complete:
# ip link

The bridge interface (vmbr0) should read “NO-CARRIER, MULTICAST, UP” as well as “state down” a few words further to the left of the results.

# dmesg | grep eth

Read the entries in the dmesg logs, it tells you the name of network interfaces on your system.

“NO-CARRIER” indicates it does not detect an uplink, the interface is configured but none of its bridge members have a network cable or connection being detected.

To fix this you will want to run the following commands:
# ifdown -a
# vi /etc/network/interfaces

By default the installer sets up “eth0” as your only bridge member since the network card numbering got setup differently, the logical name on proxmox for eth0 is actually eth2.

Edit the single instance of eth0 with eth2 – save the file and exit the editor.

# ifup -a
should try to bring back up your interfaces. Trying pinging your network gateway, it should be working now. Cheers.

The problem I recently encountered was trying to find the executable PATH of the git-bash.exe so that I can configure my Webstorm IDE to use it. All the documentation on the internet seems to point to C:/Program Files/Git folder but Github may have changed this as in the latest release I downloaded (v 3.3.3.0) the files reside elsewhere and I will share where to find them.

To find your git-bash.exe path try the following:

1. Open File Explorer and put %AppData% in the address bar, hit enter.
2. It should redirect to something like:  C:\Users\Giovanni\AppData\Roaming
3. Now change folders from Roaming to Local
4. You should now be at: C:\Users\Giovanni\AppData\Local 
5. Find the Github folder, enter it.
6. You should see a list of files and folders, we care about “PortableGit” it has a longer name that just PortableGit, so enter it.
7. You will see git-bash.exe in there.
8. Go back into Webstorm > Settings > Terminal
9. Set your terminal to this new path, in my case: “C:\Users\Giovanni\AppData\Local\GitHub\PortableGit_d7effa1a4a322478cd29c826b52a0c118ad3db11\git-bash.exe”

You’re all set! Webstorm should now be able to launch Github Desktop’s git-bash.exe as the terminal, no additional software required.

There is a gotcha: the terminal window will open separate from Webstorm window, if you want a tab under your code then I suggest to download and install git for windows in addition to Github Desktop.https://git-for-windows.github.io/