linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Summerfield <reluctanthacker@js.id.au>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Intelfb, Q965 etc etc
Date: Thu, 12 Jun 2008 00:45:15 +0800	[thread overview]
Message-ID: <4850011B.6030202@js.id.au> (raw)

I have an HP DC7700 on which I wish to run SL5, a RHEL clone and xen. I
also wish to have framebuffer support whilst XEN is running.

I can do that with an IBM Thinkcentre with this video:
21:16 [summer@numbat ~]$ lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA])
         Subsystem: IBM Unknown device 0285
         Flags: bus master, fast devsel, latency 0, IRQ 17
         Memory at f0000000 (32-bit, prefetchable) [size=128M]
         Memory at e8000000 (32-bit, non-prefetchable) [size=512K]
         I/O ports at 1800 [size=8]
         Capabilities: <access denied>

21:17 [summer@numbat ~]$

I simply modprobe intelfb and all works well, despite nasturtiums cast
on this list.

I've noticed that intelfb does not support the graphics on my HP box:
[summer@bobtail ~]$ lspci -v -s 00:02.0
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965
Integrated Graphics Controller (rev 02) (prog-if 00 [VGA])
         Subsystem: Hewlett-Packard Company Unknown device 2801
         Flags: bus master, fast devsel, latency 0, IRQ 21
         Memory at f0400000 (32-bit, non-prefetchable) [size=1M]
         Memory at e0000000 (64-bit, prefetchable) [size=256M]
         I/O ports at 1100 [size=8]
         Capabilities: <access denied>

[summer@bobtail ~]$

I don't know much at all about these things, but it seemed a fair bet
that a '945G driver might work, so I did some hacking on intelfb and
I've booted.

The good news is that "modprobe intelfb" doesn't hang the system; the
screen goes powersaving, which given the gas supply here (Thankyou
Apache), is probably a good thing.

fbset finds a framebuffer driver and all seems well, better than it
should be:-) Except for the blank screen.

Time to call for help I think. But first:
http://sourceforge.net/mailarchive/forum.php?thread_name=4815EEB4.2060509%40frugalware.org&forum_name=linux-fbdev-devel 


says that intelfb isn't really being maintained, and that clever souls
are working on a replacement.

Now, that _was_ about six weeks ago.

vesafb (which I discovered cannot be compiled as a module) drives it
fine with standard (not XEN) kernels.

I have a similar system running F9 and it's fine _but_ it's so long
since I had a working kernel-xen in Fedora that I don't recall whether I
had XEN and framebuffer.

Since I wish to run SL5, I really should stay with 2.6.18 kernels.

Before I post the copious kernel messages I have and the patch for
others' perusal, what does the list recommend?





-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

                 reply	other threads:[~2008-06-11 16:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4850011B.6030202@js.id.au \
    --to=reluctanthacker@js.id.au \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).