Hi, if there are issues with sysimage-v3, could somebody please either notify me here in the forum, or drop me a mail firstname.lastname@example.org or file an issue and @-mention me at source.mnt.re? It’s nice if problems get discovered but we should fix them at the source so that others can automatically benefit from the found solution without having to first search in the forum and then manually fix things.
When trying to replicate your issue, I actually ran into another issue:
This looks like a mesa bug and I don’t know why the desktop doesn’t start at all and I only get graphics glitches. Once I killed it and tried running reform-windowmanager again I got to replicate your issue but I don’t think it’s a mesa issue because moving the mouse actually enters some text into the terminal. Can you confirm that observation?
Maybe start a new thread about this issue because I’m quite certain that this is not sysimage-v3 specific but if you had updated your kernel and mesa in v2 to their current versions you would run into the exact same issue.
Finally got to install sysimage-v3 today, had to fiddle around with crypttab to get my LUKS+LVM on NVMe setup working but otherwise everything went smoothly.
Everything seems to be working fine, except for the HDMI output. My monitor that worked with v2 now doesn’t, even if I put imx8mq-mnt-reform2-hdmi.dtb into /etc/flash-kernel/dtbs/ (and update-initramfs)
Here’s the dmesg log when plugging the monitor in:
[ 3151.570988] cdns-hdmi-core: HDMI Cable Plug Out
[ 3151.839441] cdns-mhdp-hdmi: get block edid failed: -22
[ 3151.845038] cdns-hdmi-core: Invalid edid
[ 3151.850015] imx-dcss 32e00000.display-controller: [drm] Cannot find any crtc or sizes
[ 3151.854440] cdns-mhdp-hdmi: get block edid failed: -22
[ 3151.863419] cdns-hdmi-core: Invalid edid
[ 3151.873923] cdns-mhdp-hdmi: get block edid failed: -22
[ 3151.879509] cdns-hdmi-core: Invalid edid
[ 3151.883663] imx-dcss 32e00000.display-controller: [drm] Cannot find any crtc or sizes
[ 3151.891663] cdns-hdmi-core: HDMI Cable Plug In
EDIT: weirdly enough, the first kernel messages at boot appear on the HDMI output and then it shuts off and the rest of the logs appear on the laptop display.
Though the plan of the person handling the upstream of our Linux kernel patches also plans to do away with having two different dtbs and wants to support dual display support with a single dtb in the future once they get around doing the necessary work.
I’m seeing the following error with the latest apt upgrade…not sure if it’s just a me thing or not.
Setting up initramfs-tools (0.141) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.141) ...
update-initramfs: Generating /boot/initrd.img-5.18.0-reform2-arm64
W: No zstd in /usr/bin:/sbin:/bin, using gzip
E: /usr/share/initramfs-tools/hooks/lvm2 failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.18.0-reform2-arm64
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subproc
ess returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
Seems https (443) is down for mntre.com.
“HTTPS version of 220.127.116.11 is not available”
E: Failed to fetch https://mntre.com/reform-debian-repo/pool/main/l/linux/linux-image-5.19.0-reform2-arm64_5.19.6-1%2breform1_arm64.deb 404 Not Found [IP: 18.104.22.168 443]
E: Failed to fetch https://mntre.com/reform-debian-repo/pool/main/l/linux/linux-image-arm64_5.19.6-1%2breform1_arm64.deb 404 Not Found [IP: 22.214.171.124 443]
The server is fine, we deleted this package yesterday because the display wouldn’t come up in 5.19 and we didn’t want people to run into trouble. We identified a fix today and will update shortly. Sorry for the inconvenience!
Ran into this by skipping the MNT repo and still obtaining a kernel update via Debian.
If you’ve end up with a system that is not displaying anything, copy boot.scr.bak to boot.scr on the boot partition to revert to attempting to boot the old kernel and try to boot your Reform again.