I've still not been able to see anything useful on my Radeon based
display, when running the tutorial programs (simple.c). I'd earlier
found that I had two framebuffers created. (/dev/fb0 and /dev/fb1
replied on fbset -i queries.) I was able to get rid of /dev/fb1 by
adjusting my kernel boot args line.
I'm just concluding that my trouble is much more fundamental than
DirectFB -- I think the underlying framebuffer driver isn't right. If
I query the fb settings, I see a reasonable reply --
[EMAIL PROTECTED] simple]# fbset
mode "640x480-60"
# D: 25.176 MHz, H: 31.469 kHz, V: 59.942 Hz
geometry 640 480 640 480 8
timings 39721 40 24 32 11 96 2
rgba 8/0,8/0,8/0,0/0
endmode
but if I try to press these settings back into the system, a'la
[EMAIL PROTECTED] simple]# fbset --geometry 640 480 640 480 8 \
--timings 39721 40 24 32 11 96 2 -rgba 8/0,8/0,8/0,0/0
my monitor behaves exactly the same way as it does when running the
'simple' tutorial program -- it seems to drop sync. (Monitor goes into
standby mode.)
The 'simple' program, upon exit, restores the settings to make the
console come back to life. Likewise, after my failed fbset, I can
switch console terminals (<alt><F2>) then back to cosole-1 to get my
video back.
Does that suggest any ideas I could pursue? I'm using the v0.1.4
radeonfb.c driver. I see there are newer revs available... v0.1.6 at
least, and I see that 'mode set fixes' was among the refinements. Is
it reasonable to bring in a newer radeonfb w/o upgrading the entire
kernel?
Thanks for any help...
Benton 14jan04
--
BC&G Holzwarth
[EMAIL PROTECTED]
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-users" as subject.
