public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Didier Moens <Didier.Moens@dmb001.rug.ac.be>
To: linux-kernel@vger.kernel.org
Subject: [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)]
Date: Mon, 26 Nov 2001 11:12:00 +0100	[thread overview]
Message-ID: <3C021570.4000603@dmb.rug.ac.be> (raw)



Stephan von Krawczynski wrote:

 >On Sun, 25 Nov 2001 15:09:13 +0100
 >Didier Moens <moensd@xs4all.be> wrote:
 >
 >>Dear,
 >>
 >>Stephan von Krawczynski wrote:
 >>
 >>>
 >>>Hello Marcelo,
 >>>
 >>>I tried to find the current maintainer of agpgart module, but couldn't
 >>>find any in the MAINTAINERS list. Who is it?
 >>>I obviously could fix the oops, but I would need some input on how
 >>>I830M chipset looks like on a working config to further investigate
 >>>Didiers problem.
 >>>Any hints?
 >>>
 >>>Regards,
 >>>Stephan
 >>>
 >>>
 >>Anything I can do to help out ?
 >>
 >
 >Hm, well if you can get your hands on another box with i830, another lspci
 >output would be of interest.
 >

Examining the code :

                         if (i810_dev == NULL) {
                                 printk(KERN_ERR PFX "agpgart: Detected an "
                                        "Intel i815, but could not find the"
                                        " secondary device. Assuming a "
                                        "non-integrated video card.\n");
                                 break;


This leads me to believe the "secondary device"  could be the integrated
graphics component on the i810/815.

As the i830M doesn't have one (the i830MG does), I suppose this could
lead to the aforementioned error message, and hence failure of the
agpgart modprobe ?

Could it be that one has to differentiate between i830MG (secondary
device, and hence analoguous to i810/i815) and i830M (no secondary
device, and possibly analoguous to i830/i840/i845/... : no check for 2nd
device needed ) ?


Offcourse, I could be utterly wrong.


Regards,
Didier





             reply	other threads:[~2001-11-26 10:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 10:12 Didier Moens [this message]
     [not found] <linux.kernel.3C021570.4000603@dmb.rug.ac.be>
2001-11-26 11:47 ` [Fwd: Re: OOPS in agpgart (2.4.13, 2.4.15pre7)] Nicolas Aspert
2001-11-26 21:07   ` Robert Love
2001-11-26 22:16     ` Didier Moens
2001-11-27  7:57       ` Nicolas Aspert
     [not found]       ` <20011127101148.C5778@crystal.2d3d.co.za>
     [not found]         ` <3C034CAE.2090103@dmb.rug.ac.be>
2001-11-27  9:10           ` Abraham vd Merwe
2001-11-27  9:52             ` Didier Moens
2001-11-27 10:05               ` Nicolas Aspert
2001-11-27 10:48                 ` Didier Moens
2001-11-27 11:12                   ` Stephan von Krawczynski
2001-11-27 11:43                     ` Nicolas Aspert
2001-11-27 12:10                       ` Stephan von Krawczynski
2001-11-27 12:49                       ` Didier Moens
2001-11-27 10:51       ` Stephan von Krawczynski

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=3C021570.4000603@dmb.rug.ac.be \
    --to=didier.moens@dmb001.rug.ac.be \
    --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