Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
FlynDice:
@ChiefAlex:
Thanks for the report and the error code, I haven't seen the read errors before. That's a data timeout on the internal disk.
Which player are you using?
EDIT:
@ all: For what it's worth my e280V2 is not displaying any of these problems right now. I don't say that to discount the problems being experienced but to explain why this is becoming tricky to fix...
EDIT2:
@ epithetless:
"Data abort at 30800968" seems to fall in the memcpy function as I look at rockbox.map. It's always 30800968 correct?
epithetless:
--- Quote from: FlynDice on December 16, 2009, 08:47:19 PM ---@ epithetless:
"Data abort at 30800968" seems to fall in the memcpy function as I look at rockbox.map. It's always 30800968 correct?
--- End quote ---
Yes, it's always 30800968.
Are any other Fuze users seeing this data abort once directory cache is enabled? The strange thing is I'd actually had directory cache enabled for a long time (as in many months) without any issue, but once the data corruption occurred yesterday, even builds which accepted directory caching before now fail with the abort message. Running Check Disk, thoroughly reformatting the device, and reflashing the firmware haven't changed this. :(
ChiefAlex:
Hi FlynDice,
I use the Sandisk Fuze V1.
Some more ino: When i connect player to PC some "Files" are visible in the root folder. They have no-displayable names and cant get deleted. only way to fix it (for me) format the player via Windows. FAT or FAT32 seems to make no difference?
With a very old build from xx.09.09 this not occur. Thanks god i had this zip on my PC.
If you need more info about settings/whatever feel free to say, ill do my best to fix this.
Just DLed Rev.24039, lets see if it still occur
samstar:
Hi all,
I have a sansa e260v2 w/ a kingston 2gb uSD card, and I've been following all of your work for quite some time. This is my first time posting. First let me say I'm very impressed at the progress being made here. It's brought my music player back to life, as the OF was too frustrating to work with. Much thanks to you all.
I wanted to confirm that updating my sansa from revision 2373X (give or take a few numbers) to 20429 yesterday also gave me corruption problems. I spent the time formatting the internal memory after the update, and uploading the songs to it. Whenever I tried to initialize the database, it would always respond after a reboot that the database needed to be initialized. Cleaning the drive with chkdsk only temporarily solved the problem, and let me access the database for about ten minutes before it became corrupted. I tried creating playlists from the file browser then, only to find that all the playlists I saved became corrupted as well. It came to the point where linux would no longer recognize the partition as a usb storage drive when plugged in with the OF running. I'd have to use the OF to reformat the drive first. Also, I would often get panic errors, but I didn't have the presence of mind to write them down >:(
After reverting my player to rev. 23929 (before the 4-bit widebus update) I have been able to initialize the database and create and move files without any corruption issues at all. For the record, I've not had any corruption issues with the uSD card for any of the revisions.
If I can be of any other assistance, please let me know!
Thanks again!
Sam
FlynDice:
Well, after leaving my player on all night I came back to find several strange files in my .rockbox folder this morning :-\...
I have reverted the 4 bit widebus for now until this is figured out. I'm sorry for the inconvenience, I'll test this better before it comes back.
Please let me know if you are still getting problems now!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version