Same here. IMHO this is a duplicate of #148211

please try to switch to a console to get some more information, like SaX.log and compare to 148211.

If it's the same please close as duplicate to this one.

I don't think so, because 148211 is about SAX.

James: Is it possible to skip the configuration? The system is just idle and not stalled? Please attach the output of `hwinfo' after changing to a console within the installation system (Alt+F2). If hwinfo does not work, this might be the error. Please also attach the YaST logfiles.

Created attachment 66508 [details]
y2log during freeze

Created attachment 66509 [details]
SaX2.log during freeze

Created attachment 66510 [details]
/var/log/messages during freeze

While the screen is black a process 'sysp' is running which is also mentioned at the end of /var/log/messages. After the OutOfMemory magic happened the system continues to boot into runlevel 5.

hwinfo runs without any problems.

Some story with beta4. On the first console you can read
 Use of unitialized value in subroutine entry at
   /usr/share/YaST2/modules/XLib.pm line 437

Created attachment 69166 [details]
y2log

I forgot to mention: I still get the freeze in beta4 but not the OutOfMemory thing. But anyhow, it's still not possible to install beta4 (minimal graphical install) in VmWare.

Marcus, check the last attached log, there are many errors in the X11 proposal, which returns nil as "preformated_proposal" in the return map, and it makes the proposal broken...

Anyway, I made the generic proposal routines resitstent to this problem...

> I have a strange problem when installing beta4 into VMware 4.5.2:
> CD1 and CD2 are installed without problems, but CD3 is not recognized
> - YaST keeps asking for it.
> I use the ISOs and connect them to /dev/hdc in VMware..


I had the same problem except that I am using the latest Vmware v5.5
(VMware-workstation-5.5.1-19175). 

The install process blocked when I gave it the 3rd CD. After hiting
ENTER a couple of times, I finally chose "Ignore" and voila, I had the
same problem for the 4th CD. I chose "Ignore" again and the install
process asked for the 5th CD. The  5th CD ran without any problems and
the installation continued up until "Hardware Configuration" page setup
where there is still a problem on the "Hardware Configuration" setup
page that is related to Sax2 configuration
process.

/*************
SaX2 log     : SaX2 version 7.1 - SVN Release: 1.49 2003/03/17
**************
SVN RELEASE  : 1019
             :
DESCRIPTION  : X11 configuration log file to collect information
             : about detection, startup and configuration.
             : There are three parts of logging:
             : ---
             : 1) INIT     ( detection, 3D )
             : 2) STARTUP  ( xorg.conf, X11 log, glxinfo )
             : 3) CONFIG   ( config actions )
             : ---
             :
VERSION      : SaX2 compiled for: [SUSE LINUX 10.0.42 (i586)]
PARAMETER    : no parameter(s) given
             :
LOG DATE     : Mon Feb 20 07:15:37 CET 2006
*************/
============================
Framebuffer Info:
----------------------------
Framebuffer is active

20-Feb 07:15:37 <I> Initializing...
20-Feb 07:15:39 <I> [ Sysp: Mouse detection data
	Mouse0    =>  Protocol   : explorerps/2
	Mouse0    =>  Device     : /dev/input/mice
	Mouse0    =>  Buttons    : 5
	Mouse0    =>  Wheel      : 1
	Mouse0    =>  Emulate    : 0
	Mouse0    =>  Name       : ImPS/2 Generic Wheel Mouse
	Mouse0    =>  VendorID   : 0x0210
	Mouse0    =>  DeviceID   : 0x0013
	Mouse0    =>  Profile    : <undefined>
	Mouse0    =>  RealDevice : /dev/input/event1
	Mouse0    =>  NutShell   : 0
]
20-Feb 07:15:40 <I> [ Sysp: Keyboard detection data
	Keyboard0 =>  XkbModel   : pc102
	Keyboard0 =>  XkbLayout  : fr
	Keyboard0 =>  Name       : AT Translated Set 2 keyboard
	Keyboard0 =>  RealDevice : /dev/input/event0
]
20-Feb 07:16:02 <I> [ Sysp: Server detection data
	Card0     =>  DomainId   : 0x0
	Card0     =>  BusId      : 0x0
	Card0     =>  SlotId     : 0x0f
	Card0     =>  FuncId     : 0x0
	Card0     =>  Vendor     : VMWare Inc
	Card0     =>  Device     : VMWARE0405
	Card0     =>  VID        : 0x15ad
	Card0     =>  DID        : 0x0405
	Card0     =>  Module     : vmware
	Card0     =>  BusType    : PCI
	Card0     =>  Detected   : 1
	Card0     =>  Flag       : DEFAULT
	Card0     =>  SUB-VID    : 0x15ad
	Card0     =>  SUB-DID    : 0x0405
	Card0     =>  DrvProfile : <undefined>
]
20-Feb 07:16:03 <I> [ Sysp: XStuff detection data
	SaX: ups lost card during probing... abort
]

sorry according to your report the installation process was broken
before the hardware configuration starts, everything could be broken in
that case... missing packages, strange environment

If you can do a clean installation up to the point of the hardware
configuration and the problem still exist feel free to reopen and provide
access to the vmware host. Otherwise hardly can do anything here.

I'm sorry

If you don't mind could you test the packages from:


   ftp://ftp.berlios.de/pub/sax/head-build/i386/suse-10.1

yesterday I found a bug which could cause the problems on vmware as
well.

Thanks

I can test after I'm back from FOSDEM

At least the error is different ;-)

SaX starts, but the detection phase (until X is started) takes several seconds (feeled: longer than usual, I didn't watch the clock ;-). Then the grey X background appears for 2 seconds and disappears again. At this time, SaX is still running and takes lots of memory and CPU - until the oom killer gets active several times. My virtual machine has configured 256 MB RAM + ~500 MB Swap which should be enough ;-)

linux:~ # rpm -qa 'sax2*'
sax2-tools-2.7-84
sax2-libsax-perl-7.1-84
sax2-ident-1.7-84
sax2-libsax-7.1-84
sax2-gui-1.7-84
sax2-7.1-84

linux:~ # sax2 -r
SaX: initializing please wait...
SaX: your current configuration will not be read in

SaX: no X-Server is running
SaX: will start own server if needed
Died at /usr/share/sax/init.pl line 620.
linux:` #

I'll attach SaX.log, dmesg output (because of oom killer) and top output.

BTW: If needed, I can offer ssh -X access to my machine where you can do some tests with VMware.

Created attachment 70180 [details]
SaX.log (with sax2-7.1-84)

Created attachment 70181 [details]
dmesg output (with sax2-7.1-84)

have a look at the "oom killer" messages...

Created attachment 70182 [details]
top output (with sax2-7.1-84)

This is the top output shortly after X exited again.

:(

Thanks for testing. yes something is broken there. It would be great
if you can give me access to the machine

Thanks

same problem in beta5 (fresh installation in VMware 4.5.2 again) - but that's not surprising because sax has the same version number there ;-)

I won't do any more experiments in this VMware installation to keep the installation fresh.

Please mail me your SSH public key and include a note when you want to login - I'd prefer to do it in the evening - the later, the better ;-)  (however, starting at 19:00 CET would be OK). I will then send you the username and other details. Maybe it's a good idea to have an IRC session open while you debug this ;-)

Well, that's finally a reason to register at dyndns.org ;-)

Reopening because preconditions from comment #13 are fulfilled now ;-)

Quoting James PEARSON's mail in opensuse-factory:
> I get an error during when install SUSE 10.1_b5 under Vmware under
> "Graphics Cards" entry on "Hardware Configuration" screen
>
> # Error Message
> "ERROR: No proposal". See screen shot at
> "http://perso.wanadoo.fr/j.pearson/SUSE-b5.1.png"

Same problem here - I guess it is a related problem, therefore I don't open a separate bugreport unless you tell me to do so.

*** Bug 152789 has been marked as a duplicate of this bug. ***

asked for ssh login...

Here is a my ssh (freshly generated) public key
vi  /home/jpearson/.ssh/id_dsa.pub
######### start #########
ssh-dss
AAAAB3NzaC1kc3MAAACBAKR2wFdZg0YEXLZSE4NEK7JargB4QncAsSK5fBX4bxgy/L96ecbrgebe49IPrH3fREfUx8PBGXd6Jgoxb3w+pDoq8cgMPFCIZTQD/xRMMAigcplsxP1CKD6UrtrMngDOo0XzvAxu0Hceyu9eIVEa3b4gT7kToNhs0OO8nWygU8J7AAAAFQCXqnPprhr9mbWG0dbyqKxc2RfnnwAAAIA1qzEqno0Lf7jGwvjEeck26OWezxPyzYjcMlYYk/BXDKOn5kA2b0fN947fFjwEbq5lb6aAxPl+7fowksIq2WskSi8Yjw8Oa+Ia9mlMlSnHHkZRHQ3b8e/v6TfvCo+AQbh+IvwA5enYo/RT9W+EBMsYumxTWSlVzHN1GC+eZVSveQAAAIA8cuxDvx+Fzm329pa6HQXtncSIGfvVJCikaYChaJHoEWJsBataQu6I84LfhiMOmbFR5tjlL4fWE7hUaBVDjiwEC7OZyOG60ov63FSjpih1Vb269thuVkVRM2QKJVIFdIVBqMwI6OCVhpvvGPEUNZMlresfUJYxyTPYoIqWNjatAA==
jpearson@bigboy
######### end #########

Hello

I was contacted by suse-beta@cboltz.de - and it is possible that we might connect up this evening (Sunday) concerning this mater. 

Note : I do not have a fixed IP. If it is still possible without a fixed IP I have no objection to granting one of you a ssh login for a look over.

If interested, please send me your public key (by email) and name propose one or two CET revendez vous times (evenings please). The earliest possible date for me will be Wednesday (March 1st) as I will be out of town Monday and Tuesday.

finally I found and fixed the bug. It works now on the test
installation I made... SuSE has a gsx server *great stuff* ;)

Does your fix also solve the problem described in Comment #23?

BTW: Where can I get updated packages to test? ;-)

I have exactly the same issue, please can I also test the updated packages?

>Marcus Schaefer 2006-02-27 04:23 MST  [reply] 
>finally I found and fixed the bug. 

I have two installations at home (smp and portable setup) - any chance of trying out the updated packages ?

*** Bug 154156 has been marked as a duplicate of this bug. ***

*** Bug 155065 has been marked as a duplicate of this bug. ***

This bug is still a problem in Beta 7 code.  Issue is the same as comment #23 above.  Still cannot configure a display when running in vmware session.  Best resolution I can get is 600x800 and that is only done by booting to init 3 and then running sax2.  Still get the error: ERROR: No proposal during install.

beta7 doesn't have the fix:

  - fixed sysp compiler flags -DXORG_LOADER (#157019)

use beta8 please