On Fri, 21 Jan 2005 15:32:44 +0000, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-01-21 at 16:20 +0100, Taoufik Zammou wrote:
> >
> >
> > I'm trying for days now, without a result. Directfb doesn't want to
> > run on 1400x1050. Every time i try, directfb exits with "Caught signal
> > 7 (at 0x203c9000, non-existent physical address)".
> >
> > If i set the resolution to 640x480-60, it works (multiple dfbterm's
> > works also).
> >
> > Other resolutions (1024x768 eg..) give a black screen, but i think
> > that's a problem in radionfb driver since setting the resolution with
> > fbset also gives a black screen.
>
> What does fbset -i tell you?
>
> --
> Torgeir Veimo <[EMAIL PROTECTED]>
>
>
I've done some tests and realized that:
- When recompiling DirectFB without multi-app support (fusion),
DirectFB works in 1400x1050.
- When compiled with multi-app, DirectFB crashes on 1400x1050...
whatever the refreshrate is. I've tried [EMAIL PROTECTED] and [EMAIL PROTECTED]
Both worked good with fbset (console). Running DirectFB with the last
one gave screen for a half a second, there after i get the "Caught
signal 7" error. Running DirectFB with the fist one, DirectFB exists
immediatly with the "Caught signal 7" error.
So it seems it has something to do with the fusion kernel module.
fbset -i tells this:
mode "1400x1050-62"
# D: 108.003 MHz, H: 65.856 kHz, V: 61.778 Hz
geometry 1400 1050 1400 1050 8
timings 9259 88 40 13 0 112 3
hsync high
vsync high
rgba 8/0,8/0,8/0,0/0
endmode
Frame buffer device information:
Name : ATI Radeon Lf
Address : 0xe8000000
Size : 33554432
Type : PACKED PIXELS
Visual : PSEUDOCOLOR
XPanStep : 8
YPanStep : 1
YWrapStep : 0
LineLength : 1408
MMIO Address: 0xfcff0000
MMIO Size : 16384
Accelerator : No
I've also tried this mode:
mode "1400x1050-75"
# D: 141.905 MHz, H: 86.475 kHz, V: 75.000 Hz
geometry 1400 1050 1400 1050 8
timings 7046 50 50 50 50 141 3
vsync high
hsync high
endmode
