I downloaded the latest version of openSUSE 11.3 LiveKDE from the web yesterday and I wanted to boot it in order to see what’s new.
On my workstation a (lenovo ThinkCenter) it worked ok but on the MacBook Pro - Intel it tries to boot and I think when it came to enter the X mode failed. The screen freezes with a black screen and a lot of thin pink lines.
Does anybody tried this version on MAC? Is it possible that for the MAC should be a different version other then the regular PC version?
At boot time there was a line that failed it was something like:
Starting Virtual Box addition fail
Is there a list with the new features introduced in 11.3?
There is software that Mac and Windows and Linux users run on their system (called this a host system), which is typically Virtual Box or Vmware software, that lets one load another “client” operating system in a “virual session” under one’s Host operating system.
Back to your Mac problem. I assume this is an Intel and not a PPC based Mac. Did you try booting with safe settings or any other options ?
Actually Safe Settings and a normal boot are the same, except for a safe settings boot there are a BUNCH of “boot codes” that are inserted, to change the way in which the kernel boots, and change which other applications are loaded or not loaded upon boot.
If you look in the “options” line of the initial boot/splash menu (where you select the “safe settings” ) you will see some of the various boot codes.
After an openSUSE is installed, one will have options for a Normal boot or a Fail Safe boot, where a Fail Safe boot will show a bunch of additional options in the “options” line. BUT not all options are shown when booting. Instead there is a file known as the /boot/grub/menu.lst file, and in that file one can see additional options that are applied for a normal boot and possibly for a fail safe boot.
Typically, of the many boot codes being applied there is often only one boot code in the list that allows the boot to succeed. Most of the Safe Settings boot codes are not needed. The “trick” is to narrow it down and determine exactly which of the boot codes is the one that allows this to work. The way to do that is to reboot many times, each time removing one more boot code. Eventually the PC will refuse to boot, and one will learn which boot code appears to be the code that allows the boot to take place. Make note of that boot code.
Then reboot, and type that boot code into the options line for a normal boot, and see if the boot takes place successfully. If it does, then one has verified that is the correct boot code that allows one to boot.
Then at that time, one needs to research WHY does that specific boot code allow the PC to boot, where without that boot code the boot fails.