https://bugzilla.novell.com/show_bug.cgi?id=304995#c6
Petr Cerny changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mskibbe@novell.com
Status|NEW |NEEDINFO
Info Provider| |cstender@novell.com
--- Comment #6 from Petr Cerny 2007-09-06 06:32:25 MST ---
AFAIU (according to DirectFB and Splashy documantation) the first mode found in
/etc/fb.modes is used by default; Holger: please correct me if I'm wrong here,
Christopher: please attach your /etc/fb.modes which triggered the bug.
Therefore
1) we need fb.modes;
2) listing all possible modes won't help;
Moreover:
3) putting mode incompatible with your hw at the beginning will break
displaying completely - on some analogue displays you would get complaints
about incompatible display frequencies, not sure about digital output like DVI;
also note that the first (i.e. default) mode in distribution fb.modes is the
legacy 640x480x8bits@60Hz.
What I regard as safe is a simple script which would be uses to change
/etc/fb.modes according to the current hardware configuration. Yet this still
might break on hardware change (like on changing display or attaching an
external one to a laptop, not mentioning changing the graphical card).
Adding DirectFB maintainer mskibbe to cc as changing /etc/fb.modes would affect
it in the first place: any comments Michael? Is there some "correct mode"
detection in DirectFB which we could rely on?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.