2.6.19-rc6-rt9 - fails to compile
Hi! 2.6.19-rc6-rt9 fails to compile on my Dual Core Notebook with FC6. CHK include/linux/version.h CHK include/linux/utsrelease.h CC arch/i386/kernel/asm-offsets.s In file included from include/linux/time.h:7, from include/linux/timex.h:57, from include/linux/sched.h:50, from include/linux/module.h:9, from include/linux/crypto.h:21, from arch/i386/kernel/asm-offsets.c:7: include/linux/seqlock.h: In function '__read_seqretry': include/linux/seqlock.h:139: error: expected expression before 'do' In file included from include/linux/module.h:9, from include/linux/crypto.h:21, from arch/i386/kernel/asm-offsets.c:7: include/linux/sched.h: In function 'dequeue_signal_lock': include/linux/sched.h:1478: error: expected expression before 'do' make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 www.marcush.de/kernel/.config Regards, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.19-rc6-rt9 - fails to compile
Hi! 2.6.19-rc6-rt9 fails to compile on my Dual Core Notebook with FC6. CHK include/linux/version.h CHK include/linux/utsrelease.h CC arch/i386/kernel/asm-offsets.s In file included from include/linux/time.h:7, from include/linux/timex.h:57, from include/linux/sched.h:50, from include/linux/module.h:9, from include/linux/crypto.h:21, from arch/i386/kernel/asm-offsets.c:7: include/linux/seqlock.h: In function '__read_seqretry': include/linux/seqlock.h:139: error: expected expression before 'do' In file included from include/linux/module.h:9, from include/linux/crypto.h:21, from arch/i386/kernel/asm-offsets.c:7: include/linux/sched.h: In function 'dequeue_signal_lock': include/linux/sched.h:1478: error: expected expression before 'do' make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 www.marcush.de/kernel/.config Regards, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: Was there any differnces in the devices at 00:00.0 and 00:01.0 ? (host & pci bridges) Only the Host bridge line c0: With AGPGART: 00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0300 Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [c0] AGP version 3.0 00: de 10 e1 00 06 00 b0 00 a1 00 00 06 00 00 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 03 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00 40: 62 14 00 03 08 c0 c0 01 22 00 11 11 d0 00 00 00 50: 23 05 3f 00 03 00 00 00 00 00 00 00 00 00 00 00 60: 32 31 03 00 66 45 04 00 66 06 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 30 30 00 00 11 11 88 00 80: 13 88 88 00 c8 00 00 00 70 00 00 00 3f 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 07 00 00 00 66 00 66 00 00 00 00 00 00 00 00 00 c0: 02 00 30 00 1b 42 00 1f 01 00 00 00 ff ff ff ff d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 With NV_AGP: 00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0300 Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [c0] AGP version 3.0 00: de 10 e1 00 06 00 b0 00 a1 00 00 06 00 00 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 03 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00 40: 62 14 00 03 08 c0 c0 01 22 00 11 11 d0 00 00 00 50: 23 05 3f 00 03 00 00 00 00 00 00 00 00 00 00 00 60: 32 31 03 00 66 45 04 00 66 06 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 30 30 00 00 11 11 88 00 80: 13 88 88 00 c8 00 00 00 70 00 00 00 3f 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 07 00 00 00 66 00 66 00 00 00 00 00 00 00 00 00 c0: 02 00 30 00 1b 42 00 1f 02 03 00 00 ff ff ff ff d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: Was there any differnces in the devices at 00:00.0 and 00:01.0 ? (host pci bridges) Only the Host bridge line c0: With AGPGART: 00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0300 Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [c0] AGP version 3.0 00: de 10 e1 00 06 00 b0 00 a1 00 00 06 00 00 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 03 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00 40: 62 14 00 03 08 c0 c0 01 22 00 11 11 d0 00 00 00 50: 23 05 3f 00 03 00 00 00 00 00 00 00 00 00 00 00 60: 32 31 03 00 66 45 04 00 66 06 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 30 30 00 00 11 11 88 00 80: 13 88 88 00 c8 00 00 00 70 00 00 00 3f 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 07 00 00 00 66 00 66 00 00 00 00 00 00 00 00 00 c0: 02 00 30 00 1b 42 00 1f 01 00 00 00 ff ff ff ff d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 With NV_AGP: 00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) Subsystem: Micro-Star International Co., Ltd.: Unknown device 0300 Flags: bus master, 66Mhz, fast devsel, latency 0 Memory at d000 (32-bit, prefetchable) [size=128M] Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [c0] AGP version 3.0 00: de 10 e1 00 06 00 b0 00 a1 00 00 06 00 00 00 00 10: 08 00 00 d0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 00 03 30: 00 00 00 00 44 00 00 00 00 00 00 00 ff 00 00 00 40: 62 14 00 03 08 c0 c0 01 22 00 11 11 d0 00 00 00 50: 23 05 3f 00 03 00 00 00 00 00 00 00 00 00 00 00 60: 32 31 03 00 66 45 04 00 66 06 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 30 30 00 00 11 11 88 00 80: 13 88 88 00 c8 00 00 00 70 00 00 00 3f 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 07 00 00 00 66 00 66 00 00 00 00 00 00 00 00 00 c0: 02 00 30 00 1b 42 00 1f 02 03 00 00 ff ff ff ff d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Arjan van de Ven wrote: hmm I wonder.. .could you collect lspci -vxxx settings for the AGP device (lspci -vxxx gives you lots of devices, but only one is relevant) in both cases, maybe the difference between the two shows something useful... Hmmm...only the latency at the VGA card. With AGPGART: 01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 5 Memory at e000 (32-bit, non-prefetchable) [size=16M] Memory at d800 (32-bit, prefetchable) [size=128M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 00: de 10 31 03 07 00 b0 02 a1 00 00 03 00 20 00 00 10: 00 00 00 e0 08 00 00 d8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 05 01 40: 00 00 00 00 02 00 30 00 1b 0e 00 1f 00 00 00 00 50: 01 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00 60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 With NV_AGP: 01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 5 Memory at e000 (32-bit, non-prefetchable) [size=16M] Memory at d800 (32-bit, prefetchable) [size=128M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 00: de 10 31 03 07 00 b0 02 a1 00 00 03 00 f8 00 00 10: 00 00 00 e0 08 00 00 d8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 05 01 40: 00 00 00 00 02 00 30 00 1b 0e 00 1f 02 43 00 1f 50: 01 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00 60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Both complete output: http://www.marcush.de/bench/ Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Terence Ripperda wrote: > I wouldn't expect even falling back to pci dma would have this big of an > impact on 2d performance, but perhaps there's enough bus activity for > this to happen. Marcus, can you verify that you're actually using > agpgart in that situation? do you possibly have our XF86Config option > set to nvagp only? (with IOMMU compiled in or agpgart loaded, our driver > won't allow nvagp) you can verify whether agp is enabled with this > command when our driver is loaded and X is started up: No, IOMMU is now off, too. And I have always used nv_agp with: Option "NvAgp" "1" If the nvidia driver detects the kernel agpgart, it doesn't load nv_agp with a big message in the kernel log. I've just short tested it again: Doom3 with medium standard settings in [EMAIL PROTECTED]: agpgart: 58,1 frames nv_agp: 63,1 frames Its a lot in Doom3. (Simple) 2D test [EMAIL PROTECTED] with x11perf --> http://www.marcush.de/bench/ Same gcc, xorg 6.8.2, 2.6.11-rc3-bk8 kernel, patched (minion.de) 6629 nvidia drivers to run with newer 2.6.11-rcX kernel,... here was only nv_agp and agpgart the difference. In the past without an patched driver the same difference. And again using agpgart with GNOME under X and moving this thunderbird mail window or other bigger ones like mozille or firefox over an gnome-terminal pulls/draws a ca. 5cm shadow like field slowly after the main window. It seems so not fast enough writing to the screen, when moving. With nv_agp its really faster and you do not see this. Bad english... I know. ;) Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Terence Ripperda wrote: I wouldn't expect even falling back to pci dma would have this big of an impact on 2d performance, but perhaps there's enough bus activity for this to happen. Marcus, can you verify that you're actually using agpgart in that situation? do you possibly have our XF86Config option set to nvagp only? (with IOMMU compiled in or agpgart loaded, our driver won't allow nvagp) you can verify whether agp is enabled with this command when our driver is loaded and X is started up: No, IOMMU is now off, too. And I have always used nv_agp with: Option NvAgp 1 If the nvidia driver detects the kernel agpgart, it doesn't load nv_agp with a big message in the kernel log. I've just short tested it again: Doom3 with medium standard settings in [EMAIL PROTECTED]: agpgart: 58,1 frames nv_agp: 63,1 frames Its a lot in Doom3. (Simple) 2D test [EMAIL PROTECTED] with x11perf -- http://www.marcush.de/bench/ Same gcc, xorg 6.8.2, 2.6.11-rc3-bk8 kernel, patched (minion.de) 6629 nvidia drivers to run with newer 2.6.11-rcX kernel,... here was only nv_agp and agpgart the difference. In the past without an patched driver the same difference. And again using agpgart with GNOME under X and moving this thunderbird mail window or other bigger ones like mozille or firefox over an gnome-terminal pulls/draws a ca. 5cm shadow like field slowly after the main window. It seems so not fast enough writing to the screen, when moving. With nv_agp its really faster and you do not see this. Bad english... I know. ;) Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Arjan van de Ven wrote: hmm I wonder.. .could you collect lspci -vxxx settings for the AGP device (lspci -vxxx gives you lots of devices, but only one is relevant) in both cases, maybe the difference between the two shows something useful... Hmmm...only the latency at the VGA card. With AGPGART: 01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 5 Memory at e000 (32-bit, non-prefetchable) [size=16M] Memory at d800 (32-bit, prefetchable) [size=128M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 00: de 10 31 03 07 00 b0 02 a1 00 00 03 00 20 00 00 10: 00 00 00 e0 08 00 00 d8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 05 01 40: 00 00 00 00 02 00 30 00 1b 0e 00 1f 00 00 00 00 50: 01 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00 60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 With NV_AGP: 01:00.0 VGA compatible controller: nVidia Corporation NV35 [GeForce FX 5900] (rev a1) (prog-if 00 [VGA]) Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 5 Memory at e000 (32-bit, non-prefetchable) [size=16M] Memory at d800 (32-bit, prefetchable) [size=128M] Capabilities: [60] Power Management version 2 Capabilities: [44] AGP version 3.0 00: de 10 31 03 07 00 b0 02 a1 00 00 03 00 f8 00 00 10: 00 00 00 e0 08 00 00 d8 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 60 00 00 00 00 00 00 00 05 01 05 01 40: 00 00 00 00 02 00 30 00 1b 0e 00 1f 02 43 00 1f 50: 01 00 00 00 01 00 00 00 ce d6 23 00 0f 00 00 00 60: 01 44 02 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Both complete output: http://www.marcush.de/bench/ Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: > *shrug*, if the nvidia module is properly configured, it should make no difference at all. AGPGART operation isn't a performance critical thing, as the hardware does 99% of the work. Yes, that was also my opinion, but after using AGPGART, hmm. And it was on my last 32 bit FC2 systems with other hardware the same slow operations on the desktop. And I'm not alone, there are some nvnews.net linux forum users which report the same slow performance with AGPGART. Maybe the linux kernel AGPGART do not run well with the nVidia 2D acceleration renderer or the kernel driver and is a nvidia problem. http://www.marcush.de/Xorg.0.log Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: probably you have selected IOMMU, which is dependant on it. Yes, thanks. Sorry my fault. I had it not deactivated, arggg. This surprises me, especially considering the in-kernel nvidia-agp driver was actually written by NVidia. Are there any agp error messages in your dmesg / X log ? No warnings/errors in both logs. All clean. But switching/maximizing between tasks like firefox, thunderbird or a gnome-terminal is so slow, that you can see it how firefox/GTK+ theme is writing the GUI and the fonts slowly back. Minimizing is no more fun, like a fast slide-show. And that on a fast amd64 3200 with 1 GB RAM and a FX 5900XT. :( With the nVidia own nv_agp it appears directly in all apps, very fast under GNOME 2.8.1. Why, I do not know. Also game (opengl) performance is faster with the nv_agp, that I haven't used the kernel agp for months, now. Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: probably you have selected IOMMU, which is dependant on it. Yes, thanks. Sorry my fault. I had it not deactivated, arggg. This surprises me, especially considering the in-kernel nvidia-agp driver was actually written by NVidia. Are there any agp error messages in your dmesg / X log ? No warnings/errors in both logs. All clean. But switching/maximizing between tasks like firefox, thunderbird or a gnome-terminal is so slow, that you can see it how firefox/GTK+ theme is writing the GUI and the fonts slowly back. Minimizing is no more fun, like a fast slide-show. And that on a fast amd64 3200 with 1 GB RAM and a FX 5900XT. :( With the nVidia own nv_agp it appears directly in all apps, very fast under GNOME 2.8.1. Why, I do not know. Also game (opengl) performance is faster with the nv_agp, that I haven't used the kernel agp for months, now. Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to disable slow agpgart in kernel config?
Dave Jones wrote: *shrug*, if the nvidia module is properly configured, it should make no difference at all. AGPGART operation isn't a performance critical thing, as the hardware does 99% of the work. Yes, that was also my opinion, but after using AGPGART, hmm. And it was on my last 32 bit FC2 systems with other hardware the same slow operations on the desktop. And I'm not alone, there are some nvnews.net linux forum users which report the same slow performance with AGPGART. Maybe the linux kernel AGPGART do not run well with the nVidia 2D acceleration renderer or the kernel driver and is a nvidia problem. http://www.marcush.de/Xorg.0.log Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
How to disable slow agpgart in kernel config?
Hello, the agpgart backend is now always compiled in and selected with 2.6.11-rc3 x86_64. I can delete or disable it in the config, it is always back written. Is this the default future behaviour? The eg Nforce3 AGP is on a normal desktop so slow on 2D and also in 3D mode a lot slower and all nvidia kernel driver users can not more use the really faster nv_agp. Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
How to disable slow agpgart in kernel config?
Hello, the agpgart backend is now always compiled in and selected with 2.6.11-rc3 x86_64. I can delete or disable it in the config, it is always back written. Is this the default future behaviour? The eg Nforce3 AGP is on a normal desktop so slow on 2D and also in 3D mode a lot slower and all nvidia kernel driver users can not more use the really faster nv_agp. Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.11-rcX / 2.6.10-ac9 kernel do not more boot SATA disk on amd64
Hello, I can not more boot any kernel >=2.6.11-rcX also >=2.6.10-ac9 and latest bk6. But I have here Alan Cox 2.6.10-ac8 and Cons 2.6.10-ck5 running and booting fine without any problems. But now all kernel versions after that failed (with the same config tried) with: mount: error 6 mounting ext3 ... umount /initrd/dev failed ... on my Fedora Core 3 x86_64. The Fedora devel kernel also failed booting (2.6.11-rcX-bkX included and badly the SCSI support and all other as modules configured, what a shame... ;) . I've tried compiling all needed drivers like libata, sata_nv, SCSI support, ext3 (my root / fs),... in the kernel and also the most as always as modules with an initrd. With and wo "noapic", direct device names to grub given and always no chance to get all at the top named kernel to boot. What was there changed in this time? Or can anybody tell me, what I'm doing here wrong? :-( Hardware: nForce3 250Gb MSI K8N Neo Mainboard, Samsung SATA 80GB disk, / fs on ext3, x86_64 kernel/Fedora and gcc 3.4.3. config: http://www.marcush.de/config-2.6.11-rc3 Greetings, Marcus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.11-rcX / 2.6.10-ac9 kernel do not more boot SATA disk on amd64
Hello, I can not more boot any kernel =2.6.11-rcX also =2.6.10-ac9 and latest bk6. But I have here Alan Cox 2.6.10-ac8 and Cons 2.6.10-ck5 running and booting fine without any problems. But now all kernel versions after that failed (with the same config tried) with: mount: error 6 mounting ext3 ... umount /initrd/dev failed ... on my Fedora Core 3 x86_64. The Fedora devel kernel also failed booting (2.6.11-rcX-bkX included and badly the SCSI support and all other as modules configured, what a shame... ;) . I've tried compiling all needed drivers like libata, sata_nv, SCSI support, ext3 (my root / fs),... in the kernel and also the most as always as modules with an initrd. With and wo noapic, direct device names to grub given and always no chance to get all at the top named kernel to boot. What was there changed in this time? Or can anybody tell me, what I'm doing here wrong? :-( Hardware: nForce3 250Gb MSI K8N Neo Mainboard, Samsung SATA 80GB disk, / fs on ext3, x86_64 kernel/Fedora and gcc 3.4.3. config: http://www.marcush.de/config-2.6.11-rc3 Greetings, Marcus - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/