report: success with agp_try_unsupported=1
dear all,
i just built a system:
1.3GHz amd athlon
epox 8kha ddr motherboard
via kt266 (vt8366, vt8233)
768MB ddr ram
radeon QD with 64MB video buffer, tvio
i enabled agpgart, and got the message:
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: Unsupported Via chipset (device id: 3099), you might want to try
agp_try_unsupported=1.
agpgart: no supported devices found.
[drm] Initialized radeon 1.1.1 20010405 on minor 0
i rebuilt the kernel with agpgart built as a module. rebooted. loaded the agp module with:
insmod /usr/src/linux-2.4.9/drivers/char/agp/agpgart.o agp_try_unsupported=1
loaded the radeon driver with:
insmod /usr/src/linux-2.4.9/drivers/char/drm/radeon.o
this was successful -- DRI was enabled when i started X (and i played quake3 to reward myself).
i read that success with agp_try_unsupported=1 should be reported here, so i'm reporting it. please feel free to ask further questions if you want to know about my hardware.
i do have 2 questions:
1. modprobe didn't seem to know where agpgart.o and radeon.o lives, so i had to resort to insmod. is there a way of telling modprobe where to look for modules?
2. i recompiled the kernel but built agpgart in rather than loading it as a module. i then inserted the following line into /etc/lilo.conf:
append="agp_try_unsupported=1"
but it didn't seem to work. someone told me that to get agp work to work for my system, agpgart MUST be built as a module and you MUST pass it the argument agp_try_unsupported=1. in other words, you can't build it into the kernel and pass the argument as a kernel parameter at boot time.
is that true?
please cc replies to [email protected].
thanks guys!
pete
Signature · 3 lines
"You may not use the Software in connection with any site that disparages
Microsoft, MSN, MSNBC, Expedia, or their products or services ..."
-- Clause from license for FrontPage 2002Quoted 11 lines · Peter Jay Salzman
i just built a system:
1.3GHz amd athlon
epox 8kha ddr motherboard
via kt266 (vt8366, vt8233)
768MB ddr ram
radeon QD with 64MB video buffer, tvioi enabled agpgart, and got the message:
Quoted 6 lines
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: Unsupported Via chipset (device id: 3099), you might want to try
agp_try_unsupported=1.
agpgart: no supported devices found.
[drm] Initialized radeon 1.1.1 20010405 on minor 0
I will write a patch for this to add VIA KT266 support (so you don't need to do the agp_try_unsupported=1 mess, it will be supported natively). Although, the patch is going to be against 2.4.10.
I'll send it out in a sec, start downloading 2.4.10 :)
Quoted 8 lines
2. i recompiled the kernel but built agpgart in rather than loading it as a module. i then inserted the following line into
/etc/lilo.conf:append="agp_try_unsupported=1"
but it didn't seem to work. someone told me that to get agp work to work for my system, agpgart MUST be built as a module and you MUST pass it the argument agp_try_unsupported=1. in other words, you can't build it into
Yes, I believe this is a bug. Maybe I should take a look at it...
agpgart doesn't read the command line, or not correctly, or something.
Signature · 3 lines
Robert M. Love rml at ufl.edu rml at tech9.net
Quoted 3 lines · Robert Love
I will write a patch for this to add VIA KT266 support (so you don't need to do the agp_try_unsupported=1 mess, it will be supported natively). Although, the patch is going to be against 2.4.10.
I take that back, no I won't :)
I think support was added during 2.4.10-pre from a merge with Alan's tree.
Upgrade to 2.4.10 and see if not it works.
Signature · 3 lines
Robert M. Love rml at ufl.edu rml at tech9.net
Quoted 3 lines · Peter Jay Salzman
1. modprobe didn't seem to know where agpgart.o and radeon.o lives, so i had to resort to insmod. is there a way of telling modprobe where to look for modules?
Probably old modutils, see Documentation/Changes and check your versions.