--- Log for 29.08.117 Server: karatkievich.freenode.net Channel: #rockbox --- Nick: logbot Version: Dancer V4.16 Started: 11 days and 17 hours ago 00.04.20 Join bray90820_ [0] (~bray90820@50-83-217-236.client.mchsi.com) 00.05.02 # <_meg> brutto cornuto 00.05.41 Quit bray90820 (Ping timeout: 276 seconds) 00.09.53 Join MrZeus [0] (~MrZeus@2a02:c7f:7066:fb00:88f6:3264:7ce8:2b14) 00.12.40 Quit MrZeus (Remote host closed the connection) 00.14.49 # <__builtin> what's a good translation for narrow, as an adjective 00.18.06 Quit ulmutul_ (Quit: Leaving) 00.20.30 # muy pequeno 00.20.50 # Hm. Might be spanish 00.21.00 # I was somehow able to communicate with Italians last week in spanish 00.22.36 Quit wodz (Quit: Leaving) 00.26.45 Join MrZeus [0] (~MrZeus@2a02:c7f:7066:fb00:5cf0:590f:7934:8005) 00.31.48 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 00.32.33 Quit JdGordon_ (Ping timeout: 240 seconds) 00.49.54 *** Saving seen data "./dancer.seen" 01.07.47 # well they both derive from Latin, but italians use ciao for hello and goodbye? 01.08.55 Quit thomasjfox (Quit: Konversation terminated!) 01.09.56 # I'm sure there are plenty of other differences 01.10.29 Quit iceCalt (Remote host closed the connection) 01.12.56 Join MrZeus1 [0] (~MrZeus@2a02:c7f:7066:fb00:5cf0:590f:7934:8005) 01.15.16 Quit MrZeus (Ping timeout: 252 seconds) 01.18.42 # stretto, ristretta, ristretto, angusto, angusta I think the ristre... ones are more like short or maybe like restrict guessing from coffee terms 01.19.47 Quit _meg (Ping timeout: 276 seconds) 01.22.46 Join _meg [0] (~notsure@211.25.203.45) 01.23.09 Quit Huntereb (Ping timeout: 248 seconds) 01.23.49 Join Huntereb [0] (~Huntereb@d-209-42-136-145.cpe.metrocast.net) 01.32.51 Quit Ruhan (Quit: Connection closed for inactivity) 02.02.53 Quit MrZeus1 (Ping timeout: 255 seconds) 02.28.12 Quit _meg (Ping timeout: 240 seconds) 02.29.37 Quit quaz0r (Remote host closed the connection) 02.30.01 Join _meg [0] (~notsure@211.25.203.45) 02.30.45 Join quaz0r [0] (~quaz@c-24-18-93-195.hsd1.wa.comcast.net) 02.43.13 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus) 02.45.47 Quit Bilgus (Remote host closed the connection) 02.49.57 *** Saving seen data "./dancer.seen" 02.59.25 Join Ruhan [0] (uid76353@gateway/web/irccloud.com/x-noqhzfnffhrfeajb) 03.46.24 Nick dongs_ is now known as dongs (~dongs@bcas.tv) 04.06.57 Quit __builtin (Remote host closed the connection) 04.46.31 Quit dys (Ping timeout: 260 seconds) 04.49.59 *** Saving seen data "./dancer.seen" 05.13.34 Quit _meg (Ping timeout: 240 seconds) 05.15.28 Join _meg [0] (~notsure@211.25.203.45) 05.25.43 Quit _meg (Ping timeout: 240 seconds) 05.28.14 Join _meg [0] (~notsure@211.25.203.45) 05.33.42 Quit Ruhan (Quit: Connection closed for inactivity) 06.14.21 Quit TheSeven (Ping timeout: 246 seconds) 06.18.12 Join TheSeven [0] (~quassel@rockbox/developer/TheSeven) 06.30.06 Quit Strife89 (Quit: No Ping reply in 180 seconds.) 06.31.29 Join Strife89 [0] (~quassel@adsl-98-67-57-64.mcn.bellsouth.net) 06.39.14 Quit Strife89 (Remote host closed the connection) 06.42.03 Join Strife89 [0] (~quassel@adsl-98-67-57-64.mcn.bellsouth.net) 06.50.02 *** Saving seen data "./dancer.seen" 06.58.23 Quit Bilgus_ (Remote host closed the connection) 07.00.32 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 07.07.07 Quit ParkerR (Ping timeout: 240 seconds) 07.07.33 Join ParkerR [0] (~ParkerR@znc.withg.org) 07.07.33 Quit ParkerR (Changing host) 07.07.33 Join ParkerR [0] (~ParkerR@unaffiliated/parkerr) 07.10.34 Quit _meg (Ping timeout: 240 seconds) 07.11.17 Join _meg [0] (~notsure@211.25.203.45) 07.52.26 Quit deevious (Quit: deevious) 07.53.46 Join deevious [0] (~Thunderbi@193.226.142.214) 07.54.32 Quit The_Prospector|2 (Quit: when in doubt, kernel panic) 08.02.40 Join iceCalt [0] (~iceCalt@5.146.198.73) 08.09.01 Quit PurlingNayuki (Remote host closed the connection) 08.09.49 Join dys [0] (~dys@tmo-100-102.customers.d1-online.com) 08.14.03 Quit iceCalt (Remote host closed the connection) 08.27.12 Quit Bilgus (Ping timeout: 268 seconds) 08.28.57 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 08.31.10 Quit _meg (Ping timeout: 246 seconds) 08.32.04 Quit Bilgus (Remote host closed the connection) 08.32.17 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 08.33.07 Join _meg [0] (~notsure@211.25.203.45) 08.38.52 Join Bilgus_ [0] (~Bilgus@gateway/tor-sasl/bilgus) 08.41.57 Join The_Prospector [0] (~The_Prosp@unaffiliated/cornman) 08.42.37 Quit Bilgus (Ping timeout: 268 seconds) 08.43.51 Quit Bilgus_ (Ping timeout: 268 seconds) 08.48.20 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 08.50.06 *** Saving seen data "./dancer.seen" 09.31.51 Quit dys (Ping timeout: 276 seconds) 09.34.10 Quit robertd1 (Ping timeout: 246 seconds) 09.36.27 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 09.42.42 Join dys [0] (~dys@2003:5b:203b:100:6af7:28ff:fe06:801) 09.53.43 Quit pamaury (Ping timeout: 240 seconds) 09.57.00 Join Bozhan [0] (5778d9f6@gateway/web/freenode/ip.87.120.217.246) 10.01.39 Join MrZeus [0] (~MrZeus@81.144.218.162) 10.01.52 Join xorly [0] (~xorly@ip-86-49-24-93.net.upcbroadband.cz) 10.06.16 # Hi, I think my sansa fuze+ may be “bricked”. (http://forums.rockbox.org/index.php/topic,51932.0.html) I tried all kind of resets and still looks like dead. Any advice how to configure what is wrong? Thank you 10.39.22 Join wodz [0] (~wodz@iwl138.internetdsl.tpnet.pl) 10.50.08 *** Saving seen data "./dancer.seen" 10.56.14 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 11.01.55 Join iceCalt [0] (~iceCalt@5.146.198.73) 11.29.37 Quit alucryd (Ping timeout: 252 seconds) 11.36.17 # Bozhan, from the forums correct? 11.40.14 Quit jhMikeS (Ping timeout: 248 seconds) 11.46.28 # well idk when you'll be back so at the very least checkout https://www.rockbox.org/wiki/SansaFuzePlus#Recovery_mode 11.48.15 # Hmm, can't quite figure out how to use i2c block of atj213x. There seems to be single device on the bus at address 0xc0 which corresponds to TEA5767. The device ACK adress correctly. But reading from this device returns only 254 indefinitely. 11.48.22 # and you'll probably need linux here is our dev vm https://www.rockbox.org/wiki/DevelopmentGuide#Virtual_Machine_40Strongly_Recommended_41 11.49.46 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan) 11.52.06 # Correct 11.55.29 # Bozhan you were saying on the forum that you selected the wrong drive through the installed and now device is bricked 11.56.15 # I take it you selected the correct device at first and then the wrong device after restart of the device? 11.56.43 # sorry *through the installer** 11.59.08 # Actualy I haven't sellect any drive, but then I noticed there are some files written on the card 11.59.55 # you are on windows? 12.00.21 # Just started the installer and after popup for disconnect the sansa is like a dead 12.00.48 # right now, yes 12.01.19 # I'm downloading virtual linux now 12.01.29 # I don't think windows has a driver for the recovery mode but it should still try 12.01.46 # There is a recovery tool onlinux 12.01.49 # photorec or so 12.01.50 # with the usb cord disconnected from PC 12.02.05 # plug the usb cord into the fuze+ 12.02.19 # hold the volume up button down 12.02.28 # and plug into the pc 12.02.52 # do you get a message about device installed or even failed to install 12.04.21 # Yes, sometimes not recognizable sometimes successfully.But I can’t see the device. 12.05.27 # ok go into device manager 12.06.24 # I tried this one too: rmmod usbhid modprobe usbhid quirks=0x066f:0x3780:0x0004 12.06.40 # I'm there 12.07.03 # Is the fuze plugged in as well? 12.07.08 # Yes 12.07.26 # do you see any devices with a red x ? 12.08.08 # No 12.08.19 # I have unknown device 12.09.10 # ah ok you in devices and printers then? 12.10.03 # No, device manager 12.10.21 # On USB controllers everything looks ok 12.10.36 # No red x, no unknown devices 12.11.01 # ok if you go to devices and printers then do you have any unknown devices? 12.11.38 # I think it enumerates as rockbox device or rom recovery 12.11.42 # No 12.12.06 # while in devices and printers un plug device 12.12.08 # Sansa fuze+ is there but is greyout 12.12.26 # does it disappear? 12.12.46 # while holding volume up plug it back in 12.13.15 # ROM recovery appears :) 12.13.21 # and I assume its doing the little badonk sound each time you plug unplug 12.13.30 # correct 12.13.38 # ok good that means the device is still working 12.13.48 # now unplug 12.14.01 # ok 12.14.33 # plug it back in without holding any buttons 12.14.53 # ok 12.14.59 # do you get the sansa fuze+ greyed out again? 12.15.17 # yes 12.15.37 # ok you haven't gotten the boot loader on there yet 12.15.45 # that is still the stock firmware 12.15.56 # go back to device manager 12.16.09 # I'm there 12.16.34 # if you unplug does the unknown device disappear? 12.17.04 Quit _meg (Ping timeout: 240 seconds) 12.18.11 # No, but I got a message right now that device software was not installed 12.19.44 # hmm I want to unstall the device from, device manager but without knowing where it enumerates that'll be a pain brb 12.21.21 # http://www.nirsoft.net/utils/usb_devices_view.html 12.21.29 # I uninstalled the uknown 12.21.44 Join _meg [0] (~notsure@211.25.203.45) 12.21.54 # go here most of the way down the page Download USBDeview 12.21.54 # , Download USBDeview for x64 systems 12.22.07 # download the one for your system 12.24.20 # done 12.24.39 # ok so run it and click on the column 'Connected' 12.25.08 # do you see the fuze+ there? 12.25.26 Join robertd1 [0] (~root@201.242.188.231) 12.27.23 # Yes, but is not connected 12.27.47 # the device is still plugged in though? 12.27.59 # The connected devices are unchanged , no matter the fuze is plugged or not 12.28.16 # still plugged in 12.28.18 # hit F5 to refresh 12.28.23 # done it 12.29.02 # hmm ok go ahead and right click on the fuze plus that is not connected and choose uninstall device 12.29.47 Join [Saint] [0] (~sinner@rockbox/staff/saint) 12.29.49 # now try replugging the fuze and see if anything shows upo 12.29.59 # disappeared 12.30.12 # sorry , ROM recovery is connected 12.30.23 # oh disconnect 12.30.43 # and when plugging don't press any buttons 12.30.48 # done , disappeareed 12.31.11 # now when you plugged back in what shows up? 12.31.34 # ROM Recovery 12.32.23 # hmm ok right click and uninstall then unplug and press the power button for 30 seconds 12.33.00 # then replug, still Rom Recovery? 12.33.47 # yes 12.34.03 # got a message - usb input device installed 12.34.13 # are you downloading our VM or some other linux VM? 12.34.49 # a have a virtual OpenSuse 12.35.24 # you'd be better off grabbing our vm since it already has everything you need 12.35.26 # I'm just not sure if the USB ports are shared correctly at the moment 12.35.45 # OK 12.41.16 Quit Bilgus (Ping timeout: 268 seconds) 12.42.14 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 12.42.19 # sorry big storm got D/c 12.45.22 # everything ok? 12.46.08 # sure power just flickered and knocked my router off since its in another room and w/o a UPS 12.46.50 # ok so you will want to grab the VM and git the latest source 12.47.21 # I just downloaded the rockbox ubuntu 11.04 12.47.22 # in the rockbox folder rockbox/utils/imxtools/sbtools 12.47.22 # type make 12.47.56 Join JdGordon_ [0] (~jonno@rockbox/developer/JdGordon) 12.49.03 Quit JdGordon (Ping timeout: 248 seconds) 12.50.09 *** Saving seen data "./dancer.seen" 12.50.11 Join Bilgus_ [0] (~Bilgus@cpe-174-102-18-165.cinci.res.rr.com) 12.51.16 # IIRC you will need the Oracle guest addons 12.52.22 Quit Bilgus (Ping timeout: 268 seconds) 13.00.21 Quit iceCalt (Remote host closed the connection) 13.07.48 # downloading guest additions 13.14.08 Join Bilgus [0] (~Bilgus@unaffiliated/bilgus) 13.15.39 Quit Bilgus_ (Ping timeout: 240 seconds) 13.17.09 Quit Bilgus (Read error: Connection reset by peer) 13.18.43 Join Bilgus_ph [0] (~Bilgus_ph@108.101.201.237) 13.19.03 Join Bilgus [0] (~Bilgus@unaffiliated/bilgus) 13.19.09 Quit Bilgus_ph (Remote host closed the connection) 13.19.57 # Bozhan Sorry I keep getting kicked off I have to run some errands so i'll be bback in an hour or two 13.20.20 # OK, I will try to install all needed 13.20.25 # you need to git the latest repository 13.20.31 # is this the add on : VBoxWindowsAdditions-amd64 13.21.40 Join Bilgus_ph [0] (~Bilgus_ph@108.101.201.237) 13.22.05 # BOZHAN yes that sounds like the right addon 13.24.03 # also you will need to install a few thing to build sbloader PAMAURY is our resident guru so if you see him he should be able to help you with anything you get stuck on. Someting crypto++ related iirc 13.25.06 Quit Bilgus (Ping timeout: 255 seconds) 13.27.40 # ALSO the wiki has guides for most of it. Search for imxtools 13.28.03 Quit Bilgus_ph (Remote host closed the connection) 13.33.50 Quit mc2739 (Ping timeout: 248 seconds) 14.02.01 # to build sbloader you only need libusb-1.0-dev 14.02.31 # crypot++ is required to build mkimxboot (that creates the bootloader) 14.06.04 Quit JdGordon_ (Ping timeout: 240 seconds) 14.06.26 Join Bilgus_ph [0] (~Bilgus_ph@108.101.179.42) 14.06.36 Join JdGordon [0] (~jonno@rockbox/developer/JdGordon) 14.07.26 # Ah ok thanks for the clairfication its been a few months since i've messed with anything related to the imx 14.09.24 # BOZHAN the bigges issue you will probably have is getting the device to share usb you will need to add the devices usb_id in the vm i think its under devices/usb/add device or something along those lines 14.10.28 # There should also be something lower right corner of the status bar that does the same 14.11.21 # You might also need to eject the device from windows in order to get it to show up in the vm 14.12.18 # OH as far as the usb id you should be able to get the id from that usb dev view program 14.12.49 # actually there is a windows version of sbloader from freescale I think 14.12.53 Quit Bilgus_ph (Read error: Connection reset by peer) 14.19.50 Join Bilgus_ph [0] (~Bilgus_ph@108.101.179.42) 14.20.40 # I just runned the VM but I'm not sure the add on installed correctly 14.20.52 # I can't see rockbox folder 14.22.14 # Pamaury thats why you are our resident guru. Could you give bozhan the link? Bozhan sorry i didn't realize there was a windows version of sbloader. 14.25.20 # https://boundarydevices.com/eula/?file=sb_loader.zip 14.25.28 # I found one here 14.25.47 # Not sure if it's correct 14.27.58 # http://www.nxp.com/downloads/en/programmers/sb_loader.v1.1-g63b47f0_bin+src.zip 14.28.14 # all freescale tools are here: http://www.nxp.com/products/microcontrollers-and-processors/arm-based-processors-and-mcus/i.mx-applications-processors/i.mx-mature-processors/multimedia-applications-processors-power-management-unit-arm9-core:i.MX233?tab=Design_Tools_Tab 14.28.22 # not that they have so many ;) 14.31.26 Join mc2739 [0] (~mc2739@rockbox/developer/mc2739) 14.31.30 # Thank you, i need to download Visual Studio 2008 Professional too, correct? 14.33.12 # It says bin + src so i assume its already compiled 14.34.06 # Ha, I know why i2c readback doesn't make any sense. FM chip is NOT TEA5767. 14.37.17 # Bozhan: it contains the binary iirc 14.37.59 # pamaury: Do you know of any fm chip with i2c address 0xc0 and 0x1f registers. The access seems to be i2c_start, i2c_write(reg_addr), i2c_restart(), i2c_read() 14.38.43 # Sorry, I lost you here 14.39.06 # I tried to start the .exe - nothing happened 14.39.24 # now I'm reading user guide 14.40.13 # Its going to be a command line tool most probably 14.41.07 # And you'll probably need the cmd instance run as administrator 14.41.14 Join Ruhan [0] (uid76353@gateway/web/irccloud.com/x-revtubnlbxvryjta) 14.41.28 # yes, 1. Open a command window 2. Enter the dir in which sb_loader.exe locates 3. Copy your image to the same dir 14.43.49 Join johnb2 [0] (~johnb2@HSI-KBW-109-193-187-094.hsi7.kabel-badenwuerttemberg.de) 14.44.29 # So best bet would to make a folder in root of one of your drives with the sbloader and the boot loader 14.44.44 # BBIAB 14.44.54 Quit Bilgus_ph (Remote host closed the connection) 14.47.13 # new directory created and there are following files added: sb_loader.exe, src folder, firmware.sb and bootloader-fuzeplus.sansa? 14.50.11 *** Saving seen data "./dancer.seen" 14.52.42 # pamaury: lebellium wrote on tellementnomade that you own a NWZ-E450. Have you tried RB in it yourself? 15.00.08 # I received following error: .CStHidDevice::Download() Error (-13) during Write data 15 15.05.06 Nick uwe_ is now known as uwe (~uwe_@dslb-088-072-244-040.088.072.pools.vodafone-ip.de) 15.05.47 Nick uwe is now known as uwe_ (~uwe_@dslb-088-072-244-040.088.072.pools.vodafone-ip.de) 15.06.49 # wodz: I'll think about it, give me 5 minutes 15.07.37 # johnb2: yes I think it's correct. There is a problem with the E450, I think the internal storage is flash thus we cannot install rockbox on it (although I have everything else working), iirc 15.08.06 # Bozhan: I haven't followed the whole discussion, what is the problem with your device in the first place? 15.08.12 # pamaury: my candidate is LV24250LS. I'am trying to figure out init sequence but this @#$@#$ driver assembles values written to registers from scratch using tons of or, and and writing and reading from temp variables 15.10.06 # wodz: can't you find out by looking at the PCB ? 15.10.14 # I tried to install rockbox. Unfortunately during the installation via rockbox utility I had a sd card in the PC cardreader and some files was written on that card not to the sansa player. Now the fuze plus is dead. 15.10.36 # I tried all kind of resets and still looks like dead. 15.10.49 # that's seem very strange, why would writing files to the sd card brick the player? 15.11.12 # pamaury: marking on IC is V24230 BLK9 which can be LV24230 but online parts marking database doesn't list this marking code 15.11.44 # Bozhan: so you can reach recovery mode but the device won't boot normally? 15.12.19 # I'm not sure what exactly happened. I started the rockbox utility and there was a pop to disconnect the device. After that was dead 15.12.34 # wodz: I think the STFM1000 has address 0xc0, but the marking would not make sense 15.12.55 # was the battery low by any chance? 15.12.56 # pamaury: This one has analog output while STFM is digital 15.13.06 # wodz: ok so doesn't match 15.13.21 # Won't boot at all and ROM Recovery is all I have 15.14.13 # around 50% 15.14.49 # sounds like the flashing may have failed, unless the problem is completely unrelated. You should try sbloader with a recovery image, to see if that works, let me give you the link 15.15.01 # pamaury: seems to match LV24230LP, thanks anyway 15.16.31 # thank you 15.17.19 # Bozhan: https://www.dropbox.com/s/x5gpo0j9t6l8rbw/sansafuzep_recovery.sb?dl=0 15.17.26 Nick uwe_ is now known as uwe (~uwe_@dslb-088-072-244-040.088.072.pools.vodafone-ip.de) 15.17.52 # unfortnately I can't try it my fuze+ right now because it's at home, but I've used my recovery firmware many times and it should work assuming you device has no hardware problem 15.18.07 # it should boot and display things 15.18.24 # (I suggest you unplugged and reset the fuze+ before trying) 15.18.48 Nick uwe is now known as uwe_ (~uwe_@dslb-088-072-244-040.088.072.pools.vodafone-ip.de) 15.21.32 # pamaury: well, I have installed RB on the E453 (posted this ~10 days ago) and all codecs except flac play fine, but as soon as the screen turns off, playback stutters. I just wanted to verify that it is not only me/my hardware, but still a general problem. 15.23.12 # johnb2: oh sorry I was confused, the E450 is linux based 15.23.54 # yep, I used your NWZlinux port. 15.23.56 # ah yeah you mentioned it, but I was abroad so I couldn't try it. I'll try on mine tonight. I might have to do with the cpu frequency, I am not sure. 15.24.08 # does that happen with all codecs? 15.24.17 # how to recover the original software? 15.24.27 # Bozhan: does the recovery firmware works? 15.24.34 # I can confirm for mp3, mpc, opus, aac 15.25.29 # Bozhan: one way to recovery is to boot the recovery firmware and then write the firmware image directly to the flash (it can be easily under linux) 15.28.56 # and I have no fancy EQs active, just crossfeed and replaygain. 15.29.00 # I can't see the device at all. I have the vm rockbox ubuntu image installed. 15.29.53 # I am looking forward to seeing how it behaves on your side. Thanks. 15.30.41 Join Bilgus [0] (~Bilgus@gateway/tor-sasl/bilgus) 15.31.03 # Bozhan I'll PM you and help you get the usb workinmg 15.31.06 # Bozhan: when you plug the device, does it list in recovery mode at least? 15.31.20 # (under windows or linux) 15.31.39 # it does.. 15.33.10 # before you go any further, in windows or linux, you must be able to: 15.33.10 # 1) put device in recovery mode 15.33.10 # 2) use sbloader to load sansafuzep_recovery.sb (from the dropbox link) 15.33.10 DBUG Enqueued KICK pamaury 15.33.10 # 3) the seen should light up and display things 15.33.43 # sorry I can't be super helpful right now but I'm work... 15.33.45 # I can see it in devices and printers under unspecified as ROM Recovery. 15.34.02 # and what happens when you use sbloader with sansafuzep_recovery.sb ? 15.39.14 # with sansafuzep_recovery.sb the error is different: CStHidDevice::Download() Error(-13) during Write cbw 15.43.13 # hmm, that's odd, maybe you should try it under linux 15.43.27 # I have little experience with the windows tool 15.44.34 # first we'll need to get USB pass through working in your VM 15.46.02 # one annoying thing is that the recovery mode is extremely sensitive to any "standard" request sent before sending a firmware. the problem is the recovery mode appears as a HID device so Windows may be sending a request that confuses the ROM. Recently linux have special code for this particular device to avoid sending anything that could confuse it 15.49.58 # Bozhan PM me if you are able and i'll run you through the steps 16.01.24 Quit johnb2 (Quit: Nettalk6 - www.ntalk.de) 16.43.08 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.") 16.50.16 *** Saving seen data "./dancer.seen" 17.28.03 Quit pamaury (Ping timeout: 240 seconds) 17.31.48 Quit wodz (Ping timeout: 240 seconds) 17.49.50 Join Aldem_ [0] (~Aldem@unaffiliated/aldem) 17.53.00 Quit Aldem (Ping timeout: 276 seconds) 17.55.32 Quit xorly (Ping timeout: 264 seconds) 18.01.03 Quit _meg (Ping timeout: 240 seconds) 18.03.13 Join _meg [0] (~notsure@211.25.203.45) 18.24.24 Join iceCalt [0] (~iceCalt@5.146.198.73) 18.50.19 *** Saving seen data "./dancer.seen" 19.01.07 Join jhMikeS [0] (~jethead71@d192-24-173-177.try.wideopenwest.com) 19.06.58 Join MrZeus1 [0] (~MrZeus@2a02:c7f:7066:fb00:71a3:323:a4b6:1168) 19.08.31 Quit iceCalt (Remote host closed the connection) 19.12.28 Join lebellium [0] (~chatzilla@89-93-177-206.hfc.dyn.abo.bbox.fr) 19.19.52 Join ZincAlloy [0] (~Adium@2a02:8108:8b80:1700:c977:af6a:6c91:7d53) 19.25.39 Quit sth (Ping timeout: 246 seconds) 19.31.08 Quit dys (Ping timeout: 276 seconds) 19.41.47 Join dys [0] (~dys@tmo-122-1.customers.d1-online.com) 19.45.01 Quit Huntereb (Ping timeout: 248 seconds) 19.46.24 Join Huntereb [0] (~Huntereb@d-209-42-136-145.cpe.metrocast.net) 20.06.03 Join TheLemonMan [0] (~lemonboy@irssi/staff/TheLemonMan) 20.19.45 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 20.23.30 Join iceCalt [0] (~iceCalt@5.146.198.73) 20.31.04 # pamaury Bozhan had to go but before he did he still got an error 20.31.45 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 20.31.52 # sudo ./sbloader /home/ubuntu/Downloads/sansafuzep_recovery.sb Device: 066f:3780 @ 1.2 libusb:error [submit_control_transfer] submiturb failed error -1 errno=16 Cannot probe transfer size, using default. Transfer size: 1024 transfer error at send step 15 Error: cannot get status report 20.38.39 Join xorly [0] (~xorly@ip-86-49-24-93.net.upcbroadband.cz) 20.50.20 *** Saving seen data "./dancer.seen" 20.58.47 # Bilgus: ah a shame he is gone. when this happen you can do ./sbloader -x 1024 bla.sb 20.58.47 # and if it still doesn't work try, ./sbloader -x 64 bla.sb 20.59.55 Quit yosafbridge (Quit: Leaving) 21.00.40 # ah ok so force the size 21.01.09 # yeah, maybe I should have the tool print an advise, it's a very common error 21.04.26 Join yosafbridge [0] (~yosafbrid@68.ip-149-56-14.net) 21.27.17 Quit alucryd (Remote host closed the connection) 21.28.27 Join johnb2 [0] (~johnb2@HSI-KBW-109-193-187-094.hsi7.kabel-badenwuerttemberg.de) 21.30.07 Join alucryd [0] (~quassel@archlinux/developer/alucryd) 21.31.39 Quit _meg (Ping timeout: 246 seconds) 21.37.39 Join _meg [0] (~notsure@211.25.203.45) 22.25.34 Quit johnb2 (Quit: Nettalk6 - www.ntalk.de) 22.29.43 Quit Bozhan (Ping timeout: 260 seconds) 22.35.15 Join cc___ [0] (~ac@2001:910:113f:1:6a05:caff:fe1c:1627) 22.36.49 # john2 (logs): I can confirm your problem on my E450 22.38.09 Join __builtin [0] (~alpha@cpe-71-71-34-79.triad.res.rr.com) 22.38.09 Quit __builtin (Changing host) 22.38.09 Join __builtin [0] (~alpha@rockbox/developer/builtin) 22.41.44 Quit pamaury (Remote host closed the connection) 22.50.23 *** Saving seen data "./dancer.seen" 22.50.30 Join pamaury [0] (~pamaury@rockbox/developer/pamaury) 22.53.39 Quit dys (Ping timeout: 240 seconds) 22.55.23 Join dys [0] (~dys@tmo-112-37.customers.d1-online.com) 23.03.18 # <__builtin> hmm, what is wrong with our history page? https://www.rockbox.org/history.html 23.03.33 # <__builtin> looks like the header is somehow ending up at the end 23.09.50 Quit lebellium (Quit: ChatZilla 0.9.93 [Firefox 55.0.3/20170824053622]) 23.15.05 # john2 (logs): also now that you mention it, my E460 does it !!! 23.29.17 Quit Strife89 (Quit: No Ping reply in 180 seconds.) 23.30.46 Join Strife89 [0] (~quassel@adsl-98-67-57-64.mcn.bellsouth.net) 23.32.25 # at least the E580 does not do it 23.32.42 # so it might specific to the older ones with the em1 cpu 23.33.13 # it looks like something might be lowering the cpu speed when screen is off, but I will need to experiment more before having an answer 23.39.26 Quit pamaury (Ping timeout: 276 seconds) 23.40.01 Quit cc___ (Ping timeout: 252 seconds) 23.54.19 Quit TheLemonMan (Quit: "It's now safe to turn off your computer.")