From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 Description of problem: When starting XFree86 (up to 4.1.0-6) after an "XFree86 -configure", X fails to detect the panel size and quits. Analog to bug report #55675 Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. XFree86 -configure 2. XFree86 -xf86config /xyz.file Actual Results: X crashes. Expected Results: X should start :) Additional info: IBM A30p, ATI Radeon Mobility M6 LY, LCD panel 1600x1200, XFree86-4.1.0-6. Tried with different XF86Config's (see attachments) : - resulting from step 1. (XFree86 -configure) - example file from LinuxCare for IBM A30 (1400x1050), with and without 'Option "UseFBDev" "True" ' - explicitly stating 'Option "PanelWidth"/"PanelHeigth" '
Created attachment 38026 [details] XF86Config.new
Created attachment 38027 [details] XF86Config.new log
Created attachment 38028 [details] XF86Config LinuxCare ( http://www.linuxcare.com/labs/certs/ibm/thinkpad/a30/rh71-config.epl )
Created attachment 38029 [details] XF86Config LinuxCare log
Created attachment 38030 [details] lspci report
"Solved" by compiling and installing latest CVS XFree86 (4.1.99.2, 21/11/2001). No hardware acceleration due to bug #56526 (agpgart oops) Related question to Mr. Harris : Examining the RH XFree86.spec-file from XFree86-4.1.0-6.src.rpm : does it suffice to remove the patch-files and references, and replace the XFree86-...-tar.bz2 with the CVS tar.bz2, in order to create a CVS-based RPM ?
No, removing the patches, and whatnot is not enough to build CVS in RPM format. Each release of XFree86 is sufficiently changed that it requires a fair bit of engineering to twist into RPM format. I have been working on XFree86 CVS in RPM format now for about 3 weeks. It mostly builds, but there are some issues that still need to be resolved. Then I need to figure out what all new fonts there are, and straighten out the whole font mess.. and then add new libs, X extensions, and executables, etc to the files section. Once I have packages that build correctly (or appear to at least) and have all the new files included and intact, I'll test with rpmlint and fixup, then do installation and upgrade tests. I expect to have preliminary packages ready within 2-3 weeks, but it may be sooner than that, or later than that depending on what all I need to fix. One thing that is horribly broken is Glide3. I am likely going to separate Glide3 back out into separate RPM package and deprecate it, as it wont build with new libtool/autoconf, gcc3.
*** This bug has been marked as a duplicate of 55675 ***