--- Log for 16.08.116 Server: weber.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 11 days and 8 hours ago 00.00.31 # robertd_: no, I don't understand what you are sending me 00.01.11 # in the directory where you run ct-ng build, you must have created a file called .config, as describe in my README 00.03.52 Quit petur (Quit: Leaving) 00.09.34 # any objections against g#1355? I decided to remove two links, where I couldn't find a replacement. 00.09.35 # 3Gerrit review #1355 at http://gerrit.rockbox.org/r/1355 : 3manual: fix/remove broken links by Sebastian Leonhardt 00.10.50 # looks fine to me 00.11.09 # looks fine 00.12.00 # BTW I edited the Wiki and marked the links as broken. I didn't want to remove them, because a developer might find the original link name helpful. 00.12.57 # <[Saint]> ulmutul: ah, good, I was going to ask that. 00.13.04 # <[Saint]> something something, internet archive. 00.13.07 # <[Saint]> so, thanks. 00.13.55 # Then I'll try to push the first patch by myself :) 00.17.07 # pamaury it is the same file with the permissions error . Sorry for the delay, I was double checking http://pastebin.com/C6AjJent 00.18.08 # robertd_: did you start from an empty directory ? 00.19.36 # if I were you I could 00.19.36 # 1) create a new empty directory 00.19.36 # 2) download my sony-arm-linux.config to this directory 00.19.36 # 3) cp sony-arm-linux.config .config 00.19.36 # 4) ct-ng menuconfig 00.19.37 *** Alert Mode level 1 00.19.37 # 5) in the menu, go to Path and Misc option, change the install prefix to whatever you like (don't use /usr/local but something your user can use preferably) 00.19.39 # 6) ct-ng build 00.19.44 # Build Server message: 3New build round started. Revision fe730d3, 255 builds, 15 clients. 00.19.59 # did you try to run ct-ng as root previously ? 00.21.26 # Pamaury, excellent. No, I did not. I am going to start a new build 00.22.21 # robertd_: I recently learn that you can run "ct-ng clean" on failure 00.22.28 # it should cleanup the directory 00.26.23 # You are right, It did. Just in case let me go for the clean slate 00.29.03 # Build Server message: 3Build round completed after 559 seconds. 00.29.04 # Build Server message: 3Revision fe730d3 result: All green 00.29.38 *** Alert Mode OFF 00.31.05 # <[Saint]> when we hit the ~600s mark, doesn't that mean something gave up? 00.31.20 # no 00.31.34 # <[Saint]> we've been hitting the 599/600s build mark quite regularly, too often for me to see it as a coincidence. 00.31.34 # It means we have fewer build clients than we used to :) 00.31.56 # It's not a coincidence. It's the expected speed for the farm as it is today 00.33.49 # Is there a way to build only specific parts of rockbox? I.e. just building the manuals had speed up this patch a lot :) 00.34.23 # You mean for the build farm? 00.34.37 # * pamaury notices of one his client is missing 00.34.37 # yes 00.35.08 # That would require some reliable code to determine what exactly needs to be rebuilt 00.37.14 # hum, my client is still running on my box but did not receive any build 00.37.52 # ah no my mistake 00.40.39 # robertd_: I will start to run some code on my NWZ E363 with the toolchain 00.46.25 # Pamaury please let me know how it goes 00.46.54 # well I have a working script that displays a message but only uses Sony's binaries so far 00.47.01 # so at least I know this works 00.58.02 # hum, my executable does not seem to work 00.58.28 # ah apparently I got a command wrong 01.03.06 Quit paulk-collins (Quit: Leaving) 01.07.54 # the executable does not seem to be working 01.12.26 Quit ulmutul (Quit: ChatZilla 0.9.92 [Firefox 47.0/20160604131506]) 01.12.43 # OMG 01.12.46 # it's working :D 01.15.08 # robertd_: ^ 01.16.31 # Pamaury thats great! 01.19.50 # I am going to bed, that's good news, now we can hopefully make progress 01.20.58 # pamaury thats a lot of progress with the compiler. have a good one 01.21.09 # did you manage to build it ? 01.23.09 # Im working on it, the problem is with the 2.9 glibc with that locale error not on the nt 01.23.55 # you still get this error, even on a clean build ? 01.24.18 # With the glibc yes 01.24.31 # can you send me the whole build.log ? or is it too big ? 01.24.46 # maybe compressed by email ? 01.25.10 # pamaury sure. Ill send it 01.28.27 *** Saving seen data "./dancer.seen" 01.29.44 Join Hoshi [0] (~Hoshi@aceh198.neoplus.adsl.tpnet.pl) 01.36.08 Quit Strife89|Quassel (Ping timeout: 244 seconds) 01.38.50 Quit pamaury (Ping timeout: 264 seconds) 02.13.05 # bluebrother: i agree that "6g" is not the appropriate name, had some thought about this at the beginning of development but decided to choose the shorter one and go forward 02.16.02 # really "mk6gboot" is not only for ipod6g but for s5l8702 CPUs that includes the nano3g, the Makefile is prepared to add nano3g at any moment and it should be able to install a bootloader for this target, so I had doubts among "6g", "ipod6g", "ipod8702", "s8702"... really I have no idea what would be the most appropriate, what do you think about this? 02.23.08 Quit Hoshi (Quit: Leaving) 02.34.48 Quit ZincAlloy (Quit: Leaving.) 02.35.04 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:2dcd:eb54:1534:596b) 02.35.13 Quit ZincAlloy (Client Quit) 02.37.21 # pamaury: thanks :) 03.28.29 *** Saving seen data "./dancer.seen" 05.28.33 *** No seen item changed, no save performed. 05.31.37 Quit neersighted (Remote host closed the connection) 05.32.14 Join neersighted [0] (~neer@firebrand.neer.io) 05.39.20 Quit athidhep (Quit: athidhep) 05.43.09 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 05.45.03 Quit JdGordon (Ping timeout: 240 seconds) 05.53.45 Quit michaelni (Read error: Connection reset by peer) 06.11.22 Join michaelni [0] (~michael@chello213047041020.graz.surfer.at) 07.17.15 Quit superkuh (Quit: the neuronal action potential is an electrical manipulation of reversible abrupt phase changes in the lipid bilayer) 07.26.34 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 07.28.36 *** Saving seen data "./dancer.seen" 07.32.39 Quit alexweissman (Remote host closed the connection) 07.33.27 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 07.44.48 Quit alexweissman (Remote host closed the connection) 08.07.28 Quit amiconn (Remote host closed the connection) 08.07.29 Quit pixelma (Remote host closed the connection) 08.08.18 Join pixelma [0] (~pixelma@rockbox/staff/pixelma) 08.08.19 Join amiconn [0] (~amiconn@rockbox/developer/amiconn) 08.42.24 Join edhelas [0] (~edhelas@145.133.43.230) 09.01.02 Quit robertd_ (Ping timeout: 264 seconds) 09.01.38 Quit robertd (Ping timeout: 264 seconds) 09.11.52 Quit edhelas (Ping timeout: 240 seconds) 09.16.40 Join petur [0] (~petur@rockbox/developer/petur) 09.28.39 *** Saving seen data "./dancer.seen" 09.31.12 Join utrack [0] (~utrack@21422.s.t4vps.eu) 09.35.24 Quit utrack (Changing host) 09.35.24 Join utrack [0] (~utrack@unaffiliated/utrack) 09.58.06 Join elensil [0] (~edhelas@2001:1c02:1903:d800:6111:b4db:29b5:2e82) 10.37.12 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:c4dc:5735:17cb:2e75) 11.28.43 *** Saving seen data "./dancer.seen" 11.42.48 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 11.46.03 Quit JdGordon_ (Ping timeout: 240 seconds) 11.56.08 Join paulk-collins [0] (~paulk@gagarine.paulk.fr) 12.12.09 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 12.23.29 Quit ZincAlloy (Quit: Leaving.) 12.33.43 Join Hoshi [0] (~Hoshi@aceh198.neoplus.adsl.tpnet.pl) 12.47.30 # prof_wolfff: there is no real convention but several mk*soc*boot exist: mkimxboot, mkrk27boot, mktccboot, mkamsboot, so why not mks5l8702boot ? It's a bit long you seem to think it's more accurate 12.47.32 Quit athidhep (Quit: athidhep) 12.49.38 Quit smoke_fumus (Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/) 13.28.47 *** Saving seen data "./dancer.seen" 13.49.32 Quit [Saint] (Read error: Connection reset by peer) 13.50.45 Join [Saint] [0] (~saint@rockbox/staff/saint) 14.25.06 Quit [Saint] (Remote host closed the connection) 15.11.08 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 15.28.51 *** Saving seen data "./dancer.seen" 15.32.47 Quit rela_ (Quit: Leaving) 15.38.45 Quit elensil (Ping timeout: 258 seconds) 15.43.01 Quit bluebrother (Disconnected by services) 15.43.06 Join bluebrother^ [0] (~dom@rockbox/developer/bluebrother) 15.43.33 Join fs-bluebot [0] (~fs-bluebo@x4d09929c.dyn.telefonica.de) 15.45.59 Quit fs-bluebot_ (Ping timeout: 258 seconds) 15.48.24 Join [Saint] [0] (~saint@rockbox/staff/saint) 15.52.03 Join elensil [0] (~edhelas@2001:1c02:1903:d800:6111:b4db:29b5:2e82) 15.53.17 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:3813:b3d7:ecbe:1fe8) 15.53.50 Quit [Saint] (Ping timeout: 276 seconds) 15.57.01 Join [Saint] [0] (~saint@rockbox/staff/saint) 15.57.33 Quit bp0 (Quit: Leaving) 15.58.40 Join Hoshi_ [0] (~Hoshi@clg249.neoplus.adsl.tpnet.pl) 16.02.56 Quit Hoshi (Ping timeout: 276 seconds) 16.24.32 Join bp0 [0] (~bp@unaffiliated/bp0) 16.45.19 Quit alexweissman (Remote host closed the connection) 16.54.46 Nick Hoshi_ is now known as Hoshi (~Hoshi@clg249.neoplus.adsl.tpnet.pl) 17.24.39 Quit petur (Quit: Connection reset by beer) 17.26.48 Quit bp0 (Remote host closed the connection) 17.28.55 *** Saving seen data "./dancer.seen" 17.33.59 Join bp0 [0] (~bp@unaffiliated/bp0) 17.38.29 Quit krnlyng (Ping timeout: 276 seconds) 17.50.48 Join krnlyng [0] (~liar@77.117.107.221.wireless.dyn.drei.com) 17.55.36 Join alexweissman [0] (~alexweiss@149.160.181.111) 17.59.51 Quit alexweissman (Ping timeout: 240 seconds) 18.01.11 Quit elensil (Quit: Leaving.) 18.03.18 Quit ender| (Remote host closed the connection) 18.03.49 Join ender| [0] (krneki@2a01:260:4094:1:42:42:42:42) 19.03.43 Join alexweissman [0] (~alexweiss@c-68-51-123-75.hsd1.in.comcast.net) 19.09.56 Join rela [0] (~x@pdpc/supporter/active/rela) 19.23.42 Join lebellium [0] (~chatzilla@89-93-176-213.hfc.dyn.abo.bbox.fr) 19.28.58 *** Saving seen data "./dancer.seen" 19.54.05 Nick JanC is now known as Guest86015 (~janc@lugwv/member/JanC) 19.54.06 Join JanC [0] (~janc@lugwv/member/JanC) 19.56.17 Quit Guest86015 (Ping timeout: 276 seconds) 20.03.05 Quit saratoga (Quit: Page closed) 20.16.36 Join advcomp2019 [0] (~advcomp20@unaffiliated/advcomp2019) 20.18.38 Quit advcomp2019_ (Ping timeout: 265 seconds) 20.22.31 Join robertd [0] (c9f2b970@gateway/web/freenode/ip.201.242.185.112) 20.22.50 # pamaury http://pastebin.com/8U6Rpqz6 20.23.18 # robertd: good stuff :) 20.24.20 # thank you for all your help pamaury 20.26.34 # we are nowher near a working port yet 20.28.23 # pamaury we are closer than a few years ago. Now i can recreate the environment 20.30.00 # My next step if to produce instructions to explain how to craft an upgrade that dumps the root file system 20.43.22 # robertd: what do you mean by recreate the environment ? 20.44.47 # pamaury to create a virtual copy of the device 20.59.25 # so the nwz-474 is too included in this breakthrough? 21.06.25 Quit robertd (Ping timeout: 264 seconds) 21.07.25 Join mexit [0] (5f5bff09@gateway/web/freenode/ip.95.91.255.9) 21.09.17 Join robertd [0] (c9f2b970@gateway/web/freenode/ip.201.242.185.112) 21.10.09 # robertd: I am not sure what you mean or what you have in mind 21.11.53 # Hoshi: it's not really a breakthrough, and no the cross compiler we have does not apply to the e470, it uses a different cpu and kernel, but the same principles will apply hopefully 21.12.11 # ok :P 21.15.11 # Hi, I have Sansa Clip+, don't turn on. Linux has detected 4 MB disc. Here: http://www.rockbox.org/wiki/SansaAMSUnbrick is that "If it reports 4MB, your flash is broken." It's totally dead? 21.23.15 # mexit: better wait for someone who really knows the clip+ well but usually the 4MB disc is game over yeah 21.26.48 # pamaury the aproach is through a quick emulator 21.27.21 # we don't have any emulator for this soc 21.27.36 # we don't even have all the docs 21.29.01 *** Saving seen data "./dancer.seen" 21.50.54 Quit mexit (Quit: Page closed) 21.53.25 # pamaury, bluebrother: mks5l8702boot is long and difficult to remember but it seems the more accurate, mks5lboot seems not valid because nano4g (a possible future target) uses s5l8720 with a different bootloader installation method (AFAIK), really i don't mind too much the name, will change it to mks5l8702boot if there is no other better proposal 21.54.47 # prof_wolfff: what is the install method of the nano4g ? could a potential "mks5lboot" support several methods ? 21.55.35 Join smoke_fumus [0] (~smoke_fum@188.35.176.90) 21.56.48 # prof_wolfff: the name does not need to be 100% accurate though, clearly some others aren't 21.57.15 # so mks5lboot looks fine to fine, it can be renamed later 22.00.12 # pamaury: i don't know exactly the details but it is not the same exploit used for ipod6g and nano3g, i agree we can use "mks5lboot" now and rename it if necessary later 22.02.49 # <__builtin> is the ipod6g exploit really that much of an "exploit"? 22.05.28 # __builtin: doesn't it rely on a parsing bug in the bootrom ? 22.06.36 # robertd: are you willing to help and risk bricking your device for rockbox ? :D 22.11.32 # pamaury yes 22.11.59 # ok good, just to say, I tried it on mine and given what we know about your device, I don't see any reason why it would fail 22.12.15 # all right 22.12.41 # this involves sending a firmware upgrade that I create with a script that show information. For now it shows the output of "mount", but they it can easily be hacked to do something else 22.13.11 # like the sendfirm ? 22.13.34 # so you need: 22.13.35 # - rockbox repository 22.13.35 # - linux host 22.13.35 DBUG Enqueued KICK pamaury 22.13.35 # You need to to go utils/nwztools/upgtools, run make 22.13.35 # Then go to utils/nwztools/scsitools, run make 22.14.52 # once this is done, create an empty directory somewhere, download this: https://gist.github.com/pamaury/a8dc2a5a816e68806e93277d932243e2 22.15.04 # rename to whatever your like, for example update.sh 22.16.41 # pamaury first part http://pastebin.com/B1B5rcZh 22.17.13 # thanks fine, "just warnings" 22.17.25 # when you are done, run: 22.17.25 # /path/to/upgtools/upgtools -c -m nwz-a86x NW_WM_FW.UPG update.sh 22.17.40 # then send me the NW_WM_FW.UPG for verification 22.18.42 Quit idonob (Quit: bye) 22.24.16 # pamaury the last words sony_update.sh? 22.24.29 # whatever your named the file 22.24.48 # if you named it sony_update.sh then yes replace the last words with sony_update.sh 22.29.11 # it says upgtools command not found 22.29.31 # you have to replace /path/to/upgtools/upgtools by the path your upgtools in your rockbox repository 22.29.48 # ah sorry it's /upgtool (without s) 22.30.06 # ah let me try again 22.33.09 Join idonob [0] (~Owner@S0106602ad08ec3dd.vs.shawcable.net) 22.33.31 # pamaury http://pastebin.com/wMCNKcUu 22.33.39 # i send you the other file 22.33.44 Join athidhep [0] (~afoakf@unaffiliated/athidhep) 22.34.00 # can you send me the NW_WM_FW.UPG file by email just to make sure ? 22.36.16 # pamaury yes, it is on the mail 22.40.29 # robertd: I didn't receive any email... 22.41.35 # pamaury i sent it to the gmail adress 22.41.47 # the messenger pigeon is on its way 22.43.13 # did you receive it ? 22.43.30 # no, you must gotten my address wrong 22.44.02 # one sec 22.44.35 # ah got it 22.44.43 # ahh 22.46.54 # ok I confirmed it looks ok 22.47.02 # now for the dangerous part 22.47.09 # ok 22.47.11 # plug your device, in mass storage mode 22.47.36 # right 22.48.32 # now mount it it (using your favorite file browser for example), put NW_WM_FW.UPG at the root, umount it 22.49.12 # then you need to find the device node corresponding to your device. I suggest your use "dmesg | tail", to see what name the kernel gave to your device. Probably something like /dev/sdb 22.51.34 # tell me when you found it, in doubt just pastebin the output of "dmesg | tail" 22.53.52 # http://pastebin.com/zb2m96Au 22.55.56 # does your NWZ-A860 has 64GB of storage ? 22.56.05 # yes 22.56.14 # ok, so now for the upgrade 22.56.45 # you need to run: 22.56.45 # sudo /path/to/nwztools/scsitools/scsitool /dev/sdb do_fw_upgrade 22.57.05 # one sec please 22.57.21 # if everything goes well it should not display anything but "Result:" and your device will start a firmware upgrade 22.59.38 # bash: scsitool: command not found 23.00.10 Quit lebellium (Quit: ChatZilla 0.9.92 [Firefox 48.0/20160726073904]) 23.01.12 # did you use the correct path ? and run make -C nwztools/scsitools 23.01.33 # loop 23.02.08 # wow briefly showed several letters roofts on 23.03.19 # I assumed it worked ? Normally you should have seen a message "Rockbox me please !", then a red screen, then the output of "mount". And 10sec later the device should have rebooted and be back to normal 23.04.36 # robertd: yes ? 23.05.24 # pamaury the letters were real small it rebooted 23.06.00 # ok, so what would be awesome is if you could take of photo of the screen when it displays the output of mount 23.06.44 # at the moment I don't have any better way of doing this 23.07.07 # to rerun the whole process (if you don't want to change the script), just run again "sudo /path/to/nwztools/scsitools/scsitool /dev/sdb do_fw_upgrade" 23.07.23 # it is ok. let me see how i manage to take that pic 23.07.50 Ctcp Ignored 1 channel CTCP requests in 0 seconds at the last flood 23.07.50 # * pamaury advises not to use the flash, because it will make it unreadable 23.09.47 # just for future reference, here is a simplified version of mine: 23.09.47 # rootfs on / (rootfs) 23.09.47 # /dev/root on / (ext2) 23.09.47 # /dev/contents_part on /contents (vfat) 23.11.05 # i just miss it 23.11.17 # yes, it does say rockboxme 23.11.28 # too quick for me 23.11.57 # pamaury just like you told 23.12.26 # it should stay on for 10 seconds, that should be enough to take a pic 23.13.31 # let me try it again 23.19.55 # no, no sucess. let me try tomorrow with the light 23.25.16 Join edhelas [0] (~edhelas@145.133.43.230) 23.29.02 *** Saving seen data "./dancer.seen" 23.30.23 # yes pamaury please check your mail 23.30.46 # no email at the moment 23.33.11 # ah got it thanks 23.33.25 # I'll write a script tomorrow to dump the rootfs 23.33.43 # you are most welcome 23.40.48 Quit Hoshi (Read error: Connection reset by peer)