Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | by the way...should I bugreport or is there others things to try such as | the SD strength? This problem is bigger than access to your SD Card, it is basically issue of stability communicating with whole Glamo. The SD Card is handled by Glamo, so it gets impacted the same. I guess report it as a bug, but I don't think your issue is anything to do with SD Card per se, report it as Glamo corruption issue. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjXcCIACgkQOjLpvpq7dMrVggCggnAHP9wr6Zx8VRh38mkJDfH0 +YgAn0azIeZh+HqAfcM3kkEhKoZHOuam =+h6U -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
by the way...should I bugreport or is there others things to try such as the SD strength? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | and a screen like a tv without antenna... | i reboot That doesn't sound good at all. If you ever see juddery or noisy screen thing then SD Card communication is totally corrupted. It's juddering about because of problems with Glamo DRAM, all SD Card communication goes through that DRAM and is similarly juddered or noised. I've seen the same thing at various times due to not yet understood collection of problems with Glamo memory bus. We (olv) worked around it by cranking up bus wait states which seems to have been pretty effective, however I still see madness from it on resume on 2.6.26. Have you seen this screen corruption thing before or is this the first time? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjUw2oACgkQOjLpvpq7dMqfDACgj6k/N10ZB6naO+WT1rpr5C4c 43IAnRZ+cKiAAR7MOE0onaR8VdhSF0wG =oeUq -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
Have you seen this screen corruption thing before or is this the first time? It's the first time that i've got a tv-like corruption But one night i kept it on and connected to the power trough the power adapter and there was also a corruption...a little bit like when a CRT monitor has the wrong frequency... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
How did you do this, from kernel commandline or by changing module parameter after boot completed? - -Andy echo cd /sys/module/glamo_mci/parameters echo 1000 sd_max_clk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | How did you do this, from kernel commandline or by changing module | parameter after boot completed? | echo | cd /sys/module/glamo_mci/parameters | echo 1000 sd_max_clk I don't think this is enough, the damage with not recognizing the card at boot is done by then. If you can amend the kernel commandline in U-Boot to have ~ glamo_mci.sd_max_clk=1000 then the change will have effect from the first time the card is looked at in Linux and I guess it will work around it. I just ordered a bunch of 8GB cards to see if I can reproduce this and finally solve it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjTelcACgkQOjLpvpq7dMrz5wCeJU01l95KlYixzpaIhzAe19KZ rk0An20kQZudmcP/iiXDuT1TcAX8R0uN =UDQk -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
If you can amend the kernel commandline in U-Boot to have ~ glamo_mci.sd_max_clk=1000 then the change will have effect from the first time the card is looked at in Linux and I guess it will work around it. I just ordered a bunch of 8GB cards to see if I can reproduce this and finally solve it. here's the result of cat /proc/cmdline: glamo_mci.sd_max_clk=1000 rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs) cat /sys/module/glamo_mci/parameters/sd_max_clk 1000 I tried to install debian: SD_PART1_FS=vfat ./install.sh all then it hanged after fdisk process: Writing superblocks and filesystem accounting information: Warning, had trouble writing out superblocks.done This filesystem will be automatically checked every 33 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. then: # dmesg cblk0, sector 7882296 end_request: I/O error, dev mmcblk0, sector 7882304 end_request: I/O error, dev mmcblk0, sector 7882312 glamo-mci glamo-mci.0: Error after cmd: 0x8122 mmcblk0: error -84 sending read/write command glamo-mci glamo-mci.0: Error after cmd: 0x4302 end_request: I/O error, dev mmcblk0, sector 7882320 end_request: I/O error, dev mmcblk0, sector 7882328 end_request: I/O error, dev mmcblk0, sector 7882336 end_request: I/O error, dev mmcblk0, sector 7882344 end_request: I/O error, dev mmcblk0, sector 7882352 end_request: I/O error, dev mmcblk0, sector 7882360 end_request: I/O error, dev mmcblk0, sector 7882368 end_request: I/O error, dev mmcblk0, sector 7882376 etc... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | glamo_mci.sd_max_clk=1000 rootfstype=jffs2 root=/dev/mtdblock6 | console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot | mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs) | cat /sys/module/glamo_mci/parameters/sd_max_clk | 1000 Looks good... | I tried to install debian: By then whatever happened had happened and scrolled off. Try dmesg | grep glamo after boot. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjTr20ACgkQOjLpvpq7dMoKnACeJnzbBwUSGT2O63HvekUhfNEI oGQAn3I3O0CJe6QKUpkxb1uhqbzL4ntl =ZO0A -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
dmesg | grep glamo after boot. $ cat dmesg | grep glamo Kernel command line: glamo_mci.sd_max_clk=1000 rootfstype=jffs2 root=/dev/mtdblock6 console=ttySAC2,115200 console=tty0 loglevel=8 regular_boot mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs) glamo3362 glamo3362.0: Detected Glamo core 3650 Revision 0002 (49119232Hz CPU / 81887232Hz Memory) glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) glamo-spi-gpio glamo-spi-gpio.0: registering c03b9500: jbt6k74 glamo-mci glamo-mci.0: glamo_mci driver (C)2007 Openmoko, Inc glamo-mci glamo-mci.0: probe: mapped mci_base:c8864400 irq:0. glamo-mci glamo-mci.0: glamo_mci_set_ios: power down. glamo-mci glamo-mci.0: initialisation done. glamo-mci glamo-mci.0: powered (vdd = 20) clk: 0kHz div=255 (req: 0kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 20) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: Error after cmd: 0x8120 glamo-mci glamo-mci.0: Error after cmd: 0x120 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 195kHz div=255 (req: 195kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 1kHz div=4 (req: 1kHz). Bus width=0 glamo-mci glamo-mci.0: powered (vdd = 15) clk: 1kHz div=4 (req: 1kHz). Bus width=2 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) The kernel is not from the last week or so? It should have 89MHz PLLB on the Glamo now not 81MHz. | glamo-mci glamo-mci.0: powered (vdd = 15) clk: 1kHz div=4 (req: | 1kHz). Bus width=2 Looks completely happy until then. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjTvPAACgkQOjLpvpq7dMq1jQCfd1ijW8IFG7nrO7sWTQffvwMI KM0AmwQG+BGr3gTdQq61wCFGPvv6IGkF =Y+q9 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
On Fri, Sep 19, 2008 at 03:53:36PM +0100, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) The kernel is not from the last week or so? It should have 89MHz PLLB on the Glamo now not 81MHz. The kernel in the Om2008.8 repository is built from git revision a1e97c611253511ffc2d8c45e3e6d6894fa03fa3 according to the package version, which is about 4 weeks old. Regards, Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
The kernel is not from the last week or so? It should have 89MHz PLLB on the Glamo now not 81MHz. the kernel is from FSO milestone III...otherwise the wifi would have not worked i ran a new install with logread -f log2.txt and here are the logs: Sep 19 17:25:27 om-gta02 daemon.notice modprobe: FATAL: Error inserting ipv6 (/lib/modules/2.6.24/kernel/net/ipv6/ipv6.ko): Unknown symbol in module, or unknown parameter (see dmesg) Sep 19 17:25:29 om-gta02 auth.err sshd[1840]: error: Could not get shadow information for root Sep 19 17:25:29 om-gta02 auth.info sshd[1840]: Accepted password for root from 192.168.0.200 port 58824 ssh2 Sep 19 17:25:29 om-gta02 auth.info sshd[1844]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Sep 19 17:25:29 om-gta02 auth.info sshd[1844]: lastlog_openseek: /var/log/lastlog is not a file or directory! Sep 19 17:25:29 om-gta02 auth.info sshd[1844]: lastlog_filetype: Couldn't stat /var/log/lastlog: No such file or directory Sep 19 17:25:29 om-gta02 auth.info sshd[1844]: lastlog_openseek: /var/log/lastlog is not a file or directory! Sep 19 17:25:29 om-gta02 auth.err sshd[1844]: error: setlogin failed: Function not implemented Sep 19 17:26:14 om-gta02 user.notice root: ApplicationLayer: Application layer server unexpectedly terminated. Sep 19 17:26:14 om-gta02 user.notice root: The process exited: 15 normal: 0 Sep 19 17:26:15 om-gta02 user.notice root: ApplicationLayer: Application layer server unexpectedly terminated. Sep 19 17:26:15 om-gta02 user.notice root: ApplicationLayer: Application layer server unexpectedly terminated. Sep 19 17:26:24 om-gta02 user.info gconfd (root-1530): Exiting Sep 19 17:26:43 om-gta02 user.info kernel: mmcblk0: Sep 19 17:26:43 om-gta02 user.info kernel: p1 p2 Sep 19 17:26:45 om-gta02 user.err kernel: FAT: bogus number of reserved sectors Sep 19 17:26:45 om-gta02 user.info kernel: VFS: Can't find a valid FAT filesystem on dev mmcblk0p2. Sep 19 17:26:45 om-gta02 user.err kernel: FAT: bogus number of reserved sectors Sep 19 17:26:45 om-gta02 user.info kernel: VFS: Can't find a valid FAT filesystem on dev mmcblk0p2. Sep 19 17:31:24 om-gta02 user.info kernel: glamo-mci glamo-mci.0: Error after cmd: 0x310 Sep 19 17:31:24 om-gta02 user.err kernel: mmcblk0: error -110 sending read/write command Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 2375000 Sep 19 17:31:24 om-gta02 user.info kernel: glamo-mci glamo-mci.0: Error after cmd: 0x8120 Sep 19 17:31:24 om-gta02 user.err kernel: mmcblk0: error -110 sending read/write command Sep 19 17:31:24 om-gta02 user.info kernel: glamo-mci glamo-mci.0: Error after cmd: 0xc120 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507320 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507328 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507336 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507344 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507352 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507360 Sep 19 17:31:24 om-gta02 user.warn kernel: end_request: I/O error, dev mmcblk0, sector 5507368 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | The kernel is not from the last week or so? It should have 89MHz PLLB | on the Glamo now not 81MHz. | the kernel is from FSO milestone III...otherwise the wifi would have not | worked Sorry, what's broken with Wifi in later kernels? | i ran a new install with logread -f log2.txt and here are the logs: | Sep 19 17:25:27 om-gta02 daemon.notice modprobe: FATAL: Error inserting | ipv6 (/lib/modules/2.6.24/kernel/net/ipv6/ipv6.ko): Unknown symbol in | module, or unknown parameter (see dmesg) This looks like your /lib/modules doesn't match your kernel? | Sep 19 17:26:43 om-gta02 user.info kernel: mmcblk0: | Sep 19 17:26:43 om-gta02 user.info kernel: p1 p2 | Sep 19 17:26:45 om-gta02 user.err kernel: FAT: bogus number of reserved | sectors | Sep 19 17:26:45 om-gta02 user.info kernel: VFS: Can't find a valid FAT | filesystem on dev mmcblk0p2. | Sep 19 17:26:45 om-gta02 user.err kernel: FAT: bogus number of reserved | sectors | Sep 19 17:26:45 om-gta02 user.info kernel: VFS: Can't find a valid FAT | filesystem on dev mmcblk0p2. These above are likely OK, it looks like the userspace action was to try to mount mmcblk0p2 as FAT on the off-chance. | Sep 19 17:31:24 om-gta02 user.info kernel: glamo-mci glamo-mci.0: Error | after cmd: 0x310 | Sep 19 17:31:24 om-gta02 user.err kernel: mmcblk0: error -110 sending | read/write command That's where insanity sets in 5 minutes later. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjT1OwACgkQOjLpvpq7dMpjQACfQPiD413P81HMaoR0x0FYv5QA RiwAn3H6fy7OUMXUJczluBG//uag980c =dYcX -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Fri, Sep 19, 2008 at 03:53:36PM +0100, Andy Green wrote: | -BEGIN PGP SIGNED MESSAGE- | Hash: SHA1 | | Somebody in the thread at some point said: | | | glamo3362 glamo3362.0: Glamo core now 49119232Hz CPU / 81887232Hz Memory) | | The kernel is not from the last week or so? It should have 89MHz PLLB | on the Glamo now not 81MHz. | | The kernel in the Om2008.8 repository is built from git revision | a1e97c611253511ffc2d8c45e3e6d6894fa03fa3 according to the package | version, which is about 4 weeks old. Personally I would run current kernel packages, from whatever repo has them. The main downside is that suspend and resume performance will vary randomly build by build at the moment. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjT1VwACgkQOjLpvpq7dMpCGgCgg85KjAGmGZshvIUiwamCApS2 /uQAnjL+4gr+/B3phaFAfCtk3LTv2MJF =vAeb -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
Sorry, what's broken with Wifi in later kernels? no not the later kenrel...I was told that the kernel from om2008.8 couldn't make wifi work...and i tried without success so I updated kenrel This looks like your /lib/modules doesn't match your kernel? yes it doesn't i didn't bother updating it as everything I need is compiled in there kernel... These above are likely OK, it looks like the userspace action was to try to mount mmcblk0p2 as FAT on the off-chance. | Sep 19 17:31:24 om-gta02 user.info kernel: glamo-mci glamo-mci.0: Error | after cmd: 0x310 | Sep 19 17:31:24 om-gta02 user.err kernel: mmcblk0: error -110 sending | read/write command That's where insanity sets in 5 minutes later. Mabe it's the debian installer that is responsible...i am testing it without the debian installer copying files: /dev/mmcblk0p23.8G 1.2G 2.4G 33% /media/mmcblk0p2 actually it's doing dd if=/dev/urandom of=./random ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
That's where insanity sets in 5 minutes later. Mabe it's the debian installer that is responsible...i am testing it without the debian installer copying files: /dev/mmcblk0p23.8G 1.2G 2.4G 33% /media/mmcblk0p2 actually it's doing dd if=/dev/urandom of=./random at the end...when deleting the random file i got: EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 1887829751, count = 1 EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 4210218882, count = 1 EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 2089222141, count = 1 EXT2-fs error (device mmcblk0p2): ext2_free_blocks: Freeing blocks not in datazone - block = 789782119, count = 1 EXT2-fs error (device mmcblk0p2): ext2_free_blocks: bit already cleared for block 917457 and a screen like a tv without antenna... i reboot ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
This is just another SD corruption data point, and a partial one, since I'm afraid I've lost any detailed logs. I am running Qtopia on flash, and Debian on the SD card. Two days ago I found that booting into Debian failed at the point of trying to mount the rootfs; the last message was Kernel panic..., and before that something about not having any filesystems able to mount the partition (/dev/mmcblk0p2). I recovered by rebooting into Qtopia and running e2fsck on /dev/mmcblk0p2, then I could boot into Debian again. I'm not an expert on fsck messages, but I think they indicated that the corruption had mainly affected the initial superblock. Hoping this is is of some use to somebody, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
SD corruption(no suspend and sd_max_clk tested)
Hello, I've bought a MMBGR04GUACY-NA and its adapter... but the card produce I/O errors in dmesg... I was using the kernel from FSO milestone 3 if I remember well it does the same with 2008.8 I've tried lowering sd_max_clk to the 1000 I've tried increasing the drive strength to 3 I'd really like to try debian...and for this I would need a huge sd-card What i've done to detect it: *boot it using the flashed FSO milestone 3 kernel and the 2008.8 userland *install debian when I installed debian it stoped with I/O errors so I changed some sd settings and i restarted installing debian without rebooting...and it made others I/O errors ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD corruption(no suspend and sd_max_clk tested)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hello, | I've bought a MMBGR04GUACY-NA and its adapter... | but the card produce I/O errors in dmesg... | I was using the kernel from FSO milestone 3 | if I remember well it does the same with 2008.8 | | I've tried lowering sd_max_clk to the 1000 How did you do this, from kernel commandline or by changing module parameter after boot completed? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjSvowACgkQOjLpvpq7dMo+NACfUYeyEA9zOXDErP2R7AFC4ko5 XN8An2AUV8YnNBGZsl+LggB4BnkM4qMW =FJ5i -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
