Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar

2004-10-08 Thread Vladimir Dergachev
mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: 0xd000,0x100 overlaps existing 0xd000,0x10 This is caused by vesa framebuffer driver - try running a kernel without it.

Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar

2004-10-08 Thread Alex Deucher
ED] > 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 m

Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar

2004-10-08 Thread Alex Deucher
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 i

Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar

2004-10-08 Thread Vladimir Dergachev
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 0xd000, mapped to 0xe680a000, size 1

Re: FW: [Dri-users] ProSavageDDR, No DRI Thusfar

2004-10-08 Thread Alex Deucher
gt; >Ok. I think you should be ok. try the adding the dri section to your > >config. what does dmesg or var/log/messages show? > > > >Alex > > > > > > > >>-----Original Message- > >>From: Alex Deucher [mailto:[EMAIL PROTECTED] > >>Sent: Friday