View Single Post
Old 01-26-2015, 01:23 AM   #47
chrox
Zealot
chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.chrox ought to be getting tired of karma fortunes by now.
 
Posts: 144
Karma: 405567
Join Date: Nov 2012
Device: K3 KPW PB840
Quote:
Originally Posted by sadowski View Post
Here comes a shot with yres/2 and line_lenght+8. The screen is smaller and rotated but otherwise undistorted.

As for the basic framebuffer information: Where does the output from the print() statements end up? It is not in crash.log.
The result is interesting and proves my hypothesis. Then you can try decrease yres one by one with line_length + 8 until koreader not crashes this way:

Code:
elseif vinfo.bits_per_pixel == 8 then
            self.bb = BB.new(vinfo.xres, vinfo.yres - 1, BB.TYPE_BB8, self.data, finfo.line_length + 8)
else
to

Code:
elseif vinfo.bits_per_pixel == 8 then
            self.bb = BB.new(vinfo.xres, vinfo.yres - 10, BB.TYPE_BB8, self.data, finfo.line_length + 8)
else
.
chrox is offline   Reply With Quote