Re: [QtMoko] new version of FBReader with Qt4
On Tue, 07 May 2013 19:30:08 +0200 francesco.dev...@mailoo.org wrote: Hi There is a new version of Fbreader [1] and it now uses Qt4. Should it be easier to integrate in QtMoko now? Has someone tried it already? It is not yet in the Debian repositories but I wanted to give it a shot, so I downloaded the source code and I tried to compile it on my GTA02. Unfortunately it fails at some point with some errors related to the code, I think. I opened an issue on github here [2] but no answer yet. If you can take a look at the code, can you give me some suggestion? Thank you. Joif [1] http://fbreader.org/content/fbreader-beta-linux-desktop [2] https://github.com/geometer/FBReader/issues/236 Hi In [2]: QtWaitingSpinner.cpp:89:55: error: no matching function for call to 'min(double, qreal)' looks like std::min() has no idea what a qreal is. You could use qMin() insted. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko PC] bluetooth segfault patch
Hi
Thank you Radek for great instructions for PC build.
There is no bluetooth on my PC so qpe segfaults on start. Here is a
patch to fix it.
diff --git a/qtopiacore/qt b/qtopiacore/qt
--- a/qtopiacore/qt
+++ b/qtopiacore/qt
@@ -1 +1 @@
-Subproject commit e1d064ee4b4046d9b52eae073eea4a3bed7dd6c7
+Subproject commit e1d064ee4b4046d9b52eae073eea4a3bed7dd6c7-dirty
diff --git
a/src/libraries/qtopiacomm/bluetooth/qbluetoothabstractservice.cpp b/
src/libraries/qtopiacomm/bluetooth/qbluetoothabstractservice.cpp index
e43c485..00ffae8 100644 ---
a/src/libraries/qtopiacomm/bluetooth/qbluetoothabstractservice.cpp +++
b/src/libraries/qtopiacomm/bluetooth/qbluetoothabstractservice.cpp @@
-266,6 +266,9 @@ void
QBluetoothAbstractServicePrivate::handleError(const QDB usError error)
quint32 QBluetoothAbstractServicePrivate::registerRecord(const QString
record) {
+if(!m_ifc)
+ return 0;
+
QDBusReplyquint32 reply;
QListQVariant args;
args record;
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Kernel panic on Freerunner QtMoko boot
On Fri, 16 Nov 2012 22:19:24 -0500 Harry Prevor habsti...@gmail.com wrote: About a week ago I installed QtMoko on my Freerunner as it's first distribution and all was well. However, for reasons mostly unrelated to this post the install broke so I decided to reinstall QtMoko using instructions from here: http://sourceforge.net/apps/mediawiki/qtmoko/index.php?title=Installation However, to my surprise I wasn't able to get anything to work. Here's what I've tried so far to no avail: --Flashed the Qi bootloader several times; --Flashed the kernel several times to NAND; [...] I had a similar problem. Somehow it went away. See http://lists.openmoko.org/pipermail/community/2012-January/066196.html http://lists.openmoko.org/pipermail/community/2011-December/065998.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [qtMoko] How Contact selection UI is filled
On Wed, 25 Jan 2012 17:05:40 +0100 Guilhem Bonnefille guilhem.bonnefi...@gmail.com wrote: I still not know precisely what code is running when I select recipients of a SMS. But I found many codes doing similar things, but differently. To check which code is responsible for the functionality you can insert qDebug(__PRETTY_FUNCTION__); in the code you suspect. Build/install QtMoko. switch on logging in QtMoko. SSH to the FreeRunner. tail -f /var/log/messages Push buttons i the phone user interface looking at the tail output. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ubifs/NAND problem?
On Sun, 15 Jan 2012 18:10:11 +0100 Boudewijn wankelwan...@yahoo.com wrote: Hi List, I have problems with NAND, it seems, but I don't know how to troubleshoot it. For a while I have been unable to boot SHR from NAND, but since I had another install on uSD, it didn't really matter. Lately I wanted to move to NAND anyway, to free up the relatively fast uSD for my Phoenux. The Freerunner still won't boot from NAND though. I reflashed with SHR-core (and SHR's ubi-qi), to no avail. After that I flashed QtMoko v35 (and QtMoko's qi v35). No better result either. (For a moment I thought the MD5 sum was incorrect, downloaded again and flashed, but it turned out Sourceforge hid part of the sum when there's no mouseover). Hi Boudewijn, I had a similar problem, couldn't boot anything from NAND(qi or uboot the same). Jffs worked fine. While trying different UBIFS distributions I have accidently flashed kernel to where bootloader should be. Reflashed everything as it should be, and the phone started to boot from NAND. The distrib was QtMoko v35. I think there could be some wrong data or bad blocks somewhere that were erased by flashing kernel to the wrong place. Or some bug was fixed in qi or kernel. Cant check. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko UBIFS problem
On Sun, 18 Dec 2011 23:58:38 + Radek Polak pson...@seznam.cz wrote: On Sunday 18 December 2011 22:49:00 Ivan Matveev wrote: Hello, I can't boot QtMoko v36 fom NAND. Here is the screen of kernel panic. http://file.qip.ru/photo/NTlrXV05/uboot_gena2x-qtmoko_v36-kernel.html This is well known problem. V36 is just experiment ;-) Have you tried v35? I UBIFS in this version should work - i have tested it on my FR and IIRC nobody else had any problems with it. Also please make sure to use qi-v35.udfu. Regards Radek Hello Radek, I'v flashed V35 to NAND. It boots! And its blinding fast! Thank you! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko UBIFS problem
On Sun, 18 Dec 2011 18:11:27 -0500 Brian bn...@rochester.rr.com wrote: On Mon, 19 Dec 2011 01:49:00 +0300 Ivan Matveev imatvee...@nm.ru wrote: Hello, I can't boot QtMoko v36 fom NAND. Here is the screen of kernel panic. http://file.qip.ru/photo/NTlrXV05/uboot_gena2x-qtmoko_v36-kernel.html This probably won't be too helpful since I'm not using ubifs but I've experienced a couple of kernel panics recently. Good Luck, [...] Brian Thank you for your answer. The problem was solved by QtMoko v35 installation. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko UBIFS problem
Hello, I can't boot QtMoko v36 fom NAND. Here is the screen of kernel panic. http://file.qip.ru/photo/NTlrXV05/uboot_gena2x-qtmoko_v36-kernel.html Actually my problem started long time ago. http://lists.openmoko.org/pipermail/community/2010-December/063993.html Some early UBI QtMoko versions worked OK. Then I tried SHR and Debian. After that no UBI image boots. Now my FR is a good platform to test UBIFS improvements :). Thanks for any ideas. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: linmodem
On Tue, 04 Oct 2011 19:06:57 +0200 Ed Kapitein e...@kapitein.org wrote: [1] http://wiki.openmoko.org/wiki/Manually_using_GSM On 09/29/2010 09:19 PM, Ed Kapitein wrote: Hi all, I recently bought another freerunner and i have a plan with my provider that will give me free calls between my family members. Is there someone who ever hookup up two freerunners, using phonecalls? I took a look at [1] that uses a linmodem, software only modem. With this software you can hook up two computers using the soundcards. Is Something simmilar possible wit 2 FR 's? http://en.wikipedia.org/wiki/Circuit_Switched_Data http://en.wikipedia.org/wiki/General_Packet_Radio_Service GPRS is better. You pay per traffic not per time online. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko] qDebug, tUserLog where are the logs?
Hello All, Radek. I'm trying to reserch NeronGPS lost tracks issue. Can't find where output of qDebug(), tUserLog() functons go. Thanks for any help. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] qDebug, tUserLog where are the logs?
On Wed, 5 Oct 2011 02:01:02 +0400 Ivan Matveev imatvee...@nm.ru wrote: Hello All, Radek. I'm trying to reserch NeronGPS lost tracks issue. Can't find where output of qDebug(), tUserLog() functons go. Thanks for any help. Found the messages. They go to syslogd and can be red in /var/log/messages. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTA02 fails to charge
On Tue, 27 Sep 2011 14:46:11 -0400 Phil Vandry van...@tzone.org wrote: I have 2 GTA02v6 Freerunners which don't charge their batteries anymore. The symptoms on both are the same, but it started happening on both phones in different locations and times. The battery state is Charging whether the phone is plugged in to a computer or wall charger, but the battery slowly goes down instead of charging. Had a similar problem. New battery helped. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Building QtMoko
On Tue, 19 Apr 2011 08:04:42 +0200 Radek Polak pson...@seznam.cz wrote: On Monday 18 April 2011 23:56:20 Ivan Matveev wrote: Hello All! Thank you Radek for the QtMoko! I'm trying to complie QtMoko on Debian per instructions at https://github.com/radekp/qtmoko. After: ../qtmoko/configure -device neo an error happens: Basic XLib functionality test failed! You might need to modify the include and library search paths by editing QMAKE_INCDIR_X11 and QMAKE_LIBDIR_X11 Hi, have you already done apt-get build-dep libqt4-dev? This should quite safely install all dependencies. Maybe apt-get install libqt4-dev is enought, but the first command is better. Thank you Radek. After I have added deb-src to sources.list and run apt-get build-dep libqt4-dev ../qtmoko/configure -device neo worked. qtmoko is compiling now! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Building QtMoko
Hello All! Thank you Radek for the QtMoko! I'm trying to complie QtMoko on Debian per instructions at https://github.com/radekp/qtmoko. After: ../qtmoko/configure -device neo an error happens: Basic XLib functionality test failed! You might need to modify the include and library search paths by editing QMAKE_INCDIR_X11 and QMAKE_LIBDIR_X11 in /home/ivm/Downloads/freerunner/QtMoko/git/qtmoko/qtopiacore/qt/mkspecs/linux-g++. configure exited with value 1 at /home/ivm/Downloads/freerunner/QtMoko/git/qtmoko/src/build/bin/configure line 5223 main::bootstrap_qt() called at /home/ivm/Downloads/freerunner/QtMoko/git/qtmoko/src/build/bin/configure line 1786 looks like my Debian is missing some headers or libraries. How can I learn what went wrong? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Firmware Flashed, now UBIFS problem and Kernel Panic
root@neo:~# cat /proc/mtd dev:size erasesize name mtd0: 0020 0001 physmap-flash.0 mtd1: 0004 0002 qi mtd2: 0004 0002 depr-ub-env mtd3: 0080 0002 kernel mtd4: 000a 0002 depr mtd5: 0004 0002 identity-ext2 mtd6: 0f6a 0002 rootfs root@neo:~# ubiattach /dev/ubi_ctrl -m 6 -d 0 -O 2048 UBI device number 0, total 1972 LEBs (250396672 bytes, 238.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB) root@neo:~# mkdir /tmp/qtmoko root@neo:~# mount -t ubifs ubi0_0 /tmp/qtmoko/ You can try: mount -t ubifs /dev/mtdblock6 /tmp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v35
On Mon, 11 Apr 2011 10:13:34 +0200 Radek Polak pson...@seznam.cz wrote: [...] We had problems with ubifs too. Gennady talked to ubifs devs and they would like to see the kernel message and nandump so they could try too look into it. It seems that ubifs is not as stable as jffs2 which was 100% perfect. Only problem is that jffs2 cant do mmap and apt-get does not work without mmap. Jffs2 will never do mmap (according to the main devel it's a lot of complex work because of compression) so we have these options now: * live with bugged ubifs * patch apt-get so that it works without mmap * use the old trick with /var/cache/apt on tmpfs, but this has problems with limited memory and bigger upates/upgrades might not work * use some other flash filesystem - yaffs seems but does not support compression, i havent looked at logfs yet So any suggestions? We could use jffs2 if we link /var/cache/apt to a tiny partition on SD. Then while SD is in huge updates will work, if SD is removed - no apt, but still a runing system. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
On Sat, 05 Feb 2011 11:16:03 +0300 Gennady Kupava g...@bsdmn.com wrote: В Птн, 04/02/2011 в 13:59 +0100, David Garabana Barro пишет: Hi Just flashed qtmoko v31 in NAND. It hangs on first boot with kernel panic: UBIFS error (pid 1): mount_ubifs: 'compressor lzo is not compiled in Kernel-panic - not syncing: VFS: Unable to mount root fs on onknown-block(0,0) Usind qtmoko kernel qi: -rw-r--r-- 1 user group 29088 feb 4 12:59 qi-31.udfu -rw-r--r-- 1 user group 93585408 feb 4 13:03 qtmoko-debian-v31.ubi -rw-r--r-- 1 user group 2218272 feb 4 12:58 uImage-v31.bin Any idea? Hi, i had this error. UBIFS support 2 compression algorithms, zlib and lzo. They can be mixed with one filesystem. You may specify which one will be used then creating new files. It can be scepified as mount option. The default is lzo. lzo is significantly faster but produce bigger files. The qtmoko kernel have only zlib compiled in, is if you just run kernel you'll see your message. To avoid it you should add mount option for mounting rootfs. it's mount -o compr=zlib and kernel parameter rootflags=compr=zlib. this should be active in your bootloader. So everyone who installs QtMoko v31 to NAND and uses Qi shell have this problem? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtomoko v31 boot ploblems
On Fri, 4 Feb 2011 13:59:00 +0100 David Garabana Barro da...@garabana.com wrote: Hi Just flashed qtmoko v31 in NAND. It hangs on first boot with kernel panic: UBIFS error (pid 1): mount_ubifs: 'compressor lzo is not compiled in Kernel-panic - not syncing: VFS: Unable to mount root fs on onknown-block(0,0) Usind qtmoko kernel qi: -rw-r--r-- 1 user group 29088 feb 4 12:59 qi-31.udfu -rw-r--r-- 1 user group 93585408 feb 4 13:03 qtmoko-debian-v31.ubi -rw-r--r-- 1 user group 2218272 feb 4 12:58 uImage-v31.bin Any idea? Same here. http://lists.openmoko.org/pipermail/community/2010-December/063993.html I had QtMoko v28 in NAND(jffs). Installed QtMoko v30(ubifs) to NAND. Worked fine. Installed Debian to SD with install.sh script started from NAND QtMoko. Debian worked Installed SRH(ubifs) to NAND. Worked. Installed QtMoko v30 to NAND. Can't boot. Same error as yours. With some random multiple reflashing of kernel/rootfs/u-boot-env managed to make QtMoko v30 boot from NAND. Upgraded to QtMoko v31. Can't boot. Same error as yours. Kernel complains it cant find root fs. Pity it doesn't show boot options in the panic message. Installed QtMoko v28 to NAND(jffs). Boots fine. QtMoko v31 from SD boots fine and shows regular NAND partition layout. neo:~# cat /proc/mtd dev:size erasesize name mtd0: 0020 0001 physmap-flash.0 mtd1: 0004 0002 qi mtd2: 0004 0002 depr-ub-env mtd3: 0080 0002 kernel mtd4: 000a 0002 depr mtd5: 0004 0002 identity-ext2 mtd6: 0f6a 0002 rootfs Have no idea how to debug this. The problem manifests only on some phones so no hope for help from people who know. Can someone enlighten me how the partitions are marked in NAND? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
On Tue, 28 Dec 2010 22:40:10 +0100
Radek Polak pson...@seznam.cz wrote:
Ivan Matveev wrote:
That's the sources I'v looked at to learn how Qi uses NAND
partitions. Funny
find ./ -exec grep -H ubi '{}' ';'
finds nothing relevant. Am I looking at the right sources?
Ahh sorry, i forgot you need to be on the right branch:
https://github.com/radekp/qi/tree/qtmoko-v28
Thank you.
I think it wold be ideal if Qi wold treat NAND as a regular
partition, i.e. wold read kernel options from
identity-ext2/append-GTA2. I think I could implement that. Looking
for the place in the sources where Qi reads append-GTA02. Have a
little difficulty understanding the sources.
I might be wrong, but that would involve reading jffs2/ubifs/yaffs
and whathever else filesystem. This goes quite against the idea of qi
to keep it simple.
My idea was to put NAND kernel options in to append-GTA02 file on
identity-ext2(mtd5, dfu-util calls it factory) NAND partition.
The partition contains ext2 file system so we don't have to
add jffs/ubifs support to Qi.
Qi already mounts the partition and reads usb file from it.
See:
radekp-qi-b214400/src/cpu/s3c2442/gta02.c
char * append_device_specific_cmdline_gta02(char * cmdline)
[...]
if (!ext2fs_mount()) {
[...]
len = ext2fs_open(usb);
Also Qi already has a parser for append-[device] files.
So we cold just add identity-ext2 partition to the list of partitions
that Qi search for /boot/append-GTA2
and immediately have configurable kernel options for NAND boot.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Qi vs U-boot (was Re: QtMoko v30; UBIFS; can't boot)
On Tue, 28 Dec 2010 16:45:56 +0300 Gennady Kupava g...@bsdmn.com wrote: Please tell me how to do this! I have no religious bind to Qi. To hell with minimalism, let us all use the bootloader that is standard, smart, configurable and well supported. I think easiest way is to use fw_setenv. I rethought, need relatively trivial modification to u-boot to support loading plain file to env variable with something like 'ext2loadvar location [var]'. But this brain-dead by design idea The brain-dead idea is not mine :) /boot/grub/menu.lst require bootloader to support all possible fses (how does qi reads ubifs for kernel parameters, if it has no support for ubi?) No it doesn't require jffs/ubifs support. The identity-ext2(mtd5, dfu-util calls it factory) NAND partition contains ext2 fs. So on linux runing from NAND echo /dev/mtdblock5 /boot ext2 defaults /etc/fstab Navigate to /boot, edit append-GTA02... Natural way for people used to PC bootloader like grub. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi vs U-boot
On Tue, 28 Dec 2010 12:01:41 +0200 Timo Juhani Lindfors timo.lindf...@iki.fi wrote: Ivan Matveev imatvee...@nm.ru writes: As always with automatic someone has to build the mechanism. Qi has it already. Why shell I bother with u-boot numerous(poorly documented) options? I don't intend to flame but u-boot has a long manual: http://www.denx.de/wiki/DULG/Manual Thank you. I will see much more than 1% of kernel parameters in the file. That's indeed complex partly because it is a template that can be used to generate different configuration files. I keep my u-boot configuration in /etc/uboot.conf that reads I agree that passing kernel params is just a small part of u-boot functionality. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
On Mon, 27 Dec 2010 08:33:09 +0300 Gennady Kupava g...@bsdmn.com wrote: Hi, I don't want to go back to u-boot. I disagree - going to Qi is going back, going to u-boot is going forward :) I like Qi's minimalism, automatic setup of many options and text config files. I'v tried u-boot just to be shure. Per istructions at http://wiki.openmoko.org/wiki/U-boot-gena2x I'v downloaded: http://www.bsdmn.com/openmoko/uboot/binary/u-boot_g2x_1.udfu http://www.bsdmn.com/openmoko/uboot/config/environment.in http://svn.openmoko.org/trunk/src/host/devirginator/crc32.pl http://svn.openmoko.org/trunk/src/host/devirginator/envedit.pl Didn't edit environment.in because don't know what to put there. From http://wiki.openmoko.org/wiki/U-boot-gena2x: If you switching from qi, just run boot your distro with Qi, do cat /proc/cmdline and compare/update parameters in config file. Cant do that because I can only boot from SD but the params will be different then? So lets use the sample environment.in as it is. ./envedit.pl -s 262144 -f environment.in u-boot_env.in dfu-util -a u-boot -D u-boot_g2x_2.udfu dfu-util -a u-boot_env -D u-boot_env.in A press on the power button. FR emits a barely audible click and then nothing, the screen stays blank. OK, at least I'v removed supposedly offending options from u-boot_env partition. Lets try qi-v30.udfu again. TADA! It boots ubifs QtMoko from NAND. So I think something was wrong with u-boot_env partition, params stored in there or the partition size. echo 'rootflags=compr=zlib' p1/append-GTA02 Are you sure qi is really reading this? i am sure it is not. I agree. In Qi sources I could only find that it reads 'usb' file from 'identity-ext2' partition. No, you need ensure that this options REALLY passed to kernel somehow. I almost sure they not. In this case I had to make sure some options are NOT passed to the kernel :). All the right options are compiled in Qi. Can I modify u-boot environment from QtMoko running from SD? u-boot can boot any known distro without problems, from sd, ubi or jffs2. in hard cases of unusual fses you can just put kernel to splash NAND partition (named 'depr' in your qi) and boot it with rootfs on sd. Thanks I'll keep that in mind in case of a hard case. I think it is also possible to make such config that appends kernel params load from file on external fs, like in qi, but who needs this... I think its not external fs that matters but u-boot_env format. dfu-util -a u-boot_env -U u-boot_env.in Now we have u-boot_env.in file containing params. How do we study whats inside? Strings? Errr. Oh yes we have envedit.pl. How do we use it, and where is the doc? Run it with no params, it outputs '���6'. Look inside, there is: -i fileread environment from file (default: use empty -p print environment in human-readable form to stdout\n. ./envedit.pl -i u-boot_env.in4.problemed -p warning: environment is 262144 bytes, expected 16384 CRC error: expected 0x7b25213d, got 0x8f4d6b85 Oh yes there is -s option. ./envedit.pl -s 262144 -i u-boot_env.in4.problemed -p At last it works! But the output doesn't look like the environment.in. How do I compile the output back in to u-boot_env.in4 after editing? Can this be done from FR with no PC? nandump, edit, crc32, nandwrite? Oh my... If u-boot_env partition contained a decent ext2(like identity-ext2 partition does) you could download it with dfu-utl, mount, edit files, put back to the phone. On a booted FR you could just mount -t ext2 /dev/mtdblock2 /mnt/whatever edit files... Thank you for the discussion, it gave me a kick in the right direction. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
On Mon, 27 Dec 2010 17:40:54 +0100
Radek Polak pson...@seznam.cz wrote:
Hi Radek,
thank you for the great distrib! I'm using QtMoko since v20.
[...]
As Gennady already pointed out, you should use qi which has ubifs
boot parameters compiled in. Please flash this [1]
That is the Qi vesion I use.
The QtMoko v30 boot problem is solved by reloading u-boot_env
patition to Gennady's sample config. I think debian install.sh with Qi
option polluted u-boot_env kernel options.
Does Qi read u-boot_env?
qi or if you want
to compile from sources you can use this [2] link.
That's the sources I'v looked at to learn how Qi uses NAND partitions.
Funny
find ./ -exec grep -H ubi '{}' ';'
finds nothing relevant. Am I looking at the right sources?
I think it wold be ideal if Qi wold treat NAND as a regular partition,
i.e. wold read kernel options from identity-ext2/append-GTA2.
I think I could implement that. Looking for the place in the sources
where Qi reads append-GTA02. Have a little difficulty understanding
the sources.
In
radekp-qi-c38b062/src/cpu/s3c2442/gta02.c
i see dynparts(NAND partitions) location and size appended to cmdline.
After
len = ext2fs_open(usb);
Qi reads 'usb' file and appends g_ether parmas to cmdline.
Also there is
radekp-qi-c38b062/src/phase2.c
that looks like it can be reading append-[device] file.
Am I looking at the right place?
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Qi vs U-boot (was Re: QtMoko v30; UBIFS; can't boot)
Hi Gennady! Lets burn some linux.org.ru style flame! I don't want to go back to u-boot. I disagree - going to Qi is going back, going to u-boot is going forward :) I like Qi's minimalism, automatic setup of many options and text config files. Automatic setup is done by person who provide you with Qi. If someone start supply u-boot_env with distros, u-boot setup will be equally automatic. As always with automatic someone has to build the mechanism. Qi has it already. Why shell I bother with u-boot numerous(poorly documented) options? I know u-boot is more configurable, but I just want to boot. If I start developing an FR kernel I'l learn u-boot ways. A regular user wold like a bootloader as configurable as grub, not a set of cryptic scripts we have with u-boot. It's also possible to setup u-boot like qi, 'read kernel first from sd part 1, boot if loads, then try from sd part 2, boot if loads, then from nand'. All with 10 lines in config file. Just noone need it. No one needs the good stuff :). What 'text config files' in Qi you talking about? Does it have config files at all? If you mean ability to append kernel parameters this not like u-boot config files, only 1% of that flexibility. I think if I wget http://www.bsdmn.com/openmoko/uboot/config/environment.in less environment.in I will see much more than 1% of kernel parameters in the file. Can you give an example of a valuable non kernel parameter bootloader parameter? Minimalism? 1. You mean that Qi works only on Freerunner, has no support to anything else? I do agree that Qi is not as supported as u-boot(thank you for your advice on u-boot, sincerily). We shell spread word on Qi to make it more popular and supported and make it an embedded grub. 2. Or that you need to use NOR u-boot to flash something to NAND as qi can't do it? Decision to have 2 bootloders(NOR and NAND) in FR was a wise one and was a result of experience with neo1973 that was easy to brick by flashing a bad bootloader. With this design one of the bootloaders can afford to be minimalistic. 3. Or that nothing except kernel parameters may be configured without recompilation? What else do we(users, application developers) need? 4. Or that it can't display anything on screen so you have to decode errors by amount of blinks? If you press power button at the right moment you will have loglevel=8. You will see kernel debug, not bootloaders. Why should a user care? Does every FR user have to develop a bootloader? 5. Or that it adds 'quiet' kernel options by default, so you can't see boot logs? See 4. on power button. I'v tried u-boot just to be shure. [...] Didn't edit environment.in because don't know what to put there. You must edit it to boot, mine is only example suitable only for my custom setup. Well, I must edit environment.in. How shell I know what do I put there? I'm no u-boot expert. Can you provide the catch all u-boot config? That wold be a good u-boot advocacy. From http://wiki.openmoko.org/wiki/U-boot-gena2x: [...] A press on the power button. FR emits a barely audible click and then nothing, the screen stays blank. This only may happen if you battery discharged or 'default' boot way is not setup properly. Try menu with power+aux like described on wiki. The battery was full. There was no u-boot setup whatsoever only sample environment.in. I think qi is NOT reading u-boot_env, so you just had different Qi version before. I'm waiting for Radek's comment on this. Qi's sources are not easy, no stdlib functions. In the course of researching the 'no NAND QtMoko' situation I'v tried the following combinations: qi-s3c2442-master-hist_3b8513d8b3d9615e.udfu; uImage-v26.bin; qtmoko-debian-v26.jffs2; did boot OK qi-v28.ubifs.udfu; uImage-v28.bin; qtmoko-debian-v28.ubi; didn't boot qi-v30.udfu; uImage-v30.bin; qtmoko-debian-v30.ubi; didn't boot [...] I think it is also possible to make such config that appends kernel params load from file on external fs, like in qi, but who needs this... I think its not external fs that matters but u-boot_env format. Seem i didn't describe my idea very well. I think it's possible to write such env for u-boot, that will read text 'append' portion of kernel params like qi does. So, you'll have similar fun of editing text files with kernel options, like you have in Qi. Please tell me how to do this! I have no religious bind to Qi. To hell with minimalism, let us all use the bootloader that is standard, smart, configurable and well supported. Gennady I admire yours contribution to the community. Please do not be offended. I was frustrated by FR suddenly not booting. provocative content Still I like Qi better. Small program that does only 1 thing is the UNIX way /provocative content ___ Openmoko community mailing list community@lists.openmoko.org
[solved] Re: dfu-util doesn't list NAND partitions
Hi Martix, thank you for the reply. Hi, I had this problem few months ago. You should flash u-boot to NAND by nandwrite and run dynpart and dynenv set u-boot_env in NAND u-boot console. see: http://wiki.openmoko.org/wiki/Nandwrite Then you can flash all partitions (including NAND u-boot) via dfu-util from running NAND u-boot. the issue described at http://docs.openmoko.org/trac/ticket/2348 I think we have different cases. In my case dfu-util downloads/uploads fine if you name the partition right. But it didn't list the partitions with dfu-util --list as it was in ran time mode. The partitions have different names in dfu-util/u-boot/qi so I didn't know how to upload(FR-PC) 'identity-ext2'(qi name) partition. I'v found a workaround dfu-util -a non-existent-partition -U anyfile dfu-util says bad words you on PC console FS screens says 'bla bla switching to DFU mode' dfu-util --list Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=0, name=RAM 0x3200 Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=1, name=u-boot Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=2, name=u-boot_env Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=3, name=kernel Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=4, name=splash Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=5, name=factory Found DFU: [0x1d50:0x5119] devnum=76, cfg=0, intf=0, alt=6, name=rootfs ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
dfu-util doesn't list NAND partitions
Hi, the issue described at http://docs.openmoko.org/trac/ticket/2348 is still there. Tried with 2 versions of dfu-util dfu-util --intf 0 -l dfu-util - (C) 2007 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Found Runtime: [0x1d50:0x5119] devnum=53, cfg=0, intf=2, alt=0, name=USB Device Firmware Upgrade ./dfu-util --intf 0 -l dfu-util - (C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY dfu-util does currently only support DFU version 1.0 Found Runtime: [0x1d50:0x5119] devnum=55, cfg=0, intf=2, alt=0, name=USB Device Firmware Upgrade ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
From: Ivan Matveev supp...@monicar.ru To: community@lists.openmoko.org Subject: Re: QtMoko v30; UBIFS; can't boot Date: Mon, 27 Dec 2010 03:30:57 +0300 X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; i486-pc-linux-gnu) Organization: MoniCar Btw, don't know where this is set in qi, but you may try u-boot: http://wiki.openmoko.org/wiki/U-boot-gena2x Thank you for your replies. I don't want to go back to u-boot. I think my problem started after I'v installed debian to SD per instructions found at http://wiki.debian.org/DebianOnFreeRunner with install.sh(http://pkg-fso.alioth.debian.org/freerunner/install.sh). I'v told the install.sh to configure Qi. Probably that was the mistake. Now I'm trying to figure out what can be configured wrong. I'v read the script... Its long... Can't find anything suspicious. According to this: http://wiki.openmoko.org/wiki/Qi#Installation Qi...is mount the identity partition and get from there the globally unique MAC address for the USB over Ethernet function instead of the random one that is otherwise used (If this doesn't work (like with a GTA01) you may use kernel-commandline parameters g_ether.dev_addr= and g_ether.host_addr= for the mac in device and host mode of the usb-ether module). bad kernel options can be in identity or in u-boot environment partitions. QtMoko v30 booted from SD. neo:~# cat /proc/mtd dev:size erasesize name mtd0: 0020 0001 physmap-flash.0 mtd1: 0004 0002 qi mtd2: 0004 0002 depr-ub-env mtd3: 0080 0002 kernel mtd4: 000a 0002 depr mtd5: 0004 0002 identity-ext2 mtd6: 0f6a 0002 rootfs mount -t ext2 /dev/mtdblock5 p1 ls p1 bt imei lost+found sn usb wlan echo 'rootflags=compr=zlib' p1/append-GTA02 No joy. Same result: kernel complains that lzo is not compiled in. Maybe it misses some modules? Maybe I shell put them in identity-ext2? Have to research more... BTW tried Gennadys script to decode u-boot environment(http://www.bsdmn.com/openmoko/gpsfix/env/envedit.pl). It complains that crc32 function is not defined. Can I modify u-boot environment from QtMoko running from SD? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
To: community@lists.openmoko.org Subject: Re: QtMoko v30; UBIFS; can't boot Date: Mon, 27 Dec 2010 03:30:57 +0300 X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; i486-pc-linux-gnu) Organization: MoniCar Btw, don't know where this is set in qi, but you may try u-boot: http://wiki.openmoko.org/wiki/U-boot-gena2x Thank you for your replies. I don't want to go back to u-boot. I think my problem started after I'v installed debian to SD per instructions found at http://wiki.debian.org/DebianOnFreeRunner with install.sh(http://pkg-fso.alioth.debian.org/freerunner/install.sh). I'v told the install.sh to configure Qi. Probably that was the mistake. Now I'm trying to figure out what can be configured wrong. I'v read the script... Its long... Can't find anything suspicious. According to this: http://wiki.openmoko.org/wiki/Qi#Installation Qi...is mount the identity partition and get from there the globally unique MAC address for the USB over Ethernet function instead of the random one that is otherwise used (If this doesn't work (like with a GTA01) you may use kernel-commandline parameters g_ether.dev_addr= and g_ether.host_addr= for the mac in device and host mode of the usb-ether module). bad kernel options can be in identity or in u-boot environment partitions. QtMoko v30 booted from SD. neo:~# cat /proc/mtd dev:size erasesize name mtd0: 0020 0001 physmap-flash.0 mtd1: 0004 0002 qi mtd2: 0004 0002 depr-ub-env mtd3: 0080 0002 kernel mtd4: 000a 0002 depr mtd5: 0004 0002 identity-ext2 mtd6: 0f6a 0002 rootfs mount -t ext2 /dev/mtdblock5 p1 ls p1 bt imei lost+found sn usb wlan echo 'rootflags=compr=zlib' p1/append-GTA02 No joy. Same result: kernel complains that lzo is not compiled in. Maybe it misses some modules? Maybe I shell put them in identity-ext2? Have to research more... BTW tried Gennadys script to decode u-boot environment(http://www.bsdmn.com/openmoko/gpsfix/env/envedit.pl). It complains that crc32 function is not defined. Can I modify u-boot environment from QtMoko running from SD? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v30; UBIFS; can't boot
Hello All, Radek Trying 2010-12-06 03:03 qi-v30.udfu 2010-12-06 02:11 qtmoko-debian-v30.ubi 2010-12-06 03:03 uImage-v30.bin qi complains that lzo compressor is mot compiled in ubifs. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
On Sat, 25 Dec 2010 19:10:31 +0300 Ivan Matveev imatvee...@nm.ru wrote: Hello All, Radek Trying 2010-12-06 03:03 qi-v30.udfu 2010-12-06 02:11 qtmoko-debian-v30.ubi 2010-12-06 03:03 uImage-v30.bin qi complains that lzo compressor is mot compiled in ubifs. it wasn't qi complaining, it was the kernel. I am able to boot with SHR kernel uImage-2.6.34-r4-oe15-om-gta02.bin, but qpe crashes right after start with SHR kernel. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
