--- Log for 26.01.114 Server: pratchett.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 3 days and 22 hours ago 00.00.31 # <[Saint]> it should, yes. 00.00.40 # I wouldn't expect a failed first database init to come back to haunt you after a reboot though 00.00.54 # <[Saint]> no, that is odd. 00.01.08 # It also doesn't explain why the OF is being equally difficult 00.02.22 # <[Saint]> No. It doesn't. I just wanted to point out that the Rb Database init wasn't ever going to complete. 00.02.33 # <[Saint]> I have no idea of the underlying issue. 00.05.09 # Hmmm 00.06.30 # Does the clip+ have a reset settings onboot button? 00.06.56 # Also, is it scanning for the database, or for dircache? 00.08.41 # Interesting 00.08.53 # ok, no reset settings button 00.09.25 # I was aware of the not having any media files problem, but only after I started having this problem, and I can't put any media files on to test it. I could insert my microSD card, but now that the player will not power on whatsoever that won't help much 00.11.09 # The question is, is it powered off, or is it powered on with the screen off? 00.11.57 # If the former, I'd say there's something fundamentally broken. If the latter, if holding power for a minute or so doesn't help, waiting for the battery to run down should 00.12.01 # <[Saint]> sensitive iems or an amp will tell. 00.12.16 # <[Saint]> (if its on) 00.13.18 # What does it do when you go through the sequence -power button for over one minute -hold center button while plugging into USB 00.13.33 # holding power button for over a minute should _ensure_ it is off 00.13.58 # plugging into USB then should do _something_, best bet is with center held 00.14.07 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 00.15.27 Quit pamaury (Ping timeout: 240 seconds) 00.15.43 # toehser1: I'm not sure how that's different from booting and then plugging in 00.16.33 # OF has a special thing about what happens when it plugs in with center button, and I think RB respects it, at least, it does different things for me. 00.17.33 # as far as rockbox is concerned, holding a button while detecting USB just makes it not do USB 00.17.45 # booting then plugging I get the usb screen icon and both drives (internal and sd) 00.18.03 # plugging while center from off, I get a black screen and only the internal drive, not the sd drive 00.18.11 # Well, "not do USB" is a bit inaccurate, but close enough in this case :) 00.18.41 # but the dmesg says rockbox so I don't think I'm getting OF version of it. 00.18.59 # But definitely DIFFERENT than booting and plugging. and definitely NOT "not do USB". 00.19.11 # Hmmm 00.19.41 # Sounds like bootloader behaviour then 00.19.44 # * gevaerts looks at code 00.20.07 # Ah, yes 00.20.28 # I said I'm not too familiar with the clips I think :) 00.20.40 # So yes, that's definitely worth a try 00.22.21 # That's *before* the bootloader tries to access the filesystem, so any filesystem corruption shouldn't be an issue here and be fixable from the host 00.24.24 # I was able to get into the Sansa USB, also - I held *BOTH* the "left" and "center" while plugging from off - and made it into Sansa USB without the refreshing-media crap. 00.27.05 # Looks like that is the same as just holding "left" while plugging USB from "off". 00.41.58 Join saratoga [0] (123e1eb1@gateway/web/freenode/ip.18.62.30.177) 00.42.26 # is there some reason theres no bootloader USB mode on the AMSv2 series? 00.42.35 # seems like an obvious way to avoid problems like that 00.42.46 # i thought we had it workign at one point 00.43.56 # Isn't what I just described with "hold the center button while plugging into USB with power off" a "bootloader USB mode"? 00.44.33 Join bertrik [0] (~bertrik@2001:610:76a:0:5eac:4cff:fe9e:66ce) 00.45.58 # ah it is 00.46.04 # looking at the bootloader source now 00.59.27 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 01.10.46 Quit Scall (Ping timeout: 252 seconds) 01.29.29 Quit ender` (Quit: [].map.call( "Batman", function( x, y, z ) { return !y && z || +x }).reverse().join( " " );) 01.31.18 Quit cmhobbs (Ping timeout: 265 seconds) 01.34.19 Join Scall [0] (~chat@unaffiliated/scall) 01.38.31 Quit ikeboy (Quit: ikeboy) 01.50.28 *** Saving seen data "./dancer.seen" 01.59.53 Quit Scall (Read error: Operation timed out) 02.02.19 Join Scall [0] (~chat@unaffiliated/scall) 02.04.04 Quit saratoga (Quit: Page closed) 02.22.44 Quit Scall (Ping timeout: 248 seconds) 02.29.20 Join Scall [0] (~chat@unaffiliated/scall) 02.47.16 Quit onder` (Ping timeout: 248 seconds) 02.48.21 Join onder` [0] (~onder@dyn-dsl-to-76-75-118-5.nexicom.net) 02.53.26 Quit bertrik (Ping timeout: 245 seconds) 03.10.14 Join cmhobbs [0] (~cmhobbs@fsf/member/cmhobbs) 03.21.06 Join bertrik [0] (~quassel@ip117-49-211-87.adsl2.static.versatel.nl) 03.21.06 Quit bertrik (Changing host) 03.21.06 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 03.48.26 Quit bertrik (Ping timeout: 245 seconds) 03.50.32 *** Saving seen data "./dancer.seen" 04.34.03 Quit amiconn (Disconnected by services) 04.34.04 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.34.05 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 04.34.05 Quit pixelma (Disconnected by services) 04.34.07 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 04.34.08 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 05.42.42 Quit michaelni (Excess Flood) 05.43.06 Join michaelni [0] (~michael@chello084114129144.4.15.vie.surfer.at) 05.43.17 Quit [7] (Disconnected by services) 05.43.30 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 05.48.20 Join mikroflops_ [0] (~yogurt@s208h98o2esc1.dyn.tyfon.se) 05.49.03 Quit mikroflops (Write error: Broken pipe) 05.50.34 *** Saving seen data "./dancer.seen" 06.23.14 Quit mt (Ping timeout: 265 seconds) 06.44.58 Quit Scall (Ping timeout: 240 seconds) 06.55.22 Join Scall [0] (~chat@unaffiliated/scall) 07.09.40 Join Jinxor [0] (~Jinx@108.222.213.232) 07.10.55 Join n1s [0] (~n1s@nl118-168-30.student.uu.se) 07.10.55 Quit n1s (Changing host) 07.10.55 Join n1s [0] (~n1s@rockbox/developer/n1s) 07.20.56 Quit Scall (Ping timeout: 252 seconds) 07.32.22 Join Scall [0] (~chat@unaffiliated/scall) 07.48.04 Quit wanew (Ping timeout: 272 seconds) 07.50.37 *** Saving seen data "./dancer.seen" 08.01.01 Quit Strife89 (Ping timeout: 272 seconds) 08.03.21 Quit Scall (Read error: Operation timed out) 09.17.53 # I notice that not all SVN branches got converted to git😔 09.44.07 Join lebellium [0] (~chatzilla@80.215.129.43) 09.50.39 *** Saving seen data "./dancer.seen" 10.01.26 Join Scall [0] (~chat@unaffiliated/scall) 10.25.54 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 10.33.35 Quit Scall (Ping timeout: 260 seconds) 10.59.25 Join Scall [0] (~chat@unaffiliated/scall) 11.00.56 Join kiwicam [0] (~quassel@121.99.184.8) 11.01.10 Join ender` [0] (krneki@foo.eternallybored.org) 11.06.07 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.09.39 Join rela [0] (~x@pdpc/supporter/active/rela) 11.27.04 Quit lebellium (Ping timeout: 245 seconds) 11.27.40 Quit rela (Read error: Connection reset by peer) 11.30.25 Join lebellium [0] (~chatzilla@80.215.129.43) 11.39.59 Quit lebellium (Ping timeout: 245 seconds) 11.41.38 Quit Scall (Ping timeout: 252 seconds) 11.45.58 Join lebellium [0] (~chatzilla@80.215.129.43) 11.50.40 *** Saving seen data "./dancer.seen" 11.57.55 Join Scall [0] (~chat@unaffiliated/scall) 11.59.20 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 12.08.09 Quit sakax (Remote host closed the connection) 12.09.24 Quit Scall (Ping timeout: 248 seconds) 12.15.07 Quit lebellium (Ping timeout: 245 seconds) 12.22.24 Join lebellium [0] (~chatzilla@80.215.129.43) 12.23.39 Quit pamaury (Quit: No Ping reply in 180 seconds.) 12.23.48 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 12.31.59 Join bertrik [0] (~quassel@rockbox/developer/bertrik) 12.38.54 # hmm. So my forum signature has some messed up characters in it, but when I try to change it I run into the size limit of 255 characters with the [url]s in it. Any chance to work around this? 12.40.12 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 13.04.55 Join Scall [0] (~chat@unaffiliated/scall) 13.14.17 Quit Scall (Ping timeout: 245 seconds) 13.28.04 Quit pixelma (Disconnected by services) 13.28.05 Quit amiconn (Disconnected by services) 13.28.05 Join pixelma_ [0] (pixelma@rockbox/staff/pixelma) 13.28.06 Join amiconn_ [0] (amiconn@rockbox/developer/amiconn) 13.28.07 Nick pixelma_ is now known as pixelma (pixelma@rockbox/staff/pixelma) 13.28.11 Nick amiconn_ is now known as amiconn (amiconn@rockbox/developer/amiconn) 13.30.41 Quit SuperBrainAK (Quit: you broke it :P) 13.35.52 Join Szczepancio [0] (~Patryk@acfn161.neoplus.adsl.tpnet.pl) 13.35.59 # pamaury: ping 13.38.26 Join Scall [0] (~chat@unaffiliated/scall) 13.42.40 Join ikeboy [0] (~ikeboy@ool-435622d3.dyn.optonline.net) 13.48.14 Quit ikeboy (Quit: ikeboy) 13.50.41 *** Saving seen data "./dancer.seen" 14.01.49 Join Rower [0] (husvagn@90-230-142-55-no41.tbcn.telia.com) 14.04.21 Join kugel [0] (~kugel@rockbox/developer/kugel) 14.04.26 # PurlingNayuki: ping 14.06.15 # kugel: pong 14.06.33 # PurlingNayuki: you mentioned USB problems. can you try the latest build again? 14.06.51 # i fixed a possible memory corruption 14.07.43 # sure will try, but not now 14.08.11 # Tomorrow later? 14.09.07 # And USB works sometimes actually -- at least for today morning when I tried to copy some musics 14.26.01 Quit pamaury (Ping timeout: 264 seconds) 15.02.25 Join mt [0] (~quassel@cpe-24-165-191-253.neo.res.rr.com) 15.15.49 Quit lebellium (Ping timeout: 264 seconds) 15.18.19 Join lebellium [0] (~chatzilla@80.215.195.23) 15.32.58 Join dfkt [0] (OxO29A@unaffiliated/dfkt) 15.33.02 Quit lebellium (Ping timeout: 245 seconds) 15.33.36 Join lebellium [0] (~chatzilla@80.215.195.23) 15.35.05 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 15.48.15 Quit Szczepancio (Read error: Connection reset by peer) 15.49.35 Join _stripwax_ [0] (~Miranda@176.26.82.40) 15.49.47 Quit lebellium (Read error: Connection reset by peer) 15.50.42 *** Saving seen data "./dancer.seen" 15.51.35 Quit stripwax (Ping timeout: 272 seconds) 15.58.21 Join lebellium [0] (~chatzilla@80.215.195.23) 16.02.21 Quit Scall (Ping timeout: 272 seconds) 16.08.23 # PurlingNayuki: thanks again for your lcd sizes list 16.08.34 # PurlingNayuki: I integrated that and updated the list separator branch 16.13.38 # kugel: Uh.. Where's the list? 16.14.05 # g#729 16.14.08 # 3Gerrit review #729 at http://gerrit.rockbox.org/r/729 : 3 by Thomas Martitz (changes/29/729/1) 16.15.18 # Sorry I didn't notice the new commit.. 16.15.41 # What do you think about G#727? 16.15.42 # 3Gerrit review #727 at http://gerrit.rockbox.org/r/727 : 3 by Purling Nayuki (changes/27/727/1) 16.15.58 Join Scall [0] (~chat@unaffiliated/scall) 16.25.40 # looks goo 16.25.42 # d 16.26.58 Quit fs-bluebot (Quit: So long, and thanks for all the fish.) 16.27.37 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.27.39 Quit fs-bluebot (Remote host closed the connection) 16.27.53 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.27.55 Quit fs-bluebot (Client Quit) 16.28.12 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.28.55 Quit fs-bluebot (Remote host closed the connection) 16.29.08 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.29.26 # wtf ... why doesn't the bot terminate when I'm trying to shut it down? 16.29.42 Quit fs-bluebot (Remote host closed the connection) 16.31.14 Quit Rower (Ping timeout: 245 seconds) 16.32.30 Join ZincAlloy [0] (~Adium@pD9EEA735.dip0.t-ipconnect.de) 16.33.32 # bluebrother^: did you see FS#12947 ? 16.34.21 # yes 16.34.30 # it's not really much of a problem though 16.34.49 # and somewhat non-trivial with the current approach 16.35.17 # since "installing" the manual can be done separately, and in that case there's (currently) no way to figure the "correct" one 16.36.08 # plus, given that the manual isn't updated that often (and release manuals thus aren't too accurate anyway) I'm seeing this as a minor problem :) 16.36.59 # there is a "won't fix" close reason for that situation 16.37.34 # although I think it would be nice if it could be fixed, perhaps by looking at what version is selected in the other tab 16.38.26 # or by creating a similar drop down menu in the manual tab 16.39.31 # there are ways to address this so it's not something that qualifies for "won't fix" imo 16.39.52 # could be "later" though :) 16.40.10 # anyways, I'm going to look into this. No idea when / how long it will take though 16.40.26 # right but if you aren't going to work on this because it's too minor is pretty much a "won't fix" (you still acknowledge it's a bug, otherwise it would be "Not a bug") 16.40.40 # okay 16.41.33 # perhaps the release / current / rc selection could be promoted so it applies for all tabs 16.42.07 Join wanew [0] (~wanew@c-76-97-208-168.hsd1.ga.comcast.net) 16.42.26 # that's one option 16.42.38 # another one would be to merge the manual tab with the Installation one 16.43.09 Quit _stripwax_ (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 16.43.10 # which kinda would make sense. 16.43.33 # and maybe make the Manual tab display the HTML manual directly. Though that would need some work for proxy handling 16.43.44 # unless Qt supports this now. It didn't some years back 16.44.16 # good idea 16.44.51 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.45.09 # bluebrother: I just crashed 16.45.18 # oh, nice 16.46.56 Quit fs-bluebot (Client Quit) 16.47.41 Join |akaWolf| [0] (~akaWolf@188.134.9.161) 16.53.07 Join _akaWolf_ [0] (~akaWolf@188.134.9.161) 16.54.20 Join dotbot [0] (~dotbot@g224236252.adsl.alicedsl.de) 16.54.42 Quit dotbot (Remote host closed the connection) 16.55.24 Quit |akaWolf| (Ping timeout: 245 seconds) 16.57.16 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.58.24 # bluebrother: I just crashed 16.58.24 Quit fs-bluebot (Remote host closed the connection) 16.59.52 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 16.59.58 # bluebrother: I just crashed 17.06.41 Join ildarion [0] (4ef2d722@gateway/web/freenode/ip.78.242.215.34) 17.07.17 # Hi there ! 17.08.17 # where? 17.08.33 # I was able to update my Sansa Fuze + on Bootloader V2 (OF dosen't trigger before) but now, when I plug it on Windows, the device seem to be not detected 17.08.45 # It's normal or .... ? 17.09.07 Join Rower [0] (husvagn@90-230-142-55-no41.tbcn.telia.com) 17.16.46 Quit fs-bluebot (Quit: So long, and thanks for all the fish.) 17.17.06 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 17.18.10 Quit wanew (Ping timeout: 260 seconds) 17.18.22 Join wanew [0] (~wanew@c-76-97-208-168.hsd1.ga.comcast.net) 17.22.58 Quit wanew (Ping timeout: 265 seconds) 17.29.14 Join rela [0] (~x@pdpc/supporter/active/rela) 17.31.11 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 17.32.02 Join wanew [0] (~wanew@c-76-97-208-168.hsd1.ga.comcast.net) 17.32.32 Quit rela (Read error: Connection reset by peer) 17.32.57 # bluebrother^: I've now increased the signature limit to 300. Shout if that's still not enough 17.40.18 Quit ildarion (Quit: Page closed) 17.42.06 Join rela [0] (~x@pdpc/supporter/active/rela) 17.43.58 Quit wanew (Ping timeout: 240 seconds) 17.50.45 *** Saving seen data "./dancer.seen" 17.51.39 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 17.52.57 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 18.00.58 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.03.38 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 18.07.15 Quit lebellium (Ping timeout: 252 seconds) 18.10.37 Join sakax [0] (~sakax@unaffiliated/sakax) 18.15.06 # amiconn: ping 18.16.35 Join lebellium [0] (~chatzilla@80.215.195.23) 18.17.48 Quit Jinxor (Quit: reboot) 18.38.11 Join ildarion [0] (4ef2d722@gateway/web/freenode/ip.78.242.215.34) 18.41.38 # Hey, i Just upadate my Sansa Fuze + with the bootloader V2 and now, windows don't detect the device, it's normal ? 18.47.07 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.49.15 # When my sansa is OFF, I plug, and he stay with a black screen. If I do the same with volum down, same 18.49.29 # I have no idea what to do 18.51.33 # With rockbox ON and plug : USB Keypad Mode, the device is detected by windows by "unknow" 18.57.51 Quit TheSeven (Disconnected by services) 18.57.58 # If i unplug when sansa was ON, seem to be block (need to force shutdown) 18.58.05 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 18.59.31 # format using the OF can resolve this ? 19.01.56 Quit Karrde (Remote host closed the connection) 19.03.30 Quit Scall (Read error: Operation timed out) 19.11.08 # weird.... Work on my other PC on XP, but on my win 7 no... But my other device, work on Win7, only sansa 19.16.53 # Yeah ! I succed ! 19.17.12 # I tunr on my sansa and during the loading screen, plug it 19.24.20 # just get this error when i plugged : http://titanpad.com/3D0XHuPWhn 19.25.03 Join Scall [0] (~chat@unaffiliated/scall) 19.31.24 # ildarion: yeah, USB is buggy on some Sansas 19.32.44 # hm 19.33.03 # git HEAD seems to panic on boot on the hwcodec/Player 19.33.27 # the indicated erroneous instruction is a simple pc-relative bt 19.33.52 Quit Jack87 (Ping timeout: 245 seconds) 19.36.49 Quit mc2739 (Ping timeout: 264 seconds) 19.36.59 # it's a good idea if i format ? 19.37.12 # or it will be worse ? 19.38.37 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 19.39.02 Join Jack87 [0] (Jack87@nasadmin/admin/jack87) 19.39.13 Quit FOAD (Ping timeout: 264 seconds) 19.40.14 Join FOAD [0] (~foad@unaffiliated/foad) 19.41.00 Join Strife89 [0] (~Strife89@adsl-98-80-214-77.mcn.bellsouth.net) 19.42.21 # after formating, issue sitll here 19.42.35 # So this is a bootloader issue ? 19.44.51 # I guess I will wait paumary 19.46.10 Quit FOAD (Ping timeout: 272 seconds) 19.46.42 Join FOAD [0] (~foad@unaffiliated/foad) 19.50.49 *** Saving seen data "./dancer.seen" 19.56.46 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 19.57.58 # ildarion: ping 19.59.08 # funman: afaik USB is not particularly buggy on the Fuze+, contrary to the AMS based ones 20.03.39 # hey pamaury, i just posted a post on the forum 20.04.00 # http://forums.rockbox.org/index.php/topic,26284.msg226410.html#msg226410 20.05.34 Quit y4n (Disconnected by services) 20.05.40 Join y4n [0] (~y4n@unaffiliated/y4ndexx) 20.06.35 # I saw, it is strange because the V2 bootloader is supposed to be quite stable wrt to USB. If I understand correctly nothing happen when you plug your device ? 20.07.15 # before i format yes, or the device what no reconized 20.07.38 Quit _akaWolf_ (Ping timeout: 252 seconds) 20.07.46 # so you formatted and is it better ? 20.07.48 # I was able to connect him on win XP and copy my rockbox backup 20.08.03 # now, it' the same 20.08.15 # I doubt formatting would have any impact because the bootloader is not loaded from the file system 20.08.18 # I can only connect on OF MSC 20.08.33 # the device still unknow 20.08.52 # device is unknown under RB bootloader but not under OF ? 20.09.34 # No now, because i was format, i just have the OF (rockbox file was formated) 20.11.09 # oh you mean you reinstalled the OF without RB bootloader ? 20.11.22 # If i plug when my sansa is OFFi get really nothing 20.11.49 # the screen stay black and i need to reset with holding power 20.11.53 # pamaury: does it use the same controller? 20.11.57 # no 20.12.12 # then it's normal that it doesn't share the same sets of bugs ;) 20.12.28 # it doesn't sound like a USB bug, if the screen stays black 20.13.01 # I was refering to the data abort 20.13.26 # oh I didn't see that ildarion has a Fuze + ... sorry about this 20.13.36 Quit FOAD (Ping timeout: 252 seconds) 20.14.14 # I'm not sur i was reinstall OF without RB 20.14.23 # I was install RB 20.14.30 Part ZincAlloy 20.14.32 # and after format under the OF 20.15.01 Join FOAD [0] (~foad@83.161.135.61) 20.15.03 # So now, I have the bootloader v2 (i guess) but not the rockbox file (formated) 20.15.31 # I maybe shouldn't format 20.15.53 # I was format using the option in OF 20.15.55 # ok so rockbox bootloader is still there 20.16.00 # yes 20.16.11 # the issue is : can't plug into windows 20.16.25 # so can't install using rockbox utility 20.16.32 # even in OF ? 20.16.39 Quit kugel (Ping timeout: 245 seconds) 20.16.43 # in OF, just nothing happend 20.16.50 # scree stay black 20.16.50 # <[Saint]> Worth trying a less picky OS? 20.17.11 # hum, something very wrong must have happened, maybe bad storage 20.17.45 # before the update it was cool under the old bootloader :D 20.18.13 # but the alarm wasn't working^^ 20.18.22 # <[Saint]> It may be simply very poor timing for a HW failure. 20.18.46 # indeed, it is probably best to recover 20.18.50 # <[Saint]> I'm not sure how Rockbox could cause this directly. 20.19.00 # who has access to the theme site? 20.19.42 # it is missing the ipod6g 20.19.42 # ildarion: I'll be back in 30 min and explain you how to recover 20.21.05 # pamaury: ok, i'am not hurried. if i't long process maybe other day if you want 20.25.20 # bluebrother^: it's not *missing* the ipod6g as such. It's just that we haven't really agreed that it should be there, given its "unusable" status 20.26.23 # I think we should add it, but do we have a consensus? 20.26.47 # stupid question, I know. this is *rockbox* :) 20.26.49 # I agree we should add it. 20.26.59 # so we two have a consensus I'd say :) 20.27.26 # If we do it quickly enough, we can probably avoid people objecting in time :) 20.27.35 # yes! 20.28.36 # plus, we don't loose much anyway. 20.29.03 Quit FOAD (Ping timeout: 265 seconds) 20.29.08 # we have the Ondas there as well and they are unusable according to the front page 20.29.32 # so not having the ipod6g there because of its status doesn't make much sense in my book :) 20.29.56 # There! 20.30.34 # \o/ 20.30.44 # thanks 20.30.49 # user890104: ^^ 20.31.05 # gevaerts: btw, Rockbox Utility uses the ipodvideo image 20.31.09 # Of course now someone has to put a picture in the right place 20.31.44 # <[Saint]> chrisjj becomes relevant 20.31.53 # I'm re-running checkwps on all themes. With any luck, that will give the thing some actual themes 20.32.08 # <[Saint]> and filter out some thatfailed since. 20.32.13 # it currently shows 17 themes 20.32.26 # gevaerts: it is referred as "ipodclassic" not "ipod6g" in rbutil IIRC 20.32.34 # user890104: wrong 20.32.44 # http://themes.rockbox.org/rbutilqt.php?target=ipod6g&release=&revision=&rbutilver=1.4.0 20.32.45 # <[Saint]> it _should_ be ipod6g 20.32.52 # that definitely states "ipod6g" 20.32.53 # <[Saint]> everywhere 20.33.33 # * user890104 checks again 20.33.51 # it _was_ ipodclassic some time in the past 20.34.03 # but when cleaning up all the device names that was changed as well. IIRC. 20.34.09 # at least these days it's ipod6g 20.34.38 Join FOAD [0] (~foad@unaffiliated/foad) 20.34.42 # ah, here: 20.34.48 # fs-bluebot: .describe e3cddc2e 20.34.49 # bluebrother: I just crashed 20.34.59 # oh, nice. Yet another thing that broke :( 20.35.10 # well, that's the commit that changed it from ipodclassic to ipod6g 20.35.14 Quit FOAD (Client Quit) 20.35.32 # user890104: you have a classic, I presume. Can you provide a nice svg we can use to generate all needed images? ;) 20.35.36 Join FOAD [0] (~foad@83.161.135.61) 20.37.58 Quit sakax (Ping timeout: 241 seconds) 20.39.13 # bluebrother^: yes, the target name is indeed fixed 20.39.20 # uh 20.39.33 # why are my theme not listed on the iPod Classic theme page? 20.39.36 # themes* 20.40.10 # gevaerts: how do i create the svg? i have a classic, but no design skills :) 20.40.11 # mines and lots others 20.40.14 # copper: for now, I'm going with "because you're too impatient" 20.40.23 # ok ok :P 20.40.31 # It's not *instant* 20.40.51 # <[Saint]> maybe some ISP "helpful" caching, too. 20.43.27 # All I can say is that the checkwps run is still going 20.44.15 # http://upload.wikimedia.org/wikipedia/commons/c/cf/6G_iPod.svg 20.44.45 # <[Saint]> cheat! 20.45.04 # http://simple.wikipedia.org/wiki/File:6G_iPod.svg 20.45.06 # <[Saint]> You...you...cheaterer...you. 20.45.15 # what 20.45.17 Quit fs-bluebot (Quit: So long, and thanks for all the fish.) 20.45.23 # CC license 20.45.29 # it's perfect 20.45.35 Join fs-bluebot [0] (~fs-bluebo@g224236252.adsl.alicedsl.de) 20.46.01 # fs-bluebot: .describe e3cddc2e 20.46.02 # bluebrother: I just crashed 20.46.06 # hmm. Still? 20.47.08 # * gevaerts grumbles 20.47.20 Quit lebellium (Ping timeout: 252 seconds) 20.47.59 # "You must attribute the work in the manner specified by the author or licensor" is fair enough, but then I expect the author to specify this! 20.51.06 # comparing the wikipedia image with our images it looks somewhat out of place 20.51.19 # kinda too shiny :) 20.51.21 Join sakax [0] (~sakax@d8d862c77.access.telenet.be) 20.51.21 Quit sakax (Changing host) 20.51.21 Join sakax [0] (~sakax@unaffiliated/sakax) 20.51.52 # I'm sure inkscape has an "add scratches" feature :) 20.52.18 # well, swapping grey and white areas on the ipodvideo svn should do most of the work 20.53.18 # Actually, yes, that may be a better option. That way, it will also keep our button names and things like that 20.55.01 # http://www.alice-dsl.net/dominik.riebeling/rockbox/ipod6g-front.svg 20.55.15 # that's the ipodvideo image with colors for scrollwheel and case swapped 20.55.50 # hmm, whait 20.55.53 # something went wrong 20.56.53 # ah no, my bad. Was looking at the wrong file 20.58.28 # * gevaerts has something similar 20.58.45 # Except I also swapped the select button colour :) 20.59.54 # I just did that as well 21.00.03 # after noticing the button names to be almost unreadable ;-) 21.00.08 Quit y4n (Quit: AMIGAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHAHAHAHAAAAAAAAAAAAHAHAAA) 21.00.30 # it might be a good idea to make those even a bit darker 21.02.33 # updated 21.03.14 # I'm not entirely sure about the while line near the edge 21.03.54 Quit FOAD (Changing host) 21.03.54 Join FOAD [0] (~foad@unaffiliated/foad) 21.05.46 # updated once more 21.05.52 # white line is now grey 21.06.14 # I'm *also* not entirely sure why this checkwps run is so slow 21.07.09 # That looks quite good I think 21.07.24 # and select fixed 21.08.02 # looks quite ok imo and without that rounded effect (which I guess wouldn't look too good when scaled down) 21.09.40 # <[Saint]> inscape can do texturing, yes. 21.09.56 # <[Saint]> And I'm fairly sure I have a convincing "burnished" texture somewhere. 21.10.09 # <[Saint]> *inkscape, too. 21.10.53 # well, scale it to something like 47x80 for Rockbox Utility ... 21.11.10 # nothing texture anymore. At least not visible :) 21.11.35 Join lebellium [0] (~chatzilla@80.215.195.23) 21.11.39 # and given that we don't have any 3d like effects on the other pictures I'd prefer to not add that for the ipod6g 21.14.51 # scorche: ping 21.15.30 # ildarion: still here ? 21.20.13 # scorche: never mind, I can't figure out what I actually want to ask :) 21.20.13 # gevaerts: pong 21.20.18 # ah :) 21.21.06 # scorche: right. Any chance you could run a chown themes:www-data on themes.db-wal and themes.db-shm in the themesite's private directory? 21.21.51 # Right now I can't access the database, so I can't check what the thing is doing 21.22.39 # done 21.23.06 # Thanks! 21.24.34 # gevaerts: am i good to head to brunch? =) 21.24.40 # Go ahead! 21.25.52 # pamaury i'm bussy this night, it's possible an other day ? 21.26.29 # ildarion: sure, maybe tomorrow ? 21.26.55 # when you are less bussy :D 21.27.28 # it's not hurrie for me 21.28.30 # gevaerts: the list of iPod Classic themes hasn't moved in the last 50 minutes 21.28.35 # I know 21.28.49 # ildarion: tomorrow I should be available all evening 21.29.11 # ok ok, i will try to remember 21.29.25 # thanx for your assistance 21.32.29 Quit n1s (Quit: Ex-Chat) 21.40.13 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 21.44.03 Join wodz [0] (~wodz@89-75-151-160.dynamic.chello.pl) 21.44.22 # pamaury: Do you have images of yp-cp3 internals? 21.45.55 # wodz: no, good to remind me ^^ Let me find my tools to open it 21.45.56 Join kugel [0] (~kugel@91-64-116-250-dynip.superkabel.de) 21.45.56 Quit kugel (Changing host) 21.45.56 Join kugel [0] (~kugel@rockbox/developer/kugel) 21.47.24 # pamaury: I noted my findings on the wiki http://www.rockbox.org/wiki/SamsungYPCP3 21.47.55 # I saw that, great :) 21.48.39 # I am now digging in gpio code which is huge mess. I am still not sure how buttons are handled actually 21.48.45 Join [0xAF] [0] (~af@unaffiliated/angelfire) 21.49.23 # <[0xAF]> hello 21.49.32 Quit Provel (Read error: Connection reset by peer) 21.50.10 # <[0xAF]> i'm trying to compile RB for iPod Classic (target #29), but there are missing includes, like "lang.h" and "rockboxlogo.h" 21.50.18 # <[0xAF]> any ideas ? 21.50.53 *** Saving seen data "./dancer.seen" 21.50.56 Quit kugel (Ping timeout: 245 seconds) 21.51.31 # [0xAF]: are you building in a clean directory? 21.51.34 # those are generated 21.51.42 # run make clean, then try again 21.51.59 # Check what's there after that make clean 21.52.26 # <[0xAF]> yup, in ./rockbox/build/ 21.52.56 # <[0xAF]> only these files: autoconf.h Makefile 21.53.17 # ok, those are allowed 21.53.22 # (and expected) 21.53.39 # <[0xAF]> and my wrapper script called "arm" to add PATH and LD_LIBRARY_PATH for the toolchain 21.54.23 # How are you using that? 21.54.50 # I mean, are you sourcing it, or just running it and expecting the environment to be changed after it exits? 21.55.05 # build just fine here 21.55.31 # <[0xAF]> i'm hacking canon cameras and have few toolchains laying around, so i'm using arm-elf-eabi toolchain 21.55.35 # <[0xAF]> the "arm" script contents: 21.55.39 # <[0xAF]> #!/bin/bash 21.55.40 # <[0xAF]> export CROSS_COMPILE=arm-elf- 21.55.40 # <[0xAF]> export LD_LIBRARY_PATH=/home/af/arm/arm-elf-toolchain/lib 21.55.40 DBUG Enqueued KICK [0xAF] 21.55.40 # <[0xAF]> export PATH=$PATH:/home/af/arm/arm-elf-toolchain/bin 21.55.40 # <[0xAF]> $* 21.55.59 # <[0xAF]> calling it like this: "./arm make" 21.56.00 # And you run ./arm make, presumably? 21.56.07 # OK, that should work I'd expect 21.56.18 # <[0xAF]> works for canon dslr hacks 21.56.32 # <[0xAF]> and i see no reason for it to make troubles... 21.56.35 # Hmm, wait 21.56.54 # I don't know about that CROSS_COMPILE one 21.57.16 # <[0xAF]> copyed from canon hacks ... im using it there in the Makefile (to prefix the toolchain) 21.57.23 # <[0xAF]> it's not needed for RB actually 21.57.36 # Well, configure uses CROSS_COMPILE for some stuff 21.57.58 # <[0xAF]> couldn't hurt IMO, since most other scripts use CROSS_COMPILE to prefix the toolchain 21.58.00 # <[0xAF]> i can remove it 21.58.24 # <[0xAF]> hah 21.58.38 # <[0xAF]> quite strange ... it seems it was breaking the compilation 21.58.41 # <[0xAF]> stupid me ... 21.58.50 # <[0xAF]> i should check where it's used in RB 21.59.03 Join Provel [0] (~Provel@97-88-171-31.dhcp.stls.mo.charter.com) 21.59.22 # <[0xAF]> thanks for the hint :) 21.59.28 # No problem :) 21.59.40 # copper: all themes should be there now 22.01.48 # <[0xAF]> unfortunately i should recompile the arm-eabi toolchain ... this one would not link the RB binary 22.02.28 # Well, we do provide scripts to build one :) 22.02.39 # <[0xAF]> yeah... just looking at them ;) 22.02.52 # <[0xAF]> or it will be faster to get the VirtualMachine i guess... 22.03.19 # building single crosscompiler is pretty fast 22.03.41 # <[0xAF]> will give it a try 22.14.19 # wodz: I didn't manage to open the YP-C3 so far 22.14.54 # pamaury: thats unfortunate 22.15.07 # I wonder if it's not glued 22.16.15 # I'll keep trying, stay tuned 22.17.06 # pamaury: I see only two gpios probed for state so maybe buttons are handled by adc 22.18.14 # wodz: http://www.anythingbutipod.com/forum/showthread.php?t=64069 22.19.14 # oh wow, never heard of the YP M1 22.19.26 # you should 22.19.36 # is it good ? 22.19.43 # it's the only player along with the Zune HD to have a Tegra chip 22.19.54 # lebellium: Where did it come from? rk2706B is supposed to run at 200MHz max 22.20.14 # pamaury: read my review, as usual :P http://labo.generationmp3.com/2010/03/11/test-et-videos-du-samsung-yp-m1/ 22.21.05 # heh not speaking that the core is arm7-ejs not arm7-ejc :P The same error as in rockchip datasheet 22.21.10 # wodz: from my contact at Samsung 22.22.26 # gevaerts: great, thanks! 22.24.39 # if this is really rk2706b I'd love to see actual cpuid signature and maybe rom dump 22.25.19 # that may be wrong, you know, there are often mistakes in Samsung internal documentation :P 22.25.57 # the type in core name is granted :-) 22.26.45 # but the audio DAC should be correct 22.26.46 # anyway SDK never sets pll higher then 200MHz so this doesn't matter really 22.27.26 # lebellium: judging from disasm it is either wm8750 or wm898x so this seems to match 22.32.19 # I am still amazed by the volume of the dead code in rk firmware 22.37.57 # gevaerts bluebrother^: looks like all of the ipod6g themes are listed now (125 in total), i am trying to install all of them on my classic using rbutil, just to test if everything is fine 22.38.25 # uhm, it failed on the theme with id 995 22.40.08 Join bluebrother [0] (~dom@rockbox/developer/bluebrother) 22.42.52 Quit fs-bluebot (Ping timeout: 252 seconds) 22.43.25 Quit bluebrother^ (Ping timeout: 264 seconds) 22.46.03 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 22.46.03 # * [Saint] suddenly clicks that if checkwps let them through in the first place that it is unlikely to catch any other cases without a bit more poking 22.46.19 # <[Saint]> ...I have no idea why I thought that would "Just Work". 22.46.42 # <[Saint]> It needs a bit of a helping hand wrt allowable syntax apparently. 22.47.37 Quit Strife89 (Ping timeout: 264 seconds) 22.48.33 # <[0xAF]> the ipod looses it's usb connection... and i can hear the hard disk ticking once ... sounds like it's off and then turned on, but at this time the usb connection resets ... and the ipod hangs at it's main menu (removing the usb screen)... needs restarting 22.51.16 # <[Saint]> Windows host? 22.53.07 # <[0xAF]> linux 22.53.22 # <[Saint]> Very odd. 22.53.30 # <[Saint]> Can you try the fallback image please? 22.53.37 # <[0xAF]> it started tonight ... i had no problems in the previous few days (since i have the ipod) 22.53.44 # <[Saint]> emCORE main menu - Tools - Run rockbox fallback 22.53.46 # <[0xAF]> fallback seems to work correctly 22.53.54 # <[Saint]> Very odd. 22.54.16 # <[Saint]> I mean, that is expected, but you seem to be the one guy with a linux host that sees issue here. 22.54.27 # <[0xAF]> hmm 22.54.37 # <[Saint]> Generally speaking, linux has been very permissive of the CLassic's USB issues. 22.54.51 # <[Saint]> I haven't ever managed to catch it reliably. 22.55.09 # <[Saint]> I don't think anyone actually has been able to when trying to debug this. 22.55.12 # <[0xAF]> if i leave the ipod this way (frozen), it turns the backlight off after the timeout ... then the keys will turn it back on, but i cant move over the menus ... so it's not totally dead 22.55.14 Quit bertrik (Remote host closed the connection) 22.55.20 # <[Saint]> ...Windows machines, however, well...yeah. 22.55.36 # <[Saint]> We managed to do *something* to piss them off royally over the past two years or so. 22.55.46 # <[0xAF]> my latop has only usb3 ports ...if that matters 22.55.51 # <[Saint]> No idea what. But, they really seem to hate the Classic USB in git head. 22.56.02 # <[Saint]> Yeah, that probably does matter. 22.56.02 # <[0xAF]> hm 22.56.14 # <[Saint]> Even though it technically shouldn;t matter at all, it definitely seems to. 22.56.30 # <[Saint]> emCORE installation falls over hard with USB3 for some reason. 22.56.38 # <[Saint]> NFI why. 22.56.49 # <[0xAF]> yeah, i had problems with samsung android devices ... their download mode is not quite working with usb3 ports 22.56.57 # * [Saint] nods 22.57.01 # <[Saint]> I have that issue as well. 22.57.06 Join einhirn [0] (~Miranda@p4FC749D7.dip0.t-ipconnect.de) 22.57.35 Quit sakax (Remote host closed the connection) 22.57.46 # <[0xAF]> i've installed emCORE, but the DFU (the 64mb partition) i had to wait about 10 mins to be able to mount it ... 22.57.49 # <[Saint]> As far as I understand it, it should be absolutely 100% backwards compatible (weird early version USB3 ports/cables aside). 22.58.00 # <[Saint]> That issue is know. 22.58.16 # <[Saint]> *known. 22.58.21 # <[0xAF]> the strange thing is that i had no problems in the past few days ... never 22.58.55 # <[Saint]> There's been nothing obvious committed in the past few days that I would expect to cause this. 22.59.00 # <[0xAF]> now it's damn crashing after few seconds 22.59.08 # wodz: I'm almost done with opening it, it's a real pain 22.59.21 # <[Saint]> It might be worth checking the disk itself. 22.59.41 # <[Saint]> These things are absolutely notorious for their terrible disk firmware, and shitting their own disks. 23.00.11 # <[Saint]> smashing the heads against the platter is a fun thing they like to do to amuse themselves. 23.00.41 # <[0xAF]> [Saint]: i was thinking to replace the RB with my compilation ... the previous one was from 22.Jan (when i installed it for the first time)... the issue started with the 22th build ... it crashed when i was copying the RB binary... then i had to go to the failback image to put my newly compiled RB 23.00.53 # <[0xAF]> but it's failing with mine build too 23.01.25 # <[Saint]> I think it might be worth checking the filesystem and disk condition. 23.01.31 # <[0xAF]> did that 23.01.36 # <[0xAF]> there were fixes 23.01.36 # <[Saint]> Hmmm. 23.01.51 # <[0xAF]> havent checked the disk condition 23.01.56 # <[Saint]> But with the FS repaired, its still being a dick? 23.02.04 # <[0xAF]> yup 23.02.05 # <[Saint]> Hum. 23.02.16 # <[0xAF]> could it be a HDD problem ? 23.02.41 # <[0xAF]> just bought the ipod (second hand) few days ago ... so it's quite possible to be with broken disk... 23.02.58 # <[Saint]> It very well could be, yes. But there's a problem in determining this reliably/easily. 23.03.20 # <[Saint]> Since we wipe out the Original Firmware completely, wer can't check in diagnostic mode trivially. 23.03.25 # <[Saint]> *we can't 23.03.50 # <[0xAF]> can't i just 'dd' it to /dev/null and see if it reads ? 23.03.53 # <[Saint]> ...but, I have noticed that their diagnostic mode isn't guaranteed to give useful information to begin with, so, mah. I guess. 23.04.18 # pamaury: Is it glued? 23.04.34 # <[Saint]> You could, I believe, yes. 23.04.40 # <[Saint]> It'll take a damn while, though. 23.05.18 # it's bizarre, it is glued but the design is mostly mechanical 23.05.41 # <[0xAF]> i wonder why the FB image is working 23.05.41 # I have it opened but there is still some plastic over the PCB, I need to find out how to remove it 23.05.49 # <[Saint]> I honestly can't think of a single other case where a Classic user has seen reproducible USB issues with a linux host. 23.05.57 # <[Saint]> There's always a first, I suppose. 23.06.11 # <[Saint]> If you had a Windows host, I wouldn;t be surprised in the slightest. 23.06.29 # <[Saint]> ...but this is slightly interesting. 23.06.39 # <[Saint]> I just wish I could offer up some usable information. 23.06.40 # <[0xAF]> [Saint]: then, the way to reproduce could be a broken disk ;) 23.06.51 # <[Saint]> Hahahaha. :) 23.07.05 # <[Saint]> I have had one of these crash and burn on me myself. 23.07.39 # <[Saint]> One day, fine, next day it booted and didn;t want to do anything except slam the heads into the platter, hard, in a rhythmic fashion. 23.08.02 # <[0xAF]> i can hear similar sound ... but rarely ... 23.08.11 # <[0xAF]> i though it's just the spinning of the disk (when it's off) 23.08.35 # <[Saint]> Right. We don;t seem to handle spindown correctly with CE_ATA. 23.08.49 # <[Saint]> It just kinda...abruptly kills power. 23.08.59 # <[0xAF]> yeah ... sounds just like that 23.09.01 # <[Saint]> Rather than nicely spinning down and halting. 23.09.39 # <[0xAF]> btw, if this keeps reproducing and it's not a broken disk... perhaps i could be of help somehow... providing some information ? 23.09.51 # <[Saint]> "ka-chunk!....Peeeewwww......" 23.09.57 # <[Saint]> That was a familiar sound to me. 23.10.08 # <[0xAF]> :) 23.10.12 # <[Saint]> Especially if you have fastboot enabled. 23.10.33 # <[Saint]> emCORE doesn't get nearly enough time to spin down the disk at boot beofre it hands off to Rockbox. 23.10.43 # <[0xAF]> one more thing i just mentioned .... when this was breaking... i was working only in the .rockbox folder ... once my disk is checked, i will try to dig into the music ... 23.10.53 # <[Saint]> So the drive just powers down, and then ROckbox takes over. And in between that it makes a godawful noise. 23.11.38 # <[Saint]> Just one of the dozen or so reasons its still classed as "unusable". :) 23.12.11 # <[0xAF]> btw, just thinking noisly ... could it be something related to the directory caches or similar ? or the RB using it's files while im digging there (shouldn't be a problem though) 23.12.31 # <[0xAF]> because in the past few days i had no problems with it, but i was working with my "music" folder only 23.12.43 # <[Saint]> Rockbox won;t be accessing the disk at all when connected via USB. 23.12.52 # <[0xAF]> mhm 23.13.04 # <[Saint]> s/connected/connected and mounted/ 23.13.27 # <[0xAF]> it changes the screen to USB mode once i connect it... even if it's not mounted 23.14.14 # <[Saint]> Right. The Nano2G does this too, the magic to detect a charger vs. a host is fairly complicated I believe. 23.14.18 # <[0xAF]> btw... is there a way to make the ipod detect the charger correctly ... it switches to usb mode once i put a charger .... it's not cool for using it in car... 23.14.19 Quit Scall (Read error: Operation timed out) 23.14.31 # <[Saint]> It thinks any power source is an opportunity to enumerate it seems. 23.14.51 # <[0xAF]> hmz 23.14.52 # <[Saint]> Just hold any button while plugging USB to subvert this behavior. 23.14.55 # damned, samsung really didn't want anyone to open this device 23.15.04 # <[Saint]> That says "I don;t want you to mount now" 23.15.16 # <[0xAF]> [Saint]: cool trick, thanks 23.15.34 # pamaury: removing the screw is not enough? 23.15.45 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 23.15.58 # <[Saint]> Some DAP manufacturers *really* like glue. 23.16.01 # <[Saint]> Like, a lot. 23.16.03 # pamaury: maybe they were ashamed of using rockchip SoC :P 23.16.10 # <[Saint]> Hahahaha 23.16.22 Quit rela (Read error: Connection reset by peer) 23.16.23 # for Samsung it really depends on the device. The YP-Q2 is full of glue, the YP-R0 no 23.16.42 # <[0xAF]> [Saint]: it would be better if there is confirmation screen from RB, when the usb is plugged ... (at least for the devices where the charger/usb cannot be decided) 23.16.58 # <[Saint]> Isn't the battery glued to the LCD in one or both of those, lebellium 23.17.04 # wodz: it's a WM8988L 23.17.08 # lebellium: not quite 23.17.28 # <[Saint]> [0xAF]: how do you mean? 23.17.32 # the Samsung YP-CP3 was designed for the Russian and Chinese market. I harassed the Samsung France Product Manager to get in France too but since it was designed for "developing countries", Samsung thought shitty hardware would be enough for them :) 23.18.18 # <[0xAF]> [Saint]: when i plug the ipod to charger or computer, RB can ask if i want to mount it, or just charge it (or give 5 seconds timeout to press a key for mount mode)... this way the default will be charging mode 23.18.22 # lebellium: Still I don't get why Samsung is not using its own SoCs 23.18.36 # I still haven't got access to the back of the PCB 23.19.14 # at least in reference design the back of the PCB is not that interesting 23.19.25 # <[Saint]> [0xAF]: while I don't necessarily disagree, I think for most users that would be an annoyance. 23.19.31 # in this case there is the flash and the SoC 23.19.40 # <[Saint]> FOr most users, when they plug via USB, they will want the device to mount. 23.19.41 # on the front on the dac 23.20.14 # wodz: some Samsung players use a Samsung SoC such as YP-U3 but most of them don't indeed :) 23.20.16 # and some other small chip labelled 0219 CK60 925 23.20.18 # <[0xAF]> [Saint]: this can be done for devices which do not make difference between charger/computer i guess ... and IMO in most of the cases you will want to charge it, instead of mount it 23.20.41 # <[0xAF]> [Saint]: besides, it could be an optional :) 23.20.58 # <[Saint]> [0xAF]: this is why we already have a system in place for selectively disabling enumeration. 23.20.58 # I have *not* idea how to remove to plastic cover, it seems impossible 23.21.13 # <[Saint]> For your case, you could trivially reverse the logic used. 23.21.33 # <[Saint]> You could just make it so you held the button to mount, instead of holding it to not mount. 23.21.38 # pamaury: seek and buy the Service Manual, there is always a dissasembly guide inside :P 23.21.43 # <[Saint]> very trivial change. 23.21.53 # <[0xAF]> [Saint]: good point ;) 23.22.05 # <[0xAF]> [Saint]: should look into the code ... any pointers where to look for it ? 23.22.26 # <[Saint]> probably somewhere in usb.c 23.22.37 # <[0xAF]> [Saint]: thanks 23.22.56 # <[0xAF]> [Saint]: btw so far the disk is ok ... 23.23.11 # <[Saint]> copper: no issues your end? 23.23.12 # <[0xAF]> can i provide any debug information to help you with the usb issue ? 23.23.57 # <[Saint]> dmesg after pluging might be mildly interesting. 23.24.16 # <[Saint]> When Rockbox does crash, what exactly happens? 23.24.47 # pamaury: yeah, you need access to SoC or nand to force rkdfu rom mode. And this mode is the simplest and safest to experiment with the hardware :/ 23.24.52 # <[Saint]> Is there a panic message, or a segfault, or does it just hang? 23.25.46 # <[0xAF]> [Saint]: looks like bad hdd after all ... 23.25.48 # <[0xAF]> [84490.007416] FAT-fs (sdd): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. 23.25.51 # <[0xAF]> [84568.173615] usb 1-1: USB disconnect, device number 27 23.25.54 # <[0xAF]> [84568.230024] sd 27:0:0:0: [sdd] Unhandled error code 23.25.56 # <[0xAF]> [84568.230029] sd 27:0:0:0: [sdd] 23.25.59 # <[0xAF]> [84568.230031] Result: hostbyte=0x01 driverbyte=0x00 23.26.01 # <[0xAF]> [84568.230033] sd 27:0:0:0: [sdd] CDB: 23.26.04 # <[0xAF]> [84568.230034] cdb[0]=0x2a: 2a 00 00 06 90 fc 00 00 01 00 23.26.05 Quit stripwax (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 23.26.06 # <[0xAF]> [84568.230040] end_request: I/O error, dev sdd, sector 3442656 23.26.09 # <[0xAF]> [84568.230043] Buffer I/O error on device sdd, logical block 430332 23.26.11 # <[0xAF]> [84568.230044] lost page write due to I/O error on sdd 23.26.14 # <[0xAF]> [84568.230163] FAT-fs (sdd): unable to read inode block for updating (i_pos 2639288) 23.26.15 # <[Saint]> someone's gunna get kicked... 23.26.17 # <[0xAF]> but it's because the usb is disconnected i guess 23.26.34 # <[0xAF]> sorry (will use pastebin in future) 23.26.42 # <[Saint]> You are so lucky chanserv didn't kick you for flooding. :) 23.27.01 # <[Saint]> Also, hmmm. 23.27.03 # <[0xAF]> just got the right amount of lines ;) 23.27.50 # hum, I think I see how to unmount it, it's incredibly weird 23.27.57 # not sure it can be done easily 23.28.04 # <[Saint]> If there is no data on the device that you care about, I would say just to use emCORE to format the data partition. 23.28.28 Join Scall [0] (~chat@unaffiliated/scall) 23.29.04 # <[0xAF]> [Saint]: what good is that for ? I mean emCORE formated it few days ago ... and so far it was unmounted correctly ... so there should be no problems with the FS (until today) 23.30.00 # <[0xAF]> actually, what's the internal structure of the HDD ? more than one partition ? 23.31.09 # <[Saint]> superfloppy 23.31.38 # <[0xAF]> so no partitions ? 23.31.51 # <[0xAF]> just like how i see it in linux ? 23.32.05 # <[Saint]> No. But it will accept partitioning. 23.32.31 # <[Saint]> The default setup is just a superfloppy afaik, though. 23.32.43 # <[0xAF]> is there a point to have partitions there ? 23.33.04 # dammmmmmmn, this thing is insane 23.33.18 # <[Saint]> Depends on your use case. 23.33.34 # actually the proper way is probably to unsolder the LCD but I won't do that 23.34.34 # what purpose this plastic part services (other then protect you from reaching the PCB)? 23.35.01 # afaik, none 23.35.08 # cut it then 23.35.42 # well actually it holds everything in place 23.35.57 # it's stupid design but the way it is designed it looked needed 23.36.16 # and it's hard to cut without removing it but you're right it could be cut at the right spots 23.36.29 # still it's hard plastic 23.36.35 # not easy to cut with the PCB below 23.36.51 # maybe melt it with solder tip 23.38.15 # <[Saint]> [0xAF]: for the usb charging logic, /rockbox/firmware/usb.c line 132, btw. 23.39.17 # <[0xAF]> [Saint]: yeah, already found it, thanks ;) 23.39.52 Join stripwax [0] (~Miranda@rockbox/developer/stripwax) 23.41.10 Quit lebellium (Quit: ChatZilla 0.9.90.1 [Firefox 27.0/20140123185438]) 23.41.39 Quit wodz (Quit: Leaving) 23.42.55 # <[0xAF]> [Saint]: one more change which could be the problem ... i've rebooted my laptop today... and the new kernel booted (was 3.12.6, now it is 3.12.7) ... though it's very unlikely, there could be some change in the usb stack 23.45.15 # <[0xAF]> nothing interesting in 3.12.7 changelog 23.47.38 Join kugel [0] (~kugel@91-64-116-250-dynip.superkabel.de) 23.47.38 Quit kugel (Changing host) 23.47.38 Join kugel [0] (~kugel@rockbox/developer/kugel) 23.49.56 # yay, I ebay'd an ypr1 23.50.57 # <[Saint]> buying or selling? 23.50.58 *** Saving seen data "./dancer.seen" 23.51.03 # <[Saint]> I assume the former. 23.52.56 # right 23.53.07 # why should I sell daps :) 23.53.13 # <[0xAF]> [Saint]: is there a way to save some usb debug info on the hdd ? (i presume you already tried that) 23.54.18 # <[Saint]> I'm mostly unsure of the USB subsystem. 23.54.58 # <[Saint]> I _think_ we have some form of log-to-disk feature...maybe? 23.56.13 # <[Saint]> Right. http://gerrit.rockbox.org/r/#/c/288/ 23.56.35 # <[Saint]> That was pulled in a while ago. 23.57.14 Quit ildarion (Quit: Page closed) 23.57.27 # <[0xAF]> looks interesting ... will try ... 23.58.03 # <[Saint]> rebuild with #define ROCKBOX_HAS_LOGDISKF in /rockbox/firmware/export/config/ipod6g.h