On Fri, 8 Oct 2004 14:07:20 -0700, Nathan Olberding <[EMAIL PROTECTED]> wrote: > I've tried the drm from CVS (which wouldn't compile), both savage snapshots from > Felix's site, and the os-support/linux one from the 6.8.1 release (which I'm not > sure actually supports DRI). Is there another? Should I retry CVS? >
the one from xorg 6.8.1 in xc/extras/drm/linux should work. you can build it against whatever kernel you like. do all of the ones you've tried oops? > Side note: I recompiled my kernel without VESA Framebuffer support and copied it > over my current kernel. On rebooting, I got a blank screen. Now I know why I kept > the kernel that shipped with the distro! you may need to compile in support for vga console. Alex > > > > -----Original Message----- > From: Alex Deucher [mailto:[EMAIL PROTECTED] > Sent: Friday, October 08, 2004 1:48 PM > To: Nathan Olberding > Subject: Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar > > On Fri, 8 Oct 2004 13:42:07 -0700, Nathan Olberding > <[EMAIL PROTECTED]> wrote: > > So if I recompile the kernel without fb support, DRI might work? > > > > And for clarity, this'll take away my beautiful 1024x768 text console, which I > > almost solely use for typing "startx" and trying to get DRI to work, and leave me > > with a 640x480-or-whatever text console, right? > > > > That'll just fix the mtrr problem, but the drm will still oops. you > can also fix the mtrr problem by manually removing the mtrr added by > vesafb. mtrrs will have a minimal affect on performance however. you > should still be able to get direct rendering even if mtrrs aren't set > up right. I think your best bet is to try a new drm. > > Alex > > > > > > > -----Original Message----- > > From: Alex Deucher [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 08, 2004 1:30 PM > > To: Vladimir Dergachev > > Cc: Nathan Olberding; [EMAIL PROTECTED] > > Subject: Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar > > > > 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
