You helped my quite a lot - you made a few things clear. Now when I use the radeonfb module, fbset -i tells me that it uses the radeon module but when running one of the tools, it tells me to patch the kernel with the radeonfb-r300fix. I downloaded it using cvs or git (can't remember) and tried to patch the kernel. First I tried to patch 2.6.25, but it didn't work... he told me he skipped some parts of the patch. Then I tried to patch 2.6.22 - worked quite fine, but for me it's impossible to compile any kernel younger than 2.6.24 due to a bug fixed in March 2008 (see here: http://lkml.org/lkml/2008/4/16/436 )
Is there anyone willing to port the patch to 2.6.25? Or is it possible to patch a ready-compiled-kernel? Or can I ignore things like: "2 out of 17 hunks FAILED" ? Regards > Date: Tue, 20 May 2008 14:29:28 +0200 > From: Oliver Gabel <[EMAIL PROTECTED]> > Subject: Re: [directfb-users] DirectFB with radeonfb results in black > screen > To: directfb-users@directfb.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > 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
