Skip to content

InfoPanel Linux 0.3.8 alpha

Choose a tag to compare

View all tags
@emaspa emaspa released this 18 Oct 13:50
v0.3.8
This tag was signed with the committer’s verified signature.
emaspa Emanuele
SSH Key Fingerprint: hKua76DmRCG9XHWIXqnjM0v9IWHAa8EtBZS8kZNe1TI
Verified
Learn about vigilant mode.
d5bd4d3
This commit was signed with the committer’s verified signature.
emaspa Emanuele
SSH Key Fingerprint: hKua76DmRCG9XHWIXqnjM0v9IWHAa8EtBZS8kZNe1TI
Verified
Learn about vigilant mode.

Adds the Valkyrie V360 AIO screen, plus experimental support for the Valkyrie MC360.

Install

Ubuntu 26.04

sudo apt install ./infopanel_0.3.8_amd64.deb

Fedora 44

sudo dnf install ./infopanel-0.3.8-1.x86_64.rpm

Arch Linux, from the infopanel-bin AUR package:

yay -S infopanel-bin

Any other distro: extract infopanel-0.3.8-linux-x64.tar.gz and run ./install.sh.

Upgrading from 0.3.1 or later needs no extra steps. The deb, rpm and AUR packages now re-apply the udev rules to Valkyrie and MS9132 screens that are already plugged in, so those don't need a replug after installing.

New: Valkyrie V360 LCD (320×240)

The V360 gets its own Valkyrie section on the Devices page, with its own streaming switch, brightness, rotation, frame rate and hotkeys. It uses the same MacroSilicon MS9132 bridge (345f:9132) as the VMAX 4.6" and the Jonsbo DS339, so Scan reads the panel's EDID to tell the three apart. Earlier releases added a V360 as a VMAX 4.6" (or as a DS339 when the EDID was unreadable). The next Scan replaces that entry and keeps its profile, brightness, rotation and hotkeys.

Tested on a V360 under Fedora 44: discovery, colors, orientation, live brightness and rotation changes, and stopping and restarting the panel. Suspend/resume hasn't been tested on it yet.

New: Valkyrie MC360 LCD (640×480), experimental

The MC360 (374a:a021, Vk-Copl-08) has its own bulk USB driver, written from published protocol research. Nobody has run it on a real MC360 yet, and the device row says so. If you have one, please try it and open an issue with what you see.

Changed: VMAX 4.6" detection

The VMAX driver no longer starts up a screen whose EDID says it's a V360 or a DS339. Before, with two of these screens plugged in, the VMAX setup could reach the wrong one. A VMAX with an unreadable EDID is now skipped by Scan, which asks you to check USB/HID permissions.

Thanks to @EsiksonX for the V360 and MC360 support and for testing it on real hardware (#13). The V360 setup sequence is adapted from LCD Fusion by itsmylife44 (MIT).

Full Changelog: v0.3.7...v0.3.8

Contributors

EsiksonX
Assets 5
Loading