[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#342053: DirectFrameBuffer crashes on PPC systems if HW accelerated drivers are used

On Sat, Sep 23, 2006 at 12:07:45PM +0200, Attilio Fiandrotti wrote:
> Sven Luther wrote:
> <snip/>
> >>I belive disabling hw acceleration on PPC machines is a good choice, as 
> >>we're interested in stability, not performance, and i also belive 
> >>performance drop won't be even detectable in the case of a simple DFB 
> >>application like our GTK frontend.
> >>By the way, i think disabling HW acceleration unconditionally for *every 
> >>architecture* wouldn't be a bad idea, this could save us many a headache 
> >>in the future.
> >
> >
> >I would enable a 'secret' debconf switch to enable hw accel, be it only for
> >testing.
> That's a good idea.
> I also wonder if kernels shipped in d-i include or not modules for 
> hardware specific framebuffer devices, or generic drivers (like vesafb 
> on i386) only.


So, on powerpc, we have : offb, controlfb, platinumfb, valkyriefb, imsttfb,
nvidiafb, matroxfb, radeonfb, aty128fb, atyfb, sisfb and 3dfxfb builtin.

cirrusfb, s1d13xxxfb (no idea what this one is), savagefb, neomagixfb, kyrofb
and tridentfb as modules.

> >>Sven, looking at the PNG you posted it looks like the trashed banner 
> >>colours issue we experienced at extremadura is gone, does also the 
> >>cursor is displayed correctly (to grab both screen and pointer at DFB's 
> >>level, you can press the "PrtSc" key in the case your PPC has one) ?
> >
> >
> >The pegasos uses a normal PC keyboard, so i should have this key, but in 
> >any
> >case, indeed both these issues are gone, and the two new ones i mentioned 
> >are
> >there (the list selection dissapearance thingy). Do you see that on x86 
> >also ?
> Yes, i saw the vanished lines in your screenshots and i belive this may 
> be #385026, which  is GTKDFB 2.8.x related and affects all HW platforms.
> As Frans said, this is a quite annoying bug and i'll try to see if i can 
> fix it in GTKDFB 2.8.20 with a small patch (but i'm not sure it's going 
> to be an easy fix).

Is it fixed in 2.10.x ? 

> >Also, about the console font corruption with radeonfb, i would be 
> >interested
> >in feedback of if it is a powerpc only issue, or ppc stuff ? 
> No idea, i on no radeon boards :(

Someone else ? 

> >>Any chanche to test if disabling HW acceleration also makes the g-i 
> >>usable on machines equippped with ATI or NVIDIA graphic boards ( where 
> >>atyfb and nvidiafb modules would be used in the case HW acceleration was 
> >>not forced off ) ?
> >
> >
> >Nope, but as soon as the fixed rootskel-gtk is uploaded, we can issue a 
> >call
> >for testers on debian-powerpc, using the daily builds.
> A round of PPC tests would be useful, especially it happens to find 
> owners of ATI or NVIDIA boards.

ati being mach64 (rage) and aty (rage 128) here.

Not sure if we ever had a success with g-i on oldworld, so it is less
important, and my prep box has a sis and a matrox, but g-i is too big to boot
on it. I do have a spare matox millenium i could plug in the pegasos, and just
got a xgi volari v3xt. Will test with them. nvidia is evil and should be
boycotted anyway :)


Sven Luther
> cheers
> Attilio
> ---------------------------------------------------------------------------------------
> Orange vous informe que cet  e-mail a ete controle par l'anti-virus mail. 
> Aucun virus connu a ce jour par nos services n'a ete detecte.

Reply to: