Quoting Remco Poelstra ([EMAIL PROTECTED]):
> On 2002.02.10 19:14 Sven Neumann wrote:
> ><snap>
> >there's a stupid bug in DFBPoint that causes the error messages not
> >to be printed. That bug is fixed in CVS. We'll do a new release with
> >the DirectFB-0.9.9 release.
> >
> >I'd guess that DFBPoint is unable to find a font or an image that is
> >referred to in the XML file.
> >
> 
> Thanks for the reply.
> I installed DFBSee to check whether it is DirectFB or DFBPoint which 
> causes the error. Probably it's indeed DFBPoint, since with DFBSee I get 
> no errors from DirectFB. The only problem is that my monitor says that 
> 74Khz/74Hz is out of range. How can I see to what mode DirectFB tries to 
> switch and how can I add a correct mode line to fb.modes?

DirectFB uses the first suitable mode in /etc/fb.modes (everything with
more than 8bit). The depth is last number in the "geometry" line.

You can move the desired mode to the top.
You can also do "fbset >> /etc/fb.modes" and move the appended mode to the top.
You should remove the "argb" line after that, because fbset doesn't like
it though it spit it out.

-- 
Best regards,
  Denis Oliver Kropp

.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/                 |
"------------------------------------------"

           convergence integrated media GmbH


-- 
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with 
"unsubscribe directfb-users" as subject.

Reply via email to