After installing SUSE on virtually every build of Parallels, I find that it no longer installs under Build 3150. It fails in the last phase, Hardware Configuration. Symptoms are an hour-glass cursor from which it never recovers. Joe
Title of post should be "INSTALLATION of SuSE 10.2 broken..." I have 10.2 working fine under RC3 (and worked on RC2), but I think I installed it on the VM using an older build. I havent tried to install on a new VM using the latest Parallels RC build.
Same problem Same problem, impossible to finish the installation on the current beta build. When I use an old imge installed with an other version, Suse start but freeze during 5min at boot and peripherical are not recognize : no sound, no network ...
Which computer system are you using? The problem is on my Mac Pro and I'm beginning to suspect that it's related to the Nvidia firmware update that Apple pushed out. Are you using a Mac Pro with an Nvidia or an ATI card? TIA, Joe
I'm not using any devices other than the ones created by default when I created the VM. So, do you mean remove all those default devices except HD and CD? Joe
OK. I removed all the default devices except HD and CD but the behavior is the same. There are actually 3 things I noticed in my installation attempts: 1. The message "graphic can not be initialized" appears when the VM boots from the installer. 2. Start up pauses for about 10 minutes while the VM attempts to load the universal CD driver. 3. The installer stops responding on the last graphical install page "Hardware Configuration" I should point out that I'm now on Build 3188 but the behavior has been the same since Build 3170. Joe
I have managed to do a fresh install of SuSE 10.2 with the latest parallels (I did it because my previous one seemed broken) There was an agpgart module problem. (intel_apg) Something in the last few parallels RC's and the final realease plays badly with intel_apg I fixed it by adding a line blacklist intel-agp to /etc/modprobe.d/blacklist I was able to do this because sometimes resetting the vm allowed the suse boot process to get to a point where I could fix this (there was a kernel "oops" which messed up some things in the boot process.) If this is your problem you can fix it. In the end, I repared this problem on my original suse 10.2 install, so i havent been using the new vm created with the latest parallels, but it works too.
duncan_h Intel AGP is the common problem in Parallels. Due to physical limitations of intel i815 chipset it can not use more than 512 Mb of memory. And some linux guys wrote code based on that. /me went to opensuse webpage to find DVD image...
I resolved my installation issue by reducing the VM's RAM allocation to 512 MB. Previously, it was 1024 MB. Thanks all. Joe
So, for the record, the full fix for SuSE 10.2 installation on Parallels is (1) install SuSE 10.2 on a Parallels VM with less than 512MB memory (2) after sucessful installation, edit /etc/modules.d/blacklist to add a line blacklist intel_agp (3) shut down the Parallels VM, and edit its memory settings to use more than 512Mb memory, if that is what is wanted.