Issues with MMM-Screen-Powersave-Notification

Rags

@sdetweil Thanks for tryin for a solution. The mirror was oriented in portrait mode, and now the display is landscape and that too low resolution. All my modules displays are messed up and it is a very sorry sight. I had to switch off the mirror… In the last 5 years this is the first time i have had to go through such a major issue.
Is there a way to set the resolution in the config.js ? But i guess the OS and hardware will prevent any software configuration settings.
Can you suggest any other resolution?
Thanks

sdetweil

@Rags is there a configuration option from the desktop menu?
I haven’t tested portrait myself in years and years, I know others have, so I defer all advice to them

schlomm

@Rags Allow me to go a few steps back - maybe we can find a solution for your problem. In my opinion the problem is not caused by any MagicMirror specific issue, but it’s based on your overall setup.

0.) Reflash your image. Since I do not have any experiences with Trixie, I would suggest to use Bookworm. Ensure that you are using the the image with Desktop Envionment - here you can interactively change the resolution and orientation.
1.) Update the system to latest version using the following command:

apt update && apt full-upgrade -y && apt autoremove -y && apt clean

2.) Restart your system
3.) Set the resolution and orientation using the System Preferences
4.) Use @sdetweil script for installing the MagicMirror. The script can be found here: https://github.com/sdetweil/MagicMirror_scripts?tab=readme-ov-file#install-magicmirror
5.) Install your module (MMM-Screen-Powersave-Notification) and configure it for using the wlr-randr_control. wlr is used by default in Bookworm.

mumblebaj

@Rags Hi. I am running Trixie since the beginning of the year. I wrote a post about setting up the screen stuff and monitor on and monitor off. See my post. When you turn on the monitor with a script you can set the resolution,

https://forum.magicmirror.builders/topic/19116/having-trouble-with-screen-on-and-off-here-are-some-tips-that-could-help?_=1761576771063

Rags

@schlomm ## I just thoght of uploading the Summary of Attempts - All Failed. It is really getting frustrating. My Monitor was working perfectly well the desired rotation and resolution 1080x1960, and now is stuck at 1024x768.

config.txt modifications:**

Custom hdmi_timings for 1920x1080
Various hdmi_mode settings (82, 87)
hdmi_ignore_edid=0xa5000080
Different boost levels and drive settings
Result: Monitor only shows up to 1024x768 max

cmdline.txt kernel parameters:**

video=HDMI-A-1:1920x1080@60D
Various video= parameter combinations
Result: No effect on available resolutions

Custom EDID firmware:**

Created multiple EDID files (256 bytes, 268 bytes, 285 bytes)
Placed in /lib/firmware/edid/ and /boot/firmware/edid/
Used drm.edid_firmware=HDMI-A-1:edid/1920x1080.bin
Rebuilt initramfs to include EDID early
Result: Kernel loads file but rejects it as “Invalid firmware EDID”

Wayland/X11 rotation scripts:**

wlr-randr (Wayland) - can’t set non-existent 1920x1080 mode
xrandr (X11) - output name issues
Result: Can only work with available modes (max 1024x768)

Core Problem:

Acer HA270 monitor provides NO EDID data** to the Pi
Bookworm OS + Labwc Wayland compositor won’t accept forced resolutions
Same monitor worked with Pi 3B + Bullseye (older firmware stack)
Raspberry Pi detects only: 1024x768, 800x600, 848x480, 640x480

Current Status:

Stuck at 1024x768 rotated = 768x1024 instead of desired 1080x1920. Wonder if we the Rpi OS team is aware f this issue.