Rockbox Technical Forums
Installation / Removal => Rockbox Utility => Topic started by: John on June 05, 2009, 07:09:56 PM
-
I have a Sansa c250 v 1 and use Ubuntu as my OS
I was haveing some corrupted music files appearing in my music folder and decided to reinstall a newer version of Rockbox.
I uninstalled Rockbox using the utility, looked in the manual and then unistalled the .rockbox folder and something else named rockbox on the Sansa to remove the bootloader.
I then updated my version of Sandisk Version 01.01.07P
I can install Rockbox but it will not run without the bootloader.
The utility does not autodetect my Sansa but I manually pointed to the mount point.
When I use the current utility to intall the bootloader I get the following error message:
"Permission for disc access is denied
This is required to install the bootloader"
Elsewhere on this forum I read that Sansas like V1.0.7 so I downloaded that version.
Again I had to manually point to the mount point but now the output is:
"Starting bootloader installation
Searching for sansas
Downloading file firmware.mi4
Download error: received HTTP error 404"
What should I do next?
-
The utility does not autodetect my Sansa but I manually pointed to the mount point.
You should figure why autodetection doesn't work. If autodetection of a Sansa doesn't work you won't be able to install the bootloader, so don't "just" select it manually.
"Permission for disc access is denied
This is required to install the bootloader"
Well, this sounds pretty much like you are lacking the required disk access permissions. Please post the output of the About / System Info dialog (you can copy from that dialog).
Elsewhere on this forum I read that Sansas like V1.0.7 so I downloaded that version.
Don't do this!
There was a bug in Rockbox Utility 1.0.8 and 1.0.9 that affected bootloader installation but only on Windows. Please don't just follow heavily outdated advice -- you really think that (now as the current release of Rockbox Utility is 1.2.1) this issue isn't fixed? Furthermore, there's a list of known issues on the Rockbox Utility wiki page and a list of fixed issues. Reading it might help figuring if such an issue still persists.
Download error: received HTTP error 404"
Well, HTTP error 404 means "file not found". Most likely there was a problem with the mirror used. Just try again. But if autodetection didn't work installing won't work either. You really need to fix the permission issue first.
-
Bluebrother, thank you for your reply.
Here is the About>System output:
OS
CPU: i686
System: Linux
Release: 2.6.28-11-generic
Version: #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009
Username
john
Attached USB devices
VID: 03f0 PID: 5311, HP Officejet 6300 series
VID: 046d PID: c518, (no description available)
VID: 0781 PID: 7451, (no description available)
VID: 1d6b PID: 0001, (no description available)
VID: 1d6b PID: 0002, (no description available)
Filesystem
/, 39899 MiB available
/lib/init/rw, 1002 MiB available
/proc, 0 MiB available
/sys, 0 MiB available
/var/run, 1001 MiB available
/var/lock, 1002 MiB available
/dev, 1001 MiB available
/dev/shm, 1001 MiB available
/dev/pts, 0 MiB available
/sys/fs/fuse/connections, 0 MiB available
/lib/modules/2.6.28-11-generic/volatile, 999 MiB available
/sys/kernel/security, 0 MiB available
/proc/fs/nfsd, 0 MiB available
/proc/sys/fs/binfmt_misc, 0 MiB available
/home/john/.gvfs, 0 MiB available
/media/Sansa c250, 1630 MiB available
I am back on version 1.2.1 but autodetect is not working
Any suggestions?
-
Any suggestions?
The output shows that you are running Rockbox Utility under a normal user account. While this is perfectly fine for the main installation the bootloader installation requires direct disk access, i.e. it requires write access to the players device file. Usually this is nothing a normal user is allowed to do.
Please start Rockbox Utility from a root account (either by using sudo or directly starting from a root shell) for bootloader installation. After you installed Rockbox autodetection will also work as normal user (you won't be able to update the bootloader as normal user, but updating the bootloader is almost never needed). Hence the error message "Permission for disc access is denied. This is required to install the bootloader" which is exactly what the problem is. Unfortunately, until the player has been successfully detected it isn't possible to tell which device file it is to give a more detailed error description. Initial autodetection requires raw disk access too (it won't write to the disk but it needs access).
-
Having a bit of a problem getting the utility to run
Here is the output from my terminal:
john@john-laptop:~/Desktop$ sudo rbutilqt-v1.2.1
sudo: rbutilqt-v1.2.1: command not found
john@john-laptop:~/Desktop$ sudo ./rbutilqt-v1.2.1
sudo: ./rbutilqt-v1.2.1: command not found
john@john-laptop:~/Desktop$ Run sudo ./rbutilqt-v1.2.1
bash: Run: command not found
john@john-laptop:~/Desktop$
What is the correct syntax to run the utility as sudo?
-
The binary should be named "rbutilqt". You need to extract it from the archive that you downloaded:
tar xjf /path/to/rbutilqt-v1.2.1.tar.bz2That will create a directory called "rbutilqt-v1.2.1". Then run:sudo ./rbutilqt-v1.2.1/rbutilqt
-
Thank you cool_walking and bluebrother.
My sansa is working again :)