From: Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
To: mlan@cpu.lu, ldl@chpc.utah.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb.c bug in VRAM bank2 check if bank1
Date: Wed, 15 Sep 1999 13:05:10 -0400 (EDT) [thread overview]
Message-ID: <199909151707.MAA16408@lists.linuxppc.org> (raw)
Hi,
Just to add fuel to the fire (although I am not sure if this is related or not)
My B+W G3 rev2 with 16MB of vram has never ever detected the correct amount. In
fact, if I run Xconfigurator, it tells me I have less then 1MB of vram and
therefore won't let me use any of the higher resolutions that should work.
The interesting thing is that if I change my bpp via the MacOS, Xconfigurator
reports completely different amounts of vram available and not in any logical
way that I can see.
Any fixes along these lines would be greatly appreciated (this is with Paul's
2.2.10 stable kernel available from his website).
Just thought someone in the know should be told :-)
Kevin
>> Hmm... official 2.2.12 does detect my 4 MB... and this is a 7600, so the same
>> motherboard as the 7500...
>>
>> Michel . . .
>
>Odd. I thought I tried stock 2.2.12 and it didn't detect the 4MB VRAM in my
>PowerMac 7500. Now I'm not so sure. A quick diff of the kernel controlfb.c
sources
>between 2.2.6 and 2.2.12 reveal no difference though in the VRAM bank check
code
>though so it also seems to me that if people had this problem in 2.2.6 then
2.2.12
>should also be unable to detect the full 4MB VRAM. If you're saying that the
>hardware should be identical then could some other software be responsible such
as
>the OF software be perhaps different and causing this different behavior? I'd
>really like some confirmation now that others with 7500 don't get all
>4MB VRAM detected even using stock 2.2.12. I've read postings from others that
>they didn't get 4MB VRAM detected but I don't think that was with 2.2.12 at
that
>time.
>
--
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
Richard Ivey School of Business, University of Western Ontario
London, Ontario N6A-3K7 CANADA
khendricks@ivey.uwo.ca, (519) 661-3874, fax: 519-661-3959
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-15 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-15 17:05 Kevin_Hendricks [this message]
1999-09-15 18:26 ` controlfb.c bug in VRAM bank2 check if bank1 Kevin Puetz
-- strict thread matches above, loose matches on Subject: below --
1999-09-10 15:55 Lou Langholtz
1999-09-10 17:08 ` Lou Langholtz
1999-09-10 18:33 ` Michel Lanners
1999-09-12 16:58 ` Lou Langholtz
1999-09-13 18:13 ` Michel Lanners
1999-09-15 15:14 ` Lou Langholtz
1999-10-12 7:07 ` Lou Langholtz
1999-10-12 6:49 ` Lou Langholtz
1999-10-12 14:50 ` Daniel Jacobowitz
1999-10-12 15:36 ` Lou Langholtz
1999-10-13 6:30 ` Geert Uytterhoeven
1999-09-11 10:51 ` Brad Boyer
1999-09-10 20:13 ` Daniel Jacobowitz
1999-09-11 9:23 ` Benjamin Herrenschmidt
1999-09-12 18:10 ` Daniel Jacobowitz
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=199909151707.MAA16408@lists.linuxppc.org \
--to=khendricks@admin.ivey.uwo.ca \
--cc=ldl@chpc.utah.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.