Bugzilla – Bug 104598
YaST unuseable after initial reboot (dualhead)
Last modified: 2005-08-16 08:08:44 UTC
You remember my so-called "strange" dualhead configuration? While updating to 10.0, my external monitor (arranged above the laptop display) doesn't get any signal, so YaST2 is completely invisible after the initial reboot. (See bug 104597 for the x.org issue.) Since I expect to receive the "we don't support every strange configuration" answer again :-( let me ask a simple question: Why don't you just use the xorg.conf used in the first stage of installation also for the second stage? It has always worked - and you don't have to rely on existing x.org config files which may be broken.
xorg.conf from the first stage is copied into the system for use within the second stage. So I don't understand what you are talking about except if you did an update instead of a new installation. While updating the X configuration won't be touched and therefore used within the second stage of the installation which is in my opinion the correct workflow
You guessed right - I updated from 9.3. (I don't see this as a problem, since updating from previous versions should be well-supported.) > While updating the X configuration won't be touched and therefore used within > the second stage of the installation which is in my opinion the correct > workflow Maybe you are right - but this behaviour caused problems on my system on some SUSE releases already. Unfortunately, this time it is a worst case scenario because YaST is completely invisible :-( - the other times the problems were "only" annoying (things like "YaST cut off a bit").
I can understand your point, of course it's annoying to be unable to use the same X11 configuration from the old release within the new release. Well hopefully you can understand that I cannot fix this problem because the update workflow will not be changed for the current version as well as for SLES10. The code responsible for X11 configurations isn't even called in your process so the problem is in my opinion based on the xorg update which leads to a blank screen with the same configuration working in an older release. Maybe Stefan can explain what has changed from a drivers point of view
Unfortunately I can't. I only added support for new chipsets and some bugfixes to the radeon driver for SUSE 10.0. Anyway this is sth. which should be discussed in Bug #104597. --> DUPLICATE *** This bug has been marked as a duplicate of 104597 ***