On Sat, 8 Feb 2014 14:31:33 +0000 Mick <michaelkintz...@gmail.com> said:

> On Saturday 08 Feb 2014 13:45:55 Carsten Haitzler wrote:
> > On Sat, 8 Feb 2014 12:34:34 +0100 Jesús J. Guerrero Botella
> 
> > actually the ati chips are not one of the better supported. i have had NO
> > end of trouble with them. slowness, bugs, freezing etc. fglrx ati drivers
> > were the culprit at the time with the open drivers simply not working for
> > me at all (zero display). so as per this thread.. yes - userspace should
> > not be able to bring machines down like this...
> 
> I used to have problems like this, but may be going back 10 years now ... 
> these days hard crashes are a rarity.  The last time I had such a crash it 
> involved a Pentium 4 with a R360 card, running ... KDE!  Ha, ha!  No problems 
> with e18.

that was my first bad experience with ati. :) r250 card, p4 laptop. promised of
great support. not so much. :) i came back to ati back in 2009 or so. had to
use fglrx as radeon simply didnt work on my 4650 at the time... and all i can
say is... UGH!. they went on my perma-black-list after the second time for a
major reason - their insanely poor decisions to only allow compiz as a gl
compositor and no other process.

> > UNLESS the drivers have major bugs. and they do. i solved my problems by
> > never touching an ati chip again. that was my solution, but let me just
> > disabuse you of the image that ati chips (eg r300) are so well supported
> > and solid. in my experience, they are not. the fact that sysreq wouldn't
> > even work is a big hint... your drivers have problems. it just so happens
> > that e is tickling them.
> > 
> > people do say the newer radeon open source drivers work well, but i've
> > never gone back after my horrible experiences. i stick to intel or nvidia
> > (with nvidia drivers and one test machine with nouveau) and i don't see
> > anything close to the problems you see there.
> > 
> > so my tip is... avoid fglrx like the plague and try new radeon drivers, and
> > even then... just change gpu's. also be aware the r300 is from memory an
> > old old old gpu. it may simply not work with compositing and opengl. evas
> > needs opengl2.0 support (full glsl shader support for fragment and vertex
> > shaders). so without this it will fall back to software compositing.
> > depending on your cpu, gfx drivers, memory bus architecture, location of
> > gpu on the mem bus etc. this may or may not work well for you. given the
> > abysmal readback speeds i saw with fglrx back in the day, the compositor
> > in sw mode relies on readback for any updates... and this will hurt badly.
> > all the reading back from pixmaps plus writing to them may be tickling
> > your driver bugs too.
> 
> I am running RV730/M96-XT [Mobility Radeon HD 4670] (ChipID = 0x9488) which
> is 5 years old on my laptop and very rarely I may get e17/18 to crash, but by 
> clicking on 'Restart' or some such option that pops up it reloads and carries 
> on.  No hard locks.

sure. generally if e crashes, it's ea's (or efl's) fault... and we need to fix
it (it could be the fault of a library we depend on though - so it depends).
but a system hard lock like jesus is saying.. is a definite driver bug sign. in
big neon blinking lights.

> In defence of radeon I should say that the only time that I had to look into 
> which driver was needed and which firmware blob was back when I first 
> installed Linux on this machine and rolled its first kernel.  People with 
> NVidia post all sort of problems of incompatible driver version with 
> particular kernels, but with radeon 'it just works'™.

really? i've never hit that problem with nvidia - ever. :/


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to