> On Mit, 2003-01-22 at 03:26, Brian J. Murrell wrote: > > On Mon, Jan 20, 2003 at 11:15:17PM +0100, Michel D�nzer wrote: > > > > > > No, but these warnings are special: > > > > > > (WW) RADEON(0): Restoring MEM_CNTL (00000000), setting to 29002901 > > > (WW) RADEON(0): Restoring CONFIG_MEMSIZE (02000000), setting to 02000000 > > > > Hey! I have these as well, exactly: > > > > (WW) RADEON(0): Restoring MEM_CNTL (00000000), setting to 29002901 > > (WW) RADEON(0): Restoring CONFIG_MEMSIZE (02000000), setting to 02000000 > > > > > Don't know if they could explain the problem though. > > > > Since they have something to do with memory, I am tending to think so, > > because one of the other symptoms of this problem is that even once I > > exit the Xserver, the console display is corrupt, as if video memory > > was being tampled on. > > Indeed, this is the most outstanding thing in common between both of > you. I suspect it could be related to int10. Something like Option > "NoInt10" and/or not loading the int10 module might work for testing > that, assuming the BIOS initializes the card on bootup.
I noticed there is a patch (CVS radeon_driver.c v1.72) a few weeks ago which enabled some __alpha__ path code for initializing MEM_CNTL etc. Not sure if the change is added intentionally or accidentally and if it's well tested on all supported cards. This doesn't seem to cause problem on all my cards. But it still looks suspicious. The code also writes to some MPP registers which don't even exist on Radeon chips. Hui > -- > Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > > _______________________________________________ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
