--- Log for 02.09.111 Server: niven.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 5 hours and 26 minutes ago 00.02.42 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 00.02.46 Quit TheLemonMan (Quit: WeeChat 0.3.5) 00.03.06 Join TheLemonMan [0] (~LemonBoy@ppp-161-48.26-151.libero.it) 00.07.23 Quit ReimuHakurei (Quit: And therefore, dye this sky red. The time has come again for my body to only go forward / Even the 'people' who pass by and the 'things' which become lost in confusion / Will one day be like vanished memories) 00.07.39 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 00.07.52 Quit ReimuHakurei (Read error: Connection reset by peer) 00.07.56 Quit ChickeNES (Quit: Computer has gone to sleep.) 00.08.11 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 00.08.22 Quit bluefoxx (Ping timeout: 264 seconds) 00.08.45 Quit wodz (Read error: Operation timed out) 00.09.12 Quit bertrik (Quit: :tiuQ) 00.11.20 Quit domonoky (Read error: Connection reset by peer) 00.18.00 Join bluefoxx [0] (fuzzylomba@2002:4647:1f1f::4647:1f1f) 00.20.55 Quit ageis (Read error: Connection reset by peer) 00.21.37 Join ageis [0] (~ageis@c-76-127-201-198.hsd1.ma.comcast.net) 00.24.38 Quit stripwax (Quit: http://miranda-im.org) 00.33.30 Join nick-p [0] (~nick@82-69-105-120.dsl.in-addr.zen.co.uk) 00.36.02 *** Saving seen data "./dancer.seen" 00.37.58 Join Scromple [0] (~Simon@115-64-195-104.static.tpgi.com.au) 00.53.04 Quit ender` (Quit: A man should live forever or die trying. -- Spider Robinson) 01.02.42 Join ChickeNES [0] (~ChickeNES@c-68-51-76-85.hsd1.il.comcast.net) 01.17.01 Quit Keripo (Read error: Connection reset by peer) 01.31.47 Quit bluefoxx (Ping timeout: 260 seconds) 01.32.33 Join bluefoxx [0] (FuzzyLomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 01.36.27 Quit MethoS- (Remote host closed the connection) 01.48.29 Join CaptainKewl [0] (captainkew@216.220.65.110) 02.07.45 Quit robin0800 (Ping timeout: 258 seconds) 02.11.43 Quit pamaury (Remote host closed the connection) 02.12.55 Join Keripo [0] (~Keripo@eng340.wireless-resnet.upenn.edu) 02.13.23 Join robin0800 [0] (~robin0800@149.254.61.29) 02.14.13 Quit Scromple (Quit: Leaving) 02.17.47 Join Scromple [0] (~Simon@115-64-195-104.static.tpgi.com.au) 02.36.05 *** Saving seen data "./dancer.seen" 03.31.17 Join Scr0mple [0] (~Simon@115-64-195-104.static.tpgi.com.au) 03.32.40 Quit Scromple (Ping timeout: 250 seconds) 03.33.04 Quit robin0800 (Read error: Connection timed out) 03.33.51 Join robin0800 [0] (~robin0800@149.254.60.157) 03.36.17 Quit TheLemonMan (Quit: WeeChat 0.3.5) 03.49.59 Quit nick-p (Quit: Leaving) 03.51.15 # <[Saint]> bluebrother: Sure, send me a 240x320 build? 03.52.43 # <[Saint]> evilnick: Did you have a poke at the new theme? 03.53.17 # <[Saint]> You're probably my most...Hmmm, what's the word. Consistent? Tester...so, input == appreciated. 03.57.08 Join ReimuHakurei_ [0] (~kudo@wireless.sit-co.net) 03.57.44 Join FoH_Phobos [0] (~foh@adsl-98-71-70-193.bhm.bellsouth.net) 03.58.07 Quit ReimuHakurei (Read error: Connection reset by peer) 03.58.13 Quit FoH_Phobos (Client Quit) 04.09.58 Quit pixelma (Disconnected by services) 04.09.59 Join pixelma_ [0] (quassel@rockbox/staff/pixelma) 04.09.59 Quit amiconn (Disconnected by services) 04.10.00 Join amiconn_ [0] (quassel@rockbox/developer/amiconn) 04.10.12 Nick pixelma_ is now known as pixelma (quassel@rockbox/staff/pixelma) 04.10.20 Nick amiconn_ is now known as amiconn (quassel@rockbox/developer/amiconn) 04.36.06 *** Saving seen data "./dancer.seen" 04.40.19 # <[Saint]> ....seriously. 04.40.30 # <[Saint]> *no* comments on FS#12254 ? 04.40.31 # http://www.rockbox.org/tracker/task/12254 3RaaA cabbiev2 [Full Touch Application Port] (patches, new) 04.40.40 # * [Saint] is slightly perplexed. 04.41.14 # <[Saint]> No comments from devs I expect, but users...colour me surprised. 04.42.12 # err... users never comment 04.42.23 # and devs day nothing untill post commit 04.42.32 # and that cant be committed untill wpsbuild.pl is fixed 04.43.09 # It's been up like... less than a day? Post to the mailing list, post to the forums, and have patience if you actually want comments on the task. 04.43.27 Quit TheSeven (Disconnected by services) 04.43.43 Join [7] [0] (~TheSeven@rockbox/developer/TheSeven) 04.44.37 # <[Saint]> It's been on the forums for an age, with users constantly bugging me via PM, that's why I'm surprised. 04.44.49 # <[Saint]> Users *can't* comment on the forum, I locked the thread. 04.45.36 # <[Saint]> Ah.....I see. They've moved to Google+ now :-S 04.49.26 Join powell14ski_ [0] (~powell14s@c-174-51-194-6.hsd1.co.comcast.net) 04.52.26 Join typn [0] (~quassel@184-155-93-126.cpe.cableone.net) 05.07.47 # kugel: that's the same algorithm! :) a different autocorrelation implementation (sort of) but it looks the same 05.08.59 # or at least very, very similar enough to look nearly the same :) 05.10.07 # ah, same guy did it 05.24.25 Quit Keripo (Quit: Leaving.) 05.28.26 Quit ChickeNES (Ping timeout: 240 seconds) 05.39.37 Join Rob2223 [0] (~Miranda@p5DE4BC1D.dip.t-dialin.net) 05.43.03 Quit Rob2222 (Ping timeout: 245 seconds) 05.50.33 Quit typn (Ping timeout: 258 seconds) 05.55.24 Quit robin0800 (Ping timeout: 252 seconds) 05.56.39 Join robin0800 [0] (~robin0800@149.254.60.157) 05.59.11 Join typn [0] (~quassel@184-155-86-74.cpe.cableone.net) 06.14.13 Quit factor (Read error: Connection reset by peer) 06.16.26 Quit ageis (Read error: Connection reset by peer) 06.23.08 Quit typn (Ping timeout: 240 seconds) 06.24.27 Join typn [0] (~quassel@24-116-213-82.cpe.cableone.net) 06.26.04 Join ageis [0] (~ageis@c-76-127-201-198.hsd1.ma.comcast.net) 06.31.34 Join factor [0] (~factor@74.197.205.204) 06.32.06 Quit robin0800 (Quit: Leaving) 06.34.16 Quit typn (Ping timeout: 252 seconds) 06.35.39 Join typn [0] (~quassel@24-116-213-82.cpe.cableone.net) 06.36.07 *** Saving seen data "./dancer.seen" 06.40.47 Quit typn (Remote host closed the connection) 06.45.04 # this is probably more of a problem with my Linux, but when I try to open the rockbox installer to update RockBox, it gives the error "Mountpoint is not writeable" 06.45.41 # how could I go about fixing this? 06.45.58 # mount it with the correct options 06.46.44 # I'm mounting it with KDE by clicking it in dolphin, and it's not running as root or anything. 06.47.14 # the terminal outputs: "libusb couldn't open USB device /dev/bus/usb/002/005: Permission denied." a bunch 06.47.40 # were is that error coming from? 06.47.47 # oh, ok 06.47.52 # did you run rbutil as root? 06.48.09 # no 06.48.13 # do that 06.49.48 # still saying that the mountpoint is not writable 06.50.03 # what is? 06.50.19 # it could be that I've corrupted the RockBox install by unmounting it unproperly 06.50.30 # rbutil 06.51.10 # maybe I could try deleting the .rockbox folder after backing up my configurations? 06.51.34 # if it isnt writeable linux wont let you delete the folder 06.51.44 # did you run rbtuil as root? 06.51.58 # yes 06.52.28 # it only seems to say that after I try to install it and it fails extracting 06.53.38 # rm: cannot remove `./.rockbox/*': Read-only file system 06.54.13 # if not even root can write its a corrupt filesystem and you need to run fsck 06.56.33 # how can I tell where my SD player is located? 07.01.41 # if I use lsusb it says "Bus 001 Device 034: ID 0781:7441 SanDisk Corp." 07.02.03 # where do I fsck? 07.02.18 # what does "mount" say 07.03.09 # that worked "/dev/sdb1 on /media/SD PLAYER type vfat (rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=100,shortname=mixed,dmask=0077,utf8=1,showexec)" 07.03.44 # <[Saint]> just do "fsck -A" if you really can't be arsed tracking down the mountpoint. It will walk through fstab and go through all mountpoints it finds. 07.09.02 # "There are differences between boot sector and its backup." "1) Copy original to backup" "2) Copy backup to original" "3) No action" 07.10.23 # what do I choose? 07.13.14 Join ChickeNES [0] (HydraIRC@99-133-145-177.lightspeed.cicril.sbcglobal.net) 07.13.34 # I did fsck -a and it gave me "Unable to create unique name" 07.14.07 # and a bunch of files contained free clusters so it assumed EOF 07.15.48 # and it did nothing 07.18.31 # format the drive 07.18.33 # simplest fix 07.18.43 # <[Saint]> [17:02] <[Saint]> just do "fsck -A" if you really can't be arsed tracking down the mountpoint. It will walk through fstab and go through all mountpoints it finds. 07.18.53 # <[Saint]> not "a", "A" 07.19.20 # when I do that it tries to do it to /dev/sda2 and warns me that it's mounted 07.19.52 # I'm doing sudo fsck -a /dev/sdb1 to automatically repair the partitions of it 07.20.03 # and it's not working 07.20.29 # <[Saint]> Then, as JdGordon| said....format the bastard. Simplest "fix" for FS corruption. 07.21.01 # ok, backing up the music right now 07.21.48 # whoa a lot of music got disappeared during the corruption :/ 07.22.26 # til not to unplug without unmounting properly :p 07.30.24 Quit ageis (Ping timeout: 240 seconds) 07.30.25 # does formating the sansa e200 get rid of the original firmware? 07.30.49 # <[Saint]> No. 07.30.56 # ok good 07.35.57 # gparted: Input/output error during write on /dev/sdb 07.36.08 # wtf? 07.38.39 # it won't even let me format it 07.41.15 Join Keripo [0] (~Keripo@eng340.wireless-resnet.upenn.edu) 07.51.07 # are you using rockbox usb or sansa usb? 07.52.13 # sansa usb, rockbox won't start up properly 07.52.27 # due to said corruption 07.54.57 Join wodz [0] (~wodz@87-206-240-131.dynamic.chello.pl) 07.55.05 # I want to say you need to do a full recovery, but others might have a better idea 07.55.10 # wodz: hey 07.55.23 # tjb0607: there is a chance you are striked by linux ehci bug 07.55.37 # what's that? 07.57.11 # tjb0607: It is rather well known that certain devices doesn't like ehci driver in linux. The only known solution so far is to force fallback to USB1.1 as this is handled by diferent part of the controller and has separate driver 07.57.29 # Saidly linux developers seems to do nothing about it 07.57.43 # oh wow so I plug it in to another usb port and the permissions are fixed 07.57.51 # now to go back to updating rockbox 07.58.13 # its about usb input/output errors, spurious usb resets and so on 07.58.40 # actually nope 07.58.50 # would rebooting fix it? 07.59.18 # If this is the bug I am talking about - no 08.00.38 # my mp3 player worked before 08.00.49 # with my linux installation 08.01.02 # should it work on another linux desktop? 08.02.38 # If it worked and didn't behaved erratically than this is not ehci thing. 08.02.46 # also, it mounts and reads the files fine but it can't make any changes to the files 08.02.58 # tjb0607: Try to logout and login once more - sometimes this helps 08.03.20 Quit tjb0607 (Read error: Connection reset by peer) 08.04.22 Join tjb0607 [0] (~quassel@208-100-128-206.bendbroadband.com) 08.04.59 # Anyone have a clue why changing bit with unknown meaning in register configuring clock dividers might influence only read speed of sdram and not write speed? 08.05.37 # that didn't do anything. Does loggin out/back in via kdm restart x? 08.05.59 # dunno 08.06.22 # <[Saint]> it /should/ do... 08.06.23 Quit tjb0607 (Remote host closed the connection) 08.09.36 Join tjb0607 [0] (~quassel@208-100-128-206.bendbroadband.com) 08.09.40 Join n1s [0] (~quassel@rockbox/developer/n1s) 08.10.02 Quit powell14ski_ (Quit: powell14ski_) 08.10.24 # I rebooted and I'm trying again 08.10.42 # nope 08.11.24 # one thing - is this drive SD card? 08.11.30 # yes 08.11.42 # maybe it is simply locked by the switch? 08.11.56 # hold is off 08.12.15 # otherwise the rockbox boot loader would've halted the boot process 08.12.28 # the switch on the card 08.13.21 # does locking it prevent the reading of files? 08.14.10 # no 08.14.16 # writing though 08.14.55 # ok because that's my problem 08.15.03 # lemme screw my mp3 player open 08.15.32 # after I find a smaller screwdriver 08.17.09 Join JdGord [0] (~AndChat@58.108.85.101) 08.17.14 # sorry but is it the internal storage that is not writeable? 08.17.38 # right 08.17.51 # there's probably no switch on that 08.18.52 # yeah all there is is a battery 08.21.34 Quit wodz (Quit: Leaving) 08.22.15 # Doesn't linux mount filesystems read only if it finds errors? I'd do an fsck 08.22.25 # <[Saint]> It does, yeah. 08.24.11 # amiconn: yeah but the device node is read only too apparenlty 08.25.18 # tjb0607: does dmesg say anything interesting about it? 08.30.47 Quit tjb0607 (Read error: Connection reset by peer) 08.31.54 Join tjb0607 [0] (~quassel@208-100-128-206.bendbroadband.com) 08.32.14 # I think it fixed itself 08.32.25 Quit JdGord (Quit: Bye) 08.32.27 # I was able to successfully install rockbox 08.32.48 # siunds like something is fishy 08.34.22 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 08.34.46 # but rockbox still isnt' booting... 08.36.11 *** Saving seen data "./dancer.seen" 08.36.38 Quit bluefoxx (Ping timeout: 276 seconds) 08.37.20 # apparently I had permissions for a while after I mounted it, I was able to create a folder, but now I don't have permissions. 08.38.50 Join bluefoxx [0] (fuzzylomba@S0106e0cb4e0a6d8a.vs.shawcable.net) 08.39.03 # [ 1701.766047] FAT-fs (sdb1): error, fat_get_cluster: invalid cluster chain (i_pos 440540) 08.39.03 # [ 1701.766051] FAT-fs (sdb1): Filesystem has been set read-only 08.41.33 # and then gparted gives "Error fsyncing/closing /dev/sdb: Input/output error" 08.41.55 # when I try reformating 08.46.13 # [Saint]: Some feedback on your theme; 1) Why does the Next Track text change from bold to non-bold depending on whether AA is present? 2) The highlight on the Context menu icon looks different to that on the Quickscreen menu icon 3) Can the volume icon change to something different on mute? 08.46.37 # I guess I'll try reformatting it in windows 7, but I doubt that will work 08.46.50 # who knows 08.47.02 Quit tjb0607 (Remote host closed the connection) 08.47.50 Quit ChickeNES (Quit: Computer has gone to sleep.) 08.48.51 Join nick-p [0] (~nick@82-69-105-120.dsl.in-addr.zen.co.uk) 08.53.25 Join tjb0607 [0] (~quassel@208-100-128-206.bendbroadband.com) 08.54.07 # well windows didn't even let me use my wireless card 08.54.09 # :p 08.55.20 Join ender` [0] (~ender@foo.eternallybored.org) 08.57.14 # I could try my brother's computer 09.03.12 # nope same problem 09.03.48 Join petur [0] (~petur@rockbox/developer/petur) 09.04.18 Join einhirn [0] (~Miranda@bsod.rz.tu-clausthal.de) 09.06.10 Quit CaptainKewl (Ping timeout: 240 seconds) 09.06.16 Quit simonlnu (Read error: Operation timed out) 09.06.49 # is there something else I could try other than gparted to reformat my sansa e260 that might not give an i/o error? 09.09.27 Quit Keripo (Quit: Leaving.) 09.10.07 # tjb0607: it sounds like a hw issue to me 09.10.15 # yeah 09.10.25 # is there anything else I could do? 09.10.41 # IIRC the e200 has the flash memory on a daughter board, and some people have reported reseating it has fixed weird problems 09.10.54 # so perhaps try that? 09.11.12 # how can I reset it? 09.11.35 # It wouldn't hurt to try that, but that usually fixes the 'black screen and glowing ring of light' issue 09.11.51 # reseat, unplug, plug in 09.11.53 # tjb0607: Reseat, not reset. 09.12.26 # how can I do that? 09.12.47 # unscrew the back of the sansa and use your fingers! 09.13.17 # There are (probably) pictures on the Wiki about this 09.16.52 Join HaimN [0] (~HaimN@31.44.130.194) 09.17.04 Quit HaimN (Remote host closed the connection) 09.17.22 Join HaimN [0] (~HaimN@31.44.130.194) 09.18.10 # http://i.imgur.com/S5nIy.jpg What do I do from here? 09.19.11 # <[Saint]> Push hard on the smaller rectangle in the black bit. 09.19.26 # tjb0607: actually unscrew the back, probably remove the battery first 09.19.28 # <[Saint]> not *too* hard, though ;) 09.19.52 # check under the battery fro screws 09.20.05 # <[Saint]> n1s: I didn't think that was necessary... 09.20.20 # [Saint]: i don't know but there could be screws there! 09.20.20 # <[Saint]> perhaps I'm thinking of another player model, hmmm. 09.20.34 # <[Saint]> No, I mean removing the battery at all. 09.20.51 # tjb0607: there are pictures and videos on the internet of this and they are probably better than our guessing 09.21.08 # http://daniel.haxx.se/sansa/e200-devboard.html <= that's how it looks below the cover 09.21.13 # <[Saint]> I thought it just needed to push on the back rubber bit immediately under the case backing. 09.21.29 # (apart from an extra cable on those pics) 09.23.01 # so what do I do? 09.23.04 Join simonlnu [0] (G54TvYsAZH@unaffiliated/simonrvn) 09.23.35 # I pushed the black rubber bit but it didn't seem to do anything 09.24.11 Quit Scr0mple (Quit: Leaving) 09.24.13 Quit HaimN (Quit: Leaving) 09.24.51 Join HaimN [0] (~HaimN@31.44.130.194) 09.24.59 # yeah that did nothing 09.27.55 # I was able to install rockbox by unmounting and mounting repeatedly 09.28.15 # tjb0607: installing rockbox is unliekly to fix this 09.29.09 Quit ReimuHakurei_ (Ping timeout: 240 seconds) 09.29.57 # it at least fixes my rockbox problem 09.30.15 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 09.32.39 # and I'm now able to write to the internal storage device 09.33.52 # but after like 20 seconds of it being mounted the access is denied 09.34.09 # or me trying to delete the corrupt .rockbox folder from the trash 09.34.53 # but thanks to rockbox I can delete it without having to worry about unmounting stuff 09.36.10 # I think it's mostly fixed 09.36.58 # yeah I can do whatever and there's no I/O errors or anything 09.37.17 # idk what I did but it works 09.38.56 # did anything wps-related get changed last update? 09.40.04 Join ReimuHakurei_ [0] (~kudo@wireless.sit-co.net) 09.41.26 # nope it's just that my background image got half corrupted 09.41.57 Quit ReimuHakurei (Ping timeout: 250 seconds) 09.42.35 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 09.43.47 # ok so apparently it *didn't* get fixed 09.44.29 # I just have to unmount and remount to write to it :p 09.44.54 Join Kudo-san [0] (~kudo@wireless.sit-co.net) 09.45.17 Quit ReimuHakurei_ (Ping timeout: 252 seconds) 09.46.10 # I guess it's good for now, maybe tomorrow I can get it to stop with the read-only problem. For now, bedtime. 09.48.01 Quit ReimuHakurei (Ping timeout: 250 seconds) 09.48.26 Join Challapradyumna [0] (~Pradyumna@117.197.219.153) 09.49.37 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 09.51.37 Quit Kudo-san (Ping timeout: 258 seconds) 09.53.26 Join ReimuHakurei_ [0] (~kudo@wireless.sit-co.net) 09.55.47 Quit ReimuHakurei (Ping timeout: 240 seconds) 09.56.38 Join mudd1 [0] (~cmertes@ip-78-94-202-227.unitymediagroup.de) 10.21.31 Quit ReimuHakurei_ (Read error: Connection reset by peer) 10.21.45 Join ReimuHakurei_ [0] (~kudo@wireless.sit-co.net) 10.27.37 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 10.30.32 Quit ReimuHakurei_ (Ping timeout: 245 seconds) 10.36.15 *** Saving seen data "./dancer.seen" 10.37.53 Quit ReimuHakurei (Read error: Connection reset by peer) 10.38.30 Join ReimuHakurei [0] (~kudo@wireless.sit-co.net) 10.47.14 Quit ReimuHakurei (Ping timeout: 258 seconds) 10.49.44 Join TheLemonMan [0] (~LemonBoy@ppp-170-54.26-151.libero.it) 10.58.12 Quit TheLemonMan (Quit: WeeChat 0.3.5) 11.02.11 Join casainho [0] (~chatzilla@2.81.155.140) 11.03.56 Quit [Saint] (Quit: Imagination is for turbo-nerds who can't handle how kick-butt reality is. I'm a kick-butt reality master! I would rather die, than be imaginative. I mean that.) 11.06.34 Join NicolasMonroy [0] (~8d465195@giant.haxx.se) 11.06.36 Join [Saint] [0] (~st.lasciv@119.224.108.127) 11.08.55 # Hi guys, anyone who could add me to the CFmodguide? I would like to post a success with my ipod 11.21.35 Quit casainho (Remote host closed the connection) 11.26.50 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 11.41.36 Quit NicolasMonroy (Quit: CGI:IRC) 12.02.37 # <[Saint]> bluebrother: Ping? 12.02.47 Quit neferty (Ping timeout: 252 seconds) 12.03.22 # <[Saint]> Would it be too much to ask for you to build me one of your "AA in Notification Area" RaaA .APKs? 12.04.29 Join neferty [0] (~andor@173.242.127.201) 12.09.50 Quit Challapradyumna (Quit: Bye Bye) 12.13.19 Quit HaimN (Remote host closed the connection) 12.25.46 Quit evilnick (Ping timeout: 260 seconds) 12.29.27 Join God_Eater [0] (93722cd1@rockbox/staff/GodEater) 12.30.31 Join evilnick [0] (~evilnick@5acc2b53.bb.sky.com) 12.30.31 Quit evilnick (Changing host) 12.30.31 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 12.36.18 *** Saving seen data "./dancer.seen" 12.56.39 Join Jerom1 [0] (~jerome@79.132.42.100) 12.59.52 Quit evilnick (Ping timeout: 276 seconds) 13.00.11 Join evilnick [0] (~evilnick@5adce979.bb.sky.com) 13.00.11 Quit evilnick (Changing host) 13.00.11 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 13.02.33 Part nick-p ("Leaving") 13.18.12 Quit Jerom1 (Quit: Leaving.) 13.21.06 Quit evilnick (Ping timeout: 240 seconds) 13.57.19 Join Pradyumna [0] (~Pradyumna@117.197.219.153) 14.06.53 Join LinusN [0] (~linus@giant.haxx.se) 14.12.12 Join nick-p [0] (~nick@82-69-105-120.dsl.in-addr.zen.co.uk) 14.18.48 Join TheLemonMan [0] (~LemonBoy@ppp-170-54.26-151.libero.it) 14.23.20 Join Challapradyumna [0] (~Pradyumna@117.197.219.153) 14.26.21 Quit Pradyumna (Ping timeout: 245 seconds) 14.27.20 Join funman [0] (~fun@rockbox/developer/funman) 14.29.43 Quit scorche|sh (Ping timeout: 246 seconds) 14.35.28 # Zagor, gevaerts: There seems to be a problem with the build system's 'calculated speed'. If a host errors out early because of local problems, numbers get way too high 14.36.19 *** Saving seen data "./dancer.seen" 14.36.27 # See kugel-x-kugel in r30399..30404 14.37.02 # odd... 14.46.52 # does the build system hand out builds at random? 14.47.32 # I think it would be good if it handed out builds that the client did already recently (in reverse order) to exploit ccache, if it doesn't already 14.50.09 # it's not random, it's matched to the client speed 14.50.34 # but no, there is no consideration for possible past builds 14.50.43 # kugel: that would have the annoying side effect of possibly hiding problems for longer 14.51.21 # gevaerts: I can't follow 14.51.44 # for cases where a particular build client goes bad on a specific build 14.53.04 # but why "hiding problems"? 14.53.44 Join lebellium [0] (~chatzilla@i02m-212-194-176-149.d4.club-internet.fr) 14.54.13 Quit lebellium (Client Quit) 14.54.57 # Suppose you have three clients that can do a particular build, one of which has a different toolchain version (assume this is a sim build where that's allowed). If you add client stickyness, the one with the different toolchain will never do that build (unless it got it first), which means you won't ever see possible problems with it 14.55.31 # See e.g. the saga of the mr100 sim, Zagor's build client, and the unused variable 14.56.08 # ah, amiconn's machine now also shows that problem 14.58.00 # gevaerts: well, the build system isn't about spotting toolchain problems is it? it's about spotting build failures we introduce with commits 14.58.18 # kugel: this isn't a toolchain problem really 14.58.41 # The variable really is unused, it's just that only a few toolchain versions actually report it 15.04.40 # gevaerts: that can happen now too 15.06.12 # e.g. the player sim build has a few warnings but isn't build by strong machines with recent compilers 15.07.23 # instead it's always build by bXX-roolku because it's a low-end build, which doesn't spot the warnings 15.10.13 # so, a) it wasn't a problem back when the client speed consideration was added, and b) wouldn't be newly introduced with this idea 15.10.52 # no, but it would be worsened. because we would lock each target to machines, instead of exercising them between multiple 15.23.41 Quit user890104 (Read error: Connection reset by peer) 15.24.10 Join user890104 [0] (~Venci@6bez10.info) 15.37.19 Join benedikt93 [0] (~benedikt9@unaffiliated/benedikt93) 15.55.55 Part LinusN 16.02.16 Join domonoky [0] (~Domonoky@rockbox/developer/domonoky) 16.03.03 Quit antil33t (Read error: Connection reset by peer) 16.03.23 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 16.08.36 Join y4n [0] (y4n@unaffiliated/y4ndexx) 16.12.19 # http://i.imgur.com/7y9p3.png progress on my smART based Minecraft theme :D 16.12.51 # <[Saint]> heh. 16.18.35 Quit Bagder (Quit: Konversation terminated!) 16.19.23 # <[Saint]> Nice, the volume and battery icons should be "blocks", the build into the image when the value increases/decreases. 16.19.32 # <[Saint]> s/the/that/ 16.20.10 # the volume is the piston 16.22.06 # I'm thinking of using a redstone repeater for the battery power 16.22.07 # <[Saint]> It would be nice if the state icons were aligned properly with the "inventory" boxes. 16.22.20 # yeah I haven't worked much on that yet 16.22.25 # I plan to 16.23.17 # * [Saint] nods. 16.24.14 # <[Saint]> Put me on your list of people to bug if you get stuck, if you want. I wouldn't call myself a theme guru, but, I do alright ;) 16.24.55 Quit antil33t (Read error: Connection reset by peer) 16.25.06 # ok 16.25.17 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 16.26.26 # <[Saint]> What's the licensing for minecraft images...you've looked into this? 16.27.10 # <[Saint]> Its fine if you're recreating everything from scratch, but if you're taking images directly, you'll want to look into if the license is compatible. 16.27.40 # <[Saint]> Good job, btw. I think it'll be quite cool when its completed. 16.28.14 Quit mgue (Read error: Operation timed out) 16.30.00 # "You're free to do whatever you want with screenshots and videos of the game, but don't just rip art resources and pass them around, that's no fun." 16.30.48 # <[Saint]> it appears to be CC-SA 16.31.13 # <[Saint]> (from a brief googlin' session) 16.32.14 Join mgue [0] (~mgue@p5DDA2D5D.dip.t-dialin.net) 16.36.22 *** Saving seen data "./dancer.seen" 16.43.58 # I don't see notch being too upset by a minecraft theme for rockbox 16.46.23 # I should probably fix the hardware problem on my mp3 player before working on the theme 16.47.02 Quit antil33t (Read error: Connection reset by peer) 16.47.22 # it's not letting me write, reformat, or do anything but read my mp3 player's internal storage 16.47.25 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 16.48.35 # <[Saint]> ....perhaps its run out of free blocks to remap, and thus, shat itself? 16.49.10 # <[Saint]> if you can read from it, you should be able to see whats going on with a disk utility. 16.50.03 # the storage is 97% full 16.50.23 # <[Saint]> irrelevant 16.51.18 # I've tried fsck and it didn't fix anything 16.51.20 Quit Challapradyumna (Ping timeout: 245 seconds) 16.52.07 # <[Saint]> it can't, if it can't write to the disk. 16.52.47 # it does say when I do fsck that a lot of files contain "free clusters" 16.53.01 # so it assumes EOF 16.53.13 # Free cluster summary wrong (35207 vs. really 78830) 16.53.19 # not really sure what that means 16.53.32 # that's very common; it means you aven't been unmounting it cleanly, mostly 16.53.48 # the fsinfo sector's free space count is wrong, which normally means you unplugged the device before the OS got around to updating that 16.54.12 # yeah I unplugged it improperly and ever since it's been screwed up 16.54.51 # it was after updating rockbox so it was writing to a lot of files at the time 16.55.01 Quit petur (Quit: *plop*) 16.55.16 # anyway, it sounds like your fs is corrupt 16.55.26 # what actual fsck command are you running to fix it? 16.55.38 # just fsck 16.55.59 # That doesn't actually fix anything 16.56.04 # That just tells you about the errors. 16.56.16 # you need either -a or -r to fix automatically/manually :) 16.56.18 # I did fsck -a and it didn't do anything 16.56.36 # try with -r 16.56.51 # Once you do it there shoudl be no more errors being reported 16.56.59 # if it's still saying those things above every time then it's not fixing it 16.58.17 # pastebin the complete fsck output 16.58.24 # if you want me to see :) 16.59.40 # http://pastebin.com/LFhy6ftW 17.01.27 # and now when I turn my mp3 player on it goes to the rockbox boot loader and says "no partition found" and shuts off 17.01.48 # You just destroyed your fs 17.02.04 # When it warned you that there were differences between the boot sector and the backup.. the backup is all zeros 17.02.12 # and you chose to copy the backup :) 17.02.18 # so, now your boot sector is all zeros. 17.02.20 # oh... :p 17.02.33 # anyway, your fs is totally hosed 17.02.43 # it was anyway 17.02.45 # now it's more so :) 17.02.46 # ok 17.02.50 # format 17.03.20 # how can I format it if it doesn't connect to my computer? :p 17.03.25 # huh? 17.03.28 # it is connected to your computer 17.03.33 # otherwise how can you fsck it? 17.03.48 # I rebooted it and now it's not connecting 17.04.06 # Right, because you just destroyed the fs and now there's no rockbox to load 17.04.06 # so now I basically can't do anything 17.04.13 # boot the original firmware 17.04.24 # what device is this? 17.04.33 # sansa e260 17.05.03 # right. boot the original firmware, then, and connect it 17.05.26 # the boot loader doesn't even want to boot to the original firmware 17.05.31 Part Zagor 17.06.14 # huh 17.06.42 # all it's doing is turning on, and shutting right back off. 17.07.57 Quit nick-p (Quit: Leaving) 17.09.31 # well my mp3 player was good while it lasted 17.09.47 # and now I know not to unplug before unmounting properly 17.09.57 # i don't think this should be able to brick the device 17.10.07 # i don't have a sansa, though 17.10.08 # tjb0607: what happened 17.10.12 # tjb0607: that shouldn't cause any problems 17.10.18 # tjb0607: have you tried formatting it possibly 17.10.45 # When I turn my mp3 player on it will shut right back off, and won't even let me connect to the computer 17.10.58 # because no firmware is loading 17.11.07 # tjb0607: well, what you should've done was 1) not pick options randomly in fsck and 2) not reboot the device until you knew you had fixed it 17.11.11 # :) 17.11.13 # unfortunately ;) 17.11.41 # if fsck managed to write to it to fix/break it, then you could also have just formatted it at that time 17.12.32 # anyway. i'm somewhat surprised the OF isn't willing to boot, but it'd take someone more familiar with the pp sansas to know if that's reasonable/recoverable 17.13.21 Quit antil33t (Read error: Connection reset by peer) 17.13.44 Join antil33t [0] (~antil33t@203-100-223-143.callplus.net.nz) 17.16.17 Quit merbanan (Remote host closed the connection) 17.18.36 # I wonder if there's a way to reset the memory from opening the mp3 player and doing something 17.19.38 # jtag 17.20.03 # nope, no hard reset feature 17.24.33 # time to bid for a new one on ebay 17.27.56 Quit domonoky (Read error: Connection reset by peer) 17.30.00 # tjb0607: http://www.rockbox.org/wiki/SansaE200Unbrick 17.30.37 # gevaerts: do those devices store their firmware on the filesystem, then? 17.31.08 # tjb0607: make sure you follow the instructions though, and ask if something's not clear. It *is* possible to make things worse if you do things wrong 17.31.30 # Torne: no, but they are rather braindead 17.31.34 # ah 17.32.01 # Torne: the c200 e.g. (the e200 is a bit better) believes the FAT superblock to guess the size of the device 17.32.10 # Oh 17.32.13 # fun 17.32.15 # Which is fun if people format it as ntfs :) 17.32.33 # Or if you're me and make USB code read from the SD card and write to internal flash 17.32.51 # haha 17.33.20 # Actually, I'm not sure if the e200 is better in that respect, but at least it has the .fmt trick in recovery mode 17.35.53 # there is a VERSION.TXT file in the partition. I've put the .mi4 file on it and reset it. 17.37.54 # That didn't work. Time to format. 17.38.18 # tjb0607: you mean the "sansa.fmt" trick I hope? 17.39.09 # I got a PP5022.mi4 and dragged it into the device 17.39.41 # I didn't have one so I downloaded it from here http://daniel.haxx.se/sansa/mi4.html 17.40.16 # * gevaerts nods 17.40.17 # yes, the sansa.fmt trick next 17.41.01 # ok 17.41.32 # Just making sure you weren't about to format the recovery partition. That can be disastrous 17.41.57 # I'm following the instructions very carefully :) 17.44.02 # ok, so there's the VERSION.TXT, PP5022.mi4, and the sansa.fmt 17.44.13 # I disconnect the device 17.44.26 # and it's now formatting 17.44.52 # *Thank God I backed up my music and theme I'm working on* 17.45.18 # it finished and is now resetting the system 17.46.07 # that didn't work either. Now to restore the bootloader. 17.47.09 # Hm 17.47.47 # I sometimes suspect that the e200 needs matching firmware and bootloader, but apart from that if recovery mode works the bootloader should be fine 17.48.10 Quit wtachi (Ping timeout: 240 seconds) 17.49.48 # when I try to turn it on it says "Load to main image failed" "Switch to Recovery mode 17.51.23 # do I need to rename the bootloader rom to anything special? 17.51.39 # it's currently BL_SD_boardSupportSD.rom 17.51.46 # I think that's fine 17.51.49 # ok 17.51.55 Quit y4n (Disconnected by services) 17.52.02 Join y4n [0] (y4n@unaffiliated/y4ndexx) 17.53.16 # I unplugged it and it immediately shut off. I'll try doing it again. 17.53.34 Quit mgue (Ping timeout: 260 seconds) 17.53.39 # Did you unmount the recovery partition properly? 17.54.01 # yes 17.54.40 # it's only turning on when I plug it in 17.55.03 Join mgue [0] (~mgue@p5DDA3FD7.dip.t-dialin.net) 17.55.27 # But recovery mode works then? 17.55.46 # yes 17.56.27 # * gevaerts can't remember now where the bootloader is stored and if these symptoms might match the "flash chip comes lose" problem :\ 17.56.58 # oh now it's working 17.57.11 # I unplugged and repluged the battery 17.57.37 # While you have it open, maybe check the flash chip 17.57.59 # You should be able to see a black square somewhere. Make sure that's fully pushed down 17.58.46 # I pushed it down earlier today 17.58.58 # ok I restored the bootloader 17.59.24 # STILL not working.. 18.00.06 # Did you restore just the bootloader, or did you use all three of the .rom, .mi4, and .fmt files? 18.00.08 # huh 18.00.32 # I copied the rom and the mi4 then I created the empty .fmt yeah 18.00.43 # ok 18.00.57 # That should have been fine 18.02.45 # and the mi4 files for the e200 should work with the e260 right? 18.03.00 # yes. e200 is the entire series 18.03.19 # ok just making sure 18.05.07 # recovery mode prints constantly "LUN0 unlocked" "LUN0 locked" 18.05.25 # does that mean anything? 18.05.50 # That means you're mounting and unmounting it, or udev is having a look 18.05.59 # so no, nothing very interesting 18.07.42 # I think I'd try reseating the flash chip again, but I really don't know. I don't remember ever hearing of an e200 behaving like this 18.08.21 # so under the metal cover it's the little rubber rectangle above the battery, I push that right? 18.08.44 # yes 18.08.58 # ok so I did that 18.09.27 # what is that supposed to do? 18.10.15 # The flash chip (or daughterboard? Not sure now...) in the e200 is removable and tends to come lose 18.10.55 # ahh 18.11.16 # [Saint]: pong 18.14.03 # <[Saint]> bluebrother: Are you able to make a build for me with your AA in notification area implementation, pretty please? 18.14.26 # <[Saint]> 240x320 portrait. If you'd be so kind. 18.14.49 # I did the bootloader restore trick again after reseating it, and when I turn it on, it shows the SanDisk loader for a while, then says "Load main image failed" "Switch to Recovery mode" 18.15.37 # restoring the bootloader doesn't give any errors 18.16.07 # [Saint]: I've ran into another problem -- it doesn't work anymore after rebasing to current svn :( 18.16.20 # <[Saint]> Aaaaaaawww :-S 18.16.25 # Maybe try just the .fmt and .mi4 again, without the .rom? Which files did you download exactly? 18.16.28 # <[Saint]> Bummer. 18.16.31 # I'm currently bisecting the vorbis playback issue, will check that afterwards 18.16.46 # I can post a patch somewhere if you want to try it youself 18.16.56 # <[Saint]> bluebrother: Ok, that's cool...no rush. 18.17.08 # http://daniel.haxx.se/sansa/mi4.html the fourth one down on this list thanks to lgianasi 18.17.10 # <[Saint]> bluebrother: No build environment set up presently. 18.17.20 # it's really annoying, I wanted to get that committed :/ 18.17.49 # <[Saint]> bluebrother: Indeed, it's a damn cool idea. 18.18.21 # I'm wondering if it's useful on small screens. Since the AA gets downscaled quite a bit on those 18.18.44 # <[Saint]> bluebrother: Have you checked out my theme on the tracker? 18.19.20 # <[Saint]> Re: Small screens and AA, I wouldn't see why not. Google Music beta does it, and even though the AA is tiny, its still recognizable. 18.19.39 # maybe I could try a different one? 18.19.55 # not yet. I'm planning to give that a look this weekend 18.20.05 # <[Saint]> coolies. 18.20.17 # * bluebrother wonders why the system doesn't find the compiler after updating the NDK 18.20.22 # tjb0607: yes, always worth a try 18.20.32 # I'll see what happens if I try this on my e200 18.20.40 # maybe I should reboot that machine, it's running since quite a while now ;-) 18.22.47 # does anyone else have this vorbis playback extremely soft issue? 18.23.49 # still getting the same issue 18.24.06 # with a different mi4 18.24.25 # onse more 18.27.23 # Does it say "writing main image" at some point? 18.28.12 # yes 18.28.36 # it says formatting, reading main image, writing main image, then rebooting. 18.29.08 # Then is has to work! 18.29.10 # then load main image failed when it tries to boot back up 18.29.28 # New commit by 03jethead71 (r30409): Sanify dsp.c (re)sample buffer indirection. 18.29.37 # Unless the flash chip has a problem 18.30.04 # I'm guessing by now that it probably does 18.31.29 # Or maybe the e200 somehow suffers from the same issue as the c200 and the .fmt file doesn't fully clean everything 18.31.48 # maybe 18.32.41 Quit einhirn (Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org) 18.32.59 # * gevaerts tries to convert the c200 fixing tool to the e200 18.33.31 # r30409 build result: All green 18.36.25 *** Saving seen data "./dancer.seen" 18.36.46 # hmm. Forums down or is that just for me? 18.37.48 # bluebrother: they're down 18.38.20 # ok, thanks 18.39.24 # I guess since my sansa is bricked now I could release the beta of my Minecraft theme http://i.imgur.com/7y9p3.png 18.40.41 # tjb0607: if you want to try one more thing, download http://www.evonet.be/~gevaerts/erase.bin and e200tool 18.41.37 # wtf? Why is the playback issue gone now? 18.42.07 # I've never had a vorbis playback issue in RockBox 18.44.46 # gevaerts: ok, then do I follow the Manufacturing Mode instructions on the wiki? 18.44.50 # then put the e200 in *manfacturer* mode (i.e. not recovery), plug it in, and run "sudo ./e200tool recover erase.bin". That should then start zeroing the start of the flash (I can't remember how much...) 18.45.55 # After that, everything should at least be in a predictable state (requiring manufacturing mode). If formatting and recovering main firmware and bootloader then *still* don't work, I'd be fairly confident there's a hardware issue 18.46.09 # Note that this will take a while to run 18.48.14 # actually, the tool should install a working partition table and FAT, although they'll be too small (I copied the c240 code, which has 1GB) so redoing the .fmt thing still makes sense 18.48.20 # my mp3 player is saying "# kB left" a bunch 18.48.23 Join Horscht [0] (~Horscht@p57B57D57.dip.t-dialin.net) 18.48.23 Quit Horscht (Changing host) 18.48.23 Join Horscht [0] (~Horscht@xbmc/user/horscht) 18.48.28 # ok, it's running then 18.48.41 # It may be hard to spot, but the numbers are changing 18.49.09 # yeah 18.49.21 # it's getting lower very slowly 18.49.30 # it's at 105664 18.50.07 # On re-reading the code I actually think the displayed numbers are wrong. The erasing should still work though 18.50.17 # ok 18.51.21 Quit Horschti (Ping timeout: 258 seconds) 18.58.00 Join toffe82 [0] (~chatzilla@maf.wirelesstcp.net) 19.00.56 Quit simonlnu (Read error: Connection reset by peer) 19.02.21 # it's almost done 19.02.28 Join simonlnu [0] (RqiYHvDGJG@unaffiliated/simonrvn) 19.02.34 # it's done 19.03.10 # OK. Now you'll need "regular" manufacturing mode recovery, i.e. sudo ./e200tool recover BL_SD_boardSupportSD.rom 19.04.20 # it's in recovery mode now 19.05.20 # Good. Now copy BL_SD_boardSupportSD.rom PP5022.mi4 there and create the .fmt file 19.05.28 # Then unmount, and hope... 19.06.13 # ok 19.06.58 Join bertrik [0] (~bertrik@rockbox/developer/bertrik) 19.07.34 # it's frozen at the SanDisk logo 19.08.03 # Who's our resident AMS dualboot.S expert? 19.08.16 # Totally frozen? It stayed there a while for me 19.08.50 # It responds to the shutdown signal and plays the goodbye animation, didn't do that before 19.09.07 # IT WORKS 19.09.11 # Great! 19.09.20 # Thanks a TON 19.09.25 # You're welcome 19.09.30 # :) 19.09.33 # My plan for the clipzip dualboot loader is to first simple branch to the decompressed OF and see if that works 19.09.43 # * gevaerts is slightly unhappy about the appearance of yet another failure mode though 19.10.02 Join stoffel [0] (~quassel@p57B4DA3C.dip.t-dialin.net) 19.10.11 # next, add a delay at boot that depends on a button being pressed (so if the button code fails, it still boots the OF) 19.10.29 # finally, make the button decide whether to boot the OF or the rockbox bootloader 19.10.32 # We didn't really *need* yet another way for sansas to be half-bricked 19.11.27 # so now that the sansa firmware loads properly, it's safe to install rockbox? 19.11.33 # Should be, yes 19.11.51 # let's not be stupid this time and unmount it properly :p 19.12.01 Quit TheLemonMan (Quit: WeeChat 0.3.5) 19.12.13 # Don't ask rockbox utility to look for themes though, that's the same machine as the forums and it seems to be down at the moment 19.12.15 Join PhotoRob [0] (~none@68-188-242-119.dhcp.bycy.mi.charter.com) 19.12.26 # gevaerts, time to "brick" one of your sansas again to improve the recovery methods? :P 19.12.47 # bertrik: I did try every single step here before telling tjb0607 about it :) 19.14.42 # The sansa firmware is loaded, it says it's connected to the computer, kde detects a device but it won't mount 19.15.00 # it says "Refresh database fail" when I disconnect the cord 19.15.13 # tjb0607: it's probably still set to MTP 19.15.24 # how do I fix that? 19.15.34 # settings->usb mode in the OF 19.15.49 # You need MSC 19.15.58 # ok done 19.20.42 # I can't mount it still 19.20.53 # kde isn't even detecting it 19.21.04 # and there's no /dev/sdb 19.21.14 # hm 19.21.41 # Does settings -> info show the size? 19.22.01 # wait it has to restart. The boot takes quite a while 19.23.16 # Memory: 0 MB Free: 0 MB 19.23.33 # Right... 19.24.38 # Maybe try formatting from the recovery mode again? 19.24.44 # ok 19.25.51 # Do I put the .rom and .mi4 in too? 19.26.20 Join ChickeNES [0] (~ChickeNES@rouxbicon.rh.uchicago.edu) 19.26.24 # I suspect you have to, if you want things to still boot 19.26.57 # just making sure 19.29.07 # still 0 MB memory 19.30.08 # I'm beginning to suspect that there's a hardware problem there... 19.30.13 # me too 19.30.38 # maybe your flash chip needs a push? 19.30.47 # I'll try again 19.31.04 # bertrik: we've been through that, but also, the OF actually loads, so it does see the flash 19.34.39 # http://i.imgur.com/mwrzc.jpg 19.35.17 # would a microSDHC card help with anything? 19.36.54 # or maybe a newer OF version? 19.40.35 # I'll try changing this tool to also verify writes 19.45.05 Quit bluebrother (Disconnected by services) 19.45.06 Join bluebroth3r [0] (~dom@rockbox/developer/bluebrother) 19.45.54 Join scorche|sh [0] (~scorche@rockbox/administrator/scorche) 19.46.44 Quit fs-bluebot (Ping timeout: 245 seconds) 19.47.42 Quit PhotoRob () 19.47.51 Join fs-bluebot [0] (~fs-bluebo@g226068250.adsl.alicedsl.de) 19.50.21 Join Keripo [0] (~Keripo@eng054.wireless-resnet.upenn.edu) 19.55.39 Quit neferty (Excess Flood) 19.56.24 Join neferty [0] (~andor@173.242.127.201) 19.58.21 # tjb0607: I've updated erase.bin (still at http://www.evonet.be/~gevaerts/erase.bin) to (a) provide correct counts, (b) erase the entire flash instead of a predetermined size, (c) write both nonzero and zero blocks and reading them back to check. 19.58.34 Quit stoffel (Ping timeout: 240 seconds) 19.58.43 # The end result will be a lot slower, but it should also tell you if there's an actual problem 19.59.28 # It doesn't write a partition table and FAT superblock any more, so you will still need a full manufacturing mode recovery (the partition table wasn't really right for an e200 anyway...) 20.00.33 # If there are problems, it will stop after the first one 20.01.05 # it's working 20.01.36 # this will take a while. 20.01.46 # It will, yes 20.02.30 # We don't boost in bootloader-derived code, so the CPU is only running at 24 or 30MHz, which is *slow*. I'd rather not touch that for this sort of thing though 20.06.04 # well it's 1/16 done so far :p 20.09.28 Quit Keripo (Quit: Leaving.) 20.09.28 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 20.09.50 Part Zagor 20.11.27 Join Keripo [0] (~Keripo@eng054.wireless-resnet.upenn.edu) 20.16.07 Quit dunkaist (Quit: leaving) 20.17.01 Join Zagor [0] (~bjst@46.35.227.87.static.tab.siw.siwnet.net) 20.17.01 Quit Zagor (Changing host) 20.17.01 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 20.30.10 Quit funman (Ping timeout: 268 seconds) 20.36.27 *** Saving seen data "./dancer.seen" 20.36.31 Join robin0800 [0] (~robin0800@149.254.61.35) 20.37.45 # I put my sansa clipzip dualboot code up for review in FS#12255 20.37.46 # http://www.rockbox.org/tracker/task/12255 3sansa clipzip: dualboot code for review (patches, new) 20.42.25 # 1/2 done 20.44.50 Join petur [0] (~petur@rockbox/developer/petur) 20.51.47 Quit robin0800 (Quit: Leaving) 20.52.17 Join robin0800 [0] (~robin0800@149.254.61.232) 20.52.30 # <[Saint]> bluebroth3r: "the playback issue"? 20.53.04 # <[Saint]> Oh....you mean RaaA and random .ogg files? 20.57.38 # Does anyone have a working e200v1 nearby? What's the size of the firmware partition? 20.59.44 # gevaerts, I have 21.02.11 # bertrik: can you have a look at the partition sizes: 21.02.12 # ? 21.02.34 # gevaerts, just boot the OF and have a look at dmesg, right? 21.02.40 # yes 21.02.45 # or rockbox, doesn't matter 21.03.32 # sorry, I don't know how to find out the size of the individual partitions, I see only the total in dmesg 21.04.04 # cat /proc/partitions will tell you more 21.04.21 # That's in 4K blocks, but that's fine 21.05.13 # fdisk -l /dev/sdb gives http://pastie.org/2472494 21.05.40 Join Strife89 [0] (~Strife89@207.144.201.128) 21.06.04 # cat /proc/partitions gives http://pastie.org/2472500 21.06.52 # OK, 20MB, same as on the c200 21.07.55 # * gevaerts wonders if his code actually works.... 21.08.05 # hm 21.09.06 # Doesn't look like it does :\ 21.12.59 Join dunkaist [0] (~dunkaist@217.197.7.195) 21.13.12 # which code? 21.13.19 Join Xerion [0] (~xerion@5419A766.cm-5-2c.dynamic.ziggo.nl) 21.13.33 # I'm adding code to do the partitioning and formatting to the recovery tool 21.13.57 # Not really needed on the e200 since it has the .fmt system, but the c200 doesn't have that 21.16.52 Quit robin0800 (Read error: Connection timed out) 21.18.15 # I'm at 7,500,000/7,854080 sectors 21.18.48 # Time to get nervous! 21.21.29 # almost there... 21.22.08 # it's done 21.22.56 Join robin0800 [0] (~robin0800@149.254.61.208) 21.23.30 # how do I get it out of manufacturer's mode? 21.24.11 # Is hold still on? 21.24.20 # Normally unplug and press a button 21.24.46 # I did that and when I turn it on it's in manufacturer's mode still 21.25.17 # * gevaerts nods 21.25.41 # You now need to go back to recovery mode using e200tool, as described on SansaE200Unbrick 21.25.59 # ahh ok 21.27.40 # now I copy the bootloader and mi4 and make the fmt? 21.28.32 # yes 21.28.36 # did that, formatting... 21.29.01 # done, resetting into OF 21.29.40 # settings>info>Memory: 3807 MB 21.29.41 # :D 21.30.25 # Yay! 21.30.35 # it mounted 21.30.48 # I can edit files 21.31.07 # OK, so I suppose my old wiping code was just buggy 21.31.13 # time to install rockbox! 21.31.31 # Which wouldn't be a problem if the sansa recovery formatting code wasn't also buggy :) 21.34.27 # but rbutil is being weird and thinking the mountpoint doesn't have permissions, I guess I'll install manually 21.38.39 # [Saint]: I mean RaaAA and _any_ of my ogg files (which otherwise play fine, f.e. on the Ipod) 21.39.31 # Actually I apparently needed to run it as root 21.40.07 # <[Saint]> *derp!* ;) 21.40.25 Quit benedikt93 (Quit: Bye ;)) 21.40.27 # well dolphin was able to edit everything fine under my user! :p 21.41.04 # you need raw partition access for the bootloader 21.43.40 # ahh that makes sense 21.44.23 # now time to put my backups back 21.46.31 Join stoffel [0] (~quassel@p57B4DA3C.dip.t-dialin.net) 21.51.41 Quit stoffel (Remote host closed the connection) 21.57.30 # New commit by 03bertrik (r30410): sansa clipzip: add lcd_brightness function (to be used later to set the 'backlight' brightness) 21.59.35 # now let's unplug it while it's writing and start this all over again! 21.59.36 # jk 22.00.22 # YAY! 22.00.31 # ROCKBOX! 22.00.36 # WORKING STORAGE DEVICE! 22.01.44 # thanks a ton gevaerts, you've made my school year bearable. :) 22.02.03 # r30410 build result: All green 22.03.27 Quit robin0800 (Read error: Connection timed out) 22.05.47 # bertrik: perhaps someone should test your code? 22.06.06 Join robin0800 [0] (~robin0800@149.254.61.208) 22.07.22 # I plan to order a sansa clip zip once it becomes available for sale in my country and debug it then, I think it's not really possible to let someone else test/debug 22.09.52 # New commit by 03bertrik (r30411): sansa clipzip: annotate lcd registers 22.10.59 # I think the first real hurdle to take is to make dualboot work 22.15.02 Join Highlander [0] (~Connor_Ma@mek33-4-82-236-45-205.fbx.proxad.net) 22.15.16 # r30411 build result: All green 22.16.55 Part Zagor 22.18.24 Join Zagor [0] (~bjst@46.35.227.87.static.tab.siw.siwnet.net) 22.18.24 Quit Zagor (Changing host) 22.18.24 Join Zagor [242] (~bjst@rockbox/developer/Zagor) 22.26.04 # bertrik: maybe a good first step for the clip zip is to try inserting a delay without repacking the firmware? 22.26.10 # IIRC thats what funman did origignally 22.26.17 # to make sure he had a working GPIO 22.27.16 # saratoga, what do you mean, adding a delay without the ucl decompression? 22.27.43 Quit ChickeNES (Quit: Computer has gone to sleep.) 22.27.45 # originally funman just stuck a wait loop into the firmware so it delayed booting 5 seconds 22.27.53 # then he made that loop conditional on a button press 22.28.15 # this way he could check that he could patch the firmware without too much risk to the player - it would boot even if he did something wrong 22.30.50 # my plan for the first step is to use dualboot and ucl compression, but just boot to the OF, step 2 is to check a button and add a boot delay and step 3 is to make the button boot between OF and rockbox bootloader 22.31.16 # i suppose UCL compression shouldn't fail since its the same as the clip+ 22.32.03 # I think funman also ran the dualboot code on an emulator before (or after ...? ) trying on target 22.32.11 Join stripwax [0] (~Miranda@87-194-34-169.bethere.co.uk) 22.36.29 *** Saving seen data "./dancer.seen" 22.37.04 Join evilnick [0] (~evilnick@rockbox/staff/evilnick) 22.37.23 Quit Highlander (Quit: ChatZilla 0.9.87 [Firefox 6.0.1/20110830092941]) 22.37.38 Quit y4n (Quit: only amiga makes it possible) 22.38.23 Quit stripwax (Quit: http://miranda-im.org) 22.47.43 # I had a thought about implement backtracing on device (at least on ARM) and I think it's doable using gcc DWARF (+ some handcrafted dwarfd directive to unwind further than irq/exception) 22.50.15 # Hmm, build times are rising even though the changes are small 22.50.25 # * amiconn wonders why 22.53.39 # looks like roolku's machines are used for other work. the traitor! ;-) 22.54.49 # Only the bXX ones though, or did I overlook something? 22.55.47 # the nxx machine are working at about half their normal speed 22.55.50 # machines 22.55.58 # Ah no, the nXX ones too, just not as obvious 22.56.54 # Although - "round speed" fluctuates a lot, and some fluctuations are the effect of a primary one 22.57.48 # E.g. because the last round took much longer, my box got several builds it didn't get before, causing it to be slower, because nothing has been ccache'd for tthose builds 22.58.17 # yes. the system is too complex to predict accurately. 22.58.20 # Btw, the "sticky allocation" kugel suggested could be done for both target and android builds 22.59.06 # Only sims and wps tool should be shuffled around in order to expose them to varying toolchains 23.05.27 Quit Strife89 (Quit: Switching OS) 23.21.33 # [Saint]: ok, it's working on top of r30276. Need to figure when it breaks later 23.22.00 Quit pamaury (Remote host closed the connection) 23.23.20 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 23.25.11 Join ChickeNES [0] (~ChickeNES@rouxbicon.rh.uchicago.edu) 23.27.35 # Do we want a FAT formatting plugin? 23.28.27 # New commit by 03bluebrother (r30412): Quote command arguments to avoid the shell trying to expand them. 23.28.59 # gevaerts: for formatting the drive Rockbox is running of? 23.29.06 # Possibly :) 23.29.52 # More likely for things like archos and beast on large drives 23.30.11 # could make sense for those :) 23.30.35 # btw, is it possible to link a plugin to the system libz on Android? 23.31.07 # or can plugins only link to Rockbox libs? 23.31.11 # r30412 build result: All green 23.34.30 # New commit by 03gevaerts (r30413): Rework c200wipe to use proper partitioning and formatting code, which makes the code size-independent. ... 23.37.38 # r30413 build result: All green 23.38.04 # gevaerts: interesting keyword line that main-ppsansawipe.c has :) 23.38.20 # reminds me that I wanted to kill all keyword lines from Rockbox Utility 23.38.27 # oh 23.38.29 # right 23.38.44 # Oh well, as soon as we move to git that should be history anyway 23.39.19 # * bluebroth3r tries one last thing about his Android issue 23.39.29 # I should upload new binaries to the wiki and update the instructions there, and add a mention that the thing might be needed for e200 too 23.39.47 # I guess nobody else really wants to do that? 23.48.47 Quit pamaury (Read error: Connection reset by peer) 23.49.07 Quit robin0800 (Read error: Connection timed out) 23.54.31 Join pamaury [0] (~quassel@vit94-1-82-67-248-70.fbx.proxad.net) 23.54.31 Quit pamaury (Changing host) 23.54.31 Join pamaury [0] (~quassel@rockbox/developer/pamaury) 23.56.14 Join Jerom1 [0] (~jerome@79.132.42.100) 23.56.48 Quit petur (Quit: Leaving) 23.58.36 Join TheLemonMan [0] (~LemonBoy@ppp-131-19.26-151.libero.it)