Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

Notice: Only Gecko based browsers prior to FF4 support the multipart/mixed "server push" method used by this log reader to auto-update. Since you do not appear to use such a browser, this page will simply show the current log, and not automatically update.

#rockbox log for 2013-06-13

00:03:28 Quit ender` (Quit: Q: What's the difference between ignorance and apathy? A: I neither know, nor care.)
00:04:20 Quit amboss (Ping timeout: 240 seconds)
00:15:26 Quit freqmod_ (Ping timeout: 256 seconds)
00:16:35 Join freqmod [0] (~quassel@cm-84.215.142.108.getinternet.no)
00:16:36 Join amboss [0] (b@catbert.neet.to)
00:17:15 Quit DexterLB (Read error: Connection reset by peer)
00:22:28 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
00:31:46 Quit bertrik (Remote host closed the connection)
00:36:14 Quit mc2739 (Ping timeout: 276 seconds)
00:38:28 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739)
00:42:38 Join dewlap [0] (~dewlap@2001:5c0:1000:a::e03)
01:00
01:06:16 Quit DexterLB (Read error: Connection reset by peer)
01:08:24 Quit tjb0607 (Quit: Segmentation fault)
01:11:32 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
01:15:08 Join Strife89 [0] (~Strife89@207-144-5-207.cstel.net)
01:31:51 Quit liar (Quit: huiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii)
01:38:37***Saving seen data "./dancer.seen"
02:00
02:08:47 Quit DexterLB (Read error: Connection reset by peer)
02:12:28 Quit Strife89 (Ping timeout: 240 seconds)
02:14:09 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
02:25:13 Quit krabador (Quit: Bah...)
02:32:17fs-bluebotBuild Server message: 3New build round started. Revision 9ad50ad, 217 builds, 18 clients.
02:39:41Mir:o
02:39:45fs-bluebotBuild Server message: 3Build round completed after 449 seconds.
02:39:46fs-bluebotBuild Server message: 3Revision 9ad50ad result: All green
02:40:23Mir\o/
02:50:19 Quit pamaury (Ping timeout: 240 seconds)
03:00
03:09:35 Quit lebellium (Quit: ChatZilla 0.9.90 [Firefox 22.0/20130605070403])
03:10:44 Quit tchan (Quit: WeeChat 0.4.1)
03:19:35 Quit thegeek (Read error: Connection reset by peer)
03:21:59 Join _dv_ [0] (~quassel@chello080108009040.14.11.vie.surfer.at)
03:22:17 Join kilroy [0] (~dewlap@2001:5c0:1000:a::e03)
03:22:52 Quit dv_ (Ping timeout: 264 seconds)
03:25:09 Join krabador [0] (~krabador@unaffiliated/krabador)
03:25:20 Quit dewlap (Ping timeout: 245 seconds)
03:25:29 Join Scromple [0] (~Simon@161.43.73.67)
03:28:45 Quit bluebrother (Read error: Operation timed out)
03:29:07 Quit fs-bluebot (Ping timeout: 248 seconds)
03:30:25 Join fs-bluebot [0] (~fs-bluebo@g224237032.adsl.alicedsl.de)
03:32:20 Join bluebrother [0] (~dom@rockbox/developer/bluebrother)
03:38:39***Saving seen data "./dancer.seen"
03:38:58 Quit krabador (Ping timeout: 260 seconds)
03:59:20 Join krabador [0] (~krabador@unaffiliated/krabador)
04:00
04:17:49 Quit amiconn (Read error: Connection reset by peer)
04:17:58 Join amiconn [0] (amiconn@rockbox/developer/amiconn)
04:31:24 Nick mrtux is now known as megabit (~mrtux@unaffiliated/mrtux)
04:32:26 Nick megabit is now known as mrtux[away] (~mrtux@unaffiliated/mrtux)
04:32:42 Nick mrtux[away] is now known as cows (~mrtux@unaffiliated/mrtux)
04:33:01 Nick cows is now known as megabit (~mrtux@unaffiliated/mrtux)
04:35:01 Nick megabit is now known as mrtux (~mrtux@unaffiliated/mrtux)
04:36:48 Quit DexterLB (Read error: Connection reset by peer)
04:41:56 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
04:46:44 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn)
04:46:44 Quit amiconn (Disconnected by services)
04:46:46 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma)
04:46:46 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn)
04:46:49 Quit pixelma (Disconnected by services)
05:00
05:11:00 Join tchan [0] (~tchan@lunar-linux/developer/tchan)
05:16:44 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf)
05:20:15 Quit krabador (Quit: Bah...)
05:29:09 Quit DexterLB (Read error: Connection reset by peer)
05:34:30 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
05:35:33 Quit TheSeven (Disconnected by services)
05:35:43 Join [7] [0] (~quassel@rockbox/developer/TheSeven)
05:38:41***Saving seen data "./dancer.seen"
05:38:54 Quit FOAD (Ping timeout: 264 seconds)
05:39:57[Saint]who controls the avatars on the forum?
05:40:21*[Saint] is a little concerned about the "Artist" badge looking far too official.
05:40:49[Saint]If there was a "Some Form Of Theme Guy" badge...now, that'd be a different story ;)
05:42:39[Saint]I'm somewhat concerned that it is too easily mistaken as a developer/moderator/comething_official badge.
05:42:44*[Saint] shrugs
05:44:25 Quit DexterLB (Read error: Connection reset by peer)
05:44:25 Quit TheSphinX_ (Read error: Connection reset by peer)
05:47:16 Join TheSphinX^ [0] (~briehl@pD9FBB1F4.dip0.t-ipconnect.de)
05:49:32 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
06:00
06:00:10 Quit DexterLB (Read error: Connection reset by peer)
06:01:58 Join dfkt [0] (dfkt@unaffiliated/dfkt)
06:02:59 Quit dfkt_ (Ping timeout: 252 seconds)
06:05:03 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
06:32:17 Quit DexterLB (Read error: Connection reset by peer)
06:32:25 Join FOAD [0] (~foad@83.161.135.61)
06:32:25 Quit FOAD (Changing host)
06:32:25 Join FOAD [0] (~foad@unaffiliated/foad)
06:36:24 Join ungali [0] (~ungali@unaffiliated/ungali)
06:36:53JdGordon_[Saint]: hasnt that discussion come up before?
06:37:00JdGordon_I think gevaerts was vocal in it
06:37:28[Saint]Its possible, yes. Not sure.
06:37:37 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
06:54:35[Saint]WHo do I need to talk to about commit access?
06:54:54[Saint]...and probably having my own branch for a while.
06:55:46[Saint]Modernising Cabbie Time is long past due. And I don't really want someone to have to review a bajillion individual commits.
06:56:37[Saint]So I was thinking it'd probably be easier if I got everthing sorted in its own branch, and then we merged that?
06:57:05[Saint]JdGordon_: what's the "best" way to handle such a thing?
07:00
07:04:23 Quit ungali (Quit: leaving)
07:07:42 Quit nosa-j (Ping timeout: 264 seconds)
07:10:24 Join nosa-j [0] (~m00k@184.76.254.130)
07:20:15 Quit nosa-j (Ping timeout: 252 seconds)
07:23:17 Join nosa-j [0] (~m00k@184.76.254.130)
07:37:12 Quit akaWolf (Quit: my exit)
07:38:42***Saving seen data "./dancer.seen"
07:44:45 Quit DexterLB (Read error: Connection reset by peer)
07:49:44 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
07:51:18JdGordon_[Saint]: check your pm... but generally i tihnk push your changes to gerrit (as complete, NOT WIP) with screenshots somewhere and dont allow bikeshedding on the patch (good luck)
07:51:44 Join kugel [0] (~kugel@rockbox/developer/kugel)
07:52:43 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf)
07:55:53 Join stoffel [0] (~quassel@pD9E40F3F.dip0.t-ipconnect.de)
08:00
08:04:01 Join mortalis [0] (~kvirc@213.33.220.118)
08:04:39 Quit DexterLB (Read error: Connection reset by peer)
08:09:45 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
08:34:27 Join ender` [0] (krneki@foo.eternallybored.org)
08:34:59 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de)
08:37:01[Saint]JdGordon_: that's not really how I'd like to do it. Hmmmm. With such a large set of changes I don't really want to do it in one fell swoop.
08:37:39JdGordon_I think you need to bring it up on the ml
08:38:10JdGordon_at least one "completed" patch per target?
08:39:20[Saint]I think I'll have to get it (the whole thing) sorted, and then post it to gerrit on a per-target basis.
08:39:36[Saint]Not ideal. But, it should be ok.
08:40:53JdGordon_what's the problem with one per target?
08:43:06 Join Derpina [0] (~Derp@bb116-15-155-214.singnet.com.sg)
08:44:18Derpinahi guys
08:44:27Derpinai need help unbricking my sansa clip+
08:45:45[Saint]...randomly PMing me isn't go to do any good I'm afraid.
08:46:30Derpinawhat do I do?
08:50:09[Saint](From PM) I would advise you against using a Windows dd implementation, even though it is technically possible, it is much easier for a nove to ensure they are writing to the correct area, of the correct disc, in a linux based OS.
08:50:36[Saint]Regarding where to get the OF file, see SanDisk.
08:50:59[Saint]I would ask, though, what it is that makes you believe the device is bricked?
08:53:51[Saint]nove? *ahem* ...novice.
08:53:53[Saint]Sorry.
08:57:30Derpinawhat makes me believe the device is bricked?
08:57:46Derpinathe exact descriptions as shown in the forum posts
08:57:53 Join thegeek [0] (~thegeek@40.200.16.62.customer.cdi.no)
08:58:08Derpinaif it aint bricked i dont know what happened
08:58:35 Join LinusN [0] (~linus@giant.haxx.se)
08:58:44Derpinawell if you could provide the exact command lines for using the windows dd implementation, I believe i would have no problem with it
08:58:56Derpinacant get my hands on a linux disc right now
08:59:29Derpinawhy havent someone published a guide on unbricking the sansa with windows yet??
09:00
09:00:32[Saint]Because its a royal pain in the ass. ANd many people jump to conclusions, assuming the device is bricked, and then actually brick it, or worse, end up wiping out the host operating system on their PC.
09:02:19[Saint]If I'm going to help you through this, I would prefer it be via a livecd, to limit potential damage.
09:02:42bluebrotherone problem on Windows is drivers.
09:02:57bluebrotheron Linux you can simply use libusb to talk to a USB device if no driver exists.
09:03:04*[Saint] nods
09:03:22bluebrotheron Windows you need a driver. And if the device in recovery mode / ... decides to use differen VID / PID number (which is common) then you need a different driver
09:03:37bluebrotherso you usualy don't want to do such things on Window
09:04:29bluebrother[Saint]: you can always create a repo on github or the like and push your changes there. Though last time I said that others told me to shut up since we want people to push to gerrit (i.e. adopting our workflow, not the github one)
09:05:04bluebrotherthough I don't see much difference between working on a branch and working on a branch that lives on a different (remote) repository
09:05:23[Saint]bluebrother: Indeed. And...no one actually looks at it. I have found this from experience.
09:05:50bluebrotherat gerrit?
09:06:03[Saint]No, no, if its on github et al.
09:06:11[Saint]...though, gerrit is piling up.
09:06:21Derpinawould any version of linux work for this?
09:06:35bluebrotheryes, unfortunately. Reminds me that there are a couple of patches I wanted to give a closer look ...
09:06:50[Saint]Derpina: yes.
09:07:01bluebrotherbut IMO it would be better to have it on some remote repository like github (or any other provider) than not having it public at all
09:07:10[Saint]antyhing that has libusb and dd, which should be, everything.
09:07:14bluebrotherbut I'll shut up now before others tell me to shut up :)
09:07:25bluebrotherOS X would work as well ;-)
09:08:50Derpinaalright, but where on sandisk should I look for the OF.lib?
09:09:02[Saint]...lib?
09:09:16[Saint]Its the firmware file for the device. Its nothing special.
09:09:43Derpina.bin i mean
09:10:00Derpinai got on http://www.sandisk.com/products/music-video-players/clip-plus-mp3-player/ and found their firmware updater in an EXE
09:10:18Derpinaprobably automated updating so I dont i can get the .bin from there can I?
09:10:59[Saint]http://forums.sandisk.com/t5/Sansa-Clip-Sansa-Clip/Sansa-Clip-Firmware-Update-01-02-18/td-p/280756
09:11:41Derpinayay! Firmware Download for All Regions - Click here to download ?
09:13:51Derpinaalright, one more thing before i get out to try and get my hands on a copy of linux
09:14:13Derpinaon the image from the AMSUnbrick page, http://www.rockbox.org/wiki/pub/Main/SansaAMSUnbrick/sandisksansaclipplusdis.jpg
09:14:34Derpinatheres 1 red circle with 2 pins in it, but the caption says "Recovery pins for Clip+, use the two RED pins: "
09:14:51[Saint]assuming your PC can boot from USB, it is trivial to create a bootable USB stick.
09:14:59Derpinait meant the 2 pins in the red circle doesn it?
09:15:06[Saint]Yes.
09:15:17[Saint]http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
09:17:50Derpinagreat, then i'll be out to get myself a new usb stick
09:18:07Derpinawhen will you be on IRC until?
09:18:38[Saint]Well, unless my server falls over I'll be on indefinitely.
09:18:53[Saint]I'll be awake for several hours yet.
09:19:03Derpinaok
09:19:03[Saint]Someone can help you, if not me, though.
09:19:15 Join liar [0] (~liar@clnet-p09-185.ikbnet.co.at)
09:19:23Derpinaim installing the prog from your link right now
09:19:29Derpinawhich flavor do I select?
09:20:42[Saint]Ubuntu 12/13.* Desktop, most likely
09:20:53DerpinaUbuntu 13. 10 Desktop i1386 sound good?
09:21:12[Saint]Assuming its a 32bit machine, yes.
09:21:25[Saint]Though, I guess for this it doesn't really matter.
09:25:37Derpinaim on a x64
09:25:45Derpinadosent matter does it
09:27:10Derpina on the same picture, http://www.rockbox.org/wiki/pub/Main/SansaAMSUnbrick/sandisksansaclipplusdis.jpg, whats those pins in blue for??
09:38:45***Saving seen data "./dancer.seen"
09:38:48Derpinaalright im out
09:38:50DerpinaTTYL!
09:39:44 Quit Derpina ()
09:59:20 Join gapan [0] (~gapan@79.103.225.183.dsl.dyn.forthnet.gr)
10:00
10:08:42 Join kevku [0] (~kevku@2a01:d0:ffff:34a::8:3)
10:21:56 Quit AlexP (Ping timeout: 248 seconds)
10:26:22 Quit mc2739 (Ping timeout: 240 seconds)
10:26:34 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739)
10:45:45 Join AlexP [0] (~alex@rockbox/staff/AlexP)
11:00
11:27:33 Quit Scall (Ping timeout: 276 seconds)
11:32:00 Join Scall [0] (~chat@unaffiliated/scall)
11:38:47***Saving seen data "./dancer.seen"
11:47:23 Join snepper [0] (snepper@178.165.22.105)
11:52:12snepper somebody can help with firmware player Sansa Clip+
11:53:06funmanwe can not if you don't tell your problem
12:00
12:06:39 Join petur [0] (~petur@rockbox/developer/petur)
12:07:46 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
12:08:09[Saint]He's been in for the past few days, asking the same question, getting the same answer.
12:08:53[Saint]I have lost count on how many times I have told him there isn't any point proceeding is s/he cannot expose the recovery partition.
12:13:06 Quit stoffel (Ping timeout: 264 seconds)
12:14:10funmanI think the SansaAMSUnbrick wiki might cause more harm than good
12:23:24pamauryhow did he brick his device ?
12:28:00[Saint]I never got an answer.
12:31:32pamauryfunman: can we dump the ROM on the AMSv2 ? recovery mode has be handled by this code, did you try to reverse engineer it ?
12:32:26funmanpamaury: we can (there should be an option in debug menu)
12:36:30pamauryok, i'll have a look
12:36:51pamauryI don't have my clip+ at hand though, is the ROM of the Zip the same ?
12:36:53snepperI did as written here http://www.rockbox.org/wiki/SansaAMSUnbrick
12:38:27snepperbut player on and writ "FAT is corrupted Please connected device to Pc"
12:40:48snepper<[Saint]> told me that "<[Saint]> If you cannoy expose a ~980MB partition, you don't need anything, because there is no point in continuing."
12:40:57 Quit fs-bluebot (Ping timeout: 245 seconds)
12:41:48 Quit bluebrother (Disconnected by services)
12:41:49 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother)
12:42:22 Join fs-bluebot [0] (~fs-bluebo@f053152138.adsl.alicedsl.de)
12:44:47snepper<[Saint]>and now throw the player?
12:45:28copperTHROW IT ON THE GROUUUND
12:45:28pamauryfunman: what are the known "recovery" modes of the AMS ? there is the one you reach when bridging two pins but there is another one we don't know about iirc ?
12:45:38 Join lebellium [0] (~chatzilla@lns-c10k-ld-02-m-212-194-176-149.dsl.sta.abo.bbox.fr)
12:45:51pamaurysnepper: if it is really dead, it's probably better to send it to a dev to look at it
12:46:36snepperplayer ON and writ "FAT is corrupted Please connected device to Pc"
12:46:48funmanpamaury: there is a boot process mentioned in the as3525 datasheet
12:47:02Torneif it actually powers on and displays an error message from the original firmware then it's not bricked
12:47:14Tornedoes it come up as a disk if you connect it to the PC?
12:47:58pamauryfunman: does it apply fully to the amsv2 ? or no idea ?
12:48:17funmanno idea
12:48:21snepperyes, but immediately turns off
12:48:46funmanif it boots the instructions on the wiki are 100% useless
12:48:57funmanthe only thing you can do is break it definitely
12:51:52snepperPlayer included with the firmware, but the rest of the memory is defined incorrectly, that need a memory dump player to sew him at 0 sector
12:53:04snepperPlayer starts with the firmware**
12:54:36funmandid you have rockbox installed?
12:54:43snepperI'm sorry I translate into English from another language can be a bit wrong
12:54:52snepperno
12:54:59funmanno problem with translating
12:55:13funmanwell in this case you should ask Sandisk for help or bring your player where you bought it
12:55:28funmanI think this has nothing to do with us
12:56:05funmanif you want to use the procedure described in our wiki just smash your player with a hammer, it will have the same effect, just faster
12:56:11snepperplayer was pulled from the size sockets for data transmission
12:57:10snepperok)
13:00
13:07:29 Join krabador [0] (~krabador@unaffiliated/krabador)
13:11:23[Saint]JdGordon_: how should I approach the lists? Ideally, I would like to use skinned lists for simplicity, but that ruins functionality, and adding the conditions required to restore the functionality lost makes it nightmarish. :-S
13:11:56[Saint]I mean things like icons/no icons, scroll bar left, scrollbar right, scrollbar off, etc.
13:15:18[Saint]Is it better to let the skin engine draw the lists, or go the whole nine yards and specifically cater for each possible alignment possibility in the lists (which isn't that many, really) and use skinned lists?
13:16:18 Quit pamaury (Read error: Operation timed out)
13:29:18 Join stoffel [0] (~quassel@pD9E40F3F.dip0.t-ipconnect.de)
13:35:16 Join pamaury [0] (~quassel@rockbox/developer/pamaury)
13:38:51***Saving seen data "./dancer.seen"
13:43:06JdGordon_[Saint]: give up on skinned lists I think :/
13:43:15JdGordon_I havnt done anything with them in too long
13:43:27JdGordon_I don't think the skin engine can do what we want :(
13:43:37 Quit snepper ()
13:47:28 Part LinusN
13:52:21 Quit DexterLB (Read error: Connection reset by peer)
13:57:19 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
14:00
14:11:08 Part DarthFrog ("Konversation terminated!")
14:35:01 Quit Raptors (Ping timeout: 252 seconds)
14:36:06 Join Raptors [0] (~whoneedsa@216-58-33-203.cpe.distributel.net)
14:52:58 Join melmothX [0] (~melmoth@unaffiliated/melmothx)
14:56:49lebelliumThe new build from today still makes the UI simulator crash when loading a theme. Could someone dig into it? rasher.dk/rockbox/simulator/sansaclipzip-sim-w32.zip">http://rasher.dk/rockbox/simulator/sansaclipzip-sim-w32.zip
15:00
15:24:30 Quit kevku (Ping timeout: 245 seconds)
15:32:28 Quit mortalis (Quit: KVIrc 4.3.1 Aria http://www.kvirc.net/)
15:37:07 Quit DexterLB (Read error: Connection reset by peer)
15:38:54***Saving seen data "./dancer.seen"
15:42:28 Join DexterLB [0] (~dex@79-100-25-119.btc-net.bg)
15:47:13 Join speckmade1 [0] (~stinky@port-92-201-105-150.dynamic.qsc.de)
15:50:20speckmade1So I just managed to produce those Opus files that instantly crashed my v3.13. One quick glance at commit messages revealed a bunch of Opus fixes - and some clicks later I was all happy and fixed with a recent dev version. :-O
15:50:28speckmade1Consider this just another "thank you" by an admiring and enchanted user. :-*
16:00
16:03:44 Quit tchan (Quit: WeeChat 0.4.1)
16:16:24 Join kevku [0] (~kevku@2001:470:27:773:0:feed:c0f:fee)
16:16:40 Join petur2 [0] (~petur@91.183.48.77)
16:18:40 Quit petur (Ping timeout: 264 seconds)
16:24:46 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma)
16:52:02 Join n1s [0] (~n1s@rockbox/developer/n1s)
17:00
17:07:36 Quit krabador (Quit: Bah...)
17:13:27 Join tchan [0] (~tchan@lunar-linux/developer/tchan)
17:17:13 Join kaitsu1 [0] (~bubba@a91-152-170-133.elisa-laajakaista.fi)
17:18:51 Quit [Saint] (Remote host closed the connection)
17:20:04 Join [Saint] [0] (~saint@rockbox/user/saint)
17:22:13 Quit kaitsu1 (Quit: ( www.nnscript.com :: NoNameScript 4.22 :: www.esnation.com ))
17:30:39copperlebellium: I updated my Fuze+ theme http://themes.rockbox.org/index.php?themeid=1862&target=sansafuzeplus
17:30:56copperif you can get around to it, I'd like to know if it makes any difference regarding USB transfers
17:31:02 Quit lebellium (Ping timeout: 260 seconds)
17:31:06copperlol
17:31:10coppermeh :-(
17:36:04 Join pilsa [0] (~malle@e179137082.adsl.alicedsl.de)
17:38:25pilsahi ... since my recent upgrade to rb 3.13 my sansa clip + is not mounted on ubuntu 12.04 anymore. the players battery can still be charged but file transfer is not possible. even worse, the rb utility 1.3.1 cant acces the player anymore. what can i do now?
17:38:57***Saving seen data "./dancer.seen"
17:39:08copperpilsa: type "dmesg" in a terminal after plugging in your Clip+ via USB
17:39:16pilsaok
17:39:18pilsaone moment
17:39:22copperlook at the last lines
17:39:28coppersee if it says anything about USB errors
17:40:27 Quit petur2 (Quit: Nettalk6 - www.ntalk.de)
17:40:57pilsayes, there is a whole bunch of usb messages, e.g.
17:41:02pilsa[ 3380.884091] usb 4-1: device descriptor read/64, error -71
17:41:11pilsalsusb does not see the device
17:41:38pilsa[ 3400.632222] hub 4-0:1.0: unable to enumerate USB device on port 1
17:41:47pilsaand so forth
17:42:14pilsa[ 3400.216130] usb 4-1: new full-speed USB device number 17 using uhci_hcd
17:42:50pilsa[ 3090.772142] usb 4-1: device not accepting address 9, error -71
17:44:37copperyup, classic USB errors
17:44:47copperI can only think of two things to try
17:45:01pilsaok
17:45:14copper1) unplug every single USB device, reboot, then plug in your Clip+; try with every port if it doesn't work
17:45:29pilsaok
17:45:48copper2) try with a different USB hub, either external, or an extra USB card if you're using a PC
17:46:08copperback when I used a PC, using a third-party USB card (PCI) did the trick
17:46:11funmanor different OS maybe (Windows)
17:46:53copperpilsa: I know next to nothing about USB, but sometimes, some USB devices can screw everything up
17:46:59pilsacopper, other usb ports dont work either ...
17:47:04pilsabut the ports are okj
17:47:14pilsai use them all the time with other devices
17:47:30pilsai have been using rovkbox for two years now
17:47:37pilsanever had this issue before
17:47:47copperI think there was also something about BIOS settings for giving USB its own IRQ (but that's chinese to me)
17:47:48funmanyou can try a current build
17:47:48pilsaonly after the upgrade to 3.13
17:48:00funmanUSB has always been flaky on those Sansa
17:48:14funmanyou just had luck with 3.12, that's all
17:48:16pilsafunman, i cant install a current build
17:48:25funmanboot the OF to make USB transfers
17:48:27pilsafunman, the device is not mounted
17:49:48pilsafunman, there is no way making file transfers ... the device is not mounted ... neither sansa frimware nor rb
17:50:00copperthen it's not Rockbox
17:50:01pilsathe trouble started with 3.13
17:50:06copperif the OF doesn't work either
17:50:20copperOF = Original Firmware (i.e. Sansa)
17:50:25pilsayes
17:50:29funmanyeah if the OF doesn't work your device is broken
17:50:42pilsathen 3.13 broke my device
17:53:22pilsai upgraded two weeks ago using the rb utility... only since then the trouble started
17:53:23copperpilsa: try another computer if you can
17:53:29copperat work, or at some friend's house
17:53:32pilsaok
18:00
18:07:10 Join saratoga [0] (123e1cf8@gateway/web/freenode/ip.18.62.28.248)
18:09:47 Join Strife89 [0] (~Strife89@2602:306:250e:8d79:225:d3ff:fed6:15a)
18:14:31pilsafirst the bad news:
18:14:54pilsathe player is not mounted also on a different machine
18:15:02pilsaeeepc, ubuntu 12.04
18:15:06pilsasecond:
18:15:10copperany chance it's Ubuntu's fault?
18:15:16pilsaeven worse
18:15:33pilsathe rb utility is making trouble on that box
18:15:37pilsacant start it
18:15:47pilsawhat happened?
18:16:00pilsai never ever had trouble with rb
18:16:05pilsaworked like a charm
18:16:29copperdid it work before with Ubuntu 12.04 specifically?
18:16:41pilsaplease check your builds before it kills other players
18:16:45pilsacopper, no
18:16:51pilsanot specific to 12.04
18:17:01pilsaworked also with previous versions
18:17:04copperthen how do you know it's not that particular Ubuntu release?
18:17:08copperlike a wonky kernel
18:17:29pilsabecause it definitely used to work with that release
18:17:29copperUSB problems = pretty much kernel problems
18:17:37copperok that was my question
18:17:39pilsahow could i make the upgrade
18:17:41pilsa then
18:17:50pilsacopper, kernel issue
18:17:53pilsamaybe
18:18:01pilsacould make sense
18:18:05copperdid you upgrade the kernel recently?
18:18:11coppervia an automatic upgrade or something
18:18:25copperI'm not trying to place blame, just trying to narrow it down
18:18:29pilsayes, kernels are continually upgraded in ubuntu
18:18:37pilsaevery two weeks or so
18:18:44pilsai dont exactly remember
18:18:52copperI've had kernel problems before, even with minor upgrades
18:18:53pilsabut that might be an explanation
18:18:56coppersometimes a bug slips in
18:19:14copperyou should get a live CD of some other distro (or some other Ubuntu version) and try with that
18:19:22pilsaok, i wait for the next kernel update and see what happens
18:19:25copperjust to make sure it's not a kernel problem
18:19:28copperno
18:19:30pilsaright
18:19:39pilsaboth machines are ubuntu 12.04
18:19:40copperthe next kernel update could have the same, undetected problem
18:19:44copperbetter try OLDER ones
18:19:45pilsaright
18:19:49pilsayep
18:20:10copperand like funman said, try with a Windows PC/Laptop
18:20:16coppersurely you know someone who has one?
18:20:45pilsaok, enough said ... unless i tried a completely different system we cant proceed
18:20:47gevaertsHave you tried a different *cable*?
18:20:49pilsathanks to all
18:20:58copperthe idea is to try everything you can think of and do yourself, and if everything fails, document your problem in a bug report
18:21:00pilsano
18:21:04pilsaalways the same cable
18:21:15pilsadidnt try different moon phases also
18:21:28gevaertsWell, cables to break
18:21:35*gevaerts has several bad ones to choose from
18:21:38pilsaalso didnt try even and odd dates
18:21:48copperpilsa: don't get mad
18:21:52gevaertsRight.
18:21:56*gevaerts stops helping
18:21:57pilsaok, sorry
18:22:05copperpilsa: it's just that it's very difficult to pin-point that kind of problem
18:22:05pilsagevaerts, i apologize
18:22:13pilsahonestly
18:22:17copperthe cause*
18:22:20pilsaok, thanks
18:22:39pilsai 'll do as we already said
18:22:56pilsagood bye, have a good day everybody
18:23:09copperpilsa: if that's actually a Rockbox problem that affects many people, it will be known
18:23:30pilsaok
18:23:36copperthe idea is that you report the problem with your configuration(s)
18:23:44copperthen other people will do the same with their own configurations
18:24:04pamaurylebellium: i've got a YP-R1 now !
18:24:05gevaertsBased on what I've read, I'm prepared to bet actual money on the cable or the connector
18:24:14copperthen, either a pattern will emerge, or none will, and that's a valuable piece of information on its own
18:24:32pilsagevaerts, but battery charging still works using that cable
18:24:49copperpilsa: the cable has separate pins for charging
18:24:51pilsai think, kernel is a good candidate
18:25:00pilsainteresting
18:25:03pilsaok
18:25:08pilsadifferent cable
18:25:09pilsagosh
18:25:26 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
18:26:25pilsabye
18:26:30 Quit pilsa (Quit: Leaving)
18:26:35copperbbl
18:27:26saratogawhy don't the simulators include the test plugins anymore?
18:28:24saratogameans i have to compile one from scratch if i want to test decoding a file
18:31:57 Quit shamus (Read error: Connection reset by peer)
18:32:17 Join shamus [0] (~shmaus@ip-206-192-195-49.marylandheights.ip.cablemo.net)
18:33:43funmanweird, perhaps they were gone in Makefile rework?
18:35:08funmansaratoga: http://pastie.org/8039676
18:35:27saratogalooks good, want to commit?
18:36:18funmanI fear it would break sims for some unstable targets
18:36:41funmanif some test plugins need target-specific code
18:37:44saratogathey shouldn't
18:37:46saratogaoh
18:37:50saratogahmm maybe
18:37:58saratogaas far as I know we used to include them however
18:38:16saratogawhat target specific code would a sim need?
18:38:29funmanhum
18:38:39funmanyeah for sim it doesn't make sense
18:39:16funmani'll try this patch before committing :)
18:39:44funmanwell it didn't work
18:40:30funman-DSIMULATOR is defined in 2 places
18:40:49 Quit scorche|sh (Ping timeout: 252 seconds)
18:42:23funmanwell it worked for fuze+
18:42:48fs-bluebotBuild Server message: 3New build round started. Revision b4ca244, 217 builds, 20 clients.
18:43:07 Join y4n [0] (~y4n@unaffiliated/y4ndexx)
18:43:16funmansaratoga: pushed correct version
18:44:29 Join TheLemonMan [0] (~LemonBoy@adsl-ull-37-253.45-151.net24.it)
18:44:29 Quit TheLemonMan (Changing host)
18:44:29 Join TheLemonMan [0] (~LemonBoy@unaffiliated/thelemonman)
18:49:48 Quit TheLemonMan (Quit: WeeChat 0.4.1)
18:49:48fs-bluebotBuild Server message: 3Build round completed after 420 seconds.
18:49:49fs-bluebotBuild Server message: 3Revision b4ca244 result: All green
18:53:00funmanlooks mid-yellow to me
18:56:08 Join bertrik [0] (~quassel@rockbox/developer/bertrik)
18:56:37fs-bluebotBuild Server message: 3New build round started. Revision ab56afe, 217 builds, 21 clients.
18:59:00 Join scorche|sh [0] (~scorche@squisch.net)
19:00
19:02:53 Quit stoffel (Ping timeout: 264 seconds)
19:03:30fs-bluebotBuild Server message: 3Build round completed after 413 seconds.
19:03:31fs-bluebotBuild Server message: 3Revision ab56afe result: All green
19:19:30 Nick _dv_ is now known as dv_ (~quassel@chello080108009040.14.11.vie.surfer.at)
19:25:13n1ssaratoga: afaik, you've had to enable them in config for sims at least for a couple of years
19:32:24 Join pretty_function [0] (~sigBART@123.252.215.112)
19:38:58***Saving seen data "./dancer.seen"
19:54:38 Quit pretty_function (Remote host closed the connection)
19:58:21 Quit penth (Read error: Connection reset by peer)
19:59:18 Join penth [0] (~reikoNeko@c-68-81-89-93.hsd1.nj.comcast.net)
20:00
20:02:18 Join pretty_function [0] (~sigBART@123.252.215.112)
20:08:01 Quit speckmade1 (Ping timeout: 245 seconds)
20:10:27 Join speckmade [0] (~stinky@port-92-201-105-150.dynamic.qsc.de)
20:16:01 Quit speckmade (Ping timeout: 240 seconds)
20:27:03 Quit n1s (Quit: Ex-Chat)
20:28:40 Join n1s [0] (~n1s@nl118-168-30.student.uu.se)
20:28:40 Quit n1s (Changing host)
20:28:40 Join n1s [0] (~n1s@rockbox/developer/n1s)
20:34:50 Quit pretty_function (Remote host closed the connection)
20:55:51 Quit penth (Read error: Connection reset by peer)
20:56:36 Join penth [0] (~reikoNeko@c-68-81-89-93.hsd1.nj.comcast.net)
21:00
21:01:00 Join krabador [0] (~krabador@unaffiliated/krabador)
21:15:17 Quit amboss (Quit: leaving)
21:20:26 Join amboss [0] (b@2a00:dcc0:eda:3754:247:aa54:204:1)
21:39:01***Saving seen data "./dancer.seen"
21:46:17 Quit gapan (Quit: Leaving.)
21:50:13 Quit akaWolf (Read error: Connection reset by peer)
21:50:24 Join akaWolf [0] (~akaWolf@unaffiliated/akawolf)
21:56:53 Quit akaWolf (Ping timeout: 264 seconds)
21:58:01 Join b1101 [0] (~b@64.237.37.121)
22:00
22:02:52 Quit mc2739 (Ping timeout: 240 seconds)
22:06:32 Quit y4n (Quit: MOTHER EUROPA CALLING ME!)
22:10:57 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739)
22:27:41 Quit n1s (Quit: Ex-Chat)
22:31:59 Quit Torne (Ping timeout: 248 seconds)
22:32:46 Join Torne [0] (~torne@rockbox/developer/Torne)
22:41:21 Quit liar (Ping timeout: 245 seconds)
22:43:16 Join makoto [0] (~makoto@hey.dont.privmsg.me.uk)
23:00
23:08:54 Quit kevku (Ping timeout: 260 seconds)
23:12:29 Quit melmothX (Quit: @.@)
23:23:30 Quit olspookishmagus (Quit: All for nothing)
23:28:05 Quit nosa-j (Ping timeout: 264 seconds)
23:30:10 Join nosa-j [0] (~m00k@184.76.254.130)
23:39:02***Saving seen data "./dancer.seen"
23:55:38 Quit Strife89 (Quit: Heading home.)

Previous day | Next day