From: Jan Dittmer <j.dittmer@portrix.net>
To: linux-kernel@vger.kernel.org
Subject: agpgart, nforce2, radeon and agp fastwrite
Date: Sat, 12 Jul 2003 17:51:42 +0200 [thread overview]
Message-ID: <3F102E8E.4030507@portrix.net> (raw)
Hi,
just took me half a hour to figure out. On nforce2 you have to disable
agp fastwrites, otherwise X locks hard on startup with the following
(from serial console).
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected NVIDIA nForce2 chipset
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: AGP aperture is 128M @ 0xd0000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
agpgart: Putting AGP V2 device at 0000:02:00.0 into 2x mode
No response, neither by ping, nor sysrq or anything else. just dead.
I already defined AGP_DEBUG in agp.h but that doesn't make it noisier.
# lspci -v
02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QL
[Radeon )
Subsystem: Hercules: Unknown device 0000
Flags: bus master, stepping, 66Mhz, medium devsel, latency 32,
IRQ 5
Memory at d8000000 (32-bit, prefetchable) [size=128M]
I/O ports at a000 [size=256]
Memory at e2000000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
Without AGP Fastwrites turned on, it all works wonderful. Just if
anybody encounters the same problem.
Mainboard is nForce2 based, graphics is radeon 8500le (R200).
Jan
--
Linux rubicon 2.5.75-mm1-jd1 #2 SMP Fri Jul 11 12:49:37 CEST 2003 i686
next reply other threads:[~2003-07-12 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 15:51 Jan Dittmer [this message]
2003-07-12 20:26 ` agpgart, nforce2, radeon and agp fastwrite Dave Jones
2003-07-12 21:10 ` Jan Dittmer
2003-07-12 21:17 ` Dave Jones
2003-07-13 13:37 ` Jamie Lokier
2003-07-13 20:35 ` Rahul Karnik
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 10:17 Jaakko Niemi
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=3F102E8E.4030507@portrix.net \
--to=j.dittmer@portrix.net \
--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