--- Log for 10.08.117 Server: karatkievich.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 2 months and 11 days ago 00.03.08 Quit scorche (Read error: Connection reset by peer) 00.03.33 Join advcomp2019_ [0] (~advcomp20@65.131.153.224) 00.03.33 Quit advcomp2019_ (Changing host) 00.03.33 Join advcomp2019_ [0] (~advcomp20@unaffiliated/advcomp2019) 00.04.13 Quit advcomp2019_ (Read error: Connection reset by peer) 00.04.40 Join advcomp2019_ [0] (~advcomp20@65.131.153.224) 00.04.40 Quit advcomp2019_ (Changing host) 00.04.40 Join advcomp2019_ [0] (~advcomp20@unaffiliated/advcomp2019) 00.05.21 Join scorche [0] (~scorche@rockbox/administrator/scorche) 00.05.43 Join advcomp2019__ [0] (~advcomp20@unaffiliated/advcomp2019) 00.06.26 Quit advcomp2019 (Ping timeout: 240 seconds) 00.08.56 Quit advcomp2019_ (Ping timeout: 240 seconds) 00.16.30 Join Soap [0] (~Soap@rockbox/staff/soap) 00.25.28 *** Saving seen data "./dancer.seen" 00.45.27 Quit iceCalt (Remote host closed the connection) 00.47.32 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 54.0.1/20170628075643]) 01.02.40 Join __builtin [0] (~franklin@cpe-71-71-34-79.triad.res.rr.com) 01.02.40 Quit __builtin (Changing host) 01.02.40 Join __builtin [0] (~franklin@rockbox/developer/builtin) 01.05.06 Quit ender` (Quit: When you try to teach them to fish, they become upset, because you are very clearly communicating to them that you will not be handing them a fish every day.) 02.04.26 Quit MrZeus1 (Ping timeout: 240 seconds) 02.08.31 Join Strife89 [0] (~quassel@adsl-98-80-193-66.mcn.bellsouth.net) 02.12.15 Quit Strife1989 (Ping timeout: 248 seconds) 02.16.41 Join walle303 [0] (walle303ke@pisg/dev/walle303) 02.25.30 *** Saving seen data "./dancer.seen" 02.31.04 # I compiled the bootloader for the Cowon D2 and it's giving me a `Incorect CPU mode in mutex_lock (0x12!=0x1F)` panic. Anyone know how to fix it? 02.35.46 # <__builtin> walle303: on boot? 02.35.56 # Yeah, Instantly on boot 02.36.05 # <__builtin> I'll take a look 02.36.23 # If it matters, It's a D2 using the D2+ firmware 3.10 02.37.08 # It boots into stock fine when hold is set though. 02.37.22 # "stock" being the D2+ firmware 02.37.42 # <__builtin> I'm not an expert on the D2 though 02.39.37 # <__builtin> anything else on the screen, maybe an address? 02.41.20 # Yes, sp=21F00558, pc=21F0A124 02.41.44 # <__builtin> which bootloader and rockbox version are you using? 02.43.40 # It crashes before it searches for the rockbox version on the sdcard/memory so that doesn't seem to matter, but the bootloader is 3e1c8cca / the latest from the github mirror 02.44.26 # <__builtin> ok 02.46.26 # <__builtin> are you comfortable with making some changes to the source and testing? 02.46.35 # absolutely 02.47.24 # I'm not too versed in C and ARM ASM though, so keep that in mind. 02.48.21 # <__builtin> I'm basically going to look for all the mutex_(un)lock calls which are D2-specific 02.48.30 # <__builtin> which hopefully shouldn't be that many 02.49.28 Join uwe__ [0] (~uwe_@ipservice-092-219-220-180.092.219.pools.vodafone-ip.de) 02.50.14 # <__builtin> hmm, I'm not sure if splash() works in bootloader 02.50.35 # It crashes before the splash screen, so that's a possibility 02.51.40 # <__builtin> I have a suspicion it's one of the mutex_(un)lock calls in sd-tcc780x.c 02.52.04 Quit uwe_ (Ping timeout: 240 seconds) 02.52.30 # <__builtin> but I want to be sure before blindly removing every one of those 02.53.41 # <__builtin> does the backlight work? 02.53.46 # Yes 02.54.09 # I can give you more of the pointers listed on the screen if you want 02.54.21 # probably should've done that to begin with actually 02.55.06 # * __builtin is stupid 02.55.28 # <__builtin> yeah, I could use those 02.56.09 # <__builtin> (I'm used to stack traces not working) 02.56.26 # 21F0EB1C / 21F0DC78 / 21F09610 / 21F09400 / 21F04CB0 / 21F04DC0 / 21F0DE80 / 21F082EC then it repeats 21F10FC4 over and over again 02.56.43 # Oh, stack traces don't work sometimes? that kind of sucks 02.57.05 # <__builtin> on ipod6g for some reason I haven't bothered to debug 02.58.52 # I had an ipod6g for a while, lent it to someone, should probably see if i can get it back now lmao 02.58.52 # <__builtin> ah, I think I found it 03.00.36 # watch, there will probably be another crash after this one is fixed 03.00.50 # <__builtin> that's possible 03.01.16 # <__builtin> for now though, comment out all the mutex_* calls in firmware/target/arm/i2c-telechips.c 03.01.38 # <__builtin> so line 43, 155, 166, 175, and 196 03.01.46 # all? it's all of them? 03.01.55 # <__builtin> well just in that file 03.02.29 # for C, you use /* and */ for comments right? 03.02.53 # yeah, duh, there's others in the file 03.02.56 # <__builtin> yeah, you can do that 03.03.14 # <__builtin> also // for single-line comments is acceptable for testing purposes 03.03.54 # building and flashing, hold on 03.05.41 # <__builtin> chances are you'll run into another crash or two before it works 03.05.56 # yeah probably 03.06.16 # ok, the splash screen works now, let me put the sdcard in and see if it boots 03.07.24 # well uh, it's doing what it did before i upgraded the bootloader, which is to say, it just goes to a black screen and does nothing 03.07.39 # darn, i was hoping upgrading the bootloader would fix that 03.07.55 # <__builtin> so it won't boot? 03.08.07 # It gets past the bootloader and then sits on a black screen 03.08.25 # <__builtin> can you read anything on the screen before that point? 03.08.31 # so we're into something to do with rockbox now, same 3e1c8cc version 03.09.11 # great, i think something flashes for a frame then poofs 03.09.31 # hmm, can't tell 03.09.56 # <__builtin> it's probably the bootloader giving its progress 03.10.06 # let me see if it's turning the backlight off 03.10.54 # yeah, nothing, solid black screen 03.11.48 # it's on though because I have to hit the reset button on the side before i can get it to come back 03.11.55 # <__builtin> let's try and see for sure whether if it's the bootloader or rockbox itself 03.12.33 # The older bootloader from the installation instructions does it too 03.13.05 # <__builtin> that probably means it's rockbox itself 03.13.22 # If it can't find rockbox it just says the version, that it mounted the storage, and that it can't find it 03.13.49 Join pirik3 [0] (5225d944@gateway/web/freenode/ip.82.37.217.68) 03.15.21 # I have an idea, let me copy the TTS stuff to it and see if it's working without the screen 03.17.51 Quit Aldem (Read error: Connection reset by peer) 03.18.15 Quit pirik3 (Client Quit) 03.18.19 Join Aldem [0] (~Aldem@unaffiliated/aldem) 03.20.05 # <__builtin> what's the last rockbox version that successfully booted? 03.20.06 # yeah, i think it's crashing before it re-initializes the screen or something 03.20.33 # um, the last time i used rockbox on this thing was 2-4 years ago, so i'm not sure 03.20.59 # let me see if last month's build is still broken 03.22.16 # <__builtin> it'd be a better idea to try release 3.13 (not 3.14) 03.22.55 # I don't think there's release builds for this device on the website, i guess i could build it myself though 03.23.07 # <__builtin> oh duh, it's unstable 03.24.29 # <__builtin> pick a commit in the timeframe that you remember it working and test 03.24.42 # <__builtin> and then give me its sha1 03.26.35 # <__builtin> or even better, try and bisect it yourself 03.27.28 # <__builtin> you'll probably end up testing about 10 or so different versions at most 03.38.33 # The nightly build system should probably be reworked to exclude days where no changes occured 03.39.33 # <__builtin> it should, I think 03.39.54 # <__builtin> I don't think it's "nightly", either 03.40.17 # * walle303 uploaded an image: Attachment (145KB) 03.40.23 # <__builtin> yeah, it's on every source change 03.40.36 # well the website shows lots of duplicate builds 03.40.44 # <__builtin> hmm, where? 03.41.08 # https://www.rockbox.org/dl.cgi?bin=cowond2 or that screenshot i sent [did the matrix irc bridge handle that properly?] 03.41.09 # <__builtin> ah, never mind 03.42.11 # <__builtin> I want to believe that the swedes have a clever solution to avoid doing that 03.43.13 # <__builtin> based on the timestamps on http://download.rockbox.org/daily/cowond2/, it seems that the zips are just copied over from the on-demand build system at a fixed time each day 03.44.34 # Yeah, looks like it, should probably check to make sure the build has changed though before adding it, the build history on the website would go back a bit further if it did 03.45.14 # <__builtin> the change that introduced the issue is probably much older than the build history available there 03.45.16 # anyway, 84e13d5 is broken too, so i guess i'll have to build older ones myself 03.45.26 # <__builtin> (like, *years older*) 03.45.31 # i think the D2 thread in the forum mentions it working late 2016 03.46.33 # <__builtin> are you ok with bisecting? 03.46.50 # not entirely sure how to do that 03.47.18 # is that just hopping back and forth between commits and splitting the difference in half every time 03.47.27 # <__builtin> yes, exactly 03.47.32 # if so then yeah i've done that before, usually i pick a commit by hand though, i think there might be a command that does it 03.47.44 # <__builtin> yes, git (our version control system) does it for you 03.47.59 # yeah i'm fairly familiar with git 03.48.12 # <__builtin> but you still need to supply it with a known-good and known-bad commit 03.49.31 # When did 3.13 come out? 03.50.20 # <__builtin> 2013, but since the D2 is unstable it doesn't matter too much 03.51.33 # i think 3.13 might've been out at the time i tested it last so i'll start around there 03.51.53 # eh, i'll start early 2015 since the forum thread seems to imply it works then 03.52.21 # is it possible to view only commits that may have affected it? 03.53.06 # <__builtin> not really, nearly any change to the code could have affected it 03.54.12 # <__builtin> git will automate nearly the entire process if you use its bisect feature 03.54.46 # <__builtin> just run `git help bisect' and follow the examples 03.55.42 # Build Server message: 3New build round started. Revision ca228d3, 255 builds, 13 clients. 04.09.28 # My internet is down right now, so idk how long it'll be before you see this, but 6e5f2876 works, so the issue was introduced sometime this year 04.09.33 # and my internet is back now 04.10.00 Join smoke_fumus [0] (~smoke_fum@188.35.176.90) 04.15.06 # <__builtin> ok, that's good 04.18.27 Join Gremuchnik [0] (~Gremuchni@108.188.230.69) 04.21.04 # Good evening, I would like to find one which of the many devices supported by Rockbox is the "best" one in terms of hardware (CPU speed, storage, expansion, sound, built quality, etc.). If there one more or less (if unofficial) "flagship"? 04.21.22 # <__builtin> nope 04.21.52 # <__builtin> we don't really favor any one device over another 04.21.56 # every device has its own quirks 04.22.04 # my SanDisk Sansa Clip+ si getting very old and they don't make them any more I think. Besides it has a tiny screen. 04.22.23 # And I know nothing about all the others. So some pointers would help :-) 04.22.43 # rockbox worked pretty well on the ipod series when i tried it last 04.23.01 # <__builtin> my personal preference is the ipod6g 04.23.05 # i've ran it on a 2g, a 4g, and a classic 04.23.41 # that is what I heard, but I have to confess that I really don't like Apple/Mac/iStuff (sorry, no offense intended). Any other candidates? 04.23.51 # oh, i've also set up rockbox on a sansa clip+ and a clip zip 04.24.08 # it works very well on the sansa clip, I love it. 04.24.10 # Build Server message: 3Build round completed after 1707 seconds. 04.24.11 # Build Server message: 3Revision ca228d3 result: 4 errors 7438 warnings 04.24.19 # and of course the thing i'm trying to get it working again on now, the cowon d2 04.25.34 *** Saving seen data "./dancer.seen" 04.26.01 # <__builtin> this is weird 04.26.14 # <__builtin> the build chart isn't showing which ones have errors 04.26.15 # in the process of bisecting 04.27.07 # thanks for your replies, I need to step out. if you have any other suggestions, please pm me. thanks 04.29.01 # <__builtin> walle303: good night, I will read the logs 04.29.06 # <__builtin> \o 04.29.09 Quit __builtin (Quit: Leaving) 04.29.28 # ok, see you __builtin o/ 04.57.19 Quit smoke_fumus (Read error: Connection reset by peer) 04.57.35 Quit kugel (Ping timeout: 240 seconds) 04.58.15 Join kugel [0] (~kugel@rockbox/developer/kugel) 05.03.46 Quit Strife89 (Quit: No Ping reply in 180 seconds.) 05.05.10 Quit kugel (Ping timeout: 255 seconds) 05.05.24 Join Strife89 [0] (~quassel@adsl-98-80-193-66.mcn.bellsouth.net) 05.10.06 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 05.12.50 Join Strife1989 [0] (~quassel@adsl-98-80-194-60.mcn.bellsouth.net) 05.14.09 Quit Strife89 (Ping timeout: 248 seconds) 05.15.26 Join kugel [0] (~kugel@ip5b4177dc.dynamic.kabel-deutschland.de) 05.15.26 Quit kugel (Changing host) 05.15.26 Join kugel [0] (~kugel@rockbox/developer/kugel) 05.26.26 Join asd__ [0] (5225d944@gateway/web/freenode/ip.82.37.217.68) 05.38.13 # clear 05.38.26 Join Ruhan [0] (uid76353@gateway/web/irccloud.com/x-fsqiwalbceiodzys) 05.43.21 Join dys [0] (~dys@tmo-102-73.customers.d1-online.com) 05.44.33 Quit pirik3 (Quit: Leaving) 05.49.28 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 05.53.39 Quit pirik3 (Quit: Leaving) 05.55.52 Quit kugel (Ping timeout: 260 seconds) 05.59.26 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 05.59.39 Quit pirik3 (Client Quit) 05.59.55 Join captainkewllllll [0] (cfed664a@gateway/web/freenode/ip.207.237.102.74) 05.59.58 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 06.02.52 Quit Strife1989 (Ping timeout: 260 seconds) 06.02.55 Quit pirik3 (Client Quit) 06.03.04 Join kugel [0] (~kugel@ip5b4177dc.dynamic.kabel-deutschland.de) 06.03.04 Quit kugel (Changing host) 06.03.04 Join kugel [0] (~kugel@rockbox/developer/kugel) 06.03.18 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 06.03.23 Join Strife89 [0] (~quassel@adsl-98-80-186-112.mcn.bellsouth.net) 06.05.22 Quit TheSeven (Ping timeout: 276 seconds) 06.06.13 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.07.09 Quit Strife89 (Client Quit) 06.08.33 Join Strife89 [0] (~quassel@adsl-98-80-186-112.mcn.bellsouth.net) 06.09.47 Quit captainkewllllll (Quit: Page closed) 06.10.17 Quit asd__ (Quit: Page closed) 06.25.38 *** Saving seen data "./dancer.seen" 06.25.48 Quit Gremuchnik (Quit: Бывайте ребята) 06.39.08 Quit TheSeven (Ping timeout: 255 seconds) 06.39.27 Join [7] [0] (~quassel@rockbox/developer/TheSeven) 07.05.24 Quit pirik3 (Ping timeout: 260 seconds) 07.22.48 Quit alexweissman (Remote host closed the connection) 07.25.00 Quit ps-auxw (Disconnected by services) 07.25.03 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 07.25.14 Join ps-auxw [0] (~arneb@p578F73A7.dip0.t-ipconnect.de) 07.32.41 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 07.35.02 Quit ps-auxw (Ping timeout: 258 seconds) 07.36.46 Join ps-auxw [0] (~arneb@p5B0FBF4C.dip0.t-ipconnect.de) 07.46.56 Quit Ruhan (Quit: Connection closed for inactivity) 08.22.46 Join ender` [0] (krneki@foo.eternallybored.org) 08.24.31 Quit alexweissman (Remote host closed the connection) 08.25.41 *** Saving seen data "./dancer.seen" 08.30.49 Quit michaelni (Ping timeout: 255 seconds) 08.41.40 Join Maarten [0] (541c501c@gateway/web/freenode/ip.84.28.80.28) 08.42.11 # Hey 08.43.28 Join michaelni [0] (~michael@213-47-41-20.cable.dynamic.surfer.at) 09.03.28 # Was just looking at the Fiio X1 port, but not sure how I can help 09.16.35 Quit dys (Ping timeout: 240 seconds) 09.19.21 Join lebellium [0] (~chatzilla@i15-les04-th2-31-35-19-195.sfr.lns.abo.bbox.fr) 09.27.19 Join dys [0] (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) 09.35.05 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 09.39.42 Quit alexweissman (Ping timeout: 255 seconds) 09.51.41 Join xorly [0] (~xorly@ip-86-49-24-93.net.upcbroadband.cz) 10.25.45 *** Saving seen data "./dancer.seen" 10.33.10 Join Strife1989 [0] (~quassel@adsl-98-80-196-25.mcn.bellsouth.net) 10.33.52 Join iceCalt [0] (~iceCalt@5.146.198.73) 10.36.20 Quit Strife89 (Ping timeout: 260 seconds) 10.38.59 Quit dys (Ping timeout: 255 seconds) 10.44.20 Quit Maarten (Quit: Page closed) 10.49.07 Join dys [0] (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) 10.55.44 Join parchd [0] (~parchd@unaffiliated/parchd) 10.58.20 Quit dys (Ping timeout: 255 seconds) 11.06.40 Quit kugel (Ping timeout: 248 seconds) 11.09.40 Join kugel [0] (~kugel@rockbox/developer/kugel) 11.10.39 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan) 11.11.44 Join dys [0] (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) 11.19.35 Join johnb4 [0] (~johnb2@p5B3AFF8E.dip0.t-ipconnect.de) 11.20.19 Join petur [0] (~petur@rockbox/developer/petur) 11.21.36 Quit nlogex (Ping timeout: 260 seconds) 11.23.54 Join freenoodle [0] (~jr@p4FC7FE17.dip0.t-ipconnect.de) 11.24.30 Quit freenoodle (Client Quit) 11.41.09 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.50.34 Quit johnb4 (Ping timeout: 240 seconds) 11.56.05 Quit pamaury (Ping timeout: 240 seconds) 12.00.54 Join uwe_ [0] (~uwe_@ipservice-092-217-124-220.092.217.pools.vodafone-ip.de) 12.03.35 Quit uwe__ (Ping timeout: 240 seconds) 12.25.47 *** Saving seen data "./dancer.seen" 12.30.03 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 12.31.05 Join nlogex [0] (~nlogex@198-16-168-171.on.cable.ebox.net) 12.42.31 Quit _meg (Ping timeout: 276 seconds) 12.43.10 Join _meg [0] (~notsure@211.25.203.45) 12.57.14 Join robertd1 [0] (~root@201.242.162.112) 13.03.10 Quit iceCalt (Ping timeout: 258 seconds) 13.03.44 Join iceCalt [0] (~iceCalt@5.146.198.73) 13.16.42 Join Strife89 [0] (~quassel@adsl-98-80-197-248.mcn.bellsouth.net) 13.19.43 Quit Strife1989 (Ping timeout: 255 seconds) 13.24.46 Quit robertd1 (Ping timeout: 276 seconds) 13.29.03 Join pirik3 [0] (~pirik3@cpc128650-hawk17-0-0-cust67.know.cable.virginm.net) 13.52.44 Join robertd1 [0] (~root@201.242.162.112) 14.24.49 Quit robertd1 (Ping timeout: 240 seconds) 14.25.49 *** Saving seen data "./dancer.seen" 14.39.10 Join robertd1 [0] (~root@186-90-51-247.genericrev.cantv.net) 14.42.15 Quit pirik3 (Ping timeout: 260 seconds) 15.20.20 Join johnb4 [0] (~johnb2@p5B3AFF8E.dip0.t-ipconnect.de) 15.30.29 Join Defenestrate [0] (~defenestr@unaffiliated/defenestrate) 15.49.37 Quit Defenestrate (Quit: Defenestrate) 15.54.57 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 16.25.52 *** Saving seen data "./dancer.seen" 16.32.04 Quit johnb4 (Ping timeout: 240 seconds) 16.38.04 Quit robertd1 (Ping timeout: 240 seconds) 17.00.40 Quit deevious (Ping timeout: 255 seconds) 17.00.52 Join johnb4 [0] (~johnb2@p5B3AFF8E.dip0.t-ipconnect.de) 17.17.58 Join deevious [0] (~Thunderbi@193.226.142.214) 17.25.54 Quit deevious (Quit: deevious) 17.28.34 Join __built1n [0] (980cfef3@gateway/web/freenode/ip.152.12.254.243) 17.30.24 # <__built1n> walle303: any progress? 17.37.24 Quit __built1n (Ping timeout: 260 seconds) 17.47.49 Join saratoga [0] (86ae6e0e@gateway/web/freenode/ip.134.174.110.14) 17.48.09 # walle303: check for mutex was added in https://git.rockbox.org/?p=rockbox.git;a=commit;h=3e738661108fb2a8e3474c6336c2a5c2668f82b6 17.48.48 # the D2 hasn't been developed in a long time, so probably no one noticed that it was hitting that check 18.06.45 Quit petur (Quit: Connection reset by beer) 18.12.02 Quit saratoga (Quit: Page closed) 18.21.12 Quit MrZeus (Read error: Connection reset by peer) 18.22.51 # __builtin: Sorry, was asleep, i'm down to 076cf0aa9bc484e9dbaee17660c2e77c16f46b13 and it's still functioning though 18.23.02 # inb4 heisenbug 18.25.55 *** Saving seen data "./dancer.seen" 18.27.39 Quit johnb4 (Ping timeout: 276 seconds) 18.28.41 Quit parchd (Quit: gone, disappeared, vanished in an instance leaving nothing but a trap door) 18.29.11 # oh yeah, it's got to be 18.29.16 # it doesn't show up when i build it myself 18.39.36 # oh wait, i was just being stupid 18.44.27 Quit jhMikeS (Ping timeout: 240 seconds) 18.59.04 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 18.59.56 Join johnb3 [0] (~johnb2@p5B3AFF8E.dip0.t-ipconnect.de) 19.01.11 Quit dys (Ping timeout: 255 seconds) 19.07.47 Join JanC_ [0] (~janc@lugwv/member/JanC) 19.09.04 Nick JanC is now known as Guest25300 (~janc@lugwv/member/JanC) 19.09.04 Quit Guest25300 (Killed (leguin.freenode.net (Nickname regained by services))) 19.09.04 Nick JanC_ is now known as JanC (~janc@lugwv/member/JanC) 19.13.47 Quit pamaury (Ping timeout: 255 seconds) 19.15.21 Join Gremuchnik [0] (~Gremuchni@108.188.230.69) 19.19.02 Join dys [0] (~dys@tmo-103-98.customers.d1-online.com) 19.29.34 Quit johnb3 (Ping timeout: 240 seconds) 19.30.36 Join johnb4 [0] (~johnb2@p5B3AFF8E.dip0.t-ipconnect.de) 19.34.31 # ok yeah, __builtin, saratoga was right, that commit is the first one to have the blackscreen 19.41.41 Quit dys (Remote host closed the connection) 19.44.34 Quit johnb4 (Ping timeout: 240 seconds) 19.57.39 Join dys [0] (~dys@tmo-103-98.customers.d1-online.com) 19.58.32 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 20.11.44 Join __built1n [0] (980cfef3@gateway/web/freenode/ip.152.12.254.243) 20.16.04 Quit __built1n (Ping timeout: 260 seconds) 20.17.56 Join __built1n [0] (980cfef3@gateway/web/freenode/ip.152.12.254.243) 20.22.29 Quit __built1n (Ping timeout: 260 seconds) 20.25.56 *** Saving seen data "./dancer.seen" 20.26.10 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:e992:438a:69a5:8c42) 20.49.16 Quit Jinx (Ping timeout: 246 seconds) 20.59.38 Join Jinx [0] (Dojo@unaffiliated/jinx) 21.02.13 Quit iceCalt (Remote host closed the connection) 21.06.04 Quit Slasheri (Ping timeout: 246 seconds) 21.06.21 Join Slasheri [0] (~miipekk@xen.ihme.org) 21.06.21 Quit Slasheri (Changing host) 21.06.21 Join Slasheri [0] (~miipekk@rockbox/developer/Slasheri) 21.26.31 Join zlo [0] (d593b152@gateway/web/freenode/ip.213.147.177.82) 21.29.01 Quit zlo (Client Quit) 21.33.56 Join zlo [0] (d593b152@gateway/web/freenode/ip.213.147.177.82) 21.35.35 # Hi, I have a Sansa Clip V2 which shows Boot 5.0 then Ver 3.14 and then ATA error: -2. With a little trying I somehow managed to boot into the USB keypad mode, but now I'm back to ATA error: -2, what can I do to fix this? 21.38.45 # it behaves differently when I press the home button during boot, it seems that started the keypad mode 21.39.31 # unfortunately no storage device is added when it is connected to the PC 22.03.09 # hm, in the meantime i somehow managed to enter the USB boot mode and I could reinstall rockbox (with the bootloader) 22.03.31 Join saratoga [0] (86ae6e0e@gateway/web/freenode/ip.134.174.110.14) 22.03.54 # then it started once quite normal (but no files where shown even though I think there should have been files) 22.04.06 # zlo: reboot into the sandisk firmware or the usb bootloader mode (both of which do not depend on the installed rockbox version), and then try updating to the current development build 22.04.20 # now after a second restart I'm back at ATA -2 22.04.57 # sorry to ask, but how do I boot into the bootloader mode? I landed there acidentally 22.05.43 # hold some button on power on 22.05.43 # ok, I managed to do it 22.05.53 # I'll try the update now 22.05.56 # i forget which is which, but push some and you'll end up in one of the two usb modes 22.08.53 # ok, same situation, now it displays the new version and then ATA error: -2 22.10.10 # should I try to boot into the original firmware or even uninstall rockbox? Or would that make things worse? 22.10.23 Quit saratoga (Ping timeout: 260 seconds) 22.14.01 # btw. when I unplug the player after the update it always displays *PANIC* Unhandled masked IRQ 03: INT_USB (status 0x00000008) 22.25.59 *** Saving seen data "./dancer.seen" 22.28.14 Join iceCalt [0] (~iceCalt@5.146.198.73) 22.41.29 # well, no matter what I try, after unplugging the player it displays *PANIC*. So it seems it is never doing a firmware update. The Rockboxutil also failes to remove the bootloader. It recommends to do a "normal" firmware update with the OF but that does not work. 22.42.16 # When restarting after removing the rockbox files from the player results in "Loading firmware - file not found". 22.42.31 # reinstalling rockbox results in ATA error: -2 23.19.48 Quit zlo (Ping timeout: 260 seconds) 23.24.06 Quit _meg (Ping timeout: 260 seconds) 23.24.37 Join _meg [0] (~notsure@211.25.203.45) 23.29.04 Quit _meg (Ping timeout: 240 seconds) 23.30.53 Join _meg [0] (~notsure@211.25.203.45) 23.31.33 Quit dys (Ping timeout: 240 seconds) 23.53.51 Quit xorly (Ping timeout: 260 seconds)