Re: testing the free calypso software
I've now prepared a second distro that can be used to flash the calypso with either of the two methods using Michael's loadtool program. This distro uses QTmoko as a base and includes the loadtool-r2 release and both the leo2moko-r1 and moko11 firmware. As such, you do not need an unlock cable (although you can use this distro in conjunction with one) and you do not need to compile anything on your PC or freerunner. Like my initial offering, this distro runs from sdcard and boots from the NOR menu, so you do not need to disturb anything you have in NAND. Full write up at http://winterveldt.co.za/leo2moko-p2.html My thanks to Michael for his efforts so far to free the calypso and also to Radek for his continued work on QTmoko. -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[QtMoko] Problem mounting a nfs directory
Hello everyone, in order to compile something on my freerunner I'd like to use for that a nfs directory+chroot. I edited fstab accordingly and tried to mount: root@neo:/mnt/nfs# mount `pwd` mount: wrong fs type, bad option, bad superblock on 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.type helper program) In some cases useful info is found in syslog - try dmesg | tail or so Consequently I tried to install nfs-common, but: root@neo:/mnt/nfs# apt-get install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nfs-common 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/180 kB of archives. After this operation, 623 kB of additional disk space will be used. Selecting previously unselected package nfs-common. (Reading database ... 12006 files and directories currently installed.) Unpacking nfs-common (from .../nfs-common_1%3a1.2.6-4em1_armel.deb) ... Setting up nfs-common (1:1.2.6-4em1) ... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version [FAIL] Starting NFS common utilities: statd idmapd failed! invoke-rc.d: initscript nfs-common, action start failed. dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) I googled and tried some stuff like apt-get install portmap or apt-get install -f, but with no results. Do you have any suggestion? Thanks a lot, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Problem mounting a nfs directory
On 01/29/2014 06:02 PM, Giacomo 'giotti' Mariani wrote: Hello everyone, in order to compile something on my freerunner I'd like to use for that a nfs directory+chroot. I edited fstab accordingly and tried to mount: root@neo:/mnt/nfs# mount `pwd` mount: wrong fs type, bad option, bad superblock on 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.type helper program) In some cases useful info is found in syslog - try dmesg | tail or so Consequently I tried to install nfs-common, but: root@neo:/mnt/nfs# apt-get install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nfs-common 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/180 kB of archives. After this operation, 623 kB of additional disk space will be used. Selecting previously unselected package nfs-common. (Reading database ... 12006 files and directories currently installed.) Unpacking nfs-common (from .../nfs-common_1%3a1.2.6-4em1_armel.deb) ... Setting up nfs-common (1:1.2.6-4em1) ... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version [FAIL] Starting NFS common utilities: statd idmapd failed! invoke-rc.d: initscript nfs-common, action start failed. dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) I googled and tried some stuff like apt-get install portmap or apt-get install -f, but with no results. Do you have any suggestion? Thanks a lot, Giacomo I've to correct myself, sorry. If I do: root@neo:/mnt/nfs# mount.nfs 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/ /mnt/nfs/ It mounts well: root@neo:/mnt/nfs# mount [...] 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT on /mnt/nfs type nfs4 (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.202,minorversion=0,local_lock=none,addr=192.168.0.200) But there is something that does not seem to work as I expect: even if /home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT it's not empty: root@neo:/mnt/nfs# ls root@neo:/mnt/nfs# and, viceversa, if I create a file on the neo I can't see it on the laptop. Moreover, when I umount it, the file are still there and, even if the remote directory is mounted looking at df the FS space used is from rootfs :-( Thanks, Giacomo -- ## giacomo 'giotti' mariani gpg --keyserver pool.sks-keyservers.net --recv-key 0x99bfa859 O ASCII ribbon campaign: stop HTML mail www.asciiribbon.org ## ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] Problem mounting a nfs directory
On Wed, 29 Jan 2014 18:26:11 +0100 Giacomo 'giotti' Mariani giacomomari...@yahoo.it wrote: On 01/29/2014 06:02 PM, Giacomo 'giotti' Mariani wrote: Hello everyone, in order to compile something on my freerunner I'd like to use for that a nfs directory+chroot. I edited fstab accordingly and tried to mount: root@neo:/mnt/nfs# mount `pwd` mount: wrong fs type, bad option, bad superblock on 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.type helper program) In some cases useful info is found in syslog - try dmesg | tail or so Consequently I tried to install nfs-common, but: root@neo:/mnt/nfs# apt-get install nfs-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: nfs-common 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/180 kB of archives. After this operation, 623 kB of additional disk space will be used. Selecting previously unselected package nfs-common. (Reading database ... 12006 files and directories currently installed.) Unpacking nfs-common (from .../nfs-common_1%3a1.2.6-4em1_armel.deb) ... Setting up nfs-common (1:1.2.6-4em1) ... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version [FAIL] Starting NFS common utilities: statd idmapd failed! invoke-rc.d: initscript nfs-common, action start failed. dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) I googled and tried some stuff like apt-get install portmap or apt-get install -f, but with no results. Do you have any suggestion? Thanks a lot, Giacomo I've to correct myself, sorry. If I do: root@neo:/mnt/nfs# mount.nfs 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT/ /mnt/nfs/ It mounts well: root@neo:/mnt/nfs# mount [...] 192.168.0.200:/home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT on /mnt/nfs type nfs4 (rw,relatime,vers=4,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.0.202,minorversion=0,local_lock=none,addr=192.168.0.200) But there is something that does not seem to work as I expect: even if /home/jack/Programmazione/Openmoko/Distros/QtMoko/CHROOT it's not empty: root@neo:/mnt/nfs# ls root@neo:/mnt/nfs# and, viceversa, if I create a file on the neo I can't see it on the laptop. Moreover, when I umount it, the file are still there and, even if the remote directory is mounted looking at df the FS space used is from rootfs :-( Thanks, Giacomo Hi Giaomo. If you simples cd /mnt/nfs, it should start working. Your current directory is some directory on the root filesystem. When you mount an NFS directory on top of that it doesn't change your current directory. However if you use the full name for the directory you have mounted - /mnt/nfs - then that will lead you to the mounted directory, not your current directory. I hope that makes sense. NeilBrown signature.asc Description: PGP signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Resume bug on 2.6.39 kernel identified! (was QTMoko v55 GTA02 flash issue)
Radek Polak: On Monday, January 20, 2014 05:04:53 PM Jake Drexel wrote: the mmc0 device is actually where the ar6000 (wifi) is conneted. I had the same problem with the 2.6.39 kernel on shr. The issue looks hw and sw related. My wifi-board was not connected very well but with older kernel it still worked, which is strange. Here is the ticket where I tried to document the issue i saw: http://shr-project.org/trac/ticket/2103 Hi, it seems that thanks to your mail we have discovered resume problems on 2.6.39 kernels! I tried rmmod ar6000 and i cant reproduce my resume issues anymore! I had running my dial script over night. Freerunner now shows 333 succesful resumes, while it used to fail after 30 resumes before. So please if you are using 2.6.39 kernel edit /etc/modules, remove or comment out line with ar6000, reboot and report if your resume issues are gone. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community Confirm the removal of that module make the responses of QtMoko for suspend much quicker on my phone. Within my investigation I recognized the qpe process was hanging in disk-sleep state. If that module is included in newer version of Linux kernel it would be probably helpful to look for the changes made. Do we miss only WiFi functionality once the module is removed? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
