Jim, There have been some reports of problems with IPLs after initial installs, but they were against the Red Hat GA. What you can do is re-IPL your installation setup, mount the root file system on /mnt (for instance), then do a "chroot /mnt". From there, cd to /boot, and re-run the silo command. You should see something similar to this, which will indicate success: Silo:o->image set to /boot/image-2.2.16-122-tape Silo:o->ipldevice set to /dev/dasda Silo:o->parmfile set to /boot/par Silo:o->bootsect set to /boot/ipleckd.boot Silo:o->Testonly flag is now 0 Silo:o->Testlevel is set to 0 Silo:o->IPL device is:'/dev/dasda ' Silo:o->bootsector is:'/boot/ipleckd.boot '...ok... Silo:o->bootmap is:'/boot/image-2.2.16-122-tape ' ....ok... Silo:o->Kernel image is:'/boot/ipleckd.boot ' ....ok... Silo:o->original parameterfile is:'/boot/parm '...ok...final parameter parm is:'/boot/parm ' ....ok... Silo:ix 0:offset:078523 count:0c address 0x00000000 Silo:ix 1:offset:078530 count:80 address 0x0000c000 Silo:ix 2:offset:0785b0 count:80 address 0x0008c000 Silo:ix 3:offset:078630 count:6f address 0x0010c000 Silo:ix 4:offset:07a8de count:01 address 0x00008000 Silo:Bootmap is in block no:0x00001ed7
At that point, you should "exit" followed by "cd /" followed by "umount /mnt" followed by re-trying your IPL from the SE. Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 11:58 AM To: [EMAIL PROTECTED] Subject: Re: Attempting first IPL after initial SuSE install Right. That's a semantic misnomer from my part. I said that because that's where the LPAR is told what load device to run from is. The thing is that the ramdisk image worked and accessed the devices properly. Should I manually run a silo command with the T2 option specified? I am unsure if YaST did that all properly. Thanks for the info on the subchannel status. That give me someplace to start. Jim: The device status is Channel End + Device End, which is normal. The subchannel status is Incorrect Length, which may indicate that you have something wrong with your image on disk. The associated channel program should start at absolute location 8. See "Initial Program Loading" in the Principles of Operation for details. You aren't booting "from" the SE, by the way. You're booting via the SE from DASD. The SE is just the messenger. Romney On Mon, 11 Mar 2002 10:05:22 -0600 James Melin said: >Has anyone seen this message on the SE console when attempting to ipl a >freshly installed Linux? > >The load control unit or device is busy. Device status is 0C and >subchannel status is 40. > >This is in a G5 with Ficon to a ficon director and from there into an IBM >'shark' dasd box. > >I'm having trouble finding the device status codes and subchannel status >codes as they might pertain to an initial load from the service element.
