Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Gururaj Ananthateerta <gururaj@cup.hp.com>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: parisc <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] new vmlinux!!!
Date: Tue, 12 Mar 2002 12:13:40 -0800	[thread overview]
Message-ID: <3C8E6174.9DEBC925@cup.hp.com> (raw)
In-Reply-To: 20020312172445.B11A64849@dsl2.external.hp.com

I figured out my mistake.

First my partitions weren't correct. I created
an F0 partition, and swap and an ext2 for /.

boot partition was missing, rather it was i /. As / is not mounted
during the early stages of boot (my guess) the palo used to scream at
me.

Secondly, a strange observation.  Partitions are created in the following
order seems to have have some problem  during from /boot/vmlinux.

50 MB of  FO partition
50 MB of /boot
256 MB of swap
remaining for /

Problem is solved if partitions are created in the following order.

/dev/sda1             1        95     97264   83
Linux                           /boot
/dev/sda2            96       119     24576   f0  Linux/PA-RISC boot
/dev/sda3           120       363    249856   82  Linux swap
/dev/sda4           364      8683   8519680   83  Linux                    /

Doesn't make much sense.

One more thing to add, I am doing all this stuff on a N-Class.

Guru








Grant Grundler wrote:

> Gururaj Ananthateerta wrote:
> > I have 3 partitions on primary disk
> >    Device Boot    Start       End    Blocks   Id  System
> > /dev/sda1             1        95     97264   f0  Linux/PA-RISC boot
> > /dev/sda2            96       339    249856   82  Linux swap
> > /dev/sda3           340      8683   8544256   83  Linux
>
> partitions are fine.
>
> > I am doing some modifications to the code and trying to boot with a new
> > linux.
> > I placed my vmlinux in /boot, but the palo doesn't seems to recognize my
> > kernel.
>
> What do you mean by "doesn't seems to recognize"?
> any specific error msg?
>
> does palo.conf point to that kernel?
> or did you interact with palo to tell it to load that image?
> "file /boot/vmlinux" says what?
>
> you don't have to answer the above - just stuff to think about.
>
> grant

  parent reply	other threads:[~2002-03-12 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 15:54 [parisc-linux] woody install on 720/50 Albert Strasheim
     [not found] ` <20011002082429.C1965@silly.cloud.net.au>
2001-10-01 23:27   ` Albert Strasheim
     [not found]     ` <20011002204531.A3317@silly.cloud.net.au>
2001-10-02 15:56       ` Albert Strasheim
2001-10-02 12:37 ` Jochen Friedrich
2001-10-05 20:20   ` Albert Strasheim
2001-10-05 20:56     ` Matthew Wilcox
2001-10-05 21:36       ` Albert Strasheim
2002-03-11 22:56         ` [parisc-linux] new vmlinux!!! Gururaj Ananthateerta
2002-03-12  6:34           ` Ralf Hildebrandt
2002-03-12 17:24           ` Grant Grundler
2002-03-12 18:16             ` Paul Bame
2002-03-13  4:29               ` Gururaj Ananthateerta
2002-03-12 20:13             ` Gururaj Ananthateerta [this message]
2002-03-12 22:26               ` Grant Grundler

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=3C8E6174.9DEBC925@cup.hp.com \
    --to=gururaj@cup.hp.com \
    --cc=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox