https://bugzilla.novell.com/show_bug.cgi?id=221217 ------- Comment #12 from ms@novell.com 2006-11-20 08:47 MST ------- I think one issue we all agree is that it is impossible to migrate an existing binary driver based config to a comparable opensource variant. This means converting nvidia based configurations to nv or fglrx based to radeon would create more problems than solutions According to this the only way I see is the one you suggested already. Turning into a new "safe" configuration. This can be easily done by - calling "sax2 -r -a" at a specific stage in YaST. - or relink the xorg.conf.install file (fbdev) to xorg.conf But I doubt this is what customers want. Even if the original file is available as a .saxsave people will argue why we "remove" their xorg.conf. I'm quite unsure if any action concerning the file would be correct. I think a useful unmistakable message while updating should be enough. Installing the binary driver requires some user interaction so the user is used to that if he wants the binary driver. The only thing which needs to be clear to the user is that he needs to take care for the driver in the same way as before as soon as the update finished. Additionally the quality of the binary drivers is not the best which means starting X with another driver could influence the binary driver in such a bad way that you have to deal with several annoying problems (no console, machine crashed, etc...) Referring to that I think runlevel 3 is the best starting point to update to a binary driver. But this is only a personal note -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.