All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Puetz <puetzk@iastate.edu>
To: Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
Cc: mlan@cpu.lu, ldl@chpc.utah.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: controlfb.c bug in VRAM bank2 check if bank1
Date: Wed, 15 Sep 1999 14:26:55 -0400	[thread overview]
Message-ID: <E11RKhj-0001UA-00@puetz.penguinpowered.com> (raw)
In-Reply-To: Your message of "Wed, 15 Sep 1999 13:05:10 EDT." <199909151707.MAA16408@lists.linuxppc.org>



khendricks@admin.ivey.uwo.ca said:
> 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.

If you use 'no video driver' Linux will see the amount of VRAM that was 
actually in use by MacOS when booting. You should probably look into a newer 
kernel with aty128fb

> Any fixes along these lines would be greatly appreciated (this is with
> Paul's  2.2.10 stable kernel available from his website).

Which is probably just old enough not to have the correct driver.

> Just thought someone in the know should be told :-)

> Kevin 


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-09-15 18:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15 17:05 controlfb.c bug in VRAM bank2 check if bank1 Kevin_Hendricks
1999-09-15 18:26 ` Kevin Puetz [this message]
  -- 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=E11RKhj-0001UA-00@puetz.penguinpowered.com \
    --to=puetzk@iastate.edu \
    --cc=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.