Re: AtMoko v35 incoming SMS tone missing?
2011/5/18 Francesco De Vita fdvj...@vodafone.it: Hi, I have a similar problem but only when I send a message long more than one page, I explain: I send a sms, say it is long 2 pages, after that my moko doesn't receive incoming sms and I have to restart it. But consider that the issues with long sms' are old and to date they seem to be unsolved, I don't know if it is really related to that issue. Yep, I'm one of the guys (there is at least another one) who missed SMS and I write indeed always very long SMS. Will see whether I find my OpenMoko and test it ... Jens ___ 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
Am 08.05.2011 11:23, schrieb Noel: Anyway it could be a problem related to ubifs instability, which is a topic recently discussed in mailing list [1]. You can follow that tread and try to: It happens to me every time I boot from SD card with a linux kernel different (at least older) then qtmoko/v31/nand one. I can confirm this. My ubifs errors always happened after I started Debian from SD card. PS: I have a nanddump of the faulty images. According the ubifs FAQ one should not bother the developers with errors resulting from using old ubifs code, so I haven't send it to anyone ... Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Useful nandump? (Was: Re: qtmoko v35)
Am 10.02.2011 12:53, schrieb Gennady Kupava: The ubifs has different options to decrease stability and decrease performance, like disabling bulk read and enabling jffs-style synchronous writes. I guess it's better to try em first. OK Also i talk to ubifs guys on irc, they look like quite open to questions, but first we need something reproducible. Guy who'll have ubifs trubles please try to: 1. disable bulk read in fstab and check if problem will still exist. 2. do nanddump and post it or try to reproduce bug with nandsim. (i guess ubifs guys can fix problem in case if such dump exist quite fast) Is nanddump required? I tried to make a copy of my old destroyed nand partition and because loop-back mounting failed I saved my data with dd. Following http://www.linux-mtd.infradead.org/faq/ubifs.html#L_ubifs_nandsim: # modprobe nandsim first_id_byte=0x20 second_id_byte=0xaa \ third_id_byte=0x00 fourth_id_byte=0x15 # dd if=OpenMoko.Flash.Backup.April1 of=/dev/mtd0 bs=2048 # modprobe ubi mtd=0 FATAL: Error inserting ubi (/lib/modules/2.6.37+/kernel/drivers/mtd/ubi/ubi.ko): Invalid argument Tried also modprobe ubi mtd=1 ... Kernel log: [33221.063532] [nandsim] warning: write_byte: command (0x90) wasn't expected, expected state is STATE_READY, ignore previous states [33221.063543] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [33221.063550] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [33221.063556] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [33221.063563] [nandsim] warning: read_byte: unexpected data output cycle, state is STATE_READY return 0x0 [33221.063571] NAND device: Manufacturer ID: 0x20, Chip ID: 0xaa (ST Micro ) [33221.063590] flash size: 256 MiB [33221.063594] page size: 2048 bytes [33221.063598] OOB area size: 64 bytes [33221.063602] sector size: 128 KiB [33221.063605] pages number: 131072 [33221.063609] pages per sector: 64 [33221.063612] bus width: 8 [33221.063616] bits in sector size: 17 [33221.063619] bits in page size: 11 [33221.063623] bits in OOB size: 6 [33221.063626] flash size with OOB: 270336 KiB [33221.063631] page address bytes: 5 [33221.063635] sector address bytes: 3 [33221.063639] options: 0x8 [33221.066121] Scanning device for bad blocks [33221.070456] Creating 1 MTD partitions on NAND 256MiB 1,8V 8-bit: [33221.070475] 0x-0x1000 : NAND simulator partition 0 [33239.745490] UBI: attaching mtd0 to ubi0 [33239.745499] UBI: physical eraseblock size: 131072 bytes (128 KiB) [33239.745505] UBI: logical eraseblock size:129024 bytes [33239.745510] UBI: smallest flash I/O unit:2048 [33239.745514] UBI: sub-page size: 512 [33239.745519] UBI: VID header offset: 512 (aligned 512) [33239.745524] UBI: data offset:2048 [33239.745634] UBI error: validate_ec_hdr: bad VID header offset 2048, expected 512 [33239.745641] UBI error: validate_ec_hdr: bad EC header [33239.745646] UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0 [33239.745675] UBI error: ubi_init: cannot attach mtd0 [33239.745853] UBI error: ubi_init: UBI error: cannot initialize UBI, error -22 [33245.933633] UBI error: ubi_init: UBI error: cannot initialize UBI, error -19 # modprobe ubi # mount -t ubifs /dev/ubi0_0 /mnt/usb/ mount: wrong fs type, bad option, bad superblock on /dev/ubi0_0, Is this useful? Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko v35
Hi, Am 05.04.2011 09:24, schrieb Radek Polak: i have uploaded new stable qtmoko v35 images to sourceforge now [1]. thanks for the new version. I think it is the best distribution for OpenMoko nevertheless I'm sure the device is still not useable as phone :-( My observations: * SMS are recieved after reboot only (wasn't this fixed long time ago?) * Imported SMS from the SIM card are put into Inbox, even SMS I sent (expected them in Sent). I also cannot move them manually. * As usual it is not possible to write SMS with the integrated keyboard as it misses many characters (non-English locale). I prepared months ago an ugly patch for this but could never test it as I always fail to compile QtMoko (configure requires days, some stuff (such as Qt) is build without need, ...). Maybe it's now easier using the Debian packages but I really doubt that I will try it again, maybe with the new GTA04. My last QtMoko installation died some days after the installation (v31 or v32) with an ubifs related error. Is there anything known about this or should I expect it again? Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v26
On Sat, Aug 28, 2010 at 10:31:23PM +0200, Radek Polak wrote: qtmoko has new v26 release. You can get it from our sourceforge page [1]. thanks for this! I downloaded the kernel and extracted the modules from the tgz to revive my non-booting Debian system on SD card and now it works. Great. After a powerloss I have filesystem errors in the flash. But using the qtmoko v26 kernel I have no access to /dev/mtdblock6 to repair I see only: # cat /proc/mtd dev:size erasesize name mtd0: 0020 0001 physmap-flash.0 mtd1: 1000 0002 neo1973-nand On SHR I got many more mtd? nodes. Where is the rootfs on flash? PS: I would also test the new 2.6.32 (or 34) kernel of Radek. Can it be added to the SourceForge download page? Thanks. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] build error
On Thu, Jun 10, 2010 at 10:41:17PM +0200, Radek Polak wrote: Ricardo Martinez wrote: I'm getting the following error when trying to build Qtmoko on Ubuntu-Lucid: /home/ricardo/qtmoko/qtmoko/src/3rdparty/applications/omhacks/omhacks/batte ry.c:32: error: ‘PATH_MAX’ undeclared here (not in a function) hmm i saw this error already someone had it. It's best to avoid using PATH_MAX as e.g. the Hurd operating system removed useless limitations and doesn't support this as well. So if it's possible to eliminate usage of PATH_MAX ... Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qi-bootmenu-0.1 for GTA02
On Tue, May 18, 2010 at 01:00:01AM +0200, Marc Andre Tanner wrote: On Sun, May 16, 2010 at 11:54:50AM +0200, Jens Seidel wrote: On Sat, May 15, 2010 at 11:20:03PM +0200, Torfinn Ingolfsen wrote: Still, the AUX press is needed. I can confirm this. I also use the patched Qi and have to press AUX. The idea was to only show the menu upon AUX press. If you want the bootmenu everytime then 'hide' the other regular partitions via noboot-GTA02 files. OK, that's simple to do. Nevertheless I wonder where this idea comes from? Why not always display the menu by default? (There could be a default boot without AUX press after some seconds of no action instead of waiting for user input.) Questions: flash partitions are not scanned? Why? The reason is that it was too slow to mount the jffs2 filesystem (it almost doubled the time from boot up to the menu). ubifs should be faster but I haven't really tried it. I would have no problem waiting one or two seconds longer. Currently I have to boot into NAND from the NOR bootloader as the bootmenu doesn't provides it, right? Is it possible to use better names (Debian or maybe 1. partition SD card) in the boot menu instead of /dev/mtd... You can put an image to /boot/bootmenu.png which will be displayed along the partition name. I could probably read display the partition label if set. Patches welcome. OK. Remarks: http://www.brain-dump.org/projects/qi-bootmenu/#faq After downloading the kernel and bootloader they can be flashed to your device like any other distribution with dfu-util. is confusing. qi-bootmenu is *no* real distribution but just a kernel image (with embedded initrd). Reading this sentence I was not sure whether I need to create a new partition somewhere for the boot loader. The bootloader and kernel can be flashed as you would do with every other bootloader / kernel that you want to install into NAND flash. Better? Yep, it is. The initscripts of qi-bootmenu-system are checking /proc/cmdline for a variable called qi-bootmenu-args and pass it to qi-bootmenu upon it's execution. This can be used to tweak the behaviour of the boot menu application via first stage bootloader arguments. Currently the flash partition /dev/mtdblock6 is ignored using this method. Mhm, how can I set a kernel command line for a kernel started from /dev/mtdblock6? I also do not understand the last sentence, probably it mentions the trouble I'm seeing. You can change the kernel command line by creating/modifying the file under /boot/append-GTA02 in the relevant partition. But /dev/mtdblock6 doesn't contain a filesystem!!? I don't see a way to modify the parameters for qi-bootmenu's kernel. However the above paragraph means something different. The first stage bootloader passes: qi-bootmenu-args=\-i /dev/mtdblock6\ Ah, thanks. This is not configurable but hardcoded, right? In this case I suggest to drop the info from the end user docu. to the initramfs kernel where the initscript reads it and passes it on to the qi-bootmenu Yep, I assumed this but as one has no way to change the parameter without recompiling src/cpu/s3c2442/gta02.c it's a useless information for me ... which ignores the flash partition. OK. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qi-bootmenu-0.1 for GTA02
On Sat, May 15, 2010 at 11:20:03PM +0200, Torfinn Ingolfsen wrote: On Sat, May 15, 2010 at 4:24 PM, Dave Ball openm...@underhand.org wrote: This is the case if you have installed Marc's patched Qi. Which is this one , yes? http://www.brain-dump.org/projects/qi-bootmenu/qi-s3c2442-bootmenu-0.1.udfu If your freerunner is booting from SD card by default, and only displaying the bootmenu when pressing AUX while booting, then you're still using standard qi rather than the patched version. But how can it be, when I have installed the above qi? I even downloaded and installed it again, just to make sure. Still, the AUX press is needed. I can confirm this. I also use the patched Qi and have to press AUX. Nevertheless it doesn't matter when I press AUX, it's not so complicated as when one tries to skip the first boot partition :-) Questions: flash partitions are not scanned? Why? Is it possible to use better names (Debian or maybe 1. partition SD card) in the boot menu instead of /dev/mtd... Remarks: http://www.brain-dump.org/projects/qi-bootmenu/#faq After downloading the kernel and bootloader they can be flashed to your device like any other distribution with dfu-util. is confusing. qi-bootmenu is *no* real distribution but just a kernel image (with embedded initrd). Reading this sentence I was not sure whether I need to create a new partition somewhere for the boot loader. The initscripts of qi-bootmenu-system are checking /proc/cmdline for a variable called qi-bootmenu-args and pass it to qi-bootmenu upon it's execution. This can be used to tweak the behaviour of the boot menu application via first stage bootloader arguments. Currently the flash partition /dev/mtdblock6 is ignored using this method. Mhm, how can I set a kernel command line for a kernel started from /dev/mtdblock6? I also do not understand the last sentence, probably it mentions the trouble I'm seeing. http://repo.or.cz/w/qi-bootmenu-system.git/blob/HEAD:/flash-kernel.sh tries to flash uImage-$MACHINE.bin but http://www.brain-dump.org/projects/qi-bootmenu/#download provides uImage-GTA02-bootmenu-0.1.bin. I will continue testing this bootloader. I like it already but missing flash support is not nice. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Triggering Literki from command line?
On Fri, Apr 16, 2010 at 07:43:09PM +0300, Timo Jyrinki wrote: 2010/4/16 Neil Jerram neiljer...@googlemail.com: literki But is that what you meant? He certainly meant unhiding the keyboard of already running literki process. In this case I'm sure xwit can do it. It allows access to many basic X functions, see xwit(1). Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'opkg list-upgradable' lists up-to-date packages on latest SHR unstable
On Sun, Mar 14, 2010 at 04:20:58PM +0100, Jan Girlich wrote: r...@om-gta02:~# opkg list-upgradable python-edbus - 0.3.1+svnr46504-ml0.4 - 0.3.1+svnr46510-ml0.4 [...] r...@om-gta02:~# opkg install python-edbus Package python-edbus (0.3.1+svnr46510-ml0.4) installed in root is up to date. Can you check your file /usr/lib/opkg/status? Does it mention python-edbus twice (or check the output of opkg list_installed)? If yes this is an old problem :-( I currently try to fix a broken /usr/lib/opkg/status as well. My file was truncated and I fixed it by reinstalling all packages found via ls /usr/lib/opkg/info/*.list but not available in status. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Some questions about TangoGPS
Hi dehqan65, please follow standard mailing list etiquettes and use a proper name. On Fri, Jan 08, 2010 at 12:01:19PM +0330, dehqan65 wrote: In The Name Of God The compassionate merciful I'm not sure whether you know that at least I and probably many other people just stop reading after this line. I strongly suggest that you write in your name and not in the name of others. That's also not a religious list. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GSM Network Time
Hi, (Alex, is it really so hard for you to properly avoid top postings and to remove useless parts?) On Tue, Jan 05, 2010 at 04:29:06AM +1100, Alex (Maxious) Sadleir wrote: On Tue, Jan 5, 2010 at 4:25 AM, Esben Stien b...@esben-stien.name wrote: Any way to extract the time from the GSM network and have the time set based on this?. Many phones have this capability. Really? All phones I know about require me to input the time after I removed the battery for a longer time. It would also be nice to set the time based on GPS, when that is available, but often when indoors, only GSM works. GPS in indeed used for synchronisation, but you have to start an applications such as tangogps first (on SHR). SHR already does both (GSM and GPS). You should set the local timezone - http://trac.shr-project.org/trac/wiki/Tweaks#Timezone As far as I know only the timezone is extracted from GSM. I even read the source code to guess whether GSM is able to set time but didn't find any hint. On SHR also a timeserver is used (requested every 10min IIRC) once you setup the network. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Buzz fix (Was: Re: [Shr-User] Quick e-mail poll: Still using your Freerunner?)
On Fri, Jan 01, 2010 at 07:26:37PM +0100, Esben Damgaard wrote: Yes and no. I have two Freerunners (and a gta01 that collects dust). One without buzzfix. Using it for testing, programming and playing. Other one with buzzfix and using it as primary phone. I'm curious, do you notice any difference between the buzz fixed one and the other? I read that only a few phones are affected by the buzz problem but nearly all (including the buzz fixed ones) have major problems with audio quality (noise, echo). So I wonder whether it's worth to get such a fix. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Debian packages of QtMoko (Was: Re: QtMoko v15)
On Mon, Dec 14, 2009 at 10:08:53AM +0100, Atilla Filiz wrote: Can I upgrade my NAND image(from v14) without a fresh install? The main question is: Exist Debian packages of QtMoko? This would solve a lot of upgrade issues. I once tried building QtMoko on my Freerunner but since I had to patch the build system, to restart the make process after internal compiler errors at least once per day (by increasing swap and reducing the optimisation level) and didn't finished compiling in approximately two weeks I stopped :-( Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Navit - unusable?
Hi, I always wondered how people use navit. I started it already a few times but find it (in contrast to tangogps) completely unusable. Once I start it I just get an empty background. Shouldn't it display a map? I read http://wiki.openmoko.org/wiki/Navit and tried the described Easy Way but do not find the dialog to download maps. I haven't tried the command line solution yet as I believe a graphical application should not depend on it. How to add a destination? I select as Country Germany, and my City followed by Street and Number. And now? Any click on Map, Bookmark and Destination does nothing. I assume I have to be online for this step, this is fulfilled. I use version 1:0.1.0+svnr2735-r0.4 from the default feed. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Symptoms of failed #1024 fix
On Sun, Nov 01, 2009 at 08:54:50PM +0100, Jens Seidel wrote: On Sun, Nov 01, 2009 at 05:57:28PM +0100, Christophe M wrote: /var/log/frameworkd.log: 2009.11.01 17:25:06.733 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds I just want to confirm that these symptoms mean that the soldering was not properly done so that no capacitor is used instead of the 10uF or 22uF one. I will ask the engineer who performed this task for me to do it again to get a proper phone. I get no prompt for the SIM pin which worked in the past and also mickeyterm exits with a DBus exception before I can enter a single command. As the engineer told me he isn't sure about the soldering I assumed it wasn't done well ... If it works again after the resoldering I will drop a mail. Resoldering was performed and now all modem related problems vanished. Also my device is now #1024 bug free :-)) Don't know about the increase of battery time as I nearly always have it connected to USB but maybe it's time to unplug it ... Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Symptoms of failed #1024 fix
Hi, you performed a #1024 bug and can no longer access to modem? You get in /var/log/frameworkd.log: 2009.11.01 17:25:06.733 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds 2009.11.01 17:25:06.743 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.11.01 17:26:08.523 ogsmd.modem.abstract ERRORcould not open channel UNSOL, retrying in 2 seconds 2009.11.01 17:26:08.533 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' 2009.11.01 17:26:21.733 ogsmd.modem.abstract ERRORcould not open channel CALL, retrying in 2 seconds 2009.11.01 17:26:21.743 ogsmd.modems.ti_calypso INFO Requesting new channel from 'fso-abyss' This happened to me too on every boot of SHR. I just want to confirm that these symptoms mean that the soldering was not properly done so that no capacitor is used instead of the 10uF or 22uF one. I will ask the engineer who performed this task for me to do it again to get a proper phone. I also want to mention that I did not observed other problems. The device boots fine, the touchscreen and USB works, ... GPS failed for me but maybe I did not properly plugged the antenna. Some programs such as Cellhunter stop now with: An exit code of 1 was returned from /usr/bin/cellhunter.py So even if the capacitor cannot properly solded again I have a fine device :-) Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Symptoms of failed #1024 fix
On Sun, Nov 01, 2009 at 05:57:28PM +0100, Christophe M wrote: /var/log/frameworkd.log: 2009.11.01 17:25:06.733 ogsmd.modem.abstract ERRORcould not open channel MISC, retrying in 2 seconds I just want to confirm that these symptoms mean that the soldering was not properly done so that no capacitor is used instead of the 10uF or 22uF one. I will ask the engineer who performed this task for me to do it again to get a proper phone. I have the same error while I'm on roaming but I haven't done the 1024 fix so I'm not sure it's related ... There was at least a further Google hit on the messages above with relation to a #1024 bugfix and I just tried to confirm it. I get no prompt for the SIM pin which worked in the past and also mickeyterm exits with a DBus exception before I can enter a single command. As the engineer told me he isn't sure about the soldering I assumed it wasn't done well ... dmesg outputs: [ 1068.535000] modem wakeup interrupt [ 1081.725000] modem wakeup interrupt [ 1094.915000] modem wakeup interrupt [ 1108.11] modem wakeup interrupt [ 1121.34] modem wakeup interrupt [ 1134.54] modem wakeup interrupt [ 1147.74] modem wakeup interrupt [ 1160.935000] modem wakeup interrupt [ 1174.125000] modem wakeup interrupt [ 1187.31] modem wakeup interrupt [ 1200.51] modem wakeup interrupt On the other hand I did most tests (except the initial ones) with a disassembled device (without GSM and GPS antenna, no WLAN module and battery) ... If it works again after the resoldering I will drop a mail. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR-U] opkg displays some packages twice
Hi, I have some opkg issues recently. r...@om-gta02:~# opkg list | grep opkg libopkg-dev - 0.1.6+svnr215-r4 - Opkg Package Manager libopkg0 - 0.1.6+svnr215-r4 - Opkg Package Manager Library libopkg0 - 0.1.6+svnr215-r2 - opkg - 0.1.6+svnr215-r4 - Opkg Package Manager opkg - 0.1.6+svnr215-r2 - opkg-collateral - 1.0-r1 - opkg configuration files opkg-collateral-dbg - 1.0-r1 - opkg configuration files opkg-collateral-dev - 1.0-r1 - opkg configuration files opkg-dbg - 0.1.6+svnr215-r4 - Opkg Package Manager opkg-dev - 0.1.6+svnr215-r4 - Opkg Package Manager As you can see opkg reports that e.g. opkg is installed twice. Also list_upgradable marks this package upgradeable: r...@om-gta02:~# opkg list_upgradable | grep opkg libopkg0 - 0.1.6+svnr215-r2 - 0.1.6+svnr215-r4 opkg - 0.1.6+svnr215-r2 - 0.1.6+svnr215-r4 The problem arised once I followed http://www.mail-archive.com/community%40lists.openmoko.org/msg54860.html and tried to manually update libfso-glib0 to be able to upgrade fsousaged. I temporarily removed all packages depending on libfso-glib0 and I'm no longer able to install them again: r...@om-gta02:~# opkg install tangogps Installing tangogps (0.9.6-r1) to root... Downloading http://build.shr-project.org/shr-unstable/ipk//armv4t/tangogps_0.9.6-r1_armv4t.ipk Collected errors: * ERROR: Cannot satisfy the following dependencies for tangogps: * libfso-glib0 (= 0.2.1+gitr47+7608c8d98bb65bb5beca6621eb86920b71df1bc9) * Any hints? (No upgrading libfso-glib0 does not help as I would get similar errors mentioning that libfso-glib0 0.2.0 is not installed.) Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-U] opkg displays some packages twice
On Sat, Oct 24, 2009 at 02:37:39PM +0200, Lars Hennig wrote: Am Samstag 24 Oktober 2009 schrieb Jens Seidel: I have some opkg issues recently. r...@om-gta02:~# opkg list | grep opkg libopkg-dev - 0.1.6+svnr215-r4 - Opkg Package Manager libopkg0 - 0.1.6+svnr215-r4 - Opkg Package Manager Library libopkg0 - 0.1.6+svnr215-r2 - opkg - 0.1.6+svnr215-r4 - Opkg Package Manager opkg - 0.1.6+svnr215-r2 - opkg-collateral - 1.0-r1 - opkg configuration files opkg-collateral-dbg - 1.0-r1 - opkg configuration files opkg-collateral-dev - 1.0-r1 - opkg configuration files opkg-dbg - 0.1.6+svnr215-r4 - Opkg Package Manager opkg-dev - 0.1.6+svnr215-r4 - Opkg Package Manager As you can see opkg reports that e.g. opkg is installed twice. Also list_upgradable marks this package upgradeable: r...@om-gta02:~# opkg list_upgradable | grep opkg libopkg0 - 0.1.6+svnr215-r2 - 0.1.6+svnr215-r4 opkg - 0.1.6+svnr215-r2 - 0.1.6+svnr215-r4 opkg is not installed twice: It's installed once and one newer version is availlable in the repository. To list the installed packages run opkg list_installed | grep opkg r...@om-gta02:~# opkg list_installed opkg opkg - 0.1.6+svnr215-r4 - opkg - 0.1.6+svnr215-r2 - r...@om-gta02:~# opkg list_installed | grep opkg libopkg0 - 0.1.6+svnr215-r4 - libopkg0 - 0.1.6+svnr215-r2 - opkg - 0.1.6+svnr215-r4 - opkg - 0.1.6+svnr215-r2 - opkg-collateral - 1.0-r1 - r...@om-gta02:~# opkg install opkg Package opkg (0.1.6+svnr215-r4) installed in root is up to date. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Tue, Sep 08, 2009 at 08:56:07AM +0800, William Kenworthy wrote: On Mon, 2009-09-07 at 16:43 +0200, Sebastian Krzyszkowiak wrote: WTF? WSOD still happening? What kernel do you use? o_O 2.6.28 - never been able to get GSM working on 2.6.29 so thats not an option. WSOD happens when using Qi, not when using uboot. But uboot may need multiple boot attempts before even 2.6.28 will talk to the gsm chipset, whereas Qi is reliable - something is not getting initialised properly somewhere. Funny, it's opposite for me. I used until yesterday 2.6.29 together with uboot but switched back to 2.6.28 and now the WSOD vanished. Great! With 2.6.29 WSOD happened very often (I would say in 50% of all cases). Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it in the past mainly as PDA. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
WSOD (Was: Re: [SHR-Today] Accept call without unlocking)
On Tue, Sep 08, 2009 at 04:29:19PM +0200, Sebastian Krzyszkowiak wrote: On 9/8/09, Jens Seidel jenssei...@users.sf.net wrote: Funny, it's opposite for me. I used until yesterday 2.6.29 together with uboot but switched back to 2.6.28 and now the WSOD vanished. Great! With 2.6.29 WSOD happened very often (I would say in 50% of all cases). Don't remember GSM status with 2.6.29 (works great with 2.6.28), used it in the past mainly as PDA. BTW. Why are you playing with kernels instead of using ditribution one? A good question and I don't know the proper answer. I use SHR but have also Debian installed. SHR is currently more stable and much fancier so I prefer it. I often update the system via opkg update and opkg upgrade which resulted in kernel 2.6.29-rc3. Why should I keep it if it is unstable? And a very stupid question: I know that 2.6.29-rc3 is installed in the file system (/boot) but is it used or the kernel in /dev/mtdblock3? I didn't found the answer in the SHR manual and wasted yesterday at least 3 hours because of it. I also checked the uboot config, booted via USB serial connection started printenv, ... That's not a easy way!!! I flashed finally directly into the kernel partition which seems to work. So opkg doesn't affect the running kernel ... I know that Debian provided a script to customize the uboot configuration and I know that the kernel in the filesystem is used and /dev/mtdblock3 as fallback (or in reverse order, don't remember). But SHR? Digging into the Wiki and mailinglist postings is still the most time consuming task and I'm always lost in it and not able to do any work with my phone! I understand playing with 2.6.31 RC kernels, but downgrading? I prefer a WSOD free kernel, you not? SHR-unstable comes with latest andy-tracking. If something doesn't work in this kernel, then it has to be reported, debuged and fixed, instead of just switching back and being quiet about that! The problem in 2.6.29 is already known, there is no need to report it so I tried to avoid it using 2.6.28 (which reports itself as 2.6.29 :-)). If the latest andy-tracking kernel is no longer affected why aren't both WSOD bug reports updated? I wasn't even aware until very recently that the original WSOD bug was fixed as the initial report is still open without activity since months. I now tried again at least ten minutes to find the SHR kernel download link but failed, it's not on http://wiki.openmoko.org/wiki/Download, http://wiki.openmoko.org/wiki/Flashing#Flashing_the_Kernel, http://wiki.openmoko.org/wiki/SHR_User_Manual, wasn't able to find it via Google, What a mess! At least I don't remember seeing anything andy-tracking related (except the Wiki article about getting the source). Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-Today] Accept call without unlocking
On Mon, Sep 07, 2009 at 04:43:59PM +0200, Sebastian Krzyszkowiak wrote: On 9/7/09, William Kenworthy bi...@iinet.net.au wrote: An observation - Ive lost a few calls (~5) now due to wsod on resume - until this is fixed (and after so long, is it likely to ever be fixed?) WTF? WSOD still happening? What kernel do you use? o_O Oh, yes, WSOD still happens. But in contrast to the past the problem may vanish after a further suspend, see http://docs.openmoko.org/trac/ticket/2274 (Kernel regression: white screen of death reappeared with 2.6.29). I was suprised about the fact that one no longer has to restart to get again a working state and verified it only a few hours ago. In general one needs only one or two suspend iterations until the white screen vanished :-) Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Screen in FR goes black and white after resume from suspend
On Sun, Aug 09, 2009 at 01:43:31PM +0400, Paul Fertser wrote: tb bumbl...@gmail.com writes: Or use uboot and not qi If there's a real problem to debug please do not suggest to hide it with various work-arounds! Do you know any system-level dev who's interested in supporting u-boot? Qi is supported and the latest kernel is supported. I think I was affected as well by the white screen after suspend. The first time since months as I disabled suspend in my Debian installation but not in my new SHR installation. shr-shr-image-glibc-ipk--20090721-om-gta02.rootfs.jffs2 uImage-2.6.29-oe10+gitr119838+2d158aae9d8d36f575504f59884ed8e80802efe2-r3.5-om-gta02.bin I use uboot and no qi! It did not happened again until now ... Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
