Rockbox Technical Forums
Support and General Use => Hardware => Topic started by: bbildman on October 08, 2014, 11:52:55 AM
-
When I plug in the USB comment using 3.13 firmware, the USB works fine, with my Clip drives. Soon as I update to the newest build (10-09-2014 and 10-08-2014), the computer shows Rockbox connected, but no drives available for connect.
I reinstalled 3.13 and USB works fine.
Help?
-
You can either stick 3.13 or use the Sandisk firmware for USB transfer.
-
Yeah, I figured that, I'll stick to 3.13...as an aside, has this issue been reported before?? Thanks
-
Yeah, I figured that, I'll stick to 3.13...as an aside, has this issue been reported before?? Thanks
Yes, there are a lot of random USB bugs. Usually newer is more stable, but not always.
-
You can either stick 3.13 or use the Sandisk firmware for USB transfer.
Hi, been thinking about your reply above. The reason I decided to try the daily build for the Clip Zip is because the following notation was posted on the Major Changes page::
"Major changes since version 3.13 (in git)
2014-09-28: Improved battery life on the Clip v2, Clip+, Clip Zip and Fuze v2"
I figured I'd try it because of the battery life issue, but being I can't make a disk connection via the USB port with the daily build, I went back to 3.13.
And the reason I didn't keep the dev build and just use the Sandisk firmware for USB transfer was that each time I disconnect the Clip (after adding or changing files with the Sana firmware) the Clip spends a considerable amount of time "refreshing" and I have a lot of files on the Sansa so it takes a while....whcih was one of the original reasons I switched to Rockbox.
Thanks anyway.
-
You have this problem in all case ?
1. Plug USB when player on.
2. Plug USB when player off.
3. When player off, press "select" (middle button) and connect USB.
-
You have this problem in all case ?
1. Plug USB when player on.
2. Plug USB when player off.
3. When player off, press "select" (middle button) and connect USB.
Yes to 1 and 2, I will install the new build and try #3 and let you know, thanks
-
You have this problem in all case ?
1. Plug USB when player on.
2. Plug USB when player off.
3. When player off, press "select" (middle button) and connect USB.
Ok, here's the results::
If I press the Select button (player off) while I connect, the Rockbox boot screen flashes for a second, then goes black, the laptop shows the Sansa Clip connected (Sansa ClipZ drive) and I can read the Internal memory of the clip, but the microdisk I have inserted is not available at all. When I connect the Clip Zip normally either on or off, the laptop reports a 6 USb device, Dirve I and J, but the device never boots into those drives even though it shows the "Connected" screen. And the usual little device icon (Safely remove Hardware) is not there
If I hold the left button, it of course boots into Original Firmware and I see both drives, but when disconnected, it stays in Original firmware mode, and takes forever to refresh.
Only the 3.13 Rockbox boots normally into my 2 drives (1 is the Sansa, the other is the microchip drive)
All I want is to be able to use a build that has the Improved battery life described in the recent additions.
-
What OS you use? Can you do test on another OS (if you can do test on linux, attach dmesg output) or on another computer?
-
What OS you use? Can you do test on another OS (if you can do test on linux, attach dmesg output) or on another computer?
Windows 7 64 bit, my other laptop (same OS) does exactly the same thing.
Reverted back to 3.13, unless you all can come up with something that explains and fixes this.
Thanks
-
You have this problem in all case ?
1. Plug USB when player on.
2. Plug USB when player off.
3. When player off, press "select" (middle button) and connect USB.
The only reason I have gone down this path is to be able to have the power enhancements active in the new builds.
Well, I finally found out a way to have installed most recent daily build and to allow a USB connection.
First off even the newest daily continues to disallow me from connecting to the USB port and have the laptop see it (I get a "6 USB device connected with drives I:/ and J:/", but no I: and J: show up at all).
The zip will charge ok, but I have no access to the contents of the zip or drive J.
So, what I CAN do is boot the device into original firmware (hold L button and connect) and then I DO get both drives. My complaint with doing that was when I disconnected, it continues in original firmware, and starts refreshing, which takes forever. So I hold the power key down for maybe 20 seconds while it is still connected to the USB port, which turns the power off, disconnect and then when I power on, it boots directly into Rockbox.
If you can figure out why the daily build refuses to connect correctly to the USB and have access to the zip and the microdisk drive, please post here. 3.13 works perfectly in USB mode.
Thanks again.
-
bbildman:
Can you check my latest build?
http://gdurl.com/c_OQ/download
-
I copied your .rockbox directory over mine, and reconnecting it to my laptop usb port still give me the same message "connected to a 6 USB device (drives I and J)" and then never comes up with the computer being able to access the drive (microHD) or the Sansa Zip. I know this is a dev build problem because the same thing happens on my other laptop.
I guess I will simply recopy all my .rockbox files back to the Zip.
:(
I reinstalled the 3.13 and everything is back to normal - the laptop recognizes the Zip and the drives.
-
Could you try another theme on the Zip (maybe rockbox_failsafe for now)? For some odd reason, there appears to be an interaction with USB functionality in some cases. Old themes may also need an update.
I have had very few problems with USB on my Clip+' while using current builds. My old one would sometimes hiccup and freeze when plugged in while still powered off, the new one hasn't done that so far in spite of nominally the same bootloader version. Aside from that, they've been working splendidly, with no data corruption issues or anything.
-
I installed the latest dev build for the ZIP (8a078d7) via the Rockbox utility, and then disconnected. Turned it off and on again, changed the Theme Setting to rockbox_failsafe, reattached to USB port, and get the same "connected to a 6 USB device (drives I: and J:) with subsequent no way to see the Sanza or the microHD drives....the computer does NOT recognize the device (drives)
Have no clue.
Back to 3.13 and all is well.
I am willing to keep on trying different methodologies, just keep them coming.
Can you tell me what I will gain by using a dev build for the ZIP....for instance, how much better is the battery use (slower drain) will I have if I use the dev build??
The workaround I CAN use if I use the dev build is to connect it, and then hold the power key down for 20 seconds or so (still USB connected) until it powers down. The hold the L select button while powering up so that it boots into OF, which the computer reads as ok. Then before I disconnect, I again hold the power button down until it turns off (so that I do not have to go through the interminable refreshing the OF insists on if I JUST disconnect with OF runninjg), then disconnect, and turn it on again...to which it boots into the dev build.
The only reason I would do that sequence would be if you can tell there are significant advantages to using the latest dev build over the 3.13
Thanks again for your help and time.
Bernie
-
If you agree be tester we can try localize (bisect) regression.
http://knk.bplaced.net/rockbox-usb/rockbox1.zip
-
Tell me what does that entail...being a tester? Also what is the "http://knk.bplaced.net/rockbox-usb/rockbox1.zip"
Also, would you PLEASE answer my query...what advantages will the new dev build give me over 3.13 with my Zip??
If those advantages are minimal (in my opinion) I would probably rather stay with 3.13
-
The developer is giving you an opportunity to test a build that includes patch sets that have not yet been included to the mainline code base.
Whether you use his builds or not is up to you, but in my honest opinion no one should be using the release builds at this stage.
They are only stable in name, not in nature.
The development builds include several years worth of stability improvements, optimizations, and additional features.
[Saint]
-
Tell me what does that entail...being a tester?
Just install builds when I post it and check have this build problem with usb or not.
Also what is the "http://knk.bplaced.net/rockbox-usb/rockbox1.zip"
First build for test.
Also, would you PLEASE answer my query...what advantages will the new dev build give me over 3.13 with my Zip??
If those advantages are minimal (in my opinion) I would probably rather stay with 3.13
http://www.rockbox.org/wiki/MajorChanges + bug fix + big improvement in battery life in near future. And other improvements in future.
I don't have your problem, but I agree waste my time to fix this problem. If you agree help with testing we can try fix it.
-
We have a change log on the front page too if you want to see what been added in the 2 years since 3.13.
-
Mihail. will be glad to test your builds and report. But just to make sure :: I will be installing the builds you upload, when I unzip the files ( to a .rockbox folder on my computer), I will simply copy that entire directory to my Sansa Zip .rockbox folder, meaning overwrite each folder and each file within the Sansa .rockbox folder...and that I will not lose any of my settings or configurations, correct??
You said "Just install builds when I post it and check have this build problem with usb or not." -- will the daily dev builds be the ones you want me to test, or will you upload specific builds here to this thread that pertain to the possible USB problem? Thus far, none of the dev builds corrects the USB problem
Soon as you reply to this I will start and report back regarding the USB problem.
Thanks
-
"We have a change log on the front page too if you want to see what been added in the 2 years since 3.13."
-----------------
Saw that, and noted, the one I am especially interested in is the "Improved battery life on the Clip v2, Clip+, Clip Zip and Fuze v2"
The inability to do a connection to the USB port of my laptop remains my main concern, though I have found a work-around so I can keep all the build uploaded installed on the Sansa Zip, thanks again
-
Preferred way to test:
1. insert player and rename your .rockbox folder to something else (.rockbox1)
2. unpack my build to player
3. poweroff player
4. test it
5. remove .rockbox folder and rename .rockbox1 to .rockbox
-
You said "Just install builds when I post it and check have this build problem with usb or not." -- will the daily dev builds be the ones you want me to test, or will you upload specific builds here to this thread that pertain to the possible USB problem? Thus far, none of the dev builds corrects the USB problem
I want try find commit which introduce this problem. So I just try to build revision between 3.13 release and 10-08-2014.
-
You said "Just install builds when I post it and check have this build problem with usb or not." -- will the daily dev builds be the ones you want me to test, or will you upload specific builds here to this thread that pertain to the possible USB problem? Thus far, none of the dev builds corrects the USB problem
I want try find commit which introduce this problem. So I just try to build revision between 3.13 release and 10-08-2014.
Very good news::
I unzipped your rockbox1.zip to my Sansa Zip, (Version 1b90645M-150215) and voila...the laptop now correectly sees the Sansa and it's microHD insert, as Drives I: and J:, so it looks like all is well on that end.
Of interest, today's dev build (0f34c51-150215) does NOT connect to the USB port correctly.
I have tried this update on both of my Sansa Zips and both behave the same, looks like you found the problem...can you explain what it was??
:)
-
It just beginning in long hard way :)
I build 3.13 in my environment (compiler/libs) to be sure that ok.
Next test:http://knk.bplaced.net/rockbox-usb/rockbox2.zip
-
It just beginning in long hard way :)
I build 3.13 in my environment (compiler/libs) to be sure that ok.
Next test:http://knk.bplaced.net/rockbox-usb/rockbox2.zip
rockbox2.zip does not work (not recognized as Sansa) on laptop.
Keep 'em coming.
Where are you located? I am American but live in Spain, so if you're going by US time, I will be out of touch for 8 or so hours (as Spani time is 8 hours ahead...when you're awake, I'm sleeping often. If you are in Eastern Europe (going by your name, no disrespect intended), you're 2 hours or so ahead of me
-
http://knk.bplaced.net/rockbox-usb/rockbox3.zip
Yes, I am from Eastern Europe (Belarus).
-
http://knk.bplaced.net/rockbox-usb/rockbox3.zip
Yes, I am from Eastern Europe (Belarus).
Rockbox3.zip does not connect correctly.
:(
-
http://knk.bplaced.net/rockbox-usb/rockbox4.zip
In next 8-10 builds we should define problem place.
-
http://knk.bplaced.net/rockbox-usb/rockbox4.zip
In next 8-10 builds we should define problem place.
Rockbox4.zip (8fcce96M) works correctly. the only difference between the Rockbox firmware and the OF is that OF connects very quickly, the RF take a little while to show the drives in explorer.
Now what?? Should I leave this build on the Sansa, or revert to Rockbox1.zip??
The Sansa is recognized when connection is made both from a power on or off state.
-
No, you should test next build.
http://knk.bplaced.net/rockbox-usb/rockbox5.zip
-
No, you should test next build.
http://knk.bplaced.net/rockbox-usb/rockbox5.zip
Heh!
Rockbox5.zip (4f3f639M) does NOT work.
:)
-
http://knk.bplaced.net/rockbox-usb/rockbox6.zip
-
http://knk.bplaced.net/rockbox-usb/rockbox6.zip
Rockbox6.zip (737dafeM) does NOT work.
:) :)
Going to bed in the next 10 minutes or so, it may be tomorrow before you hear from me if for the next build try. Sorry my USB problem is creating so much of a mess....but it's clear SOMETHING is wrong in some of the builds' code.
-
http://knk.bplaced.net/rockbox-usb/rockbox7.zip
Ok, test it when you have time. In any case we very close :)
-
http://knk.bplaced.net/rockbox-usb/rockbox7.zip
Ok, test it when you have time. In any case we very close :)
Rockbox7.zip (47785caM) works
-
I'm just chiming in here to make sure you're aware that you can always boot the original firmware to facilitate a USB connection should you need to.
One of the main issues here regarding USB is that virtually no active developers use Windows or Mac, and generally speaking linux based distributions are a lot more permissive in regards to USB (for better or worse). With Windows, there's so many variables that can throw spanners in the works its not even funny. It makes it very hard to debug.
Its usually never particularly clear whether you're chasing a bug with the embedded system (Rockbox) or the host environment (Windows).
[Saint]
-
I'm just chiming in here to make sure you're aware that you can always boot the original firmware to facilitate a USB connection should you need to.
Its usually never particularly clear whether you're chasing a bug with the embedded system (Rockbox) or the host environment (Windows).
Saint, that's a given (booting into OF, but you realize that IF you do that to get the PC to recognize the Sansa, when you disconnect, you (meaning me) have to wait some 10 minutes for the OF Sansa to "refresh" - and that is one of the big reasons I switched to Rockbox, so as not to have to deal with the refresh issue.
I can guarantee you the bug is within the Rockbox code, because SOME of the Rockbox builds (including the 3.13 stable and others) DO boot quite nicely via USB on my Windows 7 machine.
-
One of the main issues here regarding USB is that virtually no active developers use Windows or Mac, and generally speaking linux based distributions are a lot more permissive in regards to USB (for better or worse). With Windows, there's so many variables that can throw spanners in the works its not even funny. It makes it very hard to debug.
Yes, think same and use linux 16 years ;) But it good if rockbox can be usable with others os.
http://knk.bplaced.net/rockbox-usb/rockbox8.zip
-
Good morning
Rockbox8.zip (f285a0fM) does not work.
-
http://knk.bplaced.net/rockbox-usb/rockbox9.zip
-
http://knk.bplaced.net/rockbox-usb/rockbox9.zip
Rockbox9.zip (a9f2086M) works.
-
http://knk.bplaced.net/rockbox-usb/rockbox10.zip
-
http://knk.bplaced.net/rockbox-usb/rockbox10.zip
Rockbox10.zip works.
-
http://knk.bplaced.net/rockbox-usb/rockbox11.zip
-
http://knk.bplaced.net/rockbox-usb/rockbox11.zip
Rockbox11.zip does not work.
-
http://knk.bplaced.net/rockbox-usb/rockbox12.zip
-
http://knk.bplaced.net/rockbox-usb/rockbox12.zip
Rockbox12.zip works.
-
Ok, we got it:
http://git.rockbox.org/?p=rockbox.git;a=commitdiff;h=074e911859a0d3464fde9b701b3cff712c5826e0
I try ask pamaury about it.
-
bbildman:
Last step - can you install latest rockbox (http://build.rockbox.org/data/rockbox-sansaclipzip.zip) and confirm that ok?
Developers want to know, why we have special case with your hardware/os - can you do another test?
1. install http://www.gevaerts.be/rockbox-logf.zip
2. reboot player
3. connect to usb, wait some time (15-20s should by enough) and disconnect it
4. in player menu: system > debug > dump log file
5. connect player to usb again
6.you should have new "logf.txt" in .rockbox folder - attach this file to your post
-
bbildman:
Last step - can you install latest rockbox (http://build.rockbox.org/data/rockbox-sansaclipzip.zip) and confirm that ok?
Developers want to know, why we have special case with your hardware/os - can you do another test?
1. install http://www.gevaerts.be/rockbox-logf.zip
2. reboot player
3. connect to usb, wait some time (15-20s should by enough) and disconnect it
4. in player menu: system > debug > dump log file
5. connect player to usb again
6.you should have new "logf.txt" in .rockbox folder - attach this file to your post
Ok, I assume "http://build.rockbox.org/data/rockbox-sansaclipzip.zip" is today's dev build. I installed that, and it boots perfect as it is supposed to.
I also assume this build includes the code for "Improved battery life on the Clip v2, Clip+, Clip Zip and Fuze v2" Is that correct??
After I upload the dump file, should I reinstall the "http://build.rockbox.org/data/rockbox-sansaclipzip.zip" files?? And I also assume all future dev builds SHOULD have the code that now allows me to connect to the USB?
Would you mind telling me why MY system had this problem...do you think others also have it but never tried the new dev builds??
Here is the dump file as an attachment
-
I also assume this build includes the code for "Improved battery life on the Clip v2, Clip+, Clip Zip and Fuze v2" Is that correct??
Yes. But it only small part. We still work on this.
After I upload the dump file, should I reinstall the "http://build.rockbox.org/data/rockbox-sansaclipzip.zip" files??
Yes.
And I also assume all future dev builds SHOULD have the code that now allows me to connect to the USB?
Yes, we fix it :)
Would you mind telling me why MY system had this problem...do you think others also have it but never tried the new dev builds??
Your hardware/driver/os send some strange command thought usb. We can't reproduce it - I try winxp and win7 - all dev builds work correct.
-
THANK YOU.
I hope I have not been too problematic, not only with my reporting of the issue in the first place but in my implementation of your testing.
Bernie
-
:) Thanks for bug report and testing!
P.S. Something wrong with logf, probably we need another test - so check forum for new post.
-
Ok no problem, just let me know
-
Thanks for testing so far! It's been really helpful to have someone who had the problem actually help with debugging it, this bug could have survived for a lot longer without your help.
I've uploaded a new test build with the logf issue fixed (we logged too much, which made us lose the line we actually care about) to http://www.gevaerts.be/rockbox-logf-2.zip (http://www.gevaerts.be/rockbox-logf-2.zip). If you could test that (same procedure as the previous one) and upload the resulting logf.txt, I think we'd have everything we need to fully understand what's going on and what Windows is actually trying to do.
-
Thanks for testing so far! It's been really helpful to have someone who had the problem actually help with debugging it, this bug could have survived for a lot longer without your help.
I've uploaded a new test build with the logf issue fixed (we logged too much, which made us lose the line we actually care about) to http://www.gevaerts.be/rockbox-logf-2.zip (http://www.gevaerts.be/rockbox-logf-2.zip). If you could test that (same procedure as the previous one) and upload the resulting logf.txt, I think we'd have everything we need to fully understand what's going on and what Windows is actually trying to do.
Ok, here it is attached
Let me know if this one is bad, and we can do it again.
-
Thanks, this is what we need.
The SCSI commands Windows tries to use that we don't implement are:
- 9E, which is "service action", which seems to be used to find out the physical block size (which is used for those modern disks that have 4K blocks internally but pretend they have 512K blocks as usual) and then presumably optimise for those.
- A1, which is "ATA Passthrough", which is used for things like S.M.A.R.T.
Neither of those is really essential, although I guess ATA passthrough would be nice to have at some point, for those players with ATA disks in them.
-
Thanks, so I guess for now and into the future I am good-to-go for my Zip(s).
I REALLY like the Zip, and especially with Rockbox installed. The original reason I even used RB to begin with was that my original Zip's up volume button stopped working and I found out that RB had a software control of it, which the OF does not. I also implemented a quickscreen with JUST the L and R buttons enabled, for lowering and raising the volume, so it's easy to do it on the While-Playing screen without having to go through menus to access the menu volume controls. I found this video that clued me in to the volume control quickscreen::
https://www.youtube.com/watch?v=Yp163_cwSy4
Thanks again.
I'll keep track of the daily builds and if I see some upgrades that will help me, I'll just use the utility to install it.
Bernie
-
Unless my mind is playing tricks on me, it seems with this new dev build I installed yesterday, my music and books sound clearer and better. I guess it doesn't make any difference if it my mind doing it or the Rockbox, I am a happy camper.
-
Mihail, is this the page in which I can find all the new "additions" to the daily dev builds::
http://www.rockbox.org/recent.shtml#code
Thanks
-
Yes. Or http://git.rockbox.org/?p=rockbox.git;a=shortlog or http://git.rockbox.org/?p=rockbox.git;a=log
-
Hi Mihail,
No complaints, but I notice regarding Windows 7 USB connection takes a significant time to finally give me the Zip's and it micro-drive File Explorer connection.
When I connect to the laptop, I get the "Rockbox Rockbox.org device enabled" balloon, then there is a short wait when the Autoplay pop-up (from Windows) displays. Then ofttimes there is maybe a 5 - 10 minute (or longer) wait until the Auto-play disappears and the 2 explorer windows show, indicating the I and J drive with the files displayed. When I had 3.13 installed, the drive windows popped up very quickly, as it does with the Original Firmware option is enabled on boot.
98a69ec is my current build, but when I reinstalled 27c7e47 (where you and I left off) is works quickly.
Is this correct, or must there be some more tweaking that need to be done.
(Sorry to bother you, Mihail)
Bernie
-
Someone else have idea whats wrong or we should try do bisect again?
-
People have had random problems with builds on the AMSv2 players since USB support was added. My guess is that bisecting will find weird things that make bugs more or less likely, but probably not fix much.
-
Mihail.
Couple new things::
I installed build 9076b433, and the first time I connected to the USB it worked ok, then the next time, the autoplay popups displayed and never finally connected to the drives with files showing, when I clicked "Open Content" in the autoplay box, it takes me to the drives but the display showed no files at all. This happens also with the 27c7e47 on occasion.
This problem is different than my original problem, where the computer never acknowledged the Sansa at all, whereas now it is hit and miss as to whether the Sansa and the microhd will display files even though I CAN look on the explorer for those drives, but no files.
Head scratcher, also see this thread here::
http://forums.rockbox.org/index.php/topic,48528.0.html
-
Can you try disable autorun/autoplay in windows?
Try use safe disconnect in windows before unplug player.
-
Ok, first I ALWAYS safe disconnect, so that's not a problem.
Also I tried disabling Autoplay; the options in Autoplay from control panel are::
1. Open Device Stage
2. Take No Action
I already tried "take No Action, and the Autoplay popups still open up, with option to Open Folder To View Files. If I wait a little while, and then click on that, the Folder Opens with an empty folder, rather than with the files inside.
I'll try it again, and restart windows to see if there's any difference with the restart.
Gets weirder by the minute.
-
Ok, I restarted and when the Zip is connected, the Autoplay (Take No Action) still pops up, and when I click the Open to View files, still 0 files.
Put it back to Open Device Stage, which is where it was when youy and were working on it in February.
Of interest also is when I connect it, between that time and when the Autoplay popups open, connections to the internet with my browser do not work, soon as the popup opens the web page displays
-
I can't find 27c7e47 revision in git. Rockbox12 have 21c5ffe.
-
Ok, I must have installed that one 27c7e47 AFTER you sent me 21c5ffe, I will install 21c5ffe again, and see if that works like before, I will get back to you.
Again, thanks, Mihail
-
21c5ffe works, I will stick to that one, seems the subsequent builds have a USB problem different from my original, but still a problem