public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: VEGH Karoly <karoly.vegh@uta.at>
To: linux-kernel@vger.kernel.org
Subject: i865G chipset AGP support - report
Date: Mon, 18 Aug 2003 10:44:46 +0200	[thread overview]
Message-ID: <20030818084446.GI5732@marvin> (raw)


Hi,

I just found an interesting behaviour of the agpgart code in
the Linux kernel with a (quite new chipset) MSI 865PE motherboard.

in the /usr/src/linux/drivers/char/agp/agpgart_be.c 2 names are in, 
but AFAIK Jeff Hartmann doesn't actively maintain the code anymore,
(also couldn't reach him at jhartmann@precisioninsight.com), and 
I'm not quite sure if David Dawes got my report, so I decided to 
post here.

Please let me have a CC personally if you reply.

I have quite a new motherboard, (MSI 865PE) with an Sapphire
Radeon 9500 128Mb card.

The agpgart module I can load fine with the 2.4.22-pre10 kernel-version:

bh:/usr/src# uname -a 
Linux bh 2.4.22-pre10 #1 Sat Aug 2 09:38:38 CEST 2003 i686 GNU/Linux
bh:/usr/src# dmesg | grep -i agp
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: Detected Intel(R) 865G chipset
agpgart: AGP aperture is 64M @ 0xf8000000
bh:/usr/src# 

couldn't load it with 2.4.22-pre8 (that's why the upgrade), I thought 
it was fixed, but now with 2.4.22-rc2 I again get the same errormsg 
that i got with 2.4.22-pre8:

bh:~# uname -a 
Linux bh 2.4.22-rc2 #1 Wed Aug 13 19:28:57 CEST 2003 i686 GNU/Linux
bh:~# modprobe agpgart
/lib/modules/2.4.22-rc2/kernel/drivers/char/agp/agpgart.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-rc2/kernel/drivers/char/agp/agpgart.o: insmod /lib/modules/2.4.22-rc2/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.22-rc2/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed
bh:~# dmesg | grep -i agp
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 941M
agpgart: Detected an Intel(R) 865G, but could not find the secondary device. Assuming a non-integrated video card.
agpgart: unsupported bridge
agpgart: no supported devices found.
bh:~#

Question: Whom can I help you with more information? What info do you need
more from me that can help your work?

Is the Documentation up-to-date? Chipset 865 isn't mentioned in it, (although 
it works with -pre10)

Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
CONFIG_AGP_INTEL
  This option gives you AGP support for the GLX component of the
  XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.

and didnt find the ChangeLog as well...

bh:/usr/src/linux/drivers/char# find . -iname changelog -type f
./ChangeLog
bh:/usr/src/linux/drivers/char# grep -i agp ChangeLog 
bh:/usr/src/linux/drivers/char# 

TIA & HTH

charlie

-- 
Végh Károly -  System Engineer - UTA - TIS.SAS.BSS
Don't worry. Everything is getting nicely out of control.

                 reply	other threads:[~2003-08-18  8: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=20030818084446.GI5732@marvin \
    --to=karoly.vegh@uta.at \
    --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