Re: [suse-sparc] Boot problem with AXi machine

From: Mike Nicewonger (twmaster@twmaster.com)
Date: Tue Nov 21 2000 - 01:38:11 PST

  • Next message: Joshua Uziel: "Re: [suse-sparc] Install problems (Sparc-5)"

    Message-ID: <001501c0539e$f5011180$04191fac@cidera.com>
    From: "Mike Nicewonger" <twmaster@twmaster.com>
    Date: Tue, 21 Nov 2000 04:38:11 -0500
    Subject: Re: [suse-sparc] Boot problem with AXi machine
    

    Hi All,

    > * Mike Nicewonger <twmaster@twmaster.com> [001119 14:43]:
    > > Well things have not been good, I shut the machine down last night after
    > > much delight in setting it up and seeing it work nicely. Now it won't
    boot.
    > > I get the following message:
    > >
    > > Warning: Fcode sequence resulted in a net stack depth change of 1
    > > The file just loaded does not appear to be executable
    >
    > Hmm... run "printenv" at the PROM OK prompt and see what "boot-device"
    > is set to. Check that if it's a "disk#" in the front that the scsi id
    > matches in "devalias" what you see in a "probe-scsi". If not, or if
    > it's not set to a disk, you can change it with the "setenv" command.

    Yep, I looked and the boot-device is pointed to the correct drive.

    >
    > > Now from past experience this tells me that the machine cannot find the
    boot
    > > partition or file it wants. I have tried pointing the PROM to the first
    > > partition and it does the same error message. Do I need to add a file
    > > argument? if so what?
    >
    > Another possibility is that either the kernel or silo were not properly
    > installed. If the previous check doesn't work, boot off the CD and go
    > to a virtual terminal. Mount the root partition (and /boot under it if
    > it is a separate partition (which isn't necesary on an UltraSPARC)).
    > Look in /boot for vmlinux and in /etc for silo.conf... see if either is
    > missing.

    I will try this later when I get a few extra minutes. I suspect the box
    wants an argument pointing to either SILO or the kernel.

    >
    > I guess we'll go from there... and if this (the latter) is what is the
    > problem, then if you want to help diagnose the cause, we can fix it
    > before the next release. :)
    >

    I'll get back later when I have better info.

    Cheers,

    Mike N



    This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:19 PDT