On Wednesday 23 June 2004 23:57, Carl Pecinovsky wrote:

There is only one console on the iSeries platform.

I'm unfamiliar with that platform. ;)

So, I took option 1, option 4, option 9==> "Enable or Disable SSH Mode". And I was prompted for an SSH password during the next install attempt, however, now when I try to ssh into the kernel, I get "Connection refused". I can ping it fine.

On the ix86 platform, I can pass boot parameters to the kernel, like e.g.: UseSSH=1 SSHPassword=abc The target system prompts when it is ready to receive ssh logins, and instructs what to do (ssh -X root@x.x.x.x, run yast). Perhaps you need to specify the SSHPassword on the target system? Cheers, Leen

I was able to send individual commands via SSH even though I couldn't log in. But even better, I found there is this wonderful kernel option 'start_shell' that pops me into a shell right away and pops me back to it when an error is encountered. I had a typo in my control file for the filesystem (used /dev/iseries/vda1 where it should have been /dev/iseries/vda). The /var/log/YaST2/y2log produced these messages: 2004-06-28 15:58:55 <1> linux(472) [YCP] AutoinstStorage.ycp:368 Creating partition plans for /dev/iseries/vda1 2004-06-28 15:58:55 <3> linux(472) [Interpreter] Report.ycp:379 Nil can be compared only for equality and non-equality 2004-06-28 15:58:55 <3> linux(472) [Interpreter] Report.ycp:379 if condition is nil. 2004-06-28 15:58:55 <3> linux(472) [YCP] Report.ycp:391 The device configured in the control file does notexist on this system. 2004-06-28 15:58:55 <3> linux(472) [Interpreter] Report.ycp:379 Nil can be compared only for equality and non-equality 2004-06-28 15:58:55 <3> linux(472) [Interpreter] Report.ycp:379 if condition is nil. 2004-06-28 15:58:55 <3> linux(472) [YCP] Report.ycp:391 Error while configuring partitions.Try again. 2004-06-28 15:58:55 <3> linux(472) [YCP] clients/inst_autosetup.ycp:126 Aborting... 2004-06-28 15:58:55 <1> linux(472) [Interpreter] bootloader/routines/autoinstall.ycp:177 Called YaST client returned: `abort However, after fixing the problem, autoyast is now just looping on the install. After installing the rpms, it restarts the system to do post-install stuff, but instead of recognizing that it already completed the first part of the install before, it proceeds to show the sles beta warning message for 10 seconds and then continues with the install all over again. Any ideas? -Carl Try to change the values in <report>. I guess you have disabled showing the messages somehow. Another option is to have the logs go to the network using syslog, just add "LogHost=<ip address of log server>" and watch the logs on a remote server. Anas Carl Pecinovsky wrote:

This is probably a newbie question, but the scenario is that I'm trying to install a ppc LPAR partition on iSeries with SLES9 (rc2). I pass the install kernel parms for autoyast, install, and networking. The install proceeds to read the autoyast control file, do some more setup which flies by, and then pops the text installer out to the root "Main menu". No error condition was given -- it just popped out and the same thing happens if I repeat the process by choosing option 4 to start system installation. How do I look at the install log at this point? I don't know how to exit the main menu and get to the ramdisk, etc. Thanks.

Carl Pecinovsky Dept X8X: eServer Middleware Enablement, 015-3/H106 "It is never safe to look into the future with eyes of fear." --E.H Harriman

-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com