No, I wasn't joking, but that doesn't mean I was right, either. Sigh. If you can't tell, it's been a while since I did a SUSE install from the beginning. I was thinking of the "starter" kernel that you use, depending on whether you'll be IPLing from tape, or the VM reader. Sorry. Once you've gotten zipl run successfully, that characteristic of the kernel is no longer relevant.
I guess it's time to start asking more detailed questions. Show us the output of: cat /proc/dasd/devices df /boot dd if=/dev/dasdb bs=512 count=12 | od Substitute the device name of your IPL volume for this particular system in place of /dev/dasdb, if necessary. Note that this is the device node, not a partition node, so don't use /dev/dasdb1, or /dev/dasdb2, etc. Also, what virtual device number do you IPL from? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Sue Sivets Sent: Wednesday, February 04, 2004 11:08 PM To: [EMAIL PROTECTED] Subject: Re: Ipl problem after instal on vm mdisk Hi Mark, when I first read your message I thought you were joking, but I'm almost hoping that you aren't. How do I tell, or can I tell if I'm using an "LPAR" kernel? Does such a thing really exist? I copied the ramdisk boot files from the cdrom to a VM minidisk, punched them to the reader, and ipl'ed. I didn't get any error messages, or I guess I should say I didn't get any messages that looked like error messages. Then I did a "normal" install, just like I the installs I've done in the LPARs. I can re-install if I have to, but needless to say, that's not my first choice of fun things on my long list of things to do. Sue "Post, Mark K" wrote: > Hmm, the other possibility (?) is that Sue is using an "LPAR" kernel, and > not the one with VM support. > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Rob > van der Heij > Sent: Wednesday, February 04, 2004 2:47 AM > To: [EMAIL PROTECTED] > Subject: Re: Ipl problem after instal on vm mdisk > > On Wed, 2004-02-04 at 08:08, Sue Sivets wrote: > > I just finished installing Suse Linux on a VM mini disk (previous installs > were > > in standalone lpars). When I tried to ipl the system for the first time I > > received the following message: > > HCPGIR453W CP entered; program interrupt loop > > Since I wasn't at all sure the ipl text really was written, I linked the > new mini > > disk to another linux guest and re-ran zipl. The system still doesn't ipl. > > Has anyone run into something like this before? Does anyone have any ideas > about > > what I can or should do next? > > Could it be that the userid is in XC mode (Q SET) now, or maybe short of > storage? If zipl did not write the IPL records you'd get different ones. > One option could be that the contents of /boot changed after zipl and it > now points the wrong way. You could make sure and start from the ramdisk > system again, load the dasd driver and re-run zipl. > If nothing else you could run TRACE I during IPL and see where it gets. > > Rob -- Suzanne Sivets Systems Programmer Innovation Data Processing 973-890-7300 Fax 973-890-7147 [EMAIL PROTECTED]
