I thought of that too. I went with no swap as I intend to use a swap file
and/or eventually expanded storage for swap. That doesn't mean that yast
didn't in fact mess with stuff.
I had /dev/dasda mounted at '/' and /dev/dasdb mounted at /usr/
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 03/12/2002 11:34 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>--------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Attempting first IPL after initial SuSE install
|
>--------------------------------------------------------------------------------------------------------------|
I just remembered something about YaST, and the way it re-orders your
"dasd=" parameter when you specify a swap volume. When you IPLed the ram
disk installation system, what did your parmfile look like? Did you
specify
a swap volume during the install? If so, YaST made that swap volume
/dev/dasda, and your root file system /dev/dasdb. Try IPLing from your
swap
volume and see what happens.
Mark Post
-----Original Message-----
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 12:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Attempting first IPL after initial SuSE install
Nope. I just did a fresh install that consisted of the following actions:
1) Load ramdisk version from HCM
2) Configure networky stuff
3) telnet into ramdisk system
4) ran insmod command to make devices available
5) ran YaST
6) Tried to IPL.
I followed the instructions to the letter this time just to make sure I
didn't have assumptions.
I did not manually adjust the parmline file, or anything else. I let Yast
do everything.
My understanding is that YaST should run silo, etc, under the covers. Is
this true?
At any rate I am now back to the point at which I was when I began manually
trying to run silo and get it to boot.
The symptoms don't change. Device status 0c and subchannel status 40.
What should the next step be?
|---------+---------------------------->
| | "Post, Mark K" |
| | <[EMAIL PROTECTED]|
| | m> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 03/12/2002 10:28 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>
---------------------------------------------------------------------------
-----------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Attempting first IPL after initial SuSE install
|
>
---------------------------------------------------------------------------
-----------------------------------|
So, if silo appeared to work, does your LPAR now IPL successfully? Or at
least _start_ to IPL, since it wasn't doing that before?
Mark Post
-----Original Message-----
From: James Melin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 9:16 AM
To: [EMAIL PROTECTED]
Subject: Re: Attempting first IPL after initial SuSE install
Silo appeared to work. I have seen no reference to zipl in any
documentation that I currently have. (dig...dig...dig) Ahh, the manual that
came with the install media... It's.... the 7.0 version I'm dealing with.
