All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: Matt Taggart <taggart@carmen.fc.hp.com>
Cc: Robert Liesenfeld <xunil96@yahoo.com>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Init not found on 735/125?
Date: Thu, 22 Mar 2001 09:57:10 +0000	[thread overview]
Message-ID: <20010322095710.C18942@linuxcare.com> (raw)
In-Reply-To: <20010322030651.33A5B38145@carmen.fc.hp.com>; from taggart@carmen.fc.hp.com on Wed, Mar 21, 2001 at 08:06:51PM -0700

On Wed, Mar 21, 2001 at 08:06:51PM -0700, Matt Taggart wrote:
> 
> Robert Liesenfeld writes...
> 
> > I'm much closer to being able to install palinux on my 735/125...at the momen
> > t, the main problem
> > I'm having is this:
> [snip]
> 
> You could try using sash as init and see if you get further. I think this is 
> the same problem as Richard mentioned in,
> 
> http://lists.parisc-linux.org/pipermail/parisc-linux/2001-March/012025.html
> 
> It's solved by a new glibc that's 16 byte aligned. See the message I just sent 
> out about where to get the new glibc debs from.

No, different problem I think.  My system found init, but init then hung.
Robert is seeing:

> Kernel panic: No init found.  Try passing init= option to kernel.

Maybe his 735/125 is mounting the wrong dir, maybe his sbin/init doesn't
have execute access.  I'd check I could nfs mount that dir from some
other machine, and see sbin/init ok.  Using init=/bin/sash is a good
idea anyway, except I don't think sash is on the .iso, so you need
to build it or ask nicely ;)

Richard

  reply	other threads:[~2001-03-22  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22  1:19 [parisc-linux] Init not found on 735/125? Robert Liesenfeld
2001-03-22  3:06 ` Matt Taggart
2001-03-22  9:57   ` Richard Hirst [this message]
     [not found] <20010322155704.A19315@linuxcare.com>
2001-03-23 10:50 ` Robert Liesenfeld
2001-03-23 11:53   ` Richard Hirst

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010322095710.C18942@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@parisc-linux.org \
    --cc=taggart@carmen.fc.hp.com \
    --cc=xunil96@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.