Hi,
> (*) DirectFB/Genefx: MMX detected and enabled > (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (directfb.org > <http://directfb.org>) You're not running the radeon driver. Your DirectFB is using the software fallback > during this, the screen stays black without anything on it, just black > black and black. > > lsmod | grep radeon says > [EMAIL PROTECTED] tools]# lsmod | grep radeon > radeonfb 108864 0 > fb_ddc 2432 1 radeonfb > i2c_algo_bit 6020 1 radeonfb > i2c_core 19348 4 radeonfb,fb_ddc,i2c_algo_bit,i2c_i801 > > fbset -i says: > [EMAIL PROTECTED] tools]# fbset -i > > mode "1024x768-76" > # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz > geometry 1024 768 1024 768 24 > timings 12714 128 32 16 4 128 4 > rgba 8/16,8/8,8/0,0/0 > endmode > > Frame buffer device information: > Name : VESA VGA > Address : 0xe8000000 > Size : 4718592 > Type : PACKED PIXELS > Visual : TRUECOLOR > XPanStep : 0 > YPanStep : 0 > YWrapStep : 0 > LineLength : 3072 > Accelerator : No You are running vesafb not radeonfb. > boot entry looks like that: > image=/boot/vmlinuz-mod > label=arch-fb > append="video=radeonfb:ywrap,mtrr" > root=/dev/sda2 > vga=792 > initrd=/boot/kernel26-mod.img > read-only The vga=... parameter is only for vesafb. Take it out of your boot entry. You have two possibilities for using DirectFB with your hardware: 1) Use vesafb (keep "vga=..." and delete the "video=radeonfb:..." option). DirectFB will automagically use its software fallback driver. You should get proper graphics output this way, but NO hardware acceleration! 2) Use radeonfb properly (delete "vga=..." and keep "video=radeonfb:..."), use the "video=radeonfb" option for initial modesetting, etc. Example: "video=radeon:[EMAIL PROTECTED]". Read the radeonfb documentation on the net or in the linux kernel sources for details and more options. This way you should get hardware accelerated DirectFB output. Your "fbset -i" output should then say something with "RADEON" instead of "VESA VGA". Furthermore, when you run a DirectFB program you should see something like (*) DirectFB/Graphics: Radeon driver version xxx or similar. In the output blurb. You might need to load radeonfb manually after bootup using "modprobe radeonfb". It seems that your were trying to use vesafb and radeonfb simultaneously and this was causing your problem... but I'm not an expert on this stuff... Hope it helps anyway... Oliver _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
