The warning message from grub can be safely ignored.

In your kernel config you should eliminate the uvesa framebuffer, since it 
conflicts with vesafb.

Next, change the 'vga=789' to 'vga=ask'. The vesafb driver will ask at boot 
time which video mode you would like. If you hit the return key it will show 
you a list of possible modes on your hardware.

What is your output from dmesg?

JDR

On Tuesday 25 May 2010, Ian Harrold wrote:
> John,
>
> Thanks for the response.   However I still cannot get it to show a
> "/dev/fb" device.   The command "cat /proc/fb" is size 0.
>
> When I add "vga=xxx" to the grub (v1.97.2) boot command, I get the
> following response from grub, input first:
>
>    - Input:
>       - insmod ext2
>       - set root=(hd0,3)
>       - linux /boot/vmlinux-2.6.32.8-lfs-6.6 root=/dev/sda3 ro vga=789
>       - boot
>    - Output when the "linux" line is entered
>       - vga=789 is deprecated.  Use set gfxpayload=800x600x24,800x600
> before linux command instead.
>
> And after the boot the "/dev/fb" device is not present.  So I tried the
> following grub command:
>
>    - Input:
>       - insmod ext2
>       - set root=(hd0,3)
>       - set gfxpayload=800x600x24,800x600
>       - linux /boot/vmlinux-2.6.32.8-lfs-6.6 root=/dev/sda3 ro
>       - boot
>
> Still no luck.   Here are my kernel .config settings related to FB
>
> CONFIG_FB=y
> CONFIG_FB_BOOT_VESA_SUPPORT=y
> CONFIG_FB_CFB_FILLRECT=y
> CONFIG_FB_CFB_COPYAREA=y
> CONFIG_FB_CFB_IMAGEBLIT=y
> CONFIG_FB_MODE_HELPERS=y
> CONFIG_FB_TILEBLITTING=y
> CONFIG_FB_VGA16=m
> CONFIG_FB_UVESA=y
> CONFIG_FB_VESA=y
> CONFIG_FB_EFI=y
> CONFIG_VT_HW_CONSOLE_BINDING=y
>
> Anyone have other words of advice?    Thank you in advance,
> Ian
>
> On Tue, May 25, 2010 at 12:08 PM, John D. Robertson <[email protected]> wrote:
> > Add 'vga=0x318' to your kernel boot command line, where you replace 0x318
> > with
> > the appropriate VGA mode:
> >
> > http://linuxandfriends.com/2008/09/17/vga-modes-used-linux/
> >
> > Regards,
> > JDR
> >
> > On Tuesday 25 May 2010, Ian Harrold wrote:
> > > All,
> > >
> > > This really isn't a DirectFB issue, but question on Frame Buffer
> > > support. I created my own linux kernel using
> > > http://www.linuxfromscratch.org/lfs/ which uses 2.6.32.8.  However when
> > > the kernel boots up there is no "/dev/fb" device.   When I try to run a
> > > directfb app it states the same.
> >
> >  I
> >
> > > have built the kernel with vesafb support.
> > >
> > > Any one have insight on what I am failing to do to create the fb
> > > device?
> > >
> > > Much appreciated,
> > > Ian
> >
> > --
> > =============================================================
> > John D. Robertson, Computer / Engineering Consultant
> > Robertson & Robertson Consultants, Inc.
> > 3637 West Georgia Rd.
> > Pelzer, SC  29669
> >
> > Phone: (864) 243-2436
> >  Fax: (864) 243-3023
> > Email: [email protected]
> >  WWW: http://www.rrci.com



-- 
=============================================================
John D. Robertson, Computer / Engineering Consultant
Robertson & Robertson Consultants, Inc.
3637 West Georgia Rd.
Pelzer, SC  29669

Phone: (864) 243-2436
  Fax: (864) 243-3023
Email: [email protected]
  WWW: http://www.rrci.com
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to