sero@homer:~ $ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 8500 DDR x86/MMX/3DNow!/SSE
OpenGL version string: 1.3 (X4.3.0-3.7.0)

sero@homer:~ $ glxgears
10500 frames in 5.0 seconds = 2100.000 FPS
11272 frames in 5.0 seconds = 2254.400 FPS
11272 frames in 5.0 seconds = 2254.400 FPS



you guys are all getting afferos from me, big time!

here is the configuration:
agp: built in
ati: module
nvidia: module (w/boot errors )

dri: built in
ati: module

mtrr: built in

i don't know what did it, but before i changed the agp from a module to built in, i *wasn't* getting the nvidia errors. then right after i changed it to built in, i started getting the errors. but now it works, so i guess i'll just live with them.

can't thank you guys enough -- everything seems sharper and clearer (probably my imagination) but moving windows around the screen is *definitely* smoother, and i'm sure i'll notice more improvements as i go along.

now on to the MBR problem.

thanks!

Awesome!!! Good work Hooper...and congratulations synaptical!

it's very weird. what you said in first paragrph is correct: with agpgart built in and chipset as module, the chipset wouldn't load but fglrx would (through rc.modules). i haven't tried it with fglrx commented out of rc.modules yet to see if it autoloads.

i put /sbin/modprobe nvidia_agp in rc.modules right under fglrx, and that's when it started working. but i just commented it out to see what would happen, and i am still getting the ATI drivers. so i really don't know what's going on -- and i don't get why i am getting the nvidia_agp error at boot, either. that is built in as a module, so why would the error say it failed to load it b/c it was built into the kernel? something is wrong there, it seems to me. well, i am not going to question it too much, i'm just glad it's finally working, but in case anyone else has a major problem like i had, it would be good to know exactly what fixed it. thanks again, everyone, great work!

WooooHOoo.... Yeah..... Su...p...er.....

Contrats!!

Now tweak out your monitor settings (modelines), get tux, and slide down some hills!!! Weeeeee...

Good Work all.


PS.... backup your config!!

Hooper

Hmmm...I have an idea. You know what works at this point, so make a note of it. Try this...

Don't load anything with rc.modules (as far as agpgart, fglrx, chipset-agp). Just boot, log in, then startx. Then do lsmod and see if all of the modules loaded.
Or...
Don't load fglrx before nvidia-agp...this will cause errors because you already told fglrxconfig to use the external agpgart...so when fglrx loads, it will try to load agpgart, which in turn should load nvidia-agp.

With what you described, I believe you are loading nvidia-agp, then fglrx (which will try to load it again) thus the errors.

If none of this clears it up, just go back to how you have it now.

The bright side? Well, no kernel recompile...for now

/sbin/modprobe nvidia_agp in rc.modules right under fglrx

You obviously have your nvidia_agp loaded as a module. No problem here as long as you load it via the /etc/rc.d/rc.modules.

Again, just happy you have some frame rate. Don't forget to tweak on the modelines. I get a real pretty desktop with this card.

Thanks DaOne.

okay, i took out fglrx from rc.modules, and now there's nothing pertaining to agpgart, chipset, etc. in there. fglrx loads when i start X, but nvidia_agp is loaded before that, and i still get the chipset errors at boot. i understand that it's mostly cosmetic, though i would like to find out what's calling it. i searched through all the rc.d files, but i didn't find anything.

not a huge deal, but if anyone comes across it, please post.

no, it's not loading through rc.modules. it's a mystery where it's loading from.

what are the modelines?

I see...so /sbin/modprobe nvidia-agp is still uncommented in rc.modules? If so # it. Like I said...if you load nvidia-agp before fglrx, nvidia-agp will try to load again with fglrx. So comment fglrx, nvidia-agp, and agpgart in rc.modules, and I am willing to bet that all modules will load in the proper order upon startx.
If you need to load them before startx (if x fails to start), try to just load fglrx...or load agpgart, then fglrx, or agpgart, then nvidia-agp, then fglrx. The order in which they load does matter.

post baleeted...

didn't read far enough, email telling me new posts had been made took me too far back. darn my inattentiveness.

okay, i'll remove it here, too sarahan.

DaOne: no references to nvidia in rc.modules at all. i already had commented it out, and when it worked with it commented out, i removed it totally. likewise for fglrx and agpgart: both commented out.

If you have the correct modelines and video display raster setup, you can get a pretty defined picture. If not set correctly for your display you'll get scrollies, artifacting, etc... especially with the ATI cards.

Here are some examples...

Section "Monitor"
Identifier "Monitor0"
HorizSync 30-115
VertRefresh 50-160
Option "DPMS"

# === mode lines based on GTF ===
# VGA @ 100Hz
# Modeline "640x480@100" 43.163 640 680 744 848 480 481 484 509 +hsync +vsync
etc... etc....

vendorname "Samsung"
modelname "SyncMaster 1100P Plus"
ModeLine "1024x768/85Hz" 98.9 1024 1056 1216 1408 768 782 788 822 -HSync -VSync
EndSection
=====

Of course your monitor/vidcard setup will be determined by your make and model. There is a modeline generator on the web you can use if you cannot determine the proper modes. You might also verify that X defines your particular monitor. This one is not supported or listed and I had to manually configure it. Yours may be fully supported by X with proper modelines. Just verify your video setup etc...

=====

Not sure what the deal is with the loading of modules if they are remmed. Just backup your files and go through your dmesg tinkering with the related errors.
It's either compiled within the kernel, or it's loading as a kernel module. Either way.... now you have it working, you should be able to figure out where the remaining issues are. If you decide to recompile or change files, just remember to back them up first... Wouldn't want to lose your fixes. That would be a bummer.

======

Ok...well at least it works for now. Not sure why you get the error, but like I said, it doesn't hurt...just one of those "ugly" things.

installing tux racer:

checking whether glx.h defines glXGetProcAddressARB... no
configure: error: Your copy of glx.h is out of date. You can get
a more recent copy from the latest Mesa distribution (http://mesa3d.sourceforge.net).



do i risk it?

Hmmm. Now you're pushing it.

Eh,,, Don't be messing with those files. SCO ownes the IP on them.. Lol...
Hell they can have mesa... ..just joking.