[opensuse-ppc] Unable to install Open Suse Alpha 3 ppc on JS20
This appears that it would be something that would effect all PPC systems trying to install any of the Open Suse Alpha releases. Once you are at the part in the installer where you do the partitioning of the disk, set what sotware you want to install, and what not. Once you want to progress in the install you are prompted with a message saying there is an Error that neededs to be resolved. This is using the ncurses installer as I have to install via a serial port. The problem is there are no errors anywhere on the screen for you to fix. So when back through every option redid some, and even set some to the predefined defaults to attempt to get past this error .. no luck. Currently I am totally unable to install it on my JS20 blade .... anybody have any ideas? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
On Thu, Apr 19, Jerone Young wrote:
anybody have any ideas?
The error is eventually in the Expert tab. YaST used to switch to that tab if there was an error. Use 'ESC e', or whatever the highlighted char is, to switch the tab. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
I have the exact error that I am getting: Error The proposal contains an error that must be resolved before continuing. On Thu, 2007-04-19 at 14:55 -0500, Jerone Young wrote:
This appears that it would be something that would effect all PPC systems trying to install any of the Open Suse Alpha releases. Once you are at the part in the installer where you do the partitioning of the disk, set what sotware you want to install, and what not. Once you want to progress in the install you are prompted with a message saying there is an Error that neededs to be resolved.
This is using the ncurses installer as I have to install via a serial port.
The problem is there are no errors anywhere on the screen for you to fix. So when back through every option redid some, and even set some to the predefined defaults to attempt to get past this error .. no luck.
Currently I am totally unable to install it on my JS20 blade .... anybody have any ideas?
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
Oh I already did that (forgot to mention).. you still don't see any error what so ever. Even changing and playing will every option. On Thu, 2007-04-19 at 21:58 +0200, Olaf Hering wrote:
On Thu, Apr 19, Jerone Young wrote:
anybody have any ideas?
The error is eventually in the Expert tab. YaST used to switch to that tab if there was an error. Use 'ESC e', or whatever the highlighted char is, to switch the tab.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
On Thu, Apr 19, Jerone Young wrote:
I have the exact error that I am getting:
If you can reproduce it, better open a bug report and attach the yast2 logs. A default installation worked for me without errors. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
On Mon, 2007-04-23 at 12:58 +0200, Olaf Hering wrote:
On Thu, Apr 19, Jerone Young wrote:
I have the exact error that I am getting:
If you can reproduce it, better open a bug report and attach the yast2 logs. A default installation worked for me without errors.
Interesting. Which installer are you using ? The ncursers or qt (GUI) installer. I think this may play a key roll here. Since on IBM Blades for JS2X blades you only have access via serial console. I will try using "useVNC" and see if I can get the GUI installer to work. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
Ok I found the problem, and the problem isn't really isn't supported (nor was it ever stated). So while if I have my JS20 under SLOF firmware I get this error while trying to install. But it DOES work fine when under open firmware. Thanks! Now the question is if you are connected only via serial console or even vnc for that matter, how do yu get to the yast2 logs? On Mon, 2007-04-23 at 12:58 +0200, Olaf Hering wrote:
On Thu, Apr 19, Jerone Young wrote:
I have the exact error that I am getting:
If you can reproduce it, better open a bug report and attach the yast2 logs. A default installation worked for me without errors.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
On Mon, Apr 23, Jerone Young wrote:
Ok I found the problem, and the problem isn't really isn't supported (nor was it ever stated). So while if I have my JS20 under SLOF firmware I get this error while trying to install. But it DOES work fine when under open firmware. Thanks!
Now I see it too with SLOF. The bootloader config does not find a valid boot partition for some reason. Its not clear why this happens. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
Have you been able to resolve this issue? I have no idea how to debug yast through a serial or vnc connection (can't get to a virtual term for messages and logs). Should I file a bugzilla bug for this? On Mon, 2007-04-23 at 20:34 +0200, Olaf Hering wrote:
On Mon, Apr 23, Jerone Young wrote:
Ok I found the problem, and the problem isn't really isn't supported (nor was it ever stated). So while if I have my JS20 under SLOF firmware I get this error while trying to install. But it DOES work fine when under open firmware. Thanks!
Now I see it too with SLOF. The bootloader config does not find a valid boot partition for some reason. Its not clear why this happens. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
On Mon, May 14, Jerone Young wrote:
Have you been able to resolve this issue? I have no idea how to debug yast through a serial or vnc connection (can't get to a virtual term for messages and logs).
An /sbin/lsprop /proc/device-tree will show no 'chrp' in "device_type", but something else. yast relies on this info. There is already a bug open for that. For the time being, select 'install no bootloader'. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-ppc+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ppc+help@opensuse.org
participants (2)
-
Jerone Young -
Olaf Hering