Re: QtMoko v37 for GTA02
O Sábado, 17 de Decembro de 2011, fdvj...@vodafone.it escribiu: > Il 11/12/2011 17:51, Radek Polak ha scritto: > > Any other ideas for cool qt apps that you would like on QtMoko? > > A better and lightweight picture-viewer, like ristretto or viewnior or > something similar. Migh be a port of Neon. Fast and very usable on FR screen. -- David Garabana Barro jabber & google talk ID:da...@garabana.com Clave pública PGP/GPG: http://davide.garabana.com/pgp.html signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: uSD corruption (OT?)
On Saturday 17 December 2011 23:10:02 Doug Jones wrote: > On 12/16/2011 01:08 AM, Radek Polak wrote: > > On Thursday 15 December 2011 22:00:22 fdvj...@vodafone.it wrote: > >> Hi > >> I have a Kingstone microSD card 8GB. It seems to be reliable for data > >> but if I use it with a running distro, at this moment QtMoko, I > >> experience, during a day of usage, several freezings. I mean, when it is > >> in suspend mode (deep suspend enabled) if I press the power button the > >> Neo does not recover from the suspend. I have to pull off the battery > >> and then restart the Neo, but as can you imagine, after a couple of > >> times the file system gets corrupted and I have to format the partition. > >> Moreover this behaviour seems to become worse as the time passes. > >> Should I consider to replace the uSD card? are there known issues in > >> using running distro on it? > >> Thanks. > > > > For me uSD card never worked as stable rootfs. I always ended up with > > corrupted filesystem after a couple of days. But for data on FAT it > > always worked quite good. > > > > I guess this is some flaw in Freerunner's hardware or kernel driver. On > > GTA04 i have rootfs on uSD and no problems at all. I am starting to > > think that NAND on GTA04 is quite useless - it would be quite cool if it > > had 2 uSD cards instead (with BTRFS as fs it could rock). > > There have been endless discussions over the years, about file systems, > race conditions, suspend modes, the gravitational influence of > Jupiter... But I have never heard anyone claim that they actually > understand why a card that Just Works in my camera can't be made to Just > Work in all of our open source devices. > > > Yes, I know this isn't very constructive... Sometimes I just have to > vent... :-) You are probably familiar with/aware of linux-mtd at infradead.org. Part of their FAQ made me suspect optimizations for FAT or parts of the spec left out of the flash translation layer giving problems with anything but FAT [1]: "(...) we suspect that vendors may user various tricks or compromises to keep their devices "good enough" and cheap. For example, it is known that some vendors optimize their FTL devices for FAT, and if you start using ext3 on top of one, you might face some unexpected problems (...)" Not very constructive either :-( But a good read if you didn't after all ;-) Boudewijn [1] smime.p7s Description: S/MIME cryptographic signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko] Error sending SMS (GTA02])
Hi, About two weeks ago, my GTA02 stopped sending SMS messages. I was running QtMoko v35 at the time, on a Kingston uSD card. Running dmesg while trying to send messages revealed this error: [ 4171.93] mmc0:0001: error -110 reading SDIO_CCCR_INTx Thinking that my uSD card had failed (I'd had it for just over a year), I bought another one (A-Ram), set up a fresh install of QtMoko, upgraded to v37, tried to send another message, and see the same error in dmesg. At this point I'm assuming it's not a fault of the uSD card. Is it hardware? There doesn't seem to be any problem writing to the uSD card... On fail of sending message, the message is moved into Drafts, which works nicely. Is it a problem with my SIM card? It's only about 5 months old. Are there any other logs I can look at to find out what's happening? Is this something I can fix in the software, or should I just get another phone for use until the GTA04 is released? Thanks, Bernie ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: uSD corruption
On 12/16/2011 01:08 AM, Radek Polak wrote: On Thursday 15 December 2011 22:00:22 fdvj...@vodafone.it wrote: Hi I have a Kingstone microSD card 8GB. It seems to be reliable for data but if I use it with a running distro, at this moment QtMoko, I experience, during a day of usage, several freezings. I mean, when it is in suspend mode (deep suspend enabled) if I press the power button the Neo does not recover from the suspend. I have to pull off the battery and then restart the Neo, but as can you imagine, after a couple of times the file system gets corrupted and I have to format the partition. Moreover this behaviour seems to become worse as the time passes. Should I consider to replace the uSD card? are there known issues in using running distro on it? Thanks. For me uSD card never worked as stable rootfs. I always ended up with corrupted filesystem after a couple of days. But for data on FAT it always worked quite good. I guess this is some flaw in Freerunner's hardware or kernel driver. On GTA04 i have rootfs on uSD and no problems at all. I am starting to think that NAND on GTA04 is quite useless - it would be quite cool if it had 2 uSD cards instead (with BTRFS as fs it could rock). Regards Radek I suspect there is something about the SD card implementation that is deeply flawed. To my way of thinking, an interface should be well enough defined so that two devices should be able to figure out how to reliably talk to one another after being connected for a short time, even if they were designed by different groups years apart. The spec should spell out how, and every device should follow the spec. If it doesn't work this way, then there is something wrong with the spec, or with the processes vendors use to implement the spec, and/or with the group that manages and enforces the spec. Four years ago I discovered that some SD cards had problems with the OLPC XO-1. Then I had troubles with micro SD cards in the Freerunner. Then I heard about problems people were having with the EEE-PC running Linux. Then the SheevaPlug. And on and on. Four years later and I'm still hearing stories about SD cards getting corrupted, and you still find lists of "known to work / not work" cards in the wikis of various projects. Yet, if you exclude those cards that have obviously failed (because they don't work properly in anything), I never have problems with any SD card in any camera. What is the source of this discrepancy? Those cameras are proprietary inside, but those other projects are open source. Perhaps the people in charge of SD aren't revealing something to the open source communities? I don't know. There have been endless discussions over the years, about file systems, race conditions, suspend modes, the gravitational influence of Jupiter... But I have never heard anyone claim that they actually understand why a card that Just Works in my camera can't be made to Just Work in all of our open source devices. Yes, I know this isn't very constructive... Sometimes I just have to vent... :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA02
I've a couple of queries (v37 gta02) 1. some of the keyboards are now redundant, to my mind just the new large landscape one and the docked keyboard for use with the console are sufficient. Is it possible to remove the others to make the switching keyboard routine slicker? 2. any idea if the built in voip client can be expected to work? Thanks -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA02
Il 11/12/2011 17:51, Radek Polak ha scritto: Any other ideas for cool qt apps that you would like on QtMoko? A better and lightweight picture-viewer, like ristretto or viewnior or something similar. Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new theme: MokoFaen
Thanks for the fix. The theme works fine now and is a very welcome addition to the QtMoko themes. Alon. On Sat, 2011-12-17 at 17:39 +, Radek Polak wrote: > On Friday 16 December 2011 15:49:56 Radek Polak wrote: > > > On Friday 16 December 2011 10:20:12 fdvj...@vodafone.it wrote: > > > Hi Radek > > > Sorry to say it but I suppose the package is wrong. There are a plenty > > > of SVGs that are not intended to be used in theme, they are just the > > > source and I'm quite sure they're causing the glitches. If you use only > > > the PNGs (except of only two SVGs for the PIN box) all the glitches > > > should go away (: Also note, in fact, that the .deb is about 7 MB, it > > > should be much more light. > > > The correct files to be packaged are here [1] in the MokoFaen.tar.gz > > > (not MokoFaen_SVG.tar.gz). > > > Thank you! > > > > > > Joif > > > > > > [1] http://db.tt/8KF7DHRp > > > > Ahh oki, i'll try to fix it. > > Hi, it should be fixed now. > > Regards > > Radek > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new theme: MokoFaen
it works like a charm (: thank you! Joif Il 17/12/2011 18:39, Radek Polak ha scritto: Hi, it should be fixed now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] new theme: MokoFaen
On Friday 16 December 2011 15:49:56 Radek Polak wrote: > On Friday 16 December 2011 10:20:12 fdvj...@vodafone.it wrote: > > Hi Radek > > Sorry to say it but I suppose the package is wrong. There are a plenty > > of SVGs that are not intended to be used in theme, they are just the > > source and I'm quite sure they're causing the glitches. If you use only > > the PNGs (except of only two SVGs for the PIN box) all the glitches > > should go away (: Also note, in fact, that the .deb is about 7 MB, it > > should be much more light. > > The correct files to be packaged are here [1] in the MokoFaen.tar.gz > > (not MokoFaen_SVG.tar.gz). > > Thank you! > > > > Joif > > > > [1] http://db.tt/8KF7DHRp > > Ahh oki, i'll try to fix it. Hi, it should be fixed now. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: NetBSD-current for openmoko GTA02
On 12/07/2011 06:27 AM, Timo Juhani Lindfors wrote:
> Peter Tworek writes:
>> For some time now I've been spending some of my free time on getting
>> NetBSD running on my Freerunner.
> Interesting, do you have this work in some version control system?
> Would be nice to see all the steps :-)
It took me some time, but the source code of the port can be downloaded
from github: https://github.com/tworaz/src/commits/gta02-5.99.58.
Building the code should be straightforward if you have some experience
with NetBSD. Just checkout the sources somewhere, enter the directory
from command line and execute:
# ./build.sh -N 1 -u -U -O ../obj-evbarm -T ../tools-evbarm -m evbarm -V
HAVE_GCC=45 build
# ./build.sh -N 1 -u -U -O ../obj-evbarm -T ../tools-evbarm -m evbarm -V
HAVE_GCC=45 kernel=GTA02
Depending on your hardware this can take several hours to complete.
After it's done the kernel images should be available under
../obj-evbarm/sys/arch/evbarm/compile/GTA02/{netbsd, netbsd.ub,
netbsd.gz.ub}. Note however that this is just a kernel image without any
kind of ramdisk. The sources for the ramdisk I've used in my previous
image can be found here: https://github.com/tworaz/netbsd-gta02-ramdisk.
To build it just add tools-evbarm from kernel build process yo your
path, enter checked out ramdisk repository and run:
# ./build.sh
This should be much quicker to complete. The result of the build process
is ramdisk.fs file. To embed the ramdisk inside the kernel I use the
following shell script: (You'll have to change _WRKDIR value to make it
work)
#!/bin/sh
_WRKDIR=/home/tworaz/devel/NetBSD
_OBJDIR=$_WRKDIR/obj-evbarm
_TOOLDIR=$_WRKDIR/tools-evbarm
_MDSETIMG=$_TOOLDIR/bin/arm--netbsdelf-mdsetimage
_OBJCOPY=$_TOOLDIR/bin/arm--netbsdelf-objcopy
_MKUBOOTIMG=$_TOOLDIR/bin/nbmkubootimage
_MKUBOOTIMG_ARGS="-A arm -T kernel -a 0x3020 -n NetBSD/gta02 -C gz"
echo -n "Removing old kernel: "
rm -f netbsd.gz.ub
echo "OK"
echo -n "Obtaining new binaries: "
cp $_OBJDIR/sys/arch/evbarm/compile/GTA02/netbsd .
cp $_WRKDIR/ramdisk-gta02/ramdisk.fs .
echo "OK"
echo -n "Preparing new kernel image: "
$_MDSETIMG netbsd ramdisk.fs
$_OBJCOPY -S -O binary netbsd netbsd.bin
gzip -c netbsd.bin > netbsd.bin.gz
$_MKUBOOTIMG $_MKUBOOTIMG_ARGS netbsd.bin.gz netbsd.gz.ub > /dev/null
echo "OK"
echo -n "Removing temporary files: "
rm -f ramdisk.fs
rm -f netbsd
rm -f netbsd.bin
rm -f netbsd.bin.gz
echo "OK"
_SIZE=`du -k netbsd.gz.ub| awk '{ print $1 }'`
echo "New Image Size: $_SIZE kB"
The final image should boot on the Freerunner using the procedure I've
described in my first email.
/ptw
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: NetBSD-current for openmoko GTA02
On 12/08/2011 07:15 PM, Nick Sheppard wrote: > On 06/12/11 23:11, Peter Tworek wrote: >> Hi, >> >> For some time now I've been spending some of my free time on getting >> NetBSD running on my Freerunner. > > At last someone bringing NetBSD to the Freerunner! I've been waiting > for the day when I can point to my phone and casually say "Of course > it runs NetBSD ...". Thank you! You're welcome :). > > I'm only a tinkerer myself, but some years ago I enjoyed getting > NetBSD running on an old Blue & White Mac G3. I was really impressed > by the enthusiasm and helpfulness of the NetBSD community, and by > their mission to make it run on every possible hardware, down to > toasters if possible. What, I really like about NetBSD is the code and documentation. While hacking on linux kernel when I wanted to learn something, I've always ended up spending enormous amounts of time on digging trough mailing list archives, some random web pages, text files under Documentation/ etc. I've usually found what I wanted, but the whole experience was tiresome. With NetBSD I've never had any problems with finding valuable information in the manual pages. > It always seemed to me that the Freerunner would make a great project > (if I only had the time and the skill). So I'm really happy to see > what you're doing. Well I can't promise that this project will ever be as usable as linux is on the GTA02. I'm afraid that there is still enormous amount of work to be done on this port. I also don't think I have the necessary skills and time to do it all by myself. I'll probably continue working on it as long as it's fun, but can't promise anything more. > One question now - what about the GTA04? Looking at NetBSD > development, it seems that people are already working on ports to > current OMAP and BeagleBoard type hardware. Does this mean that a > port to the GTA04 would be relatively straightforward? Or is this too > good to be true? I doubt I'll buy GTA04 myself. The hardware looks nice, but at this moment it's a little bit above my price range. Maybe this will change over time... Porting NetBSD to GTA04 is certainly doable. As you've said there is already some sort of support for OMAP boards in NetBSD, so it should be just a matter of getting it to run on GTA04. I guess that with the debug board working it should be a couple of days of work to get the kernel booting. After that however, all the drivers for GTA02 peripherals that NetBSD doesn't support have to be written. This is probably the most time consuming task. > > Thanks again for letting us know what you're doing, > > Nick Sheppard > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v37 for GTA02
For me it would be great to have the choice to select from a menu the folder where to look for the desired file in all the main application included in qtmoko, while actually they just look inside a default folder instead: eyepiece, media player, qdictopia, pictures, etc... urodelo On Sun, 11 Dec 2011 17:51:03 +0100, Radek Polak wrote: Hi, after a small delay i am happy to announce QtMoko v37 also for Freerunner. I have just rebuild the debian package for this release. You can find it here [1], but apt-get update && apt-get upgrade from v35 should work too. I have not tested the release at all, because my Freerunner is currently disassembled and is waiting for new case, so please take when upgrading to v37. Here is list of changes since v36: * doc - fixed toolchain instructions (Rafael Ignacio Zurita) * finger friendly patches for contacts, shutdown, call history, qtmail (Rafael Ignacio Zurita) * added security.debian.org to sources.list (pabs3) * using geomirros for in sources.list (pabs3) * new input biglangscape input method (Rafael Ignacio Zurita) * autorotation script (Rafael Ignacio Zurita) * qx can now launch Qt-X11 apps like fbreader (LD_LIBRARY_PATH problem) * qx can delete X11 lock files (useful if X crashed) * delete qtopia temp dir on start (local sockets work after unclean restart) * fixed singal status polling for AT modems * option to disable signal polling for AT modems * dont poll battery immediately on AT modems * option to disable AT+CCED on AT modem * option to decode operator name for AT modem plugins * support for Exec argument .desktop files Besides this i have figured out, how to quite easily rebuild regular Qt apps for QtMoko so that you dont have to use qbuild. You can look forward very soon for FBReader port (just finishing the .deb package), i hope i can do the same with navit. Any other ideas for cool qt apps that you would like on QtMoko? Regards Radek [1] http://qtmoko.sourceforge.net/debian/qtmoko_37-1_armel.deb -- 用斯斯！ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: uSD corruption
Am 15.12.2011 22:00, schrieb fdvj...@vodafone.it: Hi I have a Kingstone microSD card 8GB. It seems to be reliable for data but if I use it with a running distro, at this moment QtMoko,... file system gets corrupted and I have to format the partition. ... Joif Hallo Joif, when I startet with Freerunner and QTmoko v35 I bought uSD-Cards in the Electronic-Market in Town. It was a a Toshiba 4 GB and a Toshiba 8 GB. The filesystem on it get corrupted once a day. Most times it was possible to repair the uSD-Filesystem by starting the Backup-System, a small QT-Moko in NAND and running: umount /media/card e2fsck -f -y -v /dev/mmcblk0p1 But this was no solution for eternity. I ordered a Moko-tested uSD from Pulster [1], which works fine until today. But: It was a Kingston! Maybe Kingston has different types? It's not easy to find the right one as you see in [2]. [1] http://pulster.de/index.htm?d__om8msd__Speicherkarte_8_GB_microSD_fuer_Openmoko_Freerunner1003.htm [2] http://wiki.openmoko.org/wiki/Supported_microSD_cards -- Frank ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
