From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
bjk@luxsci.net, Andrew Morton <akpm@osdl.org>
Subject: Re: Bugzilla: PCI resource address mismatch
Date: Tue, 21 Feb 2006 07:26:26 +0800 [thread overview]
Message-ID: <43FA5022.6070404@gmail.com> (raw)
In-Reply-To: <20060220142600.A25613@jurassic.park.msu.ru>
Ivan Kokshaysky wrote:
> On Mon, Feb 20, 2006 at 08:51:15AM +0800, Antonino A. Daplas wrote:
> Starting from 2.6.13, kernel tries to resolve that sort of conflicts,
> so that prefetch window of the bridge and the framebuffer memory behind
> it get moved to 0x10000000.
> Unfortunately, video BIOS still expects the framebuffer to be at 0xff000000,
> that's why vesafb doesn't work.
>
> Booting with "mem=64M" (or what amount of RAM he has) should fix that,
> as it causes the kernel to ignore e820 entries above 64M.
>
Ben reported that the mem= option worked for him. I presume that this
is the best solution for this problem?
Tony
prev parent reply other threads:[~2006-02-20 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 0:51 Bugzilla: PCI resource address mismatch Antonino A. Daplas
2006-02-20 11:26 ` Ivan Kokshaysky
2006-02-20 11:31 ` Andrew Morton
2006-02-20 23:26 ` Antonino A. Daplas [this message]
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=43FA5022.6070404@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=bjk@luxsci.net \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.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