https://bugzilla.kernel.org/show_bug.cgi?id=19002
--- Comment #4 from Duncan <1i5t5.dun...@cox.net> 2010-10-12 14:45:49 --- I seem to have missed a couple email update notifications... The status as of 2.6.36-rc7-149 (pulled a couple hours ago) is basically unchanged, if not slightly worse. Without the revert, I still can't get into X/KDE. The "slightly worse" is because I've updated to kde 4.5.2 now, and it won't take xorg.conf, section module, disable "dri", at all -- it crashes X instead, leaving me back at a KMS text mode command prompt. I tried with earlier kernels that worked before (with kde 4.5.1 and no dri), too, and it still failed, so that's NOT a kernel issue, but it does mean I have no working method of testing no-dri at all. I can get working dri on the old kernels (or the new one with that commit reverted), but can't test no-dri on any kernel, now. The last tested good kernel was 2.6.35, as I thought was plain based on the bugs I noted it was a followup to. I still get a working kernel with commit 44437579efca258e3c4a09f59838c8f933611990 reversed, basically, in drivers/gpu/drm/radeon/r600.c and etc, WREG32(R_005480_HDP_MEM_COHERENCY_FLUSH_CNTL, 0x1); instead of the if statements my hardware is obviously coming up on the wrong side of. FWIW, 2.6.35.4 and 2.6.35.7, which I tested from the stable series, have the same problem. I already mentioned that I'm running the latest kde 4.5.2, and you know my kernel is testing series. xorg-server, mesa, libdrm, and xf86-video-ati are equally updated; I'm currently running xorg-server 1.9.0.901 (1.9.1-rc1), tho I tested 1.9.0 as well, mesa 7.9, libdrm 2.4.22, and xf86-video-ati 6.13.2. gcc 4.5.1 is the current compiler, with a fresh full system rebuild a couple days ago, and I'm running glibc 2.12.1 (gentoo revision -r1). Some of those are updates from the original report back on bug #17702 which this is a clone of. Possibly complicating factors include AGP, and AMD 8000 chipset so including agpgart IOMMU taking up part of the AGP window. If all r7xx are affected, why on earth is it working for me with that commit reverted, and not working for me with it applied? Based on the fact that my Radeon 4650 card is quite new, I'm still wondering if, somehow, whatever problem that commit I'm reverting is supposed to fix doesn't apply to this card revision. Or perhaps it's a mixup with AGPGART. I did note one of the recent drm/radeon commits updated an ID to categorize it correctly, but the retail package labeling, the kernel, and the radeon manpage, all seem to agree that the hd4560 I bought should be an rv730, so it'd seem the ID is right. But the hardware sure doesn't like the stuff in that if statement I'm reverting, that's for sure, whatever the reason may be! Meanwhile, if you can come up with a patch to give you information a bit more useful, or if you just need more dmesg output (beyond what's posted to the original bug), just ask and I'll do what I can. I have been working some pretty crazy hours lately, however (in addition to those missed email notifications), the reason my followups haven't been as timely as I'd have liked. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
