Rockbox on Clip+ "*PANIC* disk_init failed!"

[vladimir88x7]

Sorry that I have re-opened this thread and i just tried to install rockbox on my clip plus, but after trying out 3 different filmwares during installation i still get the "*PANIC* disk_init failed!"  error.  At one point It did go to the rockbox screen but it just froze.  I tried out
clipplus01.02.09
clipplus01.02.13
clipplus01.02.15
please don't give me a response that involves manual install and command prompt, i got lost trying to do that.
Post Merge: June 20, 2011, 08:12:44 PMand the clppa.bin file is not working for me with bootloader

[saratoga]

please don't give me a response that involves manual install and command prompt, i got lost trying to do that.

Stick to the Sandisk firmware until we get around to releasing an updated bootloader.  Then the automatic install should work.

[vladimir88x7]

I see that Rockbox 3.9 has been released, has the bootloader been fixed to work with the clip+?

[bertrik]

No

[danlayman]

I'm having the same problem and the suggestions made on other threads aren't working.  I've tried the suggestions made here and on other threads were the same problem was experienced.  I think the clip plus should be removed from the list of stable supported device builds  since any clip plus purchased at this point will either require extensive searches and investment of time or now work at all. 

[saratoga]

I think the clip plus should be removed from the list of stable supported device builds  since any clip plus purchased at this point will either require extensive searches and investment of time or now work at all. 

New hardware revisions aren't a reason to change the status.  If you can install, the port will be stable.  If not, you're not running rockbox anyway

[bertrik]

I think we should just release a new bootloader for the clip+ and not do silly things like declare it unstable or anything like that.

I can help making a new bootloader, I just need to know a few things about the procedure:
* has it now been conclusively confirmed that a new bootloader fixes the problem?
* which version should we use to create the bootloader, just the most current one?
* do we need to tag anything in the version system?
* we should probably make new bootloaders for the other AMSv2 targets too
* where do I put the binaries so they get picked up by RbUtil (who should I ask about this?)

[danlayman]

I think that at minimum a notification should be made on the main page that a clip plus purchased from now forward will not be rockbox-able. For many people this player is purchased for the sole purpose of getting into rockbox.

I've spent many hours now researching and $anaged to provide the installer three different clip plus bin files that are supposed to be supported. Rockbox still won't load despite all indications that ot is installed in the root directory of the player. 

I'm not a tech genius but I'm not stupid either and am probably in the top quarter or so of typical users.  If this first experience with a product like rockbox occurs its not good for the user, the product or its future.

Please don't misunderstand - I respect and admire this concept and the people who spend so much time developing it.

I know you can't be resoonsible or keep up with every hardware change but this problem is getting pretty widely reported now and a suitable fix that a typical user can implement hasn't been identified.  Please don't cause people to buy a player that they can't use to implement this and then to want to toss the player and get a bad opinion of rockbox. I don't want to criticize the product - I want it to work for me and for others.  Right now the situation with this player - probably the one chosen most often by new first time users- doesn't do that and that isn't a good thing. Anything I can do to help or provide details on the problem I would be happy to do.

[saratoga]

* do we need to tag anything in the version system?
* we should probably make new bootloaders for the other AMSv2 targets too
* where do I put the binaries so they get picked up by RbUtil (who should I ask about this?)

We need to tag a new binary release in SVN, then ping Bagder to get it uploaded.  Then everything else will work.  Unfortunately, I can't remember how to do that

I think that at minimum a notification should be made on the main page that a clip plus purchased from now forward will not be rockbox-able. For many people this player is purchased for the sole purpose of getting into rockbox.

If the updated bootloader didn't fix the problem, then you have some unique issue that no one else has encountered.  We're not going to update the front page for some issue that apparently only affects you. 

[danlayman]

Perhaps, but there are  postings here and other forums of the same issue - so far, I haven't seen examples of it being solved.  I think only the players purchased since roughly July 4 have the issue due to the latest firmware version.  So I wouldn't expect a huge number of people reporting this yet, but I expect there will be.

I'll keep playing with it, but I'm not optimistic.  Of course its entirely up to you whether to make some kind of visible notification to potential purchasers of the player.  I was only suggesting it to minimize the chances of people being disappointed after purchasing the player and getting a negative opinion of rockbox.


I really think the whole concept of what you're doing is cool.  It's amazing really.  I just don't want it to be diminished by people purchasing  this player to experience rockbox and experiencing only an exercise in frustration.

Honestly, I don't believe the problem is unique to me, I hope it is.  Its a cheap player and I can return it if I want to so its not a huge problem for me, just a disappointment.

[saratoga]

Perhaps, but there are  postings here and other forums of the same issue - so far, I haven't seen examples of it being solved.

I'm not aware of any.  Could you link some?  Actually, if this is a real problem, perhaps you should start a thread detailing what happens when you install the new bootloader so that people are aware it exists.

[danlayman]

That's a good idea. I'm going to uninstall everything and start from scratch again. I'll take notes of each step and what happens and post after I'm done. Probably be tomorrow until I'm able.

I had googled the error message that appeared when I tried to boot and came up with a number of threads. I can do that again and post links for that as well

[saratoga]

I think we should just release a new bootloader for the clip+ and not do silly things like declare it unstable or anything like that.

I can help making a new bootloader, I just need to know a few things about the procedure:
* has it now been conclusively confirmed that a new bootloader fixes the problem?
* which version should we use to create the bootloader, just the most current one?
* do we need to tag anything in the version system?
* we should probably make new bootloaders for the other AMSv2 targets too
* where do I put the binaries so they get picked up by RbUtil (who should I ask about this?)

I found the wiki page on releasing bootloaders and tagged one.  One question though, since this only seems to matter on the Clip+, maybe it would make sense to just release it as v3.1 for the Clip+ and leave the FuzeV2 and ClipV2 alone?  I don't really see a point in releasing a new bootloader for them as they have been discontinued and we don't yet have USB working.

[danlayman]

I downloaded the rockbox utility zip and opened.  I did an automatic complete install.  It asked for the firmware bin file which I provided (clppa.bin) version v01.02.15A.  I had also previously used the sandisk firmware upgrader to changee the firmware version of the player to the same (from 16A).  The installation completed and said it was finished.  I disconnected the device once complete.  It said upgrading firmware, then powered off.  Upon powering up, it gave message *PANIC* disk_init failed!.

I realize this isn't a very detailed explanation.  But I'm not sure what else to say.  All of the rockbox files are on the root of the player.  But it really isn't a  very complicated process.  What am I missing??  I can still boot to the sansa firmware but rockbox fails.

[WingTheDing]

Hey Im at the same point.

Is there actually a stable version for clip+ rev.1 
Or should we just wait until the bootloader or the Rockbox build has been updated and the bug is fixed ?
The main problem I saw is that its hard to find the information, that the actually bootloader/rockbox build isnt stable with the clip+ rev.1
because everywhere is standing that it's stable. is it?

I tried a lot of OS and rockbox version and nothing work... so were there ever a stable version?

sorry for the bad English...Im from Germany