public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John McGowan <jmcgowan@inch.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.9: i810 video
Date: Fri, 5 Nov 2004 11:06:49 -0500 (EST)	[thread overview]
Message-ID: <20041105110215.I85742@shell.inch.com> (raw)
In-Reply-To: <21d7e99704110421597deb381c@mail.gmail.com>

On Fri, 5 Nov 2004, Dave Airlie wrote:

> >
> > By the way, the X server runs. There is no problem with that.
> >
> > If I start it (say, with ICE as a window manager starting up an xterm)
> > *immediately after boot* I get a clean, black screen. It should be dark
> > green. I get the frame for the xterm. No xterm. I can right click to get
> > the menu to display on the screen but it gets locked there. I can right
> > click again to get a working menu and choose to logout.
> >
> > If I do something befor starting it, the screen is filled with junk.
> > Something is writing to the video ram. If I close it and restar it,
> > different junk.
> >
> > It seems that the initialization of the i810 is leaving its video ram
> > free to be grabbed and used.
>
> Can you throw your .config this way as well, I've just built 2.6.9
> with i810 drm and no i810 framebuffer (CONFIG_DRM_I810 and
> !CONFIG_FB_I810) and played tuxracer just fine for a few minutes under
> a gnome session on a Fedora core 1 box with a prerelease of Xorg
> 6.8... (my i810 test machine doesn't get taken out all that often...)
>
> I did just modprobe the i810 framebuffer module I also built and try
> to start X and X wouldn't start with a unable to bind system texture
> memory,.... so trying building a kernel without i810 framebuffer
> switched on a see what happens..

I had compiled a kernel without frame buffer (no frame buffer support at
all). Starting X gave the same screen (if I start X after doing something,
it come up with junk on it - if I start X immediately after booting, it
comes up black (should be dark green) and is unusable).

Let me try the simplest kernel configuration I can.

Regards from:

    John McGowan  |  jmcgowan@inch.com                [Internet Channel]
                  |  jmcgowan@coin.org                [COIN]
    --------------+-----------------------------------------------------

  reply	other threads:[~2004-11-05 16:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 21:53 Kernel 2.6.9: i810 video John McGowan
2004-11-03 21:58 ` Dave Airlie
2004-11-03 22:12   ` John McGowan
2004-11-03 22:15     ` Dave Airlie
2004-11-04  4:47       ` John McGowan
2004-11-04 21:34         ` Bill Davidsen
2004-11-04 22:30           ` John McGowan
2004-11-05  5:59             ` Dave Airlie
2004-11-05 16:06               ` John McGowan [this message]
2004-11-05 18:01               ` John McGowan

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=20041105110215.I85742@shell.inch.com \
    --to=jmcgowan@inch.com \
    --cc=airlied@gmail.com \
    --cc=davidsen@tmr.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