Impresions new image 20091216

Mirko Vogt lists at nanl.de
Thu Dec 17 09:22:56 EST 2009


Hey!

On Thu, 2009-12-17 at 12:53 +0800, Xiangfu Liu wrote:
> > *Powerbutton don't work to shutdown
> > 
> Hi Mirko can you add the "fnkeys /dev/input/event0" to your rootfs image.

Sure - it wasn't packaged for OpenWrt yet, was it?
If not, I'll do so this afternoon.

> > 
> > *ZimReader , I use this file that works on my PC[1] (3,2Gb) Program
> > starts and I can connect to Ben 8080 port  on PC navigato it only
> > loads the navigation part and was unable to serve an article, here is
> > the output:
> > 
> > #ZimReader -l 192.168.1.1 wikipedia_es_kiwix_120000\+_06_2009_alpha4.zim
> > IP 192.168.1.1 port 8080
> > Wikipedia ist jetzt unter http://localhost:8080/ verfügbar
> > Die Einstellungen können unter $HOME/.ZimReader geändert werden
> > ---[and after a while]-----
> > 1969-09-25 10:23:17.54669 [663.7176] FATAL tntnet.worker - requesttime
> > 600 seconds in thread 2051 exceeded - exit process
> > 
> > also here is the top info when ZimReader is loaded
> > Mem: 27380K used, 1092K free, 0K shrd, 36K buff, 14024K cached
> > CPU:   0% usr   0% sys   0% nic   0% idle   0% io 100% irq   0% sirq
> > Load average: 1.00 1.00 0.92 1/41 684
> >   PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
> >   654   647 root     R     1364   5%   1% top
> >   676   627 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   677   676 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   684   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   683   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   679   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   680   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   681   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   678   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   682   677 root     S     9080  32%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   658     1 root     D     4692  16%   0% ZimReader -l 192.168.1.1 wikipedia_es
> >   432     1 root     S     1372   5%   0% /bin/ash --login
> >   440     1 root     S     1372   5%   0% syslogd -C16
> > 
> > Too much memory hungry? maybe a swapfile can help?

Yeah, we are aware of the huge memory consumption of the ZimReader
respectively the underlying zimlib on the NanoNote.

We're in contact with the developers of the project - modifying and
tuning permanently to get memory comsumption reduced :)

> > 
> > * vido, just a blank screen and I need to reboot the  device,  here is
> > the output:
> > root at BenNanoNote:/card/zipfiles# vido wikipedia_es_kiwix_120000\+_06_2009_alpha4
> > .zim
> > commandline read: vido
> > 
> >    ~~~~~~~~~~~~~~~~~~~~~~~~~~| DirectFB 1.4.2 |~~~~~~~~~~~~~~~~~~~~~~~~~~
> >         (c) 2001-2009  The world wide DirectFB Open Source Community
> >         (c) 2000-2004  Convergence (integrated media) GmbH
> >       ----------------------------------------------------------------
> > 
> > (*) DirectFB/Core: Single Application Core. (2009-12-15 22:50)
> > (*) Direct/Thread: Started 'VT Switcher' (624) [CRITICAL OTHER/OTHER
> > 0/0] <2093056>...
> > (*) Direct/Thread: Started 'VT Flusher' (625) [DEFAULT OTHER/OTHER
> > 0/0] <2093056>...
> > (*) DirectFB/FBDev: Found 'JZ4740 FB' (ID 0) with frame buffer at
> > 0x01980000, 300k (MMIO 0x13050000, 64k)
> > (*) Direct/Thread: Started 'Linux Input' (626) [INPUT OTHER/OTHER 0/0]
> > <2093056>...
> > (*) DirectFB/Input: gpio-keys (1) 0.1 (directfb.org)
> > (*) Direct/Thread: Started 'Linux Input' (627) [INPUT OTHER/OTHER 0/0]
> > <2093056>...
> > (*) DirectFB/Input: matrix-keypad (2) 0.1 (directfb.org)
> > (*) DirectFB/Graphics: Generic Software Rasterizer 0.6 (directfb.org)
> > (*) DirectFB/Core/WM: Default 0.3 (directfb.org)
> > (*) Direct/Thread: Started 'EventBufferFeed' (628) [MESSAGING
> > OTHER/OTHER 0/0] <2093056>...
> > GConf Error: Failed to contact configuration server; some possible
> > causes are that you need to enable TCP/IP networking for ORBit, or you
> > have stale NFS locks due to a system crash. See
> > http://www.gnome.org/projects/gconf/ for information. (Details -  1:
> > Failed to get connection to session: dbus-launch failed to autolaunch
> > D-Bus session: Autolaunch requested, but X11 support not compiled in.
> > Cannot continue.
> > )
> > GConf Error: Failed to contact configuration server; some possible
> > causes are that you need to enable TCP/IP networking for ORBit, or you
> > have stale NFS locks due to a system crash. See
> > http://www.gnome.org/projects/gconf/ for information. (Details -  1:
> > Failed to get connection to session: dbus-launch failed to autolaunch
> > D-Bus session: Autolaunch requested, but X11 support not compiled in.
> > Cannot continue.
> > )
> > 
> > gtkhtml-ERROR **: gconf error: Failed to contact configuration server;
> > some possible causes are that you need to enable TCP/IP networking for
> > ORBit, or you have stale NFS locks due to a system crash. See
> > http://www.gnome.org/projects/gconf/ for information. (Details -  1:
> > Failed to get connection to session: dbus-launch failed to autolaunch
> > D-Bus session: Autolaunch requested, but X11 support not compiled in.
> > Cannot continue.
> > )
> > 
> > aborting...
> > (!) [  622:    0.000] --> Caught signal 6 (sent by pid 622, uid 0) <--

That's because of a bug / special behaviour (?) of dbus.
The short version:
vido is using gtkhtml, gtkhtml is using gconf, gconf is spawning
"dbus-launch --autolaunch". However the "--autolaunch" argument is only
available when dbus was compiled with libX11-support. As we're using
DirectFB instead of Xorg there's no need for libX11 support.

I patched out the need of gconf for gtkhtml which should solve this
problem in this particular case. Will test and commit the change this
evening.

> > 
> > *gtkperf, scrolling on gtkTexview text box and in firt tab test
> > results box produce is slow and produce a black box than hide text but
> > on Help tab text box scroll works flawlessly , Drawing doesn't draws
> > anything

That's weird - didn't experience something similar yet.
As a matter of fact not all avalable gtk/gdk-calls and -widgets are
handled in the DirectFB-backend. Maybe this is related.

Thanks a lot for your reports!

Cheers

mirko



-- 
This email address is used for mailinglist purposes only.
Non-mailinglist emails will be dropped automatically.
If you want to get in contact with me personally, please mail to:
mirko.vogt <at> nanl <dot> de





More information about the discussion mailing list


interactive