Thank you Markus, I checked boot.msg: <6>NFORCE2: IDE controller at PCI slot 0000:00:09.0 <6>NFORCE2: chipset revision 162 <6>NFORCE2: not 100%% native mode: will probe irqs later <4>NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround. <6>NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller So ther is no use for your patch. modprobe -v sis-agp runs without a problem. Henk Op maandag 5 juli 2004 12:19, schreef Markus Kohm:
Am Montag, 5. Juli 2004 10:01 schrieb Henk A.M. Weebers:
How can I find out?
You have a SiS Chipset, if loading of module sis_agp (either the original one or the patched one) is successfull und reports at /var/log/messages something like:
agpgart: Detected SiS 648 chipset
You may also read /var/log/boot.msg. If you have a SiS hid, e.g. reported as:
<4>Uncovering SIS963 that hid as a SIS503 (compatible=1) <6>Enabling SiS 96x SMBus.
or SiS IDE controller:
<6>SIS5513: IDE controller at PCI slot 0000:00:02.5 <6>SIS5513: chipset revision 0 <6>SIS5513: not 100%% native mode: will probe irqs later <6>SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller
You may also have SiS-chipset for AGP.
BTW: module loading can be done using:
modprobe -v sis_agp done whithout problems!
You should be root to do this. You may also try lsmod to find out, if sis_agp was loaded.
But:
I wonder if this patch can do some harm or good on my ASUS A7N8X-E Deluxe (nforce chipset)
I don't know, which is the valid agp modules for this.
Gruß Markus