Am Dienstag, den 20.02.2007, 20:10 +0100 schrieb Christian Neumair: > > Did you card work flawlessly with dri enabled under xorg ? > > No, it doesn't. > > The screen turns black, the computer itself does not seem to lock up, > but according to the Xorg log (attached, gzipp'd) everything seems to > go > fine. > > My "messages" log has: > > Feb 20 19:39:31 localhost kernel: [17179959.672000] [drm] Used old pci > detect: framebuffer loaded > > > Feb 20 19:39:54 localhost kernel: [17179982.140000] mtrr: > 0xc0000000,0x8000000 overlaps existing 0xc0000000,0x4000000 > (2 or 3 times) > Feb 20 19:40:22 localhost kernel: [17180009.848000] > <3>[drm:drm_release] *ERROR* Device busy: 1 0 > > (this is in the log every 20 seconds) > > But maybe this is an expected result if I bring up the whole system at > runtime? I run vesafb, modprobe drm and radeon and then just bring up > the X server. Do these FBs interfere somehow?
I didn't run vesafb, I actually ran radeonfb. The locking doesn't happen and X.Org can be launched fine when just using vesa (by appending video="vesa" to the kernel line). I'm just dropping these lines to make it simpler for people desperately grepping mail archives to get their locked X.Org server (possibly on Ubuntu/Edgy) to run. I suppose this is really an unrelated readeonfb issue, the EGL/dri driver still doesn't work though. I'll further investigate it. -- Christian Neumair <[EMAIL PROTECTED]> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
