From: "David Härdeman" <david@2gen.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: X and intelfb fight over videomode
Date: Thu, 17 Nov 2005 02:45:58 +0100 [thread overview]
Message-ID: <20051117014558.GA30088@hardeman.nu> (raw)
In-Reply-To: <437BD8D9.9030904@gmail.com>
On Thu, Nov 17, 2005 at 09:11:53AM +0800, Antonino A. Daplas wrote:
>David Härdeman wrote:
>> intelfb: Changing the video mode is not supported.
>Try booting with video=intelfb:1024x768-16@60,mtrr=0. Do not include
>the vga=0x318 option. This prevents intelfb from changing the videomode.
It seems that intelfb can't change it no matter what....booting with
video=intelfb:1024x768-16@60,mtrr=0 gives me the usual vga console and
no framebuffer. The following is printed during boot:
[...]
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 855 Chipset.
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xe0000000
[drm] Initialized drm 1.0.0 20040925
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G chipsets
intelfb: Version 0.9.2
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
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: Video mode must be programmed at boot time.
[...]
On the other hand, the vga=0x318 gives a 1024x768 console (and the vc
<-> X fight) with the following messages during boot:
[...]
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 855 Chipset.
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xe0000000
[drm] Initialized drm 1.0.0 20040925
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G chipsets
intelfb: Version 0.9.2
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
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
[...]
(I tried X in 1024x768-32bpp after seeing the messages from the vga=...
boot but the problems remained)
Suggestions?
//David
next prev parent reply other threads:[~2005-11-17 1:46 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 [this message]
2005-11-17 2:03 ` Antonino A. Daplas
2005-11-17 4:49 ` Antonino A. Daplas
2005-11-17 23:45 ` David Härdeman
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=20051117014558.GA30088@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