All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>
Cc: stegall@bayou.uni-linz.ac.at
Subject: Re: Fw: 2.6.11, framebuffer
Date: Tue, 15 Feb 2005 07:50:53 +0800	[thread overview]
Message-ID: <200502150750.53844.adaplas@hotpop.com> (raw)
In-Reply-To: <20050214100348.3542b897.akpm@osdl.org>

On Tuesday 15 February 2005 02:03, Andrew Morton wrote:
> Begin forwarded message:
>
> Date: Mon, 14 Feb 2005 12:56:08 +0100 (CET)
> From: stegall@bayou.uni-linz.ac.at
> To: akpm@osdl.org
> Subject: 2.6.11, framebuffer
>
>
> framebuffer, intel, 915g
>
> Greetings,
> complaints were requested, but I am not sure this is the correct
> place to make them:
>
> I cannot start a frame buffer on 2.6,11x using
> hardware with the
>     intel 915g
> chip. Either it crashes or nothing happens, depending on modules,
> kernel compilation etc. Nothing works.
>
> One thing I did see was
>
>    allocation failed: out of vmalloc space - use
> vmalloc=<size> to increase size.
>
> I realize that this chip is ``new'', but
> it works quite satisfactorily  on 2.4.10* !

What driver are you using vesafb or intelfb? 915 support is a very recent
addition.

Can you send your dmesg and kernel config?

Tony




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      parent reply	other threads:[~2005-02-14 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 18:03 Fw: 2.6.11, framebuffer Andrew Morton
2005-02-14 19:19 ` Zack Smith
2005-02-14 23:52   ` Antonino A. Daplas
2005-02-14 23:50 ` 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=200502150750.53844.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=akpm@osdl.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=stegall@bayou.uni-linz.ac.at \
    /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.