public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Miles Lane <miles@megapathdsl.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.20 -- Hanging (no oops and sysrq fails) after switching to rivafb
Date: Tue, 4 Jun 2002 21:27:47 +0100	[thread overview]
Message-ID: <20020604212747.C32338@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1023175418.7859.32.camel@agate> <Pine.LNX.4.44.0206041314110.1200-100000@www.transvirtual.com>

On Tue, Jun 04, 2002 at 01:16:49PM -0700, James Simmons wrote:
> 
> > I tried booting both with acpi enabled and with pci=noacpi set.
> > When the machine freezes, the VT display mode has just switched
> > to using rivafb (video=riva:1600x1200-16).
> 
> I plan to port this driver next over to the new api. I planned on doing it
> today except Linus BK tree will not compile right now :-( I get a
> 
> /usr/include/asm/eerno.h:4: asm-generic/errno.h: No such file or directory
> make[1]: *** [split-include] Error 1

If you're seeing this then your /usr/include/{asm,linux} are symlinks to
your current kernel source.  These directories must contain a copy of
the kernel header files that were used to build glibc with, not the
copy that came with the kernel you're currently running.

(Please note: this is a FAQ - there's probably even a FAQ entry for it.)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2002-06-04 20:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04  7:23 2.5.20 -- Hanging (no oops and sysrq fails) after switching to rivafb Miles Lane
2002-06-04 20:16 ` James Simmons
2002-06-04 20:27   ` Russell King [this message]
2002-06-04 20:43     ` James Simmons

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=20020604212747.C32338@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@megapathdsl.net \
    /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