Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Unstable feed is the appropriate place for kernel stable branch head. Yes it's fine, if it actually turns up there. I see thismorning they're cooking again. Grab most recent kernel package here: http://downloads.openmoko.org/repository/unstable/om-gta02/ Of course I understood we no longer made individual module packages, but there they are in that repo. So quite what users have to do to get that straight I dunno: any advice welcome as to what I should say to customers anxious to test current kernel package. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjbO6AACgkQOjLpvpq7dMqC5ACfeJwuzsQQmtCTTl4+fJSzQ8nB S6AAoISisQ1hS9YqXzEL9RLSkTYidk7q =a4BI -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy, the version of the kernel build dated the 24th of Sept from the | debian package | deb http://prophet.homelinux.org/~lynx/debian unstable main | linux-image-gta02 | now corrupts my 8GByte Samdisk SDHC card on suspend, where i had no | problems with the previous kernels with the workaround that turned the | SD clock on when suspending. I assume this kernel has your latest SD | mods in it. Ha good on Debian it's a better source of kernel packages than we are. I'll take a look at how the last changes might have impacted that. | Has anyone actually checked to make sure that the SD drivers and uboot | conform to the SDHC specification? U-Boot version we use anyway has no SD layer support at all, I added it to the Glamo driver modified from Linux driver directly and it is pretty ad-hoc. But, it should work. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjbPwwACgkQOjLpvpq7dMr0yQCeJL+2F0tkHyynK8qQdyaGY7V6 VYoAnR8zogHAJQaQNYrf9nKaSKTzENyy =EM4N -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
Andy Green wrote: It used to be that our kernel packages followed our stable kernel git daily. But the hash on that one tells it is stuck at Aug 23 patchlevel... Yet another reason why the openmoko autobuilder configuration should be documented and published somewhere. As an example, the person in charge of the openmoko autobuilder should publish the same information as can be found on http://downloads.freesmartphone.org and make the web server show the *actual* conf files used, like in http://downloads.freesmartphone.org/fso-testing/conf/ ... -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
On Wed, Sep 24, 2008 at 08:59, Andy Green [EMAIL PROTECTED] wrote: Clearly that doesn't have the patch. This from today doesn't have it either. http://downloads.openmoko.org/repository/testing/om-gta02/kernel-image-2.6.24_2.6.24+gitr105+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r2_om-gta02.opk It used to be that our kernel packages followed our stable kernel git daily. But the hash on that one tells it is stuck at Aug 23 patchlevel... what about this one (/unstable) ? directory date on http repository is 15 Sep only, so should not be the latest either.. http://downloads.openmoko.org/repository/unstable/om-gta02/kernel-image-2.6.24_2.6.24+gitr75974+1b6ea684646a9a793543ca54c8d937d5fa25cc3f-r2_om-gta02.opk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Wed, Sep 24, 2008 at 08:59, Andy Green [EMAIL PROTECTED] wrote: | Clearly that doesn't have the patch. | | This from today doesn't have it either. | | http://downloads.openmoko.org/repository/testing/om-gta02/kernel-image-2.6.24_2.6.24+gitr105+a1e97c611253511ffc2d8c45e3e6d6894fa03fa3-r2_om-gta02.opk | | It used to be that our kernel packages followed our stable kernel git daily. | | But the hash on that one tells it is stuck at Aug 23 patchlevel... | | what about this one (/unstable) ? directory date on http repository | is 15 Sep only, so should not be the latest either.. | http://downloads.openmoko.org/repository/unstable/om-gta02/kernel-image-2.6.24_2.6.24+gitr75974+1b6ea684646a9a793543ca54c8d937d5fa25cc3f-r2_om-gta02.opk It's a bit later but still nearly two weeks and several patches out of date. Somebody made a decision that we don't make up to date packages any more of our stable kernel, they are done but go in a special place (not testing or unstable?), or this is just a messup? If it's a decision, it needs rethinking. - -Andy BTW why is this -devel list so eerily quiet lately? It seems like openmoko still is in Open software development business but just not here? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjZ7ckACgkQOjLpvpq7dMqEwgCeNOkrX613+Gm0veukCaFtGpkO xF4AnAtqoVKLKBLVoB2YfMEN1nwtjxv5 =LURu -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: | It used to be that our kernel packages followed our stable kernel git daily. | | But the hash on that one tells it is stuck at Aug 23 patchlevel... | | Yet another reason why the openmoko autobuilder configuration should be | documented and published somewhere. | | As an example, the person in charge of the openmoko autobuilder should | publish the same information as can be found on | http://downloads.freesmartphone.org and make the web server show the | *actual* conf files used, like in | http://downloads.freesmartphone.org/fso-testing/conf/ ... Yes, they (whoever they are) have packages from 16th September, it doesn't look like we broke the build since everywhere is different aged package. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjZ7iMACgkQOjLpvpq7dMqOTwCdG0xiBRnLdPoxiLUJrIJv/kbD 03EAni3ZnB9MgYzqpHtjsHgtqjy0SmLg =2Pn6 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Andy Green wrote: | It used to be that our kernel packages followed our stable kernel git daily. | | But the hash on that one tells it is stuck at Aug 23 patchlevel... | | Yet another reason why the openmoko autobuilder configuration should be | documented and published somewhere. | | As an example, the person in charge of the openmoko autobuilder should | publish the same information as can be found on | http://downloads.freesmartphone.org and make the web server show the | *actual* conf files used, like in | http://downloads.freesmartphone.org/fso-testing/conf/ ... Yes, they (whoever they are) have packages from 16th September, it doesn't look like we broke the build since everywhere is different aged package. The fso-testing distro builds the version of the linux-openmoko kernel denotes as latest stable by the conf/distro/include/sane-srcrevs.inc file, which currently in OE git (not OM git) on the org.openembedded.dev branch says: SRCREV_pn-linux-openmoko ?= ca19d156400f817960efe0d14680324b2ea34171 In OM git, that same file (in the org.openmoko.dev branch) says: SRCREV_pn-linux-openmoko ?= a1e97c611253511ffc2d8c45e3e6d6894fa03fa3 which surprise surprise matches the ipk in http://downloads.openmoko.org/repository/testing/om-gta02/ I have no idea what determines which version is built for the feeds at http://downloads.openmoko.org/repository/unstable/om-gta02/ since there is no published build configuration on downloads.openmoko.org anywhere to be found. It's up the the person in charge of testing the linux-openmoko bitbake recipe to determine what the latest stable version in the feeds should be by updating that sane-srcrevs.inc file (after booting an image using that kernel of course). -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
That may be, but despite that I need a daily package for kernel I can point people to. Actually blocking current stable kernel from users by not packaging it, which seems to be the case, is completely backwards. That may be the case, and you defintely should be able to point experienced alpha testers to such isolated packages for testing, but you don't want inexperienced Joe Random User permanently setting their opkg feeds to a such a directory, so you don't really want it as part of the official feeds ... -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | That may be, but despite that I need a daily package for kernel I | can point people to. Actually blocking current stable kernel from | users by not packaging it, which seems to be the case, is | completely backwards. | | That may be the case, and you defintely should be able to point | experienced alpha testers to such isolated packages for testing, but | you don't want inexperienced Joe Random User permanently setting | their opkg feeds to a such a directory, so you don't really want it | as part of the official feeds ... -- Rod Uh... yes in fact I do want it as part of an official feed. Someone has taken time to make a stable / testing / and even unstable branches of stuff, and you think it is right that our stable kernel git HEAD is so radioactive it doesn't even belong in testing or unstable? This is certainly something we need, the only question is where to put it so people who want to update to it can routinely get it. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjaS98ACgkQOjLpvpq7dMqKzwCgkjtjR4leS67vnVELt4iDCZGk GwgAn0RAddxfaxzJffViDhX2iPPK+Ssn =Ue37 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
This is certainly something we need, the only question is where to put it so people who want to update to it can routinely get it. And also, if I may be so bold as to suggest, not to claim that repositories contain the latest builds when that is not the case. Personally my wishes are rather more prosaic - simply to be able to use my Sandisk 8GB SDHC card. Unfortunately my internet connection resembles a length of taught string and downloading the entire kernel source in order to make a stock-standard build is not a practical option for me. Jonathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | That may be, but despite that I need a daily package for kernel I | can point people to. Actually blocking current stable kernel from | users by not packaging it, which seems to be the case, is | completely backwards. | | That may be the case, and you defintely should be able to point | experienced alpha testers to such isolated packages for testing, but | you don't want inexperienced Joe Random User permanently setting | their opkg feeds to a such a directory, so you don't really want it | as part of the official feeds ... -- Rod Uh... yes in fact I do want it as part of an official feed. I expect you want it as part of the unstable feed, not the testing feed. I can fully agree with that. People who use the unstable feed are the people who know they are testing the integration and distro consistency. Someone has taken time to make a stable / testing / and even unstable branches of stuff, and you think it is right that our stable kernel git HEAD is so radioactive it doesn't even belong in testing or unstable? No, it definitely belongs in unstable, but never in testing automatically. Someone has to make a conscious decision (and commitment to the community that it should work) to edit sane-srcrevs.inc to make something new appear in testing. This is certainly something we need, the only question is where to put it so people who want to update to it can routinely get it. Unstable feed is the appropriate place for kernel stable branch head. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
Andy, the version of the kernel build dated the 24th of Sept from the debian package deb http://prophet.homelinux.org/~lynx/debian unstable main linux-image-gta02 now corrupts my 8GByte Samdisk SDHC card on suspend, where i had no problems with the previous kernels with the workaround that turned the SD clock on when suspending. I assume this kernel has your latest SD mods in it. Has anyone actually checked to make sure that the SD drivers and uboot conform to the SDHC specification? Simon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
unable to read from Sandisk 8Gb SD
There is a patch that should be in tomorrow's kernels that addresses this, at least it gets my Sandisk 8GB SDHC recognized, please let me know if it helped or not. Should it be included in this kernel? http://downloads.openmoko.org/daily/testing-om-gta02-20080923.uImage.bin I ask because I got the following: Unknown boot option `glamo_mci.sd_post_power_clock=10': ignoring when I tried playing with it. And my Sandisk 8GB SDHC is still not recognised. Jonathan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Mon, Sep 15, 2008 at 9:13 AM, Andy Green [EMAIL PROTECTED] | mailto:[EMAIL PROTECTED] wrote: | | Can you confirm if you need the idle clock set to 1? What I think I | understood about this issue is that it is timeout-related only, it means | I didn't actually understand what is going on if it needs idle | clocks too. | | | i am now sure: i don't need it. I made many other experiments (about | log2(50)) and i found out that the maximum value for the sd_max_clock | which can still read the card is There is a patch that should be in tomorrow's kernels that addresses this, at least it gets my Sandisk 8GB SDHC recognized, please let me know if it helped or not. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=9e7ba57b104e9293f746342b7450b10d5fa0c4cd - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjYE5EACgkQOjLpvpq7dMolOgCdHiZOKi1ochHy9nUUgLTNCj82 OE8Anjxg4FG5Yhf4rSH0C9xHXX8FCT7h =1os4 -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
On Mon, Sep 22, 2008 at 10:52:26PM +0100, Andy Green wrote: Somebody in the thread at some point said: | On Mon, Sep 15, 2008 at 9:13 AM, Andy Green [EMAIL PROTECTED] | mailto:[EMAIL PROTECTED] wrote: | | Can you confirm if you need the idle clock set to 1? What I think I | understood about this issue is that it is timeout-related only, it means | I didn't actually understand what is going on if it needs idle | clocks too. | | | i am now sure: i don't need it. I made many other experiments (about | log2(50)) and i found out that the maximum value for the sd_max_clock | which can still read the card is There is a patch that should be in tomorrow's kernels that addresses this, at least it gets my Sandisk 8GB SDHC recognized, please let me know if it helped or not. http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=9e7ba57b104e9293f746342b7450b10d5fa0c4cd With the kernel patch it works for me (Sandisk microSDHC 8 GB). I have started the device twice and always the card was recognized and mounted. Tomorrow (actually today) I will test it more and try to run Debian from the card (this not has worked) Alex - -Andy ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | On Mon, Sep 22, 2008 at 10:52:26PM +0100, Andy Green wrote: | Somebody in the thread at some point said: | | On Mon, Sep 15, 2008 at 9:13 AM, Andy Green [EMAIL PROTECTED] | | mailto:[EMAIL PROTECTED] wrote: | | | | Can you confirm if you need the idle clock set to 1? What I think I | | understood about this issue is that it is timeout-related only, it | means | | I didn't actually understand what is going on if it needs idle | | clocks too. | | | | | | i am now sure: i don't need it. I made many other experiments (about | | log2(50)) and i found out that the maximum value for the sd_max_clock | | which can still read the card is | | There is a patch that should be in tomorrow's kernels that addresses | this, at least it gets my Sandisk 8GB SDHC recognized, please let me | know if it helped or not. | | http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=9e7ba57b104e9293f746342b7450b10d5fa0c4cd | | With the kernel patch it works for me (Sandisk microSDHC 8 GB). I have started | the device twice and always the card was recognized and mounted. Tomorrow | (actually today) I will test it more and try to run Debian from the card (this | not has worked) That's great. FWIW I dd'd 40MB of /dev/urandom on to the SD card, md5sum'd it and confirmed it was the same after a reboot, so I expect once it is recognized it acts OK. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjYJckACgkQOjLpvpq7dMqz9QCdEtOLUnlu0WhhOLNOTQOR1S2x 2SYAnAzBO2VDT3b8GnvNHYmDqvygZVZB =h7lk -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
On Mon, Sep 15, 2008 at 9:13 AM, Andy Green [EMAIL PROTECTED] wrote: Can you confirm if you need the idle clock set to 1? What I think I understood about this issue is that it is timeout-related only, it means I didn't actually understand what is going on if it needs idle clocks too. i am now sure: i don't need it. I made many other experiments (about log2(50)) and i found out that the maximum value for the sd_max_clock which can still read the card is int(50MHz / 19) =2631578 Hz (why this value? maybe something crucial happens at low level when you raise from this value?) Anyway, i don't absolutely need the idleclock, it was just one of the thing tried to make it work. Probably the problem is just that i bought a very slow card.. I hope that performances will be sufficient to boot something from it, or maybe i could keep it just to save my mp3s.. i attach my u-boot environment, just in case anyone pass through the same pain he can try to take inspiration from it. the menus which successfully boot with the card are the 4 and the 10. if any other test could be useful to debug just tell me what to do.. at the moment i don't mind loosing the card content, i just put an experimental environment inside, and it seems not to boot very well.. roby u-boot-environment.txt.gz Description: GNU Zip compressed data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: unable to read from Sandisk 8Gb SD
mån 2008-09-15 klockan 19:50 +0200 skrev Previdi Roberto: On Mon, Sep 15, 2008 at 9:13 AM, Andy Green [EMAIL PROTECTED] wrote: maybe i could keep it just to save my mp3s.. I recommend that you start using ogg - it's free from patent issues. :) / Fredrik signature.asc Description: Detta är en digitalt signerad meddelandedel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
unable to read from Sandisk 8Gb SD
Hello. I have a big problem: i cannot read a new 8Gb SD card from Sandisk. some details: - the 512 Mb card works without any problem, i've been able to reformat it, use ext2 on it, mount /usr in it - i have partitioned the 8Gb card from my pc card reader and i've put a kernel and a rootfs inside it as the wiki explain - my FR card slot have got a little capacitor soldered between 2 pins, like in this image ( http://makovey.objectis.net/Members/dimon/issues/om/microSD2.jpg/view) , but with better soldering - during all the experiments i never suspended-resumed the phone, and i am sure the partitions in the card are not corrupted (because i checked them periodically with the card reader) - the boot loader see the card, and is able to load a kernel from it! (in NAND menu) $ cu -l /dev/ttyACM0 Connected. In:usbtty Out: usbtty Err: usbtty Unrecognized hardware revision 0x305. Defaulting to GTA02v6. PCB rev: 0x305 Power: 0mA GTA02v6 # mmcinit Card Type: SD 2.0 SDHC Manufacturer: 0x03, OEM SD Product name: SU08G, revision 8.0 Serial number: 554005576 Manufacturing date: 8/2008 MMC/SD size:3MiB All the output that follows is taken after booting from the internal flash, just with the memory card inserted. If instead i boot from the sd i noticed a strange behaviour: the first try it sometimes fail to read the card, but the second try it works good, it loads the kernel and the kernel output is exactly the same of the one below, except it ends in a kernel panic not finding his root. # uname -a Linux roby-neo 2.6.24 #1 PREEMPT Wed Sep 3 19:01:18 CST 2008 armv4tl unknown # cat /proc/cmdline glamo_mci.sd_idleclk=1 glamo_mci.sd_max_clk=500 rootdelay=5 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) - i tried to set just the sd_max_clk to the values (default,1000,833,500), i tried to set the sd_idleclk to 1 or to 0, with the sd_drive at 3 or 0 (doesn't know what's the effect).. nothing, always the same errors. - kernel output: (the relevant part, the complete one is attached) [...] [3.23] *mmc0: new high speed SDHC card at address 8fe4* [3.27] neo1973-pm-gps neo1973-pm-gps.0: FIC Neo1973 GPS Power Managerment:starting [...] [3.335000] Bluetooth: HCI USB driver ver 2.9 [3.34] usbcore: registered new interface driver hci_usb [3.35] mmcblk0: mmc0:8fe4 *SU08G 7761920KiB* [3.355000] mmcblk0:6glamo-mci glamo-mci.0:* Error after cmd: 0x8310* [3.37] mmcblk0:* error -110* sending read/write command [3.375000] end_request: I/O error, dev mmcblk0, sector 0 [3.375000] Buffer I/O error on device mmcblk0, logical block 0 [3.38] glamo-mci glamo-mci.0:* Error after cmd: 0x20* [3.385000] glamo-mci glamo-mci.0: *Error after cmd: 0x122* [3.39] mmcblk0: *error -84* sending read/write command [3.395000] end_request: I/O error, dev mmcblk0, sector 0 [3.395000] Buffer I/O error on device mmcblk0, logical block 0 [3.40] *unable to read partition table* [3.41] S3c2440 SDIO Host controller [3.515000] pnp: the driver 'sdio_s3c24xx_hcd' has been registered [...] Please, tell me that i can solve this problem! actually i'm sure it can be solved, because the boot loader is perfectly (nearly) able to read and load the kernel written in the sd. Tell me if some other kind output could be useful.. maybe my shoes number? :) roby boot-log-5Mhz.gz Description: GNU Zip compressed data ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
unable to read from Sandisk 8Gb SD
-> Re: unable to read from Sandisk 8Gb SD community -- Thread -- -- Date -- <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "000000"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FFFFFF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FFFFFF"; google_color_bg = "FFFFFF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "000000"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green unable to read from Sandisk 8Gb SD Jonathan Schultz Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green unable to read from Sandisk 8Gb SD Jonathan Schultz Re: unable
unable to read from Sandisk 8Gb SD
-> Re: unable to read from Sandisk 8Gb SD community -- Thread -- -- Date -- <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "000000"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FFFFFF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FFFFFF"; google_color_bg = "FFFFFF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "000000"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green unable to read from Sandisk 8Gb SD Jonathan Schultz Reply via email to <!-- google_ad_client = "pub-7266757337600734"; google_alternate_ad_url = "http://www.mail-archive.com/blank.png"; google_ad_width = 160; google_ad_height = 600; google_ad_format = "160x600_as"; google_ad_channel = "8427791634"; google_color_border = "FF"; google_color_bg = "FF"; google_color_link = "006792"; google_color_url = "006792"; google_color_text = "00"; //--> unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Previdi Roberto Re: unable to read from Sandisk 8Gb SD Fredrik Wendt Re: unable to read from Sandisk 8Gb SD Andy Green Re: unable to read from Sandisk 8Gb SD Alex Oberhauser Re: unable to read from Sandisk 8Gb SD Andy Green unable to read from Sandisk 8Gb SD Jonathan Schultz Re: unable
