From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>
Cc: s.egbert@sbcglobal.net
Subject: Re: Fw: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug)
Date: Sat, 15 Jan 2005 20:33:31 +0800 [thread overview]
Message-ID: <200501152024.58452.adaplas@hotpop.com> (raw)
In-Reply-To: <20050114170445.0d02ae91.akpm@osdl.org>
On Saturday 15 January 2005 09:04, Andrew Morton wrote:
> Are you folks aware of this lkml thread??
>
> Thanks.
His lspci shows:
0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP VGA Display Adapter (prog-if 00 [VGA])
Subsystem: Elitegroup Computer Systems: Unknown device 1b13
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
BIST result: 00
Region 0: Memory at d8000000 (32-bit, prefetchable)
Region 1: Memory at e5000000 (32-bit, non-prefetchable) [size=128K]
Does this look strange? Usually each resource shows both the start address
and resource size. Region 0 does not show the resource size. This is probably
confusing vesafb.
Also, his /proc/iomem shows
...
f000ef6f-f100ef6e : vesafb
...
Besides it not matching the lspci output, the start address is not 4K aligned.
You can try this (no guarantees), tell vesafb the actual amount of RAM the
card has (assuming standard kernel vesafb):
video=vesafb:vtotal:N
where N = the total amount of Video RAM in MiB
Tony
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
prev parent reply other threads:[~2005-01-15 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 1:04 Fw: Re: disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug) Andrew Morton
2005-01-15 12:33 ` 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=200501152024.58452.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=s.egbert@sbcglobal.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;
as well as URLs for NNTP newsgroup(s).