02.12.2013 04:58, Carsten Haitzler (The Rasterman) kirjoitti:
> On Sun, 1 Dec 2013 19:29:49 -0600 Jeff Hoogland said:
>
>> It is in fact the 3150
>
> THAT would be your problem then. that gpu is the black sheep of the intel gpu
> family. it's "half accelerated". it has a hw fragment shader but N
On Sun, 1 Dec 2013 21:03:47 -0600 Jeff Hoogland said:
> Meh, glad to hear it is only for that chipset I guess.
>
> Still makes me a bit sad though as I love my little Asus T101MT.
sorry to say... but your gpu is "broken" (tm). :( it worked before simply
because we didn't throw everything at it.
Meh, glad to hear it is only for that chipset I guess.
Still makes me a bit sad though as I love my little Asus T101MT.
On Sun, Dec 1, 2013 at 8:58 PM, Carsten Haitzler wrote:
> On Sun, 1 Dec 2013 19:29:49 -0600 Jeff Hoogland
> said:
>
> > It is in fact the 3150
>
> THAT would be your problem
On Sun, 1 Dec 2013 19:29:49 -0600 Jeff Hoogland said:
> It is in fact the 3150
THAT would be your problem then. that gpu is the black sheep of the intel gpu
family. it's "half accelerated". it has a hw fragment shader but NOT a hw
vertex shader. it is the ONLY gpu i know of that does this. they
I haven't tried under E17+EFL 1.8.0 yet (see my other thread about having
issues with E17 and the EFL release). Previously I had only used the older
drivers with E17.
I'll set aside some time this week to get E18 run with that command to see
if it produces anything else.
On Sun, Dec 1, 2013 at 8
Hello,
On Mon, Dec 2, 2013 at 7:11 AM, Jeff Hoogland wrote:
> To give a bit more video information -
>
> I started with 2.17 intel drivers and mesa 8.0.1, but then I upgraded to
> the 2.99 intel drivers and mesa 9.2.0 - still seeing the same thing I
> described with these newer drivers.
Did you
It is in fact the 3150
On Sun, Dec 1, 2013 at 6:57 PM, Carsten Haitzler wrote:
> On Sun, 1 Dec 2013 18:45:36 -0600 Jeff Hoogland
> said:
>
> > This is the lspci output of my card:
> >
> > VGA compatible controller: Intel Corporation Atom Processor
> > D4xx/D5xx/N4xx/N5xx Integrated Graphics Con
On Sun, 1 Dec 2013 18:45:36 -0600 Jeff Hoogland said:
> This is the lspci output of my card:
>
> VGA compatible controller: Intel Corporation Atom Processor
> D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
thats not useful. :)
check your Xorg.0.log or just find the actual cpuinfo
This is the lspci output of my card:
VGA compatible controller: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller (rev 02)
On Sun, Dec 1, 2013 at 6:15 PM, Carsten Haitzler wrote:
> On Sun, 1 Dec 2013 16:11:14 -0600 Jeff Hoogland
> said:
>
> > To give a bit mor
On Sun, 1 Dec 2013 16:11:14 -0600 Jeff Hoogland said:
> To give a bit more video information -
>
> I started with 2.17 intel drivers and mesa 8.0.1, but then I upgraded to
> the 2.99 intel drivers and mesa 9.2.0 - still seeing the same thing I
> described with these newer drivers.
is this an at
To give a bit more video information -
I started with 2.17 intel drivers and mesa 8.0.1, but then I upgraded to
the 2.99 intel drivers and mesa 9.2.0 - still seeing the same thing I
described with these newer drivers.
On Sun, Dec 1, 2013 at 2:59 PM, Jeff Hoogland wrote:
> Just got around to ins
Just got around to installing E18 on my old netbook with an intel graphics
card - opengl compositing under E17 worked fine in the past on this system.
Under E18 I am getting constant 30+% CPU usage from enlightenment while
using OpenGL compositing (with composit effects disabled).
Oddly though wh
12 matches
Mail list logo