Help me!! The fb0 no space left on device..

When I enter the android kernel console, I type :

cat 3.bmp > dev/graphics/fb0 error!!
write: No space left on device

After this, there is nothing showed on my lcd.

Could someone tell me what does this error message mean and how to solve please??

My all debug message : http://pastebin.com/m510035c5

Please help me !!

your bitmap is bigger than the framebuffer

When I enter the android kernel console, I type :

cat 3.bmp > dev/graphics/fb0 error!!
write: No space left on device

After this, there is nothing showed on my lcd.

Could someone tell me what does this error message mean and how to solve please??

your bitmap is bigger than the framebuffer

and if nothing shows up you are probably running X which takes over the fb
when I do the above with X runing I get nothing on the screen, if I
stop X and write data to /dev/fb0 it shows up on the screen

Frans

Tue, 12 Jan 2010, Koen Kooi wrote:

cat 3.bmp > dev/graphics/fb0 error!!
write: No space left on device

your bitmap is bigger than the framebuffer

Really? I thought it means that the image is bigger than the monitor. I.e. one can't put a 22" image to a 19" monitor.

To avoid the bitmap problem and image size problem, I catch the /dev/urandom to fb0. However, I still get the error message :

cat /dev/urandom > /dev/graphics/fb0

write: No space left on device

I don’t know why does it has no space left on fb0, how should I increase the space of fb0??

The following link is the log record : http://pastebin.com/m6aa4be02

Thank your all reply!!

Best Regards

Sorry, The following link is my log record :http://pastebin.com/m9d9983c

The last post is wrong.

Guys, I traced code on the driver/video/fbmem.c and I got some information.

When I enter the android kernel console, I don’t see anything in my LCD, so I type in the debug console to test the LCD:

cat 3.bmp > /dev/graphics/fb0

write: No space left on device

After typing, there is still nothing shown on my lcd.

To avoid the bitmap problem and image size problem, I catch the /dev/urandom to fb0. However, I still get the error message :

cat /dev/urandom > /dev/graphics/fb0

write: No space left on device

I trace the code, and I find that this message is shown in driver/video/fbmem.c: function fb_write(). I use printk to trace the vaule of variable, and I get a strange result which it seems a recursive program:

count = 4096 p= 0, ppos=3483934576 total_size = 0
count = 4096 p= 4096, ppos=3483934576 total_size = 0

count = 4096 p= 3686400, ppos=3483934576 total_size = 3686400
write: No space left on device

The following link is the log record : http://pastebin.com/m568ff558

I can’t find out the caller function which calls fb_write(), so I don’t know what does this happen. Could someone tell me what does this error message mean and how to solve please? I don’t know why does it has no space left on fb0, how should I increase the space of fb0?

Please help me.

Best Regards

Michael Wu wrote:

Guys, I traced code on the driver/video/fbmem.c and I got some
information.

When I enter the android kernel console, I don't see anything in my
LCD, so I type in the debug console to test the LCD:

# cat 3.bmp > /dev/graphics/fb0
write: No space left on device

Are you _sure_ that /dev/graphics/fb0 is a device node, and not an
ordinary file?

b.g.

Thank your reply, Bill.

umm … I am not sure, but I see there is a file in the android root file system /dev/graphics/fb0 which type is :character device(inode/chardevice)

Best Regards
Michael

2010/1/13 Bill Gatliff <bgat@billgatliff.com>

The framebuffer is a buffer of n bytes. If you write more than n bytes
to it, you'll get that error. /dev/urandom has infinite bytes, so you
will always get that error. And most likely 3.bmp is also bigger.

You can get the contents of the framebuffer, and also see the size of it
by looking at the file size, by
cat /dev/graphics/fb0 > foo

But that doesn't explain why you don't see anything on the LCD. Looking
at the kernel log, you configure the video mode for 1280x720. But later
an omap3evm panel driver is loaded... Are you using an EVM kernel on
Beagle board?

Tomi

As per my understanding, your fb is not properly configured based on
ur kernel log.
Use kernel image from
http://www.angstrom-distribution.org/demo/beagleboard/ & try.