> > It's actually more complicated than that. Old kernel images started
> > misbehaving from around 2.6.35-rc5 and any kernel older than that was
> > OK. When I recompiled the older kernels with squeeze gcc (migh have been
> > lenny gcc before, or different answers to make oldconfig), anything
On Mon, 09 Jul 2012 14:30:40 +0300, Meelis Roos said:
> It's actually more complicated than that. Old kernel images started
> misbehaving from around 2.6.35-rc5 and any kernel older than that was
> OK. When I recompiled the older kernels with squeeze gcc (migh have been
> lenny gcc before, or
On Mon, 09 Jul 2012 14:30:40 +0300, Meelis Roos said:
It's actually more complicated than that. Old kernel images started
misbehaving from around 2.6.35-rc5 and any kernel older than that was
OK. When I recompiled the older kernels with squeeze gcc (migh have been
lenny gcc before, or
> > > In 3.4, radeon worked with a glitch - window titles were see-throug (not
> > > drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
> > > acceleration on this system at all. Full dmesg below.
> >
> > Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32?
>
In 3.4, radeon worked with a glitch - window titles were see-throug (not
drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
acceleration on this system at all. Full dmesg below.
Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32?
That was a
> > In 3.4, radeon worked with a glitch - window titles were see-throug (not
> > drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
> > acceleration on this system at all. Full dmesg below.
>
> Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32?
That was a
In 2.6.32, radeon worked fine.
In 3.4, radeon worked with a glitch - window titles were see-throug (not
drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
acceleration on this system at all. Full dmesg below.
Fujitsu Lifebook P series, 256M RAM, 239 usable.
[0.00]
On Thu, Jul 5, 2012 at 8:00 AM, Meelis Roos wrote:
> In 2.6.32, radeon worked fine.
>
> In 3.4, radeon worked with a glitch - window titles were see-throug (not
> drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
> acceleration on this system at all. Full dmesg below.
Does
On Thu, Jul 5, 2012 at 8:00 AM, Meelis Roos mr...@linux.ee wrote:
In 2.6.32, radeon worked fine.
In 3.4, radeon worked with a glitch - window titles were see-throug (not
drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
acceleration on this system at all. Full dmesg
In 2.6.32, radeon worked fine.
In 3.4, radeon worked with a glitch - window titles were see-throug (not
drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
acceleration on this system at all. Full dmesg below.
Fujitsu Lifebook P series, 256M RAM, 239 usable.
[0.00]
In 3.4, radeon worked with a glitch - window titles were see-throug (not
drawn). In 3.5-rc5, radeon driver seems to be more careful and disables
acceleration on this system at all. Full dmesg below.
Does it always do it the same? got the dmesg from 3.4 and/or 2.6.32?
That was a good
11 matches
Mail list logo
