Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@dsl2.external.hp.com>
To: "JOERGENSEN,RUNAR (HP-Norway,ex1)" <runar_joergensen@hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Startup problem X
Date: Wed, 19 Dec 2001 08:58:06 -0700	[thread overview]
Message-ID: <20011219155807.15CF9482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from "JOERGENSEN,RUNAR (HP-Norway,ex1)" <runar_joergensen@hp.com> of "Wed, 19 Dec 2001 13:35:29 +0100." <CDB09D386161D411881900D0B77FBBC106521DA9@ibsen.sweden.hp.com>

"JOERGENSEN,RUNAR (HP-Norway,ex1)" wrote:
> I'm a bit confused because I though we installed
> the 32bit version. In fact, when we boot we get
> thew following kernel: /boot/vmlinux-2.4.9-32.
> When I do a "file" on /boot/vmlinux-2.4.9-32,
> I get 32bit ELF executable.

Look at /etc/palo.conf and see what vmlinux it points to.
That's the one that's getting loaded/run.
By default you should have gotten a 32-bit kernel.
I doubt the syscall wrapper is the issue.

Newer 2.4.16 kernels are available from ftp.parisc-linux.org/kernels/32.
I suggest grabbing one of those.

> The OS line I presented was picked from what
> "XFree86 -version" reports.

eg. Build Operating System: Linux 2.4.13 i686 [ELF] 

"uname -m" will tell you which vmlinux you are running on *now*.
Not which one the XF86 binaries where built on.

> A mismatch in the image itself?

not likely.
Sounds like you have the original, mostly working kernel still.
Just try a newer one.

grant

       reply	other threads:[~2001-12-19 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CDB09D386161D411881900D0B77FBBC106521DA9@ibsen.sweden.hp.com>
2001-12-19 15:58 ` Grant Grundler [this message]
2001-12-17 18:37 [parisc-linux] Startup problem X JOERGENSEN,RUNAR (HP-Norway,ex1)
2001-12-18 19:24 ` 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=20011219155807.15CF9482A@dsl2.external.hp.com \
    --to=grundler@dsl2.external.hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=runar_joergensen@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox