04-17-2018, 02:35 PM
(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
