Thank you for your donation!


Problem: HDMI port resolution
#1
Hi moOde fans,
 Angry
Reply
#2
There is no fixed resolution for the HDMI port. An attempt to dynamically determine the resolution of HDMI attached monitor is made by some code in the X11 display server startup script /home/pi/.xinitrc. This resolution is then used to set the Window size for Chrome Browser when its launched.

Some monitors might not report the correct resolution. YMMV. In this case I think there are some manual settings that can be made in /boot/config.txt but I have no idea what they might be.

Here is the .xinitrc script

Code:
# Turn off display power management
xset -dpms
# Screensaver timeout in secs or 'off' for no timeout
xset s 600

# launch chrome browser
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
chromium-browser --kiosk --touch-events --disable-touch-drag-drop \
--enable-touchview --enable-pinch --window-size=$SCREENSIZE --window-position=0,0 \
--disable-session-crashed-bubble --disable-infobars --no-first-run --app=http://localhost/

And here is what is returned for SCREENSIZE after I connect to my 24" 1920x1200 ASUS panel and then reboot.

Code:
pi@rp3:~ $ fbset -s | awk '$1 == "geometry" { print $2","$3 }'
1920,1200

-Tim
Reply
#3
Hi moOde fans,
 Angry
Reply
#4
Hi moOde fans,
 Angry
Reply
#5
(04-16-2018, 05:52 PM)JST1963 Wrote: Tim,
At the office today I tried lots of things, also other stuff I found on the internet (if my boss only knew I was playing with moOde and an RPi....)
Nothing really helped. But then I clicked on some button of the monitor itself you change some parameter (input and so on) and that button didn't react. In fact, none of the buttons responded to a push, only the on/off button. So I guess the monitor is f**k*d u* (read: broken).
So, let me try again on Wednesday with another (old) 1680by1050monitor. I'll keep you informed.

Johan

Hi, Johan.

I looked up the fbset command used in the .xinitrc script. The man page says 
Quote:fbset  uses  an own video mode database located in /etc/fb.modes. An unlimited number of video modes can be defined in this database. For further information see fb.modes(5).

Your 1680x1050 resolution isn't defined in fb.modes as distributed but you could define it yourself.

I'm presupposing that raspbian uses some variation of VESA EDID via HDMI to detect the monitor's capabilities and then compares that with the fb.modes data.

Regards,
Kent
Reply
#6
1680x1050 in configs here Kent.. #57 thru #59 ;-).....https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Setup configs here...https://www.raspberrypi.org/documentation/configuration/config-txt/README.md


maybe set manually in /boot/config.txt

hdmi_drive=1
# Set monitor mode
hdmi_group=2
# Set monitor resolution to 1680x1050 60Hz
hdmi_mode=58

Reply
#7
Hi moOde fans,
 Angry
Reply
#8
(04-17-2018, 07:39 PM)DRONE7 Wrote: 1680x1050 in configs here Kent..  #57 thru #59 ;-).....https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Setup configs here...https://www.raspberrypi.org/documentation/configuration/config-txt/README.md


maybe set manually in /boot/config.txt

hdmi_drive=1
# Set monitor mode
hdmi_group=2
# Set monitor resolution to 1680x1050 60Hz
hdmi_mode=58
Thanks for that, @DRONE7. Curious, though, that the raspbian config.txt and the /etc/fb.modes file in raspbian aren't better aligned in terms of resolution choices.
Regards,
Kent
Reply


Forum Jump: