Description of problem: After updating to 2.6.17-1.2139_FC5 I am noticing some issues with my ATI 9800 pro card. Not sure if the xorg ati driver needs updating or not but including my message log below: Jun 26 21:07:29 localhost kernel: [drm] Initialized radeon 1.24.0 20060225 on minor 0 Jun 26 21:07:29 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jun 26 21:07:29 localhost kernel: agpgart: Badness. Don't know which AGP mode to set. [bridge_agpstat:1f000a0a vga_agpstat:ff00021b fell back to:- bridge_agpstat:1f000208 vga_agpstat:ff00021b] Jun 26 21:07:29 localhost kernel: agpgart: Bridge couldn't do AGP x4. Jun 26 21:07:29 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode Jun 26 21:07:29 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode Jun 26 21:07:29 localhost kernel: [drm] Setting GART location based on old memory map Jun 26 21:07:29 localhost kernel: [drm] Loading R300 Microcode Jun 26 21:07:29 localhost kernel: [drm] writeback test failed Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
same issue with the 2.6.17-1.2145_FC5 kernel, however if I change my AGP mode to 4x from 8x in my bios I get a successful boot.
same issue with 2.6.17-1.2157_FC5, Jul 23 21:05:54 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jul 23 21:05:54 localhost kernel: agpgart: Badness. Don't know which AGP mode to set. [bridge_agpstat:1f000a0a vga_agpstat:ff00021b fell back to:- bridge_agpstat:1f000208 vga_agpstat:ff00021b] Jul 23 21:05:54 localhost kernel: agpgart: Bridge couldn't do AGP x4. Jul 23 21:05:54 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode Jul 23 21:05:54 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode Jul 23 21:05:54 localhost kernel: [drm] Setting GART location based on new memory map Jul 23 21:05:54 localhost kernel: [drm] Loading R300 Microcode Jul 23 21:05:54 localhost kernel: [drm] writeback test failed
bumping up sev to high per bbrock recommendation
*** Bug 197346 has been marked as a duplicate of this bug. ***
I think I've just got to the bottom of this. I've rewritten a bunch of this code upstream, but I want it to survive a trip through Andrew's -mm tree before it goes into the Fedora kernel, as this is core code that affects every AGP driver.
for me DRM won't load if i use a Fedora kernel. I use my own custom config and compile my own kernel, and i build in dri driver for my ATI X300 mobility on Dell Inspiron 9300 and it will load, full support doesn't seem complete though as i tried a 3d game - UT2004 and it loaded but was slow and nearly unresponsive.
I think this is actually a (trivial) bug in xorg-x11-drv-ati, not a kernel bug at all. Look at this code in xf86-video-ati-6.5.8.0/src/radeon_dri.c: if ((mode & RADEON_AGPv3_MODE) && (INREG(RADEON_AGP_STATUS) & RADEON_AGPv3_MODE)) { switch (info->agpMode) { case 8: mode |= RADEON_AGPv3_8X_MODE; case 4: default: mode |= RADEON_AGPv3_4X_MODE; mode |= RADEON_AGPv3_8X_MODE; should have a break; after it, otherwise it sets *both* RADEON_AGPv3_8X_MODE and RADEON_AGPv3_4X_MODE, which isn't good.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
This bug has been mass-closed along with all other bugs that have been in NEEDINFO state for several months. Due to the large volume of inactive bugs in bugzilla, this is the only method we have of cleaning out stale bug reports where the reporter has disappeared. If you can reproduce this bug after installing all the current updates, please reopen this bug. If you are not the reporter, you can add a comment requesting it be reopened, and someone will get to it asap. Thank you.