Summary: | xfree86 error on startup (ScreenInit failure) with Creator3D,series 1 (FFB) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ferris McCormick (RETIRED) <fmccor> |
Component: | Current packages | Assignee: | Sparc Porters <sparc> |
Status: | VERIFIED FIXED | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | Sparc | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Fix improper test for failure in ScreenInit (sunffb) and trace Screen setup |
Description
Ferris McCormick (RETIRED)
2003-02-10 14:58:10 UTC
Created attachment 8131 [details, diff]
Fix improper test for failure in ScreenInit (sunffb) and trace Screen setup
This seems to have fixed the problem Weeve was seeing, and it provides a little
diagnostic information at the start of ScreenInit to help with other failures
of
this sort (if they are not the same failure.)
To respond to myself: Per note from Mike Harris (redhat/xfree86), this should be getting an official fix from xfree at some point. ------------------------------------------------------ I noticed in the CHANGELOG that your fix is committed to CVS now: 866. The sunffb driver was treating a function with a void return value as if it had a Bool return value. This causes the driver to fail in some cases (#A.1588, Ferris McCormick). ------------------------------------------------------- I am using a Ultra60 with a Creator3D card. After configuring X, the X Server did not start. The error message was the following: ========== Fatal server error: AddScreen/ScreenInit failed for driver 0 =========== After applying the patch, X came up fine. Stefan Brenner closing bug sorry, my mistake ;( This is fixed in xfree-4.3.0-r2 by changing FFBDbePreInit in ffb_dbe.c to read thus: ------------------------- extern void DbeRegisterFunction(ScreenPtr pScreen, Bool (*funct)(ScreenPtr, DbeScreenPrivPtr)); Bool FFBDbePreInit(ScreenPtr pScreen) { DbeRegisterFunction(pScreen, FFBDbeInit); return TRUE; } ---------------------------- I do not know if this is gentoo-only, or a general fix from the Xfree developers. I believe the latter, since they indicated that they had applied this fix. In any event, I think the proper resolution is Closed/fixed with release xfree-4.3.0-r2 (or whenever the fix first appeared). as per Ferris McCormick's comment, i'm closing this bug Closing |