Created attachment 315975 [details] Xorg.0.log when 'nomodeset' was NOT used Description of problem: A new "EE" complaint showed up in /var/log/Xorg.0.log: (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to software rendering Expected? This error is absent if 'nomodeset' is used as a kernel argument (although then instead I see 31 lines which say: "(EE) RADEON(0): Unknown EDID version 0"). It is difficult to say how "new" is the error in question as with this version of a driver and 2.6.27-0.312.rc5.git7.fc10 kernel it is the first time for a while when I am getting anything but a black screen (unless possibly when 'nomodeset' is present). 'nomodeset' apparently gives a better deal anyway. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.9.0-9.fc10.x86_64
Created attachment 315976 [details] Xorg.0.log after a boot with 'nomodeset'
Presumably updates to assorted mesa-7.2-0.1.fc10 packages killed that error. With that, and 2.6.27-0.314.rc5.git9.fc10 kernel, I see now in log (II) AIGLX: enabled GLX_MESA_copy_sub_buffer (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control (II) AIGLX: Loaded and initialized /usr/lib64/dri/r300_dri.so The module above is from mesa-dri-drivers-7.2-0.1.fc10.x86_64.