public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@2gen.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: X and intelfb fight over videomode
Date: Fri, 18 Nov 2005 00:45:10 +0100	[thread overview]
Message-ID: <20051117234510.GA3854@hardeman.nu> (raw)
In-Reply-To: <437C0BF2.4010400@gmail.com>

On Thu, Nov 17, 2005 at 12:49:54PM +0800, Antonino A. Daplas wrote:
>Ignore the hack I mentioned in the previous thread.  Try this patch instead.

Didn't help, the messages remain the same (tried with vga=0x318 and 
video=intelfb:1024x768-32@60,mtrr=0 vga=0x318).

Boot:
intelfb: 00:02.0: Intel(R) 852GM, aperture size 128MB, stolen memory 8060kB
intelfb: Non-CRT device is enabled ( LVDS port ).  Disabling mode switching.
intelfb: Initial video mode is 1024x768-32@60.
intelfb: Changing the video mode is not supported.
Console: switching to colour frame buffer device 128x48

Starting X:
mtrr: base(0xe0020000) is not aligned on a size(0x300000) boundary
[drm:drm_unlock] *ERROR* Process 2976 using kernel context 0

First time I switch from X to VC:
intelfb: Changing the video mode is not supported.
intelfb: ring buffer : space: 6024 wanted 65472
intelfb: lockup - turning off hardware acceleration

Other suggestions?

//David

  reply	other threads:[~2005-11-17 23:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  0:01 X and intelfb fight over videomode David Härdeman
2005-11-17  1:11 ` Antonino A. Daplas
2005-11-17  1:45   ` David Härdeman
2005-11-17  2:03     ` Antonino A. Daplas
2005-11-17  4:49     ` Antonino A. Daplas
2005-11-17 23:45       ` David Härdeman [this message]
2005-11-18  1:08         ` Antonino A. Daplas
2005-11-18 18:36           ` David Härdeman
2005-11-18 20:32             ` Antonino A. Daplas

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=20051117234510.GA3854@hardeman.nu \
    --to=david@2gen.com \
    --cc=adaplas@gmail.com \
    --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