Rockbox Technical Forums
Installation / Removal => Rockbox Utility => Topic started by: margon on June 07, 2011, 05:20:51 AM
-
Hello everyone
I just bought Sansa Clip+
Got it just minute ago and now I want to install Rockbox. I have firmware V01.02.15F.
I connect player to PC in MSC Mode - Player is mapped at drive G: and microSD slot at drive H:
When I try to autodetect player in Rockbox Utility, it simple crashes as on picture related (Program Rockbox Utility stopped working)
(http://i52.tinypic.com/2cyfvqd.png)
Will it be OK if I select options as on this screenshot:
(http://i52.tinypic.com/2lvzeav.png)
Or is it more serious problem connected with 64 bit OS? It's my first day with Clip+ so I don't want to brick it.
edited: Firmware 01.02.15 ofc, sorry for mistake
-
That's interesting. Can you please post the output of the Help / Troubleshooting / System Trace dialog before and after the crash? It might be an issue related to 64bit.
Selecting the correct device manually is safe usually. Rockbox Utility tries to not mess up things even if you select the wrong drive, but then the installation obviously won't work so we generally recommend using autodetection.
-
I'm not sure what caused the problem but seems like it's fixed now. As autodetection didn't work, I set everything manually (device Sansa Clip+ and drive letter to G), then successfully installed Rockbox into it (it's running pretty good).
Now (after Rockbox installation) I wanted to do autodetection again (as you asked me) and it works fine every time I try to run it
however, here is the output from System Trace:
before detection http://pastebin.com/BRknwJrP
after detection http://pastebin.com/MwvXUPNp
Also, I want to notice that I have UAC disabled and I'm running at administrator privilliges
-
I'm not surprised by this, and it isn't fixed at all. Rockbox Utility uses various methods to figure the connected player. One of the first (the first? Can't check right now) is by looking for an existing installation. If that is found there is no need to try anything else, so any other detection method that might cause the crash isn't executed anymore. If you want to reproduce it uninstall Rockbox first or delete the file rockbox-info.txt
-
It's a little bit weird. As you said, I changed name of rockbox directory and then autodetected player. Now, every time I try, it works (I mean it doesn't crash rbutility)
Every time I try to detect player, I've got message that "No mount point was found and I have to select it manually". Here's system trace: http://pastebin.com/Fjh9pLnQ
-
Every time I try to detect player, I've got message that "No mount point was found and I have to select it manually". Here's system trace: http://pastebin.com/Fjh9pLnQ
This is pretty normal. There is currently no way that allows detecting the mount point of a clip+, detecting the player itself is much easier (as in most cases this is possible via the USB IDs). No idea why you experienced crashes earlier, the trace doesn't show anything that could explain that.
-
I get this too. Except I get it later on. I manage to detect my player and everything its just when it starts extracting the files that it crashes! I've tried many times and every time it downloads the daily build fine and then when it gets to the extracting part that's when it crashes! :(
EDIT: Never mind it just hangs a little bit. But after a while it gets back on track and finishes up. Good job Rockbox Crew :) Keep the good work up!
-
Same thing with new clip+ win7 64.
Auto detect lead to a crash.
Had to manually select.
-
Can you check if this also appears on a 32bit Windows7?
-
So, no one has ended up looking into it, right? I have this issue on Windows 8.1 x64 both with 1.4.0 and the latest official dev build. It doesn't even matter whether the player is connected or not.
-
So, no one has ended up looking into it, right?
Pretty sure it was fixed a long time ago.
I have this issue on Windows 8.1 x64 both with 1.4.0 and the latest official dev build. It doesn't even matter whether the player is connected or not.
Which issue?
-
Pretty sure it was fixed a long time ago.
Strange, maybe there's something weird about my PC setup. I've tinkered with USB devices in Control Panel before, for example.
Which issue?
Crash after clicking Autodetect, obviously. It also crashes after clicking System Info and when a player with Rockbox is connected. Here (http://pastebin.com/vwP1RqiZ)'s a System Trace output before the crash.
-
Strange, maybe there's something weird about my PC setup. I've tinkered with USB devices in Control Panel before, for example.
I'm also quite sure it was fixed -- this thread is almost 4 years old after all. Also, autodetection code has been rewritten completely, and at least the original issue was related to that. However, there is currently a bug: if you run autodetect with a player in MTP mode connected it crashes.
Crash after clicking Autodetect, obviously. It also crashes after clicking System Info and when a player with Rockbox is connected. Here (http://pastebin.com/vwP1RqiZ)'s a System Trace output before the crash.
What exactly does "tinkered with USB devices" mean? Since the current bug is in autodetection code and System Info doesn't run that it might be related to USB device enumeration. Unfortunately the trace doesn't show any hint in what could be going wrong here.
-
However, there is currently a bug: if you run autodetect with a player in MTP mode connected it crashes.
It doesn't depend on the connection mode for me. I've also tried deleting the utility's config file.
What exactly does "tinkered with USB devices" mean?
Um, nothing too extraordinary. I think I uninstalled USB devices once to try getting a gamepad to work wirelessly. Here (http://pastebin.com/rP5umsyp)'s a post-crash log without player connected.
-
However, there is currently a bug: if you run autodetect with a player in MTP mode connected it crashes.
It doesn't depend on the connection mode for me. I've also tried deleting the utility's config file.
While I cannot reproduce the issue I have a suspicion what could be causing this. Can you try if you can reproduce the problem with the file at the following link?
https://drive.google.com/open?id=0B8pPsvGJ3RdKN28zbTZTN1lWWkk&authuser=0
-
While I cannot reproduce the issue I have a suspicion what could be causing this. Can you try if you can reproduce the problem with the file at the following link?
https://drive.google.com/open?id=0B8pPsvGJ3RdKN28zbTZTN1lWWkk&authuser=0
Yep, the issue still persists.
-
Yep, the issue still persists.
I'm not sure if I like that or not -- at least it disproves my initial suspicion (which is kinda good, since that would have indicated some more fundamental underlying problem). New test version (it uses 1.4.1 as version number since I've already changed that in my local tree).
https://drive.google.com/open?id=0B8pPsvGJ3RdKYjJZMDc3eDFPOW8&authuser=0
-
I'm not sure if I like that or not -- at least it disproves my initial suspicion (which is kinda good, since that would have indicated some more fundamental underlying problem). New test version (it uses 1.4.1 as version number since I've already changed that in my local tree).
https://drive.google.com/open?id=0B8pPsvGJ3RdKYjJZMDc3eDFPOW8&authuser=0
Works just fine now though there is a warning message logged.
[system.cpp:449 WARNING] Error: SetupDiGetDeviceRegistryProperty item 71Also is it normal if my AMD FX-4300 is described as 586 in System Info? Does it mean something but Pentium architecture?
-
Works just fine now though there is a warning message logged.
Great :) So I can fix this issue the shortly and make sure it's in 1.4.1. The only thing that surprises me is that this issue didn't appear earlier ... the offending code hasn't been changed since years. The message logged is unproblematic -- it's just telling that there occured an error retrieving the description for a device (though I guess I should change that message a bit :) )
-
Hello,
The issue appeared to me as well and I was using the release version 1.4.0.
Thanks to bluebrother for dev build as the problem was that I should actually used MSC instead of MTP type of connection via USB.
So, the solution is: switch to MSC (in player system settings) and then run the utility.
-
Hello,
The issue appeared to me as well and I was using the release version 1.4.0.
Thanks to bluebrother for dev build as the problem was that I should actually used MSC instead of MTP type of connection via USB.
So, the solution is: switch to MSC (in player system settings) and then run the utility.
Don't get me wrong, I mean this in the nicest possible way, but when in doubt - use the manual (http://download.rockbox.org/daily/manual/rockbox-sansaclipplus/rockbox-buildch2.html#x4-70002.1).
USB connection.
To transfer Rockbox to your player you need to connect it to your computer. For manual installation/uninstallation, or should autodetection fail during automatic installation, you need to know where to access the player. On Windows this means you need to know the drive letter associated with the player. On Linux you need to know the mount point of your player. On Mac OS X you need to know the volume name of your player.
Note: The following steps require you to change the setting in Settings → System Settings → USB Mode to MSC from within the original firmware. Further note that all original firmware settings will be lost immediately after patching the bootloader, so you may need to correct this setting again after installing rockbox.
[Saint]