I am having stability problems with my R5A30.2 implementation and from what I've read there are some chipsets that do better with the NVAGP module (vs. the AGPGART module). Unfortunately, my motherboard uses the SIS chipset I tried adding "noagp" to /etc/lilo.conf, executing "lilo" and rebooting, but I am still getting the following in /var/log/messages:



Thanks for any help you can provide.

Marc

cd /lib/modules
find . -type f -name agpgart.ko -exec mv "{}" "{}".old ";" -ls

================

this will find the module and rename it to agpgart.ko.old

There is a correct way to keep the module from loading though!
Check your /etc/modules.conf to see if all you have to do is change an
alias..

Mac, thanks for the pointer. Renaming agpgart.ko seems to have done the trick and things seem to be working. I need to run for a few days to see if it really resolves my stability issue, but "modprove -l" now shows that agpgart isn't loaded and "nvdia-agp" is loaded. I do have a follow up question. I tried to comment out "agpgart" from "/etc/modules" instead of doing the rename, but that action does not apper to have stopped the load. Any thoughts as to why that didn't work? Also, I am now getting the following errors in /var/log/messages:


It doesn't appear to cause any problems -- I'm guessing because nvidia is now loading it's own AGP driver when I start "gdm", but it would be nice to clean this up. Any thoughts on how I can eliminate this noise? Thanks!

Marc

As you can see sis-agp.ko is not loading. It may need agpgart.ko, if it was loading before
but is now not.

Rename it as well, to prevent it from tring to load and the sis_agp noise in /var/log/messages
will stop..

Not sure not why editing /etc/modules didn't work maybe agpgart.ko is being pulled in by
the sis_agp load?

Mac, thanks for the reply. I renamed all of the ".ko" files to ".ko.orig", with the exception of the nvidia file, and now I don't have any errors. The next big question will be to see if using nvidia's agp driver really stabalizes the system. I'll know in a few days.

Thanks for the great help!

marc

I was able to prevent agpgart from loading. But I'm not able to get nvagp to load.

modprobe nvidia gives me:

FATAL: Error inserting nvidia (/lib/modules/2.6.17-chw-8/kernel/drivers/video/nvidia.ko): Unknown symbol in module, or unknown parameter (see dmesg)

dmesg gives me:

intel_agp: Unknown symbol agp_bridge
intel_agp: Unknown symbol agp_free_key
intel_agp: Unknown symbol global_cache_flush
intel_agp: Unknown symbol agp_generic_enable
intel_agp: Unknown symbol agp_generic_insert_memory
intel_agp: Unknown symbol agp_generic_destroy_page
intel_agp: Unknown symbol agp_off
intel_agp: Unknown symbol agp_remove_bridge
intel_agp: Unknown symbol agp_generic_mask_memory
intel_agp: Unknown symbol agp_create_memory
intel_agp: Unknown symbol agp_generic_alloc_by_type
intel_agp: Unknown symbol agp_generic_free_by_type
intel_agp: Unknown symbol agp_alloc_bridge
intel_agp: Unknown symbol agp_add_bridge
intel_agp: Unknown symbol agp_generic_remove_memory
intel_agp: Unknown symbol agp_generic_create_gatt_table
intel_agp: Unknown symbol agp_generic_free_gatt_table
intel_agp: Unknown symbol agp_generic_alloc_page
intel_agp: Unknown symbol agp_put_bridge
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
nvidia: module license 'NVIDIA' taints kernel.
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release
nvidia: Unknown symbol agp_bind_memory
nvidia: Unknown symbol agp_enable
nvidia: Unknown symbol agp_backend_acquire
nvidia: Unknown symbol agp_bridges
nvidia: Unknown symbol agp_free_memory
nvidia: Unknown symbol agp_allocate_memory
nvidia: Unknown symbol agp_unbind_memory
nvidia: Unknown symbol agp_copy_info
nvidia: Unknown symbol agp_backend_release