Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
notlistening:
Hate to be the bearer of bad news. r21550 has not fixed the issues for me. I am using a e260v2 and I am getting file corruption on every disk write. I have tested with a brand new rockbox build, formatted using the OF and reloaded everything.
Firstly Database initialization hangs but speech continues to give uodates and back light etc are functioning.
Saving of setting changes are being kept but there are problems being made att he time of the filesystem. I also haveed my sound and theme settings in a .cfg file to disk.
I ran fsck before ruuning rockbox again and no wrrors and after testing the above features I got this output from fsck:
fsck 1.41.4 (27-Jan-2009)
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
FATs differ but appear to be intact. Use which FAT ?
1) Use first FAT
2) Use second FAT
? 2
/SANSA E2.60
Contains a free cluster (3). Assuming EOF.
/SANSA E2.60
File size is 8 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/SYS_CONF.SYS
Contains a free cluster (4). Assuming EOF.
/SYS_CONF.SYS
File size is 316 bytes, cluster chain length is 0 bytes.
Truncating file to 0 bytes.
/MUSIC
Contains a free cluster (5). Assuming EOF.
/##MUSIC#
Contains a free cluster (6). Assuming EOF.
/RECORD
Contains a free cluster (7). Assuming EOF.
/AUDIBLE
Contains a free cluster (10). Assuming EOF.
/PHOTO
Contains a free cluster (11). Assuming EOF.
/VIDEO
Contains a free cluster (12). Assuming EOF.
/##PORT#
Contains a free cluster (13). Assuming EOF.
Reclaimed 48 unused clusters (1572864 bytes).
Free cluster summary wrong (120838 vs. really 123443)
kugel.:
I've similar issues on my clip (the FS is totally broken after *very* few writes), but they're not related to rockbox (it's broken after using the OF too). So it might be as well a hardware issue as with my clip.
I'm going to test myself a bit too (my fuze functioned fine so far).
€dit: I just got the same fsck output as in the above post. But actually, those folders are created by the OF and I didn't touch them ever. I suspect the OF is just doing it's magic hackery with the filesystem, and that it's not a Rockbox issue.
PS: WTF is /SANSA E2.60 (or /SANSA FU.ZE respectively) for a folder. Did the OF mess up nameing the partition (could that be why linux doesn't see the Dap's name after a fresh reformat?).
funman:
I have seen those names in the OF code but not sure what they mean.
The partition created by the OF has no label, I think linux has a builtin list of USB VID/PID to give a name.
werich:
--- Quote ---I have committed r21550 which fixes a problem in SD bank selection (also used at startup to enable access to the whole 1st bank).
--- End quote ---
OK - at least I can only report good things:
I'm using the actual r21572 build, and it works like a charm on my Fuze 8GB including 8GB microSDHC.
No disc corruption so far (2hours of excessive testing across internal mem and microSD including mp3, ogg, mod and flac mix, crossfade, coverflow, mpegplayer video, radio etc.) and no broken filenames anymore. I didn't even had to reformat my fuze, just replaced the .rockbox folder. Aside from very few random freezes (once the radio after scan&save, once after inserting mod file into playlist) it seems quite stable to me.
Note: I checked the file system with chkdsk /f under windows, but "no errors" imply an intact FAT32, or?!
funman:
Looks good!
I'll look at adding some code to see if freezes are related to SD driver.
Yeah I think "no error" imply an intact FAT32 filesystem ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version