I've never been sure which bugzilla to put these on. So I'm putting it on both : ) It boots and does mesa swrast, but fails to do dri/kms. It used to be able to do dri. (basically latest f11) kernel-PAE-2.6.29.4-167.fc11.i686 mesa-dri-drivers-7.5-0.14.fc11.i586 xorg-x11-drv-ati-6.12.2-14.fc11.i586 xorg-x11-server-Xorg-1.6.1.901-1.fc11.i586 [drm] Initialized drm 1.1.0 20060810 radeon 0000:01:05.0: power state changed by ACPI to D0 ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 10 radeon 0000:01:05.0: PCI INT A -> Link[LNK0] -> GSI 10 (level, low) -> IRQ 10 [drm] Detected VRAM RAM=65536K, accessible=65536K, BAR=131072K agpgart-ati 0000:00:00.0: AGP 2.0 bridge agpgart-ati 0000:00:00.0: putting AGP V2 device into 4x mode radeon 0000:01:05.0: putting AGP V2 device into 4x mode [drm] setting agp_base to d4000000 [drm] setting agp_location to d4000000 [drm:drm_agp_bind_ttm] *ERROR* AGP Bind memory failed [drm:drm_ttm_bind] *ERROR* Couldn't bind backend. [drm:drm_buffer_object_validate] *ERROR* Failed moving buffer. ea46ca00 256 2000031 10000a0 [drm:radeon_alloc_gart_objects] *ERROR* failed to allocate ring - most likely an AGP driver bug radeon 0000:01:05.0: PCI INT A disabled radeon: probe of 0000:01:05.0 failed with error -22 00:00.0 Host bridge: ATI Technologies Inc RS200/RS200M AGP Bridge [IGP 340M] (rev 02) Flags: bus master, 66MHz, medium devsel, latency 64 Memory at d4000000 (32-bit, prefetchable) [size=64M] Memory at d0007000 (32-bit, prefetchable) [size=4K] Capabilities: [a0] AGP version 2.0 Kernel driver in use: agpgart-ati 00:01.0 PCI bridge: ATI Technologies Inc PCI Bridge [IGP 340M] (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 99 Bus: primary=00, secondary=01, subordinate=01, sec-latency=68 I/O behind bridge: 00009000-00009fff Memory behind bridge: d0300000-d03fffff Prefetchable memory behind bridge: d8000000-dfffffff http://smolt.fedoraproject.org/client/show/?uuid=pub_6e4de3c3-e060-4f62-8e91-4ea96d25939d
fixed, rhbz closed. thanks.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.