RE: 8 Gigabyte Sandisk MicroSDHC Incompatibility
Alex Samorukov wrote: > Hi, i had the same problem, but good news is that this is very easy to > avoid. > > I put in the kernel line glamo_mci.sd_max_clk=1000 setting. And > after this it works perfectly, no more problems so far for a ~5 months. This solution worked for me yesterday, but, today, it isn't working. That's pretty bizarre... I was able to mkfs, fsck, mount, write, unmount, re-mount, and read a written file last night using this solution. Today, nothing doing; same problem as before. I tried re-partitioning and had the same problem as before; the new devices didn't show up until I rebooted. Still no luck. Can anyone think of a reason why it was working last night and not this afternoon? I wish that I could provide more information, but I'd just left the Freerunner charging over USB all night. Thanks again. -David _ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: 8 Gigabyte Sandisk MicroSDHC Incompatibility
> - it does affect the way, the glamo interacts with the sd card, thus no > additional "wear and tear" is included Alright, that's a relief. I have no idea how this sort of memory works or how it's worn over time, so I was, of course, ready to believe anything. > - you do, in fact, not _in_crease the max clock, but _de_crease, since the > default max clock is too fast for slow sd cards, they do not response in > time and thus the communication times out That makes sense. So, I guess that the sd_mac_clk must be the time between ticks, or something like that -- a higher number means a slower clock. Gotcha. -David _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: 8 Gigabyte Sandisk MicroSDHC Incompatibility
> So I wonder, are those general compatibility issues related to > class/speed? Considering my card and the one of Vencabot Teppoo, same > brand, same capacity (apparently at least), maybe just a class different, > I don't understand why mine is working out of the box and his isn't... Actually, according to the source that I purchased from (Amazon), mine is also Class 2. It's just listed as SDSDQ-8192, but the model is listed as SDSDQ-8192-bulk, which I'm not sure if I believe. Since all of the other SDSDQ-8192 on the wiki are of different speed classes, I wouldn't be surprised if mine was also a P36M like yours, and so it's strange that yours worked out of the box and mine didn't. Interesting. -David > To: community@lists.openmoko.org > From: urodelomuta...@yahoo.com > Date: Fri, 21 May 2010 14:01:34 +0200 > Subject: Re: 8 Gigabyte Sandisk MicroSDHC Incompatibility > > Just a semi-ot: > I've recently bought a card for my fr which is not exactly listed on the > wiki, so i think it's another sub-type. It should be similar to the card > of the thread: > SanDisk microsdhc 8GB (real 7,6)class 2 - serial: SDSDQ-8192-P36M > On the wiki there are others with similar serial. > I've partitioned and formatted it by putting it in my mp3 reader (also > SanDisk), built 1 fat partition for android and 3 ext. Put back in fr it > is working without problems, even I have to say that my fr is seldom in > suspend mode... > So I wonder, are those general compatibility issues related to > class/speed? Considering my card and the one of Vencabot Teppoo, same > brand, same capacity (apparently at least), maybe just a class different, > I don't understand why mine is working out of the box and his isn't... > > urodelo > > On Fri, 21 May 2010 13:07:55 +0200, Yann Droneaud wrote: > > > Le vendredi 21 mai 2010 à 12:56 +0200, David Garabana Barro a écrit : > >> People use sd cards without partitions. Even Windows XP doesn't > >> recognice partitions but the first one. That's why manufacturers > >> doesn't bother to say that partition alignation is required. > > > > Or they came pre-partitionned. > > Average users never touch to the partition table. Once in a while they > > could make a new filesystem, but wont touch to the partition. (eg: > > format F: don't change the partition table on any media). > > > > Regards. > > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: 8 Gigabyte Sandisk MicroSDHC Incompatibility
This solution worked for me. I'm genuinely surprised, but I doubled the max click as suggested in this post and I made the EXT3 fs as usual, but, when I checked it, it was clean. I mounted it, saved a file on it, unmounted it, remounted it, and the file was still there. It's my understanding that increasing max click will drain the battery faster and may increase "wear" on the stick (I don't recall where I read that), but it's a relief to have it working, and I'm really glad that I asked here. :D Thank you, and perhaps I should make a note about this on the SD compatibility page. -David Date: Fri, 21 May 2010 09:46:55 +0300 From: m...@os2.kiev.ua To: community@lists.openmoko.org Subject: Re: 8 Gigabyte Sandisk MicroSDHC Incompatibility Vencabot Teppoo wrote: Hi, i had the same problem, but good news is that this is very easy to avoid. I put in the kernel line glamo_mci.sd_max_clk=1000 setting. And after this it works perfectly, no more problems so far for a ~5 months. Hello, community! This is my first time joining a mailing list, so excuse me if my netiquette leaves anything to be desired, and let me know. A couple of weeks ago, I purchased an 8 gig Sandisk microsd card for my Neo Freerunner since it seems like Sandisk has a good track record of compatibility according to the wiki. Sadly, after finally getting it installed and having the time to experiment with it, it seems like its incompatible; when I run fdisk on it, fdisk completes without error, but the new partitions don't show up in /dev until I reboot the Freerunner. After that, I can mkfs, also without error, but checking the filesystem afterward yields that the filesystem is corrupt, and it remains corrupt despite fixing it (without error). Rebooting doesn't help in this case. I've been using Linux exclusively for five years now, but please excuse me for not being very familiar with changing module options and what-not. My question is this: it seems like, in some areas of the wiki, users suggest changing glamo options for microsd to improve compatibility. I've tried the ones that I've read, and none seem to have had any appreciable affect. Is there a list somewhere that describes what-all these options are? Are there more things that I could try before giving up on this card? My bootloader is the most recent version of Qi, and the system that I have in NAND is the most recent version of QtMoko. As far as I can tell, dmesg doesn't report any write errors or any errors related to the microsd except when I try to mount and it complains that it doesn't have a valid EXT3 filesystem. Thank you in advance for your help, and I'm sorry if this message should instead be posted on a technical support mailing list somewhere. If so, could anyone point me toward it? _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: 8 Gigabyte Sandisk MicroSDHC Incompatibility
2.6.29-rc3-v21 is what uname -r returns, so I guess that I'm running version... 21? 22? One thing that I've never really understood well is the relationship between hardware and software, and so I really am curious if continuing to update QtMoko really has a chance of resolving this issue. Is that all that it would take? Are these compatibility problems the result of something in the kernel that could be (will be) patched some day? Hm. Anyway, I certainly have nothing better to do than flash to v23 as you suggest. I suppose that I'll start checking the changelogs and what-not and continue updating. Also, thanks for the info about QtMoko's automatically adjusting glamo.sd_max_clk. I didn't know that. Have a good one. -David > From: pson...@seznam.cz > To: community@lists.openmoko.org > Date: Fri, 21 May 2010 08:14:36 +0200 > Subject: Re: 8 Gigabyte Sandisk MicroSDHC Incompatibility > > On Friday 21 May 2010 03:06:43 Vencabot Teppoo wrote: > > > My bootloader is the most recent version of Qi, and the system that I have > > in NAND is the most recent version of QtMoko. > > Which version exactly is it? I am mainly interested if it's 2.6.29 or 2.6.32 > (you can find out with "uname -r" command). > > You could experiment with flashing v22 (which is 2.6.29) and v23 (which is > 2.6.32). > > Btw QtMoko sets sd_max_clk by default in /etc/init.d/qpe.sh script. > > Otherwise i suppose you already know this [1] wiki page. > > Regards > > Radek > > [1] http://wiki.openmoko.org/wiki/Supported_microSD_cards > [2] > http://github.com/radekp/qtmoko/blob/master/doc/txt/debian_rootfs_howto.txt > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
8 Gigabyte Sandisk MicroSDHC Incompatibility
Hello, community! This is my first time joining a mailing list, so excuse me if my netiquette leaves anything to be desired, and let me know. A couple of weeks ago, I purchased an 8 gig Sandisk microsd card for my Neo Freerunner since it seems like Sandisk has a good track record of compatibility according to the wiki. Sadly, after finally getting it installed and having the time to experiment with it, it seems like its incompatible; when I run fdisk on it, fdisk completes without error, but the new partitions don't show up in /dev until I reboot the Freerunner. After that, I can mkfs, also without error, but checking the filesystem afterward yields that the filesystem is corrupt, and it remains corrupt despite fixing it (without error). Rebooting doesn't help in this case. I've been using Linux exclusively for five years now, but please excuse me for not being very familiar with changing module options and what-not. My question is this: it seems like, in some areas of the wiki, users suggest changing glamo options for microsd to improve compatibility. I've tried the ones that I've read, and none seem to have had any appreciable affect. Is there a list somewhere that describes what-all these options are? Are there more things that I could try before giving up on this card? My bootloader is the most recent version of Qi, and the system that I have in NAND is the most recent version of QtMoko. As far as I can tell, dmesg doesn't report any write errors or any errors related to the microsd except when I try to mount and it complains that it doesn't have a valid EXT3 filesystem. Thank you in advance for your help, and I'm sorry if this message should instead be posted on a technical support mailing list somewhere. If so, could anyone point me toward it? -David PS: Loving the Freerunner. I just wish that there was a more fool-proof way to hook it up with some more disk space. _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
