public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: agp_backend_initialize() failed on ServerWorks CNB20LE
Date: Fri, 2 Sep 2005 19:14:23 -0400	[thread overview]
Message-ID: <20050902231423.GD24062@redhat.com> (raw)
In-Reply-To: <1957123248.20050902232139@dns.toxicfilms.tv>

On Fri, Sep 02, 2005 at 11:21:39PM +0200, Maciej Soltysiak wrote:
 > Hello,
 > 
 > On a server with ServerWorks CNB20LE and CONFIG_AGP_SWORKS enabled
 > I get these upon bootup:
 > Linux agpgart interface v0.101 (c) Dave Jones
 > agpgart: unable to determine aperture size.
 > agpgart: agp_backend_initialize() failed.
 > agpgart-serverworks: probe of 0000:00:00.0 failed with error -22
 > agpgart: unable to determine aperture size.
 > agpgart: agp_backend_initialize() failed.
 > agpgart-serverworks: probe of 0000:00:00.1 failed with error -22

Every time I've seen this reported so far, its turned out that the board
doesn't actually have an AGP slot. Is this case here too ?

Documentation on serverworks chipsets is as good as non-existant,
so there's not a great deal we can do here.

 > The only problems I have that *may* be related to these messages is the
 > fact that when I boot into X and try to switch to a text console, the
 > screen gets garbled and freezes, the server works fine besides the
 > screen throwing trash at me.

Likely completely unrelated. agpgart is used only for accelerated 3d.

		Dave


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02 21:21 agp_backend_initialize() failed on ServerWorks CNB20LE Maciej Soltysiak
2005-09-02 23:14 ` Dave Jones [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=20050902231423.GD24062@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solt2@dns.toxicfilms.tv \
    /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