On Sat, 2005-02-26 at 00:30 +0100, Olaf Hering wrote: > On Fri, Feb 25, Olaf Hering wrote: > > > On Fri, Feb 25, Olaf Hering wrote: > > > > > On Fri, Feb 25, James Simmons wrote: > > > > > > > > > > > > cfb_imageblit(320) dst1 fa51a800 base e0b80000 bitstart 1999a800 > > > > > fast_imageblit(237) s daea4000 dst1 fa51a800 > > > > > fast_imageblit(269) j 1 fa51a800 0 > > > > > Unable to handle kernel paging request at virtual address fa51a800 > > > > > > > > > > is bitstart incorrect or is the thing just not (yet) mapped? > > > > > > > > Looks like the screen_base is not mapped to. > > > > > > rc3 worked ok, rc4 does not. testing the -bk snapshots now. > > > > bk8 works, bk9 breaks, it contains the radeonfb update. > > it works ok if the driver is compiled into the kernel. > > > modedb = rinfo->mon1_modedb; passes some shit to fb_find_mode() which > kills my screen(1) when DPRINTK is enabled. it dies because bitstart > relies on xres_virtual which is 0xcccccc or whatever.
I think the problem is that you have totally bogus EDID data coming from DDC. I'm still curious what makes a difference between module and built-in. Either we try to set a bogus mode, or we just fail setting a mode at all and fbdev doesn't deal with that properly. Did you try plugging a different monitor ? Also, do you have output with a recent X.org (6.8.2 for example) ? Can you send me that log too ? Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
