On Mon, Jun 15, 2009 at 11:46:31PM +0200, Kurt Roeckx wrote:
> On Wed, Jun 10, 2009 at 12:20:04AM +0200, Kurt Roeckx wrote:
> > On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote:
> > > On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote:
> > > > Kurt Roeckx wrote:
> > > > > On Th
On Wed, Jun 10, 2009 at 12:20:04AM +0200, Kurt Roeckx wrote:
> On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote:
> > On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote:
> > > Kurt Roeckx wrote:
> > > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote:
> > > >
> >
On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote:
> On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote:
> > Kurt Roeckx wrote:
> > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote:
> > >
> > >> Kurt Roeckx wrote:
> > >>
> > >>> That removes the line, but d
On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote:
> Kurt Roeckx wrote:
> > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote:
> >
> >> Kurt Roeckx wrote:
> >>
> >>> That removes the line, but does not solve the problem.
> >>>
> >>>
> >> Right, removing write
> Did you try a 2.6.30-rc* kernel? Some packages are available at
> http://kernel-archive.buildserver.net/debian-kernel/
I've tried 2.6.30-rc8 from this location, and this solves the bug for me on
865G, log shows now that DRI is enabled (but not DRI2).
However,
i didn't notice any speed up, and
Kurt Roeckx wrote:
> On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote:
>
>> Kurt Roeckx wrote:
>>
>>> That removes the line, but does not solve the problem.
>>>
>>>
>> Right, removing write-combining is only supposed to decrease performance :)
>>
>
> So I'm still
On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote:
> Kurt Roeckx wrote:
> >
> > That removes the line, but does not solve the problem.
> >
>
> Right, removing write-combining is only supposed to decrease performance :)
So I'm still seeing this problem with the latest version in
unst
Hi, same bug on my workstation with debian unstable and
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated
Graphics Controller [8086:2572] (rev 02)
with kernel: linux-image-2.6.29-1-686 and linux-image-2.6.29-2-686
with packages:
ii libdrm-intel1
Kurt Roeckx wrote:
>> echo disable=2 > /proc/mtrr
>>
>
> That removes the line, but does not solve the problem.
>
Right, removing write-combining is only supposed to decrease performance :)
Brice
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "un
On Thu, Apr 16, 2009 at 08:48:54PM +0200, Brice Goglin wrote:
> Kurt Roeckx wrote:
> > On Thu, Apr 16, 2009 at 08:09:30PM +0200, Frederic Peters wrote:
> >
> >> Brice Goglin wrote:
> >>
> >>
> >>> So now, booting 2.6.29 and doing as root
> >>> echo "base=0x0e800 size=0x800 type=
On Thu, Apr 16, 2009 at 08:09:30PM +0200, Frederic Peters wrote:
> Brice Goglin wrote:
>
> > So now, booting 2.6.29 and doing as root
> > echo "base=0x0e800 size=0x800 type=write-combining" > /proc/mtrr
> > might give you the same MTRR back, and might even fix your problems.
>
> Same
Kurt Roeckx wrote:
> On Thu, Apr 16, 2009 at 08:09:30PM +0200, Frederic Peters wrote:
>
>> Brice Goglin wrote:
>>
>>
>>> So now, booting 2.6.29 and doing as root
>>> echo "base=0x0e800 size=0x800 type=write-combining" > /proc/mtrr
>>> might give you the same MTRR back, and might
Brice Goglin wrote:
> So now, booting 2.6.29 and doing as root
> echo "base=0x0e800 size=0x800 type=write-combining" > /proc/mtrr
> might give you the same MTRR back, and might even fix your problems.
Same corrupted display for me after updating MTRR, too bad :(
Frederic
Frederic Peters wrote:
> Brice Goglin wrote:
>
>
>>> Downgrading the kernel from 2.6.29 to 2.6.26 fixes the problem for
>>> me.
>>>
>> Any difference in /proc/mtrr between 2.6.26 and 2.6.29 ?
>>
>
> I downgraged from 2.6.29 to 2.6.28, and it also fixed the problem.
>
> /proc/mtrr in
Brice Goglin wrote:
> > Downgrading the kernel from 2.6.29 to 2.6.26 fixes the problem for
> > me.
>
> Any difference in /proc/mtrr between 2.6.26 and 2.6.29 ?
I downgraged from 2.6.29 to 2.6.28, and it also fixed the problem.
/proc/mtrr in 2.6.28:
reg00: base=0x0 (0MB), size= 1024M
Kurt Roeckx wrote:
> On Wed, Apr 15, 2009 at 11:58:56PM +0200, Kurt Roeckx wrote:
>> On Sun, Apr 12, 2009 at 12:39:34PM +0200, Brice Goglin wrote:
>>> found 523415 2:2.6.99.903-1
>> I'm also seeing the same thing, but with a 830 chipset.
>
> Downgrading the kernel from 2.6.29 to 2.6.26 fixes the p
On Wed, Apr 15, 2009 at 11:58:56PM +0200, Kurt Roeckx wrote:
> On Sun, Apr 12, 2009 at 12:39:34PM +0200, Brice Goglin wrote:
> > found 523415 2:2.6.99.903-1
>
> I'm also seeing the same thing, but with a 830 chipset.
Downgrading the kernel from 2.6.29 to 2.6.26 fixes the problem for
me.
Kurt
17 matches
Mail list logo
