Bug#378713:
On Thu, 2006-08-03 at 09:27 +0200, B. Zhang wrote: Hi, I have the same problem, but only for kernel 2.6.18-rc. $ grep agp /var/log/Xorg.0.log (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module (**) RADEON(0): agp_size : 0x10216858 (**) RADEON(0): agp_base : 0x10216858 debian testing/unstable powerpc on ibook G4 VGA compatible controller: ATI Technologies Inc M9+ 5C63 [Radeon Mobility 9200 (AGP)] (rev 01) Sorry for noise, I forgot module CONFIG_AGP_UNINORTH=m. It works for me now. Best regards, Bin Bin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378713:
Hi, I have the same problem, but only for kernel 2.6.18-rc. $ grep agp /var/log/Xorg.0.log (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module (**) RADEON(0): agp_size : 0x10216858 (**) RADEON(0): agp_base : 0x10216858 debian testing/unstable powerpc on ibook G4 VGA compatible controller: ATI Technologies Inc M9+ 5C63 [Radeon Mobility 9200 (AGP)] (rev 01) Bin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Tue, 2006-07-18 at 23:17 +0200, Laurent Bonnaud wrote: On Tue, 2006-07-18 at 17:44 +0200, Michel Dänzer wrote: Note that I don't think lsmod lists the modules in the order they were loaded. Also, the above message was written back when both radeon and agpgart were still monolithic modules. Now that they have both been split into core and backend modules, the safest bet is to make sure that both the agpgart and intel_agp modules are loaded before both the drm and radeon modules. Running modprobe -r radeon; modprobe radeon should achive this in your case. If restarting the X server after doing this still doesn't enable the DRI, please provide the kernel output. I did what you suggested (several times) and DRI is still disabled. Here are the kernel messages. As you can read, I use a standard Debian kernel. In the error messages at the end, the PID are those of the X servers. Yeah, these are just symptoms of the X driver not handling the failure condition as gracefully as it could. They're harmless. Now, it's odd that there isn't anything pertaining to your AGP bridge in the kernel output, and that lsmod shows intel_agp being unused. In my experience, intel_agp should generate output about the hardware it detects, and agpgart should increase the use count of intel_agp. What happens if you unload and reload intel_agp? At any rate, this looks like a kernel AGP issue rather than an X driver issue. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Wed, 2006-07-19 at 08:57 +0200, Michel Dänzer wrote: At any rate, this looks like a kernel AGP issue rather than an X driver issue. I forgot to mention that you may be able to enable the DRI with Option BusType PCI as a workaround, but performance probably won't be great. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#378713: The problem seems to be the kernel
I find a similar problem with my custom build 2.6.17 kernel. With the same setup, but using a 2.6.16 kernel, everything works, so it does seems like the kernel is guilty of this one. The 'BusType' workaround does seem to work on 2.6.17, but it quite a bit slower. Cheers, Carlos signature.asc Description: This is a digitally signed message part
Bug#378713: The problem seems to be the kernel
On Wed, 2006-07-19 at 11:28 -0400, Carlos Moffat wrote: I find a similar problem with my custom build 2.6.17 kernel. With the same setup, but using a 2.6.16 kernel, everything works, so it does seems like the kernel is guilty of this one. In my case the problem was there before kernel 2.6.17. -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Wed, 2006-07-19 at 09:31 +0200, Michel Dänzer wrote: I forgot to mention that you may be able to enable the DRI with Option BusType PCI as a workaround, but performance probably won't be great. Thank you for the tip ! I cannot test the speed ATM because I work remotely, but according to the X server log, DRI is now enabled. -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Wed, 2006-07-19 at 08:57 +0200, Michel Dänzer wrote: Now, it's odd that there isn't anything pertaining to your AGP bridge in the kernel output, and that lsmod shows intel_agp being unused. In my experience, intel_agp should generate output about the hardware it detects, and agpgart should increase the use count of intel_agp. What happens if you unload and reload intel_agp? Nothing is displayed. If I remove then reload both AGP modules, then I get this kernel message: Linux agpgart interface v0.101 (c) Dave Jones At any rate, this looks like a kernel AGP issue rather than an X driver issue. OK. Then I will reassign this bug to the kernel package and see what kernel maintainers say. Thanks for your comments ! -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
Dear kernel maintainers, could you please check if this bug is really a kernel problem ? -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Tue, 2006-07-18 at 16:19 +0200, Laurent Bonnaud wrote: Package: xserver-xorg-video-ati Version: 1:6.5.8.0-1 Severity: important Hi, since a few revisions of the xorg server, DRI does not work any longer on this system. The computer is equipped with this videocard: 01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01) and hardware accelerated DRI/DRM/OpenGL used to work perfectly. According to the log file, the problem seems to be missing AGP from the kernel: (WW) RADEON(0): [agp] AGP not available (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. (II) RADEON(0): [agp] You may want to make sure the agpgart kernel module is loaded before the radeon kernel module. However, AGP modules are loaded: # lsmod |grep agp intel_agp 21116 0 agpgart29864 2 drm,intel_agp and the radeon module is loaded afterwards (see below the output of lsmod). Note that I don't think lsmod lists the modules in the order they were loaded. Also, the above message was written back when both radeon and agpgart were still monolithic modules. Now that they have both been split into core and backend modules, the safest bet is to make sure that both the agpgart and intel_agp modules are loaded before both the drm and radeon modules. Running modprobe -r radeon; modprobe radeon should achive this in your case. If restarting the X server after doing this still doesn't enable the DRI, please provide the kernel output. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#378713: xserver-xorg-video-ati: DRI disabled because it cannot see AGP kernel interface
On Tue, 2006-07-18 at 17:44 +0200, Michel Dänzer wrote: Note that I don't think lsmod lists the modules in the order they were loaded. Also, the above message was written back when both radeon and agpgart were still monolithic modules. Now that they have both been split into core and backend modules, the safest bet is to make sure that both the agpgart and intel_agp modules are loaded before both the drm and radeon modules. Running modprobe -r radeon; modprobe radeon should achive this in your case. If restarting the X server after doing this still doesn't enable the DRI, please provide the kernel output. I did what you suggested (several times) and DRI is still disabled. Here are the kernel messages. As you can read, I use a standard Debian kernel. In the error messages at the end, the PID are those of the X servers. -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ Linux version 2.6.17-1-686 (Debian 2.6.17-4) ([EMAIL PROTECTED]) (gcc version 4.1.2 20060708 (prerelease) (Debian 4.1.1-8)) #1 SMP Mon Jul 17 12:45:08 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 000a (usable) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 3ff74000 (usable) BIOS-e820: 3ff74000 - 3ff76000 (ACPI NVS) BIOS-e820: 3ff76000 - 3ff97000 (ACPI data) BIOS-e820: 3ff97000 - 4000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fecf - fecf1000 (reserved) BIOS-e820: fed2 - fed9 (reserved) BIOS-e820: fee0 - fee1 (reserved) BIOS-e820: ffb0 - 0001 (reserved) 0MB HIGHMEM available. 1023MB LOWMEM available. found SMP MP-table at 000fe710 On node 0 totalpages: 262004 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 257908 pages, LIFO batch:31 DMI 2.3 present. ACPI: RSDP (v000 DELL ) @ 0x000feb90 ACPI: RSDT (v001 DELLWS 360 0x0008 ASL 0x0061) @ 0x000fd164 ACPI: FADT (v001 DELLWS 360 0x0008 ASL 0x0061) @ 0x000fd19c ACPI: SSDT (v001 DELLst_ex 0x1000 MSFT 0x010d) @ 0xfffc8d51 ACPI: MADT (v001 DELLWS 360 0x0008 ASL 0x0061) @ 0x000fd210 ACPI: BOOT (v001 DELLWS 360 0x0008 ASL 0x0061) @ 0x000fd27c ACPI: ASF! (v016 DELLWS 360 0x0008 ASL 0x0061) @ 0x000fd2a4 ACPI: DSDT (v001 DELLdt_ex 0x1000 MSFT 0x010d) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 5000 (gap: 4000:bec0) Built 1 zonelists Kernel command line: root=/dev/sda1 ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Detected 2793.443 MHz processor. Using pmtmr for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1030716k/1048016k available (1478k kernel code, 16660k reserved, 540k data, 164k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5592.05 BogoMIPS (lpj=11184110) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 4400 CPU: After vendor identify, caps: bfebfbff 4400 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Hyper-Threading is disabled CPU: After all inits, caps: bfebfbff 0080 4400 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09 Total
