https://bugzilla.novell.com/show_bug.cgi?id=215440 ms@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Comment #7 from ms@novell.com 2006-11-06 06:20 MST ------- yes the vmware based X server configuration is a fixed 800x600 configuration setup. Using the vmware driver requires us to specify which resolution we want. For the yast based installation this is 800x600. Unfortunately the X11 fbdev driver which automatically used the current kernel framebuffer specification doesn't work within VMware but the kernel framebuffer support works. So what happens here is the following: 1) within isolinux you setup another resolution than 800x600 for the kernel framebuffer which caused the vmware window to expand to this resolution 2) when the X-Server starts which is used for YaST and the installation the vmware driver must be used not fbdev and the fixed configuration leads to a 800x600 X-Server which shrinks the vmware window down 3) each time you change from X to the fbdev based console the window gets resized The behavior here is intentional because we have to specify the resolution we want to use for the installation process. To get rid of this we need to ask the current framebuffer for its resolution and adapt it into the X11 config file. But I strongly recommend not to that because this will create the risc of a failing X-server. Additionally I see no reason why it is important to have the same resolution for X and the console during installation. So I still would prefer to have safe settings here According to this it is a "works for me" -- 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.