From: "Michael Guntsche" <m.guntsche@epitel.at>
To: <linux-kernel@vger.kernel.org>
Subject: AGPGART problems with VIA KX133 chipsets under 2.2.18/2.4.0
Date: Tue, 23 Jan 2001 08:33:25 +0100 [thread overview]
Message-ID: <NDBBJOKGIPCDBEEFHNFPGECPCAAA.m.guntsche@epitel.at> (raw)
Hello all,
While playing around with the agpgart module I noticed the following strange
behaviour.
The hardware in question is an Asus K7V with the KX133 chipset and has been
tested on both 2.4.0 and 2.2.18 kernels.
The output below is just from insmod,rmmod,insmod agpgart without starting
X.
insmod agpgart for the first time:
Jan 22 23:17:10 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann
Jan 22 23:17:10 deepblue kernel: agpgart: Maximum main memory to use for agp
memory: 204M
Jan 22 23:17:10 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
Jan 22 23:17:10 deepblue kernel: agpgart: AGP aperture is 64M @ 0xe4000000
^-------
rmmod, insmod agpgart:
Jan 22 23:17:16 deepblue kernel: Linux agpgart interface v0.99 (c) Jeff
Hartmann
Jan 22 23:17:16 deepblue kernel: agpgart: Maximum main memory to use for agp
memory: 204M
Jan 22 23:17:16 deepblue kernel: agpgart: Detected Via Apollo Pro chipset
Jan 22 23:17:16 deepblue kernel: agpgart: AGP aperture is 64M @ 0x4000000
^------
Apparently AGP isnt working afterwards.
Someone know what might be causing this?
If you need more information or a want me to help debug this issue further
dont hestitate to tell me.
Since Im not subscribed to the list, please CC any replies to me directly.
Cheers,
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-23 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 7:33 Michael Guntsche [this message]
2001-01-23 16:51 ` Jeff Hartmann
2001-01-23 17:58 ` [Dri-devel] " Markus Hadwiger
2001-01-23 20:34 ` Jeff Hartmann
2001-01-23 17:05 ` Wayne Whitney
2001-01-31 0:55 ` Bob_Tracy
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=NDBBJOKGIPCDBEEFHNFPGECPCAAA.m.guntsche@epitel.at \
--to=m.guntsche@epitel.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
all inboxes | Powered by JetHome®