On Fri, 8 Oct 2004 16:26:58 -0400 (EDT), Vladimir Dergachev <[EMAIL PROTECTED]> wrote: > > > On Fri, 8 Oct 2004, Alex Deucher wrote: > > > On Thu, 07 Oct 2004 07:11:42 -0700, Nathan Olberding > > <[EMAIL PROTECTED]> wrote: > >> dmesg output is attached, as well as /var/log/messages. I can feel it, > >> I'm gonna gets me my DRI! (maybe) > > > > [snip..] > > >> vesafb: framebuffer at 0xd0000000, mapped to 0xe680a000, size 1536k > >> vesafb: mode is 1024x768x8, linelength=1024, pages=40 > >> vesafb: protected mode interface info at c000:841f > >> vesafb: scrolling: redraw > >> fb0: VESA VGA frame buffer device > [snip..] > > >> agpgart: Detected VIA Apollo Pro266 chipset > >> agpgart: Maximum main memory to use for agp memory: 533M > >> agpgart: AGP aperture is 64M @ 0xe0000000 > >> mtrr: no more MTRRs available > >> mtrr: no more MTRRs available > >> mtrr: no more MTRRs available > >> mtrr: no more MTRRs available > >> mtrr: 0xd0000000,0x1000000 overlaps existing 0xd0000000,0x100000 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This is caused by vesa framebuffer driver - try running a kernel without > it.
yeah, but messed up mtrrs wouldn't be causing the oops in the drm would they? Alex > > best > > Vladimir Dergachev > ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
