Rockbox Technical Forums
Support and General Use => Audio Playback, Database and Playlists => Topic started by: antanas on May 09, 2012, 05:29:15 AM
-
Hello, I cannot boot into rockbox using d26a35d with my Sansa Clip Zip. It says scanning disk... and then a white screen appears with *PANIC* audio_reset_buffer_noalloc(): EOM (65536 > 0)
If I'm not mistaken it started happening with dae7a29 build and it does every time so I cannot use rockbox now
-
Check the filesystem for errors.
-
i did that with fsck.vfat and it said it have fixed whatever was wrong, but still it didn't help
-
This has also happened to my Clip Zip. Was working fine, now won't even mount, just goes to this white screen every time. Any help on at least getting it to mount so I can take a look at it?
Thanks
Post Merge: May 14, 2012, 05:19:21 PM
Just a quick update. I've managed to boot and mount the Clip Zip but only by booting in the Sansa firmware. I've then uninstalled Rockbox and put the Clip firmware (1.01.18) back on there. I tried to re-install Rockbox but had the same problem so have gone back once again to the Sansa firmware for the moment which is useless as I'm only using ALAC.
Will try reinstalling Rockbox again tomorrow but am open to any advice on how to fix this.
Thanks
-
Same deal just happened to me. Screenshot attached. I sure hope there's a fix for this!
My apologies that I can't offer more information about this. I'm a Rockbox nOOb at this point, and I'm just in the "how to break it" phase with my Clip Zip. Haven't yet moved up to the "how it gets fixed" stage. ::)
-
^^^ Reboot into the sandisk firmware and check the file system for errors.
Also, if this keeps happening, you can probably avoid that problem by disabling the file system cache (or maybe the database). If the file system isn't corrupt and you still get that error then I have no idea.
-
Yes -- and thanks for the informed input. I'd done that already, checking the filesystem that is, based on the prior posts. No errors found that I could see. I will keep your additional advice in mind (cache, database, etc.) if I have more trouble.
I managed to get the Clip Zip responsive by doing the 20+ second hold-down on the power button then repowering into the Sansa firmware. After that I removed Rockbox and reinstalled the original (1.01.18A) firmware.
I have since reinstalled Rockbox and I'll give it a try again for a few days. I am using a few themes, custom settings for scrolling, etc., so if I have to make a third attempt, I will forgo these niceties and "keep it simple." But for now it's working OK.
I might as well mention one other little thing. Prior to installing Rockbox the first time, I used Sandisk's utility and update the firmware from 1.01.18A to 1.01.20A, the currently latest Sandisk firmware. However when I installed the bootloader, I pointed it to 1.01.18A's .bin file for patching. I wonder if using 1.01.18A for this purpose, while overlaying 1.01.20A (installed) could have been a factor.
-
I might as well mention one other little thing. Prior to installing Rockbox the first time, I used Sandisk's utility and update the firmware from 1.01.18A to 1.01.20A, the currently latest Sandisk firmware. However when I installed the bootloader, I pointed it to 1.01.18A's .bin file for patching. I wonder if using 1.01.18A for this purpose, while overlaying 1.01.20A (installed) could have been a factor.
No, the sandisk firmware is completely irrelevant.
-
OK, that's good to know.
-
Right, I managed to fix it in the end. Here's what I did.
1) Held down the power button for 20s.
2) Booted the Clip Zip up in native firmware (hold left and power)
3) Connected to computed via USB, uninstalled Rockbox and deleted .rockbox directory on Clip Zip (must be able to see hidden folders to do this).
4) Reloaded Sansa firmware 1.01.18 and restarted Clip Zip
5) Connected CZ to computer and reinstalled Bootloader and Rockbox
6) Done!