Description of problem: The upgrade process should know about when a user needs to change something to keep their hardware working. e.g. X Servers Version-Release number of selected component (if applicable): f10 version of preupgrade How reproducible: always Steps to Reproduce: 1. upgrade from f10 to f11-rawhide Actual results: system broken (X fails to start upon final reboot) Expected results: system still works! (X starts with correct server) Additional info: my hardware (radeon mobility x1600) apparently went from being supported by 'radeon' to being supported by 'radeonhd'. I know how to read Xorg.0.log and edit xorg.conf but most users would just say the upgrade broke their system. Perhaps an assumption in the first stages could be sanity tested against later stages where autodetection is available.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The hardware is supposed to still be supported by "radeon", the fact that it doesn't work is a bug. Switching to "radeonhd" is not the correct fix.
We never use radeonhd without users explicit request. There must be something weird somewhere. Please attach your X server config file (/etc/X11/xorg.conf, if available), /var/log/dmesg, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
*** This bug has been marked as a duplicate of bug 468773 ***